Payment Method

Payment Gateway?

1) Self-Hosted Payment Gateway

Hosted Payment Gateway redirects customers away from the e-commerce website’s checkout page. Once the user clicks the Pay Now button, the application redirects the user to payment service provider page. On this page, he can fill in all required details and once the payment is done, it will bring him back to the website page. for this type of payment, a merchant id is not required. Some examples are Stripe and Circle.

2) Shared / Non-Hosted Payment Gateway

For these types of Gateways, the customer is redirected to the payment page configured within the e-commerce website. This option is easy to customize as you can control your checkout from start to finish. The only challenge with going with this option is, that merchants must follow all security measures to maintain confidentiality and protect customers’ data.

Now we will look at the list of Test Scenarios for Payment Gateway Integration. You can use these scenarios for preparing the Test Cases.

Functional Test Scenarios for Payment Gateway:

1) User Data transmitted to the gateway must be set over a secured(HTTPS or other) channel.

2) Some applications ask Users to store Card information. In that case, the system should store Card information in an encrypted format.

3) Check for all mandatory field validation. The system should not go ahead with the payment process if any data for any field is missing.

4) Test with Valid Card Number + Valid Expiry Date + Invalid CVV Number.

5) Test with Valid Card Number + Invalid Expiry Date + Valid CVV Number.

6) Test with Invalid Card Number + Valid Expiry Date + Valid CVV Number.

7) Test all Payment Options. Each payment option should trigger the respective payment flow.

8) Test with multiple currency formats(if available).

9) Test with a Blocked Card Information.

10) Try to submit the Payment information after Session Timeout.

11) From the Payment Gateway Confirmation page try to click on the Back button of the browser to check whether Session is still active or not.

12) Change Payment Language during the Payment process.

13) Check the behavior?when the payment gateway stops responding to the request. Stop the process and verify if payment is debited or not.

14) Try to disconnect the internet connection while the payment process is in progress.

15) Check after successful payment whether all necessary data was retrieved at application or not.

16) Verify that the End-user gets a notification email upon successful payment.

17) Verify that the End-user gets a?notification email with proper reason upon payment failure.

18) Some application provides confirmation through pop-up dialogues. Test this feature by keeping the web browser pop-up on.

19) Test authorization receipt after successful payment. Verify all fields carefully.

20) Check if double payment is happening for any case.

21) Try to test with real-time transactions by providing actual payment information. If not feasible, gather dummy debit/credit card information for testing purposes.

Before You Start Testing Payment Gateway:

• Gather required test data for dummy debit/credit information.
• Gather Payment Gateway type and all related information.
• Finalize performance testing parameters for testing Payment Gateway flow.
• Collect Payment Gateway error codes. It is useful when an error occurs during testing to make sure whether it is our Application’s fault or a payment gateway-related error.