April 2025
In April 2025 we added a response field, updated Mastercard auth response codes, improved simulated settlements, clarified ACH identifiers, updated Visa auth response codes, removed the Wires guide, made a few updates to the GIVE reason codes, and updated the credit reporting guide. Click April 2025 to see the details.
New response field
We added the credit_ind response field to the Get Account Overview endpoint.
Authorization response code changes for Mastercard
DELAYED
These changes will go into effect on 3 Jun 2025. The changes that we rolled out on 21 Apr 2025 have been rolled back.
As of 21 Apr 2025, Mastercard requires these changes to the Authorization Response Codes:
| Old code | New code | Reason |
|---|---|---|
78 | 46 | The account is in status: C (canceled) or status: Z (canceled without refund) |
5778 | 72 | Account/card not yet activated, in status V, W, X, Y |
Simulated settlement improvement
When you input an amount for the Create Simulated Card Settlement endpoint—and it is different from the authorization amount—the simulated transaction will now settle for that amount. Formerly, simulated settlements only settled for the authorization amount. For example, when simulating an international transaction, you can settle for a different amount than the authorization to simulate changing exchange rates, or you can simulate adding a tip after the authorization.
ACH identifiers clarification
We've retooled the ACH identifier tables in ACH Tracking and Troubleshooting to simplify and clarify which identifiers you can use to trace a transaction through the system, whether incoming or outgoing.
Authorization response code changes for Visa
As of 11 Apr 2025, Visa requires these changes to authorization response codes:
| Old code | New code | Reason |
|---|---|---|
57 | 12 | Failure during EMV Authorization Request Cryptogram (ARQC) validation |
57 | 5C | A product does not allow certain configurations. |
57 | N3 | Cash back or cash advance transactions configured to be blocked/disabled |
57 | 96 | System errors |
57 | 86 | ATM transactions where no PIN is present |
05 | 86 | PIN cannot be verified or error performing PIN update |
05 | 46 | The account in status: C (canceled) or status: Z (canceled without refund) |
05 | 82 | CVV1 check failure (CAM, dCVV, iCVV, CVV, CAVV, dcVV2, TAVV, or DTVV) |
05 | 78 | The transaction account is a spending account and the funding account is delinquent |
05 | 03 | The MCC is invalid |
05 | 19 | Received badly formatted transaction track data or generic error while processing transaction |
05 | 5C | Tokenized transactions not allowed / blocked |
New authorization response codes enumeration
We have updated the format of the Authorization Response Codes enumeration and changed its location.
Wires product update
The Wires-related endpoints provide limited functionality, along with limited sponsor bank support. We removed the product guide from documentation pending the implementation of a more scalable process. If you still need to see documentation for using those endpoints, contact Galileo.
Reason codes
The Get Instant Verification Reason Codes have been updated.
New codes: BVSUC, BVERR, BNIF, BENI
Updated codes:
- BPHNM –> BPHNOM
- BDOBNM –> BDOBNOM
- BTAXNM –> BTAXNOM
- BADDRNM –> BADDRNOM
- BEMAILNM –> BEMAILNOM
Credit reporting
We updated Credit Reporting at Galileo to suggest that programs that are not PCI compliant should consult with their legal counsel about the practice of being a data furnisher.