There are three environments for testing and deploying your code integrations with Galileo APIs. The best environment to use depends on your stage of development:

This table provides a quick comparison of environments.

FunctionSandboxClient ValidationProduction
Uses a standard product and program.X
Test environment, no movement of real funds.XX
Uses your specific product and program configurations.XX
Access to real-world transactions like ATM withdrawals, refunds, and ACH direct deposits.X
Acts on live customer data.X
Live product, transactions move real funds.X

Sandbox environment

The Sandbox environment gives you access to a standard configuration of the Galileo Program API. This shared environment is intended to help you get familiar with the Program API before you integrate your customized programs and products.

Sandbox usage

Use the Sandbox environment to:

  • Explore some of the methods in the Program API.
    • See Sandbox endpoints for a list of methods available in the Sandbox environment.
    • There is a limit of 1000 API requests every 10 minutes.
  • Test a simple program (prog_id: 6914) and product (prod_id: 2769) configured with typical parameters.

The Sandbox environment simulates a generic configuration. To test your own configuration, use the Client Validation environment.

Sandbox setup

Sandbox API calls are secured with client certificate validation. Before using the Sandbox, make sure you have the following:



New Sandbox API credentials are required after 30 days and must be generated by your company's Sandbox team admin. If the incorrect details are used, your API request will fail, and your company account may be locked.

When you have your credentials, see the Quickstart guide for a brief tutorial on connecting to the API. Then see Build a Sample App to create a test account and call some common endpoints.

Sandbox endpoints

These endpoints are available in the Sandbox environment:

Client Validation environment

The CV environment is a development environment where you can integrate your programs and products with the latest Galileo APIs. You can use this environment to create test users, accounts, and cards without affecting real customer accounts.

Client Validation usage

Use the CV environment to:

  • Develop your program and product integrations with the Galileo Program API.
  • Stage upgrades and additions to your program before deploying to your production application.
  • Test your configurations without affecting customer accounts.
  • Access the latest Program API endpoints and features.
  • Simulate point-of-sale payments using the Simulate Card Authorization. For instructions see:
  • Test the Customer Service Tool (CST).

Because CV is an isolated environment, there are some limitations. Some functionality is unavailable outside of Production:

  • ACH direct deposit simulations
  • RDFs

Client Validation setup

Your Galileo representative will help you get access to the CV environment with the Galileo Connectivity Guide. Access to the CV environment will require:

  • Your IP addresses for connecting to the Program API.
  • Your URLs for Auth API and Events API webhooks.
  • Your IP addresses for accessing the CST.

Once you have your credentials, you can use your CV URL in the same way you used the Sandbox URL. Replace the Sandbox URL with the CV URL to use the CV environment.

Production environment

The Production environment has access to live data. Any products connected to the Production environment can affect live customer accounts.

Production usage

When you are ready to go live, use the Production environment to access live data and enable your customers to make real transactions.



Enabling certain processes in Production may require approval and coordination from the issuing bank. Your Galileo representative will work with you to identify any processes that require manual testing or third-party coordination.

Production setup

Similar to CV, your Galileo representative will work with you to collect the following information to grant you access to the Production environment:

  • Your IP addresses for connecting to the Program API (must be different from CV environment IP addresses).
  • Your preferred transfer method for RDFs.
  • Your URLs for Auth API and Events API webhooks (must be different from CV environment URLs).
  • Your IP addresses for accessing the CST and Galileo Analytics.