# 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 credit card provider 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 credit card provider 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 offers built-in integration with all credit card provider 3DS mechanisms as part of its payment page. See [3DS Flow in the Payment Page](/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](/3-d-secure-integration/service-registration.md).

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

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. Your credit card provider controls the 3DS process.

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

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

In other words, 3DS gives you chargeback protection for customer-denied transactions.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developers.hyp.co.il/3-d-secure-integration/introduction-to-3ds.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.