Adding Crypto Acceptance to an Online Store: Checklist

Settings

The definitions here match usage at a regulated crypto payment provider with fiat settlement and may differ elsewhere.

• Underpayment tolerance: one percent or a small fixed amount, whichever is greater
• Payment window: matched to the network, twenty to thirty minutes for slow ones
• Confirmation thresholds tiered by amount, not flat
• Network specified in the payment request, not left to the customer’s wallet
• Notifications enabled on settlement address changes, to multiple named people

Policies to decide before launch

Policy	Options	Recommended
Refund basis	Original crypto amount, original fiat value at current rate, or bank transfer	Original fiat value, published in terms
Refund destination	Origin address, or customer-supplied	Origin only; exceptions require verification and a second approver
Payment after expiry	Credit at new rate, honour old rate, or refund	Decide and document
Overpayment	Refund excess to origin, or credit	Credit, above a small threshold
Minimum refund	Below which network fee is disproportionate	Set one; state it in terms

Screening to keep switched on

Address verification against the shipping destination. Velocity checks. Device signals. Manual review above a threshold.

Crypto acceptance removes payment reversal risk. It removes none of the fulfilment risk, and merchants who relax screening substitute one loss for another. Fund administration adds its own vocabulary, which crypto rails built for fintech companies documents.

Order patterns warranting review

• Delivery address inconsistent with every other buyer signal
• Order value far above your average from a new account
• Multiple orders in quick succession to different addresses
• Expedited shipping with no price sensitivity
• Freight forwarder or mailbox service as the delivery address
• Any request to change the delivery address after payment

Engineering

Definitions matter less than arrangements. The balance you hold belongs at a support channel with a named contact rather than wherever the terminology sounded most reassuring.

• Verify callback signatures
• Make the handler idempotent on the payment identifier
• Build a reconciliation job running at least hourly
• Log raw payloads before processing
• Handle unknown event types without failing

Customer-facing copy

State what the wait is for and roughly how long.

Measured, this affects completion more than any technical change.