A transaction list built into your Platform’s back office provides your Operations team the ability to locate specific transactions when users contact your Operations team.
A list view can provide an entry point into a detailed transaction view for further analysis.
An example is shown below for payouts. We recommend similar view be built for other financial transaction types, as your use case requires (e.g. deposits, conversions, card transactions..)
Building a transaction detail view into your back-office tooling can allow your Platform’s Operations teams to obtain in one view the details of a particular transaction, including references that may have been specified by users.
For example, this can allow identification of root causes for failed payments (e.g. due to mis-typed account numbers or beneficiary names)