Currency Field Type Change in Transaction Object

At a Glance

• Release date: March 31, 2025
• Impact: Card transaction currency fields are changing from enum to string type
• Audience: All customers using the Card Transactions endpoints and/or webhooks
• Action required: Pull the latest SDK; modify any code that expects currency enum type in the transaction
• Products affected: Card Transactions endpoints and webhooks

Overview

We are converting all currency fields in the transaction object, at the transaction level and event level, from enum to string type. This change enables more flexible support for a broader range of currency codes now and in the future.

We are implementing this in response to an upcoming ISO 4217 currency code amendment on March 31, when the Netherlands Antillean guilder (ANG) will be replaced by the Caribbean guilder (XCG) for transactions in Curaçao and Sint Maarten. Customers who have processed transactions in the Netherlands Antillean guilder have already been notified with further guidance.

Impact

The transaction object is returned by the:

• Get Card Transaction endpoint,
• List Card Transactions endpoint, and
• Event webhooks of type card_transaction.updated

Customers using any of the above will observe the following impact:

• All currency fields will be of type string instead of enum
• The values in these fields will remain unchanged (e.g., "USD", "EUR", and so forth will continue to display as is)

Required Actions

To prepare for the introduction of the Caribbean guilder currency code, by March 31:

• Update to the latest SDK version, released this week, to properly handle the currency fields as strings
• Prepare your applications to parse string-type currency codes from the transaction object

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.