> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your app to Mollie

> Connect your app to Mollie, a European payments provider, to take payments with iDEAL, Bancontact, cards, and other methods from your Lovable app.

[Mollie](https://www.mollie.com/) is a European payments provider that supports iDEAL, Bancontact, cards, SEPA, and other local payment methods. The Mollie connector lets your Lovable app create payments in your own Mollie account, send customers to Mollie's hosted checkout, and confirm each payment's status from Mollie. It's designed for apps whose owners already take payments with Mollie.

Mollie is available as an [app + chat connector](https://docs.lovable.dev/integrations/app-connectors.md): one shared connection that works in the chat while you build and in your published apps.

With Mollie, your app can:

* Create payments for the amount of an order and send customers to Mollie's hosted checkout
* Offer the payment methods enabled on your Mollie profile, such as iDEAL, Bancontact, and cards
* Mark an order as paid only after Mollie confirms the payment
* Retry a failed request without charging a customer twice
* List recent payments and their status

The connection covers the rest of the Mollie API too, so you can also ask Lovable to build refunds, subscriptions, or payment links with it.

If you don't have a Mollie account, [Lovable payments](https://docs.lovable.dev/features/payments.md) can set up Stripe or Paddle for you instead. When you ask Lovable to add payments without naming a provider, it recommends those built-in payments.

## Common use cases and example apps

These examples show what you can build with Mollie, each with a prompt to start from.

| Example app | Example prompt | Description |
| :- | :- | :- |
| **Webshop checkout** | *Use Mollie and build a checkout for my shop so customers can pay for their cart with iDEAL.* | **Take payment for a cart in one step.** The app creates a Mollie payment for the cart total, sends the customer to Mollie's checkout, and marks the order paid when Mollie confirms it. |
| **Event ticket sales** | *Use Mollie and build a ticket page where visitors buy tickets for our event and receive a confirmation.* | **Sell tickets with local payment methods.** The app creates a payment for the selected tickets and confirms the order only after Mollie reports the payment as paid. |
| **Donation page** | *Use Mollie and build a donation page where supporters choose an amount and pay with Bancontact or a card.* | **Accept one-off donations.** The app creates a payment for the chosen amount and thanks the donor when the payment succeeds. |
| **Booking deposits** | *Use Mollie and build a booking form for my salon that takes a 20 euro deposit to confirm the appointment.* | **Confirm bookings with a paid deposit.** The app charges the deposit through Mollie and confirms the booking when the payment is paid. |
| **Course purchase** | *Use Mollie and build a page where students buy my online course and get access after paying.* | **Unlock content after payment.** The app creates a payment for the course and grants access when Mollie confirms it. |
| **Payments overview** | *Use Mollie and build an admin page that lists recent payments with their amount and status.* | **See recent payments in one place.** The app reads payments from your Mollie account and shows which are paid, open, or failed. |

## How to connect Mollie

Who can create Mollie connections depends on your plan and workspace settings. App + chat connectors are available by default. On Business and Enterprise plans, [Who can create connections and clients](https://docs.lovable.dev/integrations/admin-controls.md#who-can-create-connections-and-clients) starts at **Admins**. Some Enterprise workspaces start at **No one**, which disables the connector. An admin or owner changes it in **Connectors → Admin settings → App + chat connectors**.

You can create multiple Mollie connections using different API keys, which is useful for separating test and live payments or connecting different Mollie profiles.

When the connection is created, you can [link it to the projects](https://docs.lovable.dev/integrations/app-connectors.md#link-a-connection-to-a-project) where you want to use it. Anyone building in a project can ask Lovable in chat to link their project to it.

### Prerequisites

Before connecting Mollie, make sure you have:

* A Mollie account with at least one payment method enabled on your website profile
* A Mollie API key for that profile
* Permission to **create connections** in your Lovable workspace (see [Who can create connections and clients](https://docs.lovable.dev/integrations/admin-controls.md#who-can-create-connections-and-clients))

> [!NOTE]
>
> Payments made through this connector go to your Mollie account. Mollie charges its transaction fees directly, and billing is handled by Mollie, not Lovable.

### Step 1: Get a Mollie API key

A Mollie API key lets your Lovable app create and read payments for one Mollie website profile. Each profile has a test key, which starts with `test_`, and a live key, which starts with `live_`. Payments made with a test key are simulated, so use the test key while you build and switch to the live key when you're ready to take real payments.

To get a Mollie API key:

**1. Open your Mollie Dashboard**

Sign in to the [Mollie Dashboard](https://my.mollie.com/dashboard).

**2. Open API keys**

Go to [**Developers → API keys**](https://my.mollie.com/dashboard/developers/api-keys). If your account has more than one website profile, select the profile you want to take payments with.

**3. Copy the key**

Copy the test key or the live key and store it securely. Live payments work only after Mollie has activated your account.

> [!WARNING]
>
> Your API key functions like a password. Keep it secure and never share it publicly. You'll need it in the next step.

See Mollie documentation for more: [Authentication](https://docs.mollie.com/reference/authentication).

### Step 2: Connect Mollie to Lovable

Use your test key for the first connection, so you can try payments without moving real money.

**1. Open Mollie in Connectors**

Open [**Connectors**](https://lovable.dev/dashboard?connectors) and select **Mollie**. For the other places to open the catalog from, see [Where to find connectors](https://docs.lovable.dev/integrations/introduction#where-to-find-connectors).

**2. Add a connection**

Click **Connect** on the connector page. The form is split into collapsible sections, **Details**, **Configure connection**, and **Sharing**.

**3. Name the connection**

Under **Details**, Lovable fills in a name for the connection, which you can change. The name is only used inside Lovable to identify the connection, for example `Mollie Test` or `Mollie Live`.

**4. Configure the connection**

Under **Configure connection**, enter:

1. **API key**: paste your Mollie API key. It must start with `test_` or `live_`. **Get value** next to the field opens the API keys page in the Mollie Dashboard.

**5. Choose who can use this connection**

Under **Sharing**, the connection is private to you by default and shows a **Private** label. To share it, click **Share with others**. Then add workspace members by email, or click **Invite entire workspace** to make the connection available to everyone in your Lovable workspace.

See [Who can use connections and clients](https://docs.lovable.dev/integrations/admin-controls.md#who-can-use-connections-and-clients) for more information.

**6. Connect**

Click **Connect** at the bottom of the form. Lovable verifies the key against the Mollie API before saving the connection.

When connected, anyone building in a project can ask Lovable in chat to link their project to Mollie (based on configured connection-level access). Your Lovable apps can then create payments and confirm their status through Mollie.

## How payments are confirmed

Mollie tells your app about a payment's progress by calling a webhook, a public address in your app. Mollie can't reach the editor's preview, so Lovable sets up the webhook on a public address of your app. The webhook call only carries the payment ID, so Lovable builds your app to look up the payment in Mollie and mark the order as paid only when Mollie reports it as paid. Your app does not treat the customer's return to your site as proof of payment.

Payments made with a `test_` key open Mollie's test checkout, where you choose the outcome (paid, failed, canceled, or expired) to try each path in your app.

## Limitations

The Mollie connector cannot:

* Connect with an organization access token (`access_`) or through Mollie Connect. Each connection uses one profile API key.
* Support marketplace or platform payments where each seller connects their own Mollie account. Each connection represents a single Mollie profile shared across all projects linked to it.

## Troubleshooting

Use these checks when connecting fails or a Mollie request returns an unexpected status.

> [accordion] No suitable payment methods found
>
> Mollie returns this error when no payment method is enabled on the Mollie profile for that amount and currency. Enable a method such as iDEAL or cards for that profile in the Mollie Dashboard, then try again. Test and live mode have separate payment method settings.

## Manage your Mollie connection

Connections are managed from [**Connectors**](https://lovable.dev/dashboard?connectors): select **Mollie**, then open the connection.

* **Unlink projects** to remove Mollie access from specific projects while keeping the connection available for others. See [Unlink projects from a connection](https://docs.lovable.dev/integrations/app-connectors.md#unlink-projects-from-a-connection) for the steps.
* **Delete the connection** to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use Mollie stop working until a new connection is added. See [Delete a connection](https://docs.lovable.dev/integrations/app-connectors.md#delete-a-connection) for the steps and who can delete.