›

Failed Recurring Payments in India: UPI AutoPay & eNACH Failure Reasons and Recovery

Failed Recurring Payments in India: UPI AutoPay & eNACH Failure Reasons and Recovery

9 minutes

Written by Varsha J. · Growth Lead

Reviewed by: Operations Team

Published 5 Nov 2026

A payment retry illustration showing recurring payment attempts moving through pending, failed and resolved statuses.

Why do UPI AutoPay and eNACH payments fail? Learn common failure and return codes, how to classify recurring debit issues, when to retry, and how to build a safer payment recovery workflow in India.

A recurring payment fails on its scheduled date. The customer may have enough money in the account, the mandate may appear active, and the collection team may still see a debit failure. In another case, the bank account is debited but the business has not received a final status. Both situations create work for finance and customer support, but they need different responses.


The mistake is to treat every failed instalment as the same problem and automatically try again. A retry can help when the failure is temporary and the payment is confirmed as unsuccessful. It can create a duplicate debit or another complaint when the original attempt is still pending, the mandate has been cancelled, or the customer needs to update their account.


This guide explains common UPI AutoPay and NACH/eNACH failure reasons in India, how to classify them, when a retry may be appropriate, and how to build a payment recovery workflow that is clear for customers and manageable for operations teams.


What is a failed recurring payment?


A recurring payment is a debit scheduled under an authorisation or mandate for a future date. In India, businesses may use UPI AutoPay or NACH mandates, including mandates registered electronically through eNACH, to collect recurring instalments, fees, subscriptions or loan repayments.


A failed recurring payment means the scheduled debit did not complete successfully. The reason may sit with the customer’s account, the mandate, transaction parameters, the bank or payment network, or the systems that send and receive transaction status.


It is important to separate three outcomes: a rejected debit, a technical or processing failure, and a payment whose final status is not yet known. A pending status is not a confirmed failure. The collection system should wait for the final response or an authorised status check before deciding whether another attempt can be made.


UPI AutoPay vs eNACH: why failure handling differs


UPI AutoPay uses a UPI mandate and the customer’s UPI app and bank account journey. eNACH uses an electronic mandate to authorise recurring debits through the NACH system. Both support scheduled collections, but they do not expose identical status codes, processing steps or operational controls.


Do not map a UPI decline code directly to an NACH return code. Store the original code and description supplied by the bank or payment partner, then map it to an internal category for reporting and action.


eNACH vs UPI AutoPay.


Common reasons UPI AutoPay debits fail


1. Insufficient balance or bank-side account restrictions


The account may not have enough available funds when the mandate is presented. A bank may also decline a debit because of an account restriction, debit limit, transaction-frequency limit or other control. The exact reason should come from the bank or UPI response, not from guesswork.


2. Mandate is inactive, cancelled or no longer valid


The customer may have revoked the mandate, changed the underlying account, or reached the end date of the authorisation. A business should check the current mandate state before trying again. A cancelled or expired mandate normally requires a valid new authorisation, not repeated debit attempts against the old one.


3. Mandate amount or execution limits


A scheduled amount may not match the mandate rules, or a bank or network limit may be exceeded. NPCI’s UPI circular on business declines lists examples such as a transaction-frequency limit being exceeded, a per-transaction limit being exceeded and a bank net-debit-cap limit being exceeded. These are not all customer-balance problems.


4. Pre-debit notification or customer-notification issue


Recurring UPI debits have notification requirements. NPCI’s circular on reducing business declines identifies a UPI AutoPay response where the customer could not be notified. It says the payee PSP should initiate the pre-debit notification API at least 24 hours before the subsequent execution in the specified cases. A collection platform should not treat this as a normal insufficient-funds failure.


5. Technical decline or timeout


A bank or network issue may prevent the transaction from completing or returning a final response within the expected time. NPCI distinguishes technical declines from business declines in its UPI ecosystem reporting. A technical decline should be investigated differently from a customer-induced or account-related business decline.


NPCI’s UPI decline guidance and NPCI’s UPI ecosystem statistics glossary.


Common NACH and eNACH return reasons


NACH debit files return reason codes that help the sponsor bank, destination bank and user institution identify why a debit was not completed. NPCI’s NACH Procedural Guidelines, Version 6, lists ACH debit return reasons and separate reject codes. The following are examples from that document.


Account and balance reasons


Code 1: Account Closed. Code 2: No Such Account. Code 4: Balance Insufficient. Code 5: Not Arranged For. Code 53: Account Inoperative. Code 54: Dormant Account. The response should guide whether the customer needs to update account details, fund the account or contact the bank.


Mandate and instruction reasons


Code 61: Mandate Cancelled. Code 14: Mandate Expired. Code 8: Mandate Not Received. Code 12: Mismatch in mandate frequency. Code 15: Incorrect amount or mismatch between the mandate and transaction. These are not routine temporary declines. Check the mandate record and correct the underlying issue before considering a future debit.


