Credit Card Fraud: What It Is and How It Works
By Advocate Panchanand Shaw, Bar Council of West Bengal · Published 8 Nov 2026 · Cyber crime
Credit card fraud is the use of a card or its details to obtain money or goods without the cardholder's authority. It is prosecuted as cheating and forgery under the BNS, 2023 and as identity theft or personation under the IT Act, 2000, while the bank claim follows RBI liability rules.
Credit card fraud is the use of a card, or the card's details, to obtain money or goods without the cardholder's authority. In Indian law it is cheating and forgery as much as it is a banking problem: section 318(4) of the Bharatiya Nyaya Sanhita, 2023 covers the dishonest inducement, section 336 and section 340 cover the forged documents and electronic records that support it, and sections 66C and 66D of the Information Technology Act, 2000 cover the identity theft and the personation carried out through a computer resource.
What makes card fraud different from a UPI fraud is where the vulnerability sits. In a UPI payment the customer authenticates with a PIN on their own phone. In a card transaction the merchant authenticates with the card number, the expiry date and the CVV, and often nothing else. That design is convenient, and it is why card fraud can be run at scale from a call centre with no physical card and no contact with the cardholder at all.
What the law treats as credit card fraud
The offence is not defined in one section. It is assembled from several. Section 318(4) of the BNS punishes cheating and dishonestly inducing the delivery of property, with imprisonment up to seven years and a fine, and it applies where the fraudster obtained goods, services or money by deceiving the cardholder or the merchant. Section 336 punishes forgery and section 340 punishes the making of a forged electronic record, which covers the cloned card data and the fabricated authorisation logs. Section 61 covers the conspiracy where a skimming device, a call centre and a cash-out point are operated together.
On the technology side, section 66 of the IT Act covers computer-related offences, section 66C covers identity theft through the dishonest use of another person's unique identification feature, and section 66D covers cheating by personation using a computer resource. Section 66B, which punishes the dishonest receipt of a stolen computer resource, is used against the person who receives the card data or the proceeds. Where the card details were obtained from a merchant's database, section 43A of the IT Act gives the cardholder a compensation claim against a body corporate that failed to implement reasonable security practices.
The procedure is the same as any other financial cyber crime. A complaint goes to 1930 and cybercrime.gov.in, an FIR is registered under section 173 of the Bharatiya Nagarik Suraksha Sanhita, 2023, and if the police refuse, an application under section 175(3) can be made to the Magistrate. Electronic records are admitted under section 63 of the Bharatiya Sakshya Adhiniyam, 2023 with the certificate required by its Schedule.
How the fraud actually runs
Most card fraud follows one of a small number of patterns. Knowing which pattern applies tells you what evidence exists and who is likely to be liable. The patterns differ in whether the card was present, whether the cardholder was contacted, and whether the card data was obtained from the card itself or from a database.
Card-not-present fraud through a phone call
The fraudster calls, claims to be from the bank's fraud team or from a merchant's refund desk, and asks for the card number, expiry date and CVV, or asks the cardholder to read out an OTP. Nothing is hacked. The details are simply given away by a person who has been persuaded that the call is genuine. This is the most common pattern in India and the one that produces the most difficult liability question, because the bank's records will show a successful authentication.
Phishing pages and fake payment links
A message arrives with a link to a page that looks like the bank's site or a merchant's checkout. The page captures the card details and the OTP in real time and forwards them to the fraudster. The cardholder sees an error or a "payment failed" message and tries again, which gives the fraudster a second set of details. The page's URL and the message are the key evidence, and both disappear if the message is deleted.
Skimming and cloning at a terminal
A small device fitted to an ATM or a card reader copies the magnetic stripe data, and a camera or a fake keypad overlay captures the PIN. The cloned card is then used at another terminal. The cardholder usually learns of it from a debit alert at an unusual hour or in an unusual city. This pattern leaves physical evidence at the terminal and is easier to investigate, but the money is often withdrawn before the report is made.
Card data taken from a merchant's database
A merchant or a payment gateway stores card details and is breached. The stolen data is sold and used later across many cards. The cardholder has done nothing wrong and has no contact with the fraudster. Liability in this pattern usually turns on whether the entity that held the data had reasonable security practices, which is where section 43A of the IT Act and the DPDP Act, 2023 become relevant.
The patterns compared
| Pattern | How the details are obtained | What the cardholder first sees |
|---|---|---|
| Phone call impersonation | Details and OTP given by the cardholder | A debit after a call about a refund or a blocked card |
| Phishing link | Fake page captures the card data and OTP | A failed payment followed by a real debit |
| Skimming at a terminal | Card data copied and PIN captured | Cash withdrawal alerts in an unfamiliar location |
| Merchant data breach | Stored card data stolen from a business | Several unfamiliar online charges over weeks |
| Small-value testing | Stolen data tried on low-value merchants | A tiny charge from an unknown merchant |
Each pattern produces a different documentary trail. In a phone call case, the call log and the OTP SMS are central. In a phishing case, the message and the URL are central. In a skimming case, the terminal's location and the bank's ATM logs are central. A complaint that describes the pattern accurately gives the investigator a place to start.
Who bears the loss
The RBI's July 2017 direction sets the framework. Where the fraud arises from a third-party breach and the cardholder is not negligent, and the report is made within three working days, the cardholder's liability is zero. Where the report is made after three but within seven working days, liability is capped at five thousand rupees for basic accounts and ten thousand rupees for other accounts. Beyond seven working days, the bank's policy governs. The bank must provide a provisional credit within ten working days of the complaint and resolve the matter within ninety days.
The difficult word in that framework is "negligent". Sharing an OTP, reading out a CVV, or approving a collect request on the card's linked app is normally treated as negligence, because authentication was completed with the cardholder's cooperation. Where the data was taken without any act by the cardholder, such as a skimming device or a merchant breach, the negligence argument is much weaker. The bank's own logs decide which version is true, so the dispute usually turns on device and authentication data.
There is a second layer where the card was used at a merchant that failed to apply basic checks. Section 43A of the IT Act allows compensation from a body corporate that was negligent in protecting sensitive personal data, and the DPDP Act, 2023 imposes duties on data fiduciaries. These claims are harder than a bank complaint but matter where the loss followed a breach at a business.
What to do if it happens
- Block the card through the app or the bank's hotline and ask for the block reference. Blocking stops further charges and fixes the time of your report.
- Call 1930 and give the card's last four digits, the transaction amounts, the merchant names and the times. Save the reference number.
- Write to the bank's nodal officer the same day, stating that the transactions were not authorised, listing each one, and asking for a chargeback and a provisional credit. Attach the statement and the alerts.
- File on cybercrime.gov.in and keep the acknowledgement. The portal complaint is what routes the matter to the police cyber unit.
- Register an FIR under section 173 of the BNSS if the amount or the pattern justifies it. A written police complaint also supports the bank claim, because it shows the dispute is genuine.
- Preserve the call log, the messages and the OTP SMS without editing. If a phishing link was used, note the URL and the time before the page is taken down.
- Escalate to the RBI Ombudsman under the 2021 Scheme if the bank rejects the claim or does not resolve it within ninety days.
What decides the outcome
The reporting date is the first factor. The three-day and seven-day windows in the RBI direction are counted from the transaction, and a cardholder who notices a charge weeks later has a much weaker claim than one who reports the same day. The second factor is whether the cardholder did anything that completed the authentication. An OTP read out over the phone is the clearest example, and it is also the hardest to argue against, because the bank's system records a successful verification on the registered mobile number.
The third factor is the pattern of the charges. A single large charge in a foreign currency at an unfamiliar merchant is easier to dispute than small charges spread over weeks, which the bank may treat as the cardholder's own spending. The fourth is whether the card was used at a compromised terminal, which the ATM logs can prove. The fifth is the quality of the complaint: a written list of transactions with amounts, times and merchant names is treated very differently from a phone call made a week later.
Mistakes that turn a fraud into a dispute
- Waiting for the statement to arrive before reporting, which pushes the claim past the three-day window.
- Giving the OTP to a caller and then describing the transaction as authorised when the bank calls to verify.
- Deleting the phishing message or the call log before the complaint is filed.
- Filing only a police complaint and never a written claim with the bank, or the reverse.
- Using a "recovery agent" who asks for an upfront fee, which is a second fraud built on the first.
- Ignoring a small unfamiliar charge, which is often the test before a larger one.
One mistake deserves emphasis. A cardholder who is contacted by the bank's genuine fraud team may be asked to confirm whether a charge was authorised. That call is not the same as a call from a fraudster asking for the CVV. Confirming a charge you did not make is fine; giving the CVV or the OTP to anyone who calls is not. The distinction is simple and it decides most cases.
When to involve a lawyer
Most card frauds are resolved through the bank's chargeback process without legal help. A lawyer becomes relevant when the bank alleges negligence and refuses to pay, when the amount is large, when the merchant is identified and a civil claim against the merchant or the gateway is possible, when the cardholder has been named as an accused because the proceeds passed through a linked account, or when a prosecution under section 66D of the IT Act or section 318(4) of the BNS needs to be pushed after the police decline to act.
In Kolkata, card and financial offence cases are commonly listed before the Bankshall Court, bail applications before the City Sessions Court and quashing petitions before the Calcutta High Court. If you are deciding whether to accept the bank's settlement or to pursue the merchant, a cyber crime lawyer in Kolkata can explain what each route gives up. The cyber crime law practice in Kolkata handles both the bank claim and the criminal complaint, and the contact page sets out how to send the documents for a first review.
Need help with a cyber crime matter?
Tell me what happened and I will tell you what to file, where, and by when. First conversation is free.
Call +91-9007000603 WhatsAppFrequently asked questions
What is credit card fraud in simple terms?
Credit card fraud is the use of a card, or its number, expiry date and CVV, to take money, goods or services without the cardholder's authority. In India it is treated as cheating and forgery under sections 318(4), 336 and 340 of the BNS, 2023, and as identity theft or personation under sections 66C and 66D of the IT Act, 2000.
Which law punishes credit card fraud in India?
Section 318(4) of the BNS, 2023 punishes cheating and dishonestly inducing delivery of property, with up to seven years. Sections 336 and 340 cover forgery and forged electronic records, and sections 66C and 66D of the IT Act, 2000 cover identity theft and cheating by personation through a computer resource.
How does card fraud happen without the card being stolen?
The fraudster obtains the number, expiry date and CVV through a phone call, a phishing page or a merchant database breach. Those three details are enough for many online merchants to process a payment, so the physical card never has to leave the cardholder's wallet.
Who is liable for an unauthorised credit card transaction?
Under the RBI's July 2017 direction, liability is zero if the breach was on the bank's or system's side and you report within three working days. It is capped at five thousand or ten thousand rupees if you report within seven working days. Beyond that, the bank's policy applies.
What should I do first after noticing card fraud?
Block the card through the app or the bank's hotline and note the block reference. Then call 1930 and send a written complaint to the bank's nodal officer listing each unauthorised transaction. File on cybercrime.gov.in and keep the acknowledgement for the FIR and the chargeback.
Can I dispute a credit card charge after paying the bill?
You can still raise a chargeback and a written complaint, but paying the bill weakens the argument that the charge was disputed at the time. Report before the payment due date, ask for a provisional credit, and keep the bank's written response for the Ombudsman stage.
Is credit card fraud bailable?
Cheating under section 318(4) of the BNS carries up to seven years and is generally non-bailable, while section 66D of the IT Act carries up to three years. Bail is decided on the amount, the accused's record and the investigation stage under sections 480 and 482 of the BNSS, 2023.
What evidence proves a card was used without my authority?
The bank's authentication logs, the device and IP data, the call log, the phishing message and the OTP delivery record. Where the card was skimmed, the terminal's location and the ATM logs help. Section 63 of the BSA, 2023 requires a certificate for these electronic records.
Information for general guidance only and not legal advice. Provisions cited follow the Information Technology Act 2000, the Bharatiya Nyaya Sanhita 2023 and the Bharatiya Nagarik Suraksha Sanhita 2023.
Related articles
Cyber crime lawyer in your city · Bank account freeze help · Contact