When to Issue Chargeback?

what rate is considered normal here?

A normal chargeback rate for a direct-response offer is lower than the formal network danger line, because processors act before Visa or Mastercard has to. If you run paid traffic to a VSL, a video sales letter, the number that matters isn't the one a sales page calls acceptable; it's the number your acquirer, gateway, and card networks use to decide whether your MID, a merchant identification account, still looks controllable.

For Visa, the hard merchant-level VAMP, Visa's monitoring programme for chargeback ratios, line in the U.S. moved to 150bps, or 1.50%, on 1 April 2026, with at least 1,500 combined fraud and dispute events in the month, per Visa's acquirer monitoring fact sheet. That is not a target. We would treat it as the outer fence, because the same portfolio can be in trouble at lower acquirer-level ratios.

The safer operating question is: how much room do you have before your next spike?

Mastercard uses a different structure. Its ECM, Excessive Chargeback Merchant tier, starts only when both conditions are met: 100-299 Mastercard chargebacks in a month and a 1.50%-2.99% chargeback ratio, according to Braintree's Mastercard programme documentation. HECM, High Excessive Chargeback Merchant, starts at 300 or more chargebacks and 3.00% or higher. If you are asking why chargeback happens, the useful split is friendly fraud versus real fulfilment, refund, cancellation, or descriptor failure.

at what point does a processor act?

A processor usually acts before the card network's published threshold is crossed, because the processor owns the acquirer relationship and may carry the reserve, monitoring, and MATCH risk. MATCH, Mastercard's terminated-merchant database, is the practical fear: Stripe's documentation says acquirers and processors are the reporting parties, not Mastercard, and records remain for five years after submission.

We checked the common high-risk stack against the fact pack and found a consistent pattern: PaymentCloud, eMerchantBroker, Easy Pay Direct, Corepay, and Durango are underwriting-dependent rather than rate-card businesses. That means a processor can respond with a rolling reserve, capped volume, weekly review, delayed funding, MID suspension, or termination without waiting for a public network notice. If you need the basics of what chargeback is in banking, start there before treating a processor email as just another support ticket.

Stripe's MATCH page is blunt about one trigger: MATCH reason code 04 applies when Mastercard chargebacks exceed 1% of monthly Mastercard sales transactions and total $5,000 or more. Code 05 requires an 8% fraud-to-sales ratio with at least 10 fraudulent transactions totaling $5,000 or more. A processor doesn't need a courtroom finding to act; it needs a risk file it can defend to its sponsoring bank.

We could not verify Durango Merchant Services' current supplement-specific underwriting terms from a primary source at check time; a current merchant agreement or underwriting quote would settle it.

• Expect action first where refunds slow down, descriptors confuse buyers, or cancellation requests stack up.
• Expect reserve pressure when your offer combines trial billing, subscription rebills, and aggressive affiliate traffic.
• Expect termination risk when sales from one entity or product are routed through a MID underwritten for another.

what reduces it without killing conversion?

The best reductions happen before a dispute exists: cleaner billing consent, clearer descriptors, faster cancellation, and pre-dispute enrichment lower chargebacks without forcing every buyer through more checkout friction. The uncomfortable part is that a post-dispute representment win can still count against monitoring math, while an inquiry stopped before the dispute generally doesn't enter the same numerator.

Visa's own wording matters here: the VAMP fact sheet says the ratio "excludes disputes resolved through pre-dispute solutions" and also "excludes TC40 fraud qualified for Compelling Evidence 3.0." That makes Rapid Dispute Resolution, Verifi CDRN, Order Insight, and Compelling Evidence 3.0 operational tools, not just back-office dispute products. RDR can suppress the TC15 dispute leg, but it doesn't erase a TC40 fraud report already filed by the issuer.

The claim many operators resist is that a slightly lower front-end conversion rate can be the higher-volume decision once monitoring math is included. Visa's tokenization hub reports a "4.6 percent lift in authorization rates globally, compared to PAN" and a "30 percent reduction in fraud online vs. PAN" for tokenised card-not-present transactions. If tokenisation, descriptor clarity, and cancellation access keep the MID alive, the funnel with less drama can buy more media.

Descriptor work is underrated. Visa's Merchant Data Standards Manual gives 25 spaces for the merchant name and requires longer names to be abbreviated rather than merely cut off, while preserving the uniquely identifying part. For the first recurring charge after a trial or promo, Visa also permits supplementary language after the merchant name saying the regular subscription price now applies. That is a practical defence against the buyer who recognizes the product page but not the statement line.

• Use network tokens where your gateway supports them, because approval lift and fraud reduction can move in the same direction.
• Treat cancellation UX as risk infrastructure, especially for trial-to-subscription offers exposed to Visa 13.2 disputes.
• Send order, refund, contact, item, device, and policy data into issuer-facing tools before the buyer calls the bank.

who pays, and when?

The merchant usually pays twice: first through refunds, chargeback fees, reserves, or lost goods, and later through monitoring assessments if the pattern crosses a programme threshold. Does chargeback cost is not a philosophical question for paid traffic; it is a cash-flow question, because one dispute can hit revenue, fulfilment, processor fees, and future underwriting at the same time.

MoR, Merchant of Record, changes who appears as the seller to the buyer and networks, but it doesn't automatically move the economic loss away from the offer owner. Paddle defines a Merchant of Record as "a legal entity responsible for selling goods or services to an end customer," yet Paddle's own reseller terms also let it recover the refund or chargeback amount and related fees from the vendor. ClickBank is different for physical supplement offers because it states it is the retailer and charges 7.5% + $1 per transaction from the total purchase price.

