1443 results matched your search criteria
Forum topic
OneSpan Sign
I need to add a signer to a package that has non-signature fields (i.e: textfield, checkbox, selection). Is that possible?
Forum topic
OneSpan Sign
I've noticed that the e-sign live SDK supports the ability to delegate access form one signer to another. (As documented at the bottom of this page).
Forum topic
OneSpan Sign
When I am running my code there is point where I am assigning the X and Y position to the signers, using documentBuilder.WithSignature, but next to the signatures there is a date field that has to be updated automatically, and I am trying to use documentBuilder.WithDateSigned b
Forum topic
OneSpan Sign
Hi,
Does eSignLive provide any mechanism (feed / API, etc.) to export out the statistics at an account level (e.g. # of packages created per sender, datestamp signed, etc.).
Forum topic
OneSpan Sign
Hi,
I have a scenario where a owner or a "power of attorney" can eSign the document. Currently, I have the JSON for teh rEST API to create the package where one signer can sign.
Forum topic
OneSpan Sign
HI ,
I have a scenario like i need to only pump the data and signers will manually sign the document.
Forum topic
OneSpan Sign
We have developed an API service wrapper for OneSpan Sign, using .NET framework 4.7.2. This service is currently deployed within an Azure Service App. We are investigating the possibility of moving this service to a container and running it within a Kubernetes cluster (likely AKS in Azure).
Forum topic
OneSpan Sign
Some of our clients are asking to include arbitrary documents to the package that are not intended to be signed but are just for review. While I know this is possible, I am concerned that our http posts may get so large we bump into http timeouts.
Forum topic
OneSpan Sign
It appears that all the links withing PDF document become inactive once document went trough a signing process.
i have tried 2 cases and none worked.
1. Created PDF doc with link to a web page.
2.
Forum topic
OneSpan Sign
Hi!
It would appear that the success response message sent by esign sandbox to a request for signingStatus was somehow changed, over this last weekend, from 'COMPLETED' to 'SIGNING_COMPLETED'. This seemingly minor detail cost the dev team all day today.