In March we added billing cycles for secured credit products, updated a CDF, explained AAAU message differences, added info on blocking transactions, added a new card transaction scenario, made some parameters required, changed the example sandbox URI, updated
accountNo for Add Card, detailed frozen card behavior, changed some authorization response codes, updated the Statements guide, reorganized the Auth API guide, published an Offline PIN guide, refined our transaction-reversal process, implemented emboss pausing and clarified event message timestamps. Click March 2023 to see the details.
Galileo offers three billing cycle configurations for secured credit products, which can be configured at either the program or product level, according to your business plan and the agreement with your sponsor bank. See Billing cycles section to the Setup for Galileo Secured Credit guide, which explains the different configuration options.
The Fleet Data CDF now includes JSON to accommodate the nested rows for each entry.
We added a section in the Authorization guide to show how to differentiate among the different types of
AAAU: auth messages.
We added a Blocking transactions section to the About Transactions guide, which explains how you can block various types of transactions.
We added Scenario 20: Card Load Reversal (Maestro) , which shows an example of when a cardholder receives payment from an employer but the funds are reversed.
We added information that the
phoneCountryCode parameters are required for the Create Group endpoint, both for root groups and non-root groups.
We updated the examples in the reference documentation to reflect the new Sandbox URI:
We updated the Card Statuses guide to include details about which transactions are affected by a card freeze and which are not, as well as a way to override the freeze on transactions that credit the account.
Mastercard has changed some of its authorization response codes. Check with Galileo to see if your program is using these new codes yet.
|Card status or other condition||New response code|
|78 — Invalid Account|
|57 — Transaction not permitted|
|41 — Lost Card|
|51 — Insufficient Funds|
|Fraud||63 — Security Violation|
|MCC product- or account-level block||03 — Invalid Merchant|
|Max system amount reached||13 — Invalid Amount|
|Frozen card||62 — Restricted card|
We've updated the Statements guide with current fields and definitions.
We have divided the Authorization Controller API guide into three guides for ease of navigation. The content was not updated:
- Authorization Controller API — Main guide for API functionality
- Auth API Validation Checks — The checks that Galileo performs on incoming authorization requests and the corresponding response codes
- Auth API Field Detail — Lengthier explanations for some of the specialized webhook fields
We published the Offline PIN guide, which addresses how to set PINs in some non-U.S. jurisdictions.
From the guides that explain how to initiate transactions with the Program API—Creating a Payment, Creating an Account Transfer, Creating an Adjustment—we removed references to the corresponding reversal endpoints, because those endpoints do not produce good results in terms of funds flow. Instead, Galileo recommends using Create Adjustment to reverse out payments and adjustments, using the appropriate
type to indicate a reversal.
In the case that you want to pause a card embossing, such as with Digital First cards, you can now call Set Account Feature with
featureType: 30. You can use this feature to cancel an emboss permanently or to resume it at a later time.
We added a section to Event Setup and Configuration to clarify the relationship between event timestamps and account balance.