Under an MOR, Whose Chargeback Ratio Is It Anyway?

Does the MOR's acquirer see my chargebacks or the MOR's aggregate?

The acquirer sees only the MOR's aggregate ratio, never your transactions broken out on their own. Paddle, FastSpring, ClickBank, BuyGoods and Digistore24 all sit between you and the card networks as the retailer or reseller of record, which means every authorization, refund and dispute clears through a merchant ID the platform owns. Your sales blend into transactions from other sellers on the same platform before a single ratio reaches Visa or Mastercard.

The liability question and the cost question are not the same question, though most operators treat them as one. Paddle's reseller terms make the vendor repay the full refund or chargeback amount plus any fees and expenses the moment Paddle absorbs one, which means the network-level liability moves to the MOR but the economic loss moves right back to you — the aggregation protects your ratio, not your margin.

That blending is structural, not a courtesy. Visa's Acquirer Monitoring Program calculates its VAMP Ratio as fraud reports plus disputes divided by settled transactions, counted at the acquiring level across the platform's entire card-not-present book — the same logic Mastercard applies through its Excessive Chargeback Merchant program, which divides a month's chargebacks by the prior month's sales for the merchant of record, not for any seller inside it.

Run your own merchant account and the ratio is yours alone, moving the moment your offer does. Sit inside an MOR and thousands of unrelated sellers dilute or concentrate that number before you ever see it, a trade-off laid out in MOR vs your own merchant account vs a PSP aggregator.

How do MORs measure and enforce a per-seller chargeback threshold?

No major MOR publishes a per-seller chargeback ratio it will enforce, so the threshold you actually operate under is contractual, not statistical. Paddle's terms don't cite a ratio at all — instead, clause 10.4 of its reseller agreement makes you pay back the full refund or chargeback amount plus fees the moment Paddle absorbs one, enforcing discipline through direct cost rather than a published percentage.

Polar is more explicit about the mechanics, if not a ratio: it charges $15 per dispute regardless of outcome, deducted straight from your balance, on top of its tiered headline rate running from 5% + 50¢ down to 3.4% + 30¢ per transaction depending on volume. That per-dispute fee is a threshold in effect — file too many and the fee line alone erodes margin long before any network program notices you.

What none of the platforms disclose is the internal review point where a seller gets flagged, throttled or asked to leave. The number exists somewhere in each platform's underwriting, but it isn't public, and any specific figure quoted for it should be treated as a guess dressed as data. The mechanics of how the MOR relationship works before you get anywhere near that point are covered in Merchant of Record, explained for supplement offer owners.

Can other sellers' fraud on the same MOR get my account restricted?

Yes — because the acquirer only sees the MOR's blended number, one seller's fraud spike can push the whole platform toward a threshold enforced against everyone on it. Under rules effective 1 June 2025, Visa's VAMP identified a merchant as Excessive at a ratio of 220 basis points across the AP, Canada, EU and U.S. regions, tightening to 150 basis points from 1 April 2026, and the MOR is the 'merchant' in that calculation, not any individual seller inside it.

Any one of the thresholds below is calculated on the MOR's full portfolio, not on you specifically.

Who controls the billing descriptor, and what can I change about it?

The MOR controls the descriptor, full stop — its name is what appears on the customer's card statement, per Paddle's own definition of the role, and the seller has no independent right to put a different legal name there. What you can typically influence is the product-level line beneath or beside that name, subject to the card network's formatting rules.

Visa's Merchant Data Standards Manual gives 25 character spaces for the merchant name in authorization and clearing, requires names longer than that to be abbreviated rather than simply cut off, and insists the part of the name that uniquely identifies the business survive the abbreviation. Where the descriptor doesn't obviously match the merchant category code, Visa also requires extra identifying language be added.

One allowance worth knowing: Visa's manual explicitly permits supplementary wording after the merchant name on the first post-trial recurring charge, signalling that a discounted or trial period has ended and the regular subscription price now applies. That is one descriptor lever most nutra offer owners haven't used, and it sits inside the MOR's formatting control, not yours to add unilaterally.

The invoice sitting behind that descriptor carries its own separate control question: who actually remits the sales tax or VAT charged on the sale. Paddle's terms state it handles all sales tax collection, reporting and remittance itself, which is one version of the answer — the fuller comparison across platforms sits in who remits the tax when an MOR is on the invoice.

Who handles the customer service call that prevents the dispute?

It depends entirely on which MOR you're inside, and the split decides who actually stops a dispute before it's filed. FastSpring's documentation states its own Terms and Conditions — not the publisher's — govern the transaction, which puts FastSpring, not you, in the seat when a buyer calls asking for a refund.

BuyGoods is explicit about it: its supplier terms state that all refund and exchange requests are managed by BuyGoods, and its consumer terms grant a 60-day return window that every supplement offer owner on the platform inherits. ClickBank positions itself the same way, naming itself the retailer of the product being sold — a role only a shipped-goods platform can take on, since Paddle, FastSpring and Polar exclude physical products entirely, a split covered in which MOR platforms actually accept physical supplements.

That handoff matters for one reason beyond convenience. Pre-dispute deflection tools like Verifi Order Insight and Mastercard's Ethoca Consumer Clarity work by putting order detail — item description, refund status, contact information — in front of the cardholder or the bank agent at the moment of the inquiry, before it becomes a chargeback. Whoever answers the phone, or feeds that data pipe, is the party actually preventing the dispute, not the party absorbing it afterward.

Do I get the dispute evidence and reason codes, or only a net number?

Mostly you get a net number, not the underlying case file. Paddle's clause 10.4 obligates you to reimburse the full refund or chargeback amount plus fees and expenses, which confirms the platform tracks the loss down to the transaction — but none of the published MOR terms reviewed here commit to passing you the dispute reason code, the evidence submitted, or the outcome narrative.

That gap is worth naming precisely, because the reason code is the diagnostic. Visa dispute condition 10.4, 'Other Fraud — Card-Absent Environment', and reason code 13.2, 'Cancelled Recurring Transaction', point at friendly fraud and billing disputes you might fix with clearer disclosure or better cancellation flows; codes 13.1, 13.3, 13.6 and 13.7 more often point at genuine fulfilment or refund failures on the operational side. Without the code, you're guessing which one you're fighting.

Whether a given MOR will hand over that granularity on request is not something any of the platforms state in their published terms. Treat it as a question to ask before you sign, not an assumption to carry in.

What does an MOR offboarding actually look like when ratios go bad?

It looks like a funds freeze first and an account closure second, with very little public documentation of the process in between. The clearest case study is also the worst one: Digital River Marketing Solutions filed for Chapter 7 bankruptcy on 1 May 2025, and reporting describes merchant payouts halting from around July 2024, insolvency proceedings for its German subsidiaries, and a Hennepin County lawsuit from Kaspersky alleging roughly $18 million was never remitted.

Short of collapse, the mechanics resemble ordinary high-risk processing wind-down — reserves held against future disputes, dormant-account fees accruing, payouts delayed pending reconciliation. ClickBank, for instance, charges dormant-account fees rising from $1 per pay period after 90 days of no earnings to $50 per pay period after 365 days, which is roughly the shape of what an account in wind-down looks like even short of outright termination.

None of the MOR terms reviewed here publish a formal offboarding SLA, a reserve percentage, or a hold period specific to a seller being exited for ratio reasons. That detail sits in individual account correspondence, not in public policy, and the payout mechanics that do apply during normal operation are covered in how MOR payouts, holdbacks and refund reserves actually work.

Does an MOR termination follow me to the next processor?

Sometimes, and the honest answer is that this is the least documented part of the whole relationship. MATCH listings are filed by the acquirer that terminates a merchant account, and the report follows the individual — name, address, phone number and tax ID of the principal owner — so a new company formed by the same person gets matched on inquiry.

Under an MOR, though, the legal merchant on record is the platform, not you, which raises a question none of the published MOR terms in this review answer directly: does a seller's exit from an MOR ever generate a MATCH record against that seller personally, or does it stay inside the platform's own internal notes? That needs checking against a specific MOR's actual reporting practice before you rely on either answer.

What is documented is that MATCH removal itself is narrow — limited to the acquirer admitting an error, or, for PCI-related listings only, achieving compliance — and a listing for excessive chargebacks or fraud cannot be removed by remediating afterward. If your MOR relationship ever does surface on a MATCH inquiry, plan for the listing to run its full five-year term, not to be negotiable.

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.

When the topic touches health claims, platform policy, or GLP-1 market research, validate the observable campaign signals against primary references such as Meta advertising standards, FTC health claims guidance, and Google helpful content guidance. Daily Intel adds the proprietary direct-response layer by mapping how those rules show up in active VSLs, Meta creatives, funnels, transcripts, UTMs, and checkout paths.

For deeper evaluation, continue through Daily Intel compliance and legal disclaimer, The MATCH List: How Nutra Merchants Get Blacklisted for Five Years, Processor Termination in Nutra: Reserves, Holds, and Frozen Payouts, When Ad Fraud Becomes Wire Fraud: The Criminal Line in Media Buying, The Day the FTC Files: TROs, Asset Freezes, and Receivers in Nutra Cases, 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.