Environments

For testing and deploying code integrations with MO Technologies APIs, three distinct environments are provided, each serving specific purposes based on the development stage:

Sandbox environment

Client Validation environment

Production environment

Each has its own purpose in your integration process. The table below presents the different functionalities of them:

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

Sandbox environment

The Sandbox environment is designed for testing API integration using a standard program and product. It offers a controlled setting for developers to experiment with the Sandbox API before deploying customized programs and products.

The sandbox can be used to explore some of the methods in the Sandbox API and to test a simple program and product configured with typical parameters. To test, use the following program and product identifiers:

Item	Key	value
Program	`prog_id`	6914
Product	`prod_id`	2769

Sandbox API notes

Data is wiped on a rolling 7-day basis.
Limit of 1000 requests every 10 minutes.

Sandbox setup

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

A Sandbox account from Galileo (If you don't have one, use the Request Sandbox Access form).
Access to the Sandbox Dashboard.

Sandbox API credentials

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.

Sandbox endpoints

Below, you will find every endpoint available to use with the sandbox environment:

Customer

Create Pre-customer

POST

Create Customer

POST

Update Customer

POST

Update Customer Status

POST

Get Enrollment Info

GET

Verify Enrollment Info

POST

Account

Create Account

POST

Get Account

GET

Get Account Overview

GET

Update Account

POST

Get Balance

GET

Modify Account Status

PUT

Search Account

GET

Verify Account

POST

Product/Offer

Loan

Create Pre-loan

POST

Create Loan

POST

Get All Transaction History

GET

Transactions

Create Payment

POST

Adjust Payment

PUT

Reverse Payment

POST

Get Payment History

GET

Create Adjustment

POST

Reverse Adjustment

POST

Client Validation environment

The Client Validation (CV) environment is a development environment for integrating customized programs and products with the latest Galileo APIs. This environment enables developers to create test users, accounts, and cards without impacting any real customer accounts.

The CV environment can be used for a few different options, presented below:

Develop program and product integrations with the Galileo Program API.
Stage upgrades and additions before deploying to the production application.
Test configurations without affecting customer accounts.
Access the latest Program API endpoints and features.
Simulate point-of-sale payments using the Simulate Card Authorization.

Limitations

Some functionality is unavailable outside of Production, including ACH direct deposit simulations and 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.

Note

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.

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 provides access to live data and is intended for deploying code and going live with real transactions. When ready to launch, developers can leverage the Production environment to enable customers to make real transactions.

When ready to go live, use the production environment to enable customers to make real transactions.

Production setup

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.
Your preferred transfer method for RDFs.
Your URLs for Auth API and Events API webhooks.
Your IP addresses for accessing the CST and Galileo Analytics.

Your IP addresses and URLs must be different from the ones used for the CV environment connection.

Approval required

Approval and coordination from the issuing bank may be required to enable certain processes in Production. Your Galileo representative will help identify processes that require manual testing or third-party coordination.