Test cases for UPI AutoPay mandates and recurring debits

1. In the test merchant app, pick a monthly plan and choose UPI AutoPay
2. Pick the UPI app from the app chooser
3. Check the merchant name, maximum amount, frequency, start date and end date
4. Enter the UPI PIN and let the phone return to the merchant app

Expected: The merchant app shows the subscription as Active with the next debit date. The UPI app lists the mandate as Active with the same merchant, amount, frequency and dates.

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

1. From the merchant's test dashboard, send a mandate request to the tester's UPI ID
2. Open the request from the pending requests list in the UPI app
3. Review the terms, tap Approve and enter the UPI PIN

Expected: The mandate moves from pending to Active and shows the merchant's verified name. The request no longer appears in the pending list.

1. Choose a plan that charges the first period at sign-up
2. Approve the mandate with the UPI PIN
3. Check history, the bank balance and the merchant app

Expected: Exactly one debit for the first period appears, linked to the mandate. The next debit date is the same in the UPI app and the merchant app.

1. Use a test mandate with a debit due soon in the test environment
2. Leave the UPI app in the background and lock the phone
3. When the alert arrives, tap it

Expected: The alert names the merchant, the amount and the debit date in IST. Tapping it opens that mandate, where pause and revoke are available.

Why a real phone: Alert delivery depends on real push and SMS channels and OEM battery savers.

1. Let a test mandate reach its scheduled debit date
2. Open the mandate's history in the UPI app and check the bank balance
3. Open the subscription in the merchant app

Expected: One debit of the notified amount appears on the scheduled date, marked as AutoPay with the mandate reference. The merchant app shows the subscription renewed for the next period.

1. Open an Active mandate and tap Pause
2. Choose a pause end date after the next debit date and confirm
3. Let the next debit date pass, then check history and the balance

Expected: The mandate shows Paused with the end date in the UPI app and the merchant app. No debit or pre-debit alert happens while it is paused.

1. Open a Paused mandate and tap Resume
2. Confirm with the UPI PIN if asked
3. Check the next debit date in the UPI app and merchant app

Expected: The mandate shows Active again and both apps show the same next debit date. No debit is taken at the moment of resuming unless the app said so before the user confirmed.

1. Open an Active mandate in the UPI app and tap Revoke or Cancel
2. Read the confirmation, confirm and enter the UPI PIN if asked
3. Open the subscription in the merchant app
4. Let the next debit date pass

Expected: The UPI app shows Revoked with the date, and the merchant app shows the subscription as cancelled or ending. No alert or debit follows on the next debit date.

1. From the merchant's test dashboard, request a higher maximum amount on an Active mandate
2. Open the change request in the UPI app
3. Compare old and new values, approve and enter the UPI PIN

Expected: The request shows old and new values side by side. After approval the mandate shows the new values and a change entry in its history.

1. Create a mandate in UPI app A with test bank account X
2. In UPI app B, linked to the same account, open the mandates section
3. Open the mandate and try Pause

Expected: App B either lists the mandate with the same merchant, amount and status, or says it was set up in another app. It never shows a different status from app A.

Why a real phone: Each UPI app needs its own SIM-based device binding on a real phone.

1. Open a pending mandate request in the UPI app and tap Approve
2. Enter an incorrect UPI PIN
3. Check the mandates list and the merchant's test dashboard

Expected: An incorrect PIN message appears and no mandate is created. The request stays pending so the user can try again, and the dashboard shows no Active mandate.

1. Raise a change request for a higher amount from the merchant's test dashboard
2. Open it in the UPI app and tap Decline
3. Open the mandate details

Expected: The mandate keeps its original amount and frequency and stays Active. The merchant dashboard shows the change as declined.

1. Bring the linked test account's balance below the mandate amount
2. Let the scheduled debit run
3. Open the mandate in the UPI app and the subscription in the merchant app

Expected: The UPI app shows the failed debit with the insufficient balance reason, and the mandate stays Active. The merchant app shows the payment as failed and what the user can do next.

1. On an up-to-maximum mandate, raise a debit above the maximum from the test dashboard
2. Check the UPI app history and the bank balance

Expected: The debit is declined and no money moves. The UPI app shows no debit, or shows the attempt as declined.

1. Send a mandate request to the tester's UPI ID
2. Wait past the expiry time shown on the request
3. Try to approve it

Expected: The request shows Expired and cannot be approved. The merchant dashboard shows it as expired, not pending.

1. Let a scheduled debit fail for low balance
2. Top up the account
3. Let the merchant's configured retry run, then check history and the balance

Expected: Exactly one successful debit appears for that cycle, next to the failed attempt. The merchant app shows the period as paid once.

1. Create a mandate in UPI app A
2. Revoke it from UPI app B
3. Refresh app A and the merchant app
4. Let the next debit date pass

Expected: App A, app B and the merchant app all show Revoked. No alert or debit happens on the next date.

Why a real phone: Needs two real UPI apps bound to the SIM on the same phone.

1. In the merchant app, cancel an active subscription
2. Open the mandates list in the UPI app
3. Let the next debit date pass

Expected: The UPI app shows the mandate as revoked or ended by the merchant, with no next debit date. No alert or debit follows.

