In March we removed the CAD from accepted inputs for
accountNo on the Add Card endpoint, 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, clarified event message timestamps, and updated the reference docs to show the new Sandbox URL.
Click March 2023 to see the details.
Sandbox API URL updated
We updated the examples in the reference documentation to reflect the new Sandbox URL:
Updated parameter description
We changed the description of
accountNo on the Add Card endpoint to clarify that CAD is not accepted.
Frozen card behavior
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.
New Mastercard response codes
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.
Auth API doc reorganization
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
New Offline PIN guide
We published the Offline PIN guide, which addresses how to set PINs in some non-U.S. jurisdictions.
API transaction reversal
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.
Pause or cancel card emboss
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 a new feature type. You can use this feature to cancel an emboss permanently or to resume it at a later time.
Event message clarification
We added a section to Event Setup and Configuration to clarify the relationship between event timestamps and account balance.