When to Request Chargeback?

what rate is considered normal here?

A normal chargeback rate for a direct-response VSL or subscription offer is not the same as a normal rate for clean retail ecommerce, and the safer question is how much room you have before the network math turns punitive. Mastercard's ECM tier starts only when both the count and ratio tests are met: 100-299 Mastercard chargebacks in a month and a 1.50%-2.99% chargeback ratio, per Braintree's Mastercard programme documentation. That is not a target. It is the point where a processor starts seeing a file it may not want to carry.

Visa moved the operating line lower for acquirer portfolios. Visa's VAMP fact sheet puts acquirer Above Standard at 50bps, which is 0.50%, and Excessive at 70bps, which is 0.70%, with the same minimum monthly count requirement. For merchants, the U.S. Excessive Merchant threshold dropped to 150bps, or 1.50%, on 1 April 2026. We treat anything near those lines as a funding and account-continuity problem, not just a customer-service problem.

The hard sentence: if you are asking when to request chargeback intervention, ask before the network asks your processor.

For the buyer of traffic, the useful internal trigger is lower than the formal programme trigger. A $47 trial-to-subscription funnel can look acceptable by gross margin while quietly building Visa 10.4, Visa's card-absent fraud condition, and 13.2, the cancelled recurring code, because chargebacks arrive after media spend, fulfilment cost and rebill attempts have already happened. If you need the basic banking definition first, our page on what is chargeback in banking covers the underlying transaction reversal without the media-buying layer.

at what point does a processor act?

A processor acts when your file becomes a portfolio risk, not when your first customer complains. That is the part many operators misread: acquirers carry the Visa and Mastercard monitoring exposure, so they may reserve, restrict, or terminate well before the public threshold is crossed. Visa said VAMP "consolidates five current global programs into a single, streamlined program," which means your fraud and dispute story is now easier to see in one place.

We checked the published thresholds against the fact pack and the processor-facing pressure is plain: Visa's merchant Excessive level in the U.S. is 1.50% as of 1 April 2026, while Mastercard's ECM starts at 1.50% with at least 100 chargebacks. MATCH, Mastercard's high-risk merchant file, is worse because a listing follows the principal owner, not only the LLC. Stripe's MATCH documentation says acquirers and processors are the reporting parties, and records remain for five years.

Processors also act on pattern risk. Multiple merchant IDs are not automatically improper; Easy Pay Direct and other high-risk providers market load balancing. The violation is undisclosed routing or processing one entity's product through another entity's MID, meaning merchant ID. That distinction matters if your fix for rising disputes is to move volume instead of reducing the dispute cause.

what reduces it without killing conversion?

The cleanest reduction comes from stopping preventable disputes before they become chargebacks, not from winning representment after the file is already counted. Pre-dispute tools matter because Visa's fact sheet says the VAMP Ratio "excludes disputes resolved through pre-dispute solutions" and separately excludes qualifying Compelling Evidence 3.0 fraud. A representment win may recover cash, but it usually does not erase the monitoring event that worried the processor.

The conversion-safe fixes are boring because they change recognition, cancellation and billing clarity rather than the promise. Descriptor quality is one. Visa's Merchant Data Standards Manual gives 25 spaces for the merchant name in authorization and clearing, requires abbreviation instead of blind truncation, and allows extra language on the first recurring transaction after a trial or promotional period. That can reduce calls that start as confusion and end as 10.4 or 13.2.

RDR, meaning Rapid Dispute Resolution, and Verifi CDRN, meaning Cardholder Dispute Resolution Network, help mostly on the dispute leg. Compelling Evidence 3.0 helps on the fraud leg when the issuer accepts it. That distinction is where many chargeback dashboards mislead you: one card-absent dispute can produce both a TC40 fraud report and a TC15 dispute, so removing only the TC15 still leaves part of the VAMP numerator alive.

We could not verify the current primary-source performance range for Verifi Order Insight plus Ethoca Consumer Clarity; the industry figure buyers quote is 30%-45% overall chargeback reduction, and a current Visa or Mastercard product benchmark would settle it.

who pays, and when?

The merchant usually pays first through fees, reserves, refunds, lost goods, and withheld settlement; the exact path depends on whether you run a direct merchant account, a high-risk processor, or a retailer-of-record platform. If the question is does chargeback cost, the short answer is yes even when you win later, because operations time and monitoring ratios do not disappear with a favorable representment result.

High-risk direct processing prices are quote-only in the places that matter. PaymentCloud's guidance cites average high-risk processing rates of 3.49%-3.95% plus about $0.25 per item, account fees, added PCI or gateway fees, chargeback fees around $20, and rolling reserves of 5%-10%, with 15%+ for higher risk. PaymentCloud also says merchants should get a custom rate review, so those numbers are market guidance rather than its own tariff.

