February 2026

In February 2026 we added a new Auth API object, clarified ACH fields, published the new SSH key, improved Mastercard Data Connect documentation, updated a parameter, added a new feature type, clarified an event, added dispute data, updated an enumeration, and added a couple of guides. Click February 2026 to see the details.

New Auth API object

We have added thedigital_commerce_data object to the Auth API payload for Mastercard transactions. This object contains digital commerce solutions indicators to provide more information about how a transaction was initiated.

ACH field clarification

In some ACH-related endpoints we clarified the character limitations in certain fields:

• Add ACH Account and Add ACH Account Corporate:
  • name
  • achAccountNo
  • firstName
  • lastName
  • companyName (Corporate only)
• Create ACH Transaction:
  • achDescription
  • remittanceInfo
  • authorizationMethod
  • identNumber

New SSH public key

Beginning on 27 Feb 2026, this new SSH public key will be valid.

Improvements to Mastercard Data Connect guides

We made several clarity and usability improvements to the following pages related to Mastercard Data Connect (MDC):

• Account Linking via Mastercard Data Connect
• Setting Up Account Linking via Mastercard Data Connect
• Balance Check via Mastercard Data Connect

We also added a new page, Setting Up Balance Check via Mastercard Data Connect, which includes more implementation details and a workflow diagram.

These are documentation-only changes. The features' functionalities have not changed.

New parameter behavior

We have changed the behavior of the BPAVS parameter. When this parameter is set, the mobile-wallet provisioning process now skips the phone number check in addition to AVS and CVV2, which enables instant-issue cards to be provisioned to wallets.

New feature type

We updated the following pages with information about featureType: 33, a new feature type which represents a backup tax withholding amount:

• Set Account Feature Values
• account_feature_change event
• Product Settings: Account features

AAPM clarification

We clarified that with card loads, the auth_id value in the AAPM: auth_payment event payload matches the pmt_source_id value in the corresponding BPMT: pmt event.

Additional dispute data

We have added two new enumerations for dispute-related data as well as updated some of the descriptions in the Reg E RDF to note duplicates.

• Dispute Final Statuses
• Dispute Resolution

Updated enumeration

We updated the Tokenization Recommendation Reason Codes guide to include more Visa codes.

Account balances guide

We created a new guide to explain how Galileo calculates account balances and how to interpret the response to the Get Balance endpoint.

Card expiration guide

We created a new guide to explain key details about card expiration (expiry). This guide compiles existing information from the docs into a central location. We also added links to this page in several docs that mention card expiration. The way card expiration works has not changed.