1. Create a monthly mandate starting on the 31st
2. Check the next debit dates in the UPI app and merchant app
3. Look at the dates for a 30-day month and February

Expected: Both apps show the same next debit date for every month, and the pre-debit alert uses that same date.

1. Use a test mandate whose end date is today
2. Let the end date pass
3. Open the mandate in the UPI app and the merchant app

Expected: The mandate shows Completed or Expired in both apps, and no further alerts or debits occur.

1. Open linked bank accounts in the UPI app
2. Start removing the account that funds an Active mandate

Expected: Before removal the app warns which mandates use this account and what will happen to them. After removal, the mandate list shows the result the warning described.

1. Reset the UPI PIN for the account funding an Active mandate
2. Open the mandate details
3. Let the next scheduled debit run

Expected: The mandate stays Active after the reset, and the next debit is taken as scheduled without asking for a fresh approval.

1. Open an Active mandate
2. Tap Revoke twice very quickly and confirm
3. Open the mandate's history

Expected: Only one confirmation and one PIN screen appear. History shows a single revoke entry and no error.

1. Open the approval screens for a fixed-amount mandate and a variable-amount mandate
2. Compare how each one states the amount

Expected: The fixed mandate shows the exact amount per debit and the variable one says up to the maximum. Both use lakh grouping, such as ₹1,00,000.

1. Start mandate setup from the merchant app and enter the UPI PIN
2. Turn on airplane mode within a second of submitting
3. Turn the network back on and reopen both apps
4. Repeat, submitting just as you walk into a lift or basement

Expected: Both apps show the setup as pending, then settle on one final status. Retrying from the merchant app does not create a second Active mandate.

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

1. On a 3–4 GB RAM phone, start mandate setup in the merchant app
2. Before entering the PIN, open a few heavy apps, then return to the UPI app
3. Approve, then reopen the merchant app from the launcher

Expected: The merchant app checks the status on reopening and shows the subscription as Active. It does not ask the user to set up the mandate again.

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

1. Start mandate setup from the merchant app
2. In the UPI app, press back or swipe back before entering the PIN

Expected: The merchant app shows setup as not completed and offers a retry. No pending or Active mandate appears in the UPI app.

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

1. On mobile data, open an Active mandate and tap Pause
2. Confirm while moving into a lift or an underground metro station
3. Reopen the mandate once the signal returns

Expected: The mandate shows either Paused or Active with a clear message, never stuck on a processing state. The merchant app shows the same status.

Why a real phone: Needs a real SIM losing coverage on Jio, Airtel or Vi.

1. Turn on airplane mode the day before a scheduled debit
2. Turn the network back on after the debit date
3. Open notifications and the mandate's history

Expected: History shows the debit on its scheduled date. Queued alerts arrive in order, and none says the debit is still upcoming after it has happened.

1. On a Xiaomi, Vivo or Oppo phone, leave battery settings at their defaults
2. Do not open the UPI app for several days before a debit
3. Wait for the pre-debit alert

Expected: The alert arrives before the debit through at least one channel the app uses, push or SMS.

Why a real phone: OEM battery savers on Xiaomi, Vivo and Oppo stop background apps receiving push.

1. Create a mandate on phone 1
2. Register the same number in the same UPI app on phone 2
3. Open the mandates section on phone 2

Expected: Phone 2 lists the mandate with the same status and dates, and pause and revoke work there.

Why a real phone: Re-registration needs SIM-based device binding with an SMS on a real phone.

1. On an iPhone, start mandate setup in a merchant app
2. Pick a UPI app from the list the merchant app shows
3. Approve, 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 subscription as Active.

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

1. Deny the notification permission when the UPI app asks
2. Open the AutoPay or mandates section

Expected: The app shows that pre-debit alerts are off and offers a link to turn notifications on. Mandate details still show the next debit date.

1. Send a mandate request from a merchant the tester has never used
2. Open the request in the UPI app

Expected: Before the PIN step, the screen states that approving allows repeated debits. It shows the verified merchant name, maximum amount, frequency and end date.

1. Open the UPI PIN screen while approving a mandate
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. Open the app, then send it to the background
2. Wait longer than the configured inactivity time
3. Reopen the app and go to mandates

Expected: The app asks for its lock before showing the mandate list or allowing pause or revoke.

1. With an Active mandate, start logging out or deregistering UPI
2. Read the confirmation screen
3. Finish, then check the merchant app

Expected: The confirmation lists active mandates and says whether they continue or are revoked. The merchant app status afterwards matches what the screen said.

1. Turn on TalkBack
2. Move through a mandate approval screen and a mandate's details
3. Pause the mandate and listen to the result

Expected: TalkBack reads the merchant, the amount in rupees, the frequency, the dates and the status. Pause and Revoke are announced with their purpose.

1. Switch the app language to Hindi
2. Open an approval screen, a pre-debit alert and a paused mandate

Expected: Frequencies, statuses such as Paused and Revoked, and dates appear in Hindi with no English leftovers. Amounts keep lakh grouping, such as ₹1,00,000.

1. Set font size and display size to the maximum
2. Open a mandate approval screen and a mandate's details

Expected: All terms stay visible without cut-off text, and the Approve button can be reached by scrolling.