IC API Sandbox

The IC API offers a sandbox environment for developers to test their integration and simulate different scenarios and error cases. In this section, we'll explore the features and benefits of the IC API sandbox environment, along with the steps involved in using it. However, this is optional and partners can directly integrate in UAT phase.

Benefits of the Sandbox Environment

The IC API sandbox environment provides several benefits for developers:

  • Testing: The sandbox environment allows developers to test their integration with the API and ensure that it is functioning correctly.
  • Simulation: Developers can use the sandbox environment to simulate different scenarios and error cases, such as compliance checks, rejections, and acceptances.
  • Isolation: The sandbox environment is isolated from the production environment, so developers can test and experiment without affecting live transactions.
  • Security: The sandbox environment provides a secure testing environment, with the same security protocols and features as the production environment.

Using the Sandbox Environment

To use the IC API sandbox environment сonsult the API Reference and guidelines for information on any differences or limitations in the sandbox environment. However, certain endpoints and features may not be available in the sandbox environment or may behave differently than in the production environment

Users and endpoints:

Different endpoints require different user types to successfully process a request. The below table illustrates which methods each user type triggers:

Endpoint NameUser Access LevelAgent Type
Get BalanceFirst-Level / Single-LevelSender / Both
Get Agent ListFirst-Level / Single-LevelSender / Both
Get Updated Agent ListFirst-Level / Single-LevelSender / Both
Get Anywhere Payout NetworkFirst-Level / Single-LevelSender / Both
Get Bank BranchesFirst-Level / Single-LevelSender / Both
Get CitiesFirst-Level / Single-LevelSender / Both
Get Exchange RateFirst-Level / Single-LevelSender / Both
Get Charge SlabFirst-Level / Single-LevelSender / Both
Get ModalitiesFirst-Level / Single-LevelSender / Both
Get Receiving CountriesFirst-Level / Single-LevelSender / Both
Get StatesFirst-Level / Single-LevelSender / Both
Get Transaction DetailsFirst-Level / Single-LevelSender / Both
Get Transaction ReportAllAll
Get list of transactionsFirst-Level / Single-LevelSender / Both
Generate ICTCFirst-Level / Single-LevelSender / Both
Create a transactionFirst-Level / Single-LevelSender / Both
Authorize temporary transactionSupervisorSender / Both
Cancel a transactionFirst-Level / Single-LevelSender / Both
Modify a transactionFirst-Level / Single-LevelSender / Both
Change PasswordAllAll
Get Static DataAllAll
* Update Transaction StatusAllAll
Get Outstanding RemittanceFirst-Level / Single-Level / ReceiverReceiver / Both
Get ICTC payment statusFirst-Level / Single-Level / ReceiverReceiver / Both
Receive PaymentFirst-Level / Single-Level / ReceiverReceiver / Both
Unlock a transactionFirst-Level / Single-Level / ReceiverReceiver / Both
Confirm a transactionFirst-Level / Single-Level / ReceiverReceiver / Both

* - Applicable for Sandbox environment only.

Note:

  • Ensure to integrate all the relevant methods listed above according to the type of partner/integration. In case you are not integrating a few methods, you must present the Business Cases while development. Once development and UAT are done, check list will be shared by IC OPS Team for signoff.
  • In the future, new fields may be added to the response bodies of any endpoint. We recommend implementing your system in a flexible manner so that the addition of new fields does not break your integration. It is essential to design your system to accommodate these changes seamlessly to ensure continued functionality.

Important Notice for Sandbox Environment Users

Sandbox Environment is open for all users who want to experience Instant Cash REST APIs. It is designed strictly for testing purposes. We strongly advise against sending real data to the Sandbox, as it is not designed to handle sensitive or personal information. It is the API user's responsibility to protect their data by ensuring that no real information is transmitted to non-production environments. Failure to comply with this guideline may expose your data to risks. Please exercise due diligence and use this environment strictly within its designated boundaries to protect your information.