Skip to main content

4 posts tagged with "backend"

View All Tags

Resend or reconcile: recovering a signature webhook your endpoint missed

· 4 min read
IgniSign Team
IgniSign Team

Your product embeds a signature step, and your backend waits for IgniSign's webhook to move the flow forward. Then a deploy goes wrong, or a TLS certificate expires on your server, and the endpoint answers with errors for twenty minutes. Users kept signing during that window. The question for the integrating developer is simple: how does your backend catch up on the events it missed? There are two answers, and they do different jobs.

Signed PDF, proof page or audit log: what to store for the auditor

· 4 min read
Julien Jenoudet
CEO of IgniSign

An auditor, or a customer's compliance team, sends your product a question about a signature from last spring. Your backend can answer it, but only with what it fetched at the time. IgniSign produces several proof outputs for each signed document, and they do not answer the same question. So the integrating developer has a decision to make for each flow: which output does the backend fetch and keep? This post is about that choice, not about where you store it.

Completed or proof ready: which webhook your backend should wait for

· 4 min read
Julien Jenoudet
CEO of IgniSign

Your product has a new flow that ends with a signature: a mandate, an onboarding contract, a consent. Your backend listens to IgniSign webhooks, and a few weeks after launch an auditor asks for the signed file behind one of your records. That is when a small choice in your webhook handler starts to matter: which event did your code treat as "done"? The signature request completing and the proof being ready are two separate events, and they do two different jobs.

Copy or reference: where your product keeps the signature proof

· 4 min read
Julien Jenoudet
CEO of IgniSign

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.