Root Cause Diagnosis
An authorization hold is a pre-authorization (auth) approved by the issuer that reduces the available balance or credit limit without a financial posting. The hold clears only when the merchant’s acquirer sends a reversal, void, or a clearing/presentment record that matches the original auth (same card token or PAN, auth code, amount and merchant ID). It stays in place when the merchant never sends that message, when the clearing amount or MID doesn’t match the auth (an “unmatched authorization”), when the transaction failed at the merchant end after the issuer had already approved it, or when a network timeout drops the reversal message. In that case the issuer’s system keeps the hold until its configured expiry, which is issuer- and merchant-category-dependent, commonly a few days for general retail and up to about 30 days for hotels, car rental and fuel.
Quick Fix
Raise an authorization release request with the issuing bank, quoting the transaction identifiers, and ask the merchant for a written void or reversal confirmation in parallel.
Subject: Request to release unreversed authorization hold
Card (last 4): XXXX Network: RuPay / Visa
Merchant: <name> Date/time: <DD-MM-YYYY HH:MM>
Amount blocked: INR <amt> Auth code: <6-char> RRN: <12-digit>
Status: amount blocked/pending, no corresponding settlement and no goods or services received.
Request: release the hold and confirm the reference number of the release.
Send it through the bank’s app under Cards → Service Requests / Dispute a Transaction, or by phone banking. Note the complaint reference number, because the turnaround clocks below start from it.
Step-by-Step Resolution
1. Confirm it is a hold, not a settled debit
Check the statement or app entry:
- Hold: shown as Pending, Blocked, Authorised or Memo debit. Available limit or balance is reduced, but the ledger balance is unchanged.
- Settled debit: a posted entry with a value date, appearing in the ledger and the statement.
The resolution path differs. A hold is released, while a settled debit needs a reversal or chargeback (Steps 5 and 6).
2. Collect the transaction identifiers
Gather these from the SMS, email alert, app entry, or the merchant’s payment receipt:
| Field | Where to find it |
|---|---|
| Date and time | SMS or app |
| Amount and currency | SMS or app |
| Merchant name and MCC or city | Statement narration |
| Auth (approval) code | Merchant receipt, POS slip, some issuer apps |
| RRN (Retrieval Reference Number, 12 digits) | UPI/card receipt, bank’s transaction detail |
| ARN (Acquirer Reference Number, 23 digits) | Assigned on clearing, so it may not exist for an unsettled hold |
| Card last 4 digits | Card |
For a failed online transaction, also capture the merchant order ID and the screenshot of the failure page.
3. Contact the merchant for a void
Ask the merchant to void or reverse the pre-authorization with their acquirer or payment gateway, and to send a written confirmation that includes the auth code, amount and reversal date. For online merchants, use their support ticket system, not a phone call, so there is a timestamped record. Hotels, fuel stations and rental companies can usually release the hold on the POS terminal (a “pre-auth cancel” or “completion with zero amount”).
4. Wait out the standard window, then escalate
Under RBI’s TAT (turnaround time) framework for failed transactions, where the account or card has been debited or blocked but the service wasn’t delivered, the reversal is expected by T+5 working days from the transaction date. Beyond that, the bank must compensate the customer at INR 100 per day of delay, and compensation is meant to be credited without the customer having to claim it. Confirm the current circular text on rbi.org.in because thresholds are revised from time to time.
5. File a formal complaint with the issuing bank
- Submit the complaint in writing (app, net banking, or email to the bank’s grievance address) and keep the reference number.
- Request three things explicitly: release of the hold, the date it will be released, and compensation for delay under the RBI TAT framework.
- If unresolved within the bank’s stated resolution time, escalate to the Nodal Officer and then the Principal Nodal Officer, whose contact details are published on the bank’s website under Contact Us → Grievance Redressal.
6. Raise a chargeback if the amount was actually debited
If the hold converted into a settled debit, or the merchant’s clearing posted without delivery:
- Ask the issuer to file a chargeback through the card network. RuPay disputes go through the NPCI dispute management system, and Visa disputes go through Visa’s dispute resolution framework.
- Provide the merchant’s non-delivery evidence, cancellation proof, or the void confirmation.
- Card networks apply filing deadlines, generally measured in months from the transaction or expected-delivery date (for example, roughly 120 days for Visa and a similar window for RuPay). File early, and confirm the exact deadline with your bank, since it varies by reason code.
7. Escalate to the RBI Ombudsman
If the bank doesn’t resolve the complaint within 30 days, or you’re dissatisfied with its reply, file at cms.rbi.org.in under the RBI Integrated Ombudsman Scheme. Attach:
- The bank’s complaint reference number and its reply (or a note that none arrived)
- The statement extract showing the hold
- The transaction identifiers from Step 2 and the merchant correspondence
The complaint must be against a regulated entity, and it should not be pending before a court or another forum for the same cause.
8. Verify release
Check the available balance or limit against the ledger balance. The hold is released when the two match again and the pending entry disappears. Keep the release reference and the compensation credit (if any) for your records.
Why This Fails for Some Users
- Hold has not expired yet: Holds on hotels, car rentals, fuel and some travel merchants follow longer MCC-specific windows. An issuer may decline a manual release until the timer ends or the merchant clears it.
- Auth code mismatch or missing: Without the auth code or RRN, the issuer’s operations team cannot match your complaint to the correct auth record. Recover it from the merchant’s payment gateway dashboard or invoice.
- Card-on-file tokenisation: After RBI’s tokenisation rules, merchants hold a token, not your PAN. The narration and the token reference may differ from the card number you know, so quote the last 4 digits of the card and the token requestor name if shown.
- Debit card holds on savings accounts: The hold reduces the account’s available balance and the bank may treat it as an ATM/POS memo entry. Some banks handle these through a different queue than credit card disputes, so ask that the request be routed to card operations.
- Recurring mandate or e-mandate pre-debit notifications: A pre-debit hold for a recurring payment may look like an unreversed auth. Check whether it belongs to an active mandate (Cards → Manage Mandates, or the merchant’s subscription page) before disputing.
- Dynamic currency conversion (DCC) or foreign merchants: International auths are converted at clearing, so the hold amount and the final amount can differ. The release may look partial, with the difference held until settlement.
- Multiple auths for one purchase: Some merchants send a fresh auth for each retry, leaving several holds while only one converts to a debit. Ask for a release of every unmatched auth, not just the one you noticed.
- Weekend, holiday and cut-off delays: RBI’s TAT counts working days, and settlement cycles pause on bank holidays. The T+5 period may end later than expected.
- Merchant is unresponsive or insolvent: The acquirer is then the only route. Ask your issuer to raise the case with the acquirer bank directly and to use the network’s dispute channel.
- Payment aggregator disputes: If the merchant used an aggregator, the reversal may sit with the aggregator, not the merchant. Contact the aggregator’s grievance officer, whose details must be published on its site.
- Complaint closed without resolution: Banks sometimes close tickets on a technicality. Reply to the closure in writing, reference the original complaint number, and cite the TAT framework, then escalate under Step 7.