Receiving application fees

An easy way to split a payment between your platform and your connected merchant accounts is to charge Application fees on the incoming payments on the connected accounts.

This solution is ideal for simpler use cases, where the connected account remains fully liable and in control of the payment, and your platform only deducts a fee.

The connected account in this case will still have their own dashboard, pay their own Mollie payment fees, receive a Mollie invoice, and remain liable for potential chargebacks.

An example use case is a ticketing platform that charges a fee per successful payment to each connected theater. In this case, each theater has an account with Mollie, and they have the ticketing platform’s OAuth app authorized to create payments on their behalf.

The ticketing platform can add an application fee to each payment. When the payment is successful, the fee specified in the application fee is transferred from the theatre’s account to the platforms account.

Mollie will then collect and settle the application fees to the ticketing platform. The ticketing platform itself is responsible for separately invoicing the theaters for the incurred fees, and for handling VAT.

For more advanced use cases, for example if you want to cover the Mollie payment fees yourself, or for example if you want to split a payment with another party, we offer Split payments.

Enabling application fees

In order to enable charging application fees with your app, you must first register to become an app developer. This can be done from the Dashboard. When you signed the developer agreement, application fees will automatically be enabled.

How to create an application fee

One-off application fees can be created on payments or orders. Application fees can also be set on Subscriptions, in which case the application fee will be added to each Payment created for the subscription.

They are created by passing additional parameters to the Create payment, Create order, or the Create subscription endpoint:


Adding an application fee allows you to charge the merchant for the payment and transfer this to your own account. The application fee is deducted from the payment.

Show child parameters

amountamount objectrequired

The amount the app wants to charge, e.g. {"currency":"EUR", "value":"10.00"} if the app would want to charge €10.00. Read more about maximum application fees.

Show child parameters

An ISO 4217 currency code. For application fees, this must always be EUR regardless of the currency of the payment, order or subscription.
A string containing the exact amount you want to charge in the given currency. Make sure to send the right amount of decimals. Non-string values are not accepted.

The description of the application fee. This will appear on settlement reports to the merchant and to you.

The maximum length is 255 characters.

Testing application fees

Application fees work in test mode as well.

You cannot use application fees with the same organization on which you created the oAuth application. In order to test or use application fees, you need another organization.

Maximum application fees

Payments API

The maximum application fee per payment is the amount of the payment - (1.21 × (0.29 + (0.05 × the amount of the
payment))). The minimum is €0.01.

Orders API

The maximum application fee per payment is 10% of the total amount, up to a maximum of €2.00. If a higher maximum is
required for your business, you can request this via Mollie’s customer service or
your account manager at Mollie.


Application fees are both supported on recurring payment and on subscriptions.


Application fees are supported on all payments regardless of currency. However, the application fee itself must always be created in EUR. For example, you can charge a €1.00 application fee on a US$10.00 payment.