Chargebacks and UPI Disputes in India: A Merchant’s Guide to Timelines, Evidence and Prevention (2026)
Indian merchants deal with two different dispute systems. Card payments follow the chargeback rules of Visa, Mastercard and RuPay, routed through the acquiring bank and payment gateway. UPI payments follow NPCI’s dispute process, which starts inside the customer’s UPI app and runs through banks and NPCI’s back-office system. The stages look similar, but the rules, timelines and decision makers differ.
Most guidance on chargebacks is written for the US or Europe and ignores UPI. This guide explains how both rails work for Indian merchants in 2026, how RBI’s turnaround time rules for failed transactions fit in, which evidence to keep for each dispute reason and how to reduce the number of disputes you receive.
Quick answer: Card chargebacks in India run under card network rules: the customer complains to the issuing bank, the issuer raises a chargeback through the network, and your acquirer or gateway asks you for evidence, usually within two to three business days. UPI disputes start in the customer’s UPI app, move through NPCI’s UDIR and URCS systems, and end at NPCI arbitration if contested. RBI’s 2019 TAT framework is separate: it covers failed transactions, with automatic reversal and Rs 100 a day of compensation from banks. Win disputes with reason-matched evidence and prevent them with clear descriptors, quick refunds and 3D Secure.
What are the two dispute rails for Indian merchants?
A card chargeback and a UPI dispute both end with money moving back to the customer, but they are governed by different bodies.
| Feature | Card chargeback | UPI dispute |
|---|---|---|
| Rule owner | Card network (Visa, Mastercard, RuPay, others) | NPCI operating circulars |
| Where the customer complains | Issuing bank (app, branch, phone) | UPI app or remitting bank, through UDIR |
| How it reaches the merchant | Issuer, network, acquirer, gateway | Remitting bank, NPCI URCS, beneficiary bank, gateway |
| Stages | Retrieval, chargeback, pre-arbitration, arbitration | Complaint, chargeback, pre-arbitration, arbitration |
| Final decision | Card network | NPCI |
| Customer escalation | RBI Integrated Ombudsman Scheme | RBI Integrated Ombudsman Scheme |
The practical difference is speed and evidence. Card networks allow longer windows and have detailed reason codes for fraud, authorisation and processing errors. UPI disputes are mostly about money moving correctly, refunds and delivery, and NPCI has been shortening bank response times.
How do card chargebacks work, stage by stage?
A cardholder disputes a charge with their bank. The issuer checks it against network rules and, if it qualifies, raises a chargeback. The acquirer passes it to your payment gateway or payment aggregator, which asks you to accept or contest.
| Stage | What happens | Typical window |
|---|---|---|
| Retrieval or inquiry | Issuer asks for transaction details before a formal chargeback | Gateways commonly give merchants about 3 days |
| Chargeback | Issuer raises a formal dispute with a reason code | Customers can usually dispute up to 120 days from the transaction; gateways often ask merchants to respond within 2 to 3 business days |
| Representment | Acquirer sends your evidence to the issuer | Mastercard says network deadlines are typically 20 to 45 days after the merchant is notified |
| Pre-arbitration | Issuer rejects your evidence and disputes again | Gateways often allow about 2 days; Mastercard moves funds if the acquirer takes no action for 30 calendar days |
| Arbitration | Network reviews the case and rules; the loser pays a fee | Network-defined; fees are significant |
These windows are network-defined and change with rule updates, so treat your gateway’s deadline as the one that matters. Gateways set short internal deadlines because they need time to package your evidence before the network’s cut-off. Missing that deadline usually means losing automatically.
Escalation is expensive. One Indian gateway’spublished dispute fee tablelisted arbitration fees of USD 600 for Visa, USD 675 for Mastercard and Rs 3,000 for RuPay in October 2026, charged to the losing side. Many gateways also deduct the disputed amount from your settlements when the dispute opens and return it if you win.
How do UPI disputes work through UDIR and NPCI?
RBI’s circular of 6 August 2020 required payment system operators to set up online dispute resolution (ODR) by 1 January 2021, starting with failed transactions, and required UPI apps to accept complaints in the app. NPCI’s implementation is UDIR (Unified Dispute and Issue Resolution), shown to customers as UPI Help. In 2023, NPCI asked merchant acquirers to support refund, check status and complaint APIs, so refunds are tied to the original transaction.
A merchant (P2M) dispute usually follows this path:
- The customer raises a complaint in their UPI app or with their bank.
- The remitting bank checks the transaction status. If the issue is not resolved, it raises a chargeback in URCS, NPCI’s back-office system, against the beneficiary (acquiring) bank.
- The acquiring bank passes it to your gateway, which asks you to refund, accept or contest with evidence.
- If the remitting bank rejects your response, it can raise pre-arbitration, and finally arbitration, where NPCI decides.
The main UPI dispute types, with the reason codes gateways use, are:
| Dispute type | Reason code | Who acts first | Who decides if contested |
|---|---|---|---|
| Debited, but no confirmation at merchant (failed transaction) | 1065 | Acquirer and gateway (reverse or prove success) | NPCI |
| Refund not processed for cancelled or returned goods | 1061 | Merchant (refund proof) | NPCI |
| Goods or services not as described or defective | 1062 | Merchant | NPCI |
| Paid by other means | 1063 | Merchant | NPCI |
| Goods or services not provided | 1064 | Merchant (delivery proof) | NPCI |
| Duplicate or multiple debit | 1084 | Merchant and gateway (logs) | NPCI |
| Charged more than the transaction amount | 1085 | Merchant (invoice, logs) | NPCI |
What changed in UPI dispute rules in 2025 and 2026?
NPCI has changed the chargeback process several times since late 2023. The changes are addressed to banks, but they shape how quickly disputes reach you.
| Effective date | Change |
|---|---|
| December 2023 (OC 184) | Caps of 10 chargebacks per customer in 30 days and 5 per payer and payee pair |
| 15 February 2025 (OC 213) | Chargebacks raised through bulk upload and UDIR are automatically accepted or rejected in the next settlement cycle, based on the transaction credit confirmation (TCC) or return already raised by the beneficiary bank |
| 15 March 2025 (OC 184A) | Fraud chargebacks exempted from the caps |
| 15 July 2025 | Remitting banks can raise good-faith chargebacks for genuine disputes that the caps had auto-declined |
| 1 August 2026 (OC 235) | Beneficiary banks must accept or reject fraud and wrong-credit chargebacks within 15 calendar days, down from 35, or they are deemed accepted |
Two points matter for merchants. First, the February 2025 rule means a refund or credit confirmation already processed through your gateway now counts automatically, which reduces cases where a customer is refunded twice. Second, the August 2026 change gives acquiring banks less time on fraud chargebacks, so expect shorter internal deadlines from your gateway on UPI fraud disputes.
How is RBI’s TAT framework different from a merchant dispute?
RBI’s circular of 20 September 2019 harmonised turnaround times (TAT) and compensation for failed transactions, effective 15 October 2019. A failed transaction is one not completed for reasons not attributable to the customer, such as a communication failure or session time-out. Compensation is paid by the bank, automatically, without the customer having to complain.
| Scenario | Turnaround time | Compensation if late |
|---|---|---|
| UPI payment to merchant: account debited, no confirmation at merchant | Auto-reversal within T+5 days | Rs 100 a day beyond T+5 |
| UPI transfer to a person: debited, beneficiary not credited | Reversal by T+1 day | Rs 100 a day beyond T+1 |
| Card at a POS or online: debited, no confirmation at merchant | Auto-reversal within T+5 days | Rs 100 a day beyond T+5 |
| IMPS: debited, beneficiary not credited | Reversal by T+1 day | Rs 100 a day beyond T+1 |
A merchant dispute is different. When a customer says goods never arrived or were defective, the payment did not fail. It succeeded, and the question is whether the merchant kept its side of the deal. No RBI compensation applies; the outcome depends on evidence under network or NPCI rules.
The overlap is reason code 1065. If your system never confirmed the order, reverse it quickly, because delays create compensation costs for the banks involved and push disputes back to you. If you did fulfil it, keep logs showing the success callback and order creation.
Another rule is coming. RBI’s amended directions on limiting customer liability, issued in June 2026 and effective from 1 January 2027, give customers zero liability for fraud caused by third-party breaches, including at payment aggregators or gateways, if reported within five calendar days. Expect banks to pursue fraud disputes more firmly.
What evidence wins a dispute?
Evidence has to answer the specific reason code. A generic bundle of invoices rarely wins.
| Dispute reason | Evidence to keep |
|---|---|
| Goods or services not received | Delivery proof with date, address and recipient or delivery OTP; tracking history; for digital goods, access or login logs |
| Not as described or defective | Product listing as shown at purchase, photos, quality checks, return policy, messages showing no return was requested |
| Refund not processed | Refund reference (ARN for cards, UPI reference number), date, amount and refund policy |
| Duplicate debit or paid by other means | Logs showing two separate orders, or proof that one payment was refunded |
| Card fraud or unauthorised use | 3D Secure result, ECI value, transaction ID, device and IP data, delivery to the customer’s known address, prior undisputed orders |
| Debited but not confirmed (1065) | Payment success callback, order creation log, or proof of reversal |
| Recurring payment disputes | Mandate registration, pre-debit notifications and cancellation records |
For card-not-present fraud claims, prior history helps. Visa’s Compelling Evidence 3.0 lets merchants link a disputed transaction to at least two earlier undisputed transactions from 120 to 365 days before, using matching identifiers such as device ID, IP address or login. Indian gateway documentation describes a similar requirement for RuPay card-not-present fraud disputes.
Store authentication data with every card order. Domestic card-not-present payments in India need an additional factor of authentication, so the 3D Secure result and ECI value are often your strongest fraud evidence. Our guide toRBI’s authentication directionsexplains the current rules.
Why do merchants lose disputes they should win?
Most lost disputes come down to process rather than merit:
- Missing the gateway deadline, which is often only two or three business days.
- Sending evidence that does not match the reason code.
- Delivery proof without a matching address, signature or OTP.
- Refunding the customer after a chargeback opens, which can mean paying twice. Accept the dispute instead.
- A billing descriptor or UPI payee name the customer does not recognise.
- No authentication or device data stored for card fraud claims.
How do you respond to a dispute?
A consistent routine helps teams meet short deadlines:
- Read the reason code and the gateway’s deadline as soon as the alert arrives. Use dispute webhooks so alerts reach the right person.
- Check whether you have already refunded or reversed the payment.
- Decide whether to accept or contest. For small amounts with weak evidence, accepting avoids escalation fees.
- Collect evidence matched to the reason code, with a one-paragraph summary that explains the timeline.
- Submit before the deadline and record the outcome, so you can see which reasons you lose most.
How can merchants reduce chargebacks and UPI disputes?
Prevention starts with removing reasons for customers to call their bank:
- Clear descriptors. Make sure the name on card statements and the UPI payee name match the brand customers know.
- Refund speed. Publish a refund timeline and meet it. Use API refunds linked to the original transaction, and reverse failed orders quickly.
- Delivery confirmation. Use OTP or signature on delivery for high-value orders, and share tracking.
- 3D Secure. Send full data for card payments to reduce fraud and support liability claims. See our guide to3D Secure 2 and checkout friction.
- Fraud screening. Check velocity, devices and repeat claimants. Our articles onchargeback fraud and friendly fraudandrefund fraudcover abuse patterns.
- Reachable support. Customers who cannot reach you go to their bank instead.
- Monitoring. Track dispute rates by method and reason. International card volumes also fall under network programmes such as Visa’s VAMP, covered in ourcard brand monitoring programsguide. For more general tactics, seehow to reduce chargeback fraud.
UPI-specific fraud such as fake screenshots and collect requests is covered in our guide toUPI fraud prevention for merchants.
Frequently asked questions
1. What is a UPI chargeback?
It is a dispute raised by the customer’s bank against the beneficiary bank through NPCI’s URCS system, asking for money to be returned. For merchants, it usually concerns a failed transaction, a refund not processed, goods not delivered or a duplicate debit.
2. How long does a customer have to raise a card chargeback?
Under most network rules, customers can dispute for up to 120 days from the transaction, and some reasons are measured from the expected delivery date. Check the exact limit for each reason code with your acquirer.
3. How long do merchants get to respond?
Gateways usually ask for evidence within two to three business days for a chargeback and less for later stages. The network allows the acquirer longer, but the gateway deadline is the one you must meet.
4. What is UDIR?
UDIR is NPCI’s Unified Dispute and Issue Resolution framework, the in-app complaint system behind UPI Help. It lets customers raise and track complaints and connects banks and merchant acquirers through APIs.
5. What changed for UPI chargebacks from 15 February 2025?
NPCI began automatically accepting or rejecting chargebacks in the next settlement cycle, based on credit confirmations and returns already raised by the beneficiary bank. This reduces duplicate refunds.
6. Does RBI’s TAT framework apply to disputes about goods not delivered?
No. It covers failed transactions, where the payment did not complete for reasons not attributable to the customer. Delivery and quality disputes follow card network or NPCI dispute rules.
7. Should I refund a customer who has already raised a chargeback?
Usually no. Accept the chargeback through your gateway instead, because a separate refund can lead to the customer being paid twice.
8. Does 3D Secure protect merchants from chargebacks?
It strengthens your position on fraud disputes because the issuer authenticated the cardholder. It does not cover delivery, quality or refund disputes.