Dispute, Chargeback, Pre-Arb: The Merchant Map

at what point does a dispute stop being a dispute and become a chargeback?

A dispute becomes a chargeback the instant the cardholder's bank files a TC15 dispute-financial record into the card network, Visa or Mastercard, against your merchant account. Before that filing, the cardholder has only complained to their own bank. After it, you owe the transaction amount back, and the event counts against your ratio whether you eventually win it back or not.

Card networks separate the two by data record, not by feeling. A retrieval request or pre-dispute inquiry generates no TC15 at all: it's the issuer asking you, through a tool like Ethoca Consumer Clarity or Verifi Order Insight, to explain a charge before the cardholder's bank decides whether to escalate. Only escalation creates the chargeback, a distinction worth checking against what actually counts as a chargeback in banking, because the ratio only moves on the second event, never the first. We checked that sequencing against Visa's own dispute-rule-language update rather than take a processor's summary at face value.

The complaint is a phone call; the chargeback is a data record with your name attached.

what is a retrieval request and why does it never hit your ratio?

A retrieval request is the issuer asking for proof of a transaction before anyone files a formal dispute, and it never touches your ratio because no TC15 record exists until a chargeback actually follows.

Two tools carry most of this traffic today. Ethoca Consumer Clarity, a Mastercard solution since Mastercard acquired Ethoca in 2019, surfaces your merchant name, logo, item description, order number, authorization code, IP and device data, and refund policy inside the cardholder's banking app the moment they query a charge. Verifi Order Insight is the Visa-side equivalent, and it doubles as the delivery channel through which Compelling Evidence 3.0 data reaches the issuer.

Visa's own fact sheet defines the VAMP Ratio as '[Count of Fraud (TC40) + Disputes (TC15)] / [Count of Settled Transactions (TC05)]', counted only on card-not-present transactions, per Visa's Acquirer Monitoring Program fact sheet. An inquiry deflected at the Consumer Clarity or Order Insight stage never generates the TC15 half of that equation, so it never reaches the numerator at all.

We could not confirm the widely quoted 40-45% Order Insight deflection rate against a Visa-published number; it circulates only in vendor and consultancy write-ups. What would settle it is a deflection figure Visa or Verifi publishes directly, rather than one reprinted secondhand.

which stages can still be resolved before the debit lands?

Two windows still let you stop the debit before it happens: the pre-dispute inquiry, and, for networks that support it, an automated Rapid Dispute Resolution (RDR) credit issued before the issuer files anything at all. Everything after a chargeback posts is damage control, not prevention.

RDR looks like a save, and for the VAMP ratio it is. We traced its mechanics against Visa's own clarification: when a participating merchant returns a merchant-credit response, Visa suppresses the TC15 that would otherwise post. What it does not do is retract a TC40 fraud report the issuer already filed on the same transaction, since a single card-absent dispute can generate both records, and only an accepted Compelling Evidence 3.0 response removes the fraud leg. Get the sequencing wrong and you can find out what one nutra chargeback really costs you despite having 'resolved' the dispute on paper.

Card-present style liability protection has a narrower footprint than operators assume. Stripe's own documentation states that 'if a cardholder disputes a 3DS payment as fraudulent, the liability typically shifts from you to the card issuer,' per Stripe's 3D Secure documentation, but only for transactions authenticated at the time of sale.

Off-session rebills never get that authentication, so the liability shift never applies to them.

what does each stage cost you in fees, ratio and processor attention?

Each stage escalates the cost in a straight line: no direct fee at the inquiry stage, a flat per-transaction charge once a chargeback posts, and ratio damage that follows you regardless of which stage a case is finally settled at.

NMI, whose gateway processes over $200 billion a year for roughly 300,000 businesses, walks merchants through those figures directly, per NMI's VAMP breakdown, and the Excessive tier's missing warning step is the detail operators miss most: there's no grace period between $4 and $8, just a threshold crossing. That's before processor attention enters the picture. Once an acquirer's own VAMP Ratio crosses 50bps, portfolio-level enforcement applies across every merchant that acquirer processes, which is why a nutra account flagged Excessive tends to get dropped rather than fined into compliance, and why the fuller accounting of what a single filing does to margin is broken out separately in does a chargeback actually cost you.

