13 posts tagged with "developers"

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.