Pay.net vs Adyen for Platforms: Multi-Rail Gateway vs Enterprise Marketplace Payments

What Adyen for Platforms Does

Adyen for Platforms is a marketplace- and platform-specific product — distinct from Adyen's standard payment gateway. It is purpose-built for businesses that need to orchestrate payment flows between buyers, sellers, and the platform itself: split payments, sub-merchant onboarding, fund escrow, and payout management.

The core use case is the Uber or Airbnb model: a buyer pays $100 for a ride or a rental, the platform takes a 20% fee, and $80 flows to the driver or host. Adyen for Platforms handles the entire orchestration: payment capture, split calculation, sub-merchant fund segregation, KYC/AML compliance for each sub-merchant, and timed payouts. For large marketplace operators, this orchestration layer is mission-critical infrastructure.

Key capabilities:

• Split payment orchestration — split any transaction between the platform and multiple sub-merchants with configurable rules
• Sub-merchant KYC/onboarding — automated identity verification and risk scoring for each seller or service provider
• Managed fund flows — escrow, payout scheduling, and reserve management per sub-merchant
• Platform liability management — manage MCC risk, chargeback liability, and dispute resolution at the sub-merchant level
• 600+ local payment methods (APMs) — global coverage including iDEAL, Alipay, GrabPay, BLIK, and hundreds more

Adyen for Platforms is used by Uber, Airbnb, Grab, and Deliveroo — organizations with extremely high marketplace payment volume and complex sub-merchant relationship management needs.

Feature Comparison

The Core Distinction: Split Payments vs Multi-Rail Acceptance

Adyen for Platforms and Pay.net solve fundamentally different problems within payment infrastructure. Understanding the distinction removes ambiguity about which product applies to your use case:

Adyen for Platforms solves a marketplace orchestration problem: how do I split $100 between a driver and my platform, while managing the driver's KYC, compliance, and payout schedule? This is about fund flow orchestration between multiple parties in a single transaction. The payment-acceptance layer is almost secondary — Adyen for Platforms cares most about what happens to the money after it arrives.

Pay.net solves a routing optimization problem: how do I accept $100 at the lowest cost and fastest settlement speed across every available payment rail? This is about getting money from buyer to merchant as efficiently as possible. Pay.net does not split payments or manage sub-merchant relationships — it optimizes the single-party merchant acceptance flow.

If you are building a marketplace where buyers pay sellers through your platform, Adyen for Platforms is the architecturally correct choice for that split-payment layer. If you are a merchant or payment gateway operator optimizing acceptance rates and settlement costs across rail options, Pay.net is the right tool. Many large platforms ultimately need both layers.

Where Adyen for Platforms Has Genuine Advantages

Sub-Merchant Onboarding at Scale

Adyen for Platforms handles automated KYC and AML verification for sub-merchants (sellers, drivers, hosts, contractors) at scale. For a marketplace with tens of thousands of sellers, this automated onboarding infrastructure is mission-critical. Each sub-merchant gets a verified account, risk score, and compliance status managed by Adyen — the platform doesn't need to build or operate this compliance layer independently. Pay.net has no equivalent sub-merchant onboarding capability.

600+ Local Payment Methods Globally

Adyen's APM coverage — over 600 local payment methods including iDEAL (Netherlands), Alipay (China), GrabPay (Southeast Asia), BLIK (Poland), PayNow (Singapore), and many more — is unmatched in breadth. For marketplaces operating across many markets with locally-preferred payment methods, Adyen's APM library significantly reduces payment friction and increases checkout conversion. Pay.net covers major rails per corridor but does not match Adyen's depth of APM coverage.

Marketplace Liability Management

When a sub-merchant has a chargeback, who is liable? Adyen for Platforms manages this complexity — MCC risk categorization, chargeback dispute handling at the sub-merchant level, reserve management, and liability allocation between the platform and sub-merchant. For marketplace operators, this liability management capability can mean the difference between a sustainable and an unsustainable chargeback exposure profile.

In-Country Acquiring Network

Adyen operates its own acquiring licenses in 40+ markets, enabling in-country acquiring for card transactions. In-country acquiring typically reduces interchange costs compared to cross-border acquiring, because the transaction is treated as a domestic card transaction by the card networks. For high-volume card transactions in major markets, Adyen's in-country acquiring can deliver meaningfully lower interchange rates than gateways routing transactions through a single acquiring country.

Enterprise-Grade SLA and Account Management

Adyen for Platforms is an enterprise product with dedicated account management, SLA guarantees, and deep professional services support for complex marketplace implementations. For organizations at Uber or Airbnb scale, this enterprise support layer is part of the product value. Pay.net is designed for faster onboarding with transparent self-serve pricing — better for organizations that don't need (and don't want to pay for) enterprise white-glove service.

Where Pay.net Leads

FedNow and RTP Native Support

Pay.net natively supports FedNow — real-time settlement in under 5 seconds, 24/7/365. Adyen for Platforms' real-time rail coverage is SEPA Instant (EU) and select local APMs. FedNow is not supported. For US-based payment flows where instant settlement is a product requirement — gig worker instant pay, real-time B2B supplier payments, insurance claim disbursements — Pay.net's FedNow integration is a decisive operational advantage.