Visa VAMP fees are reported at USD $4 per fraud or non-fraud dispute transaction at Above Standard and USD $8 at Excessive, with no warning tier for merchants identified as Excessive. Mastercard's ECM/HECM fines escalate by month in programme, and Braintree's documentation lists $0 in month 1, then $1,000, $5,000, $25,000, $50,000, and eventually $100,000 tiers depending on duration and classification. Your processor may also add its own chargeback fee and reserve holdback.

Reserves are where the cost becomes invisible until you need the money. Corepay's high-risk reserve guidance puts typical rolling reserves at 5%-15% of processing volume held for 90-180 days, with capped and upfront reserves as alternatives. In a supplement offer, that can turn a profitable media day into a funding problem if fulfilment, affiliate payouts, and refund exposure all come due before the reserve releases. We counted reserves separately from fines because they do not show up as a network penalty, but they still decide whether you can keep buying traffic.

what does the monitoring programme actually measure?

Visa VAMP measures combined fraud reports and disputes against settled card-not-present Visa transactions, not just old-style chargebacks. Visa defines the VAMP Ratio as fraud TC40 plus disputes TC15 divided by settled TC05 transactions, limited to card-absent VisaNet activity. In plain English: a buyer's bank can put risk into the numerator before the merchant sees the familiar chargeback workflow.

That is why chargeback operations has to sit upstream of representment. Visa said VAMP "will consolidate 38 remediation processes into one streamlined program," and the practical result is that fraud and dispute control now share the same scoreboard. A $47 bottle with a confusing trial rebill can create 10.4 fraud claims, 13.2 cancelled recurring claims, refund complaints, and TC40 records from the same funnel weakness.

Mastercard still separates several regimes. ECM and HECM focus on chargeback count and chargeback ratio, while EFM, Excessive Fraud Merchant, looks at fraud criteria, and SMMP, Scam Merchant Monitoring Program, becomes enforceable 24 July 2026 for combined refunds plus chargebacks above 5% of total transactions over a rolling 30-day period with at least 500 transactions. Justt's Mastercard-citing analysis also says SMMP treats multiple MID requests without clear business justification as a scam signal.

The split matters because mitigation has to match the numerator. RDR, Rapid Dispute Resolution, can stop a dispute record from counting for VAMP, but industry analyses say Compelling Evidence 3.0 accepted by the issuer is the tool that can remove the TC40 fraud leg. For Mastercard, refund timing, chargeback count, and issuer fraud coding can place the same offer into different risk buckets. We changed our mind on this after reading the VAMP formula; calling it a chargeback programme alone is too narrow.

how fast does a bad month show up?

A bad month can show up inside the same monthly monitoring cycle, but the exact clock depends on the network metric. Visa's merchant VAMP threshold uses monthly fraud-plus-dispute counts and settled transaction counts. Mastercard's chargeback ratio is lagged: Braintree states it is chargebacks received in a given month divided by sales transactions processed in the prior month.

That lag creates a trap for campaign operators. If May volume is large and June chargebacks arrive from the same cohort, the ratio can look worse after the media buy has already been paused, scaled, or moved. The person asking when to issue chargeback is usually thinking about one purchase; the operator has to think in cohorts, because today's refund backlog can become next month's monitoring event.

SMMP adds a faster lens. Mastercard's scam programme, according to Justt's analysis of the Mastercard rules, uses a rolling 30-day period for combined refunds plus chargebacks, with a minimum 500 transactions. That is closer to a live operating window than a monthly statement review. If you are running advertorials, affiliate traffic, and post-purchase upsells, a bad buyer cohort can age into visibility before the finance team has closed the month.

what happens after a threshold is crossed?

After a threshold is crossed, the path is usually remediation first, then fees, reserves, account limits, or termination if the processor decides the risk cannot be controlled. Visa's 2025 advisory period ended 30 September 2025 for the new VAMP framework, and acquirer Above Standard enforcement began 1 January 2026, so the tolerance window has narrowed.

Mastercard's published ECM/HECM schedule is harsher the longer the merchant stays in programme. Per Braintree, month 1 can be $0, month 2 starts at $1,000, months 7-11 can reach $25,000 for ECM and $50,000 for HECM, and month 19 and beyond can reach $100,000 for ECM and $200,000 for HECM. Mastercard also adds a $5 issuer recovery assessment for each chargeback above 300 in the month.

The worst outcome is not the fee; it is losing clean processing identity. Transaction laundering, also called undisclosed aggregation, is routing one merchant's transactions through another undisclosed MID. Venable describes it as one merchant processing card transactions for another undisclosed entity, and the consequences can include network fines, principal-level penalties, and bans from payments. Several MIDs can be legitimate when disclosed and underwritten correctly, but hiding the product, entity, or traffic source is the line that turns routing into a termination file.

A crossed threshold should force three immediate checks: stop the source creating the disputed cohort, reconcile refund and cancellation queues, and compare issuer reason codes against the offer promise. If the VSL claims a subscription is easy to cancel, your cancellation path has to prove it. If a customer has a valid unresolved billing dispute, they may have a legitimate reason to issue chargeback; if they simply forgot the descriptor, your best outcome is to answer the issuer inquiry before it becomes a formal dispute.

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 Reversed?, Chargeback for Defective Product: The Practical Version, When Can Chargeback Be Used?, When is a Chargeback Appropriate?, 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.