Estornos por “Produto vencedor não corresponde à descrição”: Guia do comerciante para 2026

Item Not As Described chargebacks put small businesses in a uniquely frustrating position. A Reddit post by MaxSATX encapsulates this. A customer buys an item in-store with a credit card, and within days, the bank reports that the customer claimed "Item Not As Described." And the funds are refunded. The merchant submitted video evidence of the customer being shown the merchandise, holding it, paying for it, and leaving the store. The bank still sided with the customer, anyway. As the owner put it, "this is theft. It's theft supported by the credit-card and banking system."

That reaction is understandable, but Item Not As Described disputes aren't a loophole that automatically favors cardholders. They're a specific, well-defined chargeback category, with their own rules for what counts as valid evidence and how much time each side has to act. Understanding those rules in advance puts you in an advantageous position the next time a customer tries to have their cake and eat it.

Understanding Item Not As Described Chargeback And Why It Happens

Cardholders file Item Not As Described (INAD) chargebacks when they believe what they received doesn’t match what your store described they’d get. An INAD claim is about accuracy and an expectation gap.

The merchandise arrived, but the customer believes it failed to match its description, was defective, or fell short of the quality they were promised.

The Item Not As Described chargeback reason code does not only cover physical goods. Services and digital or intangible products are also included in the bucket.

You may encounter a dizzying array of synonyms for this issue. They range from casual buyer complaints like 'order not as described' or 'merchandise not as expected,' to marketplace acronyms like PayPal’s 'SNAD,' to technical API codes like Stripe’s product_unacceptable. The terminology shifts constantly depending on whether you are reading a customer email, a developer log, or a bank notice. But they all speak to the same substance: a fundamental gap between what was promised and what actually arrived.

Why The Item Not As Described Category Exists

Card networks built this dispute right alongside fraud and non-delivery because a customer shouldn’t have to eat the cost of a purchase that wasn’t what they were told it was. They shouldn’t have to rely on the merchant’s goodwill to fix expectation gaps.

Visa’s rules make that intent explicit: A merchant’s return policy has no bearing on whether the dispute is valid. A “no returns, no refunds, all sales final” sign doesn’t block a reason code 13.3 claim. The network decided this particular protection is one that buyers keep regardless of what the seller’s terms say.

Nevertheless, the rules also give merchants a related lever. If a cardholder claims they returned the item and the merchant has no record of it, that's absence. No attempted return, exchange, or refused delivery is substantial evidence you can point to when fighting the claim.

Why Item Not As Described Disputes Happen

A handful of recurring situations account for most “Not as Described” chargebacks across networks. These include:

• Mismatch between listing and item. Wrong colors or models, missing features, malfunctioning products, or services that failed to meet advertised expectations are the most common triggers the networks have identified. This is especially common in card-not-present environments, where the customer has only photos, dimensions, or a written description to go on before the item arrives.
• Damage in transit. Even a perfect description will not matter if the parcel arrives dented, cracked, or leaking. The product can be accurately described and still trigger the claim if it’s damaged by the time it reaches the customer.
• Subjective quality disputes. Some claims aren’t about an objective mismatch at all. Some claims are about whether the item met the quality the customer expected. This is harder to settle than a wrong color or a broken part.
• Genuine merchant error. This happens when a wrong item shipped, a stale or outdated product listing, a verbal description at the point of sale that didn’t match what was delivered.
• Friendly fraud. Visa’s own guidance acknowledges that Item Not As Described is a common reason code for friendly fraud chargebacks, as it is easy to make subjective and falsify claims about products arriving in unsatisfactory condition.

That last point is the throughline of the MaxSATX story. The owner’s frustration wasn’t about a defective product or a wrong listing. It was about a chargeback category that, by design, is easy for a customer to invoke and hard for a network to verify on the spot, sitting right next to a card-present sale that doesn’t fit its usual fact pattern at all.

Item Not As Described Code by Card Network

