Token and NFT Purchases (Journal)
Access Prerequisites
- Permission (module):
viewBuyTokensJournal - License/Feature: None
- Menu container: GENERAL → group Transaction Journals → Token and NFT Purchases (
/buy-tokens-journal)
In the menu, this item may appear labeled as "NFT Transactions"; technically it is the buy track of any tokenized asset sold by the platform — tokens and NFTs.
What it is / when to use
Records each sale/purchase of a tokenized asset (buy track): who purchased it, which asset (asset_id), at what price, and in which currency. The operator uses it to audit a specific purchase, verify which wallet the asset was delivered to, and check two important flow markers: whether the owner/fundraiser was paid (paid_owner) and whether there was a call to the blockchain/PGH service (pgh_call).
Prerequisites
- Permission:
viewBuyTokensJournal(dual permission — CPM enum + dynamic module in DB). - License/Feature: none.
- Dependencies on other screens: None. The track is fed by the asset purchase audit in the OrderBook/OBS.
Step by step
- Go to Transaction Journals → Token and NFT Purchases.
- The listing loads paginated from the server.
- Search by customer ID or asset ID in the search field (500 ms debounce).
- Click View details to open the modal with the full track.
Filters and columns
| Filter / Column | What it shows / does | Data source |
|---|---|---|
| Search (customer or asset) | Filters by customerId or assetId. 500 ms debounce. | search parameter. |
Date (when) | When the purchase occurred. | when. |
Asset (assetId) | Identifier of the purchased asset. | asset_id. |
Customer (customerId) | Buyer. | customer_id. |
Price (price) | Amount paid, with the monetary unit. | price (BigNumber) + unit_of_money. |
| Actions | Opens the full detail. | openTransactionDetails(buyTrack). |
Detail modal fields
| Field | What it shows | Effect/reading |
|---|---|---|
| Transaction ID | Track identifier. | Key for support/audit. |
Asset (asset_id) | Asset sold. | — |
| Source customer | Buyer's e-mail (resolved) or the raw customer_id. | The UI resolves the e-mail by looking up users. |
| Destination customer | Recipient's e-mail/ID, when the purchase delivers to another user. | customer_id_to. |
| Destination wallet | Wallet to which the asset was delivered. | wallet_id_to. |
| Blockchain ID | On-chain reference of the asset, when applicable. | blockchainId. |
| Currency / Price | Unit and value of the purchase. | unit_of_money / price. |
Owner paid (paid_owner) | Indicates whether the transfer to the asset owner/fundraiser has already been settled. | Yes/No — useful for reconciliation on the house/fundraiser side. |
PGH call (pgh_call) | Indicates whether the operation triggered the blockchain service (PGH) to complete the on-chain delivery. | Yes/No — distinguishes purchases already settled on-chain from purely internal ones. |
Date (when) | Moment of the purchase. | — |
Actions and modals
- View details: opens
BuyTrackDetailsModalComponent(840 px), read-only. Resolves buyer and recipient e-mails from the user registry.
Business rules / considerations
Attention
paid_owner = Noon a completed purchase signals a pending transfer to the owner/fundraiser — cross-check with Distributions/Commissions before advising.pgh_call = Noindicates that the on-chain delivery has not yet been triggered (or the purchase is purely internal). For assets that require on-chain delivery, this may indicate pending work by the watcher.- The sale value reflects the operation price; in book markets, the house revenue comes from the spread between the limit price and the execution price — it is not directly visible on this line; check the financial journals.
- Financial values:
priceis BigNumber — no rounding at the source; the UI formats to 2 decimal places for readability.