UPI AutoPay Mandate: How to Stop Silent Recurring Debits

Stopping a subscription inside a merchant app and revoking the bank mandate are related but not always the same action.

What the customer or business should understand

• 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.
• Revocation of a mandate does not necessarily settle amounts already lawfully due under the customer’s contract.

For the connected rule, example or next step, see UPI AutoPay and Mandates: Convenience or Silent Leakage?.

The five-point review

Practical example

How to apply the framework

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.

Dispute workflow

Classify the problem before choosing the remedy

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.

Create one written chronology

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.

Escalate to the correct authority

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.

Implementation checkpoint

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.

Action checklist

• Open the mandate-management section.
• Record the mandate reference.
• Cancel the merchant service.
• Pause or revoke the mandate.
• Save confirmation screenshots and emails.
• Monitor the next scheduled debit date.

Evidence to keep

• Mandate details and UMN
• Merchant terms and cancellation
• Revocation timestamp
• Debit alert and bank statement
• Complaint IDs

Warning signs

Finin2min takeaway