Card operations section

Card Auth, Clearing & Reconciliation

Follow the card transaction after provisioning: authorize in real time, reserve stablecoin value, process reversals and clearing, settle with the issuer/provider, and reconcile every ledger and provider record.

4 operational flows Auth is a hold, not final spend Recon creates financial truth

Interactive flow lab

Track the transaction from swipe to reconciliation

Switch between authorization, clearing, settlement, and reconciliation workflows.

High-level sequence

Authorization → clearing → settlement → reconciliation

The four card truths, kept as separate postings against one ledger — never overwritten.

Card issuer Cards API Ledger · Treasury Reconciliation Ops

1

Card issuer→Cards APIauthorization

Authorization request at the point of sale.
2

Cards API→Ledger · Treasuryrequest

Place an authorization hold.
3

Ledger · Treasury⇢Cards APIresponse

Hold placed — approve or decline.
4

Cards API⇢Card issuerdecision

Decision inside the network window.
5

Card issuer→Cards APIevent

Clearing file with final amounts (later).
6

Cards API→Ledger · Treasuryrequest

Post clearing — convert the hold to a settled entry.
7

Ledger · Treasury→Reconciliationrequest

Three-way match: issuer vs ledger vs customer.
8

Reconciliation→Opsevent

Raise a break when the numbers disagree.

Endpoint map

Find the operational call

Filter authorization, clearing, settlement, reconciliation, exception, and provider endpoints.

Concept notes

The operational ideas worth remembering

Questions

Check your understanding

Pick an answer and the page will explain the reasoning.