Signer Experience

To download the full code sample see our Code Share site. Text within the Signer Experience can be using Markdown. Formatting is supported within the following area of the Signer Experience: Thank You Summary page Error pages Alerts ...

The Thank You Summary page appears after a signer has completed signing a transaction. This page can customized by using our Branding Migration Forms . Layout Customization The following elements of the Thank You Summary page can be cust...

Java SDK .NET SDK REST API APEX SDK Java SDK To download the full code sample see our Code Share site. After a transaction has been sent, you can create a Signer Experience for your signers. This can be done in one of the following...

Java SDK .NET SDK REST API APEX SDK Java SDK To download the full code sample see our Code Share site. The OneSpan Sign Signer Experience can be customized. By customizing the Signer Experience you can seamlessly integrate the si...

Java SDK .NET SDK REST API Java SDK A Handover URL is a redirect link pre-set in the transaction settings, which allows you to determine where the Signer Experience will be relocated after a recipient interacts with a transaction. The ...

Java SDK .NET SDK REST API APEX SDK Java SDK To download the full code sample see our Code Share site. When creating a signing session, extra data can be stored as part of the evidence summary. This is done by passing additional ses...

iFrames can be used to integrate the Signer Experience into a third-party application. The following sections describe some best practices for developers who are performing such an integration: Cross-Origin Resource Sharing Making an iFra...