Stablecoin Settlement at 0.3%

Pay.net's stablecoin rail (USDC) settles at 0.3% — dramatically below SWIFT wire fees for large cross-border B2B transactions. For marketplace operators handling large supplier or contractor payments internationally, Pay.net's stablecoin capability reduces settlement cost per dollar transferred. Adyen for Platforms does not support stablecoin settlement.

No Minimum Volume Requirement

Adyen for Platforms typically requires $1M+/month in platform payment volume and involves an enterprise sales process that can take months. Pay.net has no minimum volume requirement and transparent published pricing — sandbox access can be provisioned same-day, and production access follows shortly after approval. For growing platforms not yet at Adyen's enterprise threshold, Pay.net is accessible from day one.

Transparent Published Pricing

Pay.net publishes its rates: 2.4% + $0.25 standard card processing; cross-border via real-time rails at 0.5–1.0%; stablecoin at 0.3%. Adyen for Platforms uses interchange++ enterprise pricing — custom negotiated rates that require a formal proposal process. For finance teams that want predictable, benchmarkable payment costs without a procurement cycle, Pay.net's published pricing is a significant operational advantage.

Fraud.net Contractual Guarantee

Pay.net's fraud prevention engine guarantees fraud losses below 2 basis points — contractually. Adyen's RevenueProtect is a strong ML-based fraud product, but it carries no contractual performance guarantee. For platforms processing high-risk transaction types or operating in fraud-sensitive categories, a guaranteed ceiling on fraud losses provides financial predictability that RevenueProtect cannot deliver.

The Cost Comparison

For card volume specifically, Adyen for Platforms' interchange++ pricing can be competitive with Pay.net at significant scale. Adyen typically charges 0.3%–0.8% over interchange — on a $50 average transaction at 2.0% interchange, that's an effective rate of 2.3%–2.8% total, comparable to Pay.net's 2.4% + $0.25 on the same transaction.

However, the cost comparison diverges sharply on non-card rails:

• FedNow / RTP: Pay.net natively supported; Adyen for Platforms: not available
• Stablecoin cross-border: Pay.net at 0.3%; Adyen for Platforms: not available — SWIFT rates apply
• Cross-border via real-time rails (SEPA Instant, PIX, UPI): Pay.net 0.5%–1.0%; Adyen: available but not multi-rail optimized

At $10M/month in payment volume, Adyen's IC++ pricing can be competitive with Pay.net on card volume — particularly where in-country acquiring reduces interchange. But for any platform with significant non-card cross-border flow (B2B supplier payments, international contractor disbursements, stablecoin-denominated transactions), Pay.net's rail diversity delivers meaningfully lower total cost.

When to Use Both

For marketplaces that need Adyen's split-payment and KYC infrastructure but also handle cross-border B2B transactions or want FedNow capability, a hybrid architecture works effectively:

• Adyen for Platforms handles domestic split-payment orchestration — buyer-to-seller fund flows, sub-merchant KYC, chargeback liability management, and APM coverage for consumer-facing checkout
• Pay.net handles cross-border flows and real-time rail transactions — international supplier payments via stablecoin or SEPA Instant, FedNow for instant domestic settlement where Adyen doesn't reach, and any B2B payment corridor where rail optimization delivers cost savings

This architecture is increasingly common for global marketplaces that have outgrown pure card-centric payment infrastructure and need both the marketplace orchestration depth of Adyen and the real-time rail breadth of Pay.net.

Frequently Asked Questions

Does Pay.net support marketplace split payments?

Not natively. Pay.net is optimized for merchant payment acceptance and multi-rail routing. For marketplace split payments — where a single transaction flows to multiple parties (platform + sub-merchants) — and for sub-merchant onboarding at scale, Adyen for Platforms is the purpose-built solution. Pay.net and Adyen for Platforms can coexist in a hybrid architecture.

Does Adyen for Platforms support FedNow?

No. Adyen's real-time rail coverage is SEPA Instant (EU) and select local APMs. FedNow — the Federal Reserve's real-time payment network — is not supported by Adyen for Platforms. Pay.net natively supports FedNow with sub-5-second settlement, 24/7/365.

What is the minimum volume for Adyen for Platforms?

Adyen for Platforms typically requires $1M+/month in platform payment volume and involves an enterprise sales process that can take several months. Pay.net has no minimum volume requirement. Sandbox access is provisioned same-day, and transparent published pricing applies from day one — no enterprise negotiation required.

Which handles cross-border better?

It depends on the transaction type. For cross-border card volume in established markets, Adyen's in-country acquiring network often achieves lower interchange than cross-border card acquiring — a genuine advantage for high-volume card marketplaces. For non-card cross-border flows — stablecoin, SEPA Instant, PIX (Brazil), UPI (India), or SWIFT-optimized routes — Pay.net's multi-rail routing delivers meaningfully lower total cost, including stablecoin settlement at 0.3% for large international B2B transfers where SWIFT fees would otherwise apply.