A practical sandbox-to-live checklist for crypto merchants

Moving from sandbox to live crypto acceptance is less about flipping a boolean and more about proving your operational runbook.

Separate keys and endpoints. Issue sandbox and live API keys with distinct prefixes. Webhook URLs should differ so test events never touch production fulfillment code.

Reconcile a full synthetic order. Create an invoice, pay it in sandbox, confirm webhook delivery, and mark the order complete in your store. Capture screenshots or logs for finance and support teams.

Document confirmation thresholds. Each asset on mzapayments carries a default confirmation count. Align your “ship order” automation with those thresholds rather than with mempool visibility alone.

Plan for underpayment and expiry. Decide how your catalog handles partial sends and timed-out quotes. Customer support scripts should reference payment ids and invoice ids from dashboard exports.

Review access control. Limit who can create API keys, rotate webhook secrets, and request payouts. Audit logs in the dashboard help trace configuration changes.

Live activation may depend on business verification and payout configuration—contact support if your account is not yet eligible. Until then, sandbox remains the authoritative place to harden integrations.