March 2024

In March 2024, we added autopay for secured credit products, updated an enumeration, clarified the type field, moved an endpoint, added auth entry types, added MCCs to velocity ALCs, added a field to ODAA, changed billpay endpoints, removed and required ACH account params and clarified details about fee otypes. Click March 2024 to see the details.

Added support for autopay on secured credit

We've launched autopay capability for Galileo's Secured Credit product. Autopay enables your customers to pay the full balance of the previously calculated billing cycle every month through scheduled, recurring transfers.

There are three new APIs to support autopay:

• Set AutoPay Plan
• Set AutoPay Attempt
• Get AutoPay History

Updated enumeration

We updated the DE061 Subfields enumeration with more recent information from Mastercard. Specifically, we updated the values for Subfield 7.

Clarity on a type field

We updated the documentation to clarify that the type (otype) field in the Get All Transaction History response can return an integer under some circumstances, even though string is the default datatype.

Location change for endpoint

We have moved the Replace Lost/Stolen Card endpoint from its old page to the main Reference section.

New entry types for Auth API

The entry_type field in both versions of the Auth API now supports two new entry types for Mastercard only:

• E-Commerce
• Card on File

MCCs for velocity ALCs

For velocity ALCs you can now specify which MCCs to apply the ALC to. For example, you can apply one velocity limit to gas pumps, another to grocery stores, and another to video games.

These endpoints have changed to accommodate velocity MCCs:

• Get Auth Control — Addition of beginningMcc and endMcc so that you can retrieve individual controls with a particular MCC range. In the response, the beginning_mcc and end_mcc fields are present only when the MCC range exists.
• Set Account-Level Auth Control — The new mccControls input parameter permits you to set ALCs for several MCC ranges with one request.
• Delete Account-Level Auth Control — Addition of beginningMcc and endMcc so that you can specify an individual control with a particular MCC range.

We've also reorganized the ALC guides to break out the different ALC types into their own guides. This is how they appear now:

• Account-Level Authorization Controls — We've added a new use case for MCC ranges.
  • Designing Authorization Controls — There's a new subsection of the workflow when velocity MCCs are involved.
    • Velocity Control Design — Additional information for MCCs
    • MCC Control Design — No new content
    • Merchant ID Control Design — No new content
  • Setting ALCs — Now with instructions for the new use case
    • Set Velocity Controls — Additional information for MCCs
    • Set MCC Controls — No new content
    • Set Merchant ID Controls — No new content

The MCC and Merchant ID ALC Example page also has a section on velocity MCC controls.

New field for the ODAA event

We added the source_id field to the ODAA: overdraft_authorization event. It contains the auth_id of the transaction that used overdraft funds.

Active accounts and billpay endpoints

We changed the behavior of four billpay endpoints to require that the account in accountNo be active (status: N) before the endpoint can be called. If the account is not active, a new status code is returned: Account not active

Nacha file names for ACH accounts

We have removed the following input parameters from documentation:

• Add ACH Account
  • fileFirstName
  • fileLastName
• Add ACH Account Corporate
  • fileCompanyName

Our documentation had indicated that the values in those fields would be included in outgoing Nacha files. However, not all clients were using those parameters in that way, because there was confusion between those parameters and firstName, lastName, and companyName. To comply with Nacha directives and enforce consistency in API usage, we are asking our clients to consider the parameters below to be required:

• Add ACH Account
  • firstName — Supports 40 characters to be stored in the Galileo system, but only the first 9 characters will be included in the Nacha file.
  • lastName — Supports 40 characters to be stored in the Galileo system, but only the first 12 characters will be included in the file.
  • Take care that the most identifiable portion of the account holder’s name is in the first 9 and 12 characters of firstName and lastName, respectively.
• Add ACH Account Corporate
  • companyName — Supports 40 characters to be stored in the Galileo system, but only the first 22 characters are included in the Nacha file so take care that the most identifiable portion of the company name is in the first 22 characters.

Galileo clients that support ACH payments should review their ACH accounts to verify that first_name and last_name or company_name are properly populated. If they are not, use Modify ACH Account to populate those parameters.

Fee otypes

The About Fees guide incorrectly stated that fee otypes can be found in the Funds Flow document provided by Galileo. This has been corrected.