Notes

Testing module:

I)Place order
Check if funds are received in merchant account
Verify if transaction can be refunded or void successfully

ii)Security Testing – During a transaction, a customer will be providing sensitive information like their credit card number, CVV number etc. It is very important to ensure that all the sensitive information is transmitted after encryption and that the channel is secure.

iii)Make sure the transaction is tested end to end. In our projects, we tested and reported numerous bugs related to data capture and data flow from application to the Payment gateway. Some of the specific bugs were:

Customer (buyer) name information was not getting captured correctly
The customer Credit card expiry date was getting captured incorrectly due to an incorrect function which was causing the transactions to be declined by the issuing bank on account of incorrect credit card information.
Duplicate transaction showing in Payment Processor
iv)If payment fails during a transaction for any reason, a suitable message should be shown to the customer. Any error message that is too technical like ‘Object not set to instance’ or ‘404 error’ can confuse the customer and impact user experience.
===============================================================
The following checklist can be helpful for testers and could be used as a reference:

1) Set up payment processor sandbox.

2) Gather test credit card numbers that would be used for testing different credit cards.

3) Verify the behavior of the application when a transaction is successful.

4) After successful transaction verify if the payment gateway returns to your application to show some kind of successful transaction/confirmation message.

5) Verify that the customer gets some kind of transaction confirmation notification like Order confirmation email, etc. if the transaction is successful.

6) Check what happens if a payment fails or payment processor stops responding- is there any error message?

7) Verify the application behavior with browser popup blocker on and off. This may be helpful if any confirmation messages are being displayed in the popup.

8) Verify different fraud prevention/security settings.

For example, if customer billing information does not match with the address provided to issuing bank- any mismatch will result in transaction decline.

9) Verify the transaction entries in the database if the tester has access to the Application database.

10) Check what happens when a customer session expires.

11) Check the console during entire transaction and report any console errors that are observed.

12) Verify that that transaction is done on a secure channel.

For example, the checkout pages may be HTTPS versus rest of website that are HTTP pages.

13) Verify that the payment processor currency is setup correctly.

For example, if the application/website is a Canadian company/retailer, the payment processor should be set up to accept CAD currency.

14) If the applications have multiple payment options like Credit card and PayPal together, both payment options need to individually tested from end to end.

15) Verify that refund or void amount (from payment processor admin portal) is same as the transaction amount. In no case, the refund/void amount should exceed the transaction amount.