> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/mollie.md).

# Mollie

Configure Mollie card, wallet, bank debit, bank redirect, and pay later payments with Hyperswitch.

<div align="left"><img src="https://hyperswitch.io/icons/homePageIcons/logos/mollieLogo.svg" alt=""></div>

European bank redirects, SEPA Direct Debit, Klarna, PayPal, Apple Pay, and cards come together in Mollie's payment gateway route. Automatic, sequential automatic, and manual capture apply throughout, while mandates are supported for cards. Mandates are not supported for the bank debit, bank redirect, pay later, or wallet methods.

### Status and capabilities

**Integration status:** sandbox

**Category:** payment gateway

**Webhook flows:** None declared in code

| Payment method | Type              | Mandates      | Refunds   | Capture methods                         | 3DS                 | Card networks                                                                                       | Countries | Currencies |
| -------------- | ----------------- | ------------- | --------- | --------------------------------------- | ------------------- | --------------------------------------------------------------------------------------------------- | --------- | ---------- |
| bank debit     | SEPA Direct Debit | not supported | supported | automatic, sequential automatic, manual | not applicable      | -                                                                                                   | -         | -          |
| bank redirect  | Bancontact Card   | not supported | supported | automatic, sequential automatic, manual | not applicable      | -                                                                                                   | -         | -          |
| bank redirect  | EPS               | not supported | supported | automatic, sequential automatic, manual | not applicable      | -                                                                                                   | AUT       | EUR        |
| bank redirect  | Giropay           | not supported | supported | automatic, sequential automatic, manual | not applicable      | -                                                                                                   | -         | -          |
| bank redirect  | iDEAL             | not supported | supported | automatic, sequential automatic, manual | not applicable      | -                                                                                                   | NLD       | EUR        |
| bank redirect  | Przelewy24        | not supported | supported | automatic, sequential automatic, manual | not applicable      | -                                                                                                   | POL       | EUR, PLN   |
| bank redirect  | Sofort            | not supported | supported | automatic, sequential automatic, manual | not applicable      | -                                                                                                   | -         | -          |
| card           | Credit Card       | supported     | supported | automatic, sequential automatic, manual | supported, optional | American Express, Cartes Bancaires, Diners Club, Discover, Interac, JCB, Mastercard, UnionPay, Visa | -         | -          |
| card           | Debit Card        | supported     | supported | automatic, sequential automatic, manual | supported, optional | American Express, Cartes Bancaires, Diners Club, Discover, Interac, JCB, Mastercard, UnionPay, Visa | -         | -          |
| pay later      | Klarna            | not supported | supported | automatic, sequential automatic, manual | not applicable      | -                                                                                                   | 19        | 8          |
| wallet         | Apple Pay         | not supported | supported | automatic, sequential automatic, manual | not applicable      | -                                                                                                   | -         | -          |
| wallet         | PayPal            | not supported | supported | automatic, sequential automatic, manual | not applicable      | -                                                                                                   | -         | -          |

### Activate Mollie with Hyperswitch

#### Before you start

1. Register with Mollie. Sign up at [mollie.com](https://www.mollie.com/).
2. Sign into the [Hyperswitch control center](https://app.hyperswitch.io/register) or create your Hyperswitch account.
3. Copy your API key from the Mollie dashboard; if you use card tokenization, also copy the profile token.
4. Enable the same payment methods in Mollie and in your Hyperswitch connector configuration.

To connect Mollie to your Hyperswitch account, follow [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md), then return here for what Mollie supports.

### Connector-Specific Notes

Card tokenization requires the profile token in addition to the API key. Hyperswitch places the profile token in the tokenization request body. See [`MollieCardTokenRequest::try_from()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/mollie/transformers.rs#L623-L665).

### Authentication

Mollie accepts two credential paths. Provide an `<API key>` for the `HeaderKey` path. For card tokenization, provide an `<API key>` and `<profile token>` through the `BodyKey` path, where `key1` maps to the profile token. Both paths send `Authorization: Bearer <API key>`; the profile token is carried in the tokenization body rather than the authorization header. See [`MollieAuthType::try_from()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/mollie/transformers.rs#L828-L848), [`get_auth_header()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/mollie.rs#L108-L119), and [`MollieCardTokenRequest::try_from()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/mollie/transformers.rs#L623-L665).

### Webhooks

The feature matrix declares no webhook flows, but the connector processes a payment resource callback. The callback body has an `id` field and no event-name field, so there is no separate wire event value to configure. Source verification currently returns `false`, so the callback is not accepted as verified by this implementation. See [`MollieWebhookBody`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/mollie/transformers.rs#L1073-L1076) and [`verify_webhook_source()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/mollie.rs#L837-L849).

The connector maps 1 callback shape:

| Wire field | Effect                       |
| ---------- | ---------------------------- |
| `id`       | Payment is marked processing |

The mapping is defined by [`get_webhook_event_type()`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/mollie.rs#L850-L867).

### Source reference

The connector implementation is [`mollie.rs`](https://github.com/juspay/hyperswitch/blob/a17a23c4c4c907d2314043a32a9f505f7f2bd4f9/crates/hyperswitch_connectors/src/connectors/mollie.rs).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/mollie.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.