Quality,  Software Testing,  Test Scenarios

Mobile Payment User Flow

In Mobile Payment User Flow, the Debit and Credit process is the most important process of any Payment app. It is also referred to as Online Payment sometimes, so it is very important to know the Online Payment Use Cases so that any user, as well as any QA or Developer, can test their application and make it better.

Online Payment Use Cases

Let’s try the transaction of $10 as an example, we have the below the Mobile Payment User Flow to verify the transaction.

1. Sender >> initiate payment with all the valid details >> Debit done >> response received >> message display to sender “$10 has been debited from your account” >> Credit done >> response received >> message display to receiver “$10 has been credited from your account” >> “Payment Successful” status will display in Sender’s transaction history after successful credit.

2. Sender >> initiate payment with all the valid details >> Debit done >> response received >> message display to sender “$10 has been debited from your account” >> Credit response is not receiving within a certain time >> “Payment is In-progress” or “Awaiting for credit confirmation” status will display in Sender’s transaction history with “Refresh” status button >> within some certain time Credit response received >> message display to the receiver “$10 has been credited from your account” >> “Payment Successful” status will update in Sender’s transaction history.

3. Sender >> initiate payment with all the valid details >> Debit done >> response received >> message display to sender “$10 has been debited from your account” >> Credit response is not receiving within a certain time >> “Payment is In-progress” or “Awaiting for credit confirmation” status will display in Sender’s transaction history with “Refresh” status button >> Credit not done >> if credit not done after a certain time then message display to sender “Payment failed, Awaiting for Refund”.

4. Sender >> initiate payment with all the valid details >> no internet / internet interrupted >> payment not initiated >> message “Please check the internet connectivity”.

5. Sender >> initiate payment with all the valid details >> Low balance >> Debit failed, the message “Payment failed due to low balance”.

6. Sender >> initiate payment with all the valid details >> Debit API hit >> debit response not get within a certain time >> message “Payment failed, server not responding”.

7. Sender has $10 amount only >> initiate first payment of $10 with all the valid details >> Debit API hit >> debit response is in progress and getting late due to slow internet connectivity >> Again initiate second payment of $10 with all the valid details >> “Payment is In-progress” status will display for both the payments till getting a response with “Refresh” status button.

8. Sender >> initiate payment with any invalid detail >> message “Payment failed”.

There can be many use cases that can implement as per the functionality of the payment app.

——–*———–*———-*———-*———–*———-

Click here to read Login, Logout and Forget Password

Click here to read Cut Copy Paste Test Scenarios

Leave a Reply

Your email address will not be published. Required fields are marked *