Integration reference
Settlement checkpoint model
Checkpoint types, owners, and progression rules between detection, policy confirmation, and treasury posting.
01
Checkpoint types
Checkpoints are explicit gates—not implicit hope.
| Checkpoint | Question answered | Typical owner |
|---|---|---|
| Detection | Did we observe a payment attempt? | Integration |
| Eligibility | Does amount/asset/reference match? | Operations |
| Policy confirmation | Does merchant policy allow Confirmed? | Operations/finance |
| Finance reconciliation | Do books-ready rules pass? | Finance |
| Treasury posting | May funds be recognized/released? | Treasury |
- Retries are normal. Webhook delivery is at-least-once. Design consumers to tolerate duplicates and out-of-order arrivals where possible.
- Asynchronous by design. Payers, chains, and your servers operate on different clocks. UI and finance should not assume synchronous finality.
- Eventual consistency. API reads, webhooks, and portal views may briefly diverge during transitions. Reconciliation jobs exist to converge truth.
Walkthroughs: /operations