Product

6
MIN READ

When should you enable 3DS? And when it holds back your conversion

Zru Team

Isabel Martín

Business Development

Updated

Published

Configuration of selective 3D Secure showing the "Risk only" option enabled with a fraud score threshold above 20
Table of contents

Applying 3DS across the board to every transaction only makes sense if you don't have a scoring system or when fraud exceeds TRA (Transaction Risk Analysis) thresholds. In every other case, you're paying with conversion for insurance you don't always need.

And yet most businesses end up doing it anyway: without an optimized system, changing it depends on the tech team, and that gets in the way of making changes quickly.

What is the real cost of 3DS on every transaction?

The real cost of 3DS lies in the challenge flow: according to a Forter analysis using data from Amazon and Microsoft, abandonment rates due to 3DS friction exceeded 40% in Spain and France during the PSD2 rollout (2020). And not because customers don't want to pay, but for reasons that have nothing to do with fraud: they're on their phone, the SMS takes too long, or they simply drop out of the process.

That percentage climbs in channels where friction weighs even more: in-app purchases, low ticket sizes, new customers who don't have their banking app on their phone yet. That's why the challenge has a real cost and isn't always justified.

To put it in context, 3D Secure is an authentication protocol that steps in at the moment of payment. Three parties are involved: the acquirer (the bank or PSP processing the payment), the card-issuing bank, and the card scheme (Visa, Mastercard). If you want to understand how it works in detail, we explain it step by step in this article: 3D Secure: what it is, how it works, and how it protects against fraud.

What matters here is the difference between the two possible flows: frictionless and challenge.

When 3DS is triggered, one of two things can happen:

  • In the frictionless flow, the issuing bank analyzes the transaction in the background and lets the payment through without the user doing anything.

  • In the challenge flow, the buyer has to verify their identity through their banking app, an SMS, or biometrics.

Diagram of the three possible flows in a card payment: with 3DS challenge (the buyer authenticates), with 3DS frictionless (the buyer does nothing), and without 3DS

When 3DS on every transaction does make sense

There are scenarios where applying 3DS universally is the right call:

  • When fraud volume is high and you don't have a scoring system to tell risky transactions apart from those that aren't.

  • When you operate in markets where issuing banks require it anyway, regardless of how you configure it, as in India, where the RBI mandates strong authentication on all digital card transactions.

  • When you're a new business without enough data to set a risk threshold with confidence.

In these cases, the liability shift that 3DS provides (fraud liability moves to the issuing bank instead of the merchant) outweighs the impact on conversion, and 3DS is the most direct way to get it.

Which SCA exemptions allow payments to be processed without 3DS

Selective 3DS is compliant with PSD2 because, while PSD2 requires 3DS in Europe, it also defines exemptions. These are cases where a payment can be processed without strong authentication; they're part of a regulatory framework that exists precisely so that not every transaction gets weighed down with friction.

Low value

Payments under 30 euros. The issuing bank can exempt the transaction, although once there have been more than 5 consecutive exempt payments or more than 100 euros in total since the last authentication, it no longer applies.

TRA (Transaction Risk Analysis)

The exemption that can recover the most conversion if used well. To apply it, the acquirer has to be below certain fraud thresholds:

  • Fraud below 0.13% → exemption for transactions up to 100 euros

  • Fraud below 0.06% → up to 250 euros

  • Fraud below 0.01% → up to 500 euros

These thresholds apply to the acquirer, not the merchant. The PSP you work with directly affects which exemptions you can request. If your acquirer has a high fraud rate, you won't be able to use this exemption even if yours is low.

MIT (Merchant-Initiated Transactions)

For recurring payments, authentication is only needed once. The customer authenticates on the first charge and subsequent charges are exempt from the challenge, as long as they're referenced to that initial authentication. This applies whether the amount is fixed or variable.

Trusted beneficiaries

The buyer can add a merchant to their trusted list. Subsequent transactions with that merchant don't trigger a challenge. It isn't widely implemented across issuers yet, but it's part of the protocol.

