August 2025

In August 2025 we added fields to the Auth API, clarified the id and id2 parameters, clarified lost/stolen tokenized cards, updated RDF data types, added an Auth API field, clarified some RDF descriptions, and added a missing RDF field. Click August 2025 to see the details.

New Auth API fields

We have added several new fields to the Auth API. Many of these fields are currently present in Auth API payloads, but the values will not be populated until after Visa and Mastercard launch their various initiatives. Galileo will send client communications with more information about these initiatives.

  • Visa only
    • account_attack_intelligence_score — Helps identify enumeration attacks for CNP transactions.
    • vdcap_infoVDCAP information such as authentication_program and applied_special_service
    • is_in_person_tap_transaction — Whether it is an in-person tap transaction.
    • visa_atm_managed_services — Information regarding ATM managed services.
    • service_processing_type — Service processing type for scheduled, deferred OCTs.
    • is_advance_payment — (transactions object) Whether the transaction is an advance payment.
    • cavv_result_code — (ecommerce object) Result code for CAVV authentication for 3DS.
  • Mastercard only
    • relay_resistance_protocol_data — Information related to relay attacks for contactless transactions.

Casing for id and id2 parameters

We updated the id and id2 parameter descriptions and examples to reflect that Galileo converts letters in these fields to lowercase. This affects the following endpoints:

Lost/stolen card replacement in mobile wallets

We clarified the process for marking cards lost or stolen in a mobile wallet per network as well as which cards are automatically replaced and which are not.

RDF data types

After migrating our Base RDF databases to a new platform, some of the data types values have changed. The Old value was displayed in the documentation prior to this update.

Customer Master RDF

FieldOld valueNew value
PRIMARY CARDHOLDERS FNAMEVARCHAR2 (40)VARCHAR2 (73)
PRIMARY CARDHOLDERS LNAMEVARCHAR2 (40)VARCHAR2 (73)
ADDRESS LINE 1VARCHAR2 (48)VARCHAR2 (73)
ADDRESS LINE 2VARCHAR2 (48)VARCHAR2 (73)
CITYVARCHAR2 (48)VARCHAR2 (93)
STATEVARCHAR2 (16)VARCHAR2 (29)
PRIMARY PHONE NUMBERVARCHAR2 (53)VARCHAR2 (29)
CURRENT BALANCENUMBER (10,2)NUMBER (14,2)
NEGATIVE BALANCE FEE AMOUNTNUMBER (9,2)NUMBER (14,2)
AVAILABLE BALANCENUMBER (9,2)NUMBER (14,2)
EXTERNAL ACCOUNT NUMBERCHAR (53)VARCHAR2 (53)
AGENT USER IDVARCHAR2 (30)VARCHAR2 (80)
CIP IDVARCHAR2 (50 bytes)VARCHAR2 (50)
CIP STATUSCHAR (1)VARCHAR2 (1)
CREDIT LIMITNUMBER (9,2)NUMBER (14,2)
EMAIL ADDRESSVARCHAR2 (64)VARCHAR2 (93)
THIRD PHONE NUMBERVARCHAR2 (100)VARCHAR2 (53)
OD BAL IDNUMBERNUMBER (18)
SAVINGS GALILEO IDNUMBERNUMBER (18)

Account Card RDF

FieldOld valueNew value
UNIQUE PROGRAM IDCHAR (12)NUMBER (18)
GROUP IDNUMBERNUMBER (18)
GALILEO ACCOUNT IDNUMBERNUMBER (18)
PRNNUMBERCHAR (12)
CARD IDENTIFIERNUMBERNUMBER (18)
TYPE OF CARDNUMBERNUMBER (18)
GALILEO CLIENT IDNUMBERNUMBER (18)
XIDNUMBERNUMBER (18)

Authorized Transactions RDF

FieldOld valueNew value
MERCHANT NUMBERCHAR (15)VARCHAR2 (15)
TRANSACTION CODECHAR (2)CHAR (6)
AUTH TRANSACTION CODEVARCHAR2 (10)CHAR (2)
MOBILE TRANSACTIONSCHAR (1)VARCHAR2 (11)
PIN ENTRY CAPABILITYCHAR (1)CHAR (3)
POS ENTRY MODENUMBER (2)CHAR (3)
DE38CHAR (6)
DE63_BRNVARCHAR2 (9)VARCHAR2 (50)

Posted Transactions RDF

FieldOld valueNew value
TRANSACTION AMOUNTNUMBER (9,2)NUMBER (14,2)
MERCHANT NUMBERCHAR (25)VARCHAR2 (15)
ACQUIRING IDVARCHAR2 (11)CHAR (11)
ACTIVITY IDNUMBERNUMBER (18)
AUTH AMOUNTNUMBER (9,2)NUMBER (18)
CASHBACK AMOUNTNUMBER (9,2)NUMBER (14,2)
CCA FEE AMOUNT SETTLENUMBER (9,2)NUMBER (14,2)
FULL MERCHANT DESCRIPTIONVARCHAR2VARCHAR2 (99 Byte)
NAMEVARCHAR2VARCHAR2 (30 Byte)
CHECK NUMBERVARCHAR2VARCHAR2 (20 Byte)
ROLLING BALANCENUMBER (9,2)NUMBER (14,2)
ORIGINAL AUTH CODENUMBERNUMBER (18)
SECURE CODEVARCHAR2VARCHAR2 (3 Byte)
POS ENTRY MODENUMBER (2)CHAR (3)
REVERSAL IDNUMBERNUMBER (18)
SLI INDICATORCHAR (1)VARCHAR2 (999)
XIDNUMBERNUMBER (18)
PIN ENTRY CAPABILITYCHAR (1)CHAR (3)

Reg E RDF field

We added the ERROR_DESCRIPTION field to the Reg E RDF field descriptions. This is a change to the documentation, not to the RDF.

ACH RDF clarifications

We updated the descriptions of two ACH-related RDFs to clarify exactly which transactions are included in each file:


© Galileo Financial Technologies, LLC 2025    Privacy Disclosure

All documentation, including but not limited to text, graphics, images, and any other content, are the exclusive property of Galileo Financial Technologies, LLC and are protected by copyright laws. These materials may not be reproduced, distributed, transmitted, displayed, or otherwise used without the prior written permission of Galileo Financial Technologies, LLC. Any unauthorized use or reproduction of these materials are expressly prohibited.