Transaction Margin Report

Overview

With Transaction Margin Report, you now have access to transaction-level fee details, designed to support easier financial reconciliation while providing deeper visibility into how fees impact your transaction margin.

By exposing detailed fees data per transaction, the report enables precise margin analysis, improved financial reporting and simplified invoicing workflows within your team.

Transaction Margin Report can be used by our Connect SaaS Partners who have the Resell Pricing configured or are monetizing their payments via Application fees via Payments API. This means that both the revenue-share and buy-rate partners can benefit from using this report.

What you need to do in advance

To ensure a smooth and responsive experience, the report generation works asynchronously: first, you will need to generate the report and then retrieve the data. The full process is described below.

Importantly, to successfully generate Transaction Margin Report that includes all of the data, your access token must include a set of relevant permissions (both when processing payments and when generating the report) - ensure that it is configured with the following scopes: payments.read & organizations.read.
If you are generating a report for a connected application (partner) for which you haven't been granted payments.read & organizations.read - the payments won't show up in the report. You can request (or re-request, for existing clients) relevant permissions using our Authorize flow.
You can find a detailed guide on generating tokens in our Setting up OAuth article.

curl -X GET https://api.mollie.com/oauth2/authorize?client_id=app_j9Pakf56Ajta6Y65AkdTtAv&state=aa&scope=payments.read organizations.read&response_type=code&locale=en-GB

📘
In case one of the permissions is missing, the transactions data for that client won't be included in the report.

Generating Transaction Margin Report

📘
You can retrieve data starting from January 1, 2026 onwards. Same-day reports are not available. Note that Credit Card details might be missing in the past transactions data.

Create Report
Log into your Mollie Dashboard and access the Transaction Margin Report tab in Reports section. Click Create button and select the desired data range and confirm to generate the report.

Retrieve Report Data
Log in to the Dashboard, access the Reports section and navigate to the Transaction Margin tab. There, you will find a complete list of generated reports, including their creation dates and statuses.

The report can have one of the following statuses:

In progress: the report is still being generated. Please wait and refresh the page.
Completed: the report is ready to be downloaded.
Generation failed: the report could not be generated. Reach out to our Support team if your report fails repeatedly.
No data found: the report is empty (for the selected time range).
Outdated: the same report has been re-generated (for the same time range), hence the old one will show as outdated.

Example report

Below is an example of the generated CSV file:

Report column	Description
Transaction type	Type of transaction. At the moment, this defaults to `payment`, but in the future will include new transaction types (e.g. `capture`, `stacked payments`)
id	Unique identifier of the transaction. (e.g. `tr_fraserh2`)
Payment id (Optional)	Unique identifier of the payment (e.g. `tr_fraserh2`). Optional, present only for transactions with type different from `payment`
Paid At	Date and time when the transaction was paid. Returned in `ISO 8601` format. Optional, present only for transactions with type `payment`.
Created at	Date and time when the transaction was created. Returned in `ISO 8601` format. Optional, present only for transactions with type `capture`
Description	Transaction's description
Metadata	Transaction's metadata
Method	Payment method's name
Method Card Audience	Card's target audience, if known. Possible values for regular cards pricing: `consumer` `business` Possible values for split cards pricing: `consumer` `commercial` Optional, present only for online cards and POS payments.
Method Card Label	Card label, if known. Possible values for regular cards pricing: `American Express` `Carta Si` `Carte Bleue` `Dankort` `Diners Club` `Discover` `JCB` `Laser` `Maestro` `Mastercard` `Unionpay` `Visa` Possible values for split cards pricing: `american-express` `carte-bancaire` `maestro` `mastercard` `visa` Optional, present only for online cards and POS payments.
Method Card Funding	Card type. Possible values for regular cards pricing: `debit` `credit` `prepaid` `deferred-debit` Possible values for split cards pricing: `debit` `credit` Optional, present only for online cards and POS payments.
Method Fee Region	Applicable card fee region. Possible values for regular cards pricing: `american-express amex-intra-eea` `carte-bancaire` `intra-eu` `intra-eu-corporate domestic` `maestro` `other` Possible values for split cards pricing: `intra-eea` `inter domestic` Optional, present only for online cards and POS payments.
Method Billing Country	Customer's billing country code in `ISO 3166-1 alpha-2` format. Optional, present only for payment methods `billie`, `in3`, `klarna` and `riverty`
Method Terminal Id	Unique identifier for terminal payments (e.g. `term_CQxQFmC9xBSkFttm4dCAJ`). Optional, present only for POS payments.
Method channel	Source where the payment comes from. Possible values for POS: `pos` `tap-to-pay` Possible values for vouchers: `online` `pos` Optional, present only for POS and voucher payments.
Method submethod	Details about specific submethod (e.g. `pay-later` `pay-now` `financing` ). Optional, present only for Klarna or Alma payments.
Method voucher brand	Name of the voucher brand (e.g `edenred` `monizze` `sodexo`). Optional, present only for voucher payments.
Client Id	Organization token of the client
Client Name	Name of the client
Client Country Code	Country code of the client in `ISO 3166-1 alpha-2` format
Client Profile Id	Identifier referring to the profile this transaction belongs to (e.g. `pfl_D96wnsu869`)
Resell Rate Segment id	Unique identifier for the segment (e.g. `rpst_sdjjEjhke34kPoh`). Optional, present only for transactions with source `resell pricing`.
Resell Rate Segment name	Name of the segment. Optional, present only for transactions with source `resell pricing`.
Resell Rate Source	Source of the resell rate applied. Possible values: `default` `base` `segment`. Optional, present only for transactions with source `resell pricing`.
Application id	OAuth application token of the app authorized by the client a transaction belongs to (e.g. `app_12341829371`)
Currency	Currency of the transaction
Amount	Amount of the transaction
Transaction Fee amount	Transaction fee amount. Optional, present only for transactions linked to OAuth app on managed fee, not transactions linked to OAuth app on revenue share.
Transaction Fee fixed amount	Fixed amount. Optional, present only for transactions linked to OAuth app on managed fee, not transactions linked to OAuth app on revenue share.
Transaction Fee variable amount	Variable amount. Optional, present only for transactions linked to OAuth app on managed fee, not transactions linked to OAuth app on revenue share.
Transaction Fee VAT amount	VAT amount. Optional, present only for transactions linked to OAuth app on managed fee, not transactions linked to OAuth app on revenue share.
Application Fee Type	Application fee type. Possible values: `payment`
Application Fee amount	Total amount of the application fee
Application Fee currency	Currency of the application fee
Application Fee fixed amount	Fixed amount of the application fee
Application Fee variable amount	Variable amount of the application fee
Application Fee source	Source of the application fee. Possible values: `api` `resell_pricing`