European alternatives to Stripe Connect.

Stripe Connect is the default answer for marketplace payments the same way Stripe is for checkout, and it carries the same structural caveat: Stripe Inc. is US-incorporated, so the consolidated group including the Dublin entity sits under US CLOUD Act jurisdiction. For a marketplace, the exposure question covers more than your own data, because the platform holds identity files and payout details for every seller on it. That is what sends European platforms, especially those selling to public-sector or regulated buyers, looking at alternatives.

Europe happens to be strong in exactly this niche. Marketplace payments under PSD2 needs an e-money or payment-institution licence, seller KYC machinery, and wallet infrastructure, and two of the global specialists are European: Mangopay (Luxembourg) and Lemonway (France). We checked six alternatives on the usual questions: who owns the company, who regulates it, where the money and data sit, and what the migration actually involves.

The three names worth knowing up front are Lemonway (France, Paris; ACPR-licensed, EU-owned cap table, 400+ marketplaces, CLOUD Act exposure: Minor), Mangopay (Luxembourg; CSSF-licensed, the deepest marketplace feature set, behind Vinted, Malt, and Chrono24, but Advent-owned since 2022, CLOUD Act exposure: Material), and Adyen for Platforms (Netherlands, Amsterdam; a publicly listed Dutch credit institution with global reach, CLOUD Act exposure: Minor).

What carries over from Stripe Connect:

• Split payments, commission collection, and scheduled payouts to sellers. This is core product on Mangopay, Lemonway, and Adyen for Platforms.
• Seller onboarding with document collection and KYC/KYB, delivered as hosted flows or API.
• PSD2/SCA-compliant checkout and PCI-DSS-scoped card acceptance.
• Webhooks, sandbox environments, REST APIs on all three.
• Escrow-style flows: funds held until delivery confirmation. On wallet-based providers (Mangopay, Lemonway) this is more natural than on Connect, one of the few places the alternatives are ahead.

Left behind on the way:

• Stripe's developer experience and documentation depth. Mangopay and Lemonway are built for payments teams at platform companies; expect more integration work and more contact with solution engineers.
• Express-style hosted seller dashboards. The EU alternatives provide onboarding flows and APIs, but the polished self-serve seller portal is more often something you build.
• Instant payouts to seller debit cards, a Connect feature tied to card-network rails; SEPA Instant covers some of the gap in Europe.
• Deep coverage for US-based sellers. Adyen keeps global reach; Mangopay and Lemonway are EEA/UK-centric.
• One-invoice simplicity: platform fees, acquiring, and payouts can split across parties depending on the setup you choose.

1. Map your account architecture before talking to vendors. Connect's connected accounts, balances, and transfers need translating into the target model: wallets per seller (Mangopay, Lemonway) or balance accounts (Adyen). Draw the money flow for your top three transaction types, including refunds and disputes, in both models. This diagram becomes the core of the vendor conversation.
2. Treat seller re-onboarding as the project, not a task inside it. KYC files do not transfer. Plan cohort-by-cohort migration: new sellers onboard to the new provider first, existing sellers follow in waves with in-product prompts and deadlines. Track completion rates per cohort; expect the long tail to need direct outreach, and decide in advance what happens to sellers who never complete verification.
3. Run both rails in parallel. Route new sellers' transactions through the new provider while existing sellers keep transacting on Connect, then move cohorts across as their re-verification completes. Marketplaces rarely manage a clean single cutover; the dual-rail phase typically runs a quarter or more.
4. Get balances to zero on Connect before closing accounts. Wallet balances and pending payouts cannot be transferred between regulated institutions as a lump; sellers must be paid out through the old rail before their account closes. Freeze new charges per cohort, flush payouts, reconcile, then close.
5. Rebuild your webhook and reconciliation layer early. Event models differ meaningfully between Connect and the EU providers (wallet credits and debits versus charges and transfers). Your finance team's reconciliation reports are usually the hidden dependency; involve them from the first integration week, not after cutover.
6. Check your DAC7 reporting path. EU marketplaces report seller income to tax authorities under DAC7 regardless of payment provider. If your current reporting pipeline reads from Stripe data exports, confirm what the new provider exposes and rebuild that feed as part of the migration, not as a January surprise.