Signing with custom info
Wednesday, May 4, 2022 at 12:03pmHi team,
We are developing a web application that uses OneSpan Api to authorize transactions. We want to know if is possible to set a signature data with values that we already have stored in our database.
We have a use case when the OneSpan transaction is rejected because a new signer needs to be added, we want to save every signature already signed in the rejected transaction and use them in a new one. Note: We create the pdf files in the web application with signature fields and upload them to OneSpan via API.
Example.
1. Final user rejects OneSpan transaction in order to add a new signer.
2. Every signed info is already saved in database (Name, authorization date, email) from previous transaction.
3. Create a new OneSpan package using previous signatures info and new ones (if applied).
4. Set signature as signed with the info that we have stored in application database.
5. Send transaction to pending signers.
Reply to: Signing with custom info
Wednesday, May 4, 2022 at 03:46pmHi there,
Unfortunately no, the signing date will always be the moment when the application invoked the API.
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Signing with custom info
Wednesday, May 4, 2022 at 01:18pmHi rdcj_89,
Thanks for your post! When you mentioned "set a signature data with values that we already have stored in our database", it sounds like you are trying to automatically sign on behalf of signers because they have already signed in the previous transaction. OneSpan Sign does provide the capability to bulk sign on behalf of signers, but it's important to be aware that the audit trail will prove that the signatures are programmatically signed by your application instead of signer themselves.
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Signing with custom info
Wednesday, May 4, 2022 at 03:44pmHi Duo,
Thanks for your quick answer. So, using bulk sign on behalf of signers function, can we provide a signing date into the request? Or there is a limitation?
Thanks in advance.