Five EU Payment Methods and Where Each One Silently Fails on Shopify

Five EU local payment methods - iDEAL, Bancontact, TWINT, BLIK, and SEPA - each fail on Shopify in a different way, and the payment settings screen looks correct in every case. Here is how they compare, and which combinations actually render at checkout.

iDEAL handles roughly 70% of online payments in the Netherlands. Bancontact holds around 78% of Belgian online spend. In Germany, 82% of shoppers abandon a purchase when their preferred method is missing at checkout - the EHI Retail Institute number that Dutch and Belgian merchants keep re-posting to r/shopify when they explain why their conversion looks the way it does. These are the default payment rails in their countries. Missing one costs a merchant real orders, on the same scale as hiding the credit card option would in the US. Shopify supports most of them. The path from "enabled in admin" to "visible at checkout" just has more gates than the admin exposes.

Here is the quick lay-of-the-land I hand to merchants before we dig into any specific one:

Method	Native path	Third-party gateway path	The silent failure to expect
iDEAL	Shopify Payments (NL)	None on standard checkout	Six eligibility gates, no error surfaced
Bancontact	Shopify Payments (BE)	None on standard checkout	Same six gates as iDEAL
TWINT	Shopify Payments (CH), Swiss accounts only	Mollie or PEND (CHF-primary store)	Non-Swiss accounts blocked with no admin flag
BLIK / Przelewy24	Shopify Payments (PL) since Spring 2026	Przelewy24 gateway direct	Enabling in Stripe does not surface it at checkout
SEPA (recurring)	None	Firmhouse + Mollie	Native subscriptions do not accept it

Which gateway actually surfaces them

The most common EU payment mistake I see is a merchant on Stripe enabling iDEAL, Bancontact, BLIK, or Przelewy24 in Stripe's dashboard, watching them show up in Stripe's own payment method list, and assuming that means they will render at Shopify checkout. They do not.

Shopify's third-party gateway integration for Stripe exposes card-based methods only. When a Dutch customer opens your checkout, Stripe's iDEAL toggle sits in Stripe's admin looking active, and Shopify's checkout page quietly omits it. There is no error, no warning, and no admin badge that flags the misalignment. A French merchant running a Polish store described exactly this in an August 2024 Shopify Community thread: BLIK and Przelewy24 enabled in Stripe, neither appearing at Shopify checkout, Shopify staff replying with a redirect to sign up separately with Przelewy24 directly.

The four EU local payment methods that only work through Shopify Payments are iDEAL (Netherlands), Bancontact (Belgium), TWINT (Switzerland, and only if your Shopify Payments account is Swiss-registered), and BLIK plus Przelewy24 (Poland, since Spring 2026). If Shopify Payments is not available in your country of registration, none of these have a standard-checkout path. You either register an entity in a Shopify Payments-eligible country or you route customers through a separate checkout tool that they experience as an external redirect - which usually costs 3 to 8 conversion points compared to the native flow, in the audits I have done.

The six eligibility gates

Enabling iDEAL in Shopify Payments looks like a one-click toggle. In practice, six conditions all need to be true before the method actually renders at a Dutch customer's checkout:

Shopify Payments is your active gateway, not a third-party one.
Test mode is off in Settings, Payments.
The Netherlands market exists and is active in Settings, Markets.
The checkout currency for Dutch customers resolves to EUR.
Your store has a published legal notice (Impressum) with company name, address, and contact information. Shopify added this to the Help Center eligibility list in 2026; earlier setup guides do not mention it.
The store has processed roughly 100 prior orders. This is reported consistently by Netherlands merchants and a Shopify Expert cited an OpKlopper article on the same threshold in a June 2026 thread. It is still not documented in Shopify's Help Center as of this writing.

Fail any one of the six and iDEAL does not appear. The admin does not tell you which one. Bancontact carries the same shape with Belgium in place of Netherlands. TWINT has a similar list with Switzerland and CHF, plus a country-of-registration gate that quietly excludes non-Swiss Shopify Payments accounts entirely.

A Swiss merchant (Clementin in the "TWINT not showing at checkout for Swiss customers" thread) documented the extreme version of this in December 2025: every eligibility box checked, TWINT still absent, three weeks of support contact before Shopify manually flipped a switch on the backend. No public explanation of what changed. A German merchant running a Swiss market, who has done the same setup, gets no such switch - the answer they receive is "there is no proper solution for TWINT in Shopify Payments for non-Swiss shops."

If you are on day one of a new Netherlands store and iDEAL does not appear, do not assume you are misconfigured. Check the six gates, then keep processing orders. The 100-order threshold clears itself over the first few weeks of activity for most stores I have watched go through it.

What breaks quietly after activation

Even when every gate passes, two failure classes remain.

The first is a PPRO-layer routing error. PPRO is the backend provider Shopify uses for iDEAL processing, which is not something Shopify advertises anywhere in the admin. In February 2023, a Dutch merchant (Stefan at SDB-Forums) reported abandoned checkouts triggered by a "payment_method_unavailable" error on iDEAL despite everything looking correct in his admin - roughly half his daily revenue at the time of reporting. The same error shape shows up again in threads from March 2025 and December 2025. The December 22, 2025 outage was traced, in a Shopify developer forum thread, to "a regional routing issue between Shopify's payment orchestration layer and PPRO's iDEAL gateway." When your customers hit this and your settings look right, the correct next step is Shopify Support with specific order IDs, not iDEAL - you have no direct account with iDEAL and cannot open a ticket there. Some of the older Community threads on this had merchants going in circles for weeks before figuring that out.

