Test cases for UPI payment: PIN, intent and pending states

1. Open Pay and enter a valid test UPI ID
2. Check the payee's registered name shown below the ID
3. Enter ₹10, add a note and tap Pay
4. Enter the correct UPI PIN and submit

Expected: The success screen shows ₹10, the payee name, a UPI transaction ID and the IST date and time. The balance is ₹10 lower on the next balance check.

1. Choose Pay to mobile number and enter a 10-digit test number
2. Wait for the payee name to appear
3. Enter an amount, tap Pay and enter the UPI PIN

Expected: The payee's bank-registered name appears before the PIN step. The receipt shows the payee's UPI ID or a masked mobile number, not the full number.

1. Tap Pay contacts and allow the contacts permission when asked
2. Search a contact by name and pick one shown as on UPI
3. Pay ₹1 and enter the UPI PIN

Expected: Only contacts with a reachable UPI handle offer Pay. After the payment, the contact appears at the top of recent payees.

1. Choose Pay to bank account
2. Enter the account number twice, the IFSC and the holder's name
3. Enter an amount, tap Pay and enter the UPI PIN

Expected: The bank and branch for the IFSC are shown before payment. The receipt shows a masked account number, the IFSC and the transaction ID.

1. In the test merchant app, choose UPI at checkout
2. Pick the UPI app from the app chooser
3. Check that the amount and merchant name are prefilled and locked
4. Enter the UPI PIN and let the phone return to the merchant app

Expected: The merchant app shows the order as paid without a manual refresh. The UPI app history shows the same reference number as the merchant's order screen.

Why a real phone: Needs two real installed apps and an Android app switch and return.

1. Link two test bank accounts and set one as primary
2. Start a payment and switch to the second account on the confirm screen
3. Enter that account's UPI PIN

Expected: Money is debited from the selected account and the receipt names that bank with a masked account number. The primary account setting does not change.

1. Open transaction history and filter to the last 7 days
2. Open a successful payment
3. Tap Share and send the receipt to a messaging app

Expected: The receipt shows the amount with lakh grouping, payee, bank, transaction ID and IST time. The shared image or PDF shows the same details with the account number masked.

1. Complete a payment and lock the phone at once
2. Wait on the lock screen
3. Tap the notification and unlock

Expected: A notification with the amount and payee arrives, and tapping it opens the receipt for that transaction.

Why a real phone: Delivery depends on real push channels and OEM battery savers on Xiaomi, Vivo, Oppo.

1. From a second test account, send a collect request for ₹5
2. On the payer phone, open the request from the pending list
3. Check the requester name, amount and expiry, then tap Pay and enter the PIN

Expected: The request shows Paid on both phones and leaves the pending list. The debit matches the requested amount exactly.

1. Start a ₹1 payment to a saved payee
2. Enter an incorrect UPI PIN and submit
3. Open the transaction in history

Expected: The app shows an incorrect PIN message and no money is debited. History lists the attempt as Failed, never Pending.

1. Enter a wrong UPI PIN repeatedly until the bank stops accepting attempts
2. Try a new payment with the correct PIN

Expected: The app shows the bank's block message and explains how to reset the PIN. Later attempts show the same block message, not a generic error.

1. Choose an account whose balance is below the amount
2. Enter the amount, tap Pay and enter the correct PIN

Expected: The insufficient balance reason is shown in plain words and no money moves. The user can retry with another linked account without re-entering the payee.

1. Enter a UPI ID without the @ part
2. Enter one with spaces or an emoji
3. Enter a well-formed ID that does not exist

Expected: Malformed IDs show an inline format error. The non-existent ID shows a not-found message, and Pay stays disabled in all three cases.

1. Enter 0, then 10.555, then paste text containing letters
2. Enter 100000 and look at the displayed amount

Expected: Zero, three decimal places and letters are rejected inline. 100000 displays as ₹1,00,000.

1. In Pay to bank account, enter an IFSC with the wrong length
2. Enter a correctly formatted IFSC that does not exist

Expected: The wrong length is rejected inline. The unknown IFSC shows an error with no bank name, and the PIN screen does not open.

1. Receive a collect request from a second test account
2. Open it and tap Decline
3. Check the request on the requester's phone

Expected: Both phones show Declined, no PIN screen opens and no money moves.

1. Use a test setup where the bank's response is delayed
2. Pay and stay on the result screen
3. Wait, then pull to refresh

Expected: The screen shows Pending with advice not to pay again. It changes to Success on its own or on refresh, with only one debit.

1. Use a test case where the payee bank's confirmation times out after the debit
2. Open the result screen and then history

Expected: The status uses the app's deemed or under-confirmation wording and says the money is debited and will settle or be reversed. No Pay again button is offered.

1. Open a transaction where the payer was debited but the payee got nothing
2. Tap Check status
3. If still unresolved, raise a complaint from the same screen

Expected: The status check shows the latest bank status with a time. The complaint returns a reference number that stays visible on that transaction.

1. Use a failed transaction whose debit has been reversed by the bank
2. Open it in history and check the balance

Expected: The transaction shows Failed with a reversed note and the reversal time. The balance includes the refunded amount.

1. Fill in the payee and amount
2. Tap Pay twice very quickly
3. Enter the UPI PIN

