Transaction Margin Report
Overview
With Transaction Margin Report, you 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 with 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 successfully generate Transaction Margin Report that includes all of the data, your access token must include the following permissions: payments.read & organizations.read.
Read more about permissions and scopes in Permissions.
If you are generating a report for a connected organization (partner) for which you haven't been granted both
payments.read&organizations.read- the payments won't show up in the report.
Generating Transaction Margin Report
You can retrieve data starting from January 1, 2026 onwards. Same-day reports are not available.
-
Create Report
Log into your Mollie Web App and access the Reports section > Transaction Margin Report tab.
Click Create button, select the desired data range and confirm to generate the report. -
Retrieve report data
Log in to the Web App, 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 allow a few minutes and then refresh the page.
- Completed: the report is ready to be downloaded.
- Generation failed: the report could not be generated.
- 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); the old one will show as outdated.
Example report
Below is an example of the generated CSV file:
| Title | Description |
|---|---|
| Transaction type | Type of transaction. Defaults to payment. |
| id | Unique identifier of the transaction (e.g. tr_fraserh2). |
| Payment id (Optional) | Unique identifier of the payment*. *Present only for transactions with type different from payment |
| Paid At (Optional) | Date and time when the transaction was paid (ISO 8601)*. *Present only for transactions with type payment |
| Created at (Optional) | Date and time when the transaction was created (ISO 8601)*. *Present only for transactions with type capture |
| Description | Transaction's description. |
| Metadata | Transaction's metadata. |
| Method | Payment method's name. |
| Method Card Audience (Optional) | Card's target audience, if known. Possible values: consumer business commercial*. *Present only for online cards and POS payments |
| Method Card Label (Optional) | Card label, if known (e.g. Mastercard, Visa, American Express).Present only for online cards and POS payments |
| Method Card Funding (Optional) | Card type. Possible values: debit credit prepaid deferred-debit. Present only for online cards and POS payments. |
| Method Fee Region (Optional) | Applicable card fee region*. *Present only for online cards and POS payments. |
| Method Billing Country (Optional) | Customer's billing country code (ISO 3166-1 alpha-2) . Present only for billie, in3, klarna and riverty. |
| Method Terminal Id (Optional) | Unique identifier for terminal payments . Present only for POS payments. |
| Method channel (Optional) | Source where the payment comes from . Present only for POS and voucher payments. |
| Method submethod (Optional) | Details about specific submethod . Present only for Klarna or Alma payments. |
| Method voucher brand (Optional) | Name of the voucher brand . 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 (ISO 3166-1 alpha-2). |
| Client Profile Id | Identifier referring to the profile this transaction belongs to. |
| Resell Rate Segment id (Optional) | Unique identifier for the segment*. *Present only for transactions with source resell pricing. |
| Resell Rate Segment name (Optional) | Name of the segment*. *Present only for transactions with source resell pricing. |
| Resell Rate Source (Optional) | Source of the resell rate applied. Possible values: default base segment*. *Present only for transactions with source resell pricing. |
| Application id | OAuth application token of the app authorized by the client. |
| Currency | Currency of the transaction. |
| Amount | Amount of the transaction. |
| Transaction Fee amount (Optional) | Transaction fee amount. *Present only for transactions on managed fee. |
| Transaction Fee fixed amount (Optional) | Fixed amount. *Present only for transactions on managed fee. |
| Transaction Fee variable amount (Optional) | Variable amount. *Present only for transactions on managed fee. |
| Transaction Fee VAT amount (Optional) | VAT amount. *Present only for transactions on managed fee. |
| 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 |
Updated 5 days ago