June 2025
In June 2025 we added a new program parameter and additional details to Payment Screening for Incoming ACH Credits, added a feature to secured credit, a new preview guide, a link to Galileo's privacy policy, corrected a billpay process, clarified DE003, added auth response code changes, corrected the level at which emboss providers are set, and modified an event field. Click June 2025 to see the details.
Payment Screening for Incoming ACH Credits guide
The updated guide now explicitly addresses the upcoming Nacha mandate for screening all incoming ACH credits, highlighting its critical role in compliance. It also clarifies that your program will utilize the default global thresholds or your own custom thresholds set via the NMSMT
parameter, with examples illustrating how name-matching scores are compared to these thresholds for fraud detection.
Semi-secured credit
We have added the option of semi-secured credit for two and three account Secured Credit models. See Setup for Galileo Secured Credit for more details.
New Secure Instant Account Link preview guide
Secure Instant Account Link is an open banking feature powered by Mastercard Finicity. This allows your account holders to securely link external accounts by logging in with their bank credentials, which instantly verifies account ownership. This removes the need for manual account and routing number entry when setting up ACH transfers.
Added link to Galileo privacy disclosure
In the site footer, we added a link to the Galileo privacy policy in effect for this site.
Correction to cancelling a billpay series
The instructions to cancel a series scheduled bill payments has been corrected to indicate that frequencyType
should be set to O
and the date and amount fields set to null.
DE003 clarification
We have updated the DE003 Codes enumeration to provide a detailed explanation of where the processing code (DE003SF1) is exposed in Galileo data.
Authorization response code changes for Mastercard
Note
Galileo will implement these changes during the change window of 17 Jun 2025.
As of 3 Jun 2025, Mastercard requires these changes to the authorization response codes. These are the changes that were rolled back from April 2025:
Old code | New code | Reason |
---|---|---|
78 | 46 | The account is in status: C (canceled) or status: Z (canceled without refund) |
57 78 | 72 | Account/card not yet activated, in status V , W , X , Y |
We have also added an Account and card status response codes table to indicate where different statuses affect the response code.
Emboss providers
Updated Partners, Programs and Products to correct the level at which the emboss provider is set. Previously it was listed at the program level, which was incorrect. Emboss providers for physical cards are set at the product level.
Directory server transaction ID
The ds_transaction_id
field in the BAUT: auth
event formerly said that it contained information from Visa, but Visa doesn't actually populate that field.