Transaction data model overview

Our transaction data model is designed to be a unified structure that handles both monetary (financial transfers) and non-monetary (administrative events like logins or profile changes) transactions. This flexible model serves as the foundation for all event monitoring, ensuring consistent data structure regardless of the event type.

Key components

At its core, every transaction includes standard identifiers for the event and the associated customer, along with a timestamp. The model supports extensive customization through custom fields, allowing you to append key-value pairs (strings or decimals) to capture specific business context alongside the standard data.

Monetary transactions

For transactions involving funds, the model expands to include specialized types such as Bank Payments, Card Payments, and Remittance. 

Non-monetary transactions

Non-monetary transactions are not captured yet but will be in the future. 

They model administrative or behavioral events that do not involve a direct transfer of funds but are relevant to risk. They utilize the same core structure as financial transactions. Common examples include: Card activation, location events, login attempts, and profile updates.

Next steps

• API Documentation: For full understanding of the transaction model please refer to our Transactions API documentation.

• Bulk Uploads: for details on how to upload transaction in batches by file, please see our knowledge base article on Batch transaction upload.