Chargeback protection: what it covers, what it costs and what it never does
Chargeback protection explained: 3D Secure liability shift, merchant of record, guarantees and alerts, what each covers, and why none protects your ratio.

Chargeback protection is any arrangement where someone other than you absorbs the loss when a cardholder disputes a payment. It comes in four forms: the card networks’ liability shift for payments authenticated with 3D Secure, a merchant of record such as Paddle or Lemon Squeezy that handles disputes for you, a paid guarantee from a fraud vendor or processor, and pre-dispute tools that let you refund before a chargeback is filed. The liability shift and most guarantees cover fraud claims only, and none of the first three stops a dispute from counting in your card network chargeback ratio: only resolving it before it becomes a chargeback does.
For subscription businesses, the gap matters twice: renewals charged without the customer present usually cannot carry 3D Secure, and many subscription disputes (“I cancelled”, “I don’t recognize this”) are not fraud claims at all. This guide explains what each kind of protection really covers, with the rules from Visa, Stripe, Paddle and Lemon Squeezy behind it, and what to check before you pay for one.
What are the four kinds of chargeback protection?
- 01 3D Secure liability shift The issuer carries fraud claims on the authenticated payment
- 02 Merchant of record The MoR answers the dispute; you pay the amount and a fee
- 03 Chargeback guarantee A vendor reimburses covered chargebacks under its contract
- 04 Pre-dispute tools You refund before a chargeback is filed
| Kind | Who carries the loss | Covers fraud claims | Covers “cancelled” or “not as described” | Keeps the dispute out of your ratio |
|---|---|---|---|---|
| 3D Secure liability shift | The card issuer | Usually, not guaranteed | No | No |
| Merchant of record | You, through your balance, plus a fee | The MoR answers | The MoR answers | No: Paddle counts it, won or lost |
| Chargeback guarantee | The vendor, under its contract | Usually | Depends on the contract | No |
| Pre-dispute tools | You (you refund) | Yes, by refunding | Yes, by refunding | Yes, for Visa disputes they resolve |
The rest of the guide goes through each row.
How does 3D Secure liability shift protect you?
When a customer completes 3D Secure, the issuer has confirmed who they are, so the network moves liability for a later “I didn’t make this payment” claim from you to the issuer. In Visa’s rules (Visa Core Rules and Visa Product and Service Rules, edition of 24 October 2026), this is written as a list of cases where a fraud dispute under condition 10.4, Other Fraud – Card-Absent Environment is invalid. Two of them matter for online sellers:
- Authenticated payments (ECI 5). The issuer confirmed authentication through Visa Secure with EMV 3DS, and the authentication value (CAVV) was included in the authorization request.
- Attempted authentication (ECI 6). The issuer, or Visa on its behalf, answered with an attempt response and a CAVV was included, unless the card is a non-reloadable prepaid card.
Stripe’s 3D Secure documentation adds the caveats that matter in practice:
- Liability shift is expected for authenticated payments that later receive eligible fraud disputes, but Stripe says it is not guaranteed for any specific payment or dispute.
- If the card does not support 3DS or authentication fails with an error, the payment can still go through, but liability generally does not shift.
- If you receive an inquiry on an authenticated payment, you must answer it. Otherwise the issuer can raise a “no-reply” chargeback that may invalidate the shift.
- If the customer disputes for any other reason, such as product not received, the normal dispute process applies.
- Merchants with excessive fraud levels in a monitoring program, and some industries, may lose the shift. Visa’s rule above lists merchant categories (wire transfers, adult content, betting and others) where US domestic fraud disputes apply whatever the ECI value.
The same mechanism exists at the gateway whatever billing tool sits on top: a Chargebee or Recurly subscription charged through Stripe, Braintree or Adyen gets the shift only if that charge was authenticated at the gateway.
Does liability shift cover subscription renewals?
Mostly not. The rule is attached to the transaction whose authorization carried the authentication value. A renewal charged a month later without the customer present is a new transaction, and Stripe notes that not all transactions support 3DS, giving off-session payments as an example.
In practice:
- The first payment (or the setup of the card for future use) can be authenticated and protected.
- Each renewal is charged off-session, usually without a new authentication, so a fraud claim on it falls back to the normal process.
- Your defense on renewals is evidence that the same customer used the same card before without disputing. Visa’s Compelling Evidence 3.0 is built for exactly that case, and it is the closest thing to liability protection a recurring charge gets.
So a subscription business that turns on 3D Secure at signup is protected on a small slice of its volume. That is still worth doing, because every subscription starts with that first payment, but it is not “chargeback protection” for the subscription as a whole.
What does a merchant of record protect you from?
A merchant of record (MoR) sells to your customers in its own name, so disputes are raised against it, not against you. That removes the work, not the cost. Here is what Paddle and Lemon Squeezy document:
| Paddle | Lemon Squeezy | |
|---|---|---|
| Who the dispute is against | Paddle | Lemon Squeezy handles chargebacks on your sales |
| Disputed amount | Deducted from your seller balance | Refunded on your behalf and deducted from your next payout |
| Fee | 20 USD/GBP/EUR or 40 CAD/AUD per chargeback, not refunded if won | $15 dispute fee |
| Who answers | An automated system; Paddle says evidence from sellers is “not required or accepted” | Lemon Squeezy makes the case to the payment provider |
| Refunds before a dispute | On a pre-chargeback alert (typically a 48-hour window), Paddle refunds and still charges the fee | May refund within 60 days of purchase, at its discretion, to prevent chargebacks |
| Your rate | Paddle’s acceptable rate is 0.65% of monthly volume by value; won disputes still count | Too many chargebacks can lead to account suspension |
Two consequences for subscriptions. First, a “no refunds” policy does not stop anything: Lemon Squeezy says customers can still dispute, and it may refund for you. Second, you cannot add your own evidence on Paddle, so the best lever left is preventing the dispute in the first place.
What do paid chargeback guarantees cover?
Some fraud-screening vendors and processors sell a guarantee: they review each order and reimburse fraud chargebacks on the orders they approved. Terms vary by contract and change often, so this guide does not quote any. Before you sign, get written answers to these questions:
- Which dispute reasons are covered? Fraud only (Visa 10.x), or also “cancelled recurring” and “not as described”?
- Are renewals covered, or only the first, customer-present payment?
- Who decides? If the vendor declines an order to protect itself, you lose a sale; ask how declined orders are reported.
- How is it priced? A percentage of all volume, or only of approved orders? Is there a cap per month or per order?
- Does the dispute still count against you? Almost always yes (next section).
- Can you still answer disputes yourself, and who keeps the money if you win?
Why doesn’t chargeback protection lower your ratio?
Because card network programs count disputes, not losses. Stripe’s monitoring program documentation says that, for these programs, a dispute is any disputed payment that moves funds, whatever the reason, and that the programs do not consider outcomes. Even disputes where you have no liability, which Stripe handles for you and does not show in your dashboard, are still included in the networks’ calculations.
For Visa’s VAMP, Stripe describes the count as disputes reported in Visa’s TC15 data plus fraud reports (early fraud warnings) from TC40 data, with one transaction counted twice if it appears in both. Visa excludes disputes resolved through pre-dispute products and TC40 fraud that qualified for Compelling Evidence 3.0.
That has a direct consequence for 3D Secure: Stripe notes that a payment covered by the liability shift can still receive an early fraud warning. The issuer pays, but the fraud report still counts. You can check where you stand with the VAMP calculator.
What actually protects a subscription from non-fraud disputes?
Many subscription disputes are about the relationship, not the card. Visa’s condition 13.2, Cancelled Recurring Transaction covers a cardholder who withdrew permission to be charged for a recurring transaction, and limits the dispute amount to the unused portion of the service. No guarantee or liability shift helps here; the customer is right, or believes they are. What works:
- A cancel path the customer can find, with a confirmation that states the end date.
- Reminders before a trial converts and before an annual renewal.
- A descriptor that matches your brand, so the charge is recognized.
- Fast, full refunds when someone asks, and when an early fraud warning arrives on a payment you cannot defend. Stripe notes that a fully refunded payment cannot be disputed, but a partially refunded one can, for the full amount.
- Pre-dispute tools where your processor offers them. Stripe’s dispute prevention, for example, works with Verifi (Visa) and Ethoca (Mastercard): it can refund disputes automatically by rules you set, and says resolved disputes do not count towards your dispute rate.
The detail of each lever is in how to prevent chargebacks on subscriptions.
Which mistakes should you avoid?
- Treating “protected” as “free”. On a merchant of record you still pay the disputed amount and a fee per case.
- Assuming 3D Secure at signup protects every renewal. It protects the authenticated transaction.
- Ignoring inquiries on authenticated payments. A no-reply chargeback can cost you the shift.
- Buying a guarantee to fix a high ratio. The disputes still count; only fewer disputes fix the ratio.
- Relying on a “no refunds” policy. It does not remove the cardholder’s right to dispute.
- Answering a cancelled-subscription dispute with fraud evidence. Match the evidence to the reason code: the cancellation date, your cancellation terms and proof the customer did not cancel.
FAQ
Is chargeback protection the same as chargeback insurance?
People use both words for the same thing: a third party reimbursing some chargebacks under a contract. The card networks’ own mechanism is different: the liability shift for authenticated payments, which moves fraud liability to the issuer under the network rules.
Does 3D Secure stop chargebacks?
It stops most fraud chargebacks on the authenticated transaction from being charged to you, but Stripe says the shift is not guaranteed for any specific payment. It does not stop disputes for other reasons, and the payment can still receive an early fraud warning that counts in Visa’s program.
Am I protected from chargebacks if I sell through Paddle or Lemon Squeezy?
You are protected from the work: they receive and answer the dispute. You still pay the disputed amount and a fee (20 USD/GBP/EUR or 40 CAD/AUD at Paddle, $15 at Lemon Squeezy), and a high rate can lead to changes on your account or its suspension.
Do won chargebacks still count against me?
Yes. Stripe says network monitoring programs do not consider dispute outcomes, and Paddle says a won dispute still counts towards your chargeback rate.
How NoChurn helps
NoChurn works on the part no protection covers: fewer disputes, and better answers to the ones that arrive. It runs cancel flows with one-click cancel always visible, flags early fraud warnings with a one-click refund, and for each dispute gathers evidence automatically (cancel flow answers, emails sent, usage you send by API, support conversations read only) with an AI-drafted reply that a person reviews before it is sent. See chargebacks.
Sources
All accessed 15 November 2026.
- Visa Core Rules and Visa Product and Service Rules, edition of 24 October 2026 (PDF), sections 11.8.5 (Dispute Condition 10.4) and 11.11.3 (Dispute Condition 13.2)
- 3D Secure authentication flow, section “Disputes and liability shift”, Stripe documentation
- Dispute and fraud card monitoring programs, Stripe documentation
- Common types of online fraud, Stripe documentation
- Dispute prevention, Stripe documentation
- Understanding chargebacks with Paddle, Paddle help center
- Refunds and chargebacks, Lemon Squeezy documentation