OneSpan Inc. (OSPN) Earnings Call Transcript & Summary

Thank you for joining us. Today, we're going to share the latest OneSpan Sign innovations and show how we're extending e-signature into the broader digital agreement workflow. The focus today is practical, reducing the manual work that slows customer agreements, making those agreements easier to complete and strengthening trust in the people and documents behind them. You're going to see a mix of available capabilities, early access innovations and product direction, and we'll be sure to be clear about the status of each as we go. I'm joined by a fantastic team of OneSpan Sign experts with Carolyne Moran, Vidushi Yadav, Ralitsa Miteva, Laurence Soucy and Candice Mueller, who will take us through the innovations and explain what they mean for real agreement workflows. Rather than covering the features in isolation, we will connect each one to a familiar challenge such as preparing an agreement, collecting the right documents, helping a signer understand the terms, verifying identity or even reviewing potential document issues. Let's start with the bigger picture. How OneSpan since supports the work surrounding the signature. Then we'll move through the innovations in three key areas: speed, experience and security. Then we'll use demonstrations and examples to show how these capabilities fit into existing workflows. And we'll finish with live Q&A. So please feel free to submit questions at any point during the session. Now before we dive into the innovations, I'd like to welcome our Vice President of Product, Carolyne Moran. Hi, Carolyne. Before we dive into today's innovations, let's level set for anyone joining us for the first time. Can you tell us a little bit about OneSpan Sign and what sets it apart from other solutions in the market?

Thanks, Scott. And yes, I absolutely can. And thank you, everybody, for joining us today. At a high level, OneSpan helps organizations manage the agreement process, from preparing and sending agreements to verifying signer identity, collecting signatures and routing completive agreements into downstream business systems. What really does set OneSpan apart is how we build trust into every agreement without compromising the user experience and our technology has been proven in the most demanding highly regulated environments. That being said, we combined our industry-leading security foundation with these capabilities to help organizations defend against evolving fraud threats while moving business processes forward with confidence. Okay. For many years, organizations have relied on e-signature to digitize the final step of an agreement. But today, customers are realizing that there's so much more than just a digital signature. The digital signature is pure security, but there are so many processes that happen, so what I'd like to say is that, that signature block at the end is really only one piece of the hundreds of flows that happened before to make it happen. Our customers really value our ability to deliver fully branded experiences that meet complex regulatory requirements. They rely on comprehensive APIs that we provide for seamless integration. And we also have a handy support team ready to help you at any moment, and we also have industry expertise whenever you need. That's why evolving our digital agreements portfolio is necessary. We're expanding beyond the signing moment to address the broader challenges that happened before and after signing is captured, whether it's helping users complete forms accurately, providing AI-powered insights to understand agreements faster, validating information early in the process or connecting agreements downstream in your processes, we're focused on helping organizations drive better business outcomes from every agreement at every moment. So what's interesting is when we did take the time to speak with our customers, we consistently heard three major priorities: speed, experience and security. Those priorities became the foundation for how we approached our innovations and where we focus on outcomes versus individual features, right? If you think about it, first, customers want to move faster by reducing manual work, eliminating avoidable delays and accelerating business processes. Take, for example, auto field placement. During document preparation, it helps really to get things done quick. You may have hundreds of documents that you need to prepare depending on your lines of business and large contracts with many signature and data fields can take time. We at OneSpan, can help you place those fields and then have you validate and get you going really quickly to send your agreements off for Signature. Second, they want to create better experiences for employees, partners and users because every point of friction can impact completion rates and satisfaction. So not only do we create great experiences for our customers, we also think of your customers. In the digital world, you can still receive pdf documents, and that's why we've introduced , for example, AI submarine questions. This way, the Ciner can easily guide them sells through the entire document process. Imagine there's 20, 30 pages, and you have questions or you're not sure what you're seeing, you can easily use our AI summary tool. This way, it makes things much more impactful and also avoids delays in signing. And third, they need to maintain the highest levels of security, trust and compliance in an environment where fraud and regulatory pressures continue to increase. Our not in good order suite helps eliminate risk live as they are happening. So imagine you need attachments or requirements in order to validate the user. If someone uploads a Tambore or an incorrect file, you don't have to search and validate it. We will send an alert the moment we identify that there's a potential risk involved. What this all means is that under speed, we're helping organizations remove bottlenecks and get agreements completed faster. Under experience, we're reducing friction and making agreement processes easier and more intuitive for everyone involved. And undersecured, we're helping organizations strengthen trust, combat evolving fraud threats and meet the demands of highly regulated environments. Now that being said, I'd like to turn it over to Relenza, who will help us uncover our first innovations under speed outcomes. Thank you.

