The classic Docusign signing ceremony can be used standalone or within an iframe.

Standalone (no iframe) is recommended. In particular, some Docusign signing features, including IDV, are not available if an iframe is used.

Benefits of the classic signing ceremony:

• It shows the envelope sender’s information, including their name, photo, their company (account name) and company logo (if set for the sender's account)
• The sending account branding is used
• Many Docusign signer authentication features can be used

This demo uploads a template to your account, and then uses it for the envelope.

The signing ceremony can include supplemental documents with different levels of signer acceptance:

• No Interaction No recipient action is required.
• View The recipient is required to view the document.
• Accept The recipient is required to accept the document by selecting accept during signing, but is not required to view the document.
• View Accept The recipient is required to view and accept the document.
• Read Accept The recipient is required to view the entire document and then accept it.

Focused View provides a productive user interface for the signer. The signing ceremony fits within your website using unobtrusive framing.

Benefits of using Docusign.js:

• You can use the Signing Ceremony's default button UX, or set the text and background colors of the primary buttons
• The Docusign.js library creates the iframe for you
• The events raise a DOM event to your JS app; the redirection page is not used

This demo uploads a template to your account, and then uses it for the envelope.

The signing ceremony can use different document types including Responsive Smart Sections HTML documents. You can use the included documents, upload your own Smart Sections HTML document, or use a template from your account.

The signing ceremony can include supplemental documents with different levels of signer acceptance:

• No Interaction No recipient action is required.
• View The recipient is required to view the document.
• Accept The recipient is required to accept the document by selecting accept during signing, but is not required to view the document.
• View Accept The recipient is required to view and accept the document.
• Read Accept The recipient is required to view the entire document and then accept it.

Known Issues

• C2A-3558 SMS/Phone Authentication does not work with Docusign JS
• C2A-3499 Payment tabs don't work with Focused View

Docusign.js Default View uses the classic Docusign signing ceremony via the convenient Docusign.js library.

Benefits of this view:

• It shows the envelope sender’s information, including their name, photo, their company (account name) and company logo (if set for the sender's account)
• The sending account branding is used

Benefits of using Docusign.js with the classic view:

• You can use the Signing Ceremony's default button UX, or set the text and background colors of the primary buttons
• The Docusign.js library creates the iframe for you
• The events raise a DOM event to your JS app; the redirection page is not used

This demo uploads a template to your account, and then uses it for the envelope.

The signing ceremony can include supplemental documents with different levels of signer acceptance:

• No Interaction No recipient action is required.
• View The recipient is required to view the document.
• Accept The recipient is required to accept the document by selecting accept during signing, but is not required to view the document.
• View Accept The recipient is required to view and accept the document.
• Read Accept The recipient is required to view the entire document and then accept it.

Known Issues

• C2A-3558 SMS/Phone Authentication does not work with Docusign JS