How to Tell If a Website Uses Mollie

Mollie is a popular European payment service provider (PSP), founded in the Netherlands and known for an easy integration and broad support for European local payment methods. Because it loads a distinctive Components script and processes on its own domain, detecting it is straightforward: look for js.mollie.com/v1/mollie.js and the global Mollie constructor, plus mollie.com checkout/API traffic. This guide covers every reliable signal, the European-methods model behind them, the look-alikes to rule out, and what Mollie usage tells you about the business.

What is Mollie?

Mollie is a Dutch payment service provider that lets businesses accept payments across Europe through a single, developer-friendly integration. Its defining strength is breadth of European local payment methods: cards, plus iDEAL (the dominant Dutch method), Bancontact (Belgium), SEPA Direct Debit, SOFORT, Giropay, Przelewy24 and more — alongside PayPal, Apple Pay and BNPL options. That local-methods coverage makes it a favourite of European ecommerce and SaaS businesses, especially in the Netherlands and Belgium, that need to serve customers' preferred local ways to pay. It competes with Stripe, Adyen and regional PSPs in the European market.

For detection, the key context is that Mollie is a strong European signal. Because it is EU-focused and centres on European local methods, finding it almost always indicates a European-market business — frequently Dutch or Belgian. Finding it tells you the business serves European customers and supports their local payment preferences. Because Mollie loads its Components from js.mollie.com and processes on mollie.com, it is easy to confirm. Its presence marks a European online business and its market focus, much as Razorpay marks an Indian one.

How Mollie loads and processes payments

Mollie offers two main integration styles. The hosted checkout redirects the customer to a Mollie-hosted payment page on mollie.com (historically mollie.nl) to choose and complete a method. The embedded Mollie Components solution loads js.mollie.com/v1/mollie.js, which exposes the global Mollie constructor, initialised with the merchant's profile ID: const mollie = Mollie('pfl_...', { locale, testmode });. Components renders card fields inside iframes from mollie.com for PCI compliance, and the payment is processed via Mollie's API on mollie.com.

The available local methods (iDEAL, Bancontact, SEPA) presented at checkout are characteristic of a European PSP, and the profile ID identifies the merchant. So a Mollie site shows the js.mollie.com Components script (and Mollie global) and/or a mollie.com hosted-checkout redirect, plus the European local methods. Knowing these — the js.mollie.com/v1/mollie.js script, the Mollie constructor, the mollie.com checkout/API, and the European local methods — makes detection quick.

How to tell if a website uses Mollie

Confirm at least one strong signal.

1. Check the Network tab. On a checkout, filter for mollie. The Components script from js.mollie.com/v1/mollie.js and traffic to mollie.com confirm Mollie.

2. Use the console. Type Mollie and press Enter. A returned constructor (used for Mollie Components) confirms it.

3. Inspect the card fields. Card inputs rendered inside mollie.com iframes (Mollie Components) are characteristic.

4. Watch the checkout. A redirect to a mollie.com hosted payment page, or local methods like iDEAL/Bancontact presented, indicates Mollie.

5. Note the methods. European local methods (iDEAL, Bancontact, SEPA) handled by Mollie are a strong corroborating signal.

What the Mollie signals look like

<script src="https://js.mollie.com/v1/mollie.js"></script>
const mollie = Mollie("pfl_aBc123", { locale: "nl_NL", testmode: false });
<iframe src="https://js.mollie.com/.../component/..."></iframe>   <!-- Mollie Components card field -->
// Hosted checkout redirect to https://www.mollie.com/checkout/...

The js.mollie.com/v1/mollie.js script, the Mollie constructor, and mollie.com checkout/API traffic are conclusive.

Mollie versus other PSPs — avoiding false positives

Match the domain and methods to keep PSPs distinct. Mollie uses js.mollie.com/mollie.com and the Mollie constructor; Stripe uses js.stripe.com; Adyen uses checkoutshopper-*.adyen.com; Klarna and regional providers have their own hosts. The mollie.com domains and the Mollie Components constructor are unique to Mollie. Its European local-method focus distinguishes it — heavy iDEAL/Bancontact support points to Mollie (or Adyen). Finding Mollie rather than Stripe is itself a European-market signal. A business may use Mollie for Europe and another processor elsewhere, so check for multiple PSPs on cross-border sites, and note that wallets/BNPL presented within Mollie are part of its flow, not separate providers.

