Transactions - Operator user
A guide to the global Transactions view used by Operators to monitor and investigate payment activity in DJUST.
Introduction — Operator Transactions
The Transactions view (Operator) allows an Operator to access and supervise all transactions processed via DJUST Pay within their authorized store scope.
It provides a consolidated financial overview built on the latest payment event of each transaction.
Accessing the Transactions view
The Transactions page is the main screen used by Operators to supervise all financial transactions processed via DJUST Pay.
This first view is a global overview of transactions built on the latest event of each transaction.
Each row in the table represents one transaction (linked to one commercial order), displayed through its most recent event.
The Transactions view is accessible from the DJUST Back Office via the main navigation menu :
- Connect to the Back Office as an Operator user
- Open the DJUST Pay section in the main menu
- Click on Transactions
Structure of the Transactions table
The table below describes the columns displayed in the Transactions list and the information associated with each transaction.
| Column | Description | Business purpose / Notes |
|---|---|---|
| Order Reference | Reference of the DJUST commercial order linked to the transaction. | Main business identifier linking Orders, Transactions and financial events. |
| Customer account | Name of the customer account associated with the transaction. | Example: “Agence Lyon”, “Usine Clermont”, “Paris Rive Gauche”. |
| Payment method | Functional payment label used by the customer. | Examples: Credit card, Purchase card, SEPA transfer. |
| Payment network | Payment network used to route the transaction. | Card networks (Visa, Mastercard…) or transfer network (SEPA). |
| PSP Reference | Unique and stable payment reference stored at payment level. | Used as grouping key for all events related to the same payment. Does not change over time. |
| Event ID (latest event) | Identifier of the most recent event received for the transaction. | Changes over time. Updated whenever a new payment event (AUTHORIZATION, PAID, REFUND…) is received. |
| Event Status (latest) | Status of the most recent event associated with the transaction. | Reflects the current payment state. Makes this a “latest state” view. |
| Amount | Commercial amount of the order. | Represents the financial value associated with the transaction. |
Created at (createdAt) | Exact timestamp of the transaction creation. | Corresponds to the moment the transaction record is created in DJUST. |
Updated at (updatedAt) | Exact timestamp of the last update of the transaction. | Updated every time a new payment event linked to the transaction is processed. |
| Status | Operational lifecycle status in DJUST. | Derived from the latest payment events (see Status logic below). |
Transaction Lifecycle Status
The Status column represents the operational lifecycle of the transaction in DJUST.
It is an aggregated business status derived from the latest payment event(s).
Available lifecycle statuses:
- Payment authorised
- Payment in progress
- Refund in progress
- Closed
Single logistic order context :
In a single logistic order context, the transaction lifecycle status is directly derived from the latest payment event status of that logistic order.
| Latest Event Status | Transaction Lifecycle Status |
|---|---|
INIT_PAYMENT | Payment authorised |
CARD_REGISTERED | Payment authorised |
WAITING_AUTHORIZATION | Payment authorised |
AUTHORIZED | Payment authorised |
WAITING_PAYMENT | Payment authorised |
WAITING_REFUND | Refund in progress |
WAITING_BANK_WIRE_REFUND | Refund in progress |
REFUND_FAILED | Refund in progress |
PAID | Closed |
REFUSED | Closed |
REFUNDED | Closed |
Multi logistic orders context
In a multi logistic orders context, the transaction lifecycle status is an aggregated status computed from the latest event of each logistic order.
| Transaction Lifecycle Status | Aggregation Rule |
|---|---|
| Refund in progress | All logistic orders have a latest event in refund-in-progress statuses (WAITING_REFUND, WAITING_BANK_WIRE_REFUND, REFUND_FAILED). |
| Closed | All logistic orders have a latest event in final statuses (PAID, REFUSED, REFUNDED). |
| Payment in progress | At least one logistic order has a PAID event AND not all logistic orders are in a final status. |
| Payment authorised | No logistic order has reached PAID. |
Searching, filtering and sorting transactions
The Transactions view allows Operators to efficiently navigate large volumes of financial data by combining search, filtering and sorting capabilities.
These tools help users quickly identify relevant transactions for investigation, reconciliation or reporting.
All search, filters and sorting operations are applied within the current store context in the Back Office.
Search
A global search field allows Operators to search transactions across key business and payment identifiers.
| Searchable Field | Marketplace only |
|---|---|
| Commercial Order Reference | No |
| Customer account – Name | No |
| Customer account – ID | No |
| Supplier name | Yes |
| Supplier external ID | Yes |
| PSP Reference | No |
| Last Event ID | No |
Filters
Filters allow Operators to narrow down the list using structured criteria.
All filters are cumulative (AND logic). If no filters are applied, all transactions visible within the current store scope are returned.
| Filter | Type | Possible Values / Format |
|---|---|---|
| Payment method | Multi-select | CREDIT_CARD, PURCHASE_CARD, SEPA_TRANSFER (platform-configured values) |
| Payment network | Multi-select | VISA, MASTERCARD, SEPA |
| Amount | Range | minAmount / maxAmount (numeric, in transaction currency) |
| Status | Multi-select | Payment authorised, Payment in progress, Refund in progress, Closed |
| Last event status | Multi-select | INIT_PAYMENT, AUTHORIZED, PAID, REFUSED, REFUNDED, PARTIALLY_PAID, OVER_PAID, RECONCILED, etc. |
| Created date | Date range | createdFrom / createdTo (ISO 8601 format) |
| Updated date | Date range | updatedFrom / updatedTo (ISO 8601 format) |
Sorting
Transactions can be sorted to prioritize recent or financially relevant activity.
| Sortable Field | Default Order |
|---|---|
| Updated date | Descending (most recent first) |
| Created date | Descending |
| Amount | Descending |
| Commercial Order Reference | Ascending |
Navigation behavior
In the Operator view:
- Clicking on a row allows the Operator to access the list of the Transaction events related to that transaction.
The Operator can therefore:
- View the full payment event timeline (authorization, paid, refund, etc.)
- Investigate payment issues
- Access technical PSP references and event details
Updated 11 days ago