Thank you, Carolyne. Good morning, good afternoon, good evening, everyone. If I ask you right now to think about this signature, you probably picture a customer signing a contract. But here is a thing. At that moment, takes just a few seconds. What takes days, sometimes weeks is everything around it. Think about what needs to happen before an agreement is even sent teams create and maintain templates. They need to map fields for data from CRM and other business systems set up the right workflow, the authentication methods. After the agreement is signed, information is to go back to the system of record, agreements are archived and often signature needs to trigger the next step in the business process. So when you look at the entire journey, there is still a lot of manual setup and effort involved for administrators, developers and business owners. And of course, AI has the potential to change that. In fact, adoption is already high. McKinsey reports that 88% of organizations use AI regularly in at least one business function. But here is a challenge. Using AI is one thing. Scaling it is another. Only 23% have started scaling agentic AI in the organizations. And analysts are already worrying us that, by the end of next year, we may see a large portion of these AI projects being canceled and not only because of escalating costs, which is probably what you're thinking about but also due to inadequate risk controls. So that's particularly important when we are talking about digital agreements because agreements are not just another business process. They require a high level of trust there legally binding, time to identity, dependent on clear evidence auditability. So the opportunity is not to simply automate and to kind of move faster. But it's to do that. Why remaining secure, compliant, transparent and accountable. And that's really what I want to show you next with the innovations we are introducing in this section. So let's get started. Today, if you're ascending the same document again and again, you probably think to create it and play it, right? And that works well for documents that we use all the time. But what about all the rest. What about the form that is updated in the quarter or the document that you just need to send once or twice a year. In those cases, creating and maintaining templates doesn't make a lot right. Then you probably will do this manually. From customers, we hear there are two types of documents that are creating the most friction. The first one is the we go them. Many organizations still have these old forms that were created years ago in tools like Acrobat with fields that are already embedded in the document. The second one is the structured documents. I think about contract exports from world, so like a one-off agreement or simply a document that change. going to justify creating a template, what we spoke about earlier. There are no fields, no tax, nothing that you can use. So every time we need to practically start from scratch. And this is where out-of-field placement capability comes in. Coming early next year, this feature is addressing both of these scenarios. So when a document already has a structure such as our PDFs or tax or placeholders are saying like sign here. Once an signed automatically takes that structure and place the appropriate fits where they work. When no structure exists, AI otherwise is a document and suggests where fields should be placed, center simple to review and to approve this. So the goal is less manual set up, less effort and a faster part to sending agreement. Our next innovation is part of our early access program in Q1, and this is a challenge that we have heard from customers like so many times. And you probably recognize it as well. Signing doesn't happen in isolation, as we say, think about your signing core poser connected to CRM, HR, IT systems, document repositories, loan origination systems, insurance applications and many, many other applications. So that's great, right, until something changes. Maybe you need a new workflow, maybe there is a new business requirement, new regulation or just you introduced a new system. So a simple change means a problem because you need to wait for IT, for developers, for resources, the vendor maybe need to make some modifications. And even maybe sometimes there is a connector, but maybe it doesn't fit actually your use case. This is the challenge self-serve integrations to do is designed to address. It is available directly within Antonin and gives administrators access to an integration library and a local no-code environment to build, configure and adapt to workflows. So we don't necessarily need to start from scratch, so don't worry. You can start from a pre-built template and to customize it to fit our process. So you can create also entire new workforce or anything that you need. What it means this for you, more flexibility, you have more freedom to automate signing corps in different parts of your business. Second, speed changes are just happening faster. Low operational cost because there is less requirements on specialized development skills and best customer integration work. And I think the bigger point here is that your business doesn't thanks to your processes are constantly evolving. So your signing Corpus should be able to evolve as well. Self-serve integration studio is putting more of that control directly in your hands. Our next innovation is one that I'm particularly excited about. It's something which is fundamentally different. So far, we have talked about innovations that help people to complete individual steps, right? Do things just faster. But let me ask you a different question. What if the process didn't have to wait for somebody to take the next step at all? That's where our first agentic workforce capability comes in. So as we discussed earlier, signing itself is not really the bottleneck, delays happen before and after the singer. So we are working towards allowing organizations to connect AI agents to agreement workflows, helping processes move across systems while keeping people involved where it matters most. So how does it work? The solution is built on the open model context protocol MCP. It is a government integration there, which allows standardized MCP authorization practices to help organizations securely connect the AI agents, they already use. So practically, to make this a little bit more tangible, Imagine simply telling in your agent sent the updated conditions to this customer list using our approved and plate and apply our authentication policy. Pretty simple, right, the agent can coordinate the processes across connected systems, gather information, initiate the workforce, keep the teams informed. Through MCP, it can evolve trustees capabilities, such as agreement preparation with the existing templates out indications, collection. OneSpan govern how those agreement related actions are being performed compliance teams on your side define the rules maintain visibility into exceptions and stay in control of how agents operate. So mitis is really an opportunity because you can embrace speed with confidence. The goal, as we said earlier, is not simply to move faster, but to preserve trust, security and oversight. This is our first step into agentic agreement workforce, and we're excited to bring this to you as part of our early access program in Q1 next year. And with that, I will hand it over to Candice, who will take us through the innovations we are introducing in the experience category. Candice over to you.

