We have a scenario that if a customer signed the contract but didn't complete the payment, when the person came back again, he needs to do the whole transaction again.
So, for an archived package, can we use the same customId and Package Name?
Thank you
For over a year I have been creating packages using a JSON string as the package name (something like "{ApplicationId: 1033}"). I do this because the package name comes through in the event callback notification, and I can easily deserialize the package name and extract some informatio
Hi,
We have a requirement where we need to impose unique package name when users create a transaction. I understand that the only uniqueness that eSL has is the packageId and not the name.
Is it possible to check the uniqueness of package name before it is created?
Thank you.
Welcome to the OneSpan Community
The place for developers, admins, and end-users to get started building secure digital customer journeys
OSSToolkit, a tool designed to update the signing order in OneSpan Sign packages. Future updates will extend its capabilities, addressing additional functionalities currently missing in the SenderUI.
In recent years, the wealth management industry has faced numerous challenges that have affected its revenue streams. From changing client expectations to increased financial pressures to evolving…
In this article, credit card advice website CardRates.com profiles OneSpan's eSignature solution and security features such as digital identity verification. Summary: Digital solutions allow…
When businesses rely on manual and hybrid document processing, they encounter several challenges. Manual data entry, filing, and document retrieval demand significant time and effort, raising the…