March 2026

In March 2026 we clarified details about statements, updated information about paper checks, added details to a Program API field, updated Program API field lengths, deprecated some parameters, added new Auth API fields, added an ACH field, and updated some param descriptions. Click March 2026 to see the details.

Statements for deposit accounts

In Statements, we clarified that the statement-generation process for deposit accounts can be configured to run on a specific day of the month

Paper check issuer change

In About Bill Pay, we updated a sentence to specify that paper checks are now issued by First Community Bank of Texas.

Phone number field details

In Get Billpay Switch Token, we added a more detailed explanation of the phoneNumber field.

Updated field lengths

We changed the minimum field length from 9 to 6 digits on the following fields:

• ddAccountNo in Get Direct Deposit Switch Token
• accountNo in the ddAccounts object in Get Billpay Switch Token

Deprecated parameters

The product parameters that were related to disputes have all been deprecated.

New Auth API fields

In response to mandate GLB 8701.3 Enhancing Mastercard Transaction Link Identifier, we have added a new object to the Auth API payload called mastercard_transaction_id_data. This object contains further information about the TLID to support multi-use transaction identification data and provide information on updated TLID usage.

This object will not contain data until Mastercard begins sending it through the auth stream.

Nacha compliance update: Company entry descriptions

To comply with Nacha rules, Galileo now supports the companyEntryDesc field on Create ACH Transaction. This field appears on the receiver’s bank statement to clarify transaction intent and streamline reconciliation. Currently supports the values PAYROLL, PURCHASE, and custom description (excluding restricted values).

The field is available in CV (March 6) and Production (March 20). After June 30, 2026, ACH transactions without this field will be rejected.

includeRelated behavior

Many of our data-retrieval endpoints have an includeRelated request parameter. The default behavior was to permit the retrieval of transactions from all accounts that share a balance when a secondary account number was passed for accountNo.

Over time, that behavior has changed for many endpoints — such as returning all data from accounts with the same owner instead of shared balance — and so we have updated each individual includeRelated description to describe how it behaves in each endpoint. These are the endpoints that have an includeRelated parameter: