3DS Liability Shift Calculator
Put your own numbers in and see what fraud-coded disputes cost you in a year, and what the liability shift would actually cover.
What the liability shift actually is
When a cardholder tells their bank "I never made this charge," the dispute lands as a fraud or unauthorized claim. On a normal card-not-present transaction, that loss usually sits with you, the merchant, and it is one of the hardest dispute types to answer after the fact.
Card network rules published by Visa and Mastercard describe a different outcome for transactions authenticated with 3D Secure: liability for that fraud claim generally moves to the card issuer instead. The bank that approved the authentication absorbs the loss, not the merchant who ran the charge.
Whether that matters for your store depends on one thing: how much of your dispute pain is actually fraud-coded. If most of your disputes are item-not-received or not-as-described, the shift does little for you. If they are fraud claims, the calculator below shows the size of the pool the shift applies to. It is arithmetic on your inputs, nothing more, and the caveats sit right under the result where they belong.
Your numbers
Count only disputes coded as fraudulent or unauthorized. In Stripe these show the reason "fraudulent." Leave out item-not-received and not-as-described; the shift does not touch those.
The typical transaction amount on your fraud-coded disputes, not your overall average order value. Fraud disputes often skew larger.
If you add this, the result includes your fraud-dispute rate per 1,000 orders for context.
What that costs at your current pace
Estimated annual fraud-dispute exposure
$4,080
$340 per month: 4 disputes at $85 each, carried out 12 months at the same pace.
On transactions authenticated with 3D Secure, card network rules shift liability for this dispute class, fraud and unauthorized claims, from you to the card issuer. The number above is the pool that shift applies to. It is not a refund you collect; it is the class of loss that generally stops landing on you for authenticated transactions going forward. Network rules carve out exclusions for some merchant categories and regions, so treat it as the rule, not a guarantee.
READ THIS BEFORE YOU ACT ON THE NUMBER
- Fraud claims only. The shift covers authenticated fraud and unauthorized-transaction claims. Item-not-received and not-as-described disputes are untouched: the buyer can still file them, and you still answer with evidence.
- Not every transaction gets a challenge. Under 3D Secure 2, issuers approve many low-risk transactions through a frictionless flow, and exemption paths are treated differently. The issuer makes that call, not you, so the shift does not blanket every order you route to 3DS.
- Friction is real. A challenge adds a step at checkout and some buyers abandon it. We are not going to invent a conversion number for you. Test on a segment of your own traffic, for example orders above a dollar threshold, and measure before requiring it everywhere.
- This is arithmetic, not a forecast. Count times amount times 12, assuming your current pace holds. It is not a prediction of future disputes and not a promise about any dispute outcome. Issuers and networks decide disputes; nobody selling you software does.
The friction tradeoff, said plainly
Requiring 3DS puts a step between the buyer and the purchase: a code from their bank, an approval in a banking app, sometimes a redirect. Some buyers quit at that step. Anyone quoting you a universal conversion cost is guessing, because the drop depends on your buyers, your price points, and how issuers in your markets handle challenges. So we will not quote one.
The honest way to adopt it is segmented. Most merchants start by requiring 3DS where fraud actually clusters: orders above a dollar threshold, first-time buyers, mismatched countries, or traffic flagged by fraud rules. In Stripe you can do this with Radar rules rather than forcing every checkout through a challenge. Measure the completion rate on the segment before you widen it.
Also worth knowing before you flip anything on: under 3D Secure 2, many low-risk transactions are approved through a frictionless flow the buyer never sees. Your real-world friction is usually lower than the worst case, but how often that happens is the issuer's decision, not a setting you control.
Is the shift actually working for you?
This is the part most merchants never check. Having 3DS available is not the same as having it fire on the orders that turn into fraud disputes. If your fraud-coded disputes keep landing on charges that were never authenticated, you are carrying the exposure above while assuming you are covered.
The check is straightforward: pull your recent fraud-coded disputes and look at whether each disputed charge was authenticated. If the answer is mostly no, your rules are routing the wrong orders, or none at all, through authentication. That gap is fixable, but only if you find it before the next dispute, not after.
Find out if 3DS is doing its job
The dispute readiness audit checks whether the liability shift is actually working for you: which order segments get authenticated today, where fraud disputes are landing on unauthenticated charges, and what evidence your checkout captures for the dispute types 3DS does not cover. $149 flat, delivered within 48 hours. We promise the work and the deadline, never the bank's decision.
Reflex answers the disputes that still get through, at a 15% success fee with no monthly cost.