Hi Team,

We are using .net rest api to create transactions. We have one scenario where we are getting error from OSS:

"technical":"EsepCommand failed and no fallback available.","messageKey":"error.internal.default","code":500,"message":"Unexpected error. We apologize for any inconvenience this may have caused you, please try again. If the problem persists, please contact our support team.","name":"Unhandled Server Error"

 

Please find attached JSON request created and help us to understand the root cause.

 

Thanks,

I was a bit surprised to find the PackageService.updatePackage only updates package-level properties and does not deal with the complexities of adding/removing/updating the signers and documents. Given that, I am wondering if it would be advisable to simply delete the package and recreate it - seems much easier. Am I missing something? Is there a good reason not to do this?

Hi Team,

We have below types of documents in the create transaction request.

1. Sign  2. View   3. Accept

Please clarify below questions:

1. How onespansign handles different types of documents?

2. How "View" and "Accept" types of documents gets processed at OSS side? We want to sign only the documents of type "Sign".

3. Do we need to set any parameters in onespansign create request? What are they?

 

Hello,

 

When we create a package and send it to OneSpan, OneSpan sends an email to the customer to inform him/her that there is a document which he/she can sign. In this email, there is also a link to OneSpan where the document is available for signing.

I would like to ask, if it is possible to have different such email templates per package.

For example, can we have 2 different templates, and during the creation of the package we select which one to be sent to the signer?

I would like to do it in Java.