> 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/integrations/connectors-integrations/3ds-providers/juspaythreedsserver.md).

# Juspay 3DS Server

Activate the Juspay 3DS Server connector in Hyperswitch and provide the merchant metadata required for standalone 3DS authentication.

Juspay 3DS Server handles standalone 3DS authentication for card payments. Enable it in the Hyperswitch Control Center, enter the merchant authentication metadata, then follow the external 3DS workflow guide.

### Status and capabilities

**Integration status:** alpha

**Category:** authentication provider

**Webhook flows:** None declared in code

*This connector declares no payment methods. It is an authentication provider rather than a payment processor.*

### Activation fields

The connector configuration declares `NoKey`. The Control Center does not ask for an API key or bearer token when you activate this connector.

The form also asks for a **Connector label**, a display name for the connector account. It is required and appears in the connectors table after activation.

Have these merchant-specific values ready, in the order the form shows them:

* **merchant\_country\_code:** Required text.
* **merchant\_name:** Required text.
* **ThreeDS requestor name:** Optional text.
* **ThreeDS request id:** Required text.
* **merchant\_category\_code:** Required text.
* **Pull Mechanism Enabled:** Required toggle. Controls how the payment proceeds after 3DS authentication: on (the default when unset) confirms the payment through the standard flow; off routes challenge completions through the decoupled challenge-notification flow.

### Activate the connector

1. Sign in to the [Hyperswitch Control Center](https://app.hyperswitch.io/).
2. Follow [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md).
3. Select **Juspay 3DS Server** and complete the activation fields above.
4. Follow [External 3DS with the Juspay 3DS Server](https://github.com/juspay/hyperswitch-docs/tree/main/integration-guide/workflows/3ds-decision-manager/external-3ds-with-the-juspay-3ds-server.md) to integrate the payment and browser steps.

### Webhooks

Handled webhook event wire values: **0**. The feature matrix declares no webhook flows. The connector's incoming-webhook methods return `WebhooksNotImplemented`.

### Troubleshooting

**The activation form asks for an API key**

The current connector configuration does not define an API key field. Confirm that you selected **Juspay 3DS Server**. Do not put an API key into a metadata field.

**The connector cannot be saved because metadata is missing**

Complete every required activation field above. Only **ThreeDS requestor name** is optional in the current configuration.

### Source reference

The activation fields and webhook behavior on this page are tied to Hyperswitch `c934d28c22cb7dbf3e6fcf58e39305556cc177ea`. See the [production connector configuration](https://github.com/juspay/hyperswitch/blob/c934d28c22cb7dbf3e6fcf58e39305556cc177ea/crates/connector_configs/toml/production.toml#L7043-L7079), [connector specification](https://github.com/juspay/hyperswitch/blob/c934d28c22cb7dbf3e6fcf58e39305556cc177ea/crates/hyperswitch_connectors/src/connectors/juspaythreedsserver.rs#L631-L674), and [connector validation](https://github.com/juspay/hyperswitch/blob/c934d28c22cb7dbf3e6fcf58e39305556cc177ea/crates/router/src/core/connector_validation.rs#L371-L379).


---

# 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/integrations/connectors-integrations/3ds-providers/juspaythreedsserver.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.