Platform Revenues
Access prerequisites
- Permission (module):
viewGeneralJournal - License/Feature: None.
- Menu container: GENERAL → Operations group
What it is / when to use
Daily ledger of the revenues/financial entries retained by the house — the taxes/fees and other amounts appropriated by the platform across user operations. It is the consolidated view of how much the platform collected in each transaction, with the detail of the flow (transactionFlow), the transacted currency, and the participants. Use it to perform reconciliation and audit platform revenue per token.
Prerequisites
- Permission:
viewGeneralJournal(dual permission — CPM enum + dynamic module in DB). - License/Feature: None.
- Dependencies on other screens: entries are generated by financial operations (purchases, exchange orders, settlements). This screen only queries them.
Step by step
- Access the menu Operations → Platform Revenues.
- Filter by token (the token list is loaded via
getTokens; "all" for all tokens). - Use the search to refine results and click the receipt icon to open the entry details.
Filters and columns
| Filter/Column | What it shows | Data source |
|---|---|---|
| Token filter | Restricts entries to a single token (or All) | selectedDepositType → getTaxTransactionHistoryAdmin |
| Search | Refines by transaction | selectedStatus (search field) |
| Date | Date/time of the entry | when |
| Transaction origin | customerFromEmail | |
| Name | Name of the originating customer | customerFromName |
| Type | Transaction flow | transactionFlow |
| Amount | Appropriated amount | totalAmount |
| Transacted currency | Unit of the entry | monetaryamount.unitOfMoney |
Actions and modals
- View details (receipt): opens the entry details modal (
DetailsViewTaxComponent) with the complete flow of the transaction that generated the revenue.
Business rules / considerations
Attention
- This is a query/audit screen — it does not create or reverse entries.
- The source of revenues includes transaction fees, spreads, and other appropriations. To understand exchange order spreads, see the corresponding page.
Spread as revenue
- A significant portion of the displayed revenue comes from the limit × execution spread of exchange orders: the seller receives at the limit price and the house captures the delta. These amounts appear here as platform revenue. (Details in Exchange Orders.)
- Financial values: treated as BigNumber — no rounding; verify the token's decimal places.
- Idempotency: entries derive from idempotent operations by
externalIdin FinLib; anE00021at the origin means the operation has already been settled (success) — the corresponding revenue entry is not duplicated.