Skip to content
99tests Blog
Testing guides

How to Test UPI AutoPay Mandates: Setup, Pre-Debit Alerts, Pause and Revoke

A practical guide to testing UPI AutoPay: mandate setup with the UPI PIN, pre-debit alerts, recurring debits, pause, revoke, failed debits and retries, cross-app mandates and OEM battery savers.

Hand-drawn sketch of a calendar, a rupee coin and a phone receiving an alert
In this article
  1. Scope
  2. Set up before you test
  3. 1. Happy path
  4. 2. Validation and negative cases
  5. 3. Edge cases that become disputes
  6. 4. Interruptions and network
  7. 5. Device and OS
  8. 6. Security and privacy
  9. 7. Accessibility and language
  10. The six places it breaks most
  11. Get the full test case set

UPI AutoPay looks simple: the user approves a mandate once with their UPI PIN, and the merchant debits them every month. It's hard to test because one mandate lives in three places: the merchant app, the UPI app and the bank. They drift apart when a status update is missed, when a battery saver stops the pre-debit alert, or when the user manages the mandate from a different UPI app.

When they drift, users see a debit they weren't warned about, get charged after cancelling, or lose a service they're still paying for. Each of those becomes a support ticket or a dispute.

This guide is based on the free UPI AutoPay test case set in the 99tests library: 40 cases with steps, expected results, priority and whether each one needs a real phone.

Scope

Cover these parts of the mandate's life:

  • Creating a mandate with the UPI PIN, from a merchant app or a collect-style request
  • Pre-debit alerts and the recurring debit itself
  • Pause, resume, revoke, and changes to amount or frequency
  • Failed debits and merchant retries
  • Mandate status in the merchant app, the UPI app and a second UPI app

One-time UPI and QR payments, and card or net banking e-mandates, belong in separate plans.

Set up before you test

  • A test merchant app and dashboard that can create mandates and trigger debits
  • Two UPI apps on a real dual-SIM Android, both linked to the same test bank account
  • Test bank accounts with known balances, including one you can empty for failure cases
  • Test mandates with a debit due today, so you don't wait a month to check a debit

Note the mandate reference for every test so each debit can be traced afterwards.

1. Happy path

  • Create a monthly mandate from the merchant app. Check the merchant name, maximum amount, frequency, start and end dates, then enter the PIN. Both the merchant app and the UPI app should show Active with matching details. This needs a real phone: it's two installed apps and an Android app switch and return.
  • Approve a mandate request sent to a UPI ID.
  • Take the first payment at sign-up when the plan charges upfront. There should be exactly one debit.
  • The pre-debit alert. It should name the merchant, amount and debit date in IST, and open the mandate where pause and revoke are available.
  • The recurring debit happens once, on the scheduled date, marked as AutoPay.
  • Pause and confirm nothing is debited, and no alert is sent, during the pause. Then resume.
  • Revoke from the UPI app, and check that the merchant app shows the subscription as cancelled.
  • Approve a change of amount or frequency. Old and new values should appear side by side.
  • Manage the mandate from a different UPI app than the one that created it.

2. Validation and negative cases

  • A wrong UPI PIN while approving. No mandate is created, and the request stays pending.
  • Declining a change request. The original terms stay.
  • A debit failing for insufficient balance. The mandate stays Active, and both apps explain what happened.
  • The merchant tries to debit above the approved maximum. It must be declined and no money should move. This is P1.
  • A mandate request left to expire.

3. Edge cases that become disputes

  • A retry after a failed debit. There must be exactly one successful debit for the cycle, after the user tops up.
  • Revoking in a second UPI app, then checking app A, app B and the merchant app all show Revoked.
  • Cancelling inside the merchant app, then checking the UPI app shows the mandate ended, with no next debit date.
  • A monthly mandate starting on the 31st. Both apps and the alert should show the same date for 30-day months and February.
  • A mandate reaching its end date.
  • Removing the bank account that funds an active mandate. The app should warn first.
  • Resetting the UPI PIN while a mandate is active.
  • Tapping Revoke twice quickly. There should be one PIN screen and one revoke entry.
  • Exact-amount versus up-to-maximum mandates, shown differently, with lakh grouping (₹1,00,000).

4. Interruptions and network

  • The network drops right after the UPI PIN while creating a mandate, including walking into a lift. Retrying must not create a second Active mandate. P1, and it needs a real phone, because real dead zones lose packets slowly while an emulator's cut is instant.
  • The merchant app is killed while the user approves on a 3–4 GB RAM phone. On reopening, the merchant app should check the status and not ask the user to set up again.
  • Pressing back in the UPI app before approving.
  • Pausing on a weak network in a lift or metro. The mandate should never be stuck on "processing".
  • The phone is offline on the debit date. Queued alerts should arrive in order.

5. Device and OS

  • The pre-debit alert on a Xiaomi, Vivo or Oppo phone with default battery settings, and with the UPI app unopened for days. This is where alerts go missing.
  • Mandates still listed after moving to a new phone.
  • Creating a mandate on an iPhone and returning through the app switcher.
  • Notifications denied on Android 13+. The app should say that alerts are off.

6. Security and privacy

  • A request from an unknown merchant must state that approving allows repeated debits, and show the verified name, maximum amount, frequency and end date before the PIN step. P1.
  • Screenshots and screen recording blocked on the PIN screen, including the maker's own gestures.
  • The app lock required before showing or changing mandates.
  • A clear statement of what happens to active mandates on logout or deregistration.

7. Accessibility and language

  • TalkBack reads the merchant, the amount in rupees, the frequency, dates and status.
  • Hindi for frequencies and statuses, with lakh grouping kept.
  • The largest font size, with the Approve button still reachable.

The six places it breaks most

  1. Pre-debit alerts never reach users on Xiaomi, Vivo, Oppo and Realme phones where the UPI app hasn't been opened for weeks.
  2. On low-RAM phones the merchant app is killed during approval, the user sets up again, and ends up with two Active mandates.
  3. A cancel in one place never reaches the other: Active in the UPI app, cancelled in the merchant app, or the reverse.
  4. Mandates set on the 29th to the 31st, or dates converted around midnight IST, show different next debit dates in different places.
  5. A mandate set up in one UPI app appears differently, or not at all, in another, so users can't find where to stop it.
  6. Retries after a low-balance failure show up as several entries, and users who top up after cancelling get charged.

Get the full test case set

All 40 UPI AutoPay test cases are free, with steps, expected results and real-device reasons, ready to copy into your test tool.

The cases marked "real device" are the ones emulators miss. 99tests runs exploratory testing sessions on real Android phones and iPhones across Indian cities and networks, from ₹9,999 + GST with a report in 3 business days.