> For the complete documentation index, see [llms.txt](https://developers.hyp.co.il/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.hyp.co.il/enterprise/3-d-secure-integration/3ds-flow-in-payment-page.md).

# 3DS Flow in Payment Page

Apart from [registering for 3DS](https://developers.hyp.co.il/enterprise/3-d-secure-integration/service-registration.md) and having it activated in your Hyp Enterprise terminal, you as a merchant do not need to take any additional implementation steps to enable 3DS.

The resulting 3DS flow, based on version 2 of the protocol, works as follows:

1. You generate and display a payment page to the customer.
2. The customer enters their credit card details and clicks **Pay**.
3. Hyp receives the information and initiates a 3DS process with the card issuer.
4. If required, the card issuer prompts the customer to enter a one-time password (OTP) sent by SMS. The prompt varies by issuer — for example, with Max it looks like this:

   ![3DS prompt from Max](https://3255314327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQDmIAW4sQ20lCItJGzcS%2Fuploads%2Fgit-blob-41d20b2a1322a510465cfc0af97a74e3cf8973e1%2F3ds-popup.png?alt=media)
5. The customer enters the OTP, and the card issuer informs Hyp whether the challenge succeeded.
6. The card issuer's response is validated against the 3DS authentication service.
7. If the challenge succeeds, the transaction is processed normally.

## FAQ

### Can I customize the graphics of the 3DS screens?

No. The 3DS screens are provided directly by the card issuer and cannot be customized by Hyp.

### Does the card issuer always trigger an OTP challenge?

No. In some cases, the issuer may choose not to show an OTP challenge. Hyp has no control over whether a challenge is displayed.


---

# 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://developers.hyp.co.il/enterprise/3-d-secure-integration/3ds-flow-in-payment-page.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.
