Why are Chargebacks Legal?

why are chargebacks legal: what rate is considered normal here?

A normal chargeback rate depends on the card network math, but for a direct-response operator the practical answer is below 1% and preferably well below it. Visa's VAMP, Visa's monitoring programme for fraud and disputes, tightened the merchant excessive threshold in the U.S. to 150bps, or 1.50%, on 1 April 2026, per Visa's acquirer monitoring fact sheet. Mastercard's ECM, Excessive Chargeback Merchant tier, starts at 100-299 Mastercard chargebacks and a 1.50%-2.99% ratio, according to Braintree's Mastercard programme documentation.

The harder number is not the headline threshold; it is the space before the threshold. A $47 continuity supplement offer running cold traffic can look fine in daily sales reporting while stacking refund complaints, issuer inquiries and first-rebill anger that only becomes visible after the chargeback window opens. That is why why do chargebacks happen is not a theoretical question for media buyers. It is the delayed report card for offer framing, descriptor clarity, cancellation handling and fulfilment.

We checked the legal and network figures in the fact pack against named primary or source-attributed materials dated 2026-08-04, and we did not use any unlisted rate for a threshold, fee or statutory requirement.

at what point does a processor act?

A processor acts before the card network has to act if the account starts threatening its portfolio. That sounds backwards to offer owners, but the processor is the acquiring-side counterparty, and Visa's portfolio thresholds are lower than many merchants expect: 50bps for Above Standard and 70bps for Excessive at acquirer level, with acquirer Above Standard enforcement beginning 1 January 2026.

The processor also sees patterns you may not see in Shopify, CRM exports or affiliate-network dashboards. It sees chargeback count by MID, MID meaning merchant ID, retrievals, refunds, descriptor complaints, authorization behavior, reserve drawdown and whether support is reducing disputes or merely moving them into another reason code. If your traffic team is optimizing only for approved orders, the payments team is watching the tail risk attached to those orders.

Operators consistently report that processors become nervous before formal network placement when a nutra trial or VSL, video sales letter, creates a spike in 10.4 fraud disputes or 13.2 cancelled-recurring disputes. Meta does not decide whether chargebacks are legal, but paid social traffic can create the front-end volume that makes a processor move faster. The processor's question is simple: can this MID be defended, or is it contaminating the book?

• Visa 10.4 is officially 'Other Fraud—Card-Absent Environment', the common CNP fraud dispute path.
• Visa 13.2 is the recurring-billing cancellation dispute most exposed by trial-to-subscription offers.
• MATCH code 04 is Excessive Chargebacks, not a vague high-risk label.
• Multiple MIDs are not automatically illegal; undisclosed routing or laundering is the violation.

what reduces it without killing conversion?

The best reduction comes before a dispute exists: make the buyer recognize the charge, solve cancellation fast and deflect issuer inquiries with order data. The surprising part is that winning representment, the formal post-chargeback evidence response, is usually less valuable for monitoring math than preventing the dispute from becoming a chargeback in the first place.

Visa's fact sheet says the VAMP Ratio "excludes disputes resolved through pre-dispute solutions" and separately excludes qualified Compelling Evidence 3.0 fraud records when timing permits. That matters because RDR, Rapid Dispute Resolution, can suppress the TC15 dispute leg, while accepted Compelling Evidence 3.0 is the tool industry analyses identify for removing the TC40 fraud leg from the VAMP numerator.

Clear descriptors are not cosmetic. Visa's Merchant Data Standards Manual gives 25 spaces for the merchant name and requires longer names to be abbreviated rather than merely truncated, while keeping the uniquely identifying part intact. For the first recurring charge after a trial or promotional period, Visa also permits supplementary wording after the merchant name to signal that the trial or promo ended and regular subscription pricing now applies.

We would spend less attention on heroic chargeback fighting and more on making the first rebill boring. That is the claim many buyers dislike, because representment feels like combat and cancellation UX feels like surrender, but VAMP and ECM count the event before your win rate comforts you. If the buyer recognizes the descriptor, sees the order detail inside the issuer app and can cancel without hunting, you reduce the thing the networks measure.

• Use Verifi Order Insight or Ethoca Consumer Clarity where available, because issuer inquiries deflected before dispute filing do not become TC15 or Mastercard chargebacks.
• Separate fraud, cancellation and fulfilment causes; 10.4, 13.2, 13.1, 13.3, 13.6 and 13.7 do not describe the same failure.
• Keep retry logic inside network rules; Visa Category 1 declines must not be retried, and Categories 2-4 are capped at 15 attempts in 30 days for the same card, amount and currency.

who pays, and when?

The merchant normally pays first, even when the buyer's claim is weak, because the merchant agreement lets the processor debit the account while the dispute runs. That is the commercial answer to why are chargebacks legal: card acceptance is conditional, and the chargeback right is one of the conditions.

Merchant of Record, or MoR, changes the named seller and liability chain but doesn't make the economic loss disappear. Paddle defines a Merchant of Record as "a legal entity responsible for selling goods or services to an end customer" and says that entity manages payments and associated liabilities. But Paddle's own terms also say that when it prevents a chargeback or refunds a buyer, "Paddle is entitled to receive from you" the full refund or chargeback amount plus related fees.

