Implemented controls · external commissioning pending
Stablecoin payments prelaunch specification
Stablecoin payments: fail-closed production controls
Payment intents are restricted to one configured chain and stablecoin, with bounded quotes, confirmation, idempotency, finality, and recovery controls. No production payment is claimed.
- Before confirmation: verify token contract, decimals, recipient checksum, amount, quote expiry, network, fees, and irreversibility.
- During settlement: require simulation, authenticated delivery, replay protection, bounded limits, and explicit pending/finalized/failed/expired/refunded states.
- After settlement: reconcile finality, replacements, reorgs, refunds, and manual recovery without server-held private keys.
Non-wallet path: Invoice, card, and manual recovery remain available. Mobile users may choose a wallet deep link only after the same confirmation details are displayed.
Status: Implemented in code; production verification, custody, audit, compliance, and independent commissioning remain pending.
Error and recovery: If a wallet, credential, or network step fails, focus returns here with a plain-language error and the non-wallet fallback remains available. This page never auto-connects a wallet; mobile users may choose a wallet-app deep link only after reviewing the same consequences and recovery path.
Evidence, freshness, and corrections
- Written and edited by
- Rachel Julian, founder and editor
- Last reviewed
- 2026-08-13
- Readiness rule
- Scaffold means designed, not implemented. Beta means implemented with production verification pending. Live means independently verified end to end. Source code, ABI files, endpoints, or configuration never prove production availability.
- Correction path
- Report a correction or compare the capability changelog.
Source hierarchy
- Primary standards: Protocol specifications and standards bodies define what an implementation must do.
- Security guidance: Threat-model and identity guidance define controls, failure handling, and recovery expectations.
- Deployment evidence: Independent end-to-end checks establish whether a configured production capability is live.
- Editorial judgment: I apply those sources to revenue-travel decisions and state where the evidence stops.