> 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/integration-guide/workflows/3ds-decision-manager.md). # 3DS / Strong Customer Authentication Implement 3D Secure and Strong Customer Authentication for payments **Juspay Hyperswitch** provides comprehensive 3D Secure (3DS) authentication capabilities. 3D Secure (3DS) is an authentication protocol that adds an extra layer of protection to card transactions. It helps confirm that the person making the purchase is the legitimate cardholder, reducing the risk of fraud for both businesses and customers. When 3DS is triggered, the issuing bank may prompt the cardholder to authenticate using methods such as a password, a one-time code sent to their mobile device, or biometric verification. Many customers recognize this experience through familiar card network brands like Visa Secure, Mastercard Identity Check, or American Express SafeKey. Strong Customer Authentication (SCA), introduced under PSD2 in the European Economic Area and reflected in similar regulations in the UK, India, Japan, and Australia, may require the use of 3DS for certain card payments. In other regions, 3DS remains optional but can still be used strategically to help reduce fraud.
Authenticate with 3D Secure via PSPPerform 3D Secure (3DS) via the PSP that is processing the transaction
Standalone 3D Secure
(via Hyperswitch)		Run 3D Secure (3DS) via any 3DS server (Juspay, Netcetera, 3DSecure.io) while processing the subsequent payment on a third party gateway
Import 3D Secure resultsProcess payments via Hyperswitch when 3DS Secure (3DS) runs outside Hyperswitch
3D secure Intelligence EngineUse Rules and SCA exemptions to reduce cardholder friction on eligible transactions
--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.hyperswitch.io/integration-guide/workflows/3ds-decision-manager.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.