Dropshipping INR Chargebacks: Winning Without Tracking
Preventing INR chargebacks starts with knowing which dispute you are answering. An item-not-received chargeback is filed under Visa reason code 13.1, and dropshippers see it most. Slow or untracked overseas shipping gives a customer's bank the gap it needs to side with them.
I've built dispute packets on my own stores where the supplier shipped without scan-level tracking. The issuer asks only whether the order arrived, so the fraud evidence most merchants reach for answers nothing.
You can still win one of these without full tracking, and you can tell early when you won't.
Key takeaways
What is an INR chargeback, and why dropshippers get so many?
An item-not-received (INR) chargeback is a dispute a customer files with their bank claiming the order never arrived, and Visa processes it under reason code 13.1. Dropshippers meet this code more than any other, because overseas suppliers ship slowly and often without tracking a merchant can point to.
A bank needs almost nothing to open one. The cardholder says the package never came, no record contradicts them, and the dispute goes through.
Slow shipping is what keeps that story believable. Chinese shipments commonly take 40 to 60 days to arrive, per Dropship.io's shipping data. So "I never got it" holds up for weeks. Every one of those days is a day your customer can call their bank, and that call adds to your chargeback rate.
Code 13.1 accounts for 1.9% of alerts with a recorded reason code in our dataset. That share looks small because we count every merchant we protect, and most don't dropship.
Not every complaint about a missing order gets that far, though. A customer who emails you before calling the bank is a support ticket, and sorting it out there never moves your rate.
Why "just use tracked shipping" doesn't fully solve it
Tracked shipping lowers your 13.1 risk without closing it, because a tracking number proves movement while the code asks about arrival. Two gaps stay open, one in what tracking evidences and one in who picks the shipping method:
- The tracking-vs-delivery-proof gap: A number that never gets a final scan is worth about as much as no number at all.
- Supplier-side shipping choices: Your supplier picks the carrier tier, order by order.
Dropship.io covers the shipping-side fixes, including how to set delivery expectations before the order ships.
The tracking-vs-delivery-proof gap
Card networks want evidence the order reached your customer, and a tracking number shows only that a shipment existed. Chargeflow's dispute guide puts the distinction plainly. Tracking shows movement, and it doesn't show that the order was received by the appropriate contact.
Nothing unusual has to happen for that gap to open. A supplier creates a label, the carrier scans it at origin, the parcel crosses to a domestic handler, and nobody scans it again.
Your dashboard shows a tracking number, and the issuer sees no delivery.
Supplier-side shipping choices you don't fully control
Your supplier decides which shipping tier each order goes out on, so your evidence quality changes order to order without you touching anything. An agent who quoted you a tracked line can ship the cheaper untracked one when stock moves warehouses.
Two orders placed the same afternoon can leave with completely different paperwork behind them.
So go and check what actually shipped. Pull last month's fulfillments from your supplier dashboard and count how many carry a delivery scan.
Whatever that number is, it is how many 13.1 disputes you could defend today. The shipping tier on your invoice won't tell you, and merchants who count come out lower than expected.
What Visa requires for a 13.1 dispute, and what to submit
Visa's 13.1 evidence framework asks for proof of fulfillment and delivery, and Compelling Evidence 3.0 does not apply to it. Each reason code accuses you of a different failure, so each takes its own proof. Evidence built for the wrong code does nothing.
That mismatch is why merchants lose winnable disputes. A 10.4 dispute asks whether the cardholder authorized the charge, and a 13.1 dispute asks whether the order arrived. Same customer, same order, two unrelated questions.
Read the code off your dispute notice before you gather anything. Our reason code lookup names what each one alleges.
Three pieces of the picture follow:
- What code 13.1 alleges, and the evidence that wins it.
- Why Compelling Evidence 3.0 answers a different question.
- The four layers of fulfillment proof, strongest first.
1. Reason code 13.1: what it alleges
Code 13.1 alleges the customer paid and received nothing, so it's won with fulfillment and delivery evidence tied to the disputed order. In Visa's eyes the strongest form of that evidence is carrier tracking showing a confirmed delivered status. A signature or a delivery photo makes it stronger still.
Match every document to the specific transaction. An order number, the address the customer typed, and dates that match will do more than volume.
Our rebuttal letter guide covers how to assemble the letter that carries this packet.
2. Why Compelling Evidence 3.0 does not apply
Compelling Evidence 3.0 chiefly answers code 10.4, card-absent fraud, so it proves whether a charge was authorized, and 13.1 asks whether an order arrived. The program lets you cite earlier undisputed transactions on the same card. Those prove the cardholder is the person who bought from you before.
That proof will beat a fraud claim, and it does nothing for a delivery claim. A customer who ordered four times is still owed the fifth order.
Most packets go wrong right here. A merchant reads that Visa runs a program for fighting friendly fraud, builds that packet, and answers a question nobody asked.
3. The Fulfillment Proof Stack, layer by layer
The Fulfillment Proof Stack layers four evidence types in priority order, strongest first, so weaker signals together can stand in for a missing delivery scan. Here is what each layer contributes:
- Order and payment confirmation: Proves the order exists and matches the disputed charge.
- Supplier shipment record: Proves the order was fulfilled, not just paid for.
- Delivery-adjacent signals: Proves the parcel went to the customer's own address.
- Customer communication trail: Proves the customer knew, and when.
This works because the person reviewing your case weighs how well your documents agree. No single substitute is worth a delivery scan alone, but three records agreeing on the order, the address, and the dates tell a story one document can't.
Layer 1: Order and payment confirmation
Start with the order and payment record, because it ties the disputed amount to a real order you can describe. Export the order confirmation from your store. It should show the order number, the items, the amount, and the timestamp, plus the email and address the customer entered.
The person reviewing your case is matching your paperwork against a charge on a statement. When the amount and the date reconcile exactly, everything else you send counts as part of that order.
Layer 2: Supplier shipment record
Add your supplier's own shipment record, the closest thing to a fulfillment receipt when you never touch the parcel. Screenshot the order status page in your supplier dashboard. Keep the order ID, the fulfillment date, the destination address, and any carrier reference in one frame.
Pull it while the order is still recent. Suppliers delete old order detail on their own schedules, and a dispute can land months after you fulfilled. The merchants who win these already had the screenshot before they needed it.
Layer 3: Delivery-adjacent signals
Gather every signal that points at delivery without confirming it, since several together narrow the gap a missing scan leaves. Three are worth pulling on a dropshipped order:
- The Address Verification System (AVS) result from the original transaction, showing the billing address matched.
- Partial tracking, including origin scans, customs clearance, and any handoff event.
- The delivery estimate the customer saw at checkout, with the actual transit time against it.
An AVS match is the quiet one, and it is worth pulling first. It shows that whoever paid also controlled the address the order shipped to, which makes a stranger-took-my-package story harder to tell.
Arrival itself stays unproven. Put that match next to origin scans and a closed transit window, though, and the customer's version becomes the weaker one.
Layer 4: Customer communication trail
Close with dated communication, because a customer who tracked the order in writing is a customer who knew it was coming.
Attach the timestamped email thread, including the order confirmation and the shipping notification with the address. Add any reply where the customer confirmed the address or asked where the parcel was.
A complete packet still loses when a customer disputes in bad faith and the issuer believes them. These four layers improve your odds on a real fulfillment dispute, and they guarantee you nothing.
When you can't win a 13.1 dispute
A dropshipper whose fulfillment can't produce delivery proof keeps losing 13.1 disputes, because the cause is a shipping decision rather than a paperwork gap. You can paper over one missing tracking number. You can't paper over a process that never creates one.
So run that count again. If most of last month's orders shipped without a delivery scan, your losses keep arriving as fast as your supplier ships. Each one costs you the transaction, the goods, and a dispute fee.
Two fixes work, and both happen before the dispute. Move to a tracked shipping tier and price it into the product, or catch the dispute early.
The second one is what we built. Our chargeback alerts tell you while the dispute is still pending, so you can refund the customer and keep the chargeback off your rate.
If you sell on Shopify, Shopify's chargeback process sets the submission deadlines these fixes have to fit inside.
Shipping is one root cause among several, and our chargeback prevention guide covers the rest.
How we sourced our data
The reason-code figure in this article comes from anonymized, aggregated dispute-alert data across merchants enrolled on the Chargeback.io platform, not from industry-wide statistics. The population is our own merchants, and the unit is alerts received.
We counted the alerts carrying the 13.1 reason code and report that as a share of alerts with a recorded code. The same labeled-base rule applies across the site. Networks and processors send us codes unevenly, so these shares describe our dataset rather than the industry's mix.
FAQ
What does INR stand for in a chargeback?
INR stands for "item not received," the shorthand for a customer claiming an order never arrived. In payments it means this dispute type, and the currency-code sense for the Indian rupee doesn't apply.
Can I win a 13.1 dispute with only an order confirmation?
Rarely. An order confirmation proves the order and the charge match, and it says nothing about the fulfillment or delivery that code 13.1 asks about.
Does PayPal handle item-not-received disputes like Visa?
No. PayPal runs its own buyer-protection process with its own evidence rules and deadlines, so a packet built for Visa's 13.1 needs reworking.
Should I stop using untracked shipping methods entirely?
Not necessarily, since the cheapest tier still pays for itself on low-value orders where a full loss costs less than tracking every parcel. Price tracked shipping against your real dispute losses per product, and keep untracked only where the math survives.
