A payment gateway for a single business is one decision. Infrastructure for a marketplace is another: who holds the funds between buyer and seller, who owns compliance, and how much your engineering team builds versus gets out of the box.

Both OPP and Stripe Connect let platforms embed payments and pay out to multiple merchants. But they start from different premises: OPP is purpose-built for marketplaces, with functionality for models such as C2C and B2B marketplaces built into its payment infrastructure, while Stripe Connect extends Stripe's broader payments infrastructure to platforms that need to onboard, pay, and manage multiple sellers.

This guide compares OPP and Stripe Connect across the areas that matter most for platforms: PSD2 compliance, fund holding and escrow, split payments, pricing model, KYC handling, and EU marketplace support.

Last updated: August 2026. Based on publicly available Stripe documentation and product materials at the time of writing.

OPP vs Stripe Connect at a glance

PSD2 compliance and licensing

Both providers operate as licensed, passported entities, just structured differently by region.

OPP

OPP holds a Payment Institution licence from the DNB (Dutch Central Bank) and an EMI licence in the UK from the FCA, passported through the EEA for payments.

Stripe 

Stripe's European entity, Stripe Technology Europe Limited, is authorised as an electronic money institution by the Central Bank of Ireland and passports that licence across the EEA under PSD2. In the UK, Stripe holds a separate EMI licence from the FCA.

In practice, both structures give platforms a passported, EEA-wide compliance base to build on. The difference is where the "home" licence sits (Netherlands as a Payment Institution for OPP, Ireland as an EMI for Stripe) and how liability is allocated depending on the Connect account configuration a platform chooses. Stripe's own PSD2 guidance notes that responsibility can shift depending on account type, so platforms should confirm the exact liability split for their intended setup before going live, the same caveat that applies to any PayFac-style arrangement.

Choose OPP if: you want one Dutch Payment Institution licence as the consistent compliance anchor as you expand across European markets, with escrow and payout logic managed under that single framework.

Choose Stripe Connect if: an Ireland-based EMI structure, passported EEA-wide, fits your platform's existing regulatory footprint or global expansion plans beyond Europe.

Fund holding and escrow

This is the area where the two providers diverge most clearly, and it's worth being precise about it because the terminology gets used loosely across the industry.

OPP

OPP provides native escrow: funds from a buyer are held until the transaction completes (delivery confirmed, service rendered, dispute window closed), then released to the seller. This is core infrastructure, not a bolt-on setting.

Stripe

Stripe is explicit on this point in its own documentation: escrow has a precise legal definition, and Stripe does not support escrow accounts. What it offers instead is "escrow-like" behaviour through manual transfers and delayed payouts, holding funds in a connected account's balance (up to a maximum of 90 days) until the platform triggers a payout via the Transfers API.

For platforms where holding funds until a condition is met (delivery, service completion, dispute resolution) is central to trust and safety, that's a meaningful difference: one is a licensed escrow function built into the product, the other is a configurable delay that a platform's engineering team assembles and manages.

Split payments

Both providers support splitting a single payment across multiple recipients, so this is closer to parity than the fund-holding question.

OPP

OPP supports multi-split payouts natively as part of its marketplace product: a single transaction can be divided across multiple parties in one flow.

Stripe

Stripe Connect also supports this natively, offering both one-to-many payments (a single payment split between several recipients) and many-to-many payments (multiple payers and multiple payees tracked through one system).

Where the two differ is less in whether splits are possible and more in what sits around them: OPP bundles split logic together with native escrow, KYC, wallet management, and dispute mediation in one operational environment, while on Stripe Connect a platform typically assembles split payments, fund holding, and dispute handling as separate configuration choices within a broader, more general-purpose product.

Merchant interface

OPP

OPP includes a built-in dashboard for merchant management, payout visibility, KYC document handling, and transaction monitoring as part of the core product.

Stripe

Stripe Connect does not ship a ready-made merchant-management interface for platforms in the same way. Platforms typically build their own merchant-facing dashboard using Stripe's Embedded Components, or point merchants to the standalone Express Dashboard, a lighter, Stripe-hosted view that connected accounts can use to see their own payouts and update their own details. Either route means development work sits with the platform rather than coming out of the box.

Support

OPP

OPP runs support as a tiered, in-house model: partners reach the team directly by email or a Jira ticket, backed by a dedicated solutions team for anything beyond first-line questions, through to direct dispute handling for escalations. Every case is logged for audit purposes, and coverage spans major European languages across 30+ markets.

Stripe

Stripe offers account management support across its product suite, with dedicated partner managers available for eligible Connect customers. Support channels and response models vary by plan and account tier, and platforms should confirm the specifics of their support arrangement directly with Stripe.

Pricing model

OPP

OPP publishes itemised pricing per payment method (for example, Visa/Mastercard at €0.15 plus IC++ plus 0.60%, iDEAL at €0.25), so platforms can see the exact cost of each method before integrating. 