None of these exemptions guarantee that the issuing bank will accept them. The issuer always has the final say. But they have a real impact on the challenge rate if the acquirer requests them correctly.

SCA exemptions at a glance

Exemption

Condition

Requires 3DS?

Liability if fraud

Low Value

< €30 (max. 5 uses or €100 accumulated)

No

Merchant

TRA

Acquirer fraud < 0.13% (up to €100)

No

Merchant

MIT

Recurring payment referenced to initial auth

No

Merchant

Trusted Beneficiary

Merchant saved as trusted by the customer

No

Merchant

No exemption

All other cases

Yes

Issuer

How selective 3DS works in practice

Applying 3DS only to risky transactions requires two things:

  • a system that calculates the risk of each transaction (fraud scoring)

  • a flow that acts based on that risk (orchestration flow)

Fraud scoring

Fraud scoring assigns a score to each transaction based on variables such as the amount, the card's issuing country, the customer's history, the device, or the IP address. The higher the score, the higher the estimated risk.

In Zru, each company sets its own thresholds. A selective flow could be configured like this, for example:

  • Score < 20 → the payment proceeds without 3DS

  • Score between 20 and 99 → 3DS is triggered before processing

  • Score ≥ 100 → the transaction is blocked

Zru orchestration flow with three routes based on fraud score: score below 20 goes directly to payment without 3DS, score between 20 and 100 runs 3DS Agnostic before processing, and all others are rejected

Scoring determines when to trigger 3DS. Low-risk transactions go through without authentication. Those above the threshold enter the 3DS flow before being processed.

There's a direct implication of selective 3DS worth being clear about: when the scoring decides not to trigger 3DS and that transaction turns out to be fraudulent, the merchant absorbs the chargeback, since there's no liability shift without authentication.

That's why scoring isn't just a conversion tool but also a risk decision: every transaction that skips 3DS is one where liability stays with the business if it turns out to be fraudulent. The same applies to any exemption: Low Value, TRA, MIT, or Trusted Beneficiary. When the merchant requests the exemption and there's no authentication, the chargeback falls on them. A well-calibrated threshold protects conversion without significantly increasing fraud exposure, but a poorly calibrated one increases risk and leads to direct losses.

At the same time, the scoring layer doesn't replace the processor's fraud tools (Stripe Radar, Adyen RevenueProtect). It sits on top of them, before the transaction reaches the processor. And if you work with multiple processors, the logic is applied consistently across all of them, from a single place.

Orchestration flow

To apply that logic to the payment flow, you need a system that sends the payment down different routes based on the fraud score. That's what payment orchestration systems are for. Without a payment routing system, the decision of whether or not to apply 3DS can't be automated.

Next, we'll look at how this routing can be implemented.

How to implement selective 3DS without depending on IT

There are two ways to implement selective 3DS: build the logic in-house or use a payment orchestration provider like Zru that lets you configure it directly. Let's look at why.

Most payments teams know selective 3DS matters. The difficulty lies in implementation, because any change to the flow has to go through IT.

Without a payment orchestration provider, changing anything in the 3DS flow means contacting the company's IT team and waiting for them to prioritize and carry it out, which can take anywhere from a few hours to a few weeks.

On the other hand, if you're using a payment orchestration provider that doesn't let merchants make changes to the orchestration themselves, the payments team has to contact the orchestrator's team and request the changes. That approach isn't agile day to day either.

In Zru, the payments team configures the 3DS flow directly from the orchestration dashboard. Scoring thresholds, fraud rules, and the logic for when to trigger the challenge are all adjusted from the same place, without touching code. Changes are published in seconds and take effect immediately.

This also means that when a new fraud pattern appears, the response can be instant. And that way, whenever the payments team makes a decision, it doesn't depend on IT.

Where to start if you currently apply 3DS to every transaction