Thanks, Ralitsa. You covered a lot of great innovations there in our speed category. Now as you've mentioned, we're going to move into experience. And one of the things that both Ralitsa and Carolyne mentioned is that customers really tell us several times that while Signature has simplified the signing experience, there's the broader journey basically creates friction for both centers and signers. And so for this really sits around preparing agreements, collecting and supporting documentation and managing the manual processes. And for signers navigating complex agreements and really understanding what is required and completing multiple steps can lead to confusion delays and even abandonment. At OneSpan, we believe a great digital experience should actually go beyond e-signature, making the entire experience easier. And why does this matter? Well, even with digitization of e-signatures, banks are still seeing issues with customer abandonment and digital workflows due to complexity. Capgemini's global banking report cited that nearly half of all customers abandoned an onboarding process. Now what's really behind this drop off. Well, Capgemini and I cited that banks responded with the findings that 75% of customers actually often submit incomplete documentation causing significant delays and 61% of banks are really overwhelmed by the sheer volume of applications that they received due to lack of automation. So that's why we're introducing the innovations designed to simplify the agreement preparation to help streamline workflows and help signers move forward with greater clarity and confidence. So the first feature that I'd like to share with you is flexible attachment flow. And if we think about one of the biggest bottlenecks to completing digital agreements, we hear consistently that collecting and improving documentation at the right time, create significant delays. And so think about a mortgage application before an agreement can be finalized, of bank needs to supporting documents such as proof of income and identification. Teams can end up chasing these documents over e-mail, SMS or a separate portal. And too often, what they receive comes back missing wrong and that further delays the signing process. Well, today in OneSpan can actually specify documents needed as part of the signing flow. The signers are prompted to upload them after they've signed. But we've actually heard from you that use cases such as onboarding, documents are really collected upfront, the e-signature. So with our flexible attachment flow capabilities, we're excited to announce that organizations will be able to request documentation directly within the agreement workflow. They can review what's been submitted and accept a return documents before releasing the agreement for Signature. The result is a more conducted experience with fewer handoffs, less rework and greater control over the entire process. So first, you can collect before you commit. You can ask signers to upload what you need right up front. So an agreement is only signed once right when the paperwork is on hand. Second, you can review and validate all of this in one place so you can accept or return each document before signing is released, right within the transaction. And third, you can make any of the key documents mandatory and keep collection review and decisions in one secure auditable record. This will replace scattered e-mails, SMS and third-party portals that you might be using today. And this all stays within a familiar OneSpan transaction. So nothing changes for your existing workflows. And this feature is an active development and it's coming soon. The next feature we are excited to announce today is self-service template ingestion. So when we first look at when you migrate new use cases over to OneSpan, this feature is going to significantly help. So most organizations have dozens, sometimes hundreds of templates, especially for complex workflows, including loan agreements, account opening forms, policy documents and such. So each form has multiple field elements, including signature fields, initials, dates, signer roles and really a lot of rules too that took time to create. Rebuilding all of this by hand is slow, it's tedious, and it's also very easy to make mistakes. And this field or wrong signing order can be a document has to be sent again or worse it gets completed inaccurately. So self-service template ingestion makes it easy to import and convert templates in seconds, whether you're importing one file or multiple. You can upload a single file or in a batch. So OneSpan reads the template and recreates the supported elements for you automatically. Document signature locks are mapped and retained during the upload. This even takes effort on any document design work because every field is automatically mapped. You save manual effort, teams, move from rebuilding the same fields over and over to simply focus on reviewing and testing. And you also gain better accuracy because fields are mapped automatically, you reduce the risk of small errors that can creep in when people create templates by hand. The goal here is really that switching should feel like an easy project that you can plan effortlessly and not feel like you have a mountain to climb. And this feature is available today. Now we'll look at how OneSpan sign is improving the customer experience. I'm deeply passionate about how we help our customers gain more effortless experience when they interact with our brand. And so think about the last time you've signed something important. It could be a mortgage, an insurance policy or a new account agreement. You were probably faced with dozens of pages of legal language. And did you read every word. Most of us don't, so one of the biggest complaints we hear from signers is that they are signing a legally binding agreement. And often, it's very difficult to fully understand what they're agreeing to. AI signer summary makes the entire experience easier for the customer. When a customer opens an agreement, they're presented with a clear language summary that explains what the document is about and highlights the key terms they need to understand. And if they have questions such as what is my interest rate or what terms am I committing to, they can simply ask in their own words and receive answers based directly on the contents of their agreement without ever leaving the signing experience. Now there is also a very important distinction that I'd like to call out today. AI signer summary is designed to explain an agreement not to interpret the terms and conditions. So it will never offer legal or financial advice. Its role is to help signers better understand the information contained in the document with responses grounded in the agreement itself. And rather than having customers copy sensitive information and put them into an external AI tool to get answer, this capability brings that experience directly into the signing workflow within an environment governed by the organization. And when customers can easily understand what they're signing, they can move forward with greater confidence. And for organizations, this means the potential for fewer abandoned transactions fewer clarification calls and a smoother signing experience from start to finish. This is also in development and coming soon. Now to Vidushi, we have another category, I'd love to transition over to you for our secure section.

