- Modification to the Transaction schema where the
transaction.events.amountfield 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
200response is returned to indicate a successful decline (coming to Sandbox on September 27; no Production impact)
digital_card_art_token field will be accepted in request payloads when creating or updating a card object. Users will be able to pass in a specific card art token to be associated with a card, which will determine the card art displayed when the card is added to a digital wallets. Additional documentation for using this feature to come. Note that in the near-term, the token will not be returned via the API (i.e., will not be visible in GET /cards calls or response schemas when creating or updating cards).
A new “KYC-exempt” workflow will be added to our “create an individual or business account holder” endpoint. This will allow users with pre-approved use cases (e.g., authorized user cards) to create representations of their cardholders on the Lithic platform without having to run a full KYC process. See documentation here for details.