November 2020
In November 2020 we debuted our guides, added JWT validation for the Events API, added a new business name parameter, added new Auth API parameters, accepted datetime in date parameters, included card data in Add Account responses, added a new endpoint, and implemented a new pagination method for selected endpoints. Click November 2020 to see the details.
Guides debut
We added the first set of guides to help you understand how to use Galileo's APIs:
Accounts
- About Accounts — Describes the account structure in the Galileo system
- Creating an Account — How to create an account using the Create Account or Create Virtual Card Account endpoints
- Adding an Account — How to add a secondary account to an existing account holder
Cards
- About Cards — Describes how cards are represented in the Galileo system
- Activating a Card — How to activate a new physical card using the Activate Card endpoint
- Lost, Stolen, or Damaged Cards — How to report cards as lost, stolen, or damaged, and how to replace or reissue them
Transactions
- About Transactions — Basic characteristics of transactions in the Galileo system
- Transaction History — How to create your own transaction history or how to use the Program API for transaction history
- Mapping Transactions Within Your System — How to create unique identifiers for transactions in your system
- Creating an Internal Transfer — How to transfer funds from one account to another in the same program
- Creating a Payment — How to create, update, or reverse a payment (credit) for a customer account
JWT validation for the Events API
We now support using JWT to validate JSON messages in the Events webhook, in addition to using HMAC.
New business name parameter
For Program API endpoints that pass a customer's first and last names, we added the new businessName parameter, which you populate when prodId specifies a business product.
New Auth API parameters
We added new parameters to Auth API Webhook 2.0 and Auth API Webhook 3.0:
- The
validation_resultsparameter includesavs_result, which indicates what was verified by AVS. mtidisplays the ISO 8583 message type identifier.transactionindicates whether the transaction is recurring and whether the cardholder was present.
Datetime in date parameters
We changed our validation method to accept datetime in all parameters that accept a date.
Card data in Add Account response
The Add Account endpoint now returns card_id. If you are PCI compliant, it also returns PAN/CVV/expiry.
New endpoint added
The new Charge Off Account endpoint charges off the specified account (sweeps funds and sets balance to 0) and moves the account to status: R (Charged off).
New pagination method for selected endpoints
For Program API endpoints that return large amounts of data, we standardized a new pagination method. The new default is 200 results per page. To change this default, set the provider parameter MXRPG.