Why Do Chargebacks Happen?

what rate is considered normal here?

Normal is lower than most direct-response operators want to admit: for US card-not-present ecommerce, aggregated 2025 industry benchmarks put mainstream authorization environments around 85-90% approval, but high-risk nutraceutical merchant category codes sit materially below that range, and dispute tolerance is narrower than refund tolerance. A chargeback is not a complaint score. It is a network-visible reversal record, and once your offer is running paid traffic, every mismatch between the VSL, descriptor, fulfilment, refund flow and rebill timing turns into math your processor can see.

A useful operating baseline is to treat anything approaching 1% as dangerous, even before a formal card-network threshold is crossed.

Visa's VAMP, Visa's monitoring programme for fraud and disputes, moved the practical ceiling lower by joining fraud reports and disputes into one numerator. Per Visa's acquirer monitoring fact sheet, the VAMP Ratio is fraud reports plus disputes divided by settled Visa card-not-present transactions. That matters because a $47 trial-to-subscription offer can look acceptable in refund-rate terms while producing 10.4 fraud and 13.2 cancellation disputes that create a much worse network ratio.

We counted this page against the operator question, not the legal theory: people ask why chargebacks happen because they want to know which operational failure creates the reversal. The answer is usually one of six: the buyer says they did not authorize it, did not receive it, did not get what the VSL implied, cancelled before a rebill, did not receive a promised credit, or recognized neither the descriptor nor the support path.

at what point does a processor act?

A processor acts before the card network forces it, because the acquirer carries portfolio risk and can be fined for the merchant's month. Visa says VAMP took effect on 1 April 2025 and consolidated five prior programmes into one. Visa's own wording is unusually blunt: "collapsing 38 separate remediation processes into one" is the network telling acquirers that scattered exception handling is over.

At merchant level, Visa's Excessive threshold in the U.S., Canada, EU and AP regions was 220bps, or 2.20%, from 1 June 2025, with a minimum 1,500 monthly fraud-plus-dispute count. The same fact sheet says that threshold dropped to 150bps, or 1.50%, on 1 April 2026 for those regions. LAC was already at 150bps, while CEMEA remained at 220bps in the cited material.

Processors often act well before that because their own portfolio thresholds are tighter: acquirer Above Standard starts at 50bps and Excessive at 70bps, with a monthly fraud-plus-dispute count requirement. If your account pushes the processor toward portfolio monitoring, your individual explanation matters less than the arithmetic. That is why companies hate chargebacks: each case can create fees, reserve pressure, underwriting review and future account risk even when the merchant wins the representment.

Mastercard uses a different structure. Per Braintree's Mastercard monitoring documentation, ECM requires both 100-299 Mastercard chargebacks in a month and a 1.50%-2.99% ratio, while HECM requires 300 or more chargebacks and a ratio of 3.00% or higher. The denominator is lagged: chargebacks received this month are divided by sales from the prior month. That lag is easy to miss when a traffic spike looks clean in week one.

what reduces it without killing conversion?

The highest-return fixes reduce confusion before the issuer turns it into a dispute: clear descriptors, cancellation that actually works, visible support, transaction enrichment, refund speed and disciplined retry logic. None of those require burying the offer. They require making the buyer, the issuer and the processor see the same transaction.

This is where many operators argue with the wrong premise: softer billing disclosure does not protect conversion once paid traffic reaches scale. It moves the loss from checkout to disputes, reserves and account review. For a VSL, video sales letter, the practical test is whether a buyer can answer three questions before entering the card: what am I buying, when am I charged again, and how do I stop it? If the page cannot survive those questions, the chargeback rate is not a support problem.

Visa's Merchant Data Standards Manual gives a concrete example of prevention that does not touch the VSL: the merchant name has 25 spaces in authorization and clearing, names longer than 25 characters must be abbreviated rather than merely truncated, and the uniquely identifying part must remain. The same manual permits supplementary language after the merchant name for the first recurring transaction after a trial or promotional period, signalling that the regular subscription price now applies.

Pre-dispute tools help because they stop the chargeback record from forming. Ethoca Consumer Clarity, Mastercard's issuer-side transaction-enrichment tool, and Verifi Order Insight, the Visa-side equivalent, surface order details when the cardholder questions a charge. Industry reporting puts Order Insight deflection around 40-45%, but that needs checking against a primary source before you treat it as a planning number. We could not verify the current primary-source deflection rate; a current Verifi or Mastercard performance study would settle it.

• Use the billing descriptor as a recognition tool, not a legal name dump.
• Put cancellation next to account lookup, support email and order status, because a frustrated buyer chooses the bank.
• Treat a refund issued before dispute creation differently from a representment win after the dispute exists.
• Do not retry Category 1 Visa declines; Visa says the issuer will never approve them.

who pays, and when?

The merchant usually pays first in cash-flow terms, even when another party is legally the seller or when the dispute is later won. A chargeback pulls funds, adds processor fees, can raise reserves, and can still count in monitoring-program math. That is why the question why chargebacks are allowed has a separate answer from who ultimately bears the business loss.

Merchant-of-record platforms do not make the economics disappear. Paddle defines a Merchant of Record as "a legal entity responsible for selling goods or services to an end customer," and its terms separately say Paddle can recover from the vendor the refund or chargeback plus fees and expenses. ClickBank takes the retailer position for digital or physical product purchases and states its fee as "a 7.5% + $1 transaction fee from the total purchase price" before vendor and affiliate splits.

