A UPI AutoPay control for viewing, pausing, revoking and documenting mandates while separating merchant subscription cancellation from payment-mandate cancellation.
Stopping a subscription inside a merchant app and revoking the bank mandate are related but not always the same action.
UPI AutoPay supports recurring e-mandates and provides mandate-management functions through participating apps.
A mandate record should show merchant, amount or cap, frequency, debit dates and status.
Users should cancel the underlying merchant service and also revoke or pause the UPI mandate where appropriate.
A post-cancellation debit should be reported with proof of the revocation time, merchant cancellation and transaction reference.
| Check | What to examine |
|---|---|
| Merchant | Legal name, app and subscription account. |
| Mandate | UMN/reference, cap, frequency and validity. |
| Action | Pause, revoke, modify or merchant cancellation. |
| Debit | Date, amount and pre-debit notification. |
| Dispute | App, bank and merchant complaint trail. |
A user cancels a streaming plan but leaves the UPI AutoPay mandate active. The next debit may reflect a failed merchant cancellation or an active mandate. The user should preserve both the subscription screen and the mandate status rather than rely on one.
Review active mandates monthly, especially after free trials, loan closure, app deletion or change of service provider.
Where a debit occurs after revocation, compare the revocation timestamp with the debit presentation and raise one structured dispute.
Identify the regulated entity, transaction or loan account, date, amount, contractual document and exact failure. Review merchant, mandate and action together. A failed transaction, authorised mistake, unauthorised fraud, merchant dispute, credit-report error and lawful account freeze require different remedies.
Record the event, alert, discovery, first report, complaint number, response and financial impact in date order. Attach only the documents that prove each step. Phone calls can stop urgent harm, but a written acknowledgement creates the escalation record.
Start with the bank, card issuer, lender, credit institution, app or other regulated entity responsible for the service. Use cybercrime or law-enforcement channels for suspected fraud. Use RBI CMS only after the regulated entity process satisfies the Scheme’s timing or rejection condition and the issue is within Ombudsman scope.
Before treating the case as closed, verify the actual bank statement, loan ledger, credit report, account status or merchant refund rather than relying only on a ticket message. Record who confirmed the financial outcome, the date, remaining open amount and the next escalation deadline. This final check prevents a complaint from being marked resolved while the money, lien, overdue status or credit record remains unchanged.
Banking disputes are resolved through classification, speed, written evidence and the correct escalation route. No legitimate bank, regulator or recovery process requires disclosure of an OTP, UPI PIN or remote-control access.
Use the current official instrument, portal or regulator publication before acting. This panel separates the category authority from page-specific references.