Mollie

What Is Mollie?

Mollie is a European payments provider that lets businesses accept online payments through a single integration, with a strong focus on the local payment methods that dominate European markets. Founded in the Netherlands in 2004, Mollie has grown into one of the most popular payment service providers among small and mid-size businesses across Europe, known for transparent pricing, a developer-friendly API, and broad support for methods such as iDEAL, Bancontact, SEPA, credit cards, and digital wallets.

A defining characteristic of Mollie is its breadth of European payment methods behind one account and one integration. While card acceptance is global, European shoppers frequently prefer local options, iDEAL in the Netherlands, Bancontact in Belgium, and various bank-transfer and direct-debit schemes, and Mollie's appeal is that a merchant can offer all of them without negotiating separate contracts for each. This focus on local methods, combined with straightforward onboarding, is why Mollie is so widely adopted by European SMBs and the platforms that serve them.

Mollie is a payment service provider: it handles the gateway and the processing relationship, so merchants do not need to source a separate merchant account. It exposes a clean API and hosted checkout, and it integrates deeply with popular ecommerce platforms and plugins, which is part of why it appears so often on European online stores. The merchant controls how payment is initiated; Mollie supplies the secure processing, the hosted payment pages or components, and the payouts.

Mollie is not a website builder, a hosted store, or a browser extension. On the merchant side it is an API, hosted checkout, and a dashboard; on the shopper side it is the payment screen where they choose a method and complete payment, frequently a Mollie-hosted page or component. Because Mollie hosts much of the payment experience and serves recognizable scripts and domains, it is relatively straightforward to detect from the outside.

It helps to understand who Mollie is for. The platform deliberately targets European small and mid-size businesses, and the developers and agencies who build for them, that want simple, transparent pricing and the local payment methods their customers expect. A merchant who needs to accept iDEAL and Bancontact alongside cards, with minimal contractual overhead, is the natural Mollie customer. That orientation explains many of Mollie's product decisions, from its no-code plugin integrations to its hosted checkout that offloads payment-page complexity and PCI burden from the merchant.

How Mollie Works

At a technical level, Mollie centers on the Payments API and a hosted checkout experience. The common flow is straightforward: the merchant's server creates a payment via Mollie's API, specifying the amount, currency, description, and a redirect URL. Mollie returns a checkout URL, and the merchant redirects the shopper to a Mollie-hosted payment page where they choose a payment method, iDEAL, Bancontact, card, and so on, and complete the payment. Mollie then redirects the shopper back to the merchant and notifies the merchant's server of the result via a webhook.

This hosted-redirect model is central to Mollie's simplicity. Because the actual payment details are entered on Mollie-hosted pages, the merchant keeps sensitive data out of their own systems and minimizes PCI scope. Mollie also offers Components, embeddable, Mollie-served fields for card details that let merchants build a more integrated card form while still keeping the sensitive inputs within Mollie-controlled elements, similar in spirit to hosted-field approaches used by other providers.

Mollie handles the processing relationship and payouts. Funds collected across the various payment methods are settled to the merchant's bank account on a payout schedule, and the Mollie dashboard provides reporting, refunds, and management of payments and methods. Because Mollie is a payment service provider rather than only a gateway, merchants get processing and settlement through a single onboarding rather than sourcing a separate acquiring relationship.

A useful way to picture the flow is to follow a purchase end to end. A shopper at a European online store clicks "pay," and the store's server calls Mollie to create a payment and receives a checkout URL. The shopper is redirected to Mollie's hosted page, selects iDEAL, and is taken to their bank's authentication to approve the transfer (or, for a card payment, enters card details on Mollie's secure page or components). Mollie processes the payment, redirects the shopper back to the store's confirmation page, and sends a webhook to the store's server so it can mark the order paid. Later, Mollie settles the funds to the merchant's bank account. From the shopper's perspective it is a familiar local payment experience; behind the scenes Mollie coordinates the method, the processing, and the payout.

Mollie also leans heavily on platform integrations. It provides official and community plugins for major ecommerce platforms and a well-documented API for custom builds, so many merchants enable Mollie through a plugin rather than writing integration code. Recurring payments, refunds, multicurrency support, and a range of local and international methods round out the platform, positioning Mollie as a one-stop payments provider for European-focused commerce.

How to Tell if a Website Uses Mollie

Mollie leaves several recognizable fingerprints, most visible at or around the checkout step. StackOptic inspects these from the server side, and you can confirm them manually.