Expected: Only one PIN screen opens and only one debit happens. History shows a single transaction.

1. Enter an amount equal to the configured limit and pay
2. Start another payment one rupee above the limit

Expected: The exact limit goes through to the PIN screen. One rupee more is blocked with the limit message before the PIN screen.

1. Enter the UPI PIN and submit
2. Turn on airplane mode within a second
3. Wait a minute, turn the network back on and open history
4. Repeat, submitting just as you walk into a lift or basement

Expected: While offline the app shows Pending or Checking, not Failed. Once online it shows the final status and does not ask to pay again.

Why a real phone: Real dead zones lose packets slowly; an emulator's network cut is instant and clean.

1. Start a payment on Wi-Fi
2. On the confirmation screen, turn Wi-Fi off so the phone moves to mobile data
3. Tap Pay and enter the PIN

Expected: The payment completes or shows Pending with a status check. There is no session-expired loop and no duplicate debit.

Why a real phone: Wi-Fi to mobile data handover needs a real SIM on Jio, Airtel or Vi.

1. Open the UPI PIN screen and type two digits
2. Answer an incoming call
3. End the call and return to the app

Expected: The partial PIN is cleared, and the app either cancels safely or shows an empty PIN screen. No payment goes through without a fresh PIN.

Why a real phone: Needs a real incoming SIM call to interrupt the secure PIN screen.

1. On a 3–4 GB RAM phone, start an intent payment from the merchant app
2. Before entering the PIN, open a few heavy apps, then return to the UPI app
3. Enter the PIN and reopen the merchant app from the launcher

Expected: The merchant app checks the status on reopening and shows the order as paid. It does not ask for payment again for the same order.

Why a real phone: Low-RAM phones and OEM memory managers kill background apps during app switching.

1. Start an intent payment from the merchant app
2. In the UPI app, press back before entering the PIN

Expected: The merchant app shows the payment as not completed and offers a retry. The order is not marked as paid or left stuck in Pending.

Why a real phone: The return path between two installed apps depends on real app switching and gesture navigation.

1. Submit the UPI PIN
2. Press home or lock the screen at once
3. Return to the app after a minute

Expected: The app opens on the final status of that payment, not a blank screen or a fresh payment form.

Why a real phone: OEM battery savers on Xiaomi, Vivo and Oppo freeze or kill backgrounded apps.

1. On a dual-SIM phone, start UPI onboarding
2. Choose the SIM whose number is registered with the bank
3. Let the app send the verification SMS

Expected: The app names the SIM slot it will use, sends the SMS from it and lists the bank accounts linked to that number.

Why a real phone: Device binding SMS is sent from a physical SIM slot over the carrier network.

1. Complete onboarding with SIM 1
2. Power off, remove SIM 1 or swap the slots, and restart
3. Open the app and try to pay

Expected: The app detects the change and asks to verify the device again before any payment. No payment is sent on the old binding.

Why a real phone: SIM removal and slot swap detection needs physical SIMs in a real phone.

1. Use a 5-inch phone on the oldest Android version the app supports
2. Make a payment with the keyboard open on the amount field

Expected: The Pay button stays reachable above the keyboard and the PIN screen renders in full.

1. On an iPhone, start a UPI payment in a merchant app
2. Pick a UPI app from the list the merchant app shows
3. Pay, then return using the app switcher instead of the automatic return

Expected: The merchant app checks the status when it comes back to the foreground and shows the correct result.

Why a real phone: Switching between real installed iOS apps cannot be reproduced in a simulator.

1. Open the UPI PIN screen
2. Try the phone's screenshot buttons and gesture
3. Start a screen recording and type a PIN

Expected: Screenshots are blocked or come out black, and the recording shows the PIN area blank.

Why a real phone: OEM screenshot gestures and recorders on Android skins must respect the secure flag.

1. Set the phone to show notification content on the lock screen
2. Receive a payment and look at the locked screen

Expected: The notification shows the amount and payee only, with no balance or full account number.

Why a real phone: Lock-screen notification display differs across OEM skins and their privacy settings.

1. Open the app and send it to the background
2. Wait longer than the configured inactivity time
3. Reopen the app from recent apps

Expected: The app asks for its lock before showing balance, history or payees. The recent apps thumbnail does not show account details.

1. Send a collect request from an account not in the payer's contacts
2. Open it on the payer's phone

Expected: The screen says plainly that approving will debit money from the payer, shows the requester's verified name and marks the sender as unknown.

1. Log out or deregister UPI from the app settings
2. Reopen the app

Expected: Linked accounts, payees and history are no longer visible. Paying again requires a fresh device verification.

1. Turn on TalkBack
2. Move through payee, amount, account picker and Pay
3. Listen to the result screen

Expected: Every control is announced with its purpose, the amount is read in rupees, and the result is announced as success, pending or failed.

1. Switch the app language to Hindi
2. Pay with a note typed on a Hindi keyboard, then one in Hinglish
3. Open the receipt and history

Expected: Labels, errors and statuses, including Pending, appear in Hindi with no English leftovers. Both notes display correctly in the receipt and history.

1. Set font size and display size to the maximum
2. Make a payment and look at the confirmation and result screens

Expected: The amount, payee name and Pay button stay fully visible with no cut-off text. The transaction ID stays readable and can be copied.