> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/~/revisions/9QlGypixZFcbkq8oGjaF/explore-hyperswitch/workflows/3ds-decision-manager.md).

# 3DS / Strong Customer Authentication

3D Secure (3DS) is a robust security protocol designed to prevent fraud in card-not-present transactions. By employing multi-factor authentication mechanisms such as biometrics or OTPs, 3DS helps issuers verify the authenticity of transactions.

The **Hyperswitch 3DS Decision Manager** allows merchants to define advanced rules based on payment parameters, ensuring that 3DS authentication is selectively enforced for high-risk transactions.

### Benefits of Using the 3DS Decision Manager:

* **Fraud Reduction:** Enforce 3DS on high-risk transactions to mitigate fraudulent activities.
* **Enhanced Compliance:** Meet regulatory requirements for Strong Customer Authentication (SCA) in regions like the EEA.
* **Improved Customer Experience:** Apply 3DS only when necessary, minimizing friction during checkout for low-risk transactions.

Hyperswitch 3DS Decision Manager allows the merchant to configure advanced rules using various payment parameters such as amount, currency etc., to enforce 3D Secure authentication for card payments to reduce fraudulent transactions.

{% embed url="<https://youtu.be/-VTnngditlU>" %}

## How does it work?

#### 3DS Decision Flow:

Hyperswitch integrates with multiple payment processors, enabling seamless 3D Secure authentication.

<figure><img src="/files/LPhnmzf7iVKKgqmYmCGX" alt="" width="375"><figcaption><p>3DS Decision Flow</p></figcaption></figure>

The **3DS Decision Manager** in the Hyperswitch Control Center provides merchants with a rule-based interface to enforce authentication selectively.

For example: If you wish to enforce 3DS for transactions over $100, you can define a rule that automatically sets `authentication_type` as `three_ds` for such transactions. Payments meeting this rule will trigger 3DS authentication.

<figure><img src="/files/CUowXGBSq1G9HGiwSsm4" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}

* Rules set in the **3DS Decision Manager** can be overridden if an explicit value is passed in the `/payments` request using the `authentication_type` parameter. ([API Reference](https://api-reference.hyperswitch.io/api-reference/payments/payments--create))
* Some processors may mandate 3DS regardless of your configuration.
  {% endhint %}

{% content-ref url="/pages/ZfXkg0Mfi7wzPzFVaIY4" %}
[3DS Decision Manager](/~/revisions/9QlGypixZFcbkq8oGjaF/explore-hyperswitch/workflows/3ds-decision-manager/3ds-intelligence-engine/get-started-with-3ds-decision-manager.md)
{% endcontent-ref %}

{% content-ref url="/pages/l28HCGRBvHUVXZcSIrCF" %}
[Test a payment](/~/revisions/9QlGypixZFcbkq8oGjaF/hyperswitch-open-source/account-setup/test-a-payment.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hyperswitch.io/~/revisions/9QlGypixZFcbkq8oGjaF/explore-hyperswitch/workflows/3ds-decision-manager.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.