June 2026

In June 2026 we added pending auth disputes, enhanced overdraft, added specific auth expiry, added IVS, added card network mandates under consideration, 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.

Dispute pending transactions

The Dispute API 3.0 now supports disputing pending authorizations when ClaimReasonType: Fraud and ClaimReason: CardSecure or when ClaimReasonType: NonFraud and ClaimReason: MerchantRecurring. Contact Galileo to enable this feature.

We have also added auth_id as an optional field for the dispute-related events.

Enhancements to overdraft

Galileo has introduced several enhancements to the Overdraft product to provide greater flexibility in account configurations and overdraft limit assignments. Key changes are:

Overdraft limits can now be shared across multiple spending accounts if they are associated with the same balance ID. Previously, only a single DDA account could use overdraft. See Account Configuration for Overdraft to learn more.
Overdraft credit limit can now be set account-level via the Set Overdraft Limit endpoint. Previously, overdraft limits were strictly rule-based and configured at the product level. See Configuration Overdraft products for setup and Overdraft line of Credit for a workflow example.
Overdraft fees can now be assessed on either the primary DDA or directly within the overdraft account. Previously, fee assessment was restricted exclusively to the primary DDA.

Expire authorizations control

The Expire Authorization endpoint has a new request parameter, expirationDate, which you can use to specify a date in the future for an individual authorization's expiry.

New Identity Verification Service

Galileo is introducing the Identity Verification Service (IVS), an automated and streamlined way to verify your customers—both individuals (KYC) and businesses (KYB). This service can be used standalone, using a set of endpoints, or it can be integrated with Create Account.

IVS replaces Galileo's Legacy CIP service. Those who are using the older service can still access the instructions on these pages, which are accessible via direct link only:

Added card network mandates under consideration

We updated the Card Network Mandates guide to include a section listing mandates under consideration. If a mandate is under consideration, it means we are currently investigating it to determine its impact to clients. This new section lists only the mandate number and title; if a mandate is determined to have client impact, we will add a more detailed explanation to the list of 2026 mandates on that same page.

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:

settleAmount
settleCurrencyCode
cardBillingAmount
cardBillingCurrencyCode