Duplicate and account-control reasons


Code 13 identifies a duplicate transaction already debited under ACH or NACH. Code 6 indicates payment stopped by the drawer. Other codes cover payment stopped under a court order, an account blocked or frozen, and account limits. Do not re-present a debit simply because the first attempt appears as an exception in an internal dashboard.


The same NPCI document lists reject codes, including an invalid UMRN or inactive mandate and cases where a debit is not valid for the mandate. A rejected instruction should be corrected at the mandate or file level rather than treated as a successful retry opportunity.


NPCI’s NACH Procedural Guidelines, Version 6 for the ACH debit return and reject-code tables. The code labels shown in a bank or sponsor-bank report should be retained exactly as received.


How to decide whether a failed payment should be retried


The right question is not simply whether a debit failed. It is whether the system has a final failed status, whether the mandate remains valid, whether the reason is correctable, and whether another attempt is permitted under the applicable payment and customer-notification rules.


Retry may be considered after a confirmed temporary failure


For a confirmed balance-related decline, a future attempt may be considered after the customer has had a reasonable opportunity to fund the account and after checking the bank or network’s permitted processing rules. The business should communicate the intended next attempt and avoid surprising the customer.


Fix the mandate before another attempt


For a cancelled, expired, inactive or missing mandate, a retry against the same authorisation is not the fix. Ask the customer to complete the required mandate update or fresh authorisation, and wait for its confirmed active status before scheduling another debit.


Do not retry an uncertain transaction


If the status is pending, timed out or inconsistent between systems, first query the bank or payment provider for the final status. A second debit may create a duplicate if the first transaction later confirms as successful. Keep the original transaction reference linked to the investigation.


Avoid repeated attempts with no new information


A retry policy should not resubmit the same debit several times in quick succession. Repeated attempts can increase customer friction, bank declines and support tickets without changing the underlying cause. Set a maximum number of attempts and a stop condition for every failure category.


Build a failure-classification and recovery workflow


A reliable workflow connects the scheduled instalment, the mandate, the debit attempt and the customer communication. It should record a clear reason and choose the next action instead of putting every failure into one generic retry queue.


  1. 1. Identify the scheduled debit. Load the customer or account reference, mandate ID or UMRN, amount, due date, payment rail and the original instruction ID.

  2. 2. Receive and store the final transaction response. Preserve the raw status, response or return code, description, bank reference and timestamp. Do not overwrite the raw response with a simplified label.

  3. 3. Classify the outcome. Use categories such as balance-related, account-related, mandate-related, limit-related, technical, duplicate or pending/unknown.

  4. 4. Check mandate state and transaction history. Confirm the mandate is active, the amount and frequency are valid, and the same instalment has not already been debited.

  5. 5. Select the next action. This may be a customer reminder, account or mandate update, support ticket, bank status enquiry, or an eligible future retry.

  6. 6. Apply notification and retry controls. Follow the relevant pre-debit notification requirements, retry policy, customer preferences and any bank or network constraints.

  7. 7. Update the collection ledger. Record the outcome, next action, owner, next review date and final payment status.

  8. 8. Stop collection activity when resolved. A confirmed payment, mandate cancellation, dispute or customer instruction should trigger the relevant suppression or escalation rule.


Customer communication: what should happen after a debit fails?


A useful message explains that the scheduled debit was unsuccessful, states the next step and gives the customer a route to get help. It should not disclose sensitive information to an unauthorised person or imply that a payment succeeded when it did not.


For a balance-related decline, a neutral message could say: “Your scheduled instalment could not be collected today. Please check your account balance and contact us if you need help. We will confirm any further debit attempt before it is scheduled.”


For a mandate issue, explain that the authorisation needs attention and share the approved steps to update or register it again. For a pending transaction, tell the customer that the payment status is being checked and that they should not pay again until the outcome is confirmed.


Offer an accessible support route. Some customers may need to change their bank account, understand the return reason or dispute a debit. A human team should handle complaints, hardship requests and cases where the system cannot safely determine the next action.


RBI timelines for failed transactions are not retry schedules


RBI’s 20 September 2019 circular on failed-transaction turnaround time sets outer limits for specified cases where a transaction has failed. For UPI funds transfers where the payer is debited but the beneficiary is not credited, the circular specifies auto-reversal by T+1 day. For UPI merchant payments where the payer is debited but the merchant does not receive transaction confirmation, it specifies auto-reversal within T+5 days, with compensation for delay beyond the applicable timeline.


The circular also covers specified NACH cases, including delay in crediting a beneficiary or reversing an amount. These are failed-transaction resolution rules. They should not be interpreted as a general permission to retry a recurring mandate after one or five days, nor as the merchant’s settlement timetable.


For recurring collection operations, keep failed mandate execution, a pending or uncertain transaction, a reversal, and a merchant settlement delay as separate statuses. Each has a different owner and next action.


RBI’s circular on turnaround time and compensation for failed transactions.


