Testing a Gateway Before You Switch Traffic

Why one successful sale proves little

A single successful authorisation confirms that credentials work. It says nothing about whether you can refund, whether your CRM hears about the payment, or what a customer sees when a card is declined.

Those are the paths that generate support tickets and disputes in week one. Test them deliberately.

The go-live checklist

Run each of these as a real low-value transaction where the provider permits it.

• Authorisation and capture, including delayed capture if you use it
• Full refund, partial refund and void on an uncaptured authorisation
• A deliberately declined card, checking the message shown to the customer
• An expired-card and an incorrect-security-code attempt
• Recurring setup: initial charge, stored credential, and the first renewal
• 3-D Secure or equivalent authentication, both challenged and frictionless
• Webhook delivery into your CRM, fulfilment system and reporting
• Settlement reporting, reconciled against the orders you created

Check the descriptor on a statement

Descriptors are truncated, reformatted and sometimes prefixed in ways the configuration screen does not reveal. The only reliable test is a real transaction on a real card, then looking at the statement or banking app.

Getting this right before launch prevents a category of dispute that is entirely avoidable.

Keep card data out of your systems

Use hosted fields or the gateway’s tokenisation layer wherever possible. Card data that never touches your servers reduces both breach risk and compliance scope.

Be sceptical of any integration pattern that routes raw card numbers through your own application without a clear reason. And no legitimate provider will ask you to email card numbers, full bank credentials or passwords.

Plan the cutover

Switch during a low-traffic window. Keep the previous route available if the provider allows it. Watch authorisation rates, decline reasons and webhook delivery for the first day rather than the first hour.

For subscriptions, confirm the first renewal cycle end to end before assuming the migration succeeded — the failure usually surfaces a month after launch, not on day one.