Reembolsos por «artículo no recibido»: la guía más completa para comerciantes en 2026

Item Not as Received (INR) chargebacks are one of eCommerce's most common pain points. They’re common enough that platforms like PayPal have treated them as a first-class dispute category. INR is also among the most frequently manipulated dispute reasons by buyers.

That's why even PayPal's Seller Protection changed. It no longer covers transactions received after January 16, 2024, that result in a card-issuer INR chargeback.

eBay moved the opposite way, but only partway. If you ship within handling time with eBay-integrated tracking showing delivery before the due date, you owe no refund. If delivery is only confirmed after you’ve refunded the buyer, and the label came from eBay, eBay reimburses the item cost and clears related negative or neutral feedback. That second case is a clawback, not an upfront exemption. You still pay first.

Neither shift makes Item Not Received chargebacks easier to ignore. PayPal's change is pure added exposure. eBay's protection depends on procedural work, an eBay label, on-time shipping, and tracking that holds before it pays off. Card-network chargebacks fall outside both policies and are governed by distinct evidentiary standards.

That's the gap this guide closes: not whether INR still matters, but what documentation each rail requires before a dispute is contested.

Understanding Item Not Received Chargeback: What INR Means as a Dispute Category

Item Not Received is the reason code card networks require buyers to assign when they say they never got the product or service they paid for.

INR is a fulfillment claim, not a quality or authorization claim. The cardholder isn't disputing what they got. They're disputing that they got anything at all, or that they got all of it.

Merchandise or Services Not Received disputes are especially prevalent in retail, digital goods, and ticketing businesses.

Why Item Not Received Disputes Happen

Genuine non-delivery is the obvious driver, but it's worth being specific about the other paths into this code, because each implies a different prevention fix:

1. Logistics failure: Carrier loss, misrouting, and warehouse errors are not unusual. It may be that your team fulfilled correctly, but the shipment didn't complete.
2. Timing mismatch: A cardholder may file a dispute for a transaction before receiving the merchandise or services because the customer grew impatient or there was a non-communicated delay. This resolves itself if delivery completes, but only if you catch it before the chargeback posts.
3. Billing before shipping: Processing payment before product shipping can generate a knee-jerk dispute, even when the order is perfectly on track.
4. Partial fulfillment: This stems from multi-item or service orders where one component is delivered while another isn't. There’s a distinct evidentiary problem for this scenario. And we’ll discuss that in detail in a subsequent section.

Having said that, the biggest driver of INR chargebacks today is friendly fraud. The customer received the order and disputes anyway, sometimes called cyber-shoplifting. This is functionally indistinguishable from genuine non-receipt at the moment the dispute lands; only your fulfillment records tell the two apart.

Item Not Received Reason Codes Across Networks (Visa, Mastercard, Amex, Discover)

Every major card network maintains Item Not Received as a distinct chargeback reason code family, although the naming inconsistency is mostly cosmetic. The reason code shifts by network, but the underlying claim doesn't.

Visa: Dispute Condition 13.1, Under "Consumer Disputes"

Visa's Dispute Management Guidelines for Visa Merchants groups disputes into four categories: Fraud (10.x), Authorization (11.x), Processing Errors (12.x), Consumer Disputes (13.x). It lists 13.1, "Merchandise/Services Not Received," as the first condition under Consumer Disputes.

Services are in the condition's title, not as an addendum. Visa's own dispute-rule clarifications confirm that reason code 13.1 applies literally to service failures, not just goods.

Visa also carves out a sub-rule specific to travel services. For Merchant Category Code 4722 (travel agencies and tour operators), the issuer must wait 30 calendar days from the date the merchant cancelled the service before initiating a 13.1 dispute. This exists precisely because service cancellation timing doesn't map cleanly onto goods-shipment timing.

Mastercard: Folded Into 4853, Sub-Reason "Goods Or Services Not Provided"

Mastercard's current Chargeback Guide files this under "Cardholder Dispute Chargeback (Message Reason Codes 4853/53/4850/4854)". The retired standalone code that existed for this claim, 4855, carried the title "Goods or ServicesNot Provided." Again, they named services directly, not a goods code stretched to cover services informally.

Mastercard's structure means that a services merchant and a goods merchant receiving non-receipt chargebacks see the identical code and sub-reason text.

American Express: Code C08, "Goods/Services Not Received or Only Partially Received"

Services are named in the code title itself, alongside an explicit partial-receipt qualifier that the other three networks don't carry in their code names.

Amex's current Merchant Regulations confirm this is the actual published title, not shorthand. None of the other three networks' code names include comparable partial-receipt language. Visa's 13.1 reads "Merchandise/Services Not Received," Mastercard's sub-reason reads "Goods or Services Not Provided," and Discover's RG reads "Non-Receipt of Goods, Services, or Cash."

Discover: Code Rg, Alongside The Related Rm Code

Discover uses an alphabetic scheme for Discover chargebacks. RG, "Non-Receipt of Goods, Services, or Cash," is Discover's direct equivalent to Visa's 13.1, Mastercard's 4853/4855, and Amex's C08. Discover keeps it as a separate code from RM. That covers quality and description disputes, mirroring Visa's separation of 13.1 from 13.3 rather than Mastercard's consolidated approach.

Fighting Item Not Received Chargeback: Evidence and Representment Standards by Sector

Winning an Item Not Received or Service Not Received chargeback comes down to one thing. Proof of fulfillment.

Every network’s own rules say roughly the same thing: show that the goods shipped, the service happened, or the digital goods were accessed. The evidence that satisfies that requirement changes depending on what you sell.

Retail: Tracking Isn't Proof; Delivery To The Right Contact Is

Tracking shows movement. It doesn’t show that the order was received by the appropriate contact. Visa’s own merchant guidance ties the strongest delivery evidence to verification that happened at checkout, not after.

If you received an AVS positive match “Y” response during authorization, and the billing and shipping addresses match, then submitting proof of the shipping address and signed proof of delivery helps your case. This is a materially stronger position than a bare carrier tracking number.

Timing matters just as much as the delivery record itself.

Extracting and compiling the relevant documentation becomes meaningless if you can't submit within the network time limit. That's why an automated chargeback response pays for itself. The evidence Visa asks for already exists somewhere in your systems. The only real variable left is whether you can extract it and deliver it before the dispute before the clock runs out.

Digital Goods And Subscriptions: The Evidence Is Data, Not Paper

There’s no carrier scan for a download. So, prove access instead of delivery. Provide the device and IP address captured at login. Include the date and time of access, not just purchase information. Match each download to a specific order. Revoke access the moment a chargeback is confirmed.

Visa and Mastercard each reward this with a real mechanism. Visa's Compelling Evidence 3.0 enables merchants to use the IP address from an earlier, undisputed transaction on the same account as evidence for the current dispute. Mastercard's "Digital Goods Download" modifier accepts the cardholder's written confirmation that they registered for electronic delivery, and its "Customer Profile" modifier accepts proof that the disputed transaction came from a known device or IP address.

That evidence must exist before the dispute arrives. Chargeback automation ensures it's already captured and ready, instead of chased down against a 20-day clock.

Ticketing: The Dispute Clock Runs On The Event, Not The Sale

A ticket dispute runs through the same "services not received" mechanics as any other service-INR case. The same card network evidence standard applies.

You need documentation proving the cardholder, or another authorized person, received the merchandise or service as agreed. These can include delivery confirmation of the ticket itself (email, transfer, wallet record), under the same general standard applied to any other undelivered service.

What makes ticketing disputes harder to disprove is that there's a longer gap between sale and fulfillment. A ticket bought in March for an October show creates months during which a cardholder can dispute, forget the purchase, or claim non-receipt before anyone has scanned anything. The evidence standards haven't changed to account for that gap. That means the burden lands entirely on you to produce proof.

How To Prevent Item Not Received Claims

Most INR disputes are preventable. The fix usually lives upstream of the dispute: in billing timing, customer communication, and what gets verified at checkout. Let’s look at the sector-by-sector Item Not Received prevention guidelines as shared by the card networks.

Comercio minorista

Visa’s rules are explicit that card-absent merchants should not deposit a transaction receipt with their acquirer until the related merchandise has shipped. A charge appearing on a cardholder’s statement before delivery invites a dispute.

Furthermore, ensure the customer is aware of the delivery window. Card network rules require card-not-present merchants to disclose the delivery method and tentative date upfront. If that date slips, notify the cardholder in writing of the new expected date.

In addition to these precautionary steps, you should also use chargeback alerts to catch the disputes before they reach the chargeback stage. You can auto-refund matched transactions before they post as chargebacks. That keeps a late shipment from escalating into a formal dispute on your record.

Digital Goods And Subscriptions

Capture access data at the moment it happens, not after a dispute has occurred. Track usage data to demonstrate fulfilment, and revoke access immediately once a chargeback is confirmed. Require account registration at checkout. That's the foundation Mastercard and Visa's evidence modifiers run on.

