Embedded Signing vs Redirect Signing in BoldSign

BoldSign supports Embedded Signing, where you generate a secure signing link via API and launch the signing experience from your application. Embedded signing can be delivered in two common ways:

• In-App Embedded Signing (signing UI shown inside your app)
• Redirect-Based Embedded Signing (signing UI opened externally, then redirected back)

Both methods use the same embedded signing capability—the difference is where the signing page is rendered and how users navigate to it. Embedded signing can be launched in an iFrame, popup, or new tab depending on your app experience. Integrate embedded signing into your application

Important note about email invitations

• Embedded signing does not automatically mean “no emails.”
• If you want recipients to sign only through your embedded flow (and not receive BoldSign email notifications), disable emails while sending the document by setting DisableEmails = true. Disable Emails Notification

What Is In-App Embedded Signing?

In-App Embedded Signing allows signers to complete the signing process inside your application UI, typically using an iframe, modal, or WebView.

Purpose
Enable signers to finish signing without leaving your app.

User Experience

• User clicks Sign inside your application.
• The embedded signing page opens inside the app (iframe/modal/WebView).
• User completes signing.
• Your application continues the workflow immediately.

Impact / Implementation Notes

• Provides a seamless experience with your branding and navigation.
• Requires UI embedding logic and event handling within your application.
• Your application controls authentication and access flow.

Best For

• SaaS platforms with authenticated users
• Internal portals (HR, procurement, operations)
• Guided workflows where signing is a core step
• Scenarios requiring consistent branding and full UI control

What Is Redirect-Based Embedded Signing?

Redirect-Based Embedded Signing opens the embedded signing link outside your app, such as in a browser tab, external page, or redirect flow. After signing, the signer can be redirected back using a configured redirect URL.

Purpose
Enable signers to complete signing through an external navigation flow using the embedded signing link.

User Experience

• User starts signing from your application (or a public portal).
• Your application redirects the signer to the embedded signing link.
• User completes signing on the BoldSign-managed embedded signing page.
• User is redirected back to your application (if a redirect URL is configured).

Impact / Implementation Notes

• Easier to implement than in-app embedding.
• Signer temporarily leaves your application during signing.
• Best suited for lightweight integrations or external users.

Best For

• Quick integrations or simpler app flows
• External signers (customers, partners)
• One-time or ad-hoc signing
• Mobile and cross-platform flows
• Demos and proof-of-concept implementations

Summary Table: Key Differences

Which Option Should You Choose?

Choose In-App Embedded Signing if:

• Your users are already authenticated in your app
• You want a seamless “never leave the app” workflow
• Branding and UI continuity are important
• Signing is part of a multi-step guided process (ex: onboarding, approvals)

Choose Redirect-Based Embedded Signing if:

• You want the fastest implementation with minimal UI work
• Signers are external users (customers/partners)
• You’re fine with opening signing in a browser tab or external page
• You need an easy cross-platform flow (especially mobile)

Important Notes

• Both approaches use the same embedded signing mechanism provided by BoldSign.
• Embedded signing does not automatically suppress email invitations; email notifications must be explicitly controlled through the API request configuration.
• The only difference between the two approaches is how the embedded signing page is opened—either within your application UI or via a redirect to an external page.
• Embedded signing links are generated per signer and are secure, unique, and time-limited.