11 example fintech processes. Each is a governed graph: agents run the reversible steps, and the irreversible ones wait for the role that must sign. Import one and adapt it — your connectors, your signers, your time limits.
| Example | Steps | Gates | File |
|---|---|---|---|
| KYC/AML compliance AML transaction monitoring | 11 | 1 | JSON |
| Chargeback representment Chargeback representment | 13 | 4 | JSON |
| Complaints handling & redress Complaints handling | 8 | 1 | JSON |
| Document & liveness verification Identity document verification | 8 | 1 | JSON |
| DSAR & privacy-request fulfilment DSAR fulfilment | 8 | 1 | JSON |
| Failed-payment smart-dunning Failed payment recovery | 11 | 2 | JSON |
| Cash-flow underwriting Income and affordability verification | 9 | 2 | JSON |
| Payment exception repair & STP auto-repair Payment exception repair | 8 | 2 | JSON |
| Transaction-reporting exception remediation Transaction reporting exception remediation | 9 | 2 | JSON |
| Stipulation & condition-clearing Loan stipulation clearing | 8 | 1 | JSON |
| Tier-1 card & account servicing Card and account servicing | 7 | 1 | JSON |
Filing a SAR with FinCEN is irreversible and legally consequential, so a compliance officer signs the SAR/no-SAR decision before it fires; the same applies to blocking a sanctions hit.
Accepting a chargeback (writing off the disputed amount) or firing off representment evidence both foreclose options and can't be re-tried, so a disputes analyst signs off the accept/fight decision and the evidence package before it's submitted.
Rejecting a genuine customer (or approving a fraudulent identity) is consequential and can't always be cleanly undone, so borderline or failed identity cases route to a human adjudicator before the account is opened or denied.