Payment Gateway Testing

What is Payment Gateway Testing?

Payment gateway Testing is a type of testing where testing of a payment gateway tests the security, dependability, and execution of a payment gateway by encrypting and safely the payment details between the user and seller delivering a soft payment experience.

Mostly payment gateway systems are used in e-commerce websites for online purchases by credit card or debit card. Payment gateways defend the credit/debit card details by encrypting sensitive information like card numbers, account owner details, etc. This information is given safely and securely between the customer and the seller and vice versa.

Payment Gateway Terminology

Below explain some primary terms related to the payment gateway which is more used in this type of testing.

1) Merchant – A merchant is one of the persons or organizations that sell products or services Flipkart, Amazon, and eBay are examples of merchants.

2) Credit Card – Credit card is a plastic card that can be used to buy products or services through a credit account. A credit card has a 16-digit card number, its expiration date, magnetic strip, signature panel, and a Card verification value (CVV) number which is shown below in the image front and back of the credit card

Front of Credit Card:

credit card front

Back of Credit Card:

credit card back

3) Acquiring bank – Acquiring Bank is one of the financial institutions that manage the merchant’s bank account and allows a merchant to receive and process debit/credit card transactions in their store.

4) Issuing Bank – Issuing Bank is also one of the institutions that issue the customer’s debit/credit card. When a customer uses their credit/debit card to
Purchase, Issuing Bank is the financial institution that issues the customer’s debit or credit card. Whenever a customer uses a credit or debit card to create a purchase, the Issuing bank either approves or denies the transaction based on the cardholder account standing and gives that data to the Acquiring Bank.

For example, the transaction will be rejected if the amount exceeds the card limit, if enter the wrong CVV, the wrong expiry date, etc.

5) Transaction – Transaction is the end-to-end process in which the merchant receives an amount for a transaction with a buyer.

6) Authorization – An authorization request is generated when the customer tries to make a payment. Authorization is mainly provided by the customer’s issuing bank and confirms the validity, payment ability, and checks sufficient funds are available in the account, etc. Once the process is completed amount is held and the balance is deducted from the customer’s credit limit but yet not it is transferred to the merchant account.

7) Capture – In capture, the vendor collects the suitable buyer payment information and transmits a settlement/capture request to the processor. The processor uses this information to initiate a funds transfer between the buyer’s card account and the vendor’s bank account.

Why do we need to test Payment Gateways?

If we going to buy in actual stores, we would pay cash money or pay using swipe our card (credit/debit) through the machine during payment to complete the transaction.

If using credit or debit cards, the POS (Point of Sale testing) machine will display if the payment processing would be approved or declined.

Also, during online transactions, we need to have a similar system in place, which approves or rejected a transaction instantly.

From a customer point of view, the online payment processing on the e-Commerce website should be seamless. When the Customer clicks the ‘Pay now button and in the next few seconds payment is successful or declined message should be displayed.

ecommerce domain testing

From the e-Commerce store point of view, the merchant needs to ensure that the complete payment cycle (getting transactions from an online store, capture and authorizing, refund, voiding) is working fine. If any of these sections do not work as expected, then it can be a problem for the merchant.

From the merchant’s viewpoint, the testing step allows them to get used to the selected payment processor flow and consider if the selected choice is actually the best fit for their application and business.

Kinds of Testing required

Based on the choice of the Payment processor and the product /application necessity, you may be needed to perform the following kinds of testing.

  • Functional Testing – Functional testing is needed for newer, less established payment gateways to confirm that the application acts as it should i.e. it handles orders, calculations, taxations, etc. exactly how it is considered to. For more established payment processors, this type of testing may not be required.
  • Integration Testing – Integration testing is required while integrating with a payment gateway. As a tester, you would need to confirm that the integration of your website/online store/application is working fine with the selected payment gateways. Testers need to test the entire transaction flow:
    • Place order
    • Test if funds are received in the merchant account
    • Confirm if the transaction can be refunded or voided successfully
  • Performance Testing – It is important to test the website for performance. The payment processor should not fail if multiple users are trying to make a payment at the same time.
  • Security Testing – At the time of the transaction, a customer will be providing sensitive information like their credit card number, CVV number, etc. It is very essential to ensure that all the sensitive information is sent after encryption and that the channel is secure.

Payment Gateway Testing Checklist and Test Cases

  1. During the payment process try to change the payment gateway language.
  2. After the payment process, test all the required details, and whether it is recovered
    or not.
  3. Test what happens if the payment gateway stops responding at the time of payment.
  4. Test what happens if the session ends during the payment process.
  5. Test what happens in the backend during the payment process.
  6. Verify what happens if the payment process fails.
  7. Test the Database entries whether they store credit card details or not.
  8. Verify error pages and security pages during the payment process.
  9. Test the settings of the pop-up blocker and verify what happens if a pop-up blocker is on.
  10. Check buffer pages Between the payment gateway and the application.
  11. Test after successful payment, a success code is sent to the application and a confirmation page is shown to the user.
  12. Verify after a successful transaction if the payment gateway returns to your application.
  13. Test all formats and messages when the successful payment process.
  14. Verify the amount format with the currency format.
  15. Verify if each of the payment options is selectable.
  16. Verify if each listed payment option opens the respective payment option according to
    specification.
  17. Test whether the payment gateway defaults to the selected debit/credit card option.
  18. Check the default option for debit card shows card selection drop-down menu.

Conclusion:

Different types of payment gateways provide different costs, supports, and payment types. But it is absolutely a factor to decide whether you can make a sale or not since sometimes, customers have to cancel purchasing and check for other options from different stores, just because your store doesn’t offer their selected payment gateway. so, a payment gateway that supports all payment types of payment is always a preferred choice.

Secondly, it is also important to assess the integration of payment gateway, the payment gateway which is simple to integrate with any eCommerce platform is the next choice.

The third option is whether the customer would decide to buy products or not so the payment gateway must be trustable and secured.

It is good if you know which is the better and most used payment gateway and which eCommerce platform provides that payment gateway.

Read Also:

1) Test Cases of E-commerce Website

2) How to test an E-commerce website or application?

3) Top-rated E-commerce Testing Service Providers

4) E-commerce Website Testing Guide

Twisa Mistry

Twisa works as a Software Tester at QACraft. She is a Computer Engineer with a degree and she has 5+ years of experience in the QA field(Manual as well as Automation Testing). As an automation tester, she has good knowledge about Automation testing of web-based applications using selenium Webdriver. In her free time, she loves to explore new technologies.

https://qacraft.com/author/twisa-mistry/