Before changing anything, it's worth reviewing your current data:

  • Challenge rate. What percentage of transactions go through user authentication?

  • Challenge abandonment rate. How many users don't complete the process?

  • Risk distribution. Of the transactions that do reach a challenge, how many turn out to be actual fraud?

If challenge abandonment is high and fraud among those transactions is low, you're losing conversion on transactions that don't warrant it.

The next step is to define a basic scoring model, and you can start with just a few variables (amount, issuing country, customer history) and refine it over time.

In Zru you can configure it from the dashboard, with no development work, and see the effect in real time. If you'd like to review how it would fit into your current flow, the team can go through that with you.

Going deeper


















Preguntas frecuentes

What happens if I don’t activate 3DS and the transaction turns out to be fraud?

The merchant absorbs the chargeback. Without authentication there is no liability shift, so responsibility does not transfer to the issuing bank. That’s why the scoring needs to be properly calibrated.

What happens if I don’t activate 3DS and the transaction turns out to be fraud?

The merchant absorbs the chargeback. Without authentication there is no liability shift, so responsibility does not transfer to the issuing bank. That’s why the scoring needs to be properly calibrated.

What happens if I don’t activate 3DS and the transaction turns out to be fraud?

The merchant absorbs the chargeback. Without authentication there is no liability shift, so responsibility does not transfer to the issuing bank. That’s why the scoring needs to be properly calibrated.

Do I approve SCA exemptions as a merchant?

Not directly. Exemptions are requested by the acquirer, but the issuing bank always has the final say. If the issuer decides not to accept it, the transaction may still go to challenge.

Do I approve SCA exemptions as a merchant?

Not directly. Exemptions are requested by the acquirer, but the issuing bank always has the final say. If the issuer decides not to accept it, the transaction may still go to challenge.

Do I approve SCA exemptions as a merchant?

Not directly. Exemptions are requested by the acquirer, but the issuing bank always has the final say. If the issuer decides not to accept it, the transaction may still go to challenge.

Do I need IT to configure selective 3DS?

Not with Zru. The entire flow, including 3DS configuration, is managed from the orchestration panel without touching code. Changes are published in seconds and take effect immediately.

Do I need IT to configure selective 3DS?

Not with Zru. The entire flow, including 3DS configuration, is managed from the orchestration panel without touching code. Changes are published in seconds and take effect immediately.

Do I need IT to configure selective 3DS?

Not with Zru. The entire flow, including 3DS configuration, is managed from the orchestration panel without touching code. Changes are published in seconds and take effect immediately.

Product

6
MIN READ

When should you enable 3DS? And when it holds back your conversion

Zru Team

Isabel Martín

Business Development

Updated

Published

Configuration of selective 3D Secure showing the "Risk only" option enabled with a fraud score threshold above 20
Table of contents

Applying 3DS across the board to every transaction only makes sense if you don't have a scoring system or when fraud exceeds TRA (Transaction Risk Analysis) thresholds. In every other case, you're paying with conversion for insurance you don't always need.

And yet most businesses end up doing it anyway: without an optimized system, changing it depends on the tech team, and that gets in the way of making changes quickly.

What is the real cost of 3DS on every transaction?

The real cost of 3DS lies in the challenge flow: according to a Forter analysis using data from Amazon and Microsoft, abandonment rates due to 3DS friction exceeded 40% in Spain and France during the PSD2 rollout (2020). And not because customers don't want to pay, but for reasons that have nothing to do with fraud: they're on their phone, the SMS takes too long, or they simply drop out of the process.

That percentage climbs in channels where friction weighs even more: in-app purchases, low ticket sizes, new customers who don't have their banking app on their phone yet. That's why the challenge has a real cost and isn't always justified.

To put it in context, 3D Secure is an authentication protocol that steps in at the moment of payment. Three parties are involved: the acquirer (the bank or PSP processing the payment), the card-issuing bank, and the card scheme (Visa, Mastercard). If you want to understand how it works in detail, we explain it step by step in this article: 3D Secure: what it is, how it works, and how it protects against fraud.

