January 2026

In January 2026 we added a note to the network codes page, added credit statements, corrected an example, added new account closure reasons, changed a default, fixed a label, added recipes, removed a report, added a new value, updated a brand name, added KYC parameters, deprecated a product parameter, documented a missing account closure reason code, added features for secured credit products, fixed a field name, and deprecated some more product parameters. Click January 2026 to see the details.

Resolving network-code collisions

To the Network Codes enum we added a note about resolving the code collision in the RDFs, where P refers both to Maestro/Cirrus and to Visa PLUS. We suggest using the SOURCE field in the Authorized Transactions RDF and SOURCE or ASSOCIATION fields in the Posted Transactions RDF.

Credit statements

We've added credit statements for secured credit products. A credit statement file contains information about transactions that occur within a billing cycle for a credit account. This includes debits, credits, fees, and details like the credit limit.

See Credit Statements for more details on how to configure this feature for your program.

Corrected an example

We corrected the example values to configure delinquency management for secured credit products. See Setup for Galileo Secured Credit for the updated example.

New account closure reasons

We have added four new values for the closureReason parameter on the Modify Status endpoint:

paid_chargeoff
paid_collection
deleted_no_fraud
deceased

See Account Closure Reasons for descriptions.

Changed overdraft default

We have changed the behavior of the ODOBI parameter, which determines the default value for account feature 17 (overdraft eligibility) when a primary account opts out of overdraft. Previously, there was no default, so not setting ODOBI returned an error. Now, the default is N, which sets the account to I (ineligible), preventing automated processes and the account holder from opting the account back in to overdraft.

Corrected label

In the Auth API payload, we corrected the label for tar_info: {token_type} to indicate that H is from VTS and not MDES.

New recipes

We added 2 new recipes relating to the Load External Account Links endpoint:

Use these recipes to better understand the setup process for Account Linking via Mastercard Data Connect.

Removed Daily Loan Installments Status file

We removed the Daily Loan Installments Status file from the list of supported reports for installment loans. You can call Get Loan Status endpoint or Get Loan Installment Statuses endpoint to get loan statuses for customers.

Location override for instant-issue cards

You can now specify a new value for locationType:3 to override the activation location for instant-issue cards during account creation. This is valid on Create Account only. For implementation details, see Setup for Instant Issue.

Terminology change

In these guides, we've changed "Visa Money Transfer" to "Visa Direct," according to the rebranding performed by Visa Inc. The Visa Direct transactions are incoming OCT and AFT transactions.

New KYC parameters

For clients who operate in Mexico and who have chosen Galileo as their BIN sponsor, there are new KYC request parameters for Create Account and Update Account.

Deprecated parameter

We have deprecated the IOANV product parameter. It was used in CV to enable an extended set of request fields for the Create Simulated Card Authorization endpoint, but now those fields are enabled for all clients by default.

Added missing account closure reason code

We added the missing deleted_fraud closure reason to the Account Closure Reasons table.

Delinquency management

We've added delinquency management for secured credit products. This feature configures automated rules to enforce your business’s policies for handling delinquent credit accounts.

See Setup for Galileo Secured Credit for more details on how to configure this feature for your program.

Corrected field name

In the Interest Savings Supplemental (ISS) RDF table, the SAVING_ACCOUNT_ID field was misspelled as SAVINGS_ACCOUNT_ID. It has now been corrected.

Deprecated parameters

We have deprecated the following product parameters related to single-use virtual cards:

SUMTA — Specifies the threshold below which a transaction is declined
SUVCT — Specifies the threshold above which the transaction will be considered a consumer-initiated transaction on a single-use virtual card

We also removed mentions from our API documentation.