July 2026

In July 2026 we modified an ID format, clarified ID updating, fixed response codes, removed an improper mapping, corrected a corporate hierarchy detail, added Digital First options, modified a parameter description, added a search field, rebranded our documentation, clarified Risk 2.0 fields, and added IIAS fields to the Auth API. Click July 2026 to see the details.

Modified INE info

We updated the information for idType: 17 in the Customer ID Types enum to show that for the <<glossary:INE> we can validate either the clave de elector or the CIC.

Clarified ID updating

For the Update Account endpoint we clarified that the id2 and id3 fields cannot be nullified or cleared—they can only be changed. Further, omitting the fields in an endpoint request does not change or delete the values in the system.

Corrected response codes for balance inquiries

In the Authorization Controller API guide, we list the response codes to return when a balance inquiry is for an account that does not exist. The codes for STAR and Discover were incorrect.

Corrected mapping

In the About Accounts guide, the externalCustomerId field was improperly mapped to a field in the Customer Master RDFs. In fact, it does not map to a field in the RDFs. We have removed the error.

Corrected detail for corporate hierarchy group ID

In the Creating a Corporate Hierarchy guide, we corrected a detail about where to find the group ID. The guide previously said this field could be found in the Posted Transactions RDF as CH GROUP ID, but this was an error.

New Digital First options

We have added a few enhancements to your Digital First implementation:

• When you ask SoFi Tech Solutions to preset account features 20 or 21 to protect the card in transit, this preset now applies to reissued and replaced cards, not just new cards.
• You can now call Activate Card to remove the block from account features 20 or 21, not just Set Account Feature.

The previous methods of setting and removing the block are still valid.

Dependency removed from parameter

From the description for the VLDLV parameter, we removed language saying the parameter was valid only when using Program API or when TOTID was set (legacy CIP integration). This is a change to the documentation, not to system behavior.

New field for account searching

We've added a new request parameter to Get Account by ID: customerId, which corresponds to client_id in the code and GALILEO CLIENT ID in the RDFs. When you pass this parameter the endpoint returns the external customer ID, if it exists.

Documentation rebrand

Galileo is now SoFi Tech Solutions, so we updated our documentation to align with the company rebrand. This includes the following changes:

• Changing instances of "Galileo" to "SoFi Tech Solutions" across Guides, API Reference, Recipes, and clients-only docs in the Console
• Updating the look and feel of the docs site
• Changing the docs site URL to docs.tech.sofi.com

We will continue to make rebrand-related updates over the coming weeks.

Clarity on ID generation

In the Customer ID and Entity ID fields for Verify Customer we clarified that the ID can be generated either by Galileo or by the client (you).

IIAS updates

We updated the iias_info object on the Auth API pages to show all possible fields for that object. We also added more detailed information in the Auth API Field Detail guide about those fields.

This is an update to the documentation, not to system functionality.