![\"Steps](\"\/blog\/wp-ttn-blog\/uploads\/2017\/07\/123.jpg\" "\\"Steps")
Figure 1: Steps in payment transaction and stakeholders involved.<\/p><\/div>\n
As can be seen in Figure 1 above, the first stakeholder in the process is the User<\/strong><\/em>, who places the order which in the form of order reaches Merchant\u2019s<\/strong><\/em> web server. Based on the availability of the product, the merchant server responds back to the user. Once the user gets the confirmation about the availability of the product, they process the payment through Payment Gateway<\/strong><\/em> which is linked to the merchant\u2019s server. During the payment process, there are three stakeholders, i.e. User<\/em>,<\/b> who use the credit\/debit card, Acquiring Bank<\/strong><\/em> (Merchant\u2019s bank account) and Issuing Bank<\/strong><\/em> (User\u2019s bank account). The last step is the transaction, wherein the transaction is completed and then the merchant receives funds from the user. However, this step is further sub-divided into two steps, wherein the first authorization is given by user\u2019s issuing bank by confirming the card holder\u2019s validity and ability to pay. At this stage, the payment is deducted from the user\u2019s account, however, is not credited to the merchant. The merchant receives the payment in capture step wherein customer\u2019s payment information is processed between user\u2019s card account to merchant bank account.<\/p>\n 1. Availability of free isolated environment:<\/strong> Look for a free isolated environment (for trial and exploratory purposes) that can be used for the Payment Gateway; it needs to be tested or implemented. Having such an environment definitely, helps and gives the team that extra flexibility to customize the tool and test as in depth as required.<\/p>\n 2. Testing should be done end-to-end:<\/strong> We must make sure that transaction is tested end to end. Few common bugs are related to data capture and data flow from application to the Payment Gateway.<\/p>\n Figure 2: Common bugs to watch out for.<\/p><\/div>\n 3. Issue resolving options:<\/strong> If payment fails during a transaction for any reason, an appropriate message should be shown to the customer. A technical message like \u2018Server is down\u2019 or \u2018404 error\u2019 can confuse the customer and might affect the usability of the application. Generic messages like \u201cThere seems to be some issue in processing the transaction, please contact us at Customer Care Number\u201d will make the user experience better.<\/p>\n 4. Post production verification:<\/strong> For this purpose, the business owner will need to create a live payment processor account and set up their Merchant ID. After setting up, Regress testing<\/a> should be done on the payment processor before the application and payment processor integration goes live for the public.<\/p>\nNeed to test payment gateway<\/strong><\/h2>\n
\n\n
\n Type<\/th>\n Explaination<\/th>\n Examples<\/th>\n<\/tr>\n \n Black Box Testing\/Functional Testing<\/th>\n Required for raw, less reputed payment gateways to ensure that the application behaves in the proper way.<\/td>\n Order handling, Calculation of payment, taxes etc.<\/td>\n<\/tr>\n \n Integration Testing<\/th>\n Required during the integration of the application with chosen payment gateways.<\/td>\n Order placing, Fund receiving, Refund of payment etc.<\/td>\n<\/tr>\n \n Performance Testing<\/th>\n Required for a performance of process mainly to check that the website does not lead to failure when multiple customers try to complete the transaction at the same time.<\/td>\n Website\/online store\/application<\/td>\n<\/tr>\n \n Security Testing<\/th>\n Required during the payment part when a customer shares sensitive information online.<\/td>\n CVV number, credit\/debit card no, transaction password<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n \n\n
\n Table 1: Kinds of testing needed in the process<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Tips for testing the payment gateway:<\/strong><\/h2>\n
![\"](\"\/blog\/wp-ttn-blog\/uploads\/2017\/07\/656.jpg\" "\\"")
Conclusion<\/strong><\/h2>\n