Architecture section
Provider Adapter Architecture
Keep product APIs stable while Sardine-like fraud, Sumsub-like identity, Rain-like card issuing, Fireblocks-like custody, Noah/Tazapay/Infinia-style fiat rails, local banks, and country integrators evolve behind adapter contracts.
4 adapter flows
Contracts stay internal
Webhooks become events
Interactive flow lab
Translate provider complexity into stable product behavior
Switch between command adapters, inbound webhooks, mapping/versioning, and health/failover. Fiat rail detail lives in the Fiat Rails section.
Endpoint map
Find the adapter control
Filter adapters, commands, webhooks, mappings, credentials, health, and replay endpoints.
Concept notes
The adapter ideas worth remembering
Questions
Check your understanding
Pick an answer and the page will explain the reasoning.
Reference snapshot