When to File Chargeback?

what rate is considered normal here?

A normal chargeback rate for a direct-response offer is whatever leaves enough distance below the card-network thresholds, not whatever a media buyer calls acceptable in a group chat. For Mastercard, the published Excessive Chargeback Merchant tier starts only when both counts and ratios are hit: 100-299 Mastercard chargebacks in a month and a 1.50%-2.99% ratio, per Braintree's Mastercard programme summary. That sounds forgiving until your first bad cohort ages into disputes.

The harder number is Visa's VAMP, Visa's monitoring programme for fraud and disputes. Visa's fact sheet defines the numerator as fraud plus disputes divided by settled transactions, and its merchant excessive threshold moved to 1.50% in AP, Canada, EU and U.S. regions on 1 April 2026. The count gate still matters: a merchant also needs at least 1,500 fraud plus dispute items in the month. A small offer can be damaged before it is formally identified; a large offer can enter the programme in one cycle.

We counted the practical breakpoints differently after checking the VAMP numerator. A $47 supplement funnel with 0.8% chargebacks can still be a problem if TC40 fraud reports are stacking beside TC15 disputes, because Visa adds both legs unless pre-dispute tools or Compelling Evidence 3.0 remove the right record. If you're asking why chargebacks happen, the answer is rarely just fraud. Billing descriptor confusion, cancellation friction, refund delays and over-claimed VSL copy all show up as payment risk.

Normal is not the target; headroom is the target.

at what point does a processor act?

A processor acts before the network forces it to act if your offer threatens the portfolio. That is the uncomfortable part: the acquirer is judged on its own VAMP portfolio ratio, not just on your merchant record, so a nutraceutical continuity funnel can become a processor problem while your internal dashboard still frames the month as manageable.

Visa described VAMP as consolidating prior programmes and "collapsing 38 separate remediation processes into one," which means the monitoring conversation is less fragmented than it was under VDMP and VFMP. In the same practical period, NMI and Merchant Risk Council guidance put enforcement fees at USD $4 per fraud or disputed transaction at Above Standard and USD $8 at Excessive. A processor looking at that math doesn't need to wait for your brand to become famous for the wrong reason.

Your processor also cares about the story behind the rate. Multiple MIDs, merchant IDs used to process card sales, are not illegal by themselves; high-risk providers market load balancing. The problem starts when one entity's transactions run through another entity's MID, or when the acquirer did not underwrite the real product. Venable describes transaction laundering as one merchant processing for another undisclosed entity, which can create network, contract and law-enforcement exposure.

We could not verify Durango Merchant Services' current supplement-specific underwriting terms from the source pack because the direct page failed at check time; a current signed quote or live provider page would settle it.

• Expect a processor review when chargeback counts rise faster than sales, even below a formal network tier.
• Expect reserve pressure when refunds, disputes and fulfilment complaints move together.
• Expect sharper scrutiny if descriptors, customer support records and product names don't match what was underwritten.

what reduces it without killing conversion?

Pre-dispute resolution, better transaction enrichment and cleaner cancellation paths reduce chargebacks with less conversion damage than simply adding friction at checkout. That is the claim many operators argue with, because 3-D Secure feels like the obvious fraud shield. The problem is placement: off-session merchant-initiated transactions, the recurring rebill leg, do not support 3DS authentication under Stripe's documentation, so 3DS doesn't protect the continuity charges that create many trial-subscription disputes.

Visa's own wording says the VAMP Ratio "excludes disputes resolved through pre-dispute solutions," and separately excludes qualifying Compelling Evidence 3.0 fraud records when timing allows. That distinction matters. Rapid Dispute Resolution, a Visa pre-dispute refund workflow, can stop the TC15 dispute from entering VAMP, but industry analyses say it does not erase a TC40 fraud report already filed by the issuer. Compelling Evidence 3.0 is the tool aimed at that fraud leg.

Descriptor work is boring until it saves the file. Visa's April 2026 Merchant Data Standards Manual gives 25 spaces for the merchant name and requires longer names to be abbreviated with the uniquely identifying part preserved. The same manual permits extra language after the merchant name for the first recurring transaction after a trial or promotional period, signalling that the regular subscription price now applies. If your descriptor reads like a mystery, the cardholder's banking app becomes the dispute form.

We checked the reduction tools against monitoring math, not against vendor marketing.

who pays, and when?

The merchant usually pays the economic cost, even when a marketplace or Merchant of Record is the legal seller. A Merchant of Record, or MoR, is the seller responsible for payment acceptance, tax handling and disputes. Paddle defines it as "a legal entity responsible for selling goods or services to an end customer," but its own terms also say the vendor must reimburse the full refund or chargeback plus fees when Paddle prevents or absorbs one.

ClickBank is different from Paddle in one useful way for supplement operators: ClickBank materials identify it as retailer and refer to digital or physical product purchase and shipping fees. It states the platform takes "a 7.5% + $1 transaction fee from the total purchase price," before vendor and affiliate splits. That can solve legal-seller positioning for some direct-response offers, but it doesn't make refund economics disappear.

