---
updatedAt: 2026-08-25T13:46:35.000Z
agentTools:
projectIndex: https://docs.mollie.com/llms.txt
---
# Connect for Platforms: Processing payments
## Accepting payments
In its simplest form, setting up a payment requires only three steps: **setting up the payment with our Payments API**, **sending the customer to our hosted checkout**, and **monitoring the status** to verify that the payment is complete.
To set up and test your payment processing flow, refer to the [Accepting Payments overview](https://docs.mollie.com/docs/accepting-payments) for a step-by-step guide on implementing the [Payments API](https://docs.mollie.com/reference/payments-api) and testing your integration with the first sandbox transaction.
As we are just **testing** the flow and not processing actual transactions live yet, make sure to [enable test mode](https://docs.mollie.com/reference/create-payment#:~:text=testmode,Defaults%20to%20false) by setting the `testmode` param to `true`.
## Monetizing payments with Application fees
### Receiving Application fees
A simple way to monetize transactions is by charging an **Application fee** on any payments created by your platform on behalf of a connected customer. This means you can charge your customers for every transaction processed through your platform.
In this setup, the connected account (i.e. your customer) pays their own Mollie payment fees, receives a Mollie *invoice* for these fees, and remains liable for potential refunds and chargebacks.
Some advantages of using Application fees are:
* Allows platforms to collect a fee for processing payments through their platform.
* Gives platforms the flexibility to charge as much or as little as they like, giving them complete autonomy on how they monetize payments.
> 📘 Example
>
> A ticketing platform wants to charge a fee per successful payment to each connected theatre (customer). In this case, each theater has an account with Mollie, and they have the ticketing platform’s OAuth app authorized to create payments on connected theaters' behalf.
>
> The ticketing platform can add *Application fee* to each payment, so that when the transaction is successful, this fee is automatically transferred from the theater’s account to the platform’s account.
>
> Note that the **ticketing platform itself** is responsible for invoicing the theaters for the incurred fees, and for handling VAT.
### Enabling application fees
In order to be able to charge Application fees with your app, you must first register to become an *app developer*. This can be done from the [Web app](https://www.mollie.com/dashboard/developers/applications) > Developers. When you sign the developer agreement, Application fees will automatically be available.
### How to create Application fees
One-off Application fees can be created on payments or orders and can also be set on *[Subscriptions](https://docs.mollie.com/reference/create-subscription)*, in which case the Application fee will be deducted from each payment created for that subscription.
Application fees are created by passing additional parameters to the [Create payment](/reference/create-payment), [Create order](/reference/create-order), or the [Create subscription](/reference/create-subscription) endpoint:
#### applicationFee object
Adding an Application fee allows you to charge the customer for the payment and transfer this to your own account. The Application fee is deducted from the payment.
#### `amount` **object** *required*
> 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](/docs/application-fees#maximum-application-fees).
* #### `currency` **string** *required*
> An [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217) currency code. The currency of the application fee depends on the currencies your customer has available.
* #### `value` **string** *required*
> 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.
#### `description` **string** *required*
> The description of the Application fee. This will appear on settlement reports to the customer and to you.\
> The maximum length is 255 characters.
### Testing Application fees
You can submit the `applicationFee` parameter in `test` mode to test your payments flow.
The Application fee will be visible in the payment details (in the transaction owner's dashboard). However, it is not added to the balance if the payment was created in *test mode* , so we advise to test your payments with Application fees in a *live* environment if you are using the Settlements or Balances APIs.
> 📘
>
> You cannot charge Application fees to the same organization on which you created the OAuth application. In order to test or use Application fees, you need to create another organization.
You can find all received Application Fees in the **Balance** tab of your Mollie Web app.
### Example API Call
```json
{
"amount":
{
"currency":"EUR",
"value":"10.00"
},
"description":"I can accept payments now",
"redirectUrl":"https://myVeryOwnWebshop.com",
"profileId":"pfl_zcfJRjkf6P",
"applicationFee":
{
"amount":
{
"currency":"EUR",
"value":"1.50"
},
"description":"Platform fee"
},
"testmode":true
}
```
In this example, the consumer pays `10.00 EUR`. Once successful, Mollie will move `1.50 EUR` to the partner’s balance and will then settle the amount minus transaction fee to the customer’s balance.
> 📘 Example
>
> If processed with [iDeal](https://www.mollie.com/pricing#psp-block), there will be an incoming transaction of `10.00 EUR` with `1.85 EUR` deduction (`1.50 EUR` Application fee + `0.29\*1.21` iDeal list price + `VAT`) resulting in `8.21 EUR` net.
### Maximum Application fees
#### Payments API
Since Mollie usually also charges a fee on every payment, there is a limit to the **maximum** Application fee amount.
The Mollie fee charged will depend on which method the consumer selects. However, to keep things simple, we reserve `€0,35` + `6%` of the payment amount for us to be able to charge the *[Mollie fee](https://www.mollie.com/pricing)*.
This means the **maximum** can be calculated as follows:\
Max Application fee = total payment amount - `0.35` + (`0.06` × total payment amount)
> 📘 Example
>
> The connected account of the ticket platforms has a payment of `€10.-`:
>
> Max Application fee = `€10` - (`€0.35` + `0.06×€10`) = `€10` - `€0.95` = `€9.05`
The **minimum** amount 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, submit a request to Mollie’s [customer service](https://www.mollie.com/contact) or your account manager.
### Multicurrency support
Application fees are supported on all payments regardless of the [currency](/docs/multicurrency). However, the currency of the application fee is dependent on the currency balances your customer has available. You can check which balances an organization has with the [Balances API](https://docs.mollie.com/reference/list-balances).
The currency you need to use is determined according to the following rules:
* **If** your customer has a balance in the currency of the payment, then the application fee **must** be charged in that currency: e.g. `US$1.00` fee on a `US$10.00` payment.
* **Otherwise**, the application fee **must** be charged in the currency of your customer's **primary balance**. e.g. `€1.00` application fee on a `US$10.00` payment if your customer's primary balance is in *euros*.
You can use the [Balances API](https://docs.mollie.com/reference/list-balances) to check which currency balances your customer has, including their primary balance.
## Refunds and chargebacks
### Refunding a payment with Application fees
When using [Application fees](/docs/application-fees), refunds will be processed **on the customer’s account** and Application fees are **non-refundable**.
The **full transaction amount** will be taken from the customer’s balance, including the **refund fee**.
If the customer's services are covered by VAT regulations, they should add it to the application fee themselves. Mollie will apply VAT on the transaction fee in accordance to the settings of the customer.\
(*It is also**partner's responsibility** to decide whether VAT should be applied for a given transaction, and if applicable send the VAT-inclusive amount to Mollie as the amount for the application fee and invoice their consumers accordingly.*)
As a platform, you can create refunds on behalf of the connected customers by using the [Refunds API](/reference/refunds-api) with the connected account’s permission.
For more fine-grained control over the refund and chargeback flows, consider using [Split payments](https://docs.mollie.com/docs/connect-marketplaces-processing-payments#/monetizing-payments-with-split-payments) instead.