Thanks, Candice, and hello, everyone. So we are living in a time where trust is being redefined, and there are two shifts that are driving it. The first one, all of us are aware, is AI, right? That has made the section cheap so much so that close to 40% of the attacks targeting organization are driven by AI. A convincing face, a voice or a document cannot be produced in minutes. So it looked real it's no longer proof of anything. But the same technology that enables fraudsters also powers the defense, right? AI that can tell a live human from a synthetic one and spot a document that was quietly audited. The second shift is that identity is going digital. The ID cards that we always carried in our physical wallets are now also being issued directly to our phones. In United States, mobile driving license from more than 20 states are now being accepted at TSA checkpoints at over 250 airports. In Canada, Alberta offers a mobile health care to all residents. And in Europe, every member state by regulation must offer their citizens, a digital identity wallet by end of this year. So fraud is getting smarter, and so are the tools to stop it. But an important point is that a signature on its own can't tell you who really signed or with what they sent is genuine. That takes confidence in two things. First, we're signing and how to prove it; and second, what they are sending. The art is applying the right checks and proportion, matching the controls to the risk so that a routine acknowledgment doesn't feel like a board of crossing. It's key to get that balance right, to trust speeds up agreements instead of slowing them down. So let's start with the first question, which is who is signing and how do they prove it, and it starts with ID verification. So earlier I said it looked real is no longer proof of anything. And that's exactly the problem. IT modification in OneSpan sign is built for, and we are making it even stronger. So first, stopping fraud at the source. So fraudsters today, they're very intelligent. I think they don't just hold up a photo to the camera. They use deface, they use AI generated phases and videos that look and move like real people. Certified lives detection is built to cat exactly this, and it confirms that it is a real live person in front of the camera. Sometimes, the signer is asked to make a simple movement like tilting their head, and that challenge changes every session, so it cannot be predicted or replayed. There are other checks also that quite a run in the background that look at things like skin textures, light reflection, timing natural involvements and the 3D shape of the face. These are the details of photo video or a synthetic phase struggles to fake. But we're not stopping there. Attackers have now also started to use injection attacks feeding fake video directly into the verification flow. So it never passes through the camera at all. Protecting against this remains our top priority in quality planned on the road map. But these checks actually only work if people actually finish them, right? So we have removed the moments where signers tend to drop off. For example, the country is automatically selected based on their geo location. If they start on a laptop, they scan QR code and they carry on their phones, and they capture their identity document holding the phone up right the way they naturally work. Last but not the least, we catch mismatches early. We automatically compare the country the signer selects with the RD document the proud and flag anything that doesn't line up. The result is a stronger confidence in who's signing and an experience your customer can actually get through. So a lot being said, let's transition, and let me show you what this experience actually looks like. So meet Mike, Mike is applying for a loan to purchase a camper. So this is a high-value transaction. Therefore, the financial institution requires Mike to verify his identity before he gets access to the documents for signing. Mike prepares his government issue ID and other attachments that are needed by the workflow and he starts the process. As you saw, the country is automatically selected based on Mike's geolocation, but he can change it. So Mike Basile follows the clear guidance and instructions and takes the picture of this identity document. However, as you will see that the document was rejected because the country did match with what he was selected. This time around, might make sure that he selects the right country and the document and repeat the same steps and takes the picture of the front and the back of this driving license. So once the document capture is done might then proceed to a facial scan. So here, we first start with a passive life to check where the AI analyzes the micro movements and life reflections. It is automatically followed by an active liveness check their pronged mic to follow the instructions on the screen. So Mike is now verified and he gets access to the loan agreement for his final signature. So now let's talk about where identity is heading next and how we are preparing for it. So you just saw how our IDB works, right, a document capture, likes detection and checks that confirm the signer is who they say they are. So this is the foundation that will continue to be, but at the same time, something new is emerging. So governments around the world are now starting to issue digital versions of IDs and digital credentials like mobile driving license that people would carry on their full wallets. The adoption is still early, and it's deferred by return and countries. But more people will carry their ID this way over the coming years. And we want, at OneSpan sign to be ready for that. So we have been exploring what that experience could look like. So imagine a signer who has a digital license on the phone. What opens and shows exactly what is being asked for, maybe just the name and whether their license is valid or not. They prove with Face ID, and they basically done. The date of birth, the address on the IMT document, the license number, they stay private because they were never requested. So what does this mean for you, right? It means more choice for your signers. So those with a digital credential or a digital ID can use it, but everyone else can continue with IDP as they do today. It's a faster and much simpler experience that helps more people complete the process. It's a strong identity assurance with signers sharing only the information you actually need. And the confidence that as a digital identity evolves, your signing process involved with it without you having to rebuild anything. And that's exactly what we are building towards. One platform that supports the full arenas that people prove who they are. So that's how we know who's signing, but even a real person can upload a wrong document or wrong tiltable that has been altered. So next, Laurence will talk more about how to make sure what they're sending is right and real.