Redirect to a Mollie-hosted checkout. The clearest signal is the payment step redirecting the shopper to a Mollie domain such as mollie.com (checkout pages commonly live under a Mollie-hosted path). Watching the checkout redirect to a mollie.com URL is a strong, specific indicator.

Mollie script and asset domains. Sites using Mollie Components or its JavaScript load assets from Mollie's hosts (for example js.mollie.com). Requests to Mollie domains in the Network tab are a dependable tell.

JavaScript globals and Components. Mollie Components expose a Mollie object on the page (the components client is created from it). Finding the Mollie global in the console, or Mollie-served iframes around card inputs, confirms the integration.

Local payment methods. A checkout offering iDEAL, Bancontact, and similar European methods is consistent with Mollie (though other European PSPs also support these), so treat the method list as supporting evidence alongside the domain and script signals.

Webhook and API references. Server-side, payment creation calls Mollie's API hosts; while not visible to a casual visitor, these reinforce detection in a deeper analysis.

Method	What to do	What Mollie reveals
View Source	"View Page Source" on the checkout page	References to Mollie scripts such as js.mollie.com
Browser DevTools (Network)	Open the Network tab and start a payment	A redirect to mollie.com and requests to Mollie domains
Browser DevTools (Console)	Type window.Mollie	The exposed Mollie Components global object
Browser DevTools (Elements)	Inspect the card-input fields, if Components are used	Mollie-served iframes around the inputs
Wappalyzer	Run the extension on the checkout page	Identifies "Mollie" under payment processors

A practical approach is to begin a purchase on the site, open DevTools, and watch the Network tab for a redirect to mollie.com as you reach the payment step. For the broader methodology, see our guide on how to find out what payment processor a website uses. Because Mollie often appears via an ecommerce plugin, the techniques in how to find out what ecommerce platform a website uses help you reach checkout and read the surrounding stack.

It is worth noting how these signals behave on production sites. With the hosted-redirect model, the most obvious signal, the redirect to mollie.com, appears only once the shopper commits to paying, so you generally need to reach the actual payment step to see it. Sites that use Mollie Components instead keep the shopper on their own page but load Mollie's scripts and render Mollie-served iframes for card inputs, so the js.mollie.com reference and the Mollie global become the key tells. The presence of iDEAL or Bancontact alone is suggestive but not conclusive, because other European providers support those methods too; the dependable approach is to combine the method list with a Mollie domain request or the Mollie script object. Server-side analysis helps by fetching the unmodified response and surfacing Mollie's script references and, where applicable, the redirect target without the noise a browser introduces.

Key Features

• Broad European payment methods. iDEAL, Bancontact, SEPA direct debit and bank transfer, cards, and digital wallets behind one account.
• Hosted checkout and Components. A Mollie-hosted payment page for minimal PCI scope, plus embeddable components for a more integrated card form.
• Single onboarding as a PSP. Processing and settlement through one provider, without sourcing a separate merchant account.
• Transparent pricing. Per-transaction pricing that is straightforward to understand, a frequent reason SMBs choose Mollie.
• Strong platform integrations. Official and community plugins for major ecommerce platforms plus a clean API for custom builds.
• Payments management. Dashboard reporting, refunds, recurring payments, and multicurrency support.
• Webhook-driven flow. Reliable server notifications to keep order status in sync after payment.

Pros and Cons

Pros

• Excellent coverage of European local payment methods through a single integration.
• Simple, transparent pricing that appeals to small and mid-size businesses.
• Easy to enable via plugins for popular ecommerce platforms, often with minimal code.
• Hosted checkout keeps merchants out of most PCI scope.

Cons

• Strongest fit is European commerce; merchants focused elsewhere may prefer a more globally oriented provider.
• The hosted-redirect flow takes shoppers off-site unless Components are used, which some merchants dislike.
• Feature depth for very large or highly customized enterprises may be narrower than some global gateways.
• Some advanced flows still require API integration work beyond a basic plugin.

Mollie vs Alternatives

Mollie competes with other European-focused providers and with global gateways. The table below clarifies where it fits.

