Introduction — Transactions Export

The Transactions Export feature allows users to generate a CSV file containing transaction data for reconciliation, reporting and financial analysis purposes.

Exports are asynchronous and respect the same visibility and store scoping rules as the Transactions view.

The export is based on a combined view of Transactions and Events.

Scope & Visibility

Operator

An Operator can export transactions:

Within the current store (Back Office context)
Or across authorized stores (via API when dj-store is not provided)

In Marketplace mode, the export includes:

All suppliers within scope
Commission breakdown (platform / marketplace)

Supplier

A Supplier can export:

Only transactions linked to their own logistic orders
Only financial data within their own perimeter

Launching a Transactions Export

Users can launch a Transactions export directly from the Transactions list.

Where to launch

Connect to the Back Office (Operator or Supplier).
Open the DJUST Pay section.
Go to Transactions.
Apply filters if needed.
Click on Export CSV.

Export Format

The export format is:

CSV only
UTF-8 encoding
; separator
Line break: \n
First row = column headers
Dates formatted in ISO 8601 (YYYY-MM-DDTHH:mm:ssZ)

Email Delivery

Once the file is generated:

An email containing the download link is automatically sent to the connected user (the user who initiated the export).

The email includes a secure download link.

When launching the export, the user may optionally provide one or multiple CC email addresses.

The CC field accepts valid email addresses.
Multiple emails must be comma-separated.
All recipients will receive the same download link.

If no CC is provided, only the connected user receives the email.

Operator Export — Columns

Each row corresponds to one exportable transaction (or eligible event depending on configuration).

Column	Description	Notes
Logistic Order Reference	Reference of the logistic order	Business identifier
Creation date	Creation timestamp of the logistic order	ISO 8601 format
Customer account name	Name of the customer account
Customer account external ID	External identifier of the customer account
Supplier name	Name of the supplier	Marketplace only
Supplier external ID	External identifier of the supplier	Marketplace only
Payment method	Credit card, SEPA, Purchase card	Functional label
Payment network	Visa, Mastercard, SEPA	Technical routing info
Event status	Latest eligible payment event status	`PAID`, `REFUSED`
Logistic order status	Operational status of the logistic order
Payment status	Payment status of the logistic order
Total amount HT	Amount excluding taxes
Total amount TTC	Amount including taxes
Platform commission	Platform share of commission	Marketplace mode
Marketplace commission	Marketplace commission amount	Marketplace mode
Total commissions	Total commission amount

Supplier Export — Columns

Each row corresponds to one exportable transaction (or eligible event depending on configuration).

Column	Description	Notes
Customer account name	Name of the customer
Logistic Order Reference	Reference of the Supplier’s logistic order
Creation date	Creation timestamp of the logistic order	ISO 8601 format
Update date	Last update timestamp of the logistic order
Customer account external ID	External ID of the customer account
Payment method	Credit card, SEPA, Purchase card
Payment network	Visa, Mastercard, SEPA
Event status	Latest eligible payment event status	`PAID`, `REFUSED`
Logistic order status	Operational status of the logistic order
Payment status	Payment status of the logistic order	`PAID`
Total amount HT	Amount excluding taxes
Total amount TTC	Amount including taxes
Total commissions	Commission amount

Filters & Scope

The export respects:

All active filters
Search criteria
Sorting configuration
Store context

If no filters are applied, the export includes all visible transactions within scope.

Eligibility Rules

A transaction is exportable if at least one eligible payment event exists.

Eligible statuses include:

PAID
REFUSED

If filters include transactions without eligible events, they are automatically excluded from the exported file.

Date Range Limitation

To ensure system stability:

Maximum exportable period: 365 days
Evaluated based on createdAt and/or updatedAt
If no date filter is provided, default scope = last 12 months
Applies to both Back Office and API

Requests exceeding this limit are rejected.

Export List View

The Export List view allows users to monitor and manage their export requests.

It acts as a tracking and control screen.

To access the list :

Connect to the Back Office.
Open DJUST Pay.
Navigate to Exports (or “Transaction Exports” depending on naming).
This view lists all exports launched by the current user.

Visibility Rules (Export List)

Operator

Can view only exports they personally launched.
Cannot see exports created by other users.

Supplier

Can view only their own export requests.
Scope is automatically restricted to their own transactions.

Export Lifecycle

The export creation request does not immediately return the file.

Possible statuses:

Status	Description
`PENDING`	Export request created and processing
`READY`	File generated and email sent
`FAILED`	Generation or email sending failed
`EXPIRED`	Download link expired

Downloading an Export

When status = READY:

The user can download the file directly from the Export List view.

The file matches exactly the filters and scope defined at creation time.

When status = EXPIRED:

The download link is no longer valid.

The export must be relaunched.

🚧
Important

A user cannot launch a new export while one is PENDING within the same scope.

The user must wait until the previous export reaches a terminal state (READY, FAILED, EXPIRED).