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).

Information available in the Event Details view

Transaction fees

On a marketplace, every capture carries transaction fees charged by the payment provider. These fees are debited from the marketplace balance account and returned on the transaction event of the capture they belong to.

They are exposed in the amounts of the event, in the transactionFees field:

{
  "eventId": "EVT-001",
  "status": "CAPTURED",
  "currency": "EUR",
  "amounts": {
    "amountWithTaxes": 100.0,
    "amountWithoutTaxes": 80.0,
    "commissionsAmount": 5.0,
    "withoutCommissionsAmount": 95.0,
    "transactionFees": 0.35
  },
  "commissions": {
    "marketplaceCommission": 2.0,
    "platformCommission": 2.5
  }
}

Rules to keep in mind:

• Marketplace and operator only. transactionFees is returned to callers using dj-client: OPERATOR on a marketplace. It is absent from the supplier view.
• Nullable. The field stays empty until the payment provider has settled the fees for that capture. An empty value means not settled yet, not no fees.
• Commissions stay gross. marketplaceCommission is still expressed gross of these fees — no net amount is derived from transactionFees. Compute your own net figure if you need one.
• Per capture. Fees are attached to the capture event, not to the transaction as a whole. A transaction captured in several steps carries fees on each capture event.
• Independent of the commission. A commission at zero does not prevent the fees from being returned.

In the Back-Office, the Amounts section of the event detail displays a Transaction fees line next to the commissions, in the currency of the event. The line is shown only when fees are known for that event; the other lines of the section, the event table and the CSV export are unchanged.

API Reference

Event details can also be retrieved programmatically via the DJUST API.

Endpoint: GET /v1/transactions/events/{eventId}

operationId: ADM-TRANSACTION-552

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.