/transactions
endpoint allows you to operate on the Transaction entity.
Calling GET /transactions/{transactionId}
will return the entire transaction payload and rule execution results for the transaction with the corresponding transactionId
Unique Transaction Identifier
Unique transaction identifier
Timestamp of when transaction took place
Model for rule action if a rule is hit. This is returned in the API response and can be configured on Console by operational accounts like a Compliance Analyst
UserId for where the transaction originates from
UserId for transaction’s destination. In other words, where the value is being transferred to.
Model for transaction states. E.g. Processing, Refunded, Successful etc.
Model for transaction amount details
Model for transaction amount details
Payment details of the origin. It can be a bank account number, wallet ID, card fingerprint etc.
Model for origin funds information
Type of produce being used by the consumer (ex wallets, payments etc)
Whether a promotion code was used or not the transaction
Reference field for the transaction indicating the purpose of the transaction etc.
Model for device data
Model for device data