Money Debited but Kotak Credit Card Bill Unpaid — Is It a Delay, a Reversal, or Fraud?
Credit Cards · Disputes & Fraud · India · Kotak Mahindra Bank
Money Debited but Kotak Credit Card Bill Unpaid — Is It a Delay, a Reversal, or Fraud?
Three things can be true at once: your account was debited, your Kotak card shows the bill unpaid, and nothing has gone wrong. Two other things can also be true: the money is sitting in a reconciliation queue, or someone else spent it. Those five situations look almost identical on a phone screen at 11pm, and they carry completely different deadlines. Getting the diagnosis right in the first hour is worth more than any amount of chasing afterwards.
Quick Summary
A debit without a matching card credit is usually a settlement delay, not a lost payment. Kotak’s help centre states NEFT can take up to 3 working days and a non-Kotak cheque up to 5 working days to reflect. Save the debit entry and the reference number, and do not pay twice inside that window. If the charge is one you did not make, the clock is far shorter: reporting within 3 working days gives you zero liability under RBI’s 2017 circular, and Kotak’s 24-hour fraud line is 1800 209 0000.
Five different problems wear the same name
“Kotak credit card payment issue” is a phrase covering at least five distinct events, and the correct action for one is the wrong action for another. Retrying a payment is sensible when nothing was debited and harmful when something was. Waiting is correct for a NEFT in progress and expensive for an unauthorised charge. Work out which row you are in before you do anything else.
| What happened | Money left your account? | Who owns the fix | Wait before acting | Proof to collect | Statutory clock |
|---|---|---|---|---|---|
| Failed, nothing debited | No | You, on retry | 15 to 30 minutes | Error screen only | None running |
| Failed, but debited | Yes | Payment platform | T plus 5 calendar days | Debit entry, reference | ₹100 per day after that |
| Success, bill unchanged | Yes | Kotak, after the window | Up to 3 or 5 working days | Attested bank statement | 30 days to reply |
| Marked pending | Usually yes | Payment network | 1 to 3 working days | Platform status page | Varies by rail |
| Posted, limit unchanged | Yes | Kotak, if it persists | 24 hours | In-app payment entry | 30 days to reply |
| Charge you did not make | Yes | Kotak, immediately | Do not wait at all | SMS alert, statement | 3 working days to report |
The last row is the one people misfile most often. A charge you do not recognise is not a payment problem and does not belong in the same queue as a slow NEFT. It has its own reporting deadline, its own liability rules, and its own phone number.
What actually happens between your debit and your bill
A card bill payment is not one transaction. It is a chain, and each link runs on its own clock, which is why “payment successful” and “amount due unchanged” can both be accurate at the same moment.
Check the limit, not the bill
Your available credit limit updates at link five. The total amount due updates at link six. If the limit has increased by the amount you paid, the payment has landed and everything else is cosmetic. Checking the wrong number is the single most common reason people conclude a payment has vanished when it has not.
Money debited, bill unpaid: the first hour
Do these in order. Most cases close by step four, and the ones that do not are decided weeks later by the evidence gathered in steps one and two.
- Confirm the debit is a completed debit, not a hold or a pending authorisation. A pending entry is not a payment and can disappear on its own without any intervention.
- Copy the reference number now: the UTR for NEFT, the IMPS reference, or the UPI reference. Nobody at either bank can trace anything without it, and this is the item people most often fail to save.
- Verify the last four digits of the card the payment went to. On a third-party platform, a biller added once with a wrong digit will keep failing quietly on every future payment.
- Check your available credit limit rather than the total amount due, for the reason set out above.
- Identify which settlement window applies to the rail you used. If you are still inside it, stop, set a reminder and do nothing further.
- If the window has expired, call and obtain a complaint reference number before ending the call. A call without a reference number is not a complaint and starts no clock.
Do not pay a second time inside the window
A duplicate does not repair a delayed payment. It creates a credit balance that then needs its own resolution, and under RBI’s Master Direction the issuer needs your explicit consent before adjusting credit above one per cent of your credit limit or ₹5,000, whichever is lower, against your limit. If the due date is genuinely upon you and the first payment is stuck, pay only the minimum amount due through an instant rail to protect your record, then pursue the stuck payment separately.
The deadline that decides everything: unauthorised charges
If the entry on your statement is a purchase you never made, you are no longer dealing with settlement timing. RBI’s circular of 6 July 2017 on limiting customer liability in unauthorised electronic banking transactions sets out a sliding scale, and the only variable you control is how fast you report.
Zero liability
Capped
Board policy
Uphill
Ombudsman
Two features of that circular are worth knowing because banks rarely volunteer them. First, if the loss arises from the bank’s own negligence or a system deficiency, your liability is zero regardless of when you report. Second, when a bank disputes your claim, the burden of proving the transaction was genuine sits with the bank, not with you.
Worked example: what three days are worth
An unauthorised charge of ₹68,000 lands on a card with a limit of ₹6 lakh. Report it on working day 2 and your liability is ₹0; the full ₹68,000 is reversed. Report the same charge on working day 6 and your liability caps at ₹25,000, so the bank absorbs ₹43,000 and you absorb the rest. Report on working day 9 and no statutory cap applies, so the entire ₹68,000 may sit with you depending on the bank’s policy. The difference between day 2 and day 9 is ₹68,000, and the only thing separating them is a phone call.
The five clocks running in a card dispute
Cardholders lose cases they should win because they track the wrong deadline. There are five, they run in parallel, and three of them are the bank’s obligations rather than yours.
Why the card gets declined at checkout
A decline at a merchant is a separate problem from a bill that will not update, though the two often arrive in the same week. Most declines have mundane causes that you can clear yourself in under a minute.
| What you see or suspect | What is actually happening | What to do |
|---|---|---|
| OTP rejected or expired | An older OTP was entered, or the session timed out | Use the most recent OTP only. Never enter one on a link sent to you. |
| Limit looks large, payment fails | Available credit is far below the sanctioned limit | Check available credit, not total limit, before a large purchase. |
| Online usage declined | The e-commerce card control is switched off | Enable domestic online usage in the app, then retry once. |
| International site declines | International usage is disabled by default on many cards | Turn it on for the period you need and switch it off after. |
| Card blocked without warning | A risk rule flagged an unusual pattern | Call the bank. Do not keep retrying, which reinforces the flag. |
| Contactless tap fails | The per-transaction contactless cap was exceeded | Insert the card and use the PIN instead. |
| New card never worked | The card was not activated within 30 days of issuance | RBI requires OTP-based consent to activate it after that. |
| EMI purchase declined | The merchant or amount is outside the EMI programme | Pay in full and convert afterwards if the bank allows it. |
| Repeated failures, one merchant | A merchant category or acquirer-side restriction | Try a different card. The problem is not on your account. |
| A caller offers to fix it | This is the fraud, not the fix | Hang up. Banks never ask for OTP, CVV, PIN or screen sharing. |
Tracking a refund that has not arrived
Reversals are their own category of anxiety, because unlike a payment there is no receipt to hold on to. A refund can be travelling along three different routes, and knowing which one you are on tells you how long to wait before it becomes a complaint.
An automatic reversal of a failed transaction is the fastest and the most rule-bound. Under RBI’s turnaround-time framework a failed card payment at a point of sale or on e-commerce, where you were debited but the merchant never received confirmation, must be reversed within five calendar days of the transaction date. Miss that and the issuer owes ₹100 for every additional day. Calendar days, not working days, so weekends do not pause the count.
A merchant refund is slower and outside the bank’s control. The merchant initiates it, the acquirer processes it, and only then does it post to your card. Chasing your bank on day three of a merchant refund achieves nothing, because your bank has not received anything to post. Chase the merchant for the acquirer reference number first, then give it to the bank if the credit still does not appear.
A dispute-driven credit is the third route, and it is the one with real teeth. When you have reported an unauthorised transaction, the bank’s obligation to credit you within ten working days is not conditional on the investigation finishing. It is a provisional credit while the facts are established, value dated so no interest is lost. If it has not arrived by the eleventh working day, that omission is itself worth putting in writing, because it strengthens everything that follows.
When not to wait at all
Most of this article is an argument for patience. These are the exceptions, where the settlement window is irrelevant and delay costs you money or rights.
- A charge appears that you do not recognise, or you receive an OTP for a purchase you never started. The three-working-day clock is already running.
- Your account was debited more than once for the same bill, whether by your own retry or by a system fault.
- The payment platform shows no traceable transaction reference at all, which means nobody downstream can locate the money.
- Your card is blocked without explanation, or a new payee or biller you did not add has appeared on your account.
- Someone calls offering to resolve the issue and asks you to install an application or share your screen.
- A refund the platform promised has passed its own stated date with no credit and no explanation.
- Support cannot or will not give you a written complaint reference number.
In each of those cases the useful instruction to the bank is not “why is this delayed” but “please trace this reference and confirm the status in writing”. A trace request creates a specific task with a specific answer. A general grievance creates a ticket that can be closed with a general reply.
A complaint that actually gets traced
Support teams cannot investigate a sentence. They can investigate a reference number. The difference between a case closed in three days and one closed in six weeks is almost entirely the quality of the first message.
Use this structure, in writing
Subject: Credit card bill payment debited but not reflected, card ending 1234. Body: I paid ₹[amount] toward my Kotak credit card ending [last four digits] on [date] at [time] through [channel]. The amount was debited from my [bank] account but has not reflected on the card. Transaction reference: [UTR or reference]. Please trace the transaction, confirm its status, and ensure no late payment charge or adverse credit bureau reporting applies while this is under review. The debit proof is attached. Please share a complaint reference number.
That last sentence matters more than the rest. The 30-day period the issuer has to respond runs from the date of your complaint, and without a reference number there is no agreed start date. The request to hold adverse bureau reporting matters too, because a payment held up in reconciliation can otherwise be reported as overdue while you are still waiting.
Kotak’s help centre is specific about what it wants when a payment from a non-Kotak account has not been credited: a clear scanned copy of the bank statement showing your name, the bank name, the account number, the IFSC code and the debit entry, along with the payment mode and reference number. Attach it with the first message rather than waiting to be asked.
The escalation ladder
Scale gives some comfort here. The RBI’s Annual Report of the Ombudsman Scheme for 2024-25 recorded 13,34,244 complaints, up 13.55 per cent, with credit cards the second-largest category at 20.04 per cent. The Reserve Bank also recovered ₹7.18 crore from 31 banks whose grievance handling it found inadequate. Complaints of this kind are routine, and the machinery for them is real.
Nine habits that end the problem for good
Frequently asked questions
Money was debited but my Kotak credit card bill is still unpaid. What should I do?
Identify the rail first. Kotak’s help centre states NEFT can take up to three working days and a non-Kotak cheque up to five, so the payment may be perfectly valid and simply in transit. Save the debit entry and the reference number, check your available credit limit rather than the total due, and do not pay again inside that window. If it has expired, raise a written complaint with the bank statement attached.
How quickly must I report a fraudulent charge on my card?
Within three working days of receiving the bank’s communication about the transaction. Under RBI’s circular of 6 July 2017, reporting inside that window in a third-party breach gives you zero liability. Between the fourth and seventh working day your liability is capped, and beyond seven working days there is no statutory cap and the bank’s board-approved policy applies.
What is the Kotak number for reporting an unauthorised transaction?
Kotak’s help centre lists 1800 209 0000 as its 24-hour helpline for reporting fraud and blocking cards and other channels, with 1800 4100 as the general phone banking line. Use only numbers printed on the card, in the app or on the bank’s own website. Searching the web for a helpline number is itself a well-known fraud vector.
Do I have to bear the loss if I get a refund only after weeks?
Not while the dispute is open. For an unauthorised transaction, the bank must credit the disputed amount to your account within 10 working days of your notification, value dated so you lose no interest, and it cannot wait for an insurance settlement first. The final question of liability must then be resolved within 90 days of the date you reported it.
My card was declined even though I have a large credit limit. Why?
Because the sanctioned limit and the available credit limit are different numbers. Recent purchases, EMI conversions, pending authorisations, cash withdrawals and an unpaid statement all reduce what is available. A card with a one lakh rupee limit can easily have only a few thousand rupees free. Check the available figure in the app before any large transaction.
Can an OTP be used to reverse a transaction or get a refund?
No. An OTP authorises a payment; it never reverses one. Anyone telephoning to say they need an OTP, your CVV, your PIN or screen-sharing access to process a refund is attempting fraud, whatever they claim to represent. End the call and report it on the bank’s own published number rather than any number the caller gives you.
Should I pay again if the due date is tomorrow and the payment is stuck?
Pay only the minimum amount due, through an instant rail, to protect your repayment record, then keep pursuing the stuck payment separately. Paying the full amount twice creates a credit balance, and the issuer needs your explicit consent before adjusting credit above one per cent of your limit or ₹5,000, whichever is lower, against that limit.
What if the delay gets reported to the credit bureaus?
Ask, in your first written complaint, that no adverse bureau reporting be made while the matter is under review. If a report has already gone out and the bank later accepts the delay was not yours, ask specifically for a correction to the bureau record as part of the resolution, not merely a reversal of the late fee. Get that commitment in writing.
When can I take a Kotak card dispute to the RBI Ombudsman?
Once the bank has not replied within 30 days of your written complaint, or has replied in a way you find unsatisfactory. Filing is free through the RBI Complaint Management System portal, with a toll-free helpline on 14448, and you have up to one year. Keep the bank’s complaint reference number, because the Ombudsman will ask for it.
The short version
Diagnose before you act. A debit with no matching card credit is usually settlement lag, and the fix is patience plus a saved reference number, not a second payment. A charge you did not make is a different animal on a much shorter fuse: report it within three working days on 1800 209 0000 and you bear nothing, wait past seven and the statutory protection disappears. Whichever it is, get a complaint reference number, put everything in writing, ask for a hold on adverse bureau reporting, and diarise day 30 for the free escalation to the RBI Ombudsman.
