Raise a Chargeback: What It Is and What It Is Not

what rate is considered normal when buyers raise a chargeback?

Normal depends on the network math, but in practical direct-response terms a chargeback rate near 1% is already uncomfortable and a card-absent Visa ratio near 1.50% can be a formal problem. Visa's VAMP, Visa's monitoring programme for fraud and disputes, counts fraud reports and disputes together, so a buyer who decides to raise a chargeback can hurt the file even before the merchant loses the case.

We separate refund pressure from chargeback pressure because they are not the same operating signal. A buyer asking support for a refund is a service event; a buyer going to the bank creates a network event, and that network event can follow the merchant account, processor relationship, and principal owner much longer than the order itself.

The contested point is this: for a paid-traffic VSL, a low refund rate can be more dangerous than a higher refund rate if it means dissatisfied buyers are being pushed toward the issuer. We counted the monitoring formulas first, then the cancellation rules, and the conclusion changed: the cheapest dispute is usually the one that never becomes a dispute.

Visa's own VAMP fact sheet says the ratio “excludes disputes resolved through pre-dispute solutions,” which is why pre-dispute refund rails matter more than post-dispute representment wins. If your team treats every refund save as a victory, your dashboard can look good while the acquirer sees the opposite.

at what point does a processor act?

A processor acts before the network's published ceiling if the account starts threatening its portfolio ratio, reserve exposure, or sponsor-bank tolerance. Visa's acquirer-level VAMP thresholds are tighter than many merchants expect: Above Standard starts at 0.50% and Excessive starts at 0.70%, with minimum monthly fraud-plus-dispute counts attached.

That is why your processor can pressure you even when your own MID, merchant ID, has not crossed a headline merchant threshold. The acquirer is judged on the book it sponsors, not only on your offer. One aggressive continuity funnel can become an internal portfolio problem before it becomes a public network problem.

For the consumer side of the term, what is chargeback in banking matters because the bank action is not just a complaint ticket; it is the opening move in a regulated card-network workflow. Once that workflow starts, the processor sees data the landing-page team usually does not: TC40 fraud reports, TC15 disputes, reason codes, alerts, refunds, and authorization behavior.

We could not verify the exact current supplement-specific underwriting terms for Durango Merchant Services and Authorize.net at check time; direct provider pages or a signed 2026 underwriting quote would settle it.

• A processor may ask for a remediation plan before network enforcement begins.
• A processor may raise reserves when chargeback velocity rises faster than sales volume.
• A processor may terminate faster if descriptor confusion, trial complaints, or undisclosed MID routing appear together.

what reduces it without killing conversion?

The highest-return controls reduce buyer confusion before the issuer call, not after the dispute lands. Clear descriptors, cancellation links, order-detail enrichment, and pre-dispute resolution all protect conversion because they do not add friction at checkout for every buyer; they add context when the buyer is deciding whether the charge is legitimate.

Descriptor work is underrated. Visa's Merchant Data Standards Manual gives 25 spaces for the merchant name in authorization and clearing, and it requires names longer than 25 characters to be abbreviated with the uniquely identifying part left intact. That matters for trial-to-subscription offers because a cardholder who cannot recognize the billing name has a simple path to Visa 10.4, Other Fraud-Card-Absent Environment.

Pre-dispute tools are not magic, but the arithmetic is favorable. Order Insight, Visa-side transaction detail, and Consumer Clarity, Mastercard-side transaction detail, can show logo, item description, refund status, contact details, and order data inside issuer workflows. An inquiry deflected there never becomes the chargeback entry your processor has to explain.

If you want the broader cause map, why does chargeback happen is the useful next question because not every dispute is fraud. In nutra trial billing, 10.4 and 13.2 are often filed as friendly fraud, meaning the buyer authorized the purchase but disputes it, while 13.1, 13.3, 13.6, and 13.7 more often point to fulfillment, product, or refund failure.

who pays, and when?

The merchant usually pays economically, even when another party is the legal seller or the processor fronts the network relationship. Fees, reserves, refund debits, chargeback debits, and lost processing access land at different times, so the question is not only who pays; it is which balance gets hit first.

Direct merchant account

With a direct high-risk merchant account, the processor can charge dispute fees, hold rolling reserves, and pass network assessments through the merchant statement. Typical high-risk reserves run 5%-15% of processing volume held for 90-180 days, with capped and upfront reserves also used. For a cash-flow model, does chargeback cost is not a yes-or-no issue; timing determines whether payroll, media spend, or inventory breaks first.

