Embedded vs BySide Integration

Understand the two main approaches for integrating the IgniSign signature interface and choose the right one for your application

Integration Approaches Overview

IgniSign offers two distinct approaches for integrating the electronic signature process into your applications. Each approach has its own advantages and use cases, making them suitable for different scenarios.

Detailed Comparison

Understanding the differences between Embedded and BySide integration is crucial for selecting the approach that best fits your application's needs.

Factor	Embedded Signature	BySide Signature
User Experience	✅ Seamless, within your app	➖ Requires redirect
Implementation Effort	➖ More complex	✅ Very simple
Security Responsibility	➖ More considerations	✅ Fully handled by IgniSign
Customization	✅ More options	➖ Limited
Cross-Platform	✅ Web, iOS, and Android	✅ All platforms

Embedded Signature Deep Dive

The Embedded signature approach integrates the IgniSign interface directly within your application, providing a seamless experience for your users.

How It Works

In the Embedded approach:

1. Your application backend (or API integration) creates a signature request through the IgniSign API
2. Your application UI embeds the IgniSign interface through an iframe (web) or WebView (mobile)
3. The signer interacts with the signature interface directly within your application
4. The IgniSign interface communicates with your application via events/callbacks
5. Your application can respond to these events to provide a customized experience

Key Benefits

• Seamless User Experience: Users remain within your application throughout the signature process
• Brand Consistency: Maintain your application's look and feel around the signature interface
• Real-time Feedback: Receive events from the signature interface to update your UI in real-time
• Custom Integration: Integrate the signature flow exactly where it makes sense in your application
• Control Over UX: Manage how users are guided through the signature process within your application flow

Implementation Considerations

• Security: You must verify the origin of messages from the iframe/WebView
• Responsive Design: Ensure the embedded interface works properly on all device sizes
• Event Handling: Implement proper event listeners for communication with the interface
• Error Handling: Handle error scenarios gracefully within your application
• Authentication Requirements: The signerAuthSecret parameter is mandatory for all embedded integrations (Web, iOS, Android)

Authentication in Embedded Integration

When using the embedded integration approach, special consideration must be given to authentication security. Unlike the BySide approach where IgniSign handles the entire authentication flow (typically including email verification), in embedded integrations, your application is responsible for managing part of the authentication security.

The signerAuthSecret is a critical security element that serves as an additional authentication factor. This secret is generated when you create a signer through the IgniSign API (returned in the IgnisignSigner_CreationResponseDto) and must be provided each time you initialize a signature session for that signer.

This authentication model ensures that:

1. The signature request is legitimate (verified by the signatureSessionToken)
2. The signer identity is properly managed by your application (verified by the signerAuthSecret)

Without this additional factor, embedded integrations would be significantly less secure since they bypass some of the standard authentication mechanisms that are present in the BySide flow.

Ideal Use Cases

The Embedded approach is ideal for:

1. Business Applications with Complex Workflows

   • When signature is just one step in a larger business process
   • When you need to maintain context and state throughout the signature process
   • Example: HR onboarding platforms where signing employment contracts is part of a multi-step process

2. Customer-Facing Applications with Brand Importance

   • When maintaining consistent branding throughout the user journey is critical
   • Example: Banking applications where customers sign loan agreements

3. Mobile Applications

   • When developing native mobile apps with a seamless UX
   • Example: Insurance apps where users submit claims and sign documents

4. Applications with High Transaction Volume

   • When users frequently sign documents and a seamless experience is important
   • Example: Real estate platforms where agents regularly send documents for signature

BySide Signature Deep Dive

The BySide approach uses the IgniSign-hosted signing interface, where signers receive the signature URL via email and complete the process entirely on the IgniSign platform.

How It Works

In the BySide approach:

1. Your application backend (or API integration) creates a signature request through the IgniSign API
2. IgniSign sends an email to the signer with a URL to access the signature interface
3. The signer clicks the link in the email and is taken to the IgniSign platform
4. The signer completes the signature process entirely on the IgniSign platform
5. Upon completion, the signer can be redirected back to your application (if configured)
6. Your application backend receives webhooks about the signature status

Key Benefits

• Simple Implementation: Minimal development effort required
• Security: The entire signature process is managed by IgniSign
• Maintenance: No need to update your application when IgniSign updates the signature interface
• Compliance: IgniSign manages all legal and regulatory aspects of the signature process
• Fast Integration: Get up and running with electronic signatures in minutes

Implementation Considerations

• Return URL Handling: Implement proper handling of the return URL and status parameters
• User Flow: Design a clear user flow with appropriate messaging before and after the redirect
• Mobile Considerations: Ensure the redirect flow works properly on mobile devices
• Session Management: Maintain user session context through the redirect flow

Ideal Use Cases

The BySide approach is ideal for:

1. Simple Document Signing Requirements

   • When you only need basic signature functionality
   • When the signature process is isolated from other workflows
   • Example: Simple document signing portals where signing is the primary function

2. Quick Implementation Needs

   • When you need to integrate electronic signatures quickly with minimal development resources
   • Example: Small businesses or startups with limited development resources

3. Low-Volume Signature Applications

   • When signature is an occasional need in your application
   • Example: Membership applications where signing happens only during initial registration

4. Applications with Strict Security Requirements

   • When you prefer to delegate all security aspects of the signature process
   • Example: Financial institutions with strict security and compliance requirements

Making the Right Choice

When deciding between Embedded and BySide integration, consider the following factors:

Choose Embedded If:

• User experience is a top priority
• Signature is a frequent action in your application
• You want tight integration with your application workflows
• You have resources to implement and maintain a more complex integration
• Maintaining brand consistency throughout the user journey is important

Choose BySide If:

• Implementation speed is a priority
• You have limited development resources
• Security and compliance are primary concerns
• Signature is an occasional action in your application
• You prefer to delegate the signature experience to IgniSign

Next Steps

Now that you understand the differences between Embedded and BySide integration, you can explore the specific implementation guides for your platform:

• Web Integration
• Android Integration
• iOS Integration