December 20, 2022

Reminder of Upcoming Sandbox Changes

Following up on our November 7 and December 7 emails, we would like to remind users of a set of upcoming changes to the Lithic API in Q1 of 2023. These changes will be deployed to our sandbox environment on January 4, 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 production impact until February 8, 2023.

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:

Deploy Dates:

  • 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 will also be updated to reflect the changes. There will be no impact to the schema of ASA requests.

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

All of the above changes will be available to begin testing in sandbox on 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.