Fiat rails section
Fiat & Local Rails
Separate fiat and local payment rails from crypto custody: route local collections and payouts through local rail providers, partner banks, and country rails such as PIX, SPEI, ACH, SEPA, and Faster Payments.
Interactive flow lab
Route local money without muddying the ledger
Switch between rail selection, local collection, fiat payout, and reconciliation.
High-level sequence
Fiat deposit and payout through a bank partner
Screened, ledgered, and reconciled — with returns handled safely.
-
1
Customer→Fiat rails servicerequest
Request a payout to a local bank account.
-
2
Fiat rails service→Risk · AMLrequest
Screen the beneficiary and amount.
-
3
Risk · AML⇢Fiat rails serviceresponse
Clear — or hold for review.
-
4
Fiat rails service→Ledger · Treasuryrequest
Debit the balance and reserve the payout.
-
5
Fiat rails service→Bank partneroff-platform
Submit the payout instruction (ACH / SEPA / local).
-
6
Bank partner→Fiat rails serviceevent
Accepted — later settled or returned.
-
7
Fiat rails service→Ledger · Treasuryrequest
Post settlement — or reverse on a return.
-
8
Fiat rails service→Customerevent
Payout status updates.
Endpoint map
Find the fiat rail boundary
Filter capability, routing, collection, payout, provider webhook, reconciliation, and event endpoints.
Concept notes
The fiat rails ideas worth remembering
Questions
Check your understanding
Pick an answer and the page will explain the reasoning.
Reference snapshot