OverviewAuthentication & environmentsStaging faucetCore conceptsReceive paymentsAuto-detect paymentsConfirm settlementWithdraw fundsContract interactionsReconcile balancesBusiness identitySettings & complianceCustomers & invoicesWithdrawals & treasuryContracts & automationReference data & billingWebhooks & eventsUse-case playbooksErrors & edge casesGo-live guideChangelog
Production
Go-live guide
Use this checklist before moving real customer value through the integration.
Checklist
- Webhook signature verification is implemented and tested in sandbox.
- Your backend stores `requestId`, invoice IDs, withdrawal IDs, and your own references for support correlation.
- You tested underpayment, overpayment, expiry, and retry handling with sandbox data.
- You quote before creating withdrawals, and you store requested amount, payout amount, and fees separately.
- Programmatic withdrawals use dedicated payout API keys with destination policy, spend caps, and alerting.
- Live credentials, webhook URLs, and API keys are stored outside the browser in a secret manager.
- Operators understand that sandbox activation is not the same as live approval.
Production cutover cautions
Re-run environment setup at cutover
Do not assume a sandbox-ready integration is production-ready. Swap API keys, webhook secrets, URLs, network IDs, and alerting before using live value.
Recommended support data
For every incident, capture your request payload, PayChainHQ request ID, invoice or withdrawal ID, webhook delivery ID, and your internal customer / payout reference.