What matters here is the difference between the two possible flows: frictionless and challenge.

When 3DS is triggered, one of two things can happen:

  • In the frictionless flow, the issuing bank analyzes the transaction in the background and lets the payment through without the user doing anything.

  • In the challenge flow, the buyer has to verify their identity through their banking app, an SMS, or biometrics.

Diagram of the three possible flows in a card payment: with 3DS challenge (the buyer authenticates), with 3DS frictionless (the buyer does nothing), and without 3DS

When 3DS on every transaction does make sense

There are scenarios where applying 3DS universally is the right call:

  • When fraud volume is high and you don't have a scoring system to tell risky transactions apart from those that aren't.

  • When you operate in markets where issuing banks require it anyway, regardless of how you configure it, as in India, where the RBI mandates strong authentication on all digital card transactions.

  • When you're a new business without enough data to set a risk threshold with confidence.

In these cases, the liability shift that 3DS provides (fraud liability moves to the issuing bank instead of the merchant) outweighs the impact on conversion, and 3DS is the most direct way to get it.

Which SCA exemptions allow payments to be processed without 3DS

Selective 3DS is compliant with PSD2 because, while PSD2 requires 3DS in Europe, it also defines exemptions. These are cases where a payment can be processed without strong authentication; they're part of a regulatory framework that exists precisely so that not every transaction gets weighed down with friction.

Low value

Payments under 30 euros. The issuing bank can exempt the transaction, although once there have been more than 5 consecutive exempt payments or more than 100 euros in total since the last authentication, it no longer applies.

TRA (Transaction Risk Analysis)

The exemption that can recover the most conversion if used well. To apply it, the acquirer has to be below certain fraud thresholds:

  • Fraud below 0.13% → exemption for transactions up to 100 euros

  • Fraud below 0.06% → up to 250 euros

  • Fraud below 0.01% → up to 500 euros

These thresholds apply to the acquirer, not the merchant. The PSP you work with directly affects which exemptions you can request. If your acquirer has a high fraud rate, you won't be able to use this exemption even if yours is low.

MIT (Merchant-Initiated Transactions)

For recurring payments, authentication is only needed once. The customer authenticates on the first charge and subsequent charges are exempt from the challenge, as long as they're referenced to that initial authentication. This applies whether the amount is fixed or variable.

Trusted beneficiaries

The buyer can add a merchant to their trusted list. Subsequent transactions with that merchant don't trigger a challenge. It isn't widely implemented across issuers yet, but it's part of the protocol.

None of these exemptions guarantee that the issuing bank will accept them. The issuer always has the final say. But they have a real impact on the challenge rate if the acquirer requests them correctly.

SCA exemptions at a glance

Exemption

Condition

Requires 3DS?

Liability if fraud

Low Value

< €30 (max. 5 uses or €100 accumulated)

No

Merchant

TRA

Acquirer fraud < 0.13% (up to €100)

No

Merchant

MIT

Recurring payment referenced to initial auth

No

Merchant

Trusted Beneficiary

Merchant saved as trusted by the customer

No

Merchant

No exemption

All other cases

Yes

Issuer

How selective 3DS works in practice

Applying 3DS only to risky transactions requires two things:

  • a system that calculates the risk of each transaction (fraud scoring)

  • a flow that acts based on that risk (orchestration flow)

Fraud scoring

Fraud scoring assigns a score to each transaction based on variables such as the amount, the card's issuing country, the customer's history, the device, or the IP address. The higher the score, the higher the estimated risk.

In Zru, each company sets its own thresholds. A selective flow could be configured like this, for example:

  • Score < 20 → the payment proceeds without 3DS

  • Score between 20 and 99 → 3DS is triggered before processing

  • Score ≥ 100 → the transaction is blocked

Zru orchestration flow with three routes based on fraud score: score below 20 goes directly to payment without 3DS, score between 20 and 100 runs 3DS Agnostic before processing, and all others are rejected

Scoring determines when to trigger 3DS. Low-risk transactions go through without authentication. Those above the threshold enter the 3DS flow before being processed.

