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), you can start your integration efforts: for example, implement the basic integration flow.

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: 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.

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 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)