For a direct merchant account, the processor can add per-case chargeback fees, hold a rolling reserve and eventually terminate. PaymentCloud's own guidance cites high-risk processing rates averaging 3.49%-3.95% plus item fees, monthly fees, added PCI, gateway or statement fees, about $20 chargeback fees and rolling reserves of 5%-10%, or 15%+ for higher-risk accounts, held 90-180 days. PaymentCloud also says merchants need a custom rate review, so those are market figures rather than its published quote.

The timing matters more than the label. Refunds usually leave through the merchant's normal balance. Chargebacks remove funds when the dispute is filed. Reserves withhold future settlement before any particular dispute occurs. Monitoring fines arrive after network identification. MATCH, Mastercard's terminated-merchant database, can outlast the account itself because records remain for five years when properly reported by the acquirer.

what does the monitoring programme actually measure?

The monitoring programme measures records, not intent, and that is the part many advertisers get wrong. Visa's VAMP numerator includes TC40 fraud reports and TC15 disputes; the denominator is settled Visa card-not-present transactions. Visa's fact sheet states the VAMP Ratio "excludes disputes resolved through pre-dispute solutions" and separately "excludes TC40 fraud qualified for Compelling Evidence 3.0," subject to data-extract timing.

A TC40 is a Visa fraud report from the issuer. A TC15 is a Visa dispute financial record. A single card-absent complaint can create both legs, which is why Rapid Dispute Resolution can remove the dispute leg for VAMP purposes while not retracting a fraud report the issuer already filed. Compelling Evidence 3.0, Visa's evidence path for proving legitimate prior customer activity, is the tool industry analyses identify for removing the TC40 leg when the issuer accepts it.

Mastercard ECM is simpler but less forgiving in another way: it looks at Mastercard chargebacks received in the current month divided by Mastercard sales from the prior month. That means a bad rebill cohort can punish the month after acquisition volume has already been bought. The operator sees yesterday's ad account results; the network sees last month's denominator. Those clocks rarely line up cleanly.

Enumeration monitoring is a separate Visa measurement for card-testing attacks. Visa defines the Enumeration Ratio as enumerated authorization transactions divided by all authorization transactions, counting approvals and declines, with a 2000bps, or 20%, threshold and a 300,000 transaction-count threshold. If your checkout is being used to test cards, the dispute rate may not be the first signal that reaches the acquirer.

how fast does a bad month show up?

A bad month can show up inside the same monthly monitoring cycle, but the sales month and the chargeback month are not always the same thing. Visa's VAMP uses monthly counts of fraud and disputes against settled card-not-present transactions. Mastercard ECM uses chargebacks received in a given month divided by the prior month's sales, so the problem can surface after the traffic decision that created it.

That delay is why daily internal dashboards need both refund and dispute views. Refunds tell you what buyers are doing with your support path. Chargebacks tell you what buyers are doing through their bank. Early Fraud Warnings, issuer inquiries, Verifi or Ethoca hits, RDR outcomes and refund tickets are leading signals; formal chargebacks and monitoring notices are lagging signals.

We checked the card-brand math because this is where operator folklore usually breaks. A representment win can recover money, but it does not necessarily erase the record that placed the merchant into a programme. A pre-dispute deflection can prevent the record from existing. That distinction is the practical reason chargebacks exist as a consumer-protection mechanism but behave like a merchant-risk score in paid acquisition.

what happens after a threshold is crossed?

After a threshold is crossed, the processor moves from support conversation to risk control: notices, remediation demands, reserve changes, traffic restrictions, fee assessments, MID suspension or termination. Visa VAMP has no warning tier for merchants identified as Excessive. NMI and Merchant Risk Council reporting put VAMP enforcement fees at $4 per fraud or non-fraud dispute transaction at Above Standard and $8 at Excessive.

Mastercard's monthly ECM and HECM fines escalate with time in programme. Month 1 is $0, month 2 is $1,000, month 3 is $1,000 for ECM and $2,000 for HECM, months 4-6 rise to $5,000 and $10,000, and the schedule reaches $100,000 and $200,000 from month 19 onward. Mastercard also adds a $5 Issuer Recovery Assessment for each chargeback above 300 in the month for merchants in the excessive chargeback programme.

The hard ending is termination and possible MATCH reporting. Stripe's MATCH documentation says acquirers and processors, not Mastercard, report terminated merchants within one business day. MATCH reason code 04 covers excessive chargebacks, code 05 covers excessive fraud, and records stay for five years. Removal is limited: error by the reporting processor, or PCI DSS compliance for code 12. Remediating the chargeback problem after a valid excessive-chargeback listing does not create a removal right.

Running multiple merchant IDs is not automatically illegal, and that is the claim many people in this niche flatten too far. Load balancing across disclosed MIDs can be a legitimate high-risk processing feature. The violation is routing one entity's sales through another entity's MID, or hiding the true product, seller or traffic source from the acquirer. Venable describes transaction laundering as one merchant processing for another undisclosed entity through its own MID, which can create card-network and legal exposure.

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, Why Do Chargebacks Exist?, What is Chargeback Process?, Chargeback Guide Mastercard: The Working Method, Why are Chargebacks Legal?, 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.