May 2022

In May 2022 we clarified card-related info, added a new response field, added TAR info to the Auth API, added guides on statements, added emboss UUID fields, corrected the cancel ACH endpoint, added missing characters to the businessName parameter, enhanced some event descriptions, clarified some descriptions, added account-closure reporting for secured credit, a new Auth API field and object, removed some non-AWS URLs, clarified digital image requirements, added a response code, added event message fields, added two events, added ACH account ID to two events and corrected some card-status descriptions. Click May 2022 to see the details.

About Cards clarification

We updated the Card identifiers section in the About Cards guide to clarify the relationships between the CAD and PAN and PIN-setting, and between CVV, expiry date and emboss UUID.

New response field

To the Set Credit Limit endpoint response we added the available_credit field to indicate how much credit the account currently has for spending.

New Auth API object

To the Auth API webhook (v2 and v3) we have added the tar_info object that contains subfields for tokenization authorization request data. Specific fields vary by card network.

New statements documentation

Galileo is now offering statements for clients who would like basic statements for debit accounts.

• Statements — Galileo's offering, and how to call individual statements from your interface.
• Creating Statements from the RDFs — Details on how to use the RDFs to generate customized statements.

Emboss UUID fields

We have added new fields to some Program API responses and event messages that help distinguish between new and older emboss records.

• new_emboss_uuid — UUID for an emboss record that has not yet been sent to the embosser.
• emboss_uuid — UUID for an emboss record that has been sent to the embosser. When this field is present outside the embossed_cards object, it contains the most recent emboss UUID.

The new fields are in the responses to these endpoints. Check the response schema for each endpoint to see where the fields are nested.

• Create Account
• Get Card
• Get Account Cards
• Reissue Card
• Switch Product

By request, you can also get the new fields in these event messages:

• LSCR: lost/stolen card with replacement (new_emboss_uuid)
• SHIP: card_shipped (emboss_uuid)
• BACT: card_activated (emboss_uuid)

Cancel ACH Transaction correction

The description for the Cancel ACH Transaction description incorrectly instructed the user to pass the transactionId of the transaction to cancel. Instead, you should pass the achTransactionId of the transaction to cancel.

Special characters for the businessName parameter

We added some missing characters to the list of accepted characters for businessName.

Event descriptions updated

We updated the descriptions for these events, to provide more context:

• BDPM: pmt_delayed
• BSPM: pmt_split

Clarified descriptions

We clarified parameter descriptions for the Create Bulk Card Order endpoint.

User-defined field locations

We clarified that the user-defined fields created by the Set User-Defined Account Field endpoint are visible on the Account tab of the CST.

Secured credit account closure reporting

In the Secured Credit guide, we added information about reporting account closures for secured credit products.

• Account closure status reporting under Setting Up Secured Credit
• Reporting account closure status under Developer Setup for Secured Credit

New Auth API field

To v2 and v3 of the Auth API, we added a new field to the amounts object: upcharge_amount, which shows how much of the trans_amount is an upcharge.

AWS URL requirement

When you access the asset application, Galileo now prefers that you call an AWS instance that is specially provisioned for your program. We have removed the non-AWS URLs from the following guides. If you don't have an AWS URL yet, request one from Galileo.

• Digital Cards
• Direct POST PIN-Set Procedure
• Direct Render PIN-Set Procedure
• PIN Retrieval Service

Auth response code added

We added response code 04 (capture card) to the Authorization Response Codes enumeration.

Digital image clarification

In the Digital Cards guide we clarified that you must provide two image templates to Galileo: one blank and one populated.

Event message fields

All of the Event API messages now show msg_id (four-letter event code) and msg_event_id (unique message ID) as optional fields.

New events

We have added events related to External Trans API retries:

• GDBR: ext_trans_debit_retry
• GDBF: ext_trans_debit_fail

ACH account ID

The BADJ: adj and BPMT: pmt events now show ach_acct_id as an optional field.

Card status descriptions

The Card Statuses enumeration has been corrected to show that status B indicates when the bounce-mail flag is set to Y rather than status D.