Interactive field guide
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, ledger, and risk ideas in every section.
Built by Achala Arunalu
I build practical stablecoin products across 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.
The custody provider is the 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.
Deposits, withdrawals to external wallets, internal transfers, allowlisting, Travel Rule.
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.
Local money Fiat & Local RailsLocal rail providers, local banks, PIX, SPEI, ACH, SEPA.
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 a customer adds stablecoin on-chain, withdraws to an external wallet, and sends to another customer, with the controls that keep pay-ins and payouts safe.
Learn how product events flow into a fraud engine, how decisions come back, and where a fraud and risk provider fits for fraud, AML, device, and case signals.
Learn how applicants are created, how verification is handed off to a KYC provider, and how review results gate stablecoin cards.
Learn how KYC-approved cardholders are provisioned, how a card issuing provider 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.
Follow value from a customer deposit through risk, custody, ledger, settlement, card spend, clearing, reconciliation, disputes, and finance reporting.
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.
Follow the system beneath the wallet and card APIs: provider 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.