UPI AutoPay: Control Recurring Mandates

Quick View

What Matters

UPI AutoPay allows creation of electronic mandates for recurring payments through supported apps and banks. The user authorises the mandate terms, after which debits can occur according to the approved amount, frequency and validity.

The mandate should be distinguished from the underlying contract. Revoking a bank mandate can stop payment but may not cancel the subscription or contractual liability. Cancel through both merchant and payment channels where appropriate.

Limits, authentication requirements and eligible use cases can change. The app’s current mandate screen and NPCI or bank rules should be checked rather than relying on an old rupee threshold.

Decision Table

Action Checklist

1. Open the mandate section in every UPI app.
2. List active merchants and maximum amounts.
3. Cancel trials before the renewal date.
4. Revoke unused or unknown mandates.
5. Confirm cancellation with the merchant.
6. Monitor the next bank statement.

Practical Example

Evidence to Keep

• Mandate creation screen and UMRN or reference.
• Merchant subscription terms.
• Pre-debit and debit notifications.
• Revocation confirmation.
• Bank statement.
• Merchant cancellation acknowledgement.

Warning Signs

How to Decide

Use a recurring-payment register with merchant, purpose, amount, renewal date, cancellation channel and bank account. Review it before annual subscriptions renew.

For an unrecognised mandate or debit, report through the app and bank promptly. Liability and refund depend on the authorisation, reporting time and applicable electronic-transaction rules.

The decision should be recorded in writing when it changes a loan, claim, mandate, account status or family right. Verbal assurances are useful only when the institution later confirms them through the official channel.

Costs, limits, product terms and regulatory processes can change. Use the latest agreement, policy schedule, KFS, account statement or regulator instruction for the specific transaction rather than copying an old threshold from another case.

Control Test

The practical test is whether the reader can explain the decision using four separate records: the contractual position, the money movement, the institution’s communication and the final status. For this topic, the key stages are create, execute, pause or revoke, merchant cancellation. Each stage should have an owner, a date and a document.

Start with Open the mandate section in every UPI app. Then preserve Mandate creation screen and UMRN or reference. A later complaint is much stronger when it shows what was known, what was requested, what the institution did and which amount or right remains disputed.

Do not let urgency erase the audit trail. One of the clearest warning signs is Approving a maximum amount far above the subscription. Any payment, consent, waiver, mandate or family instruction made under pressure should be paused until the receiving entity and legal effect are independently confirmed.

A payment reference establishes that money moved, but the underlying purpose comes from the mandate, invoice, subscription or agreement. Preserve both layers. This distinction becomes critical for refunds, rent, deposits, recurring debits and business reimbursements.

Review payment controls at least monthly: active mandates, app permissions, linked accounts, small-value balances and failed or reversed items. Low-value transactions can still create repeated leakage or weak evidence when they are never reconciled.