> 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/external-authentication-for-3ds.md).

# Standalone 3D Secure (via Hyperswitch)

Use a standalone 3DS server to authenticate a cardholder before authorizing the payment with a payment processor.

Standalone 3DS separates cardholder authentication from payment authorization. Use it when a dedicated 3DS provider should authenticate the cardholder before your payment processor authorizes the payment.

Set `request_external_three_ds_authentication` on the payment to request this path. When browser work is required, the payment can return a `three_ds_invoke` next action.

## Choose the provider guide

Provider setup and browser handling differ. Use the guide for the 3DS provider you configured:

* [Juspay 3DS Server browser walkthrough](/integration-guide/workflows/3ds-decision-manager/external-3ds-with-the-juspay-3ds-server.md)
* [3DS provider setup pages](https://github.com/juspay/hyperswitch-docs/tree/main/integration-space/connectors-integrations/3ds-providers/README.md)

For processor-managed 3DS, use [Authenticate with 3D Secure via PSP](/integration-guide/workflows/3ds-decision-manager/authenticate-with-3d-secure-via-psp.md) instead.


---

# 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/external-authentication-for-3ds.md?ask=<question>&goal=<user_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.