Merchant of record

A Merchant of Record, legal seller for the buyer, moves the card-network merchant relationship but not necessarily the economic loss. Paddle defines a Merchant of Record as “a legal entity responsible for selling goods or services to an end customer,” yet Paddle's own terms still let it recover refunds, chargebacks, fees, and expenses from the vendor. ClickBank is different because it supports digital or physical product purchases and states a 7.5% + $1 transaction fee, while Paddle and Polar prohibit physical products.

Network and programme fees

Visa enforcement fees are reported at $4 per fraud or non-fraud dispute transaction at Above Standard and $8 at Excessive, per NMI's VAMP guide. Mastercard's ECM and HECM programme can escalate from $0 in month 1 to $100,000 or $200,000 per month by month 19 and beyond, depending on tier and currency, per Braintree's Mastercard programme documentation.

what does the monitoring programme actually measure?

The monitoring programme measures network-visible events, not your internal explanation of buyer intent. Visa's VAMP Ratio is fraud reports plus disputes divided by settled card-absent VisaNet transactions; Mastercard's ECM ratio is chargebacks received in a month divided by sales transactions from the prior month.

Visa described VAMP as consolidating prior programmes into one acquirer programme, and its own corporate note says it is “collapsing 38 separate remediation processes into one.” That means the old habit of treating fraud monitoring and dispute monitoring as separate dashboards is out of date for Visa card-absent traffic.

This is where chargeback operations, the repeatable workflow for disputes, has to connect with media buying. What is chargeback operations is not just representment packets; it is descriptor testing, cancellation logging, refund timing, alert coverage, issuer data enrichment, reason-code triage, and weekly cohort math by traffic source.

RDR, Rapid Dispute Resolution, can remove the TC15 dispute leg for VAMP purposes when a participating merchant returns a credit response, but it does not erase any TC40 fraud report already filed. Compelling Evidence 3.0, issuer-accepted evidence for Visa fraud disputes, is the separate route that can exclude qualified TC40 fraud from the numerator. That distinction is small in wording and large in risk.

how fast does a bad month show up?

A bad month can show up in the next monitoring cycle, but Mastercard's chargeback ratio is deliberately lagged. Its ECM ratio uses chargebacks received in the current month divided by sales transactions processed in the prior month, so June disputes are measured against May sales.

Visa's VAMP math is more immediate because the numerator counts fraud and dispute records against settled card-absent transactions. The painful version is a scaling month where orders fall at the same time complaints rise; the denominator shrinks while the numerator keeps arriving from earlier cohorts.

For operators, the work is cohort timing. A 14-day trial offer bought on day 0, rebilled on day 15, refunded on day 22, and disputed on day 35 can make the campaign that caused the risk look clean if your media report stopped at day 7. We check by order cohort, not only by calendar month, because the chargeback arrives after the buying decision that created it.

Speed also matters for consumers using fintech cards; the procedural article on how to chargeback Revolut is a reminder that app-based dispute flows reduce buyer friction. Lower friction does not make the claim valid, but it can make the merchant's monitoring data move faster.

what happens after a threshold is crossed?

After a threshold is crossed, the processor can demand remediation, impose or increase reserves, pass through assessments, restrict processing, or terminate the MID. The network programme is the formal layer; the sponsor-bank decision is often the faster commercial layer.

MATCH is the part many offer owners underestimate. Acquirers and processors, not Mastercard, report terminated merchants to MATCH within one business day, and records remain for five years before Mastercard automatically deletes them. A listing can follow the principal owner because the report includes owner identity data where available, not just the LLC name.

Stripe's MATCH documentation says “records remain on MATCH for five years and are then automatically deleted by Mastercard.” For code 04, Excessive Chargebacks, and code 05, Excessive Fraud, removal is not available just because the merchant later fixes operations; the processor must have added the merchant in error, except code 12 has a PCI DSS compliance path.

The worst response is undisclosed MID hopping. Running multiple MIDs is not automatically a violation, but routing one entity's sales through another entity's underwritten account can become transaction laundering, also called undisclosed aggregation. Venable describes transaction laundering as “one merchant processing card transactions on behalf of another, undisclosed entity,” and that is a different risk class from a high chargeback month.

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, Facebook Ads Not Spending: What Matters and What Does Not, Facebook Ad Account Disabled Unusual Activity, Facebook Ad Disabled Appeal: What It Is and What It Is Not, Meta Ad Rejected: 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.