---
agentTools:
  siteIndex: https://docs.tech.sofi.com/llms.txt
  projectIndex: https://docs.tech.sofi.com/pro/llms.txt
---

# September 2023

In September, we added a new reference page, adjusted the card-load scenarios, corrected STAR dispute otypes and Expire Hold status codes, clarified Get Access Token, corrected parameter descriptions, clarified an RDF field and AAPM, added new auth event fields, changed a table header for events and added a new status code for the Reissue Card endpoint. Click [**September 2023**](https://docs.tech.sofi.com/pro/changelog/september-2023) to see the details.

### New reference page

We added <a href="page:finding-transaction-data" target="_blank">Finding Transaction Data</a>, a page that summarizes where to find a particular transaction type across Galileo's various data sources.&#x20;

### Corrected card-load sequence

In <a href="page:scenario-17-card-load-maestro" target="_blank">Scenario 17: Card Load</a> and <a href="page:scenario-20-card-load-reversal-maestro" target="_blank">Scenario 20: Card Load Reversal</a>, we corrected the sequence of events to show that Galileo sends <a href="ref:api-reference-events-api-auth-payment" target="_blank">`AAPM: auth_payment`</a> when the load is approved, and then sends <a href="ref:api-reference-events-api-pmt" target="_blank">`BPMT: pmt`</a> when the load is posted to the cardholder account.

### Dispute otypes for STAR

The dispute-related otypes for STAR were incorrect in the <a href="ref:api-reference-transaction-types#disputes" target="_blank">Transaction Types</a> enumeration. They have been corrected.&#x20;

### Expire Hold status code corrections

The description text for the <a href="ref:post_expirehold" target="_blank">Expire Hold</a> status codes was incorrect. It has now been updated.&#x20;

### Get Access Token clarification

For the <a href="ref:post_getaccesstoken" target="_blank">Get Access Token</a> endpoint we clarified that when `type: 0` (card token), the CAD should always be used instead of the PRN.&#x20;

### Advanced Auth API Fields correction

We corrected <a href="doc:auth-api-field-detail#advanced-auth-api-fields" target="_blank">the descriptions for the ADVAF and AAFAL</a> parameters, which control whether to receive `advanced_auth_api_fields`.&#x20;

### Clarification in Customer Master RDF

We clarified that the `CURRENT BALANCE` and `AVAILABLE BALANCE` fields in the <a href="doc:secondary-rdf-reference#customer-master-rdf" target="_blank">Customer Master RDF</a> will be blank if there was no transaction activity for the account during the previous day.&#x20;

### Update to AAPM event

We removed the phrase "Available balance has changed" from the <a href="ref:api-reference-events-api-auth-payment" target="_blank">`AAPM: auth_payment`</a> description because the event is triggered when the card load is approved, not when it is posted. The <a href="ref:api-reference-events-api-pmt" target="_blank">`BPMT: pmt`</a> event is triggered when the card load is posted.&#x20;

### New fields for auth events

To the `BAUT`, `AAAU`, and `DAUT` events (<a href="ref:api-reference-events-api-auth" target="_blank">`auth`</a> and <a href="ref:api-reference-events-api-denied-auth" target="_blank">`denied_auth`</a>), we added these new optional fields:&#x20;

* `auth_id_response` — DE038
* `financial_network_code` — DE63SE1
* `stan` — DE011, system trace audit number

### Change to event fields tables

We made a minor change to the **Fields** tables on each event page: The center column now says **Default** instead of **Required**. We've added a note at the top of each table that links to <a href="ref:api-reference-events-api-about-events-api-paths-and-content-types#default-and-optional-fields" target="_blank">this section</a>, which explains what "Default" means as well as how Galileo handles empty fields.&#x20;

### New status code for Card Reissue Endpoint

The <a href="ref:post_reissuecard" target="_blank">Reissue Card</a> endpoint has a new error code: “Lost/Stolen Reissue Error”: 589-12.&#x20;