A processor account has its own cash timing. Typical high-risk merchant reserves run 5%-15% of processing volume held for 90-180 days, with nutraceuticals among the verticals facing heavier reserve demands. If you're asking whether chargebacks cost money, the answer includes the fee, the refund, lost product, reserve drag, processor review time and the chance that future acquiring becomes harder.

The refund is immediate; the reputation cost compounds.

• Cardholder: the bank may give provisional credit while the dispute is investigated, but the source pack does not give timing rules by issuer.
• Merchant on direct MID: the refund, chargeback fee, lost fulfilment cost and monitoring impact sit with the merchant.
• Vendor using MoR or retailer-of-record: the platform may face the card network, but contract terms can pass the chargeback cost back to the vendor.

what does the monitoring programme actually measure?

Visa VAMP measures fraud reports plus disputes against settled card-not-present Visa transactions, while Mastercard ECM measures chargebacks against prior-month sales. That is the sentence to keep on your monitor: the two programmes are not counting the same thing, and a dashboard that treats them as one generic chargeback percentage will mislead you.

Visa's fact sheet defines the VAMP Ratio as "[Count of Fraud (TC40) + Disputes (TC15)] / [Count of Settled Transactions (TC05)]." It covers card-absent VisaNet transactions, domestic and cross-border. In plain English, TC40 is an issuer fraud report, TC15 is a dispute financial record, and TC05 is the settled transaction count. A single disputed card-not-present order can create both a fraud report and a dispute record, so the numerator can be harsher than the word chargeback suggests.

Mastercard's ECM ratio is lagged: chargebacks received in a given month divided by sales transactions processed in the prior month. That lag matters if your media spend spikes in May, your refunds slow in June and your disputes arrive in July. The month that gets you identified may not be the month your buyer first saw the VSL, the video sales letter driving the purchase.

For the consumer, what a chargeback is in banking is a cardholder protection path; for the operator, it is also a network-monitoring event.

how fast does a bad month show up?

A bad month can show up within the next monitoring cycle, but the visible damage may lag the media buy by weeks. Visa VAMP is monthly programme math built from settled transactions, fraud reports and disputes; Mastercard ECM uses chargebacks in one month divided by the previous month's sales. Your first clue is often not a formal notice. It is a reserve demand, rolling cap, document request or processor call.

The bad month arrives late because the buyer's timeline is longer than your ad account's timeline. A subscriber may click a ClickBank or direct-MID offer today, receive a bottle days later, notice a rebill after a trial period, contact support, wait for a refund, then file through the issuer. By then, the campaign that created the dispute may be paused, cloned or renamed, but the network math still lands on the MID that processed the sale.

This is why chargeback operations has to sit next to media buying, not after it. If support tags show cancellation confusion in week 1, the dispute ratio may not prove it until week 4 or week 8. Operators consistently report that issuer inquiries, refund tickets and descriptor complaints are earlier signals than the network threshold notice; Meta or Google ROAS will not tell you that.

We changed our read of timing after comparing Visa and Mastercard formulas.

• Daily: watch refund requests, cancellation contacts, descriptor complaints and issuer inquiry alerts.
• Weekly: compare disputes by cohort, traffic source, VSL, offer SKU and rebill number.
• Monthly: reconcile Visa VAMP, Mastercard ECM/HECM, reserve movement and processor communications.

what happens after a threshold is crossed?

After a threshold is crossed, the processor can demand remediation, assess fees, hold reserves, restrict processing or terminate the account. The network consequence depends on the programme, the month in programme and the reason code mix. For Mastercard, ECM/HECM fines escalate by month, and the Issuer Recovery Assessment adds USD/EUR $5 for each chargeback above 300 in the month for merchants in the excessive chargeback programme.

MATCH is the severe ending operators underestimate. Stripe's MATCH documentation says acquirers or processors report terminated merchants, not Mastercard itself, and the report must be submitted within one business day after termination. Records remain for five years. A listing follows the principal owner using available name, address, phone and tax ID, so forming a new company does not make the old file vanish.

Removal is narrower than most sales decks imply. Stripe's summary says MATCH removal is limited to processor error or PCI DSS compliance for code 12; excessive chargeback and excessive fraud listings cannot be removed just because the merchant later fixed operations. That is why the practical answer to when to file chargeback, from the operator side, is this: investigate the cause before the network or acquirer writes the story for you.

If you are the cardholder, file when the merchant won't fix an unauthorized, undelivered, misdescribed, unrefunded or post-cancellation charge.

• Visa Above Standard or Excessive: per-item assessments can apply, and merchants identified as Excessive do not receive a warning tier under the cited NMI/Merchant Risk Council guidance.
• Mastercard ECM/HECM: monthly fines escalate after repeated months in programme, with larger amounts at HECM levels.
• MATCH: termination reporting can affect future merchant-account applications by the same principal.

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 Competitors Run Ads That Would Get You Banned: Enforcement, Explained, Meta Verified for Business: Does Paying for Support Fix Ad Bans?, TikTok Ad Account Suspended: Every Trigger and the Appeal That Works, Facebook Page Restricted From Advertising: Page-Level Flags and Fixes, 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.