A merchant of record, or MoR, is the legal seller to the customer. Paddle defines it as "a legal entity responsible for selling goods or services to an end customer," but Paddle and Polar are digital-only by policy, so shipped nutraceutical offers cannot use them as a clean answer. ClickBank and Digistore24 are different because their published materials cover physical-product commerce, but their fees come off the transaction before vendor and affiliate splits.

The uncomfortable point: an MoR can move card-network liability without removing economic loss. Paddle's own terms say that where it prevents a chargeback or refunds a buyer, "Paddle is entitled to receive from you" the refund or chargeback amount plus fees and expenses. For your model, that means MoR is a counterparty-risk and compliance trade, not a magic shield. Digital River's 2025 Chapter 7 filing is the reminder that funds held inside an MoR are still funds held by someone else.

what does the monitoring programme actually measure?

Visa VAMP measures combined fraud reports plus disputes against settled card-not-present transactions, while Mastercard ECM measures chargebacks against the prior month's sales transactions. Visa's formula is the important one for current U.S. direct-response risk: the VAMP Ratio equals Count of Fraud TC40 plus Disputes TC15 divided by Count of Settled Transactions TC05, counting card-absent VisaNet transactions only, per Visa's acquirer monitoring fact sheet.

That means fraud alerts and disputes are no longer separate operational silos for Visa monitoring. A TC40, Visa's fraud-report transaction type, can exist even when the merchant resolves the customer complaint through RDR. Visa's dispute-rule update says that when a participating merchant returns a merchant-credit response, Visa Resolve Online submits a dispute financial through TC15; the operational effect is that RDR suppresses the dispute record for VAMP but does not retract an issuer fraud report already filed.

Mastercard is lagged. The ratio is chargebacks received in the current month divided by sales transactions processed in the prior month. So June chargebacks are measured against May sales, which makes a sudden scale-down dangerous: the numerator can keep arriving after the denominator shrinks. If you need the broader operating function, our page on what is chargeback operations explains the workflow around alerts, evidence, refunds and reporting.

how fast does a bad month show up?

A bad month can show up before you feel it in cash, because the network measures event counts that lag the media buy and the processor reacts before final loss is known. Visa VAMP runs monthly identification, and Mastercard's ECM uses current-month chargebacks over prior-month sales. That lag is why a campaign that looked profitable on Monday can become a reserve conversation after the following billing cycle.

The first visible warning is usually not a formal network notice. It is a processor email asking for fulfilment logs, cancellation proof, affiliate traffic sources, descriptor history, refund percentages, or a remediation plan. We count that as the first operational threshold because it changes your room to spend even if the public card-network threshold has not been crossed.

Rebill funnels have a second clock: cancellation law. ROSCA, 15 U.S.C. 8403, still requires clear material terms before billing information, express informed consent before charging, and simple cancellation mechanisms. 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 live. California, New York and Colorado have their own timing and cancellation rules from the fact pack, so your chargeback timing cannot be separated from subscription compliance.

what happens after a threshold is crossed?

After a threshold is crossed, the cost moves from ordinary dispute handling to monitoring fees, reserves, processing restrictions, and possible termination. Visa's published VAMP fee structure reported by NMI and the Merchant Risk Council is $4 per fraud or non-fraud dispute transaction at Above Standard and $8 at Excessive, with no warning tier for merchants identified as Excessive. Mastercard's ECM fines escalate by programme month, starting at $0 in month 1 and reaching $100,000 per month for ECM after month 19.

The next step is usually remediation. A processor may ask for tighter refund paths, descriptor changes, evidence enrollment, affiliate-source cuts, revised cancellation flows, shipping proof, customer-service staffing, or lower-volume caps. This is why the better question is not only why does chargeback happen, but which reason code is telling you what to fix. Visa 10.4 points at fraud or friendly fraud; 13.1, 13.3, 13.6 and 13.7 point more often at delivery, quality or refund failure.

The last step is account continuity. MATCH reason code 04 is Excessive Chargebacks, and Stripe's MATCH documentation says removal is limited: error by the processor, or PCI DSS compliance for code 12 only. Excessive chargeback and excessive fraud listings cannot be removed simply because the merchant later cleans up. We changed our mind on this point after checking the MATCH mapping: the prompt's assumed code mapping was wrong, and code 04 is the one tied to excessive chargebacks.

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 Whatsapp Business Account is Banned?, My Ad Account is Disabled on Facebook How to Get Back, Facebook Ads Manager Account Disabled: The Practical Version, Digistore24 Banned Countries: What It Is and What It Is Not, 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.