IndiaLaw by assureOffice
Commercial-bank credit-card closure: seven working days, outstanding dues and ₹500 daily delay

Commercial-bank credit-card closure: seven working days, outstanding dues and ₹500 daily delay penalty

RBI’s commercial-bank directions distinguish the seven-working-day closure clock from the ₹500-per-calendar-day delay penalty. Keep the request, dues-clearance period, actual closure and compensation calculation in one evidence file.

Reviewed by CA BB Gupta · Chartered Accountant & Company Secretary | 45+ years in corporate matters

Small business owner maintains accounting records

The closure clock and the delay-payment clock use different day concepts

Paragraph 19 of RBI’s current commercial-bank card directions requires a closure request to be honoured within seven working days, subject to all dues being paid. Qualifying delay attracts ₹500 per calendar day until account closure, provided no outstanding amount remains. Do not calculate the closure deadline using seven calendar days or exclude weekends from an already established calendar-day delay period.

Use the current commercial-bank directions

The Reserve Bank of India (Commercial Banks – Credit Cards and Debit Cards: Issuance and Conduct) Directions, 2025 were issued on 28 November 2025 and are displayed as updated on 1 October 2026. This article uses paragraph 19 as checked on 26 October 2026. The document’s defined commercial-bank population excludes Small Finance Banks, Payment Banks and Local Area Banks; it is not a substitute for checking the applicable directions for an NBFC or another issuer type.

Record a real request and an actual closure

Paragraph 19 requires multiple request channels, such as helpline, dedicated email, IVR, a prominent website link, internet banking or mobile application. The issuer must not insist on post or another method that delays receipt. Retain the request acknowledgement and reference number, not merely a draft email or an unsubmitted application screen.

The directions require immediate notification after closure through email, SMS or similar means and suitable reporting to credit information companies. Card blocking, expiry, a zero statement balance and account closure are not interchangeable events. Obtain evidence of the actual closure rather than assuming that a disabled physical card ended the account.

Outstanding dues require an explanation and a clock adjustment

Where payment is outstanding, the issuer must provide details on receipt of the request without waiting for the billing cycle, and advise payment to complete closure. Paragraph 19’s explanation excludes the number of days taken by the cardholder to clear outstanding dues from the prescribed timeline. Retain the statement, communicated dues, payment date and confirmation of clearance so the adjustment can be reproduced.

Do not impose a penalty calculation for a period that fails the no-outstanding condition. Conversely, do not allow an unexplained “pending dues” flag to defeat a supported closure request indefinitely. Reconcile actual amounts and dates and ask the issuer to identify the item and relevant period. The illustrations assume the applicable working-day calendar and excluded intervals are established or expressly hypothetical.

Apply ₹500 to the established eligible calendar-day delay

After establishing the applicable closure endpoint, calculate qualifying delay in calendar days, then multiply by ₹500. Keep any amount already credited as the closure-delay penalty separate from refunds, rewards, disputed transactions or the card’s own credit balance. Deduct an actual penalty credit when reconciling the unpaid remainder; do not claim the same amount twice.

The date example uses a hypothetical Monday–Friday working calendar with no holidays and excludes the request date in counting. This is a transparent arithmetic model, not a statement of the actual bank-holiday calendar. A real case must use the correct working days and any dues-clearance exclusion. Other examples start with an accepted eligible delay count rather than inventing the bank’s calendar.

Close the evidence loop

Keep the request, account statement, outstanding-dues explanation, payment/clearance record, calendar calculation, closure notification and penalty credits together. Use the issuer’s grievance process for unresolved differences. This article does not promise a universal NOC form, calculate finance charges or substitute the rules for unused cards for the customer-requested closure rule.

Six worked illustrations

All facts and amounts below are fictional. Assumptions describe the model, not additional statutory rules.

Illustrative example 1: Timely closure

All dues are cleared and closure occurs within the applicable seven-working-day period. Established eligible delay is zero calendar days. Delay penalty is ₹500 × 0 = ₹0.

Illustrative example 2: Three accepted delay days

The validly established eligible delay after the closure deadline is three calendar days, with no outstanding dues. Penalty is 3 × ₹500 = ₹1,500. A weekend within that accepted interval is not removed merely because the original deadline used working days.

