May 2025

In May 2025 we added new providers for cash loads, added reversal IDs, clarified the recommended TLS version, removed mentions of Mastercard rePower, added new event fields, clarified otype: L usage, updated which transactions go over which networks, updated the Get Instant Verification (GIVE) reason codes, clarified STIP with the Auth API, rolled back auth response codes, and added support for tap to provisioning. Click May 2025 to see the details.

InComm Payments services

We added documentation about InComm Payments card load services. See Crediting Cardholder Accounts for more details.

Card-load reversal update

We have updated Scenario 20 and Scenario 22 to include the reversal IDs for the auth entries. (Payment and adjustment entries do not have reversal IDs.) We also added a BAUT: auth event for the reversal advice coming in through the authorization stream.

Recommended TLS version

We clarified that endpoint requests to Program API should use TLS 1.3 to ensure enhanced security. TLS 1.2 is the minimum supported version.

Discontinuation of Mastercard rePower

Mastercard has announced that it will discontinue support for its rePower cash load services at retail locations in the United States and Puerto Rico by December 31, 2025. We have updated our documentation, including the MCLD parameter, to remove specific mentions of Mastercard rePower. Galileo has sent specific instructions via email to impacted clients.

Two new fields for refund-check events

If you have refund checks set up, you can enable these fields for some check-related events:

• original_balance_id — Balance ID (galileo_account_number) of the closed account that is being refunded.
• original_prn — PRN of the closed account that is being refunded.

These events support the two new fields:

• BPCR: billpay_request_returned
• BPCL: billpay_cancelled
• BPAY: billpay
• BPCM: billpay_check_mailed
• BPCC: billpay_check_cleared
• BPEX: billpay_expired

We also changed the descriptions for act_type and otype for some of the billpay events to indicate that the event does not return a value for that field.

Settlements with otype: L

We clarified that sometimes otype: L (preauth) is present with a settlement act_type in cases where a merchant obtains a preauth but settles it instead of completing it.

Signature transactions over debit rails

It had been the case that PIN (debit) networks did not transmit PIN-less (signature) transactions, but in 2022 a clarification to the Durbin amendment permitted it. We've updated our docs accordingly.

GIVE reason code updates

Galileo rolled out changes in GIVE to enhance the performance of account verification and ownership authentication, which includes some changes to the reason codes.

• Deprecated: BVSCC, BVSCP, BVSCR, BVSCU, BVSDA, BVSDB, BVSHR, BVSNI
• Updated: BACLT, BACMT, BACST, BACVST, BALNGT, BALOWT, BAMEDT, BANEW
• New: BACVLT, BAVLNGT, BVRSN2

Clarification on STIP and the Auth API

We clarified that an Auth API message is triggered only by approved financial STIP advices, not by denied or non-financial STIP advices.

Tap to provision

We support cardholders' ability to add their card to a mobile wallet by tapping the card on their mobile phone, also known as tap to provision. See Setup for Mobile Wallets for details.