Your product already has users. The first time one of them signs inside your app, IgniSign needs a signer: a record with a name, an email and whatever else the signer profile asks for. The second time the same user signs, you face a small decision that shapes your integration: do you point the new signature request at the signer you already have, or describe the person again on the new request?
When you add a signature step inside your product, the first technical choice is not the UI mode. It is what you put in the signature request. Your app may already hold a PDF contract, an office file, a JSON or XML record, or a document you prefer not to upload. IgniSign accepts those shapes. The integrating developer’s decision is which payload matches the object your product already owns — and what proof you expect back.
You create an IgniSign application once, then you get three environments: development, staging and production, each with its own API keys. The integrating developer’s decision is which of those environments you use for which work, and what that choice costs when a signature request runs. The answer is not “everything is free until production.” It depends on the environment and on what the request does.
You have embedded signing in your product: the signer opens a page in your app, the IgniSign iframe loads inside it, and they sign without leaving. Then two things happen almost at once. The iframe tells your page that the signer is done, and IgniSign sends a webhook to your backend. Both say "signed". The decision for the integrating developer is which of the two signals your product acts on, and for what.
Your product has a new flow: a user signs a mandate inside your app, and the moment the signature is done your backend activates the account, releases the file or moves the deal forward. That moment arrives as a webhook. The decision every integrating developer faces is simple to state: does your handler act on any call that reaches the endpoint, or does it first confirm that the call really came from IgniSign?
Many product flows ask a signer for more than one document at once: an onboarding contract with its data-processing annex, a mandate with a consent form, a set of terms that changed together. With the IgniSign API you can put them all in one signature request. The decision left to the integrating developer is how the signer gets through them: one document at a time, which is now the default for requests with several documents, or every document with a single swipe. This post is about that choice and what it changes in your backend.
When a signature request completes, your product has a new thing to look after: the proof. One day an auditor, a customer or your own support team will ask for it, often months after the signer finished. So the integrating developer has to decide early how the backend treats that proof: copy it into your own storage as soon as the signature is done, or keep a reference and fetch it from IgniSign when someone asks. This post is about that choice.
When a new flow in your product needs a signature (an onboarding contract, a mandate, a consent), the first technical decision is not the signature level or the document format. It is where the signer will be when they sign. For documents, IgniSign gives you two answers: embedded, where the signing interface runs in an iframe inside your page, and BySide, where the signer opens an IgniSign-hosted signing page from a link. Both start from the same signature request. This post is about picking one.
Digital signatures have become an essential part of modern business operations, but traditional e-signature solutions often come with limitations that can slow down processes and compromise document integrity. At IgniSign, we've developed an innovative approach to digital signatures that addresses these challenges while enhancing security, efficiency, and privacy.
Traditional digital signature solutions require signers to decide where to place signatures and initials within documents. This can be time-consuming and sometimes leads to formatting issues. Our solution? IgniSign creates a cryptographic binder on each page and adds a dedicated signature page, eliminating the need to manually position signatures within the document.
One of the most significant advantages of our approach is that it keeps your original documents untouched. Instead of embedding signatures directly into the document, IgniSign creates a separate representation of the signature with a cryptographic binder. This means your original document remains pristine while maintaining a secure, verifiable proof of signature.
When multiple parties need to sign a document, traditional solutions often require careful sequencing of signatures. IgniSign's approach eliminates this complexity. With our cryptographic binder system, multiple parties can sign efficiently without worrying about the order or placement of their signatures.
Privacy is a crucial concern in today's digital world. Our innovative binding system makes it possible to share only specific parts of signed documents while maintaining proof of signature. The cryptographic binder visible on each page ensures the authenticity of the shared portion, giving you more control over sensitive information while maintaining the validity of the signature.
The key to our system is the cryptographic binder that appears on each page. This not only serves as a visible marker of authenticity but also creates an unbreakable link between the signature and the document content. It's a sophisticated yet user-friendly approach that combines security with practicality.
IgniSign's innovative approach to digital signatures represents a significant step forward in document signing technology. By eliminating manual signature placement, preserving original documents, simplifying multi-party signing, and enabling selective sharing, we're making digital signatures more efficient and secure than ever before.
In the digital age, where every transaction, agreement, and contract can be executed electronically, maintaining control and integrity over your signature process is paramount. Ignisign offers a comprehensive suite of features designed to empower organizations to manage their electronic signature processes with precision, security, and flexibility.