Settlement
Your payout address is correct and you control it
Your payout address is correct and you control it
Check it character by character in Settings → Payout, and confirm on-chain at /verify.If it’s an exchange deposit address, stop. Exchange addresses can be rotated or retired without warning, and a payment sent to a dead deposit address is gone. Use a wallet you hold the keys to.
You've claimed successfully at least once
You've claimed successfully at least once
Do a full round trip on testnet: take a payment, claim it, see it arrive. Claiming is a transaction you sign, so make sure you can — including having native gas on that chain.
You have native gas on every chain you enabled
You have native gas on every chain you enabled
Claiming costs a network fee in the chain’s native currency — ETH, POL, BNB, AVAX, TRX. A chain you can’t claim on is a chain where your money sits until you top up.
Integration
Fulfilment runs from webhooks, not browser callbacks
Fulfilment runs from webhooks, not browser callbacks
onPaymentConfirmed fires in the customer’s browser. If they close the tab, it never fires — but the payment still completed.Treat browser callbacks as UI only. Ship goods from the webhook.Your webhook verifies signatures and returns 2xx fast
Your webhook verifies signatures and returns 2xx fast
Reject anything that fails verification. Acknowledge quickly and do slow work in a background job — we time out after 10 seconds and retry.
Webhook handling is idempotent
Webhook handling is idempotent
Retries mean you will occasionally see the same event twice. Key on
X-Webhook-Id and make redelivery a no-op. Charging or shipping twice is the failure mode here.The embed still has integrity and settlementAnchor
The embed still has integrity and settlementAnchor
Easy to drop while refactoring a template. Both exist to protect you. Why.
Your CSP allows the checkout
Your CSP allows the checkout
If you set a Content Security Policy,
https://www.cryptocheckout.ai needs to be permitted in script-src and frame-src.Operations
You have a refund process
You have a refund process
There is no refund button, because we never hold your money. Refunds are sent by you, from your wallet, to an address the customer supplies at refund time.Decide now who does it and how you collect the address. Refunds.
You know what to do with an underpayment
You know what to do with an underpayment
A customer who sends less than quoted lands in
underpaid. Decide whether you ask them to top up, refund, or fulfil anyway on a small shortfall. Edge cases.Someone scans for unmatched arrivals
Someone scans for unmatched arrivals
Rare, but real: wrong token, wrong chain, an arrival long after expiry. These show in Payments without a matching order and need a human. There is no dedicated view for them yet, so put a weekly scan in someone’s routine.
Your confirmation thresholds suit your risk
Your confirmation thresholds suit your risk
Defaults scale with value. If you sell instantly-consumable digital goods, consider raising them. Finality.
Commercial
Your pricing accounts for 1%
Your pricing accounts for 1%
Flat, all-in, every chain. Ask about custom rates before you deploy if you expect volume. Fees.
Your terms mention payment finality
Your terms mention payment finality
Customers should know before paying that crypto payments are irreversible and refunds are handled by you directly.
You've picked which chains to enable
You've picked which chains to enable
More chains means more customer choice and more native-gas balances to maintain. Starting with two or three cheap chains is a reasonable opening position. Chains and tokens.
Rehearse these three
Worth doing deliberately on testnet rather than discovering in production.Customer closes the tab
Pay, then close immediately. Confirm your webhook still fulfils the order.
Duplicate webhook
Replay a delivery. Confirm you don’t ship twice.
Underpayment
Send slightly less than quoted. Watch where it lands and confirm you have a response.