How reliable is each Mollie signal?

The js.mollie.com/v1/mollie.js script and the Mollie constructor are definitive, as is mollie.com checkout/API traffic. Mollie Components iframes from mollie.com are equally strong. The European local methods corroborate. The weakest situation is a homepage that loads Mollie only at checkout, so test the payment step; for hosted checkout, the mollie.com redirect appears at payment. As a rule, the js.mollie.com script or a mollie.com checkout settles it.

What Mollie usage reveals about a business

Finding Mollie signals a European online business accepting local payment methods through a developer-friendly PSP. Its EU focus and local-methods support mean its presence almost certainly indicates a European-market business — frequently Dutch or Belgian, given Mollie's strongholds and iDEAL/Bancontact support. Finding it tells you the business serves European customers and has integrated their preferred local methods, a sign of a localised, conversion-conscious operation. If you sell to European businesses, or to companies expanding into Europe, a Mollie site marks an EU-market operation. The specific local methods enabled hint at the countries served (iDEAL → Netherlands, Bancontact → Belgium). Because Mollie is a default for many European SMBs and mid-market merchants, its presence is also a useful "this is a European company" signal for market research.

What finding Mollie means for sales, agencies and competitive research

For sales and prospecting, Mollie marks a European online business — a precise market signal for anyone targeting or expanding into Europe, and a fit for ecommerce, SaaS and fintech tools serving EU merchants. The local methods hint at the specific countries.

For agencies and consultants, finding Mollie tells you the client serves European customers with local methods, so engagements can address EU-specific conversion (offering the right local methods), checkout, or cross-border expansion.

For competitive and market research, Mollie (versus Stripe, Adyen or local PSPs) reveals a business's European focus and which markets it serves; mapping Mollie across a sector identifies the EU-focused players.

Mollie in the wider stack

Mollie sits in the payments layer of a European-focused commerce stack. It accompanies an ecommerce platform (Shopify, WooCommerce, Magento or a European platform like Lightspeed), analytics (GA4), a consent-management platform (GDPR), and European logistics/tax tools. On cross-border businesses, Mollie (for Europe) may sit alongside another processor for other regions. For an auditor, the valuable details are the profile ID and mode, the local methods enabled (revealing target countries), whether other PSPs serve other markets, and the ecommerce platform; together these reveal a European-focused business and its payment and market strategy. As with Razorpay for India, Mollie's real power is as a market-and-geography filter: because it is chosen specifically for European local methods, it isolates the EU-focused businesses in a list, and the particular methods enabled narrow the market further still. A store offering iDEAL is almost certainly serving the Netherlands; Bancontact points to Belgium; a broad SEPA-plus-local mix suggests a pan-European operation. So a Mollie detection, read together with its enabled methods, can pinpoint not just that a business is European but roughly which countries it prioritises — precise geographic intelligence that is genuinely difficult to obtain from a website any other way, and exactly what anyone targeting or sizing European markets needs.

A quick Mollie confirmation walkthrough

Open a checkout with developer tools on the Network panel and filter for mollie. The Components script from js.mollie.com/v1/mollie.js and traffic to mollie.com confirm Mollie. In the console, type Mollie to confirm the constructor. Inspect card fields for mollie.com Component iframes, or watch for a mollie.com hosted-checkout redirect. Note the European local methods (iDEAL, Bancontact, SEPA) offered. The js.mollie.com script or a mollie.com checkout confirms Mollie.

A quick Mollie detection checklist

• On a checkout, filter the Network tab for mollie; the js.mollie.com/v1/mollie.js script is conclusive.
• Type Mollie in the console to confirm the Components constructor.
• Inspect card fields for mollie.com Component iframes, or watch for a mollie.com redirect.
• Note European local methods (iDEAL, Bancontact, SEPA) and the countries they imply.
• Treat Mollie as a strong European-market signal.
• Distinguish Mollie (mollie.com) from Stripe, Adyen and regional PSPs.

Detecting Mollie at scale

Checking one site is quick, but mapping PSP adoption across many domains — to find European-focused businesses — calls for automation. StackOptic detects Mollie and thousands of other technologies from a real browser, reading the script, constructor and checkout traffic. For related reading, see our guide to finding out what payment processor a website uses and the full Mollie technology profile.