> 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/introduction/environment-setup.md).

# Environment Setup

As a new merchant, we recommend that you don't immediately start working in your production environment.

Instead, you should start your integration efforts in the test environment that Hyp sets up for you. Only move to production once you've done thorough testing and ensured your integration works well.

## Setting up a test environment

Once you've received credentials for the test environment (as shown in step 3 of [Prerequisites and Requirements](https://developers.hyp.co.il/enterprise/introduction/prerequisites-and-requirements.md)), you can start your integration efforts: for example, [implement the basic integration flow](https://developers.hyp.co.il/enterprise/introduction/basic-integration-flow-hello-world-with-a-full-working-charge.md).

The test environment is exactly the same as the production environment, with the following exceptions:

1. It performs mock transactions, not real transactions. In other words, it doesn't have any side effects outside of Hyp's own infrastructure. (One notable exception is [bit](https://developers.hyp.co.il/enterprise/available-payment-options/digital-wallets.md#bit): there's no testing environment for bit transactions.)
2. Mock transactions are still recorded inside the test environment's console, as if they were real transactions, allowing you to make sure your integration is stable before going live.

### Test cards

By default, the test terminals that Hyp sets up for you are connected to the credit card companies for authorization. Because of this, Hyp doesn't provide test cards directly. You should **contact the relevant card issuers** (Isracard, Cal, or Max) to obtain test cards for testing purposes.

Using test cards from the card issuers is recommended because they allow you to simulate various real-world scenarios, including successful transactions, declined transactions, and other authorization failures.

Alternatively, you can contact Hyp support and request a test terminal configured for **internal approval**, which doesn't send transactions to the credit card companies for authorization.

Internal approval terminals allow testing with synthetic card data, such as `4580458045804580` for the card number, `0729` for the card expiry, `000` for the CVV, and `000000000` for the Israeli ID. These terminals are convenient for basic end-to-end payment flow tests, but they don't allow you to simulate authorization failures such as declined transactions or incorrect ID numbers.

## Switching to production

When you've tested all the payment flows that you need in your test environment and are ready to go live, [contact Hyp support](mailto:cg-support@hyp.co.il) and ask to have a new production environment set up for you.

Migrating from the test environment to the production environment requires updating the following configuration information:

1. Base URL used for API requests
2. Username and password for API access
3. Terminal number
4. Merchant ID (MID)


---

# 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/introduction/environment-setup.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.
