Earlier this year, we announced two breaking changes that you should be aware of. This will be the final posted announcement before these changes are deployed on September 27 (Tuesday). Please refer to this announcement for more details, and reach out to [email protected] should you have any questions.
- Modification to the Transaction schema where the transaction.events.amount field will become signed (deployed to Sandbox on August 30 and coming to Production on September 27)
- Modification to the Simulate Authorizations feature where if a simulated transaction is declined, a 200 response is returned to indicate a successful decline (coming to Sandbox on September 27; no Production impact)
As part of our Advanced KYC workflow that can be used to create account holders on the Lithic platform, tokens (i.e., unique identifiers) representing both account holders and identity documents are used. Previously, the naming of various token types were inconsistent across our documentation and endpoints. We have deployed a fix that now clarifies the use of each of those tokens, and our documentation has been updated accordingly. See the Initiate Document Upload and Get Document Upload Status sections of our documentation for the latest.