How the card was presented or authenticated for the purchase.Example:
ecommerceRepresents a unique identifier that is Base64 obfuscated. It is often used to
refetch an object or as key for a cache. The ID type appears in a JSON
response as a String; however, it is not intended to be human-readable. When
expected as an input type, any string (such as
"VXNlci0xMA==") or integer
(such as 4) input value will be accepted as an ID.The cashback reward amount earned on this transaction, in USD.Example:
6.9The datetime the card transaction was created.Example:
2023-12-01T05:00:00.401ZThe ISO 4217 currency code for the transaction amount.Example:
USDThe issuer-provided reason the transaction was declined.Example:
insufficient_fundsThe unique identifier for the card transaction.
Whether the transaction was made with a merchant outside the card’s home
country.
The transaction amount in the merchant’s local currency before conversion.Example:
6.9A user-provided note attached to the transaction.Example:
Team dinnerThe enriched or raw category label for the merchant.Example:
SoftwareThe four-digit ISO 18245 merchant category code (MCC).Example:
5734A URL to the enriched merchant logo image.Example:
https://logo.clearbit.com/example.comThe enriched or raw name of the merchant where the purchase was made.Example:
Acme CorporationWhen the transaction was settled by the card network.Example:
2023-12-01T05:00:00.401ZThe current lifecycle status of the transaction.Available options:
pending, completed, reversed, declinedThe type of transaction.Example:
spendThe transaction amount in USD.Example:
6.9