Every card network has its own version of this code. Visa calls it dispute condition 13.3, Not as Described or Defective Merchandise/Services. Mastercard folds it into reason code 4853, its broad cardholder dispute category. American Express calls it reason code C31, “Goods/Services Not as Described.” Discover’s equivalent is reason code RM, Quality Discrepancy, used when the cardholder claims that the goods or services were defective or not as described prior to the transaction.

Visa: Dispute Condition 13.3

Visa’s INAD code lives under Condition 13.3, Not as Described or Defective Merchandise/Services, within its Consumer Disputes category. Visa’s own guidelines describe the claim as covering merchandise or services that did not match the description on the transaction receipt or other documentation presented at the time of purchase, as well as goods that arrived damaged, were misrepresented verbally over the phone, or simply failed to meet the quality the cardholder expected.

Mastercard: Reason Code 4853

Mastercard doesn't carry a standalone "not as described" code the way Visa and Amex do. It's filed under reason code 4853, Mastercard's broad cardholder dispute category covering cancelled subscriptions, addendum charges, no-show hotel fees, and counterfeit merchandise. Within that umbrella, the relevant sub-type is "Goods or Services Were Either Not as Described or Defective."

American Express: Reason Code C31

Amex’s own merchant guide defines reason code C31, “Goods/services not as described,” as triggered when the Card Member claims to have received goods/services that are different from the written description provided at the time of the charge. Amex draws a related but separate code, C32, for goods that arrived damaged or defective. The two are filed under different reason codes even though the underlying customer complaint can look similar.

Discover: Reason Code RM

Discover’s equivalent is reason code RM, Quality Discrepancy, defined as a claim that the goods or services were defective or not as described prior to the transaction. This is distinct from Discover’s RG code, which covers non-receipt rather than a description mismatch. The two are easy to conflate, but they require different evidence when a user files a Discover chargeback.

The table below summarises the INAD codes and timelines by card network:

How To Win An Item Not As Described Chargeback

Winning an INAD dispute comes down to three things:

1. knowing exactly which claim you’re rebutting,
2. having the right evidence that speaks directly to the cardholder’s specific complaint rather than a generic defense,
3. submitting a timely response before the clock runs out.

Here’s how to do each.

Knowing Which Claim You’re Rebutting

Item Not As Described chargebacks arrive as a reason code, not a sentence, and the code tells you what kind of evidence will actually move the needle. Before assembling anything, confirm:

• Which network, which code? Visa 13.3, Mastercard 4853 (not-as-described subtype), Amex C31, or Discover RM. Each has its own evidence standards, expectations, and time limit.
• What specifically the cardholder is alleging. “Not as described,” “defective,” and “counterfeit” sound similar. But they call for different proof. A product mismatch claim needs your original listing; a defect claim needs your inspection or testing records; a counterfeit claim needs third-party authentication, not a product photo.
• Whether this is genuinely INAD, or a different code wearing an INAD costume. A customer who says “it’s not what I ordered” because the wrong item shipped is closer to a fulfillment error than a description mismatch. The distinction matters for which evidence wins the case.

Having The Right Evidence Package Before The Clock Starts

Not every item applies to every dispute. But across networks, a strong INAD dispute response includes a combination of the following:

Proof That The Item Matched Its Description

• The exact product listing, description, or transaction receipt language as it existed at the time of purchase, not the current version of your site.
• Photos or specifications that match what was advertised.
• For verbal or phone sales, include a record of the script or call notes describing the item.

Proof of Condition at Time of Shipment or Sale

• Quality control or inspection records.
• Packaging and shipping method documentation, particularly for damage claims.
• Photos taken before the item left your facility, if you have them.

Proof The Cardholder Accepted The Item As Delivered

• Signed delivery confirmation.
• Any post-purchase communication where the customer didn't raise an issue.
• For card-present sales, anything showing the customer, not just receiving the item, but specifically inspecting the item in accordance with the listing before leaving (video, signed receipt).