Illustrative example 3: Ten accepted delay days

An eligible delay of ten calendar days gives 10 × ₹500 = ₹5,000. This is a fixed daily calculation, not a percentage of the credit limit or former card balance.

Illustrative example 4: Penalty partly credited

The supported penalty calculation is ₹5,000 and the issuer has already credited ₹2,000 specifically towards that penalty. The unreconciled penalty balance is ₹3,000. A separate card-balance refund must not be silently treated as that penalty credit.

Illustrative example 5: Dues-clearance exclusion affects the deadline

In a stipulated agreed working-day schedule, nine working days have elapsed since receipt, of which three are properly excluded for the cardholder’s dues-clearance period. Counted time is six working days, so this model has not exceeded seven. It makes no penalty claim for a period when the no-outstanding condition fails.

Illustrative example 6: Hypothetical working calendar versus calendar delay

Assume a valid request with no dues is received Monday 1 June 2026, a Monday–Friday working week with no holidays, and start-date exclusion. The seventh working day is Wednesday 10 June. If actual closure is Saturday 13 June and the accepted eligible delay includes 11–13 June, the delay is three calendar days and penalty ₹1,500. The example does not prescribe any real bank’s holiday calendar.

Ten-step verification table

StepActionEvidence
1Identify the issuer’s frameworkApplicable commercial-bank definition or separate issuer directions.
2Retain the closure requestSubmitted channel, acknowledgement and reference.
3Reconcile the dues positionStatement, charges and actual outstanding amounts.
4Obtain prompt dues detailsIssuer communication without waiting for another billing cycle.
5Prove clearance datesPayment and issuer confirmation with excluded interval evidence.
6Build the working-day calendarCorrect calendar and seven-day endpoint.
7Verify actual account closureClosure notification rather than card blocking alone.
8Count eligible calendar delayNo-outstanding condition and documented endpoints.
9Reconcile penalty credits₹500 calculation, paid amount and remaining balance.
10Resolve and preserve the caseIssuer grievance trail and supporting closure/reporting evidence.

Sixteen practitioner FAQs

1. Is the closure deadline seven calendar days?

No. Paragraph 19 uses seven working days.

2. Is the penalty counted only on working days?

No. It specifies ₹500 per calendar day of qualifying delay.

3. Does every card issuer fall under this document?

No. Check the defined commercial-bank population and the separate framework for other issuer types.

4. Can the issuer insist only on postal requests?

Paragraph 19 bars insisting on post or another method causing delay and requires multiple channels.

5. Is a draft request enough to start the evidence trail?

Retain proof of actual submission and receipt, not only a draft.

6. What if dues are outstanding?

The issuer must promptly identify them and advise payment; the timeline excludes the cardholder’s dues-clearance period as stated in the explanation.

7. Must the bank wait for a billing cycle to tell the dues?

No. The explanation says to provide details on receiving the closure request without waiting for completion of the billing cycle.

8. Does a zero balance prove the account is closed?

No. Obtain actual closure evidence.

9. Does blocking a card equal account closure?

Not automatically. Treat the status and closure notification separately.

10. Is the daily amount linked to the old credit limit?

No. The cited closure-delay amount is ₹500 per qualifying calendar day.

11. Can a penalty be assumed while an outstanding amount remains?

The provision contains a no-outstanding condition; establish the relevant facts and eligible interval.

12. Should existing penalty payments be deducted from a claim?

Yes. Reconcile what has specifically been credited towards the penalty.

13. Is a card-balance refund always a penalty payment?

No. Identify the nature of each credit and do not conflate them.

14. Do the examples establish actual Indian bank holidays?

No. The dated example expressly uses a hypothetical calendar; actual cases need the correct working days.

15. Does the direction require notification after closure?

Yes. Paragraph 19 requires immediate notification through email, SMS or similar means and addresses suitable CIC reporting.

16. What should an unresolved complaint include?

Request receipt, dues and clearance evidence, the correct calendar, actual closure, eligible delay calculation and credits already received.

Conclusion

RBI’s commercial-bank directions distinguish the seven-working-day closure clock from the ₹500-per-calendar-day delay penalty. Keep the request, dues-clearance period, actual closure and compensation calculation in one evidence file.

Sources and primary references