What to check before launching a payment gateway
Confirm approval, documents, charges, settlement, refunds, and support. Ask your developer to test successful payments, failures, and duplicate messages.
- Written and edited by
- DokanNao Editorial Team
- Reading time
- 2 minutes
Key takeaways
- Confirm business eligibility and current commercial terms directly with the provider.
- Require signed server notifications, idempotency, verified status, and a tested failure path.
- Do not launch until settlement, refund, support, checking payment and order records, and production evidence are understood.
In this guide
Adding a payment plugin is one part of the job. Your business agreement, payment records, secure setup, and support process also need to be ready.
Check approval, documents, and charges
Begin with the business contract. Ask about eligibility, documents, onboarding, approval, payment methods, charges, taxes, settlement account and schedule, reserve or hold rules, refunds, disputes, limits, support, and termination.
Ask your developer to check the integration
Inspect the current provider API rather than copying old sample code. The server must confirm the payment securely with the provider, check the amount and currency, and match it to the right order. Repeated messages must not apply the payment twice. Check timeouts, keep credentials secret, and log the reason for failures without sensitive payment details.
Check failures and repeated payment messages
Plan for customer close, network timeout, duplicated callback, callback before browser return, browser return without callback, late success, mismatched amount, already-paid order, refund failure, and provider outage. Payment completion must be exactly once.
Test payment, settlement, and support
In sandbox, test success and every supported failure. In production, use an authorized low-risk transaction, confirm provider dashboard, your payment record, settlement, accounting, and refund path. Sandbox success does not prove production approval.
Check everything before going live
Release only when legal and commercial approval, production credentials, secure configuration, webhook verification, monitoring, support ownership, checking payment and order records, refund procedure, and rollback are ready. Pair this with the payment-options guide and launch checklist.