Okay. Thank you, Vidushi, and hi, everyone. So for our next innovation, first, let's just acknowledge once again the fact that in financial services, most agreements can't move without supporting documents. You need proof of income, you may need a government ID, mined a bank statement as part of the process. And when one of them is wrong, it's actually the full agreement that can come back not in good order. So that's Nigel. It's the catch-all term for an agreement that can't move forward as submitted. And it's common to, Industry estimates that about 20% to 40% of wealth management account opening submissions come back not in good order. And I'm sure you probably have seen it happen too. For instance, a simple example, think about an agreement that's come back from review and supporting document was attached that is not recent enough. What happens then is the whole workflow that is stopping. So one has to e-mail the customer, there's a wait time, there's back and forth. There's a review step all over again. So every loop costs staff time and it costs also customer patients. You may end up with some applicants that never come back or pursue the process because of these back and forth. And I think most of the organization also treat this as a review problem or just review friction. But catching an error late doesn't actually prevent it. The problem started earlier when the document was submitted. So that's actually where we should start fixing this. So our NIGO document validation functionality will actually prevent your team from chasing missing our wrong documents and help them focus on the ones that actually need a human decision. And here's how it works. So as soon as you as a document is uploaded by saner, our system will leverage AI to classify it. Is this the id you asked for? Or is it just a random document that was attached by mistake. The signer will find out right away on the spot if it's the wrong document, while they're still in the signing session. So they can correct it and upload the right one at that exact model. So right there, you can see it prevents a whole lot of back and forth where your team are just chasing the right document. Then from there, our system will perform verification checks on the submitted document. As it expired, is it recent enough, is the image quality good enough? Or is it to blurry or maybe it's cut out halfway. So whether a reviewer will actually open the file, they will be able to preview these results right next to the actual document. They see the failures coming first. than anything that might just need a closer look than everything that actually passed. So your reviewers can go straight to the one or two things that need their judgment instead of having to manually recheck everything. From there, our system also extract the data from these documents, things like the names, the dates may be a document number, an income number. And we're making that available through our API. So it can be used to actually populate other downstream systems automatically instead of having someone manually going in and retyping everything. And lastly, the reviewer can mark each of these documents as verified or they can reject it and ask for a new one. But either way, going to be capturing this directly in the other trial. So it contains a proof of who checked it, who checked what and at what time. The result with that functionality is you have actually fewer agreements that are coming back, not in good order. Your reviewers are spending more time on the documents that actually need them. And this functionality is actually available today in our early access program, and it's coming to general availability early next year. So if we move on to the next one, it's actually very closely related. We just saw how NIGO document validation will tell you whether a document is the right one if it's complete enough and matches your requirement. But it doesn't tell you whether it's a real document. And I think that matters more every month. Taking a bank statement, it used to take scale. Today, anyone can edit one or you can use AI to generate a document in what seconds. So a document can be the right time. It can be perfectly readable. It can look in good order, but it can still be forged. So we're actually adding temper checks layer on top of that validation. And how it works, so it examines each PDF that your client will submit as an attachment and look for a sign that it's been altered or not. So think about bank statement, based on utility bill. They should all be coming from legit sources. They should not be edited. So our template will actually look for signs that it was edited after the document was created. It will look for signs that the source doesn't match what it claims to be. That may be the dates don't add up in that document or maybe that it looks like it's been AI generating. So anything suspicious is actually flag or the reviewer in the preview panel before a document is accepted. And it will not reject anything by itself. It's also tuned in to not flag everything. So a clean document will actually go through, but a questionable one, we'll get the second look. It's instead of just slipping by. We're basically giving you the signal that something may be up with a document and it's certain to decide what they want to do with this. So we just saw how the NIGO document validation ask, is this the right type of document. Is this complete enough our temper checks will ask is genuine. And I think that, that second question is just getting harder and harder to answer by eye every day. So we're going to take a look at how this looks like in practice. And the first thing you need to do is to set up and specify your attachment requirement. So if we start here a video, you can see, I have my transaction in OneSpan sign. I've added my recipient and I can go and add my attachments requirements in that specific menu. For the sake of that example, I'm adding a couple of different documents. And you can see we have a drop down here that will contain a lot of different document type. We're supporting today about 15 different document type that ranges from the usual one, driver's license, up to things such as T4, VOI check, property insurance documents. So the variety is pretty large. And the last thing we're doing here is checking that little box, verify document. That is important, and it's actually what will trigger our classification of the document, the extraction of the data and all the verification check. So once that is set up, then we can look what is happening next. So we have our attachments now that are specified. And next step as a signer, I will receive an e-mail from my bank. That is telling me I have to upload something, and I have some documents to sit. So I will most I click on the link, and I will arrive in the upload portal. So if we go to the next one, and start this so as a signer, I arrived in this portal, I can see clearly what are the requirements, what are the documents I need to upload. So I'm proceeding with that. And I will get warnings in case something is actually wrong. So for that one example, it's asking me for a driver's license, I've selected a document that is not the driver license. Clearly, I see the label here, we couldn't identify this as a driver license. I can go ahead. I know that I made a mistake, I can replace it on the spot and continue my task and new upload. So we can see how just this step will be preventing a lot of back and forth and a lot of loop with the sender. So here, we're continuing to upload and finishing this, and we're going to move to the sender view of the transaction. So December, I'm entering my transaction and right away are still despite all the documents that have been provided with a status bill. I can enter each one individually. I see what has passed, I see the extracted data I can market as approved. For the second one, we see the driver license. I have the warning. It appears to be expired. I still see the expected data, the rest of the verification check that path, but I'm probably going to reject this one. Then the third one, there's a little something here as well. It's telling me that the document may be too old. It's older than six months older than my requirements. Maybe for the purpose of this document, I only needed the proof of address, and it's fine. I'll accept it. And the last one, well, a lot of things are going wrong with this. Document is too old, and you can see the attentivity cannot be confirmed. So the temper checks showing a sign that it's been altered. We see the source was different, we've seen it was a digitercreation, which looks really suspect. So I'm going to go ahead and reject those documents there. So you can see that as the center throughout the transaction, I stayed in control of the decisions. I got the signals I needed to speed up the review process. I could see even more information that I could be seen by eye and I still get to decide if I accept and reject it and it stays within the same agreement workflow. Once again, all of that is available today in our early access program and coming to general availability early next year. So with that, that was our innovation, and I will get back to you Scott.

