Map the payment and order states
Write down what pending, paid, failed, cancelled and refunded mean in your store. Clarify when stock is reserved and when the fulfilment team may act. A successful redirect back to the website is not enough to establish payment. Order status should be based on the gateway’s documented verification process and your agreed operational rules.
Use the provider’s test tools
Follow the gateway’s current sandbox instructions for success, failure and other supported scenarios. Check what the customer sees when a payment is declined or they close the payment window. Preserve a recoverable cart where appropriate. Never put real card details into an improvised test form or treat a sandbox success as proof of live merchant readiness.
Consider repeated or delayed notifications
Payment notifications may arrive later than the browser return or be delivered more than once. The integration should verify authenticity and avoid creating duplicate orders or repeating fulfilment actions. Test the relationship between gateway references and store orders. A support person needs enough information to investigate a mismatch without accessing sensitive payment data.
Agree a controlled live check
Once the merchant account is approved, arrange an authorised live test and its reconciliation process. Confirm the order, customer notification, fulfilment visibility and any agreed refund. Record who checks settlement and discrepancies. Live payment behaviour depends on provider configuration, so this release check belongs alongside the technical test results.
Your practical checklist
- Define payment and fulfilment states
- Exercise sandbox failure scenarios
- Handle repeated and delayed notifications
- Approve and reconcile a controlled live test
Working through a similar question?
We’re happy to help you find a practical starting point.
Talk to AMGK