225 results matched your search criteria
Forum topic
OneSpan Sign
Hi,
We've discovered some behaviour that seems strange/inconsistent to our team. It may just be a case of not understanding the APIs properly, but either way hopefully you can help us out.
Our application supports both remote and in-person signing.
Forum topic
OneSpan Sign
Is there any way how we can authenticate the signing process using email address rather than the phonenumber.
The scenario to be more precise is that
after eslClient.SendPackage(packageId);
When we get the signingUrl back, we would want to authenticate it via email.
I have found the authentication
Forum topic
OneSpan Sign
Hey,
I am looking to include SMS authentication for a signer by first creating an authentication object and then including it in the constructor for the Signer object.
Forum topic
OneSpan Identity Verification
For work I have to use the One Span Authenticator. But I use a Librem 5 phone.
Where can I find the Authenticator application to use on the Librem 5 to authenticate myself?
Forum topic
OneSpan Sign
Im using the REST API and doing a POST to /authenticationTokens/sender to get a SenderAuthenticationToken.
Forum topic
OneSpan Sign
Hello,
Forum topic
OneSpan Sign
Hello,
I am working with .NET SDK. Currently according to my requirement I need to change my enforceCaptureSignature to true for allowing user for multiple time signing. While searching for solutions I found "https://sandbox.esignlive.com/api/packages/{packageId}".
Forum topic
OneSpan Sign
Hi
I am trying to perform an in-person signing but I require to authenticate the signer. I have enabled SMS/Security Question authentication while creating the transaction. The authentication mechanisms work fine when the signing process is started from the link sent through email.
Forum topic
OneSpan Sign
After creating a package, I get the session token for that package, and return the access signing URL which I pass to an iframe.
The ceremony comes up but with this error at the top in a red box:
“Unexpected error. We apologize for any inconvenience this may have caused you, please try again.