What should a dunning management system track?


Dunning is the organised process of following up when a payment cannot be collected. For recurring payments in India, it should combine accurate transaction status, customer communication and controlled recovery actions. It should not be a sequence of automatic retries without context.


  • Scheduled amount, due date, instalment number and customer or account reference.

  • Mandate type, mandate ID or UMRN, current status, validity dates and permitted amount or frequency.

  • Original payment instruction ID and unique transaction reference.

  • Raw UPI response code or NACH return code, as well as an internal failure category.

  • Attempt count, last attempt time, notification status and next eligible action.

  • Customer contact preference, communication delivery status and callback request.

  • Manual review notes, dispute status, assigned owner and resolution timestamp.

  • Final outcome, including collected, reversed, cancelled, mandate updated or unresolved.


Metrics to improve recurring payment recovery


Measure the process from the initial scheduled debit through to final resolution. A single overall success rate hides where the workflow is breaking.


  • First-attempt success rate: share of scheduled debits collected on the first presentation.

  • Failure rate by rail and reason: UPI AutoPay, NACH/eNACH, balance-related, mandate-related, technical and other categories.

  • Recovery rate: share of initially failed instalments that are ultimately collected within the defined observation period.

  • Time to resolution: time from the first failure to a final collected, reversed, cancelled or closed status.

  • Retry success rate: success of eligible subsequent attempts, split by original failure category.

  • Duplicate and uncertain-status rate: cases where another attempt was made before the first transaction’s final status was known.

  • Customer impact: complaints, opt-outs, callback requests and repeat contacts per failed instalment.


Compare the results by customer segment, bank, payment rail, collection date and failure reason. If one bank or response code contributes a disproportionate share of declines, investigate the pattern with the sponsor bank or payment partner instead of simply increasing retry volume.


How SlashCollect can support failed-payment recovery


SlashCollect is built around recurring collections, payment reminders, tracking and reconciliation. A useful recovery workflow should show the scheduled instalment, its payment rail, the final transaction status, the reason for failure and the next approved action in one place.


Teams can use that visibility to prioritise the cases that need attention, send a relevant reminder, capture a customer response and follow up on exceptions. Automated reminders and AI-assisted calling can support the process, while account disputes, hardship cases and mandate changes remain easy to route to a person.


UPI AutoPay for businesses and AI voice agents for payment reminders.


Frequently asked questions


Why do UPI AutoPay payments fail?


Common causes include insufficient available balance, bank or transaction limits, mandate status issues, customer-notification problems, and technical declines or timeouts. Check the bank or PSP response code before selecting the next action.


What are common NACH return reasons?


NPCI’s NACH ACH debit table includes reasons such as account closed, balance insufficient, not arranged for, payment stopped, account inoperative, mandate cancelled, mandate expired, duplicate transaction and mandate not received. Use the code and description returned for the actual debit.


Can a failed UPI AutoPay debit be retried automatically?


A future attempt may be appropriate for some confirmed temporary failures, but not for every decline. First verify the final status, active mandate, amount and frequency, customer-notification requirements and the applicable bank or network rules. Do not retry a pending transaction.


Should a business retry after an eNACH mandate is cancelled?


No. A cancelled or expired mandate is not a temporary decline. The customer must complete the relevant mandate update or fresh authorisation before a future debit can be scheduled.


What is the difference between a failed debit and a failed transaction reversal?


A failed debit means the scheduled collection was not completed. A failed-transaction reversal concerns money that was debited but did not reach the intended beneficiary or merchant confirmation flow. RBI’s timelines for reversal should not be treated as a retry schedule for mandate execution.


How many times should a business retry a failed recurring payment?


There is no single retry count that suits every payment rail, bank, mandate and failure reason. Define a limited policy with stop conditions, apply the relevant customer-notification and bank rules, and review retry outcomes by reason code.


Conclusion


Failed recurring payments need diagnosis before recovery. UPI AutoPay and NACH/eNACH expose different response and return information, and a balance decline is not the same as an inactive mandate, a duplicate instruction or a technical timeout.


Build a workflow that preserves the original response, checks mandate status, separates pending from failed transactions, sends relevant customer communication and retries only when the outcome and rules permit it. This helps teams recover more payments without creating duplicate debits or unnecessary customer friction.


This article is for general information and operational planning, not legal advice. Exact processing and retry rules may vary by bank, sponsor, PSP, payment rail, mandate type and current operating circulars. Confirm the applicable requirements with your acquiring or sponsor bank and compliance team before changing a live retry policy.

Let's connect to discuss more?

Whether you collect fees, EMIs, subscription payments, memberships, rent or B2B collections, SlashCollect automates the repetitive work behind payment collection.

Connect with our team to automate your payment collections · Get onboarded in 2 hours!

Connect with our team to automate your payment collections · Get onboarded in 2 hours!

Connect with our team to automate your payment
collections · Get onboarded in 2 hours!