July 2024

IIn July 2024 we added a PRP guide, clarified an RDF field, added a 3DS guide, 9-digit BINs, four new status codes, moved wire-related endpoints, added new STIP reporting, added visa_trans_id, corrected Auth API fields, clarified statement criteria, added steps for canceling electronic billpay transactions, added Cloudflare response codes, and added a couple of LATAM-specific features. Click July 2024 to see the details.

New guide

We added the Payment Risk Platform Core Features guide, which contains information about the Feature Platform, Decision Rules Engine, and the Case Management system.

RDF field clarification

We clarified how the EXTERNAL TRANSACTION ID field is populated in the Posted Transactions RDF.

New guide

We added the 3-D Secure Access-Control Server guide, which contains information about Galileo's new access-control server offering. At the same time, we've moved details about the ecommerce object from the Auth API reference to this guide.

9-digit BINs

Galileo is developing support for 9-digit BINs, which you can use in a variety of ways. This support is currently being offered on a limited basis. Contact Galileo to see if your program is eligible.

New status codes

We added three new status codes to the Add Account endpoint:

Status code	Description
456-07	`Maximum number of secondary accounts exceeded`. Product settings do not permit this many secondary accounts per primary account. Set SECLM on the secondary account to a higher number.
456-08	`Secondary accounts cannot be added to secondary accounts`.
456-09	`Primary account is invalid`. The account number in `accountNo` cannot be an instant-issue card.

We added one new status code to the Create Adjustment endpoint:

Status code	Description
409-09	`Transaction limit exceeded.`

Wires endpoints in new location

We have moved the wires-related endpoints to a new place: Payment Hub API. In the future, this API will facilitate advanced methods of sending payments using the FedNow service.

Next-generation STIP reporting

We are moving to a new model for STIP reporting that provides you with additional information on STIP transactions. You must arrange with Galileo to use this new reporting model, which replaces the previous model. For this new reporting you must contact Galileo to have the STIPR parameter enabled. Along with this new reporting we've added these items to the documentation:

Authorization Event — STPN: auth_stip_notification
Two new enumerations:
- Advice Reason Codes
- STIP Additional Detail

Visa transaction ID

To the Authorization Events we have added the visa_trans_id field, which contains Field 62.2.

Auth API doc updates

We have corrected the Auth API documentation (v2 and v3) as follows:

In the amounts object:
- Added billing_currency and billing_currency_amount
- Changed local_surcharge_amount to local_surcharge_amt
- Changed settlement_surcharge_amount to settlement_surcharge_amt
Added aav_indicator to the ecommerce object

Statements clarification

We clarified what the criteria are to generate statements for accounts.

Canceling electronic bill payments

We added steps for canceling unprocessed electronic billpay transactions to the Managing Billpay Transactions guide.

Cloudflare response codes

We added the Cloudflare response codes that you might receive in response to your API requests to Galileo endpoints.

ATM issuer-fee inquiry

Colombia only. Galileo now supports ATM issuer-fee inquiries so that cardholders can accept or reject all ATM fees before withdrawing cash.

Reset offline PIN count

Mexico only. Set up a specialized script with Galileo to automatically reset the offline PIN-fail count when entering the correct PIN at an ATM.