August 27, 2024

Changes and Improvements

Beginning September 4th (Wednesday), several new fields will be added to the transaction object.

Aggregate Transaction Amounts

A new amounts object will be added to the top level of transactions. This new object contains multiple mutable aggregate amounts. These aggregate amount values represent the current state of the transaction, and may be updated as a result of subsequent transaction events.

"amounts": {
      "hold": { 
          "hold_amount": 0,
          "currency": "USD",
      },
      "merchant": {
          "cleared_amount": 7000,
          "currency": "USD",
      },
      "cardholder": {
          "cleared_amount": 9100,
          "currency": "CAD",
          "conversion_rate": "1.300000"
      },
      "settlement": {
          "amount": 7000,
          "currency": "USD",
      }
   }

This change is purely additive. There will be no impact to the existing aggregate amount field currently found at the top level of the transaction object nor any impact to transaction events and their amounts.

Transaction updated and account_token

Two additional fields will be added to the top level of the transaction object.

• updated: ISO 8601 timestamp for when the transaction was last updated by a transaction event.
• account_token: The token for the account which is associated with the transaction.

Bug Fixes

• It was reported that the updated_at field for tokenizations was not correctly populating. The fix will be released August 27 (today).
  • The updated_at field is returned in the following endpoints: Get a single card tokenization, Get a card's tokenizations, Update digital card art for a card tokenization, and Simulate a card's tokenization.

If you have any questions or concerns, please contact us via the HELP link in your Lithic Dashboard.

The Lithic changelog has an RSS feed! To monitor for new update announcements, subscribe with your preferred RSS reader.