For physical supplement offers, most software MoRs are the wrong bucket. Paddle prohibits physical products; Polar says its MoR service resells digital goods and bars physical products; FastSpring markets digital categories and does not publish a physical-goods fit. ClickBank and Digistore24 are different because their materials cover physical products or reseller sale flows, with ClickBank stating a 7.5% + $1 transaction fee and Digistore24's calculator stating $1 + 7.9% on U.S. sales.

We could not verify ClickBank's widely cited $49.95 vendor activation fee against a ClickBank-published page in the fact pack; a live ClickBank pricing or support page showing that fee would settle it. That uncertainty does not affect the main point: published transaction fees and refund obligations matter more than the label on the checkout footer.

what does the monitoring programme actually measure?

Visa VAMP measures fraud reports plus disputes against settled card-not-present Visa transactions; it is not just a chargeback ratio. Visa's own fact sheet defines the VAMP Ratio as "[Count of Fraud (TC40) + Disputes (TC15)] / [Count of Settled Transactions (TC05)]" for VisaNet card-absent activity.

That numerator is why the same customer complaint can hurt twice if it produces both a TC40 fraud report and a TC15 chargeback. A TC40 is the issuer's fraud report; a TC15 is the dispute financial message. RDR can stop the dispute from counting for VAMP purposes when it resolves pre-dispute, but it does not pull back a TC40 fraud report the issuer already filed.

Mastercard ECM is narrower because it uses chargeback count and a lagged sales denominator: chargebacks received in one month divided by sales transactions processed in the prior month. That lag makes a rising rebill complaint problem look less urgent until the next reporting period lands. Why are chargebacks allowed sits inside that wider framework: the networks allow them because the system assigns a formal path for contested card-not-present payments.

Visa also measures enumeration, meaning automated card-testing attempts, with a 20% Enumeration Ratio threshold and at least 300,000 enumerated authorization transactions. That can catch a different kind of problem from angry subscribers: bot traffic, stolen-card testing or a checkout being used as a card validator.

• Visa VAMP numerator: TC40 fraud reports plus TC15 disputes.
• Visa VAMP denominator: TC05 settled card-not-present transactions.
• Mastercard ECM denominator: prior-month Mastercard sales transactions.
• Enumeration denominator: approved plus declined authorization transactions.

how fast does a bad month show up?

A bad month shows up after the network's reporting cycle, but the commercial pressure can start within days if refunds, disputes and authorization failures spike together. The calendar matters because direct-response teams often judge a campaign by same-week ROAS while disputes follow delivery times, buyer memory and rebill timing.

Visa VAMP took effect on 1 April 2025 and had merchant thresholds under the 1 June 2025 structure before the U.S. merchant excessive threshold dropped to 1.50% on 1 April 2026. Mastercard's ECM ratio is explicitly lagged, so June chargebacks are divided by May sales, per Braintree's Mastercard documentation. That means a scaling decision made in May can be punished numerically in June, after the buyer has already received the product or reached the first recurring charge.

The fastest early warning is not the formal chargeback letter. It is usually a cluster: more issuer inquiries, more refund tickets using the same complaint language, more declined rebills, more support contacts mentioning cancellation, and more processor questions about the offer page. If you wait for the programme notice, your best fixes are already late.

The legal layer moves on its own clock. ROSCA, 15 U.S.C. 8403, still requires clear negative-option terms before billing information, express informed consent before charging and a simple way to stop recurring charges. The FTC's 2024 Click-to-Cancel amendments were vacated by the Eighth Circuit on 8 July 2025, but ROSCA, Section 5 of the FTC Act, state automatic-renewal laws and state UDAP statutes remain active.

• California's amended ARL took effect 1 July 2025 and requires online cancellation through a direct link or click-to-cancel button.
• New York's amended law took effect 5 November 2025 and adds renewal and price-increase notice rules for covered subscriptions.
• Colorado SB25-145 took effect 16 February 2026 and extends auto-renewal protections to business-to-business subscriptions.

what happens after a threshold is crossed?

After a threshold is crossed, the processor can impose reserves, fees, remediation demands, traffic restrictions or termination, and the network programme can add per-event fines. That is why why companies hate chargebacks has a more concrete answer than lost revenue: the dispute becomes a risk file.

For Visa VAMP, NMI and Merchant Risk Council reporting put enforcement fees at $4 per fraud or non-fraud dispute transaction at Above Standard and $8 at Excessive, with no warning tier for merchants identified as Excessive. For Mastercard ECM and HECM, Braintree's documentation lists monthly fine escalation from $0 in month 1 to $100,000/$200,000 in month 19 and beyond, depending on tier and currency, plus a $5 Issuer Recovery Assessment for each chargeback above 300.

MATCH is the long tail. Stripe's MATCH documentation says acquirers and processors, not Mastercard, submit reports after terminating a merchant account; records remain for five years and include principal-owner identifiers where available. MATCH code 04 has a quantitative excessive-chargeback trigger, and removal is sharply limited, which means a new entity formed by the same principal can still be matched during underwriting.

The edge case nobody should dress up as optimization is transaction laundering, also called factoring or undisclosed aggregation. Venable describes it as one merchant processing card transactions for another undisclosed entity through its own MID, and the consequences can include network penalties, principal bans and criminal exposure. Multiple disclosed MIDs can be legitimate; undisclosed routing is the line you do not cross. That is the same operational lesson behind is cloaking legal: hiding the real transaction is usually where risk compounds.

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, Raise a Chargeback: What It Is and What It Is Not, Why are Chargebacks Allowed?, Why Do Chargebacks Happen?, How Much are Chargeback Fees?, 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.