In February 2022 we corrected some parameters, added new events, updated endpoint parameter descriptions, clarified a status code, clarified the guide on secured credit, added new status codes, corrected information about secondary accounts, clarified disqualifying overdraft events, added information about driving accounts negative, added new STIP fields, clarified endpoint descriptions, clarified an event trigger, added our breaking-change policy, clarified the PIN-set events, updated how to use the
id2 parameters and removed an erroneous statement about the Pulse network. Click February 2022 to see the details.
In the Galileo setup section of the Customer ID Verification (KYC/CIP) guide, the description for the VALID parameter was incorrect, and the VLDLV parameter was missing.
We added a new Account Event,
CLIM: credit_limit_change, which is triggered when the limit on a credit account changes.
We clarified the descriptions for the following endpoint parameters:
- Switch Product and Reissue Card — For the
oldCardStatusparameter, the default is blank. Clarified description and examples for
- Expire Hold — Leave
expirationDateTimeempty to expire the hold immediately.
- Modify Status — The
bypassRepFeeparameter is only valid when
- Get Fee History, Get Pending Fees, and Assess Fee — The
typefield is the three-letter fee code, not the transaction type (otype).
We clarified the descriptions for Expire Hold status codes. 540-02 can be resolved with a future date-time or by leaving
expirationDateTime empty. 540-03 does not apply to new holds; removed “when creating a hold” from the description.
We updated the Secured Credit guide with information about customer benefits and made clarifications about the customer experience. We also added some new use cases and added a new section on program manager responsibilities.
The Switch Product endpoint has new status codes: 590-03 through 590-12.
The About Accounts guide stated that secondary accounts cannot be used as primary accounts. This is no longer true. A secondary account number can be used for
accountNo with Add Account. A secondary account number still cannot be used for
primaryAccount with Create Account.
To the Managing Overdraft Accounts guide we added details about what causes an account holder to lose access to overdraft and how to restore access.
To the description for the Create Account Transfer endpoint we added a note about setting the ALWNB parameter to allow the endpoint to drive the sending account negative.
We added a new Account Event,
ACST: account_status_change, which is triggered when an account changes to a status that is specified in the ACMSG product parameter.
When the networks perform STIP, Galileo can include the response code that the network sent to the merchant in the
in_de39 field in the
STPD: denied_auth_stip Authorization Event message and in the RDFs. These fields are enabled by request.
We updated the following endpoint descriptions:
- Update Pending Merchant Credit — To be used only if you are handling your own disputes.
- Modify Pending Deposit Status — Used for returns on incoming ACH credit.
- Create IVR Call, Get IVR Call Status, and Get IVR Call Identifier — Connect your system to Galileo’s for PIN setting.
- Get Promontory Bank List — Related to Promontory high yield accounts for sweeps. Shows the banks that are involved in the sweep.
- Add ACH Account — Added information about the RPVIR parameter for Plaid integration.
We clarified the trigger for the
CRCA: ready_to_activate event, which is when a card is activated in the CST. The
ready_to_activate name is a misnomer, because the card is already active when the event is sent.
We added our Breaking Change Policy to indicate which types of changes are to be communicated in advance of the change going live.
We clarified the event triggers for the PIN-set events:
PINC: PIN_changed— The PIN change has been staged by the CST, IVR, or Galileo-hosted website.
PNCH: system_pin_change— The PIN change was successful, usually as the result of Commit Card PIN Change.
In the Customer ID Verification (KYC/CIP) guide, we clarified how to use the
id2 parameters in the enrollment endpoints.
The Networks guide had formerly indicated that Pulse was not supported as a secondary network. That is no longer true: Pulse is now supported as a secondary.