Working in the Sandbox

Token's sandbox is a software testing environment enabling isolated execution of API functionality for independent evaluation, monitoring or testing. The idea is to be able to test API features and code integration with or without your project in ideal conditions, emulating a production environment and its behaviours to test the functionality of the Token API with notional banks, account information and transaction values. Working in the sandbox, TPP developers can check and validate their code by testing it against a specific web service without creating unforeseen impacts within their normal operating environment and business processes.

As pictured above (click to enlarge), our sandbox is compromised of three major areas:

  • Documentation – the guidance package you're currently reading. You can access this resource at any time from the sandbox. You can also access Documentation from its link in the navigation panel on the left side of the dashboard UI.
  • Testing – combined with the API's Swagger specification, this tool lets you simulate bank connectivity using relevant parameters and data so you can see how individual API features perform and the response details you'll receive for each well-defined request.
  • Payload Builder – generates an authorization token you can use for integration testing with your application. You can select either an API key or signing for authentication. You can also specify a callback URL for testing purposes to validate successful redirection and execution.

A word about testing with notional banks. Although Token's demo banks — also called notional banks — can be used to test your integration with the Token API in our sandbox environment, they should never be used for production testing.

To test your PIS integration in the sandbox, you should ideally use one bank for the source account (e.g., requestPayload.transferBody.instructions.source) and the other for the transfer destination (e.g., requestPayload.transferBody.instructions.transferDestinations). The account properties you assign will need to adhere to the object and field definitions for the endpoint being tested. Required objects and fields are labelled accordingly. All others are optional.

Presuming your test request is successful, the populated fields you receive in the response from the notional source bank will adhere to the applicable definition (click to enlarge):

Definition and format rules apply in the sandbox, as well as in production. You can find object-field definitions for each supported endpoint in Swagger Object and Field Definitions. Simply click an item to expand its contents.

Next, let's take a brief look at each area of the sandbox and how to use it.

Working in the Sandbox

Token's sandbox is a software testing environment enabling isolated execution of API functionality for independent evaluation, monitoring or testing. The idea is to be able to test API features and code integration with or without your project in ideal conditions, emulating a production environment and its behaviours to test the functionality of the Token API with notional banks, account information and transaction values. Working in the sandbox, TPP developers can check and validate their code by testing it against a specific web service without creating unforeseen impacts within their normal operating environment and business processes.

As pictured above (click to enlarge), our sandbox is compromised of three major areas:

  • Documentation – the guidance package you're currently reading. You can access this resource at any time from the sandbox. You can also access Documentation from its link in the navigation panel on the left side of the dashboard UI.
  • Testing – combined with the API's Swagger specification, this tool lets you simulate bank connectivity using relevant parameters and data so you can see how individual API features perform and the response details you'll receive for each well-defined request.
  • Payload Builder – generates an authorization token you can use for integration testing with your application. You can select either an API key or signing for authentication. You can also specify a callback URL for testing purposes to validate successful redirection and execution.

A word about testing with notional banks. Although Token's demo banks — also called notional banks — can be used to test your integration with the Token API in our sandbox environment, they should never be used for production testing.

To test your PIS integration in the sandbox, you should ideally use one bank for the source account (e.g., requestPayload.transferBody.instructions.source) and the other for the transfer destination (e.g., requestPayload.transferBody.instructions.transferDestinations). The account properties you assign will need to adhere to the object and field definitions for the endpoint being tested. Required objects and fields are labelled accordingly. All others are optional.

Presuming your test request is successful, the populated fields you receive in the response from the notional source bank will adhere to the applicable definition (click to enlarge):

Definition and format rules apply in the sandbox, as well as in production. You can find object-field definitions for each supported endpoint in Swagger Object and Field Definitions. Simply click an item to expand its contents.

Next, let's take a brief look at each area of the sandbox and how to use it.

Working in the Sandbox

Token's sandbox is a software testing environment enabling isolated execution of API functionality for independent evaluation, monitoring or testing. The idea is to be able to test API features and code integration with or without your project in ideal conditions, emulating a production environment and its behaviours to test the functionality of the Token API with notional banks, account information and transaction values. Working in the sandbox, TPP developers can check and validate their code by testing it against a specific web service without creating unforeseen impacts within their normal operating environment and business processes.

As pictured above (click to enlarge), our sandbox is compromised of three major areas:

  • Documentation – the guidance package you're currently reading. You can access this resource at any time from the sandbox. You can also access Documentation from its link in the navigation panel on the left side of the dashboard UI.
  • Testing – combined with the API's Swagger specification, this tool lets you simulate bank connectivity using relevant parameters and data so you can see how individual API features perform and the response details you'll receive for each well-defined request.
  • Payload Builder – generates an authorization token you can use for integration testing with your application. You can select either an API key or signing for authentication. You can also specify a callback URL for testing purposes to validate successful redirection and execution.

A word about testing with notional banks. Although Token's demo banks — also called notional banks — can be used to test your integration with the Token API in our sandbox environment, they should never be used for production testing.

To test your PIS integration in the sandbox, you should ideally use one bank for the source account (e.g., requestPayload.transferBody.instructions.source) and the other for the transfer destination (e.g., requestPayload.transferBody.instructions.transferDestinations). The account properties you assign will need to adhere to the object and field definitions for the endpoint being tested. Required objects and fields are labelled accordingly. All others are optional.

Presuming your test request is successful, the populated fields you receive in the response from the notional source bank will adhere to the applicable definition (click to enlarge):

Definition and format rules apply in the sandbox, as well as in production. You can find object-field definitions for each supported endpoint in Swagger Object and Field Definitions. Simply click an item to expand its contents.

Next, let's take a brief look at each area of the sandbox and how to use it.

 

 

© 2023 TOKEN, INC.     ALL RIGHTS RESERVED.