Event details
A guide to the detailed view of a transaction event and the technical and business information it contains.
Introduction — Event Details
The Event Details view provides the complete and granular detail of a single transaction event.
This is the lowest level of the Transactions feature, exposing the exact technical and financial snapshot of a specific payment step.
It is designed to:
- Investigate payment issues
- Understand precisely what happened at a given lifecycle step
- Retrieve technical PSP references
- Access detailed financial breakdowns
It complements:
- The Transactions list (aggregated, latest-state view)
- The Events list (timeline view)
By providing the full detail of one specific event.
Accessing an event detail
Users can access the Event Details view in two ways:
1- From the Events list
- Click on any event in the list of events of a transaction.
- This allows access to the detail of any lifecycle step (INIT_PAYMENT, AUTHORIZED, PAID, REFUND, etc.).
2- From the Transactions list
- Click on any transaction in the Transactions list.
- In this case, the user is automatically redirected to the detail of the latest event only (the most recent event associated with that transaction).
Example:If a transaction has the following events: INIT → AUTHORIZED → PAID
Access from the Transactions list will open:
Event detail: PAID
Information available in the Event Details view
| Category | Field | Description |
|---|---|---|
| Identification | Commercial Order Reference | Reference of the DJUST commercial order |
| Logistic Order Reference | Reference of the logistic order (if applicable) | |
| PSP payment reference | Common PSP reference identifying the initial payment | |
| Event ID | Unique identifier of the event | |
| Event status | Technical status of the event | |
| Event creation date | Exact timestamp when the event was created | |
| Business context | Customer account | Customer account that initiated the payment |
| Supplier | Supplier concerned by the event (Operator view only) | |
| Payment method | Payment method used (e.g. credit card, bank wire, purchase card) | |
| Payment network | Payment network used (e.g. Visa, Mastercard, SEPA) | |
| Financial details | Amount without commissions | Amount excluding commissions (+ currency) |
| Commission amount | Commission applied (+ currency) | |
| Total amount | Total amount (HT / TTC) | |
| Authorization | Authorisation code | Bank authorisation code returned by the acquirer during payment processing. Available for purchasing card transactions only; null for standard card payments. Also included in transaction event CSV exports. |
| Investigation data | Error code | Technical error code (if the event failed) |
| Error message | Human-readable error message (e.g. “Insufficient funds”) |
API Reference
Event details can also be retrieved programmatically via the DJUST API.
Endpoint: GET /v1/transactions/events/{eventId}
operationId: ADM-TRANSACTION-552
| Header | Required | Description |
|---|---|---|
dj-client | Yes | OPERATOR or SUPPLIER |
dj-api-key | Yes | API key |
| Path parameter | Required | Description |
|---|---|---|
eventId | Yes | Unique identifier of the transaction event |
Visibility rules
- OPERATOR (
dj-client: OPERATOR): can access any event across all suppliers and transactions. - SUPPLIER (
dj-client: SUPPLIER): can access only events linked to their own logistic orders and transactions.
Updated 7 days ago