All use-cases

PDF receipt generation

Turn a settled payout or sale into a verifiable PDF receipt — rendered from a branded template, hashed and written once to immutable store, then delivered — with an audit row on every step.

The whole flow, end to end

Mail = email sent Bell = in-app alert Amber diamond = automatic check Teal diamond = a person decides
Payout approved / sale settled receipt generation triggered Assemble receipt data line items · totals · tax · parties Render PDF — branded template server-side · your-brand header/footer Render OK? template + data valid yes Stamp + hash, immutable store SHA-256 · write-once bucket Deliver receipt email link + in-app + download Email delivered? bounce / spam check yes Receipt available + audited downloadable · on the immutable trail Render failed retry queue 3x ops alerted BLOCKED → RETRY no Bounce in-app + download fallback · flagged RECOVERED bounce

Settlement is the only trigger; nothing is re-keyed — the receipt is built from the source-of-truth record. The PDF is hashed and written once before anyone sees it, so the document on the trail is provably the document issued. A render failure retries with ops alerted; a bounced email falls back to in-app plus download and is flagged. Every step is immutably audited.

What receipt generation guarantees

  • Every receipt is tamper-evident — a SHA-256 hash is taken before delivery and the file lands in a write-once bucket, so it can never be silently re-issued.
  • Delivery is fail-loud: a render error retries three times with ops alerted; a bounced email falls back to in-app plus download and is flagged for follow-up.
  • Generation is fully audited — assemble, render, hash, store and deliver each write one immutable row, so the receipt is downloadable and traceable end to end.