Crypto Payments API
Learn how merchants lock a price, create a payment intent, wait for chain confirmations, settle funds, and issue refunds as new transfers.
- Quote expiry and consumed quotes
- Payment intent lifecycle
- Signed webhooks and retry safety
Interactive API walkthrough
Use this guide as a product map, not a pile of API pages. Start with the recommended path, use the master map when you need the whole system, and use the canonical topic map to avoid repeating the same KYC, KYT, provider, ledger, and webhook ideas in every section.
Built by Achala Arunalu
I build practical product architecture across stablecoin banking, card issuing, crypto payments, fiat rails, fraud and AML, treasury settlement, reconciliation, and internal operations tooling.
Guided path finder
Pick a product persona and the problems you need to solve. The site will trim the tutorial library to the most useful path so you are not forced through every section.
1. Choose your lens
2. Add current needs
Master platform map
Each product has its own lifecycle, but all money-impacting paths meet at the same control points: risk and identity decisions, provider adapters, custody infrastructure, and the internal customer ledger.
Fireblocks or BitGo is the custody infrastructure that observes and moves on-chain assets. The internal customer ledger is the balance source of truth: deposits credit it, card authorizations reserve it, clearing posts debits, refunds and payouts reduce it, fiat rails move local money, and reconciliation proves it.
Canonical topic map
If a section only touches a topic, link to the owner below instead of restating it. This keeps the tutorial focused and makes future changes easier.
Quote, intent, deposit detection, merchant settlement, refund initiation.
Fraud, AML, KYT Fraud & AMLRisk decisions, wallet exposure, sanctions, transaction monitoring, cases.
Identity proof KYC / KYBApplicants, provider review, eligibility, resubmission, ongoing monitoring.
Card issuing Stablecoin CardsCardholders, card provisioning, controls, first authorization decision.
Card transaction ops Card OpsAuthorization holds, clearing, settlement, auto-recon, manual recon.
Exceptions Ops ControlsDisputes, freezes, holds, releases, evidence, customer-safe status.
External providers Provider AdaptersSardine, Sumsub, Rain, Fireblocks, BitGo, bank rails behind contracts.
Local money Fiat & Local RailsNoah, Tazapay, Infinia-style providers, local banks, PIX, SPEI, ACH, SEPA.
Security API SecurityScopes, idempotency, signatures, approvals, audit, key rotation.
Async contracts Event CatalogEvent types, schemas, delivery, retries, replay, ownership.
Object truth Data ModelCustomerLedgerAccount, custody wallets, ledger entries, lineage, recon links.
Money execution TreasuryCustody, ledger posting, minting, burning, staking policy, FX, payout rails.
Operating model PlaybooksCase triage, incidents, escalation, glossary, metrics, postmortems.
Tutorial library
Open a section when you need the detail. Each page now declares what it owns and links out for related topics.
Showing the recommended path for Stablecoin banking PM.
Learn how merchants lock a price, create a payment intent, wait for chain confirmations, settle funds, and issue refunds as new transfers.
Learn how product events flow into a fraud engine, how decisions come back, and where a Sardine-like provider fits for fraud, AML, device, and case signals.
Learn how applicants are created, how verification is handed off to a Sumsub-style provider, and how review results gate stablecoin cards.
Learn how KYC-approved cardholders are provisioned, how Rain-style card issuing connects behind an adapter, and how a real-time card authorization is approved or declined.
Learn the operational lifecycle after a card exists: real-time authorization, reversals, clearing, issuer settlement, auto-recon, and manual reconciliation.
Learn how refunds, card disputes, chargebacks, freezes, AML holds, evidence packs, and operational SLAs work across crypto and card products.
Learn how to simulate crypto payments, card authorizations, provider webhooks, retries, failures, idempotency, and go-live readiness.
Follow value from checkout through risk, custody, ledger, settlement, card spend, clearing, reconciliation, disputes, and finance reporting.
Learn how Sardine, Sumsub, Rain, Fireblocks, BitGo, fiat rail providers, banks, and country integrators sit behind stable contracts and mappers.
Learn how local fiat collections and payouts route through country rails like PIX, SPEI, ACH, SEPA, and Faster Payments without mixing rail state with customer ledger truth.
Give support, risk, finance, product, and engineering a shared operating language for incidents, cases, SLAs, glossary terms, and escalations.
Learn API keys, service tokens, scopes, idempotency, webhook signatures, audit logs, key rotation, and privileged operations control.
Build the canonical event list for payment, risk, identity, card, ledger, provider, ops, and finance updates.
See how merchants, applicants, cardholders, wallets, custody accounts, customer ledger accounts, transactions, and cases relate.
Follow the system beneath the merchant API: Fireblocks custody, USDC ledgering, mint and burn lifecycle, optional staking policy, locked FX quotes, and dual payout rails.
Mental model
Use this table when deciding where a concept belongs. The first column is the owner; other pages should link back instead of repeating the same explanation.