February 1, 2023

Final Reminder of Upcoming Production Changes

This is a final reminder of a set of upcoming changes to the Lithic API production environment that will be deployed on February 8, 2023.

These changes relate to the transaction object that is sent via transaction webhooks and returned via the transactions API endpoints. There will be no impact to the schema of ASA requests.

These improvements were developed based on feedback we’ve received from customers over the past year, and we believe will make building and scaling your card programs on the Lithic platform easier and more intuitive.

We have prepared two detailed resources to assist in this transition:

A dedicated guide detailing what the changes are and how to prepare for them
An updated transactions flow page that articulates the possible transaction lifecycle paths you can expect with these changes incorporated

Deploy Dates:

[Deploy Completed] Sandbox Environment: Effective January 4, 2023 (Wednesday) ~17:00 UTC / Noon EST
Production Environment: Effective February 8, 2023 (Wednesday) ~17:00 UTC / Noon EST

Impacted Surfaces:

The new transaction object schema will be evident across two surfaces:

The transaction webhook
The response payload from the transactions API (GET /transactions)

Note that after the deploy dates, all transactions (historical and new) will be returned with the new schema. Our client libraries have also been updated to reflect the changes.

Summary of Changes:

Card object to be replaced with a card_token
Funding array to be removed
Modification of status enums to clarify a transaction’s place in its lifecycle:
- Removal of BOUNCED and SETTLING
- VOIDED broken out into VOIDED and EXPIRED
Modification of events[*].type enums to bring more visibility into transaction lifecycle stages:
- Breaking out AUTHORIZATION, VOID, and RETURN
- Adding BALANCE_INQUIRY and CREDIT_AUTHORIZATION_ADVICE

All of the above changes are already available for testing in sandbox as of January 4. We sincerely appreciate your attention to these changes. Make sure to subscribe to our status page in order to be notified of the changes. If you have any questions, please contact our support team.