> 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/service-registration.md).

# Registering for 3DS

3-D Secure (3DS) is managed by [your acquirer](https://developers.hyp.co.il/enterprise/introduction/prerequisites-and-requirements.md#1-sign-a-credit-card-acquiring-agreement), such as Isracard, Cal, or Max. Its availability depends on how your merchant profile is configured by the acquirer.

To activate 3DS, you will need:

1. An Internet-enabled **vendor number** (מספר ספק אינטרנטי) from your acquirer. You should already have this from your acquiring agreement.
2. A valid **merchant category code (MCC)**, sometimes called a "branch code", assigned by your acquirer. This code identifies your business type for card networks and is required for 3DS processing. In most cases, enabling 3DS does not require signing a separate contract with your acquirer — instead, the acquirer updates your existing merchant profile with the necessary settings. Contact your acquirer to confirm what you need to do to obtain an MCC.

Once you have both, [contact your Hyp support representative](mailto:cg-support@hyp.co.il) to activate 3DS on your terminal. You can also request test cards issued by Hyp's default 3DS provider.

When Hyp enables 3DS on your terminal, it acts as a passthrough to your acquirer's 3DS configuration. If your acquirer's 3DS setup supports a specific card brand, so will Hyp, and vice versa.


---

# 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/service-registration.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.
