June 2026

In June 2026 we corrected valid values for a field, added new status codes, added new response fields, populated RDF fields, added detail to some transaction simulation fields, and clarified PRP data types. Click June 2026 to see the details.

Corrected values for `expressMail` field

For Create Account, we corrected the list of valid values for the expressMail field to show that 0 is a valid value. We had previously removed 0 as a valid value in the docs, but that was an error.

Status codes for Autopay

We’ve added new status codes for Set Autopay Plan and Get Autopay History:

639-04 — Account not found
639-05 — Account is not active

Added response fields

We added the fields pmt_ref_no and bal_id to the authorizations response object on Get Account Overview.

RDF fields to be populated

In accordance with Mastercard’s VAT Jurisprudence mandates LAC 11728.1, Galileo begins populating the following fields with Mastercard data in the Posted Transactions RDF on June 9, 2026:

INTERCHANGE FEE AMOUNT — Derived from the new PDS0298 when present; else the value in PDS0146 is used.
IVA_TAX — Derived from PDS0297 when present, else blank.

Data-type clarification for GIVE endpoint

We updated the Get Instant Verification endpoint to clarify that for partnerId, prodId, and progId, the data type is a numeric string. Other characters are not supported.

Added details on Create Simulated Card Authorization fields

For the Create Simulated Card Authorization endpoint, we updated the following field descriptions to clarify the field is required if the currencyCode differs from the account currency: