Resources
Production checklist
Complete these checks before allowing customers to move real USDT or USDC through the direct wallet route.
Frontend
- The SDK and required stylesheet are pinned to a reviewed version.
- Only pairs returned by the current merchant catalog can be selected.
- RPC URLs exposed to the browser contain no private credentials.
- Wallet rejection and chain-switch cancellation are handled for every family.
Backend
- D0 credentials never reach browser code, logs or analytics.
- Session creation is authenticated and scoped to the merchant order.
- Token and receiving addresses come from server-owned configuration.
- Submitted hash registration requires an authenticated session.
Transaction verification
- The receipt status, chain ID and token contract are verified.
- The recipient and base-unit amount are verified from event logs.
- Finality waits for the required number of confirmations.
- Transaction hashes and credited orders are both idempotent.
Operations
- Alerts cover stuck submissions and failed chain reads.
- Support can search by order ID, session ID and transaction hash.
- A kill switch can hide Connect Wallet without disabling other Checkout methods.
- The integration has a tested reconciliation path for missed callbacks.
Launch only after a complete small-value production transaction has been confirmed and reconciled by both teams.