April 2026

In April 2026 we updated our risk and fraud features for co-brand programs, updated an event, clarified supported characters for biller-supplied patterns, removed erroneous network values, updated web provisioning for Apple Pay, added four new transaction otypes, clarified supported response types for Transaction Simulation endpoints, added balance-related fields, updated the check memo field, added a new product and setup guides, added information about account closures, fixed an account-feature description, changed character support, added a card image detail, updated Payment Hub endpoint descriptions, updated a field description, updated parameter descriptions, and added a business application identifier. Click April 2026 to see the details.

Enhanced risk and fraud features for co-brand programs

We’ve enhanced risk management for co-brand programs by introducing identity verification during onboarding and continuous behavioral biometrics and device trust signals to prevent account takeovers. These updates provide protection against identity fraud and unauthorized account access. See Co-Brand Debit Program Features for details.

Autopay for Secured Credit

We've changed the configuration of autopay from a monthly schedule set to a specific day of the month to a bi-weekly scheduled based on a specific start date. To set autopay for a customer, call Set AutoPay Plan with startDatecontaining the date (in ISO 8601 format) to initiate the automated payment. See Developer Setup for Galileo Secured Credit for details on enabling and managing autopay for secured credit.

Updated event

The mobile_activation TVD event has been updated to be triggered when a tokenized card is removed from a merchant. The msg_id for this event is ATVD.

Updated account patterns legend

We updated the Account Patterns Legend on the Search Biller Directory endpoint to clarify the supported character sets for each mask type and ensure accurate account number validation.

Erroneous network support

The description for the association parameter for Create Simulated Card Authorization and Create Simulated Card Settlement contained values for networks that are not yet supported. Those values have been removed.

Updated web provisioning for Apple Pay

Apple confirmed that nonceSignature is not required for the web provisioning for Apply Pay. To support this, we’ve added a new value (4) to the walletProviderType field to specify Apple Pay Web on Create Provisioning Request. For details, see Creating a Provisioning Request.

Transaction otype update

We added the following otypes for Instant Debit Transfers to the list of transaction otypes in the Transaction Types guide:

VF — Visa Direct (AFT) load
vf —Visa Direct (AFT) reversal
VO — (Letter O) Visa Direct (outgoing OCT) withdrawal
vo — Visa Direct (outgoing OCT) reversal

Clarified supported response types for Transaction Simulation endpoints

We added a note to the Transaction Simulation endpoints in the Program API, explaining that they do not support XML responses, and removed their example XML responses. The following endpoints support JSON responses only:

New balance-related fields

We have added new balance-related fields to a couple of endpoints:

Get All Transaction History — rolling_balance
Get Balance — available_balance and ledger_balance

See the updated Account Balances guide for an explanation of what each of those new fields shows.

We have also removed the warnings about how calculated_balance and beginning_balance could be inaccurate. The addition of rolling_balance marks a new way to calculate balances with Get All Transaction History, and now those fields are reliable.

Billpay check update

We have completed the migration of all clients to the new paper check system. In this system, the memo field on the check contains the memo field from Create Bill Payment as well as the billerAccountNo from Add Paper Biller.

New Instant Debit Transfers guides

We added the following new guides for Instant Debit Transfers, which explains how to use the Visa Direct network to enable near real-time funds movement between a Galileo account and an external debit card:

Instant Debit Transfers — Explains the core functionality of account funding transactions (AFT) for pulling funds and original credit transactions (OCT) for pushing funds.
Setting Up Instant Debit Transfers — Provides a technical walkthrough of the end-to-end flow, setup fundamentals, and error codes.
Integrating the Card Capture UI — Details how to embed Galileo's secure UI to capture card information while reducing PCI compliance scope.

Specifying the reason for an account closure

We added the option to specify or update the closure reason on a closed account. This is typically done when you need to reclassify the account for fraud or compliance correction purposes. See About Accounts for details.

Corrected `featureType` description

In the Set Account Feature Values enumeration, we had erroneously described featureType: 13 as "Mark customer as high risk." (That's actually the description for card fet_id: 13.) We corrected the description to read "Enable Metro2 credit reporting," which applies to an account instead of a card.

Default support of international characters

For the Create Payment and Create Account Transfer endpoints, selected text fields now support the international character set by default, without needing Galileo setup.

Create Account Transfer — message, senderMessage
Create Payment — storeName, retailChain, partner, storeAddress1, storeAddress2, storeCity, storeState

Detail about card images

We updated Design a Card to specify that there is no upper limit to the number of card images you can associate with a product.

Clarified Payment Hub endpoint descriptions

We updated the descriptions for the Create External Account Link and Load External Account Links endpoints to clarify their use cases and better differentiate them from one another. The functions of these endpoints have not changed.

Clearer `userId` field description

For the Add Customer Note endpoint, we updated the userId field description to clarify that this field must be an email address.

Updated `BLKRI` parameter description

We updated the Authorization and Parameters pages to clarify that the BLKRI parameter is not specific to non-reloadable prepaid Visa products.

New Business Application Identifier (BAI)

We updated the Business Application Identifier page to include VA, representing Visa Accept, as a possible value for the bai field in various data sources.