2081 results matched your search criteria
Forum topic
OneSpan Sign
we get attached error:
error=redirect_uri_mismatch&error_description=redirect_uri%20must%20match%20configuration
Forum topic
OneSpan Sign
Is there a way to add custom meta data like an external transaction Id from a different system at the document level? I see where we can add Fields but I don't want this to be populated on the document.
Thank you
Forum topic
OneSpan Sign
Hi,
Please let me know whether eSignLive will accept when Owner Signatory Name and Insured name having spaces and sent in the request.
Thanks,
Allanki
Forum topic
OneSpan Sign
Hi eSignLive,
Currently the documents are auto navigating to next document with in the same package once the signing completed on document.
Forum topic
OneSpan Sign
I am implementing eSignLive integration with one of my services. I need a detailed documentation of all 'Optional details message' for 400 Bad requests that can be thrown on createPackage SDK method. Is there such a documentation available?
Forum topic
OneSpan Sign
Hi,
Is there any requirement on the PDF so that Position Extraction is captured by the REST API?
The problem I'm having is that Im working with a 3rd party which delivers a PDF with Signature Fields in the PDF.
Forum topic
OneSpan Sign
At Onboarding Accounts we have an issue with customer signed documents including Customer Agreement, Statement of Income, Customer Consent which in some cases OneSpan does not return to PEGA or there are delays in response. which causes the Unique Client File to be incomplete.
Forum topic
OneSpan Sign
Hello,
Forum topic
Intelligent Adaptive Authentication
Hi Team,
Trying with below textfield with defaut value, but not showing text field after onespan sent the document.
{{*esl_InstitutionName:" + ID + ":textfield:offset(0,-2),Value("Enter the client details")}}
Forum topic
OneSpan Sign
Hi there.
What I'm trying to do is specify the sender of a package to be [email protected]. Our main account owner is [email protected]. No matter how I update my JSON, the package sender is still [email protected].
Here is my pertinent JSON package