August 2025
In August 2025 we added active flag info, corrected a parameter example, added fields to the Auth API, clarified the id and id2 parameters, clarified lost/stolen tokenized cards, updated RDF data types, clarified some RDF descriptions, and added a missing RDF field. Click August 2025 to see the details.
Active flag information
We have added more information to several pages to specify the function of an account's active flag, how to find the flag, and which account statuses correspond with active: Y.
Correction to templateValues parameter example
templateValues parameter exampleWe corrected the example for the templateValues parameter in Create Simulated Incoming ACH Transaction. The example previously included additional square brackets, which returned an error.
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_info— VDCAP information such asauthentication_programandapplied_special_serviceis_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— (transactionsobject) Whether the transaction is an advance payment.cavv_result_code— (ecommerceobject) 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
id and id2 parametersWe 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:
- Create Account
- Create Virtual Card Account
- Get Account by ID
- Run Enrollment CIP
- Start Enrollment
- Update Account
- Update Enrollment
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
| Field | Old value | New value |
|---|---|---|
PRIMARY CARDHOLDERS FNAME | VARCHAR2 (40) | VARCHAR2 (73) |
PRIMARY CARDHOLDERS LNAME | VARCHAR2 (40) | VARCHAR2 (73) |
ADDRESS LINE 1 | VARCHAR2 (48) | VARCHAR2 (73) |
ADDRESS LINE 2 | VARCHAR2 (48) | VARCHAR2 (73) |
CITY | VARCHAR2 (48) | VARCHAR2 (93) |
STATE | VARCHAR2 (16) | VARCHAR2 (29) |
PRIMARY PHONE NUMBER | VARCHAR2 (53) | VARCHAR2 (29) |
CURRENT BALANCE | NUMBER (10,2) | NUMBER (14,2) |
NEGATIVE BALANCE FEE AMOUNT | NUMBER (9,2) | NUMBER (14,2) |
AVAILABLE BALANCE | NUMBER (9,2) | NUMBER (14,2) |
EXTERNAL ACCOUNT NUMBER | CHAR (53) | VARCHAR2 (53) |
AGENT USER ID | VARCHAR2 (30) | VARCHAR2 (80) |
CIP ID | VARCHAR2 (50 bytes) | VARCHAR2 (50) |
CIP STATUS | CHAR (1) | VARCHAR2 (1) |
CREDIT LIMIT | NUMBER (9,2) | NUMBER (14,2) |
EMAIL ADDRESS | VARCHAR2 (64) | VARCHAR2 (93) |
THIRD PHONE NUMBER | VARCHAR2 (100) | VARCHAR2 (53) |
OD BAL ID | NUMBER | NUMBER (18) |
SAVINGS GALILEO ID | NUMBER | NUMBER (18) |
Account Card RDF
| Field | Old value | New value |
|---|---|---|
UNIQUE PROGRAM ID | CHAR (12) | NUMBER (18) |
GROUP ID | NUMBER | NUMBER (18) |
GALILEO ACCOUNT ID | NUMBER | NUMBER (18) |
PRN | NUMBER | CHAR (12) |
CARD IDENTIFIER | NUMBER | NUMBER (18) |
TYPE OF CARD | NUMBER | NUMBER (18) |
GALILEO CLIENT ID | NUMBER | NUMBER (18) |
XID | NUMBER | NUMBER (18) |
Authorized Transactions RDF
| Field | Old value | New value |
|---|---|---|
MERCHANT NUMBER | CHAR (15) | VARCHAR2 (15) |
TRANSACTION CODE | CHAR (2) | CHAR (6) |
AUTH TRANSACTION CODE | VARCHAR2 (10) | CHAR (2) |
MOBILE TRANSACTIONS | CHAR (1) | VARCHAR2 (11) |
PIN ENTRY CAPABILITY | CHAR (1) | CHAR (3) |
POS ENTRY MODE | NUMBER (2) | CHAR (3) |
DE38 | CHAR (6) | |
DE63_BRN | VARCHAR2 (9) | VARCHAR2 (50) |
Posted Transactions RDF
| Field | Old value | New value |
|---|---|---|
TRANSACTION AMOUNT | NUMBER (9,2) | NUMBER (14,2) |
MERCHANT NUMBER | CHAR (25) | VARCHAR2 (15) |
ACQUIRING ID | VARCHAR2 (11) | CHAR (11) |
ACTIVITY ID | NUMBER | NUMBER (18) |
AUTH AMOUNT | NUMBER (9,2) | NUMBER (18) |
CASHBACK AMOUNT | NUMBER (9,2) | NUMBER (14,2) |
CCA FEE AMOUNT SETTLE | NUMBER (9,2) | NUMBER (14,2) |
FULL MERCHANT DESCRIPTION | VARCHAR2 | VARCHAR2 (99 Byte) |
NAME | VARCHAR2 | VARCHAR2 (30 Byte) |
CHECK NUMBER | VARCHAR2 | VARCHAR2 (20 Byte) |
ROLLING BALANCE | NUMBER (9,2) | NUMBER (14,2) |
ORIGINAL AUTH CODE | NUMBER | NUMBER (18) |
SECURE CODE | VARCHAR2 | VARCHAR2 (3 Byte) |
POS ENTRY MODE | NUMBER (2) | CHAR (3) |
REVERSAL ID | NUMBER | NUMBER (18) |
SLI INDICATOR | CHAR (1) | VARCHAR2 (999) |
XID | NUMBER | NUMBER (18) |
PIN ENTRY CAPABILITY | CHAR (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: