Skip to main content

First-Time 3DS Setup (Playbook)

TL;DR
  • Week 1: Integrate 3DS2 through a route your processor supports, implement challenge flow
  • Week 1-2: Define triggers (first-time customer? High-value? EU?), configure risk thresholds
  • Testing: authenticated with no extra step (frictionless), authenticated after the customer proves it's them (challenge), failed challenge, not enrolled, attempted
  • Go live: Choose a trial share within your loss cap, then compare completed payments and fraud losses on the same segment
  • Success: Eligible fraud disputes showing liability shift, and completed payments and fraud losses compared on the same segment

3D Secure shifts fraud liability to the issuer when authentication succeeds on an eligible sale. A challenge can lose good sales, and it has a cost, so measure both. What's below is a 3DS2 setup for first-timers.

Timeline: 1-2 weeks. Integration complexity varies by provider.

Key Principle: 3DS Instead of Decline

If you're thinking about declining a transaction for fraud, test 3DS there instead. An eligible authenticated sale can shift liability. But an order you used to reject can now go through, and a challenge can still lose a good customer, so compare completed-payment margin with fraud costs old enough to read. Required authentication comes first either way. See 3DS deep-dive for the full rationale.

3DS Only Protects Against Fraud Chargebacks

Liability shift covers eligible fraud disputes (Visa 10.4, Mastercard 4837). Customers can still dispute for merchandise not received, not as described, or credit not processed. 3DS doesn't protect against bad fulfillment.

Workflow Overview​

PhaseKey Tasks
IntegrateChoose provider, configure settings, implement challenge flow
ConfigureDefine triggers, set SCA exemptions, build risk rules
Test & LaunchTest all scenarios, choose a capped trial share, expand only after the required checks
MonitorTrack rates, tune rules, check fraud impact

You'll need a processor that supports 3DS2, access to a 3DS provider, the ability to change your checkout flow, and test cards.

Trigger Criteria​

Use this playbook when:

  • You're accepting card-not-present payments without 3DS
  • Fraud chargebacks are eating into margin
  • Your processor confirms SCA (strong customer authentication, the EU and UK rule requiring an extra identity check on many online payments) applies to the payments you accept
  • You want liability shift for high-risk transactions

Understanding 3DS2​

How 3DS2 Works​

3DS2 vs 3DS1​

Feature3DS1 (Legacy)3DS2 (Current)
User experienceA redirect to the issuerFrictionless or challenge, in a browser or an app
Data sharedMinimalRich device and transaction data
Mobile experienceBrowser pagesNative SDKs

3DS1 is history. Don't assume it's still there as a fallback (Braintree's status note).

Key Outcomes​

Eligibility rules live on the 3DS deep-dive. The short version:

ResultWhat HappensLiability
Frictionless successNo customer actionCan shift to the issuer on an eligible fraud dispute. The issuer can still decline the authorization
Challenge successCustomer authenticatesThe same
Challenge failedCustomer fails authTransaction declined
Not enrolledCard doesn't support 3DSNo 3DS shift. Your other fraud defenses can still apply
AttemptedIssuer unavailableCan shift to the issuer when the network's attempt conditions are met. Visa's are on the 10.4 page

Only eligible fraud-dispute liability moves (Visa rules, 24 October 2026, Tables 11-29 and 11-32, pp. 706-716; Mastercard's guide, Dual Message 4837). Check the payment's status and the authentication data the network requires.


Week 1: Integration​

Step 1: Choose 3DS Provider​

RouteExamplesWhat to Compare
Integrated with processorStripe, BraintreeHosted components, the controls you get and the work your integration needs
StandaloneCardinal, NetceteraWhich acquiring routes it supports, and the work to integrate
Gateway-providedAdyen, Checkout.comWhat's tied to that gateway. Checkout.com offers both platform and acquirer-agnostic standalone authentication

Recommendation: start with what your processor already supports, if it fits your routes and terms. If you need more control later, that's when standalone makes sense.

Step 2: Configure 3DS Settings​

If Using Stripe​

  1. With Radar Plus or Pro, go to Radar > Rules and select + Add rule
  2. Choose Request 3DS, then set and test your conditions before you enable the rule
  3. Or tell your developer: "Set request_three_d_secure: 'automatic' in payment options"

What to tell your developer: "Configure Stripe to request 3DS automatically based on risk. Use the Radar dashboard or API options."

If Using Adyen​

Implement 3DS2 first, using Adyen's guide for your integration and platform, browser or native app. Then, with the required Customer Area roles:

  1. Go to Risk & disputes > Dynamic 3D Secure and select Create new rule
  2. Configure authentication preferences per transaction type. Risk-based authentication and custom risk rules need Protect premium (Adyen's guide)

What to tell your developer: "Follow Adyen's 3DS2 guide for our integration and platform, and pass the browser data it lists."

Step 3: Implement Challenge Flow​

When 3DS requires a challenge, the customer sees an authentication popup or redirect:

  1. Receive challenge URL or data from 3DS response
  2. Render challenge in iframe or redirect
  3. Customer completes authentication (OTP, app approval, biometric)
  4. Receive completion callback
  5. Continue with authorization

What to tell your developer: "Follow the SDK and API version we're on, end to end. With Stripe's manual confirmation, that's handleCardAction() and then confirming again on the server. With Adyen, it's handling the action and /payments/details. Fulfill only after the confirmed payment result."

Checkpoint: 3DS integrated; test transactions showing challenge when expected.


Week 1-2: Tuning​

Step 1: Define When to Trigger 3DS​

Don't 3DS everything, unless it's required. Test optional triggers on higher-risk transactions:

Condition3DS Recommendation
First-time customerYes (no history)
High-value orderYes (over $X threshold)
High-risk countryYes
Mismatched geoYes (IP vs billing)
Returning trusted customerNo (friction hurts)
Low-value orderNo (fraud cost low)
Payment within SCA scopeFollow your processor's required authentication and available exemptions; customer location alone doesn't settle scope

Step 2: Configure Risk Thresholds​

The amounts and score below are example test settings. Choose your own from confirmed losses, margin and authentication results by segment. A score of 70 has no shared meaning across vendors; confirm the tool's scale before using any score cutoff:

ConditionRule
High-value ordersRequire 3DS when order is over $500
New customers + moderate valueRequire 3DS for new customers over $100
High-risk countriesAlways require 3DS
Geo mismatchRequire 3DS when IP country differs from billing country
High fraud scoreRequire 3DS when fraud score exceeds threshold (e.g., 70+)

What to tell your developer: "Set up Radar rules (Stripe) or Dynamic 3D Secure rules (Adyen) to trigger 3DS on these conditions. Check which of them our plan includes."

Step 3: SCA Exemption Strategy (EU Only)​

SCA allows exemptions. Use them to reduce friction:

ExemptionWhen to Use
Low valueUp to 30 EUR for eligible remote payments, with cumulative amount or transaction-count checks since the last SCA
Low risk (TRA, transaction risk analysis)The payment provider qualifies for the relevant reference rate and the payment passes its risk checks
RecurringSame amount, same payee, after SCA on creation, any amendment and the first payment. A charge you start without the customer is a merchant-initiated transaction, which is separate. A subscription label alone grants nothing
Trusted beneficiaryCustomer added you to their bank's trusted list, through the bank's authenticated procedure

These are the EEA rules (Regulation (EU) 2018/389, Articles 13-14).

Note: Issuers can override exemptions. Track exemption success rate.


Testing Checklist​

Test Card Scenarios​

ScenarioWhat to Test
Frictionless successNo challenge, auth succeeds
Challenge successChallenge presented, customer completes, auth succeeds
Challenge failureChallenge presented, customer fails, auth declined
Not enrolledCard doesn't support 3DS, auth proceeds without
Issuer unavailableAttempted result, auth may proceed

Integration Tests​

  • 3DS triggers on configured conditions
  • Challenge renders correctly (desktop)
  • Challenge renders correctly (mobile)
  • Callback handles success
  • Callback handles failure
  • Timeout handled gracefully
  • Fallback if 3DS unavailable

Checkpoint: All test scenarios passing.


Go Live and Monitor​

Initial Rollout​

  1. Choose a starting share within your loss cap. For example, 10% may fit; use a smaller share if the exposed sales would exceed the cap
  2. Monitor for 1 week
  3. Check key metrics before expanding

This is a live test. Before the first share goes live, name who owns the risk and the most it can cost, and how you'll roll back. A week shows completed payments; fraud and disputes take longer. If 3DS only adds checks, expand on conversion and keep judging fraud after the outcome window. If it replaces declines with challenges, some orders you used to reject can now go through, so wait for their fraud and dispute results before expanding (before any live test).

Metrics to Track​

MetricTargetRed Flag
Frictionless rateTrack by issuer country and customer segmentA change your processor can't explain
Challenge success rateCompare the same challenge flow before and afterFailures or abandonment rising on that segment
Conversion impactCompare completed payments on the same eligible segmentLost margin exceeds avoided fraud losses
Liability shift rateVerify eligible payments show the expected resultMissing or unexpected liability-shift results

What Good Looks Like​

  • 3DS requested where your configured risk rules or authentication requirements call for it
  • Frictionless and challenge rates tracked by issuer country and customer segment
  • Failed or abandoned challenges investigated
  • Fraud losses and completed payments compared with your baseline on the same segment, allowing equal time for disputes to arrive
  • Liability shift checked on eligible payments

Success Criteria​

You're done when:

  • 3DS integrated and processing live traffic
  • Risk-based triggers configured (not 3DS on everything)
  • Frictionless and challenge results reviewed by issuer country and customer segment
  • Completed payments and fraud losses compared with the same segment before rollout; any lost margin fits the budget you set
  • Eligible fraud disputes showing liability shift

Scale Callout​

VolumeApproach
Under $100k/moUse processor default 3DS; minimal tuning; focus on working integration
$100k-$1M/moCustom risk rules; A/B test thresholds; optimize frictionless rate
Over $1M/moSophisticated risk model; exemption strategy; issuer-level analysis

Where This Breaks​

  • 3DS on every transaction, where it isn't required. Adds challenges you may not need. Be selective, and test.
  • No browser data passed. The issuer has less to go on, so more payments can end up in a challenge. Collect and pass device data.
  • Mobile challenge renders poorly. Test on actual devices; use native SDKs.
  • Ignoring exemptions (EU). Over-authenticating loyal customers. Ask your processor to request TRA where it qualifies.
  • Not tracking liability shift. Can't prove ROI. Tag transactions with 3DS result.

SCA Requirements (EU)​

Ask your processor which payments fall within SCA scope and which exemptions it can request. Selling to an EU customer alone doesn't decide it. See PSD2 and SCA for scope and provider conditions:

Must Authenticate​

  • Payments your processor identifies as requiring SCA
  • Payments where a requested exemption is unavailable or rejected

Exemption Eligible​

  • Eligible low-value remote payments up to 30 EUR, subject to cumulative checks
  • Same-amount, same-payee recurring series, after SCA at creation, amendment or first initiation as required. Merchant-initiated transactions are a separate case (Article 14)
  • Low-risk payments where the provider qualifies for TRA
  • Eligible corporate payment processes, rather than all B2B purchases

Provider Fraud Rates for TRA​

These are the payment provider's qualifying rates. REGULATION Regulation (EU) 2018/389, Articles 18-19 and Annex, for remote electronic card payments:

Provider fraud rate, by valueMaximum eligible payment
At or below 0.13%100 EUR
At or below 0.06%250 EUR
At or below 0.01%500 EUR

The provider measures fraudulent and unauthorized value across authenticated and exempt payments of that type, including recovered funds. Transaction risk checks still apply. Ask your processor which ceiling it can request. Checked 22 October 2026.


Next Steps​

After 3DS is live and stable:

  1. Tune thresholds: A/B test your risk triggers on completed-payment margin, authentication results and fraud costs old enough to read. A frictionless authentication can still give eligible protection, so it isn't a one-for-one trade
  2. Add exemptions (EU): Ask your processor which TRA ceiling it qualifies to request and verify the results
  3. Track liability shift: Check that eligible fraud disputes land on the issuer, not you
  4. Consider network tokens: Combine 3DS with network tokenization, then test whether approval rates move

Something wrong on this page? Email matt at paymentsandrisk.com and say what needs fixing.