¿Qué es Item-not-received (INR) abuse?

What is INR abuse?

Item-not-received abuse, sometimes called INR fraud, is a false delivery dispute. The order was placed with the real cardholder's own account and card, the package was delivered, but the buyer reports it as missing to claw back the money and keep the item. It is a form of first-party or friendly fraud, because the person committing it is the legitimate account holder, not an outside thief.

The claim can run through two channels: an internal refund request straight to the merchant, or a chargeback filed with the card issuer under a merchandise-not-received reason code. Either way, the buyer's story is hard to disprove, since proving a negative like non-delivery leans on carrier records that are not always precise.

For a fraud team, INR abuse sits in the post-purchase stage. There is no stolen identity or bad card to catch at checkout; the signal only appears later, in refund and dispute behavior, which is why it slips past traditional payment fraud controls.

How an INR claim plays out

A typical abusive claim moves through these stages, from a clean order to a written-off loss:

OrderBuy normally The buyer places a genuine order with their own account and card, so nothing looks wrong at checkout.
ReceiveTake delivery The package is delivered and the buyer keeps it, but plans to report it missing.
ClaimReport it never came A refund request or a not-received chargeback is filed, often just inside the dispute window.
ResolveRefund or replace Lacking hard delivery proof, the merchant refunds or reships, and the buyer walks away with both.

Who is involved?

Who	Their role
The buyer	Files the false non-delivery claim to secure a refund or replacement while keeping the delivered item.
The merchant	Ships the order, fields the claim, and eats the loss plus fees when the dispute cannot be rebutted.
The payment provider or issuer	Runs the chargeback process and often defaults to the cardholder when delivery proof is thin.
The carrier	Holds the tracking and proof-of-delivery data that becomes the merchant's only real evidence.

What it looks like in practice

A customer with a long, clean order history buys three high-value items over a month. Each package shows as delivered to the address on file, with carrier scans confirming it. A few days after the third delivery, the customer opens support tickets on all three, saying none of them ever arrived.

Support issues refunds on the first two without much friction. On the third, an analyst notices the same address filed identical claims under two other accounts last quarter, all with confirmed delivery scans. The pattern, not any single claim, is what exposes the abuse: repeat non-delivery reports against orders the carrier says were delivered.

Why it is dangerous for operators

INR abuse is dangerous because it is invisible at checkout. The transaction is genuine, so every payment-fraud control passes it, and the loss only forms later in the refund and dispute stream. Worse, the dispute rules tilt toward the buyer, so an honest merchant often loses even with tracking in hand, and pays a chargeback fee on top of the refunded goods.

It also scales quietly through repetition. A single false claim looks like ordinary customer service, but the same buyers, addresses, and devices come back again and again once they learn the refund path is soft. Left unmeasured, it blends into legitimate returns and quietly inflates loss rates that get blamed on shipping.

What to watch in the data

Delivered but disputed. A not-received claim against an order with a clean carrier delivery scan to the address on file is the core red flag.
Repeat claimants. The same account, address, or device filing multiple non-delivery reports over time signals a pattern, not bad luck.
Timing near the window edge. Claims filed just before the dispute or return window closes suggest the buyer waited to be sure the item arrived.
High-value, resellable goods. Non-delivery claims cluster on electronics and other easily resold items far more than on low-value orders.
Address linkage. Multiple accounts sharing one delivery address that keeps reporting missing packages points to organized abuse.

Quick questions

How is INR abuse different from real non-delivery?

Real non-delivery means the package genuinely never arrived, from a carrier error, theft, or misdelivery. INR abuse is a false claim on an order that was actually delivered and kept. The distinction lives in delivery proof and the claimant's history.

Is INR abuse the same as friendly fraud?

It is a specific type of friendly, or first-party, fraud. The account holder used their own valid payment method, then disputed a legitimate charge. Non-delivery is just one of the stories used; not-as-described and unauthorized claims are close cousins.

Why do merchants often lose these disputes?

Card rules favor the cardholder, and proving a package arrived can require signed proof of delivery that most shipments do not carry. Without strong evidence, issuers commonly side with the buyer, and the merchant absorbs the refund and the fee.

How can merchants defend against it?

Keep detailed tracking and proof of delivery, require signatures on high-value orders, and track claim behavior per customer, address, and device. Repeat non-delivery claims against delivered orders are strong grounds to challenge or restrict an account.

Does refunding fast make it worse?

It can. Frictionless auto-refunds are great for genuine customers but teach abusers that the path is easy. Balancing quick service for good buyers against extra checks on repeat or high-risk claims is the practical tension operators manage.

What should a team do when it spots the pattern?

Link claims across accounts, addresses, and devices, challenge chargebacks with delivery evidence, and apply friction or holds to repeat offenders. Treat confirmed serial abusers as a first-party fraud problem, not routine customer service.