Excellent. And that wraps up our demos for today. We hope even Joe, getting a closer look at what's new with OneSpan Sign and how these enhancements can help you get even more from the platform. If you'd like to explore any of these features further, we've included a QR code linking to additional resources, including our latest release notes and product documentation. And whether you're already using OneSpan sign or exploring what it can do for your organization, our team is here to help. We'd be happy to answer your questions, discuss your specific needs or walk you through a more personalized demo. And before I move to Q&A, I would like to take a moment to thank today's presenters and sharing the latest digital agreement innovations.

Now we'd love to focus on answering your questions about what we've covered in today's webinar. So please feel free to type your questions in the chat. So first question, how do you see MCP benefiting integrations?

All right, Scott, I'll take that one. I think the honest answer is that integration so they are built completely by people, right? Someone writes code against an API, someone has to maintain it. And then every single time you do new features or have a new launch, you have to update it. It's an extremely manual process. right? And that's fine if you have a couple of integrations, but when you have a whole suite of them and you want to expand that, it just doesn't scale to the number of places an agreement actually needs to be. What MCP or model context protocol interface changes is the unit. Instead of managing or shipping a connector that a developer builds and maintains you expose that capability that an AI agent can discover and call on its own. Prepare an agreement, pull it status, assemble for one document or a template or a layout, you can then have the agent figure out what that sequence is and what is the right way to get it developed and push through and it can automatically take some of the teachers and functionalities that you're adding. So we do believe that the goal is to make sure that the AI agent learns and we trust it and we believe that it can build, but it's about getting the scalability and meeting the market news that we have out there. While maintaining is, again, I want to be clear on our self-service integrations. There's a middle layer where people will still use these while some are moving to the MCP agent, and we want to make sure that we manage both overall.

Excellent. And semi-related from all the innovations and functionality being discussed, is there a list of items of which will be available via the API. .

No, I can for all our features, like we always aim to have it available via API and U.S. So to your question, all the innovations that you see there will always be available by API. It might happen in phases. But as and when we launch it, our release notes will be clear. on what's supported. But yes, long story short, it will always be supported by API as well.

Yes, exactly. It's always easy to show things through the UI as they're coming up. But yes, we're 100% making them available and again, across the point, not just the APIs when you're integrated through our integrations even if they're not through the MCP.