Alogent Webinar: Unify, the Most Modern Payments Processing Capabilities, Seamlessly Available to Credit Unions Using Keystone

Hello, everyone. My name is Bud Cristel with Correlation. I just wanted to take a minute. I'm gonna say thank you, for attending this, webinar today. If you have any questions or follow-up, need any follow-up information, please, reach out to me at Correlation. Again, it's Bud Cristel, and my email is b Cristel at Correlation Inc dot com. Your CRM also has my information. So, if you have any questions on Allergan or any of our partners, please reach out to me. And at this point, I'm gonna hand it over to to Jason. Thanks, bud. Appreciate it. Afternoon everyone, morning to, some of you. My name is Jason Chwalwein, I'm Alligin's chief strategy officer. I know I've met some of you before at various trade shows and other activities. And today we just wanted to spend a few minutes to reintroduce, any progress that we've made as well as overall solutioning and value based stories on what is our next generation product for modernizing payments, titled Unify. It's been something we've been closely attached with the team at Correlation for some time on, and we're happy to say that customers are beginning to utilize and go live on the system. And it really is something that's a game changer and something that, the correlation base of customers has access to more than any other, right now, from a competitive analysis point of view. So just really excited to talk about that for a few minutes. So, I'm joined by several colleagues today. I just wanna review a few things about Allegiant. This is a primer. The bulk of what we wanna do is show you the application and show you what it does and the value it can bring you. Just brief primer for you. Alligent is an organization. You know, we've been longtime partners with Correlation. You know, we actually have many associates who worked at financial institutions and credit unions that were associated, over the years with Correlation, and familiarity with Keystone. We're happy to say that our payment solution, runs in a very large share of the correlation base, as well as a lot of this technology we bring into the payments platform shows up in any of the Keystone partnering that we do before it shows up in any other core in the country. So again it's a value advantage for us because together we work as a team. And what we show you today in fact is gonna be something that, you know, we started to, you know, you overhear words like about napkin drawings when you're innovating, but you know we started showing this on the back of a napkin to Jeff Dent and some of the team at it, correlation long before it ever existed. So we're happy to see, continued involvement together as a team and getting this to market together. In addition, Allergan does offer process automation solutions, which is our EIM product or fast docs as many of you use today. And again we celebrate a lot of that inside the correlation keystone base and then we have an emerging business that is digital banking with our product titled Next that a few of you are working on with us today. But today we're going to focus on the payments products overall because our goal is to automate everything in the transactional ecosystem. So for us, it's about deposits and the simplification of that, how to modernize that in a payments platform overall and why we're doing it and what value it's gonna bring to you. So first off, quick primer. Why are we doing this today? Checks have changed in its in in their cycle and how we view them over the years. But what that's done for us is create an additional need to make sure we can manage the total cost of ownership over time. Because, if we went by every single indicator in the industry that said, from a pundit perspective, we wouldn't be dealing with checks today, this webinar wouldn't be occurring. Correct? So as we know, we've seen check volumes decline, at a less accelerated rate than what what has always been viewed by the industry as far as a forecast. Overall though what we've also seen is the importance and the value of the check has really increased. It was one of those offshoots that came outside of the pandemic that we really didn't expect. You know, we knew that there would be some payments modernization that occurred as as to what was written, what was not, how, consumers are utilizing what types of payments. But seeing the value of the check and how that's actually increased while we're seeing some of the volume itself decrease is really an interesting indicator. And I know all of you working payments that are on this call, they see that. You know, this for me is what it speaks to is it's a trusted piece of technology. The infrastructure that exists for checks and payments processing, long term has been the go to system, overall, even as we move into a digital format of payments. So for us, just know that post check twenty one, more items are captured remotely than in branches. We know that. However, we do know that originally the way technology grew up is systems were built uniquely to deal with branch infrastructure as well as the mobile infrastructure as well as very self-service and full service channels. The way that we looked at it was there was a a a mixture of full and self-service together and where did they intersect? And that's where the solution we're gonna show you today start to come into effect because we started seeing that we needed to place improvement on those customer experience channels not just in the aging ecosystem of what was being built in the background. So with that today, we're introducing Unify to you. Unify is our single API processing solution. So what does unit what does that mean? If we go back to the lineage of Alligent, many of you use some of our payment products today. They were always deployed via channel, and channel meant acquire a specific software instance for that channel. So would be a teller instance, could be some back office processing, it could be mobile or ATM, those full of self-service channels I was talking about today. Essentially, internal of the company, we had fourteen ways to a channel you could capture a check. Each of those carried its own technology weight and APIs, etcetera. What we set forth to do was take all of those challenges off the table, put it into a single API so somebody like Keystone can integrate into this as a unified experience. And then as you look to collapse channels into a a deposit experience for a single fraud entity, for single view, no longer will you have to maintain multiple vendors in that ecosystem to do it. You only have to maintain one. The difference is too that you can then launch off of those and deploy channels at a more ready freight. Why? Because Unify is a single platform. It's an engine, and you can bolt on each of the additional channels. So we spent many years doing this. We spent a tremendous amount of investment on this. We're happy to say we're having success that has come to market in the last eighteen months or so for us going live, throughout institutions in the US and actually overseas. So with that, I said, I wanna pass it on to Ashish Bassey, our v t our VP of product, and I want him to go over all the idiosyncrasies and the value base as to why we did these decisions, and then we're gonna jump into a really quick demo for everybody. Thank you for your time today. Ashish? Sorry. I was here, I think, talking on get our mute. So, I think apologies for that. Yeah. Thank you, Jason. So has has Jason mentioned there's been, a lot of change and your focus on how thing checks are captured, right, how the deposits are coming in, whether it's through the mobile channel, whether it's through tellers, or or for that matter, the back counter as well, thing where you're capturing in cabal. There's been a lot of change, and there's a lot of focus, that's been kept put on that. But not so much thought has gone towards the back office. And if you can look at how how the back office, back office systems are out there, there are various systems, different systems for day one versus day two. There's a, well, there's a, fracture between what it captured upfront versus what is there in terms of in terms of getting the data to be kept processed for day two care systems. And that just brings about, I think, yeah, bad customer experience cannot only for the, customers plus, plus, members who are so work at depositing the checks, but also, I think for the people working in the back office where they have to can look at think potentially two or three different systems to really take a think look at a consolidated view of the data to process on day one, versus day two. Right? And has, as a result of that, the challenges that, are being seen is that as the volumes are going down, just because of the various systems that are out there, the cost of care processing is still going up. So how do you how do you take care of that? Plus, I've we've just said this multiple times. It's just from the multiple remote channels, the customer experience or or the member experience is get totally different. And then we are faced with fraud on a daily basis through the check, check, processing, I think channels because checks are a favorite of all, fraudsters get that out there. They're looking at various various different ways of how how thing they can, go in I think exploit the channel, whether it's thing figuring out how many number of days someone does duplicate detection on, or it is taking pictures of checks through the screen and think depositing it through the K Mobile channel. So how do you really have the consolidated view and a better view in, in in in trying to detect this right up front and, catch it before it's, thing posted and cleared, to the customer's account? Those are the challenges we really think started with because we've seen this across all sizes of financial institutions, from the smallest to some of the biggest ones that we can deal with, is that each each things, with, vertical, whether it's within the financial institution or or it's, like, a vertical, within I think within the experience of the, sort of the deposit. Well, there are different needs that are out there. And just the way that the data is segregated in the multiple cap, places, and there's not one consistent view of all of the data, it just leads to a lot of, friction and can try to process the check. Right? And as I think Jason can mention upfront, there are different channels that are out there. Like, we have Capri, Pri, Unify coming out. Each one of them has been successful in its own way, but each one has its own technology. Each one has its own set of challenges as well. And the only consistent thing that's coming out from each one of them is potentially the code line and the front end carrier images of the items that are being deposited. The rest, there's a lot of data inconsistency. There's no way to, think, no simple way to get, figure out where the, where the paycheck came from, what time it came from, how how how is the, member or customer depositing it. All of those pieces of data are, I think, getting lost, which can really can be aggregated to represent a thing consolidated view of customer behavior or holding member behavior. Right? And then it's not only that, but also getting the infrastructure. I Think today, it's a cloud based world. All of the systems that are out there, yes, they can be installed in the cloud, you know, on virtual machines, but it it's a different infrastructure that could requires a lot of care and care feeding in terms of, let's say, if you have, I think, teleworkstation that goes down. One of the things that we con constantly heard and which we've which we have to definitely, fix with Unified is that it takes three to four hours to, build, I think, teleworkstation again just because of the number of files that have to be installed, the number of registry changes that someone has to make to make sure that it's working, to make sure that the DLLs are installed. And so we did a thing comparison of what the current, product we have in the hub and foundation suite, has to get what all his put on a workstation versus where it comes, with Unify. And so the magnitude is really my mind blowing. Whereas with the current hub, product, they're nearly ten thousand files and nearly get two hundred megs of, that I can put on, I think, teleworkstation versus a thing lightweight versus a lightweight, thing scanner service that has about forty files that are installed on the workstation and can just think pushing, getting a URL to the teleworkstation, and the teller is up and running from that point. So we've really taken a look at all of these aspects as to how to we'll not only collapse the silos within the financial institution, but also from so sorry. So not only, from, I think, data perspective, but also, I think, maintenance perspective on so on the workstations. And, I'll skip that. And this is what Kailunify Karelica looks at from so if you can look at it from a, I think, fifty thousand foot level. Everything is there in one database. So you don't have to go hunting for data or hunting different, with different applications, get different screens. You don't have to have get two or three get different screens. All thing look at get two or three get different get reports to really, figure out, can I reconcile? Am I balanced? Okay. If I'm, taking a look at something on, day two or day three thing whenever, where do I can look at? How do I get to that data? Because we are aggregating all of the data, plus we are aggregating all of the touch points to the data. So if they have high I think six get different changes made to the item, all of that is captured. And we are building, think persona based visualizations as well as reporting based on what you, what you really need. And, yeah, before I turn it over, get to my colleague, Halford, here to take you through, I think, some of the, some of the functionality. Some of you can already can be using Firecap product, but, with the way it looks today, it integrated with Keystone is that when the teller logs on to Keystone and selects that they want to scan a check, I think, a window pops up right there and then where it connects to the scanner and then begins capturing the capturing, yeah, with the checks within within the, that end, the cap, feeder and presents a much simpler and, I think, more unified experience thing for the cap teller where they could don't have to be, working switching between windows, get to, capture the items and then come back to KeyStone. Said that, I'll hand it over to Alfred. Alfred? Thank you, Ashish. If you could pass, presentation rights to me. Yeah. Okay. Wendy should be doing that right now. K. Thank you. K. Can you confirm that you're seeing the screen with the launcher? Yes, Alfred. We have yeah. Okay. Thank you. Thank you. Thank you very much. Okay. So as as, as Jason mentioned and as as Ashish, both Jason and Ashish has been talking about. Right? So as it as it relates to back office, one of the things that we we we put into the product as as well is the user experience. The users in the back office, the operations users, how easy it is, how easy can we make it for them when they want to access the system to see different information, how we provide that in the in the UI layer. As we as we know, right, as part of check processing and as part of going through the process of completing the different actions throughout the day, one of the things that that I've seen is to do corrections, to do to do different, processes within the within the operations, it takes multiple systems or multiple applications to do that, which means multiple installs, which means multiple user management, and and everything else that goes with that. Right? So as part of Unify, what we did was built this portal, which provides you, the ability not only to see the information, that for everything that's happening in the operations, but also to be able to access the different modules and the different things that needs to be done in the operations from the same screen. Right? So, it's it's you know, to use the term, it's unified now in the sense that you're accessing one application that will give you then you'll be able to to be able to, address all the issues or all the the work that needs to be done to to to be able to, to say that the work is complete. Another thing with Unify, that we do is that we've added as part of the design is that it's no more batch processing. Right? Every single unit, every single transaction is dealt as a transaction as it flows through the system. So you could really extract a transaction as soon as it is as it is complete without waiting on additional work to be added to that batch or to be added to that block or that job. So that's that's the other big major benefit of the of Unify. So the this first page that I'm showing, which is what we call the dashboard, it really is meant to provide a high level view of all the activities in the system at that point in time. So, here, I have it a bit color coded. Right? So we have transactions processed and electronic files ingested. So anything that is coming into the system is color coded in this in you know, with this with this blue, this blue horizontal line here. Anything that needs to be done is represented with, with this, more orange color. And work that is, from an output point of view, anything that needs to be created or anything that has been created for the day is represented there. So if you're on this screen, you're not only seeing the information that is, you know, from what has been ingested, work that needs to be done, but you're also seeing outputs in in one single page. In addition to that, you're also you're also able to see the the alerts that has been raised in the system. So anything that needs your attention, you're able to, you know, kind of, look at those and and and and take take action before it's too late. Because one of the things is that we wanna do is to provide you information to let you know that something is going on in the system that may result in the in in issues or in work, stoppage or or any interruption in the service. So we want to alert you upfront, so you can take those remedial actions before it's too late. The other thing I wanted to to bring to to the fore is that, we're, you know, we're all familiar with the end of day and and start of day process. Right? End of day is really closing out the day so you can do all your reconciliation and make sure that everything is in balance. You've created all your your outputs. Your x nines are done. Your posting files are created. Everything that you received in the system has been, you know, processed, completely, and, you know, you're ready to to finish your day. With Unify, that whole process of end of the day and start the day, I'm used to other systems being it being a very manual process where a user has to take action, some action in kicking off those processes. In Unify, that is, more automated, in the sense that everything is based on, one, the you know, your the the dates the the the valid dates are based on a calendar interface as well as from an end of day start of day process. Every channel can be configured for a cutoff time each day. So, you know, you have a telechannel, for example, having a cutoff at four PM eastern. Your branch you you know, your other channels may have a cutoff at six PM eastern. What we can what we do what Unify offers is that at six thirty PM is where you can configure your end of day to be to be, kicked off automatically. So given that time period that where you need to complete the work that was ingested, at four PM, for example, you can have your end of day being completed without any user interruption, without any user really having to take action to do that. And we have two modes of that. One mode is it completes automatically. Any any work that is still outstanding would be, would be moved to the next business day automatically. And, you know, really, there's nothing that the user would need to do. You would get a, a notification to let you know which work has been moved to the next day and so on and so forth. The other option is it's less automatic less automated. But if there's any work that is left in the system, up up to the time when you have configured in the day to complete, then the user you know, your users would be notified through an alert, and they will be able to go to the alerts page and take action on that. So those are the things that you know, one of the things that we've tried to to to to make it more automated, make it more streamlined in the sense that the user doesn't have to to go in and manually, you know, take action on those on those things. But going back to the portal, the it answers you know, we try to answer the following questions. Right? For example, how much work in terms of item count and amount has been captured from my point of presentment channels? And that is represented by transactions processed and electronic files ingested. You know, how much work for my you know, that has been captured that we need to do work for, that we need additional processes to be done manually for for the users. So here, you know, we have code line corrections. We have, you know, the pending counts, you know, as well as incoming returns and outgoing returns processes. So we're showing to the users or to the to the to the operations how much work is left to be done, you know, for everything else to be kicked off. Because as you know you know, you have the capture, then you you you correct your work, and then everything else is is is what needs to be provided in the outputs. And then the other category is all my, outputs generated as configured. Because, you know, the biggest thing is that we've completed the work, but my outputs can't go out or my outputs I have issues with my outputs going out. So, again, you know, this one page provides that whole holistic view of the system as work is being processed and and as users are in the different modules, you know, complete in the queues or complete in the different corrections that that needs to be done. There is we do display the as we talked as I spoke about the automatic end of day start of day, when a user logs in, they are, you know, presented with the current business day automatically. So, again, nothing that they need to use. They just need to log in. They're presented with the current day, and they they start working on on that on those, whatever needs to be done on that process. We also provide the ability for the user to change the layout of what they how they see the different widgets on the in the system. For example, if you're not if you don't really care about outputs, you can always change change those. For example, post next post in output. I can, remove this from the from the view and click save, and and it is it is removed, right, from my view. And all of this is based on the user preferences. So this this change that I just did will next time I log in or from whichever workstation I log in from, this view will always be presented for me, and will never change. From a from a user from a, correction point of view, I'm just gonna go into just the module just to show you how easy it is to traverse from one to the next, meaning I'm not logging in to one system, to do the corrections and then going back and forth between here and portal. We actually have the ability to launch, modules like corrections from the actual, from the portal itself. So here is you know, I'm presenting with the item. I'm presenting with the the issue with the item. The correction reason is displayed on the top right here. It's showing the FI that I'm processing for the business date, showing the current item information. The the this is this is the ISN, for example. The financial institution is displayed on the left, the the channel. In this case, it's TeleCapture, and of, obviously, the business date. This is an example. Right? Because normally with TeleCapture, you'd be capturing the work at the point when the user is, the when the teller has, you know, processed the item. But this is more for the from a demo purposes point of view. We also have, different image views. You can look at different image formats. For example, if you need to look at an item because you may see more imperfections if you're looking at the JPEG version of the image versus the the the the TIFF version. So we provide that information as well. If the item came in, where it was, you know, it was captured, you know, maybe front to back or vice versa or or anything like that, we can allow you to flip or rotate the image, and then save the image orientation as part of that. And this process is because we have everything in in based on a transaction level or at an item level, Every item is presented in this corrections module based on, you know, an item at a time. So one of the one of the the the the things that this resolves is that I'm not sending ten items or twenty items or thirty items to one to one user and then having issues with packets and and and and all everything that comes with that where packets get corrupted, you miss items, and and so on and so forth. Right? So users will just correct all these items. They get one item at a time. They correct it. For example, if I I was to correct this one, I would, it would you just click next, and the next item is presented to them. So that's what the this, this this corrections module is is meant to is meant to provide. The other the other process is incoming returns. And as you know, incoming returns with the with the chargeback files that we receive from the from the Fed, from a partner, that takes you into the incoming returns module. You are able to, this screen is a is a representation of I received three files for incoming returns. It shows the the original RT, the send in RT, number of items that are provided that came in the file. It also we also track the items remaining. So if I'm a supervisor and I go into this page, I will be able to see what is left what is left to be done on the incoming you know, more details on the incoming returns process. In, you know, in one case, I'm showing that one file has been approved, which means it's ready for charge the the chargeback notices and advices and the chargeback posting file to be created. But we have one that's in progress for which we need to go in and and and review items. And, again, you can see that the the UI is is pretty, is is pretty constant. How we try to provide information between from one module to the next, you'll see that the UI is is pretty much the same. All the same controls just has different information, that we present based on what is required for that module. So in incoming returns, we we have we can provide some, we provide some item information, the deposit date, the payer bank, the original ISN. We we do that because we need to provide we we need to look up in our archive to find information such as the depositor account number if it's not provided as part of the addendum record. We also can provide information on the addendums that were that were presented that were provided as part of the file itself. The account information section is is something that we we can, we can integrate with a web service call from the from the core that would provide this level of information. We also have, what we call a customer information repository that as you provide information to us, from KIF, for example, we can call that, web service that's internal, to provide this level of account information such as the account the account name, could be the the balance the average balance, for example. You make, notation whether the chargeback is allowed if this is a new account because normally, you know, FIs normally treat new accounts a little bit different from established ones. And, this would be an indicator that will be provided in the CIF as well as if the account has holds. So a lot of information that we can display on the screen that helps the user to make an informed decision, because these are chargebacks. Right? Whether to, charge back the account, which means that I'm gonna charge I'm gonna, you know, create a file. This item will be included in the posting file that will take the funds from the customer's deposit, or represent, in which case for representment, I'm saying I want this account you know, it was for NSF, and it's the first time I wanna send it back to the to the paying bank to see if the item can be paid. Or, you know, in some cases, we do you do get items that are not your item. So we have that indicator as well that we can provide, and that will kick off the, the adjustment process with the Fed or with your partner to to to retrieve those funds for the item that they sent to you in, in error. Our outgoing returns, module is is pretty much the same. And as you can see, you know, again, we show the exception file. You're going to review items. Again, same same you know, similar UI just to keep the consistency, but different information. Instead of, you know, chargeback and and and redeposit or represent what we're providing as part of exam options for decisioning is return and pay. So you'll be able to you know, when these files are received from the host, it's ingested in in in Unify, and you're able to make, pay or no pay decisions. And then if if if it's if you say it's it's, you wanna pay the item, then that item gets into your posting file and sent to the core. If it's say if you say return, then then this item gets into an outgoing ICLR file that goes goes back, to, in this case, to the bank of first deposit, for them to do their, chargeback process. So, you know, again, you know, all the UI the UI, you know, we try to keep it, you know, consistent, so the user has a has the same level of, experience throughout the applications that they interact with as part of the as part of Unify. I will also so that's the that's from the the the the, you know, the main page where users can can interact with. But from a, you know, supervisor level or even other users who have who have the roles to be able to see additional information in the system, we can also we also provide a way to drill down on the the different files that are collected or different inputs or channels that are collected throughout the day. So for for I'm gonna just choose electronic cash letter, for example. So I when I click on this link, it tells me the file name that was ingested, the item count associated with with each of the file names, the total amount, gives me a status as well. Was it is it an error captured? You know, what time did I receive the files and so on and so forth. So just a just a way for the you know, somebody who is managing the system like an operations manager will be able to, you know, do you know, drill down a bit more on the the the types of files. If you're used to getting, like, say, ten files from the Fed and they're they're named a certain way or from a partner, you'll be able to come here and say, hey. Let me check if the if I received all my files from from this partner or from the Fed or from, you know, from whomever. You'll be able to to do that here and and and confirm, that you received those files for the day. The other page is is outputs. You know, on on like I said, on the portal, we did we showed, like, a a high level, of how many outputs are generated at that point in time. The this page, though, shows, the ready for generation page shows you all the outputs that are configured in the system. And in some cases, it also displays which ones have items that are ready for generation. And you will see some of these the item counts are here. But one of the things that we also do in Unify is for you to be able to schedule outputs automatically. So, again, nothing that the user needs to do to be able to, to, you know, push a button or or make a decision to create outputs. So some of the options that we have as part of the scheduling is, and I'll click on this drop down. So you, you know, there's items threshold. So if I want to create, outputs based on, you know, number of items, I wanna create this output, for every ten thousand items that is processed in the system and ready. I can I can schedule it to do that as well as amounts or so? If I wanna create one every ten thousand item or every twenty thousand dollar at a twenty thousand dollar limit regardless of the number of items, that's also, that's also, supported. Time schedule is also the other one. So if I wanna schedule one at, you know, twelve PM, three PM, and six PM, you know, in this example, that is that is also supported as well as interval every two hours, starting between eight and six PM. I wanna schedule a, this output every hour on the hour, as well as, monthly scheduling. So if there there are reports that you need out of the system that are more management type, maybe activity type, those can be scheduled on a monthly basis and and will be generated accordingly. We also have days that items can be scheduled. So if if you want your reports to be just be scheduled on regular business days, Monday to Friday, the checkbox is there, to denote that. But if you want your post to be scheduled every single day of the week, that is also something that that is supported as part of the Unify, the Unify offering. The, then we get to the alerts. Right? So the alerts page, we display, all the alerts that are raised in the system. And one thing about notification that I wanna add is that as part of the notification process, a user can be notified on certain alerts. So if you want certain alerts to go to more admin users versus you want some to go to, you know, more regular users, we have those capabilities. We we can send notification on alerts as well as we can send notification on item and transaction state changes. So if there's work in the system that needs to be completed, for example, I have work in corrections that, that are now ready to be reviewed by users or to take action by users, we can send we can send a notification to that user group to let them know that work is ready. So, again, you don't have to be on the system, you know, polling or looking at, anything constantly. We can actually, you know, be proactive in that and send you notifications to be able to, take action, whether it's an alert or it's taking action on, work that needs to be completed to to to finish your day. So last page that I'm gonna show you is this is the search. So we do have a you know, as part of, Unify, we do have a, you know, a a what I call a a basic search feature where you can, search for items, within the system based on your financial institution. If you wanna search for a specific channel, you can select that. And the drop down is just basically the any channels that you are you are configured for. You can search between the number of days, and this number of days is based on, what you have configured for as it released the retention. So I'm just gonna search for a few items here. And once the item once the list is retrieved, some information that we provide as part of the as part of the view is we provide the image, give you a view of the image. We also let you know if there are user overrides. Was, you know, was duplicate detection overwritten, image quality, pay name. We also show you if, you know, which output files the the, the item was a part of when it was extracted and so on and so forth. So, full range of information that we provide as part of the the search, the search capabilities. So I'm going to that ends the the demo. Try to you know, I know it was pretty fast. Try to cover as much as I could, as part of this, but I'm gonna turn it over to Wendy, for the next section. Great. Thank you, Alfred. And thank you, Jason and Ashish, also, for your presentation. We're going to take some questions right now. If you have any questions, please put them in the chat and go to webinar. We did get a handful prior to the call. And also, we will be at the client excuse me, the correlation client conference in a few weeks. So if you have any questions between now and then, obviously, feel free to reach out to us, but also, stop by our booth and, talk further with our team on-site there. Okay. So our first question, how would the Keystone integration to Unified benefit my credit union? Alright, Wendy. Thanks. I'll I think I'll take that. Well, how it would, benefit, couple of things that we wish to highlight. Number one, which I said when we were going through the presentation is that you no longer have to look at the multiple different, with different applications, to what we can determine what the, fate of the item is. Right? So nor can you have to, worry about what happened to the data thing that was they captured on day one, but at some point is now can no longer available for you to research on. There's multiple financial institutions that we have visited, in our, so in the total experience Cadet Cadet, Jason, and I have had is that the whether it's big or small, it really doesn't matter because there are different applications sitting out there for various reasons that have something piece of the data and some don't. So in order to, I think, bring all of that get together, you are maintaining things separate separate applications to get really achieve the same thing. So while, yes, not only from, thing, teller experience of it being a smooth experience of get going from keystone, get to capture the item, just the fact that we have this wealth of data that we are capturing and then not getting, well, for a go of it will just make, from what we've seen and what we've demonstrated, get to get our, customers and potential customers. Just having all of that data get together into one place can really helps get throughout the journey of the check. Great. Thank you, Ashish. Another question we have, what use cases does Unify consolidate? Okay. So what use case does it consolidate? So number one, we have one API that allows you to capture across all the different points of presentment. Right? So the, so you can can use the same set of, business rules if you need to to process the item in regardless of where it came from. There's, not only a consolidation of getting the infrastructure, but there's a consolidation of the channels. There's a consolidation of the user experience upfront as well as in the back office. So I don't think there are well, there are any applications out there that can provide you get that, breadth of, thing breadth of experience thing and consolidation of the data across all of these channels? Thank you. Yes. We have another question, about other Allergan products, in relation to Unify. This asks, is UNIFY a replacement for Imagepoint Hub, and does it also replace Foundation and Archive? Yeah. Great question. So, yes. I mean, it does get replaced all of those applications because it's one, system that provides you getting the ability to capture and process and clear the item on day one. It then sends all of the data that you've captured Kendo aware, which is getting the replacement cap for our archive cap product in the Hubsuite. And, you can then think think perform the day two operations within Qunify as we hold as part of getting the demo, for get returns as well as get chargebacks. So it's thing not only getting replacement, but, really, it, so it's, I think, better version of the hub, thing, foundation and archive together. Okay. We have another question about capability. How does Unify address auto approval, endorsement discarding, sale date processing, fraud detection, exception processing, and cutoff. Yeah. So what we did in terms of creating the Cabusiness Carew's engine is that we took the best of Cabot Worlds, That being our, I think, our legacy products that we have running at some of the largest banks, out here in keeping the states as well as, you know, across the pond, as well as in Canada. I think that Cap Business Carol's engine has a lot of capability, thing in the sense that you can script, anything you want in terms of getting the auto approvals, whether you want to say that, anything above or kept below, let's say, five thousand dollars, I don't want anyone to look at it. Or think based on the risk tolerance thing of the financial institution, you can script that. So, anything where you you want to change it, think based on the based on getting the changing requirements, it's it hits a simple get change given in the script. Thing in terms so anything that you want to really, someone could, putting, cannot get look at, it's I think it's just a matter of having that right setting thing in there to make sure that whatever kind kind of kind of exception it is, whether you want to would not consider getting the dollar amount to be a part part of, let's say, a duplicate detection because sometimes these days, there have been various, various things get reported, saying that the code line is the same, but they change but they get changed getting the dollar amount. And so so and and so getting the items are kept going through because of that because we are putting typically, you could duplicate detection, his thing done, thing on the entire code line plus the dollar amount. So there are various things being get done by people, thing outside to try and defraud the system. So, really, the business, rules engine that we've can build really takes care of all of those, kinds of situations where that can be scripted and made sure that we catch all of the ones that we can thing before the item is posted and clear. Great. Thank you, Rashid. Yep. We did go a few minutes over, our forty five minute mark. So, I do wanna thank everyone for staying on. We've answered all of the questions that we've received, at this time. But if there are any other questions, please, do reach out to our team, and we will get back to you directly, after today's call. Also, thank you again to our presenters, and to correlation for their partnership. As I mentioned a few minutes ago, Allergan is going to be a sponsor at the correlation, client conference in a few weeks. So please, visit our booth, say the say hello to our team on-site, and learn more. We'll have a demo there as well. If you would like any additional information, like I said, please reach out. And, thank you again for your time today. Have a great rest of your day. Thank you, everyone.