The second is TWINT's post-activation checkout error. Two Swiss merchants (Major-Fish and Frisi) reported in November 2025 that TWINT was active in Shopify Payments settings but produced a generic "problem occurred processing your payment" error at checkout. No public root cause was posted. Both reverted to PEND as a stopgap. I have not tested this on a currently-active Swiss store in the last three months, so I cannot tell you whether the underlying condition was resolved silently or is still recurring. If you hit it, contact Shopify Support directly and keep a PEND or shopify-twint.ch fallback available while you wait.

One item that sits outside the "silent" pattern but is worth naming here anyway: Sofort was removed from Shopify on December 6, 2024. If your German admin still shows Sofort listed in Settings, Payments, that configuration is inert - no customers can complete a purchase through it, and the setting is now essentially decorative. Klarna is Shopify's documented replacement. Klarna through Shopify Payments has its own set of activation and visibility failures - here is the walk-through I use with merchants when Klarna does not show up either - so budget a few hours to work through those before you switch.

Where subscriptions still do not work

Recurring billing on Shopify's native checkout path does not accept any of the EU local payment methods. Not iDEAL. Not SEPA. Not Bancontact.

Shopify Staff confirmed "no plans to support SEPA for subscriptions" in September 2022. As of June 2026, a fresh Community thread was still asking for Mollie as a native subscription gateway - no staff reply. That is four years of the same wall, and it is the single most-asked question I get from Dutch merchants who launched on a card-only checkout and then tried to layer Subscribe and Save on top.

The workaround Dutch merchants have converged on is a split-provider architecture: standard Shopify Payments for one-time orders, Firmhouse (the Dutch subscription platform) with Mollie for the recurring flow. It works. It also costs. One merchant in a May 2025 r/shopify thread ("US founders have no idea how broken Shopify is in the EU") reported paying $4-6k a month in combined third-party fees to keep an EU-compliant subscription checkout running. That is real money for a business under $1M in revenue, and the closest thing to a native path is Wero (iDEAL's successor) planning subscription support in 2027 - which is not the same thing as Shopify shipping subscription support for Wero.

If you sell subscription products to Dutch or German customers today, do not budget for a native Shopify fix in 2026. Budget for Firmhouse and Mollie, or accept the conversion penalty of restricting subscription customers to card payments and losing the direct-debit share. The middle option - card-only for subscriptions and iDEAL for one-time - is what most solo merchants in this bucket actually run, because the third-party stack costs more than the recurring revenue justifies at their scale.

What I would actually pick

Here is what I recommend when a merchant asks which EU local payment methods to enable and which route to enable them through.

If you sell into the Netherlands, Belgium, Switzerland, or Poland from a Shopify Payments-eligible country of registration: use Shopify Payments. Do not run Stripe as the primary gateway on the EU checkout. Every one of the local methods you actually need - iDEAL, Bancontact, BLIK, Przelewy24, and TWINT if you are Swiss-registered - is available natively through Shopify Payments, and none of them is available through Stripe as a third-party gateway on the standard checkout. The trade-off with Shopify Payments' own failure modes (the six eligibility gates, the occasional PPRO outage) is real, but it is a smaller trade-off than customers seeing your checkout redirect them to a domain they do not recognize.

If you are a German or Dutch merchant selling into Switzerland and Shopify Payments TWINT is closed to you: run a second, Switzerland-dedicated Shopify store with CHF as the primary currency and Mollie as an additional payment provider. Every other workaround (Stripe-based Easy Pie Checkout, the shopify-twint.ch plugin, changing your main store's primary currency to CHF) has trade-offs that hit either your other markets or your reporting. A separate store is more setup work, and it is the cleanest boundary I have found.

If you sell subscriptions to Dutch customers: assume no native fix in 2026. Plan for Firmhouse and Mollie as your subscription rail. Revisit in Q2 2027 once Wero's roadmap and Shopify's response to it are actually visible in the changelog.

If you are on Stripe as your third-party gateway and expanding into any EU country: switch to Shopify Payments before you finish the market setup, not after. The order matters. Merchants who add markets first and discover the local-method gap later end up rebuilding checkout configuration under conversion pressure, which is not a place I would want to be running a launch from.

And if you are a US-based founder about to open EU sales and you are unsure which of these apply to you, the first fifteen minutes with a help1 expert is free and this is exactly the setup call it is best used for. Most US founders arrive assuming Stripe covers them and leave with a Shopify Payments plan for two of the five methods that matter. That saves them a rebuild.

The one check to run this afternoon

Open your live storefront in an incognito window. Set your shipping address to a Dutch, Belgian, Polish, or Swiss postcode (any real address in one of those countries works). Walk your own cart to the payment step and confirm the expected local method actually appears in the list.

If it does not, work the six gates for that market in order before touching anything else, and file a support ticket with a specific customer order ID if the method still refuses after the gates pass. That single check catches the "enabled in admin but silently missing" case that starts most of the support tickets I see in this area, and it takes about as long as reading this post did.