December 2024
In December 2024 we added a note about ADq, corrected an endpoint parameter, updated a CST guide, added a product parameter for Secured Credit, started publishing clients-only documentation in the Galileo Console, added an event to balance-change triggers, added two new recipes, updated the ACH Transaction Statuses, added a new response parameter to an endpoint, added interest to Transaction History, added a new field to events, clarified supported orientation of tokenized cards, explained unmatched reversals, added new response parameters for fees, and updated the Creating an Internal Transfer guide. Click December 2024 to see the details.
Clarification for ADq trans code
ADq trans codeWe added a note to the Card loads table on the Transaction Types page to indicate how to distinguish between the two possible meanings of trans_code: ADq: Mastercard load reversal and ACH debit adjustment.
Correction to Add Card endpoint
We corrected the description for the prodId parameter of the Add Card endpoint to indicate that the product ID of the card in accountNo should be passed instead of the product ID of the instant-issue card. We also updated the Setup for Instant Issue Cards guide to reflect this change.
Updated CST guide
The Payment Posts and Returns CST guide has been reviewed and updated for clarity, completeness, and accuracy. The PDF is available in the GCC.
Update to product parameters for Secured Credit
We added the ACSET parameter to the requirements to set up for Galileo Secured Credit. For credit products, set this parameter to TC (Total ID (CIP) first, credit). See Setup for Galileo Secured Credit for details.
Clients-only documentation now available in the Galileo Console
Galileo clients who log into the GCC via OneLogin (SSO) now have self-service access to frequently requested non-public documents in the updated Knowledge Center, currently in beta.
The list of docs includes Customer Service Tool user guides, calculations for interest-bearing accounts, and overviews of additional Galileo services. We'll continue to expand this collection over time.
Update to events triggered by balance changes
We added STPN: auth_stip_notification to the Events Triggered by Balance Changes page.
New recipes
We added two recipes for Create Simulated Incoming ACH Transaction that show an example cURL request with one of the two templates: CreditsAndDebits and ManualReviewNameMatching.
ACH Transaction Statuses enumeration
We cleaned up the status table to accurately reflect statuses returned by calling Get ACH Transaction History. Additionally, we clarified the difference between statuses A and C.
New response field for Get Account Overview
We added a new first_fund_date parameter to Get Account Overview so you can determine when the account was first funded. This helps you accurately determine the date by which the provisional credit needs to be provided and when the dispute needs to be resolved per Regulation E.
Displaying interest
To the Transaction History guide we added an Interest section to indicate which endpoints to use to retrieve interest-related information.
New field in Events
We added a new merchant_country_code field to SETL:setl, BADJ:adj and BPMT:pmt events. This field applies only to Mastercard credit only.
Tokenized card design
We clarified that the image for the tokenized (mobile wallet) card must use horizontal orientation.
Unmatched reversals
We added a section to the Crediting Cardholder Accounts guide to explain how a reversal or other type of "subsequent" transaction might be posted without linking it to its original authorization.
At the same time, we improved the descriptions for:
Assess & Reverse Fees
We added new response parameters for both Assess Fee (fee_id, fee_event_id) and Reverse Fee (fee_id, fee_event_id, reversed_fee_id, reversed_fee_event_id) which are to be used instead of fee_trans_id as this field has been deprecated.
Creating an Internal Transfer guide
We updated the Creating an Internal Transfer guide to specify that if sending and receiving accounts have different program IDs, the BMAVP parameter can be used to allow cross program money transfers.