In March 2022 we corrected the ACH guide, added missing CIP status code, event webhooks and fields, corrected a code description, added a new endpoint response field, added an Auth API field, updated account and card status info, added a font, updated RDF information, updated the Mapping Transactions guide, removed a status code, clarified provisioning requests, added a parameter, clarified the authentication process, corrected network codes tables, added card-activation parameters, added three new guides, added transaction identifiers, clarified descriptions and usage for several endpoints and added the requirement for a Create Hold parameter. Click March 2022 for details.
ACH guide corrections
We made these corrections to the ACH guide.
- Same-day ACH — ACH hold days and cutoff times apply to same-day ACH. For this reason, a same-day ACH request does not typically settle on the same day it was originated.
- ACH early access — You can configure a product to enable ACH early access for all accounts, or control ACH early access for individual accounts, but not both.
CIP status code
In the Customer ID Verification (KYC/CIP) and Creating an Account guides, we added
status: S for the CIP process, which had been missing.
Several Events API webhooks were missing from the reference and have now been added:
Field for event
The optional field
response_reasons had been omitted from the
DAUT: denied_auth event webhook description.
Bill Payment Statuses correction
The description for code
P in the Bill Payment Statuses enumeration erroneously showed "Check printed." It has been changed to "Processed."
New Set Credit Limit response field
We added the
available_credit field to response data for Set Credit Limit.
New Auth API field
Both versions of the Auth API have a new field in the
transaction object called
transaction_initiator_code. It contains a four-character code that indicates whether the cardholder or the merchant initiated a recurring transaction.
Card and account status information
To the Account Statuses and Card Statuses enumerations we added information to indicate what kinds of transactions are permitted by each status as well as parameters that affect account- and card-status behaviors.
We added Monserrat as an available font for the Direct Render PIN-Set Procedure.
From the RDF Reference guide we removed an outdated statement about receiving full RDFs daily instead of differential files. We no longer offer full daily RDFs—only differentials.
Mapping transactions clarification
We updated Mapping Transactions Within Your System to clarify which identifiers have the potential to collide.
Removed status code
We removed status code 408-02 from the Create Payment endpoint reference and the Creating a Payment guide because this status code is no longer in use.
Provisioning request clarification
In the Creating a Provisioning Request guide we included information about which fields in the customer record must be populated for the provisioning request to be successful.
Page parameter added
page parameter has been added to the Get Scheduled Bill Payment endpoint.
We updated the Authentication reference page with improved parameter descriptions, authentication setup during onboarding, and steps to authenticate an endpoint request.
Network codes table
The network codes table at the beginning of Mapping Transactions Within Your System has been corrected:
- The Events API codes have been broken out between Authorization and Settlement when the codes are different for the same transaction.
- The Cirrus and Visa PLUS codes were incorrect for the RDFs
Activate Card parameters
To the Activating a Card guide we added information about product/program parameters that affect card-activation behavior.
We created three new guides:
- Reissuing Cards — Explains when to reissue and contains instructions for using the Reissue Card endpoint.
- Switching Products — Explains when to switch products with and without a card reissue. Also contains information for using the Switch Product endpoint.
- Switching Products with Different BINs — When the old and new products have different BINs, use this guide.
We filled in the blanks in the Identifying accounts table in the Transaction History guide.
Modify Status type 2
We clarified that when using Modify Status with
type: 2, all accounts belonging to the same account holder are also canceled when the ACTYP parameter is set to R.
Create Location change
When using the Create Location endpoint for the first time, it is no longer necessary for Galileo to create the top-level location. By default, the first location that you create will become the top level in the hierarchy.
Charge Off Account clarification
We clarified the explanation of how to use the
chargeOffDetails parameter of the Charge Off Account endpoint.
Get Bulk Card Order field change
The response to the Get Bulk Card Order endpoint used to provide card IDs in the
card_id_range_end fields, but now those fields are populated by zeroes because the card IDs are not necessarily created in order, in one block of numbers.
Freezing accounts and disabling fraud rules
We clarified the conventions around using
endDate when using Set Account Feature to freeze/unfreeze accounts or to disable/enable fraud rules.
Update Account restrictions
We clarified that using Update Account is valid only for active accounts (
status: N). Accounts in other states cannot be updated.
Create Hold parameter requirement
We updated the description for the
expirationDateTime parameter of the Create Hold endpoint to indicate that it is required.
Cancel Bill Payment clarification
We updated the description of the Cancel Bill Payment endpoint to indicate exactly when it may be used to cancel bill payments, including electronic payments.