Watch for the access pattern before it becomes a dispute: a login from a new device right before a chargeback, or a download immediately followed by a non-receipt claim. Catching that pattern at checkout, before fulfillment, prevents the chargeback from ever being filed.

Ticketing

The general service standard applies to preventing event ticketing chargebacks. If the service will be delayed, notify the cardholder in writing of the new expected date. That means flagging schedule changes when they're known, not at the event date.

Deliver the ticket itself promptly after purchase. A confirmed email, transfer, or wallet record at the time of sale is proof that a non-receipt claim will later turn on.

The real risk is the gap between purchase and event. Months of waiting time give a cardholder room to forget the purchase or dispute early. That’s why you need a chargeback management tool that helps make evidence capturing seamless.

Notable Platform Policies on Item Not Received (eBay, PayPal, Poshmark)

Card network rules aren’t the only thing governing INR disputes. Platforms like eBay, PayPal, and Poshmark each run their own buyer-protection program on top of whatever card network processed the payment. They each have their own deadlines and proof standards as well.

Ebay Money Back Guarantee

For sellers, eBay is specific about what tracking must show. It must include the date shipped, the date delivered, and the delivery address from a carrier eBay has integrated.

Orders of $750 or more also need signature confirmation. A stalled tracking number isn’t automatically safe, either. If a package shows no movement for 7 days or more, the seller is expected to refund rather than wait it out. Once a request opens, the seller has 3 business days to respond before either side can ask eBay to step in.

Coverage is automatic. It covers the purchase price and original shipping on eligible purchases, with no extra fee. Buyers can file an eBay chargeback on a missing item starting on the estimated delivery date, up to 30 calendar days after it passes.

PayPal Buyer Protection

A buyer must open an Item Not Received PayPal dispute within 180 days of payment. The catch most sellers miss: once opened, the buyer has to escalate to a formal claim within 20 days, or it auto-closes. Sellers get 10 days to respond once a dispute opens. If you miss it, the case typically goes to the buyer.

Proof of delivery has a specific definition, not just “any tracking number.” It means online-viewable confirmation showing the delivery address (city/state or zip), delivery date, and shipping company. Signature confirmation on $750+ orders was mandatory through January 25, 2026; after that date, it’s recommended but no longer required. With that proof, PayPal may rule for the seller even over a buyer’s claim of non-receipt.

One gap worth highlighting: Unlike eBay, PayPal has no rule treating stalled tracking as automatic grounds for a refund. Delivery is either confirmed or it isn’t. A package stuck in transit for weeks doesn’t trigger any separate obligation.

Note: This defense only works inside PayPal’s process. Seller Protection no longer covers Item Not Received claims that a buyer files as a card-issuer chargeback instead. A buyer can bypass PayPal entirely and dispute through their bank, and airtight delivery proof on PayPal’s side won’t save a seller there.

Poshmark Posh Protect

Poshmark holds funds in escrow rather than releasing them at checkout. Buyers have 72 hours after delivery to open an INR case. If none is opened within 3 days, payment is released to the seller, and the sale is final.

For sellers specifically, a lost package isn’t automatically the seller’s loss. If the item is lost or damaged in transit and the seller uses Poshmark’s own prepaid label, Poshmark covers both sides, refunding the buyer and still paying the seller the sale price. That detail isn’t on Poshmark’s own policy page in those exact words, so treat it as well-corroborated rather than verbatim-confirmed. Sellers using a non-Poshmark label or an off-platform shipment lose that protection entirely.

The table below highlights the platform rules:

How Chargeflow Helps Fight and Prevent Item Not Received Chargeback

None of the rules in this guide is secret. Visa publishes its evidence standards. Mastercard publishes its modifiers. eBay, PayPal, and Poshmark publish their own deadlines. The problem was never information. It's executing under deadline, staying ahead of policy changes, and matching evidence to the right reason code.

An AVS match has to be pulled before day 20 closes on an Amex case. A download log has to exist before Mastercard's "Digital Goods Download" modifier can use it. A delivery address must show city, state, and carrier before PayPal will weigh it over a buyer's claim. Every requirement assumes the data was captured upstream, not assembled after the fact.

That's the gap Chargeflow closes. It connects to the systems already generating this evidence (order management, fulfillment, billing, access logs) and organizes it against the standard each network or platform desires. No generic template. When a dispute can be caught before it posts, Chargeflow's alert tools step in earlier still. Chargeflow Prevent flags habitual filers before they make a habit of you.

The rules don't change because a merchant is busy. The deadlines don't move because evidence is scattered across five systems. Chargeflow exists for the part of this that has nothing to do with knowing the rules and everything to do with moving fast enough to use them.