2 posts tagged with "backend"

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.

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.