August 20, 2024
Tokenization Data Efficiency Improvements
Get a card's tokenizations now includes an option to pass ALL
in the tokenization_channel
field. This will return both digital wallet tokenizations and merchant (card on file) tokenizations. Previously the endpoint would need to be called two times with DIGITAL_WALLET
and MERCHANT
respectively to retrieve all tokenizations for the card.
Addendum to Changelog - August 1, 2024
The changelog published on August 1st, 2024 detailed the addition of a new amounts
object which is now populated in transaction events. In addition to amounts
, one more field was added at the event level, effective_polarity
, which denotes the polarity (CREDIT
or DEBIT
) of the merchant, cardholder, and settlement amounts found within the new amounts
object. The values stored in the new amounts
fields are not polarized, and effective_polarity
should be referenced to determine the polarity of included values.
As an example, this is the data structure now available in transaction events:
"effective_polarity":"DEBIT",
"amounts": {
"merchant": {
"amount": 10000,
"currency": "USD",
},
"cardholder": {
"amount": 7500,
"currency": "CAD",
"conversion_rate": "0.750000"
},
"settlement": {
"amount": 0,
"currency": "USD",
"conversion_rate": "0.000000"
}
}
NOTE: effective_polarity
refers only to the amounts found within the new amounts
object, with no impact to the long-standing amount
field which remains available in each transaction event. To reiterate, the historical amount
value (referring to the merchant amount) will continue to be populated with polarity and with no scheduled discontinuation date at this time.
If you have any questions or concerns about this change, please reach out to [email protected].