December 2025

In December 2025 we updated a contact address, added refund-check advice, rolled back a state validation, introduced Account Linking and Balance Check documentation, clarified express mail settings, added details about the Metro 2 file segments, added details about permanent card statuses, corrected a Modify Status type definition, corrected a response example, added new fields to an event, added a chargeoff field, updated the card network mandates guide, removed the Wires-related endpoint references, fixed dispute otypes. Click December 2025 to see the details.

Mobile-wallet contact info for Apple

We have updated the contact email address for Apple Pay in the Setup for Push Provisioning guide. The new address is [email protected]. This update applies to both in-app and web provisioning methods.

Account holder refund parameters

We added some parameter suggestions and a tip to help keep track of which closed accounts triggered a refund check.

State character validation rollback

UPDATE 16 DEC 2025: We had to roll back a change because it broke some client implementations. We will restore this change in Q1 2026.

Click to see the original message

We have updated the validation for state request parameters to require ISO 3166-2 abbreviations in the Enrollment endpoints such as Create Account.

Account Linking and Balance Check

We added guides and API reference documentation to support two new offerings: Account Linking and Balance Check. Both Account Linking and Balance Check leverage Mastercard Data Connect to improve account holder experience when interacting with external accounts.

• Account Linking gives your account holders a secure way to connect their external bank accounts.
• Balance Check performs real-time balance inquiries on linked external accounts before initiating an outgoing ACH debit.
• To support these features, the Payment Hub API documentation contains several new endpoints.

Express mail settings

We have clarified express mail settings (featureType: 5) to show which values are universal across vendors and indicate that the legacy Y and N values are converted to numbers by back-end processes.

Details about Metro 2 file format

We updated Credit Reporting at Galileo with information about the standardized segments in the Metro 2 file and what information is present in each segment. We also documented the base segment contains information about the primary account holder, including account status, balance, and payment history..

Details about permanent card statuses

We added information about which card statuses Mastercard and Visa consider permanent: L,S, and C. You can find this information throughout our documentation on accounts and cards, including in Account Statuses, Card Statuses, and Setting Up a Card Program.

Corrected Modify Status value definitions

In the account/card closure sections of About Accounts and Setting Up a Card Program, Modify Status type: 23 was erroneously shown to set accounts (PRNs) to status: D. Those sections have been corrected to show that only the card is set to status: D. (Use type: 10 to set the account to status: D.)

Corrected response example

We corrected the example response of the Cancel ACH Transaction event from ach_account_id to balance. This is a correction to the documentation, not a change to the API.

Added new fields to event

We added new fields to the SETL event to support the Visa Commercial Choice Omni program.

• b2b_program_id — Identifier for the B2B program, as provided by Visa.
• fpi — Fee Program Indicator (FPI) is the interchange reimbursement fee program indicator provided by Visa.
• reimburse_fee —Reimbursement fee calculated by Visa.
• visa_product_id — Product ID provided by Visa.

New chargeoff field

We have added a new request parameter to the Recover Charged-Off Account endpoint. For the closureReason field, select a reason for the account's closure.

Updated card network mandates guide

We added H2 mandates from Mastercard and Visa to Card Network Mandates, which lists and summarizes mandates from card networks that impact Galileo.

Wires documentation update

The Wires-related endpoints provide limited functionality, along with limited sponsor bank support. We removed the endpoint reference pages from the documentation pending the implementation of a more scalable process. If you still need to see documentation for using these endpoints, contact Galileo.

Fixed dispute otypes

Some of the dispute-related otypes were incorrect in the Transaction Types enumeration. These otypes have been corrected throughout.