Proof of Resolution Attempts, or Their Absence

• If you already offered a replacement, repair, or refund: include documentation that the cardholder agreed to it and received it.
• If the cardholder never contacted you at all, that absence is itself evidence. As stated earlier, Visa’s own guidance allows merchants to show proof that the cardholder never attempted to return or exchange the product as a defense.

A Direct Rebuttal, Not A Form Letter

• Amex’s merchant guide is explicit that the response should include proof refuting the Card Member’s claim that the written description differs from the goods/services received, not a generic denial.
• Address every specific point the cardholder raised. Vague responses that don’t engage the actual claim are a common reason merchants lose otherwise winnable disputes.

Counterfeit Claims Are A Different Fight

If the dispute notice mentions counterfeit goods specifically, you’re not actually defending an Item Not As Described claim anymore. Rather, you’re defending Visa condition 13.4 or its Mastercard equivalent, a separate dispute category with its own evidence bar.

Why does the distinction matter? Because the proof that wins a “not as described” claim (matching listings, delivery confirmation) does nothing for a counterfeit claim. It turns on authenticity, not description accuracy.

For counterfeit disputes, the evidence that actually moves the needle is narrower:

• Documentation from the manufacturer or authorized distributor proving the item’s supply chain.
• Third-party authentication. Visa’s rules specifically contemplate identification by a reliable, professional third party, not just the merchant’s own assertion.
• Purchase invoices from your supplier showing that the item was sourced as genuine.

One useful fact worth highlighting: A counterfeit claim removes the return-policy defense entirely. In both directions, not only does your refund policy not protect you, but the rules also don’t require the cardholder to return the item before disputing it.

Asking a customer to ship back counterfeit goods might raise its own complications. If you’re facing this dispute type, the fight is about proving the supply chain, not about anything in the transaction record itself.

Drafting The Rebuttal Letter

A rebuttal letter isn’t a legal brief. But it should read like one in structure: claim, response, evidence, conclusion. Here’s a workable template:

Re: Chargeback [Case/Reference Number] – Transaction Dated [Date]

We are submitting this response to contest the chargeback filed under [reason code] for the above transaction.

The cardholder’s claim: [State exactly what the cardholder alleged, in their words if available from the dispute notice.]

Our response: [State plainly why the claim doesn’t hold up – e.g., “The item received matched the description provided at checkout in every material respect.”]

Supporting evidence:

1. [Item description / listing as of transaction date] – Exhibit A
2. [Proof of delivery / acceptance] – Exhibit B
3. [Any communication with the cardholder] – Exhibit C
4. [Any other relevant documentation]

Conclusion: Based on the evidence above, we ask that this chargeback be reversed and the transaction amount restored.

Keep each section short and scannable for automation tools the issuer might use to analyse your documentation.

Submitting A Timely Response Before The Clock Runs Out

Networks publish a 20-to-45-day response window. But acquirers compress that internally, sometimes to a matter of few days.

Within that window, evidence must be identified, matched to the right reason code and subtype, formatted to each network's requirements, and submitted correctly. Manual processes are vulnerable at every one of those steps: missed deadlines, mismatched evidence, generic responses, and inconsistent formatting all cause otherwise winnable disputes to fail.

Visa itself has concluded that manual handling at this volume doesn't scale. In 2025, Visa processed 106 million disputes globally. That's a 35% increase since 2019. An IDC research director put it plainly in Visa's own announcement: Institutions that continue to manage disputes through fragmented, manual processes are leaving recoverable revenue on the table. They're absorbing costs that modern workflows could eliminate.

The underlying logic carries over to the merchants’ side of the aisle. A process with a hard deadline, high volume of recurring evidence types, and real cost for getting it wrong is the textbook case for automation, on either side of the dispute.

That's why chargeback automation isn't a workaround to network rules. It's a tool built into the network itself.

How To Prevent Not As Described Disputes

The cheapest INAD dispute is the one that never gets filed. Winning representment matters. It matter a lot. But even won disputes still count against your dispute ratio. Prevention is the only strategy that voids this.

Here are some actionable considerations:

Write Product Descriptions That Close The Gap Before It Opens

Every network traces most legitimate INAD claims back to the same root cause: a gap between what was promised and what shipped.

Visa tells merchants to ensure the description of merchandise or services shown in advertisements, online, and transaction receipts, or used in telephone order-taking scripts, is accurate, complete, and not misleading.

Amex’s own merchant guide says the same thing in its own words: Ensure the exact goods/merchandise or services ordered are provided/sent and provide detailed item descriptions on invoices and in online order confirmations and contracts.

Mastercard and Discover frame it identically on the merchant-prevention side. Mastercard guidance calls for transparent, detailed, and truthful product descriptions on your catalog, website, and marketing materials.

Discover’s guidance for its RM code centers on the same fix: ensure the correct merchandise is shipped and properly packaged products during shipping to avoid damage.

In practice, that means:

• Match the listing to the actual item, not the ideal version. If a product varies by batch, supplier, or finish, say so.
• Specify what’s included and what isn’t. Accessories, batteries, and “as shown” photography props are common, avoidable triggers.
• Update listings the moment anything changes. A description that was accurate at launch but never updated is functionally false for every sale after the change.
• For phone or in-person sales, standardize the verbal description. Visa explicitly includes verbal claims as a valid basis for dispute. A script that overpromises is just as exposed as a misleading product page.

Resolve The Complaint Before It Becomes A Dispute

The goal here is to ensure that customers can always reach you directly and get a real answer. The card networks’ instruction is functionally the same here: speed and ownership at first contact, before the customer’s next call is to the bank.

Visa’s guidelines state: never refer the cardholder to the manufacturer in lieu of attempting to resolve the issue. The merchant of record is considered the liable party/point of contact for resolution. Passing a dissatisfied customer to a third party removes your chance to fix the problem before they escalate.

Amex’s own merchant guide points in the same direction. Its prevention guidance for C31 tells merchants to promptly rectify/resolve claims or grievances raised by Card Members. And to promptly issue credit or replacement, or inform the Card Member of the approximate date you will be issuing credit or providing a replacement, where applicable.

In practice, that means:

• Make it easy to reach a real person. A customer who can’t get a response has no incentive not to escalate.
• Resolve the complaint yourself, every time. Don’t redirect to a manufacturer, supplier, or third party.
• Move fast. Both networks frame this as a “promptly” requirement, not an “eventually.” A slow resolution process functions the same as no resolution process once the customer has already lost patience.
• Put the resolution in writing. If a dispute is filed anyway, a documented offer of refund, replacement, or credit is itself evidence. It’s proof that you tried to resolve the issue before it reached the bank.

Friendly Fraud Is The Part You Can’t Fully Prevent, Only Manage

Not every Item Not As Described or Service Not Described dispute has merit. The same features that make this dispute category useful for consumers (low filing burden, hard-to-disprove quality claims) make it attractive to customers who want their money back after using the product or service.

You can’t eliminate friendly fraud through better descriptions alone. What you can do is make your evidence trail strong by default, so that disputing becomes a worse bet than it looks:

• Keep a dated, archived copy of every product listing as it appeared at the time of sale, not just the current version.
• Document delivery and acceptance whenever the channel allows it.
• Respond to every customer contact in writing, so a “no contact before the chargeback” pattern is documented if it happens.

There’s also a window before any of that evidence even matters: the moment between when a customer contacts their bank and when the dispute formally posts as a chargeback. Catching a complaint in that window, before it becomes a chargeback of record, means it never counts against your dispute ratio at all, regardless of how it would have turned out on representment. Chargeflow Alerts is built for exactly that window, surfacing disputes early enough to resolve them directly with the customer instead of fighting them after the fact.

