Webflow verdict · build Seeking alternatives

Native iDEAL payment gateway for Webflow

Built for European Webflow e-commerce users (especially Netherlands/DACH region) needing iDEAL payments without external paid add-ons..

“Hello, Please correct me if I’m wrong, but it still seems to be impossible to accept iDEAL payments on Webflow sites, without adding a paid add-on (@foxy). Is t…”

The receipts — real demand

“Hello, Please correct me if I’m wrong, but it still seems to be impossible to accept iDEAL payments on Webflow sites, without adding a paid add-on (@foxy). Is there any ETA on this finally being arranged? It’s been years since we’ve been asking for this.”
Webflow · view original →

Full dossier

Unlock the full dossier — free

Every corroborating quote, the source receipts, and the community echo. One email, no payment.

6.0 / 10 · demand score
Pain 8
Willingness to pay 5
Feasibility 4
Specificity 9
Audience 7
Competition 6

Why this is a gap

Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.

The market

European Webflow e-commerce users in Netherlands, Germany, Austria, and Switzerland who need iDEAL payments. This is a regional gap with clear, bounded demand in high-ecommerce-adoption markets.

Competition & the opening

Crowded market · 6/10 vs Webflow

Foxy.io and Snipcart are paid add-ons enabling iDEAL on Webflow. The gap is a native, free (or freemium) iDEAL integration built directly into Webflow's payment settings.

What's hard to build

iDEAL requires PSD2 compliance, Dutch banking infrastructure integration, and acquiring a payment processor license or partnership. Webflow's embedded payment architecture may not expose the hooks needed for true native integration without Webflow's cooperation.

Why now

Webflow lacks native iDEAL support in EU; third-party solutions like Foxy are expensive, creating demand for native integration.

How you'd monetize

$99/mo app or per-transaction 1.5%