Environments
Sandbox and Production environments within an instance.
Each instance has two environments.
production- The environment intended for use within your live application.sandbox- The environment intended for use by developers to test transactions and within your test or quality assurance systems.
These two environments have separate infrastructures so resources such as buyers and payment services are not shared between them. This also means that there are different hostnames for sandbox and production APIs and dashboards.
The hostnames for the APIs are as follows:
| Environment | Hostname |
|---|---|
| sandbox | sandbox.efundpay.com |
| production | api.efundpay.com |
Use credentials, merchant account ids, site merchant ids, and RSA keys from the same environment. Do not mix sandbox and production values in one request.
Sandbox Demo Credentials
Public sandbox demo credentials
The credentials below are intentionally published in the documentation site and are only for sandbox testing. Do not configure production keys, real merchant private keys, or customer data here.
Direct API integration
| API Key | sk_test_your_direct_key |
|---|---|
| X-MERCHANT-ACCOUNT-ID | acct_your_direct_account_id |
| JWT header kid | kid_your_direct_key_id |
| RSA private key | |
Checkout integration
| API Key | sk_test_your_checkout_key |
|---|---|
| X-MERCHANT-ACCOUNT-ID | acct_your_checkout_account_id |
| JWT header kid | kid_your_checkout_key_id |
| RSA private key | |
Webhook public RSA key
your_webhook_public_rsa_keyTogether with the environment (sandbox or production) it is used to connect to the right APIs.
You can test payment services, card rules, and other settings in the sandbox environment, before migrating them to the production environment.
Why environments?
Environments are an essential part of any development process. Your developer might run your application on their development machine, and to try and test the integration they will want to try and create some payments. To stop your dashboard from being populated with lots of testing data it would be best for the developer to create their test transactions against the sandbox environment instead.
Similarly, you might want to run either automated or manual tests against the API as part of QA and testing. To stop this from interfering with your live environments you could set these tests to run against the sandbox environment.
Environments and payment service APIs
The environment determines which payment service API environment that should connect to. For example, transactions made in the sandbox environment is processed by the Braintree sandbox environment, while transactions made in the production environment are processed by the live environment.
Other actions such as registering a digital wallet are also dependent on the environment. Apple Pay digital wallets registered using the sandbox environment will be registered with Apple Pay's sandbox environment. This wallet will not be recognized by Apple Pay's live environment and thus cannot be used in production.
In short, the production environment always connects to the live API of a payment service, whereas the sandbox environment always connects to its sandbox API.