Another equally high-priority window is the post-payment timeline. Chargeflow Prevent screens every order here, after payment, before fulfillment. It scores each one for dispute risk. The score draws on identity signals: device, IP, and customer history. Based on that score, the order gets approved, verified, or canceled automatically. Suspicious orders go through a "verify" step first. This confirms a real buyer before anything ships. It deters fraud. It also creates evidence to use if a dispute happens anyway.

Item Not As Described Policy: Amazon, eBay, Etsy, and AliExpress

Every major marketplace runs its own buyer-protection program for “not as described” claims. These are separate from the card network rules covered earlier. They're platform policies that decide the case before a bank ever gets involved. A marketplace ruling against the seller can happen even when the underlying card network would have sided differently.

What’s Consistent Across All The Platforms

• The “Contact First” Rule: With the exception of AliExpress (where the “Open Dispute” interface is the primary tool), Amazon, Etsy, and eBay all mandate that a buyer initiates a “Help” request or messaging thread before they can escalate to a platform-level claim.
• The “Short Clock” Enforcement: Every platform forces a rigid response window (48h to 5 days). If a merchant misses this window, the platform system treats silence as an admission of fault and auto-grants the refund.
• The Liability Reality: A platform-level refund debits the merchant’s account immediately. This is not “additional” to a bank chargeback, but rather the preventative measure. Once a platform has forced a refund, the buyer’s underlying card network chargeback right is effectively voided, as the merchant has already made the customer whole.

What’s Platform-Specific

• Amazon's rule is explicit on this point: Filing an Amazon chargeback chargeback disqualifies a buyer from also filing an A-to-Z claim. That means on Amazon, the two remedies are mutually exclusive. A buyer has to pick one.
• Etsy (The $250 Coverage Update): As of May 2026, Etsy’s Purchase Protection explicitly covers the first $250 of an eligible order. If a merchant’s shop remains in “good standing,” Etsy covers the refund up to $250 even if the total order value exceeds that amount. This is a deliberate shift to protect high-value sellers from absorbing entire losses on large, non-compliant claims.
• AliExpress (The Speed of Judgment): Unlike Western marketplaces that emphasize mediation, AliExpress is essentially a “case management” system. They explicitly frame the process as a judgment on evidence (unboxing videos, weight logs). Once they intervene, their 48-to-72-hour turnaround is the fastest forced resolution in the global e-commerce space.
• eBay (The Return Shipping Hook): eBay’s system is unique because it forces a return-shipping mandate. If a seller is found responsible for an INAD claim, eBay automatically generates a return label and bills the seller’s balance, regardless of whether the seller’s listing states “No Returns.”

A Note on “Double Dipping”

Be careful with the term “run independently.” While marketplace debits and bank chargebacks are separate legal frameworks, they do not run concurrently. A buyer cannot successfully “double dip.”

If you have been debited by a marketplace, you should use that proof (the platform transaction record) as your primary evidence if the buyer later tries to initiate a bank chargeback.

Banks recognize prior refunds and will reject the chargeback as a “duplicate dispute” or “resolved transaction.”

Final Thoughts on Item Not As Described Chargeback

Go back to MaxSATX’s story for a moment. The merchant did everything right and still lost. That’s a real grievance. But it’s evidence of a process failure, not a rigged system. Every network puts some burden on cardholders too: limited filing windows, an evidentiary bar that rewards good records, and a rule that the merchant gets first crack at fixing the problem.

Three things matter most. Know which claim you’re fighting. “Not as described,” “defective,” and “counterfeit” need different evidence. Treat the deadline as the real adversary, since acquirers shorten it further than the network publishes. And prevent what you can, because a dispute you never face costs nothing and never touches your ratio.

None of this guarantees a win, or stops bad rulings. But a merchant with the right evidence, filed on time, is in a different position than one hoping a reviewer agrees. That’s precisely the gap Chargeflow is built to close: matching evidence to the claim, beating the real deadline, and catching what it can before a dispute is ever filed.