Card Event Log
The type of the card event.
verification: represents a verification that merchant or wallet makes to ensure that the card exists and is activeauthorisations: represents a charge attempt on the cardfinancials: represents a clearing (i.e. settlement) event on the cardreversals: represents a dropped charge on the card
verification, financials, reversals, authorisations The ID of the transaction (on the processor's end)
The ID of the lifecycle (on the processor's end). A lifecycle ties a set of transactions together. For example, you might see authorisations, financials, and reversals for a single lifecycle, representing that a certain amount was authorized, partially captured/settled, and the remainder was reversed.
The merchant description on the processor's end. Note that this may not be cleaned, and comes directly from the processor. Slash processes the merchant's name into something readable when creating a Transaction, which may explain a discrepancy between the two.
The ID of the card
The last 4 digits of the card
The name of the card
The amount of the transaction, in the smallest unit of the currency (e.g. cents for USD)
Whether or not Slash approved this transaction. Note that Slash only has the authority to approve or deny authorisations.