Payment Gateway Testing

Payment gateway testing is the process of verifying that an application can securely and reliably process payments through a payment provider such as Stripe, PayPal, Braintree, or a bank/payment service.

Because payment processing directly affects revenue, customer trust, and financial records, testing should cover successful payments as well as failures, interruptions, duplicate requests, refunds, and other edge cases.

Major Areas of Payment Gateway Testing

1. Payment Initiation

   • Verify the correct payment amount is sent to the gateway.

   • Verify order ID, customer information, currency, and other required data.

   • Verify supported payment methods are displayed correctly.

2. Successful Payment

   • Complete a valid payment.

   • Verify the payment status is updated correctly.

   • Verify the order is created or confirmed.

   • Verify the correct amount is recorded.

   • Verify the customer receives the appropriate confirmation.

3. Payment Failure Testing

   • Declined card/payment method

   • Insufficient funds

   • Invalid payment details

   • Expired card

   • Incorrect security information

   • Gateway or bank rejection

   • Payment timeout

4. Cancellation & Interruption

   • Customer cancels payment.

   • Customer closes the payment page.

   • Browser/app is refreshed during payment.

   • Network connection is lost during payment.

   • Gateway becomes temporarily unavailable.

5. Duplicate Payment Prevention

   • Refresh or resubmit the payment request.

   • Click the payment button multiple times.

   • Retry after a timeout.

   • Verify that the customer is not charged multiple times for the same order.

6. Payment Status & Order Synchronization
   Verify that payment and order statuses remain consistent.

   Example:

   Payment Successful → Order Confirmed

   Payment Failed → Order Not Confirmed

   The exact behavior may vary depending on the application's design, but the states should be handled consistently.

7. Refund & Cancellation Testing

   • Full refund

   • Partial refund

   • Refund failure

   • Cancelled order after payment

   • Verify refund status and transaction records

   • Verify customer notifications where applicable

8. Currency & Amount Testing

   • Different supported currencies

   • Decimal values

   • Minimum and maximum transaction amounts

   • Taxes, discounts, and fees

   • Currency conversion where applicable

   • Rounding calculations

9. Security Testing

   • Secure transmission of payment information

   • Authentication and authorization

   • Session handling

   • Input validation

   • Protection against unauthorized transactions

   • Ensure sensitive payment information is not unnecessarily exposed in logs or responses

10. Webhook & Callback Testing
    Many payment systems notify the application about payment events through webhooks or callbacks.

Test scenarios such as:

• Payment success notification

• Payment failure notification

• Refund notification

• Delayed notification

• Duplicate webhook delivery

• Invalid or unauthorized webhook requests

1. Integration & Reliability Testing
   Verify communication between:

Application → Payment Gateway → Bank/Payment Provider → Application

Test gateway timeouts, API errors, delayed responses, network failures, and recovery behavior.

Example Payment Flow

A typical payment test can follow:

Add Product → Cart → Checkout → Select Payment Method → Submit Payment → Gateway Processing → Payment Result → Order Status → Transaction Record → Confirmation

Every stage should be checked to ensure that the final payment and order state are correct.