Escrow and multi-split are listed as available services but priced on request, not published, so platforms would need to contact OPP for those specific costs.

Stripe

Stripe's Connect pricing is pay-as-you-go, but for platforms it is componentised rather than published as a single flat rate card: a base processing fee, plus optional Connect account and per-payout fees if the platform (rather than Stripe) bills connected accounts, plus any additional product add-ons. 

Stripe's own pricing page presents this as a choice between models ("Stripe sets and collects processing fees" versus the platform managing its own pricing) and invites platforms to "get in touch to discuss other options" for anything beyond the two standard models.

Which is better? For a single merchant taking card payments, Stripe's rates are publicly listed and comparable. For a platform or marketplace specifically, the full cost of running Connect (base rate plus account and payout fees plus any negotiated terms) is harder to pin down from public documentation alone without a sales conversation. OPP's published itemised list gives a platform operator a firmer number without that conversation.

Merchant onboarding and KYC

OPP

OPP's consumer onboarding takes around 1 working day, and business onboarding around 1-3 working days, with KYC checks built into the flow. 

OPP applies tiered compliance levels depending on merchant type, from basic bank account and phone verification through to identity checks and, for business merchants, UBO and Chamber of Commerce verification, and it's delivered as a single seamless API flow rather than separate registration forms for the platform and the merchant. 

The platform keeps full control over how that flow is presented, while OPP handles the compliance checks running underneath it.

Stripe

Stripe Connect onboards merchants through Stripe-hosted or embedded onboarding flows, which collect the identification and verification information Stripe needs to meet its Know Your Customer obligations. 

Stripe is explicit that these requirements vary by country and change frequently as regulators update their expectations. 

Platforms using Stripe's hosted or embedded onboarding get these updates automatically; platforms that built a custom, API-based onboarding flow are responsible for updating it themselves whenever requirements change, or risk connected accounts losing the ability to accept payments or receive payouts.

For a platform team, that's an ongoing maintenance question as much as a speed one: who keeps the onboarding flow current as KYC requirements shift.

EU marketplace support

OPP

OPP is built specifically for C2C and B2B marketplace models and SaaS platforms: online marketplaces, rental and subscription platforms, delivery services, and B2B marketplaces, with escrow and multi-split logic as the foundation rather than an add-on. Support currently spans merchants from 30+ markets.

Stripe

Stripe Connect serves a much broader base of platforms, from gig-economy marketplaces to SaaS billing platforms, and supports payouts in 50+ countries with 135+ currencies and 40-plus payment methods. Its EEA presence runs through the PSD2-passported Irish EMI licence described above.

The practical distinction is focus: Stripe Connect is general-purpose infrastructure that a marketplace configures; OPP is marketplace infrastructure with escrow, dispute mediation, and multi-split logic already built for that specific use case.

Which platform should you choose?

Choose OPP if:

• You operate a C2C or B2B marketplace where holding funds until a transaction completes matters for trust and safety

• You want native escrow rather than a configured delayed-payout workaround

• You want one itemised, published price per payment method rather than a componentised rate you need to model yourself

• You're an enterprise marketplace and want a hands-on dispute management service in addition to standard card chargeback handling

• You want a merchant-management dashboard included out of the box, rather than building one on top of embedded components

• You want to offer both online and in-person payments, with payment terminals and Tap on Mobile available alongside your payment infrastructure.

Choose Stripe Connect if:

• Your platform spans use cases beyond C2C or B2B marketplaces, or you need very broad global payout coverage

• You're comfortable configuring escrow-like fund holding yourself rather than using a native escrow product

• You want the flexibility of a large, general-purpose payments platform and are willing to have a sales conversation to model exact platform-level costs

What this means for you

The right choice comes down to how central fund holding and marketplace-specific dispute handling are to your business model, not just the headline feature list. Before choosing a provider, it's worth asking directly:

• Does the provider offer licensed escrow, or a configured delay that your team manages?

• What is the full cost of running the platform product, not just the standard per-merchant rate?

• Who is responsible for keeping onboarding and KYC flows current as requirements change?

• How is liability allocated between platform and provider under your specific account configuration?

Both OPP and Stripe Connect operate on licensed, PSD2-passported infrastructure. 

For platforms where escrow, split payments, and buyer-seller dispute mediation need to be native to the platform rather than assembled from separate pieces, OPP is purpose-built for exactly that. 

Stripe Connect remains a solid option for platforms that prioritise broad global reach and want to configure that functionality themselves.

How we compared: this comparison is based on Stripe's publicly available product documentation, pricing pages, and PSD2 guidance as of August 2026. Features, pricing, and onboarding processes change over time, and platforms should confirm current terms directly with Stripe before making a purchasing decision.

Looking for a payment partner built specifically for marketplaces? Get in touch with the OPP team to discuss your payment requirements, marketplace model, and growth plans.

FAQ