why do cardholders call it a dispute and issuers call it something else?

They're describing different layers of the same event: the cardholder's word describes what it felt like, the network's word describes the data record, and the reason code underneath describes the legal category the bank filed it under.

Visa's own rulebook gives every filing a numeric identity the cardholder never sees. Dispute Category 10 covers fraud, and its dominant card-not-present code is 10.4, titled 'Other Fraud—Card-Absent Environment' in Visa's dispute rule language update. Category 13 covers everything that isn't alleged fraud: 13.1 for merchandise never received, 13.3 for goods not as described, 13.6 for a credit never processed, 13.7 for cancelled merchandise, and 13.2 specifically for a recurring charge billed after the cardholder says they cancelled.

The cardholder says 'dispute'; the bank's system logs it as TC15, reason code 10.4.

which funnel decisions push a customer from a refund request into a filing?

Cardholders default to filing instead of asking you for a refund when they can't recognize the charge, can't find a working cancellation path, or feel a price changed on them without warning, and all three are decisions made in the funnel long before support ever sees a ticket.

In nutra trial-to-subscription billing, two reason codes carry almost all of the friendly-fraud risk: 10.4, filed when the cardholder simply doesn't recognize the charge, and 13.2, filed specifically for a recurring transaction billed after the cardholder believed they'd cancelled. The other Category 13 codes, 13.1, 13.3, 13.6 and 13.7, more often point at something you actually did wrong: unfulfilled orders, defective product, refunds you never processed. Knowing which bucket a filing lands in is most of the answer to why chargebacks happen on a subscription offer specifically.

Descriptor mismatch does the rest of the damage. Visa's Merchant Data Standards Manual gives you 25 characters for the merchant name field and requires abbreviation, not truncation, when a brand name runs longer, and it specifically permits adding language after the merchant name marking the point where a trial or promotional price ends and the standard subscription price begins. Skip that signal and the cardholder doesn't recognize the second charge as theirs; they don't call you, they call their bank.

A charge nobody recognizes gets disputed, not refunded.

what does the checkout and delivery record show about where filings start?

The record shows most filings start where the paper trail is thinnest: orders with no delivery confirmation, no descriptor match, and nothing available at the inquiry stage for the issuer to hand the cardholder before they escalate.

The fields that determine whether an inquiry resolves quietly or turns into a filing are the same fields your checkout and fulfilment systems already generate. What's missing is usually assembly, not data.

Whether that record exists the moment an inquiry hits your gateway is what chargeback operations work actually is: pulling the same fields before the issuer asks for them, not after.

Where the record is thin, the filing starts.

• Merchant name and logo matching the billing descriptor the cardholder sees
• MCC and item description consistent with what actually shipped
• Order number and authorization code tying the charge to a specific event
• IP and device data captured at checkout
• Refund status and refund policy current at the moment of the query

Quick decision checklist

Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.

Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.

• Start with the TL;DR if you need the direct answer.
• Use the table to compare trade-offs quickly.
• Use the FAQ for answer-engine-ready summaries.
• Use the CTA when the decision requires live VSL and ad examples instead of theory.

Daily Intel's coverage advantage

Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.

This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.

Blackhat, whitehat, and multilingual signal coverage

Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.

The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.

How to use the intelligence responsibly

The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.

A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.

• Model structure, not protected creative assets.
• Separate whitehat durability from blackhat persuasion pressure.
• Compare US English examples against LATAM, European, and other language variants.
• Use transcripts and funnel notes to build original briefs.
• Keep compliance review separate from market research.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

For educational pages, the supporting references should help readers verify search, crawlability, and public ad research context, especially Google helpful content guidance, Google SEO link best practices, and Meta Ad Library. Daily Intel then adds the direct-response interpretation layer so the page explains what the signal means for actual affiliate research decisions.

For deeper evaluation, continue through Daily Intel for offer owners and producers, Can Chargeback Be Cancelled?, Can Chargeback Be Denied?, Can Chargeback Be Reversed?, Chargeback for Defective Product: The Practical Version, and What is a VSL?. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.