OneSpan Introduces DigipassONE, Bringing a Unified Platform Approach to Authentication Modernization
A new authentication platform helps financial institutions support diverse customer authentication preferences while modernizing at their own pace Learn More
927 results matched your search criteria
Forum topic
OneSpan Sign
Hi !
I'm trying to update a package and replace the pdf document in it, but I get this error :
Unable to update package settings. Exception: Le serveur distant a retourné une erreur : (403) Interdit. HTTP PUT on URI https://sandbox.esignlive.com/api/packages/-bANyCo4NvqdgiEPNbMG2tLdaRE=.
Forum topic
OneSpan Sign
We are facing issue with the TextAnchor visibility issue in the PDF’s on Signing Date field.
Forum topic
OneSpan Sign
Silanis
I’m a developer for Mendota Insurance. We’re still in the development phase using your eSignLive product in your sand box environment. I have some questions around the reporting.
Forum topic
OneSpan Sign
Hi! All
We have a requirement where the user need to fill in forms with additional fields being entered in the PDF post OneSpan signatures.
Forum topic
OneSpan Sign
Exception in thread "main" com.silanis.esl.sdk.internal.EslServerException: Could not create a new package in one-step Exception: HTTP POST on URI https://sandbox.esignlive.com/api/packages resulted in response with status code: [400, Bad Request].
Forum topic
OneSpan Sign
Guys,I am getting this error when trying to update the package status of a package. Is there something going on with the PUT call? I am able to do the other POST calls.url - https://sandbox.esignlive.com/api/packages/{transactionID}
Forum topic
OneSpan Sign
We have integrated with OneSpan using your .Net SDK (version 11.12.0.0 ). We are experiencing a scenario where we have a transaction has 1 document, 1 recipient and 1 attachment request. The document is signed and the user uploads an attachment. The sender rejec
Forum topic
OneSpan Sign
Hi,
We're investigating a production issue where some packages are not completing, even though they appear to be complete. They return a status of "SIGNING_COMPLETED" when queried via the REST API.