Provider	Focus	Standout strength	Best for
Mollie	European payments	Local methods and simple pricing	European SMBs and the platforms serving them
Stripe	Global developer-first payments	Breadth of APIs and reach	Developers and businesses wanting global scale
Adyen	Enterprise unified commerce	Global acquiring and omnichannel	Large international merchants
PayPal	Global wallet and processor	Buyer trust and fast setup	Broad acceptance and PayPal-centric flows
Braintree	Full-stack gateway (PayPal-owned)	Custom checkouts with PayPal/Venmo	Mid-market custom checkout builders

If a site turns out to use a different provider, the same techniques identify it; see our payment processor detection guide, and compare Mollie's European, SMB-oriented approach with a full-stack gateway like Braintree aimed at custom checkouts.

Use Cases

Mollie is the natural choice for European online businesses that need local payment methods their customers expect. Dutch and Belgian stores rely on it to accept iDEAL and Bancontact alongside cards, and merchants across Europe use it for SEPA-based payments and regional wallets, all from one account. Because it integrates cleanly with major ecommerce platforms, it is especially popular with SMBs running on off-the-shelf stores.

It also fits subscription and membership businesses needing recurring payments in European markets, agencies and developers building client stores who want a quick, well-documented integration, and merchants who prioritize transparent pricing. For competitive research, detecting Mollie on a site strongly suggests a European-focused business, useful context when profiling regional commerce.

Consider a few concrete scenarios. A Dutch ecommerce store on a popular platform might enable Mollie through a plugin so shoppers can pay with iDEAL in a few clicks, dramatically improving conversion with local buyers. A pan-European subscription service might use Mollie for recurring SEPA direct-debit payments across several countries from a single account. A web agency building stores for European clients might standardize on Mollie because its plugins and transparent pricing make onboarding fast and predictable. In each case the common thread is a business serving European customers who expect local payment options and a provider that supplies them without contractual friction.

From a sales-intelligence perspective, spotting Mollie on a domain is a strong geographic and segment signal. It typically indicates a European business, often an SMB, that has prioritized local payment acceptance, which is valuable context for vendors targeting European commerce. Knowing a prospect's payment provider is a core technographic data point, as explained in what is technographics: using tech stack data to qualify leads. Surfacing that signal automatically across many domains, rather than inspecting each checkout by hand, is exactly where automated technology detection earns its keep.

Frequently Asked Questions

Is Mollie a payment gateway or a payment service provider?

Mollie is a payment service provider, which means it handles both the gateway and the processing relationship, so merchants accept payments and receive payouts through a single onboarding without sourcing a separate merchant account. It offers a hosted checkout and embeddable components, supports a broad range of European and international payment methods, and settles funds to the merchant's bank account, all under one provider.

How can I tell if a website uses Mollie?

Begin a purchase and open your browser's DevTools. Watch the Network tab for a redirect to a mollie.com checkout page or for requests to Mollie domains such as js.mollie.com, type window.Mollie in the Console to check for the Components global, and inspect any card fields for Mollie-served iframes. A checkout offering iDEAL and Bancontact is supporting evidence, and tools like Wappalyzer list Mollie under payment processors. Reaching the actual payment step usually makes the signals clearest.

Why does Mollie redirect me to another page to pay?

That is Mollie's hosted-checkout model. The merchant's server creates a payment and receives a Mollie checkout URL, then redirects the shopper to a Mollie-hosted page to choose a method and complete payment securely. Because the sensitive payment details are entered on Mollie's pages rather than the merchant's, this keeps the merchant out of most PCI scope. Merchants who prefer to keep shoppers on-site can instead use Mollie Components, which embed Mollie-served fields directly in their own checkout.

Does Mollie only work in Europe?

Mollie is strongly focused on European markets and is best known for local methods like iDEAL and Bancontact, but it also supports cards and other international methods, so it is not strictly limited to Europe. That said, its core strength and customer base are European commerce, and businesses focused on other regions may prefer a more globally oriented provider. Detecting Mollie on a site is therefore a fairly reliable indicator of a European focus.

Does detecting iDEAL or Bancontact prove a site uses Mollie?

Not by itself. iDEAL, Bancontact, and similar local methods are offered by several European payment service providers, so their presence is suggestive but not conclusive. To confirm Mollie specifically, combine the method list with a Mollie-specific signal, a redirect to mollie.com, a request to js.mollie.com, or the Mollie Components global in the console. Relying on multiple signals together is the dependable way to distinguish Mollie from other providers that support the same methods.

Want to detect Mollie and the full payment and technology stack behind any site instantly? Run any URL through StackOptic at https://stackoptic.com.