204 results matched your search criteria
Forum topic
OneSpan Sign
The customer keeps getting random OneSpan signature failures when users try to send a document for signature. The same transaction works sometime and not others.
Forum topic
OneSpan Sign
Hello,
I am new to the OneSpan sandbox and REST APIs/.NET SDK
I have the following scenario and I'm using some CodeShare samples to piece this together:
Forum topic
OneSpan Sign
i am using sand box API with PHP for electronic signature but it shows authentication error.
Forum topic
OneSpan Sign
We have a need to create a transaction entirely programmatically without displaying any type of UI. To my knowledge this is possible through the use of templates.
Forum topic
OneSpan Sign
Hello all,
My goal is to enable an admin person to easily assist with a signature package (they will be the sender) but where the admin person is strictly the sender and will never be a signer.
Forum topic
OneSpan Sign
Hi,
I've created a layout containing a signature with all available fields (Signing Date, Date, Signer Name, Signer Title, Signer Company, Text Field, Checkbox, List, Radio, Text Area, and Label) using the eSignLive designer screen, but when I retrieve the package via the REST API some of the fiel
Forum topic
OneSpan Sign
Hello there,
I am trying to send two documents to be signed by the same person. so I am creating two document builders adding the email address to each one of them, but it keeps failing with the error that the email is already in use for this package.
Forum topic
OneSpan Sign
We have a scenario where user should initial on one of the signature fields from a group of fields (like a radio button group). We have multiple questions where we want the signer to initial on one choice.
e.g.
Forum topic
OneSpan Sign
Hello Team,
Can we remove the signature that is captured @Package Level which we use to apply again on the further docs of that package. Instead of creating new package to capture new signature on Signer change.
Thanks,
Navya.
Forum topic
OneSpan Sign
I have been using a form field anchor [Signer1.Fullname1] to identify where a signature field is supposed to go when sent through the API. However, most of the documents we create in our system are done so using fpdf, so there will not be any form fields to name.