There's a direct implication of selective 3DS worth being clear about: when the scoring decides not to trigger 3DS and that transaction turns out to be fraudulent, the merchant absorbs the chargeback, since there's no liability shift without authentication.

That's why scoring isn't just a conversion tool but also a risk decision: every transaction that skips 3DS is one where liability stays with the business if it turns out to be fraudulent. The same applies to any exemption: Low Value, TRA, MIT, or Trusted Beneficiary. When the merchant requests the exemption and there's no authentication, the chargeback falls on them. A well-calibrated threshold protects conversion without significantly increasing fraud exposure, but a poorly calibrated one increases risk and leads to direct losses.

At the same time, the scoring layer doesn't replace the processor's fraud tools (Stripe Radar, Adyen RevenueProtect). It sits on top of them, before the transaction reaches the processor. And if you work with multiple processors, the logic is applied consistently across all of them, from a single place.

Orchestration flow

To apply that logic to the payment flow, you need a system that sends the payment down different routes based on the fraud score. That's what payment orchestration systems are for. Without a payment routing system, the decision of whether or not to apply 3DS can't be automated.

Next, we'll look at how this routing can be implemented.

How to implement selective 3DS without depending on IT

There are two ways to implement selective 3DS: build the logic in-house or use a payment orchestration provider like Zru that lets you configure it directly. Let's look at why.

Most payments teams know selective 3DS matters. The difficulty lies in implementation, because any change to the flow has to go through IT.

Without a payment orchestration provider, changing anything in the 3DS flow means contacting the company's IT team and waiting for them to prioritize and carry it out, which can take anywhere from a few hours to a few weeks.

On the other hand, if you're using a payment orchestration provider that doesn't let merchants make changes to the orchestration themselves, the payments team has to contact the orchestrator's team and request the changes. That approach isn't agile day to day either.

In Zru, the payments team configures the 3DS flow directly from the orchestration dashboard. Scoring thresholds, fraud rules, and the logic for when to trigger the challenge are all adjusted from the same place, without touching code. Changes are published in seconds and take effect immediately.

This also means that when a new fraud pattern appears, the response can be instant. And that way, whenever the payments team makes a decision, it doesn't depend on IT.

Where to start if you currently apply 3DS to every transaction

Before changing anything, it's worth reviewing your current data:

  • Challenge rate. What percentage of transactions go through user authentication?

  • Challenge abandonment rate. How many users don't complete the process?

  • Risk distribution. Of the transactions that do reach a challenge, how many turn out to be actual fraud?

If challenge abandonment is high and fraud among those transactions is low, you're losing conversion on transactions that don't warrant it.

The next step is to define a basic scoring model, and you can start with just a few variables (amount, issuing country, customer history) and refine it over time.

In Zru you can configure it from the dashboard, with no development work, and see the effect in real time. If you'd like to review how it would fit into your current flow, the team can go through that with you.

Going deeper


















Preguntas frecuentes

What happens if I don’t activate 3DS and the transaction turns out to be fraud?

The merchant absorbs the chargeback. Without authentication there is no liability shift, so responsibility does not transfer to the issuing bank. That’s why the scoring needs to be properly calibrated.

Do I approve SCA exemptions as a merchant?

Not directly. Exemptions are requested by the acquirer, but the issuing bank always has the final say. If the issuer decides not to accept it, the transaction may still go to challenge.

Do I need IT to configure selective 3DS?

Not with Zru. The entire flow, including 3DS configuration, is managed from the orchestration panel without touching code. Changes are published in seconds and take effect immediately.

Subscribe to our newsletter

START NOW

Talk to a payments expert

Tell us about your situation and we'll show you in 30 minutes how Zru can improve your operations.

No commitments or long-term contracts

One integration, access to the entire ecosystem

Dedicated support from day one

Call us now

We’re available Monday to Friday.

Verification slider. Slide to verify you are not a robot.
I am not a Robot