> 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/introduction-to-3ds.md).

# Introduction to 3-D Secure (3DS)

3-D Secure (3DS) helps prevent fraud in online card transactions.

3DS creates a safer transaction environment and reduces card misuse and customer chargebacks. The card issuer confirms the validity of a transaction using two-factor authentication via the customer's phone, email, or another method of their choice. As a result, you as a merchant are protected against chargebacks because the card issuer assumes liability for any losses from the transaction.

For more information about 3DS, see the [EMVCo website](https://www.emvco.com/emv-technologies/3-d-secure/).

Hyp Enterprise offers built-in integration with all 3DS mechanisms offered by card issuers as part of its payment page. See [3DS Flow in the Payment Page](https://developers.hyp.co.il/enterprise/3-d-secure-integration/3ds-flow-in-payment-page.md) for details.

## FAQ

### Are there any prerequisites for enabling 3DS in your payment page?

Yes. See [Registering for 3DS](https://developers.hyp.co.il/enterprise/3-d-secure-integration/service-registration.md).

### What are the costs of using 3DS in Hyp Enterprise?

Each 3DS action incurs the following costs:

* Up to 200 actions: ₪2 per action
* 201–500 actions: ₪1.8 per action
* 501–1000 actions: ₪1.2 per action
* 1001+ actions: ₪0.8 per action

### Does Hyp control 3DS?

No. Hyp is just a passthrough for 3DS. The customer's card issuer controls the 3DS process.

### What does it mean when 3DS is successful?

When the card issuer verifies a transaction using 3DS, they assume liability. This means that if a customer denies the transaction, the card issuer covers any losses.

In other words, 3DS gives you chargeback protection for customer-denied 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://developers.hyp.co.il/enterprise/3-d-secure-integration/introduction-to-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.
