45 results matched your search criteria
Forum topic
OneSpan Sign
With one signer and one signature field after the signer signs the iFrame goes white for a short period or time before going to a page that says the package is complete and giving a link to download it. Is there a way to not show this page.
Forum topic
OneSpan Sign
Hello,
I have searched to find answers to this but can't seem to find them.
Forum topic
OneSpan Sign
We implemented eSign application to get signature only during signing ceremony.When we create package we added static PDF and this static PDF contains all input information.User need to enter signature only(all other inputs are read only).Now we need to build another application that requires user
Forum topic
OneSpan Sign
Our integration has the browser embedded within our app, and with it we have a fairly stripped-down look in the header area of the signing session. We would like to finish our signing with these 2 extra things I can't figure out:
1. suppress the Download links.
Forum topic
OneSpan Sign
We need to remove the ability for users to download the signed PDF through the web interface, both via the emailed signature request and the browser based version (using host/access?sessionToken={mytoken}).
Forum topic
OneSpan Sign
Hi,
I am not getting email bounce notification for wrong email signer in request. This is my post to silanis, please let me know is there anything missing in request. I have checked the email bounce check box in call back events.
Forum topic
OneSpan Sign
Is is possible to add a new signer to a document which is already signed?
I tried with below code
PackageId packageId = new PackageId("orB4GBrQKn33YIF6XJFgDMGdkb4=");
ossClient.ChangePackageStatusToDraft(packageId);
Forum topic
OneSpan Sign
Hello,
Our team has started the integration with eSignLive REST API to create and send packages, sign the documents and get response payload from callback listener.
Forum topic
OneSpan Sign
Has anyone noticed problems with the handover URL and hash location strategy routing? If so, have you found a workaround?
When setting the handover url to something like "https://www.mydomain.com/#esign", we are seeing different behavior between the handover button and text link.