OneSpan expands its e-signature pitch to the agreement work around the signature

OneSpan's update starts with the bank employee who builds an agreement before any customer sees it. That person gets a redesigned interface built around a single dashboard, and AI helps place the fields on the document ^[5]. Automated good-order checks are meant to catch problems earlier, and attachments are inspected for tampering ^[7].

Ashish Jain, OneSpan's chief technology officer, said the value of an agreement lies in "the business outcome the agreement enables" ^[3]. At a bank, that might be a new account or a loan ^[3]. OneSpan is applying intelligence "where it can remove unnecessary work," he said ^[4]. The outcome is the pitch. The work being removed is smaller and easier to check: fields placed by hand, and document problems that surface late ^[5][7].

The customer side is harder to judge. Someone reviewing the agreement before signing can open an AI-generated summary and ask the software questions about the document ^[6]. Identity checks gain advanced biometric verification and support for digital credentials and wallets ^[8]. Credential support was also built into DigipassONE, the authentication platform OneSpan launched in July ^[10]. None of it is supposed to slow the customer down, according to OneSpan ^[9]. The case for a summary assumes that a customer who reads one signs sooner and calls the bank less. No completion or support-call figures for the feature were published with the announcement.

Andrew Gens, a research analyst covering AI software at IDC, said customers want agreement data connected to broader business systems and AI initiatives ^[15]. "Value creation is expanding beyond signature capture and toward the broader agreement lifecycle," he said ^[14].

For a bank team deciding whether to pilot, I'd sort every item on two axes. One is whose work it removes: bank staff or the customer. The other is whether that work is counted today. Field placement and good-order checks land in the staff-and-counted box for any team that already logs packets sent back for errors, because that log is the baseline ^[5][7]. Summaries and Q&A land on the customer side, and they get counted only where the bank tracks drop-off at the review screen ^[6]. Planned agent access through the Model Context Protocol is staff work after signing, where OneSpan expects fewer handoffs ^[11].

I'd start with the staff-and-counted box. Those features have a before-and-after a bank can measure in its own exception queue, and the tradeoff is that a customer never sees them. The question for OneSpan's Oct. 14 webinar is which items in that box ship now ^[17].