Prepare your integration for launch
Turn sandbox evidence into a controlled production rollout with clear owners and recovery steps.
Start with an evidence record
Use this checklist as a release review, not an automatic certification. Record the date, environment, merchant, build version, test scenario and redacted outcome for every required flow. Keep private keys, payment tokens and full payment details out of screenshots, tickets and logs. A checklist item is complete only when the relevant evidence exists. Run sandbox tests First token payment recipe
Account and environment readiness
Confirm the intended commercial and technical configuration with Betterpay before production traffic. Sandbox access alone does not establish live merchant approval or feature availability. Confirm merchant approval, processor, currency and required payment methods. Record who owns onboarding, operational support and payment exceptions. Configure the correct production host and matching public/private keys through your deployment secret process. Verify that sandbox and production records cannot be mixed in the order ledger. For Apple Pay, verify the deployed domain file and allowed-domain configuration. Keys and environments Merchant onboarding Wallet configuration
Payment and recovery checks
Run the cases that match your product. Keep explicit records of scenarios that cannot be exercised in the current test environment. Area Required evidence Happy path Approved token sale, stored gateway ID and correct order confirmation Decline and validation Unpaid order and understandable customer feedback Double submission One application attempt owns submission; repeated clicks do not create competing sales Uncertain response Order stays pending until reconciled; no blind resubmission Operations Correct capture, void or refund behavior for applicable transaction state Reporting Gateway records reconcile with your application ledger Webhooks Signature validation, duplicate handling and retry recovery Recurring Plan/subscription lifecycle tested; scheduled billing limitation explicitly recorded Sandbox recurring plans and subscriptions do not submit scheduled transactions. Record this limitation instead of marking scheduled billing verified. Errors and uncertain outcomes Verify gateway webhooks Reconciliation Recurring billing
Application and access review
Review your own application boundaries as well as the provider integration. Hosted fields reduce exposure to payment details but do not settle every security or compliance responsibility. Confirm that order amount and merchant selection come from trusted server-side records. Authorize saved-method use and privileged capture/refund operations. Inspect frontend bundles and browser requests for accidental private-secret exposure. Verify HTTPS, safe logs, retention and restricted operational access. Test keyboard navigation, small screens, readable errors and loading states. Security guide Server payment implementation
Release in a controlled sequence
Choose a small approved cohort, set an observation period and assign someone to reconcile payments and respond to exceptions. Your rollback changes routing for new attempts; it must not repeat an already submitted or uncertain charge. Review the evidence record and list any unresolved account-specific issues. Agree the production validation steps and who can authorize each operation. Deploy the approved configuration and confirm the intended merchant routing. Monitor results, events and reconciliation before expanding traffic. If a problem appears, stop new affected attempts and investigate existing ones before retrying. Operations guide Migration and rollback