March 2023

In March 2023 we added billing cycles for secured credit products, updated an RDF, explained AAAU message differences, added info on blocking transactions, added a new card transaction scenario, made some parameters required, changed the example sandbox URI, updated accountNo for Add Card, detailed frozen card behavior, changed some authorization response codes, updated the Statements guide, reorganized the Auth API guide, published an Offline PIN guide, refined our transaction-reversal process, implemented emboss pausing and clarified event message timestamps. Click March 2023 to see the details.

Billing cycles for secured credit products

Galileo offers three billing cycle configurations for secured credit products, which can be configured at either the program or product level, according to your business plan and the agreement with your sponsor bank. See Billing cycles section to the Setup for Galileo Secured Credit guide, which explains the different configuration options.

New Fleet Data RDF format

The Fleet Data RDF now includes JSON to accommodate the nested rows for each entry.

UPDATE: The instances of CDF in this entry were changed to RDF.

Auth message differentiation

We added a section in the Authorization guide to show how to differentiate among the different types of AAAU: auth messages.

Blocking transactions section

We added a Blocking transactions section to the About Transactions guide, which explains how you can block various types of transactions.

New card transaction scenario

We added Scenario 20: Card Load Reversal (Maestro) , which shows an example of when a cardholder receives payment from an employer but the funds are reversed.

Required parameters for Create Group

We added information that the phone and phoneCountryCode parameters are required for the Create Group endpoint, both for root groups and non-root groups.

Sandbox API URL updated

We updated the examples in the reference documentation to reflect the new Sandbox URI:

Frozen card behavior

We updated the Card Statuses guide to include details about which transactions are affected by a card freeze and which are not, as well as a way to override the freeze on transactions that credit the account.

New Mastercard response codes

Mastercard has changed some of its authorization response codes. Check with Galileo to see if your program is using these new codes yet.

​​Card status or other conditionNew response code
  • C (canceled)
  • R (charged off)
  • Z (canceled without refund)
  • D (disabled)
  • V (voided)
  • W (waiting for payment)
  • AVS/ASI check failure
  • Invalid account
  • 78 — Invalid Account
  • X (set to emboss)
  • Y (shipped, ready to activate),
  • B (blocked)
  • O (operations hold)
  • Tokenization blocked by product settings
  • 57 — Transaction not permitted
  • L (lost card)
  • A (lost card waiting for sufficient funds)
  • 41 — Lost Card
    Q (delinquent)51 — Insufficient Funds
    Fraud63 — Security Violation
    MCC product- or account-level block03 — Invalid Merchant
    Max system amount reached13 — Invalid Amount
    Frozen card62 — Restricted card

    Statements update

    We've updated the Statements guide with current fields and definitions.

    Auth API doc reorganization

    We have divided the Authorization Controller API guide into three guides for ease of navigation. The content was not updated:

    New Offline PIN guide

    We published the Offline PIN guide, which addresses how to set PINs in some non-U.S. jurisdictions.

    API transaction reversal

    From the guides that explain how to initiate transactions with the Program API—Creating a Payment, Creating an Account Transfer, Creating an Adjustment—we removed references to the corresponding reversal endpoints, because those endpoints do not produce good results in terms of funds flow. Instead, Galileo recommends using Create Adjustment to reverse out payments and adjustments, using the appropriate type to indicate a reversal.

    Pause or cancel card emboss

    In the case that you want to pause a card embossing, such as with Digital First cards, you can now call Set Account Feature with featureType: 30. You can use this feature to cancel an emboss permanently or to resume it at a later time.

    Event message clarification

    We added a section to Event Setup and Configuration to clarify the relationship between event timestamps and account balance.