In July 2022 we added more network examples, added a disputes guide, reorganized the cards docs, added information on Galileo Secured Credit with Dynamic Funding, removed a parameter, clarified some descriptions, added Event API fields, added ALC documentation, added Auth API information and removed a Create Location parameter. Click July 2022 to see the details.
On the Card Transaction Examples page we added Other network codes tables to show the transaction codes when the transactions happen on other networks.
We completed a new guide, About Disputes, which explains the dispute process in general and then describes how disputes work at Galileo. Both card and ACH transactions are covered.
We've published a suite of new product documentation to help you take advantage of Galileo's capabilities to drive customer activation and engagement. We have also reorganized much of the card-related content to make it easier for you to find what you're looking for, whether it be business cases or implementation instructions.
- Maximizing Customer Activation Rates — A new guide to help you get your new customers to start spending on your platform and strategies to keep customers engaged
- Choose a Card Strategy — A new guide that explains the card products that Galileo offers and how you can use those products to meet your business goals
- Setting Up a Card Program — A new guide on the steps to take during the lifecycle of a card
We've also reorganized our cards-related documentation into three new sections: Card Strategy, Card Management and Card Implementation.
We added information on the new Dynamic Funding product. We also renamed and moved the Galileo Secured Credit guide to the Credit section in the sidebar. Major additions for Dynamic Funding are:
- Dynamic Funding in About Galileo Secured Credit
- Setup for Dynamic Funding in Setup for Galileo Secured Credit
- Considerations for Dynamic Funding in Developer Setup for Galileo Secured Credit
- Secured credit account structure and Secured credit authorization and settlement in Galileo Secured Credit Workflows
From the Add Card endpoint we have removed the
We've rewritten the descriptions for the Get Balance response fields to better explain exactly what each balance-related field means.
We removed the phrase "This event is not sent when a PIN is set for the first time” from the description for the
PINC: PIN_changed event.
For these events you now have the option to receive the
rrn (Reference Retrieval Number) and
We clarified that
featureType: 21 of the Set Account Feature endpoint does not block card loads.
In the API Reference, we changed the Program API category "Prepaid" to "Instant Issue."
Galileo now offers account-level authorization controls (ALCs), which allow you to set velocity, MCC and merchant ID controls at the account level.
- About Account-Level Authorization Controls — Explanation of ALCs plus use cases.
- Designing Authorization Controls — Lays out the rules that govern the different controls at both the product and account levels.
- MCC and Merchant ID ALC Examples — Multiple tables to illustrate how MCC and merchant ID controls are applied
- Setting Account-Level Authorization Controls — Procedure for using the ALC-related endpoints.
- Reference for six new endpoints:
We added information about
advanced_auth_api_fields to the Authorization Controller API guide.
We removed these parameters from the Create Location endpoint: