May 2026
In May 2026 we enabled account status inquiries for feature types 20 and 21, corrected valid values for a field, corrected a few auth response codes, added new simulated card transaction features, added card network mandates, added product-category validation, added details to our breaking-change policy, added new dispute fields, and updated the response-code pages. Click May 2026 to see the details.
Account-status inquiries
Account feature types 20 and 21 now permit account status inquiry transactions. We also updated Setup for Digital First to include account-status inquiries alongside card loads and mobile wallet provisioning.
Correction to valid values for Create Account expressMail field
expressMail fieldFor Create Account, we corrected the list of valid values for the expressMail field to show that 0 is not a valid value.
Corrections to ALC design doc
We corrected the ALC-related response codes in the Designing Authorization Controls guide to reflect current system functionality.
New simulated transaction features
We have added some Special Functions to simulate CNP transactions as well as failed CVV1 and CVV2 auth requests. We also updated the DE025 Codes enumeration.
Card network mandates
We updated the Card Network Mandates guide to explain Mastercard and Visa mandates in Q2 2026 that impact Galileo.
New product-switch validation
When switching products, Galileo now verifies that the product categories of the old and new products are compatible. If they are not, the endpoints return Product cannot be switched to an unauthorized product:
590-02— Switch Product426-05— Set Account Feature
Updated breaking change policy
We updated our breaking change policy to include details specific to RDFs. Now, the breaking change policy defines what constitutes breaking changes and non-breaking changes in an RDF.
New response fields for Dispute API 3.0
The /claim/retrieve endpoint now returns fields that show which regulatory obligations have been completed and which are approaching a deadline.
Updated and new response codes pages
We have updated the Authorization Response Codes page to contain more accurate information about network-specific codes. Both the main table and the account and card status codes table have been updated. (The Allpoint table is unchanged.) The status-codes table shows that in some cases, the response code is different for account and card statuses.
We have also created a new Response Code Object Messages page that contains possible textual explanations for the response codes in response_code_objects of the Auth API 3.0 webhook payload.
These updates are documentation changes only. System functionality has not changed.
