Test Mode Overview

Zendit offers a dedicated test mode environment that is specifically designed for development and testing purposes. This environment allows you to seamlessly integrate with the Zendit API and utilize SDKs to pull catalogs and process transactions in a controlled testing environment. It provides a safe and sandboxed environment to ensure that your integrations are working correctly and your application is functioning as expected before moving to the production environment. By utilizing the test mode environment, you can thoroughly test your integrations, validate functionality, and troubleshoot any issues or errors, ensuring a smooth transition to the production environment.

Accessing the Test Mode Environment

When you create an account on zendit, it is automatically set to test mode. In this mode, you have access to the wallet management functionality and can retrieve API Keys to use with the zendit API or SDKs. Once you are ready to move to the production environment, you can upgrade your account. After the upgrade, you can toggle between the test mode and production mode in the console. This allows you to switch back to the test mode environment to manage your wallet balance if needed. It provides the flexibility to test and manage your wallet separately from the production environment, ensuring a smooth transition and efficient management of your account.

When you are in test mode on zendit, you will notice a border around the user console. This visual indicator helps you easily identify that you are operating in the test environment. If your account has been activated for production mode, you can use the toggle switch to switch between test mode and production mode. This allows you to seamlessly transition between the two environments, depending on your needs. The toggle switch provides a convenient way to switch the environment within the user console, ensuring a smooth workflow as you navigate between test and production environments.

In production mode on zendit, the border that indicates test mode is removed from the user console. This visual change serves as a clear indication that you are now operating in the production environment. By removing the border, zendit ensures that you can easily differentiate between test mode and production mode, helping you stay aware of the environment you are currently working in. This visual cue provides a helpful reminder to exercise caution and adhere to best practices when performing actions in the production mode of your zendit account

Managing the Test Mode Wallet

In zendit’s test mode, you have the flexibility to manage your test mode wallet by setting the balance to any desired amount. This feature enables you to simulate various scenarios during testing. For instance, you can set a low or depleted balance to test scenarios where transactions fail due to insufficient funds. Alternatively, you can set higher values to test the processing of a large volume of transactions and ensure that your integration is functioning properly.

It’s important to note that transactions in test mode are processed using simulators for service providers. These simulators mimic the behavior of real top-up transactions but do not perform actual top-ups or involve real funds. The funds in the test mode wallet are simulated and do not require any payment to fund them. This allows you to thoroughly test and validate your integration without incurring any financial costs.

By providing this flexible and simulated environment, zendit empowers you to confidently test various scenarios and ensure the smooth operation of your integration before transitioning to the production environment.

To add funds to your wallet in Zendit, follow these steps:

1. Go to the wallet section in the user console.
2. Look for the option to “Modify Balance” and select it.
3. A pop-up dialog will appear, displaying the current balance of your wallet.
4. In the input field provided, enter the desired value to set the new balance.
5. Once you have entered the desired amount, click on the “Confirm” button.
6. Zendit will create a wallet transaction to modify the balance of your wallet to the specified value.

By following these steps, you can easily add funds to your wallet and ensure that it has the desired balance for processing transactions.

Accessing the API Key

To access your API Key in Zendit, follow these steps:

1. Open the user console and navigate to the API Settings section.
2. In the API Key section, you will see a dropdown menu for selecting the desired mode: Test Mode or Production.
3. Choose the mode for which you want to access the API Key.
4. To view the API Key, click on the button that is the eye with a slash through it next to the key. This will display the API Key on the screen.
5. If you prefer to copy the API Key to your clipboard, click on the copy button next to the key. This will save the API Key to your clipboard, allowing you to easily paste it into the configuration settings of your integration.

By following these steps, you can access and retrieve your API Key in Zendit, whether you are in Test Mode or Production Mode, and use it for your integration purposes

If your account has not been set up for production, you will only have the option to select the Sandbox key in the API Settings section.

Using Test Mode on the API

o test the API using Swagger, follow these steps:

1. Copy your test key from the user console.
2. Open the test environment Swagger.
3. In the Swagger interface, locate and click the “Authorize” button.
4. A dialog box will appear where you can enter your API key. Enter your key as “Bearer <your key>”, replacing <your key> with the value you copied from the console.
5. Click the “Authorize” button to authenticate with your API key.
6. Once authorized, you can try out any of the API methods available in Swagger to familiarize yourself with using the API.

If you are using a generated client or an SDK provided by zendit, you will need to set the API key in your configuration. This allows the client to authenticate against the API using your key, enabling you to test your integration seamlessly.