Multi-seller payments
Marketplace Payment Providers
Marketplace payments cover buyer collection, seller onboarding, balances, fees, refunds, disputes, and payouts across more than one seller. The provider's exact role can be a platform payment service, a registered payment facilitator arrangement, direct seller accounts, or another regulated structure. The directory includes only offers explicitly identified for marketplace payments where the provider operates the platform or marketplace payment service.
Last reviewed
8 company profiles
Reviewed marketplace payment products
Every selected offer is explicitly identified for marketplace payments, with the provider operating the platform or marketplace payment service. Confirm whether sellers receive individual accounts or sit under a PayFac structure, who approves them, who controls funds and how balances, refunds, reserves and payouts work.
Publishes a position on
Adyen
Adyen combines a payment gateway, risk tooling, processing, acquiring and merchant settlement for online and in-person payments. Adyen for Platforms adds user onboarding, split payments, balances and payouts, while Adyen Issuing supports physical and virtual card programs. Product access depends on the customer model, country, regulated activity, underwriting and contract.
Marketplace payment products
Adyen for Platforms
- Adyen for Platforms
Why this option is listed
The recorded role for Adyen for Platforms is Platform payments. Its selected platform-payments model assigns the provider the marketplace or platform payment role; open it to check seller approval, account structure, funds control, balances and payouts.
Role, account, approval and funds
- Role in this product
- Platform payments
- Account / MID
- Legal entity · Account holder · Balance account
- Approval
- Adyen for Platforms includes platform onboarding and seller verification
- Funds / settlement
- Custom platform to seller settlement
- Adyen for Platforms
Product categories
Merchant accounts & acquiring · Gateways
Airwallex
Airwallex provides online payment acceptance and acquiring, a multi-currency Wallet and Global Accounts with foreign exchange, cross-border payouts, Visa card issuing, and connected-account infrastructure for platforms. Each product requires its own approval and may use a different Airwallex contracting entity, regulated permission, partner rail, funds flow and pricing schedule.
Marketplace payment products
Airwallex Connected Accounts and Embedded Finance
- Airwallex Connected Accounts and Embedded Finance
Why this option is listed
The recorded role for Airwallex Connected Accounts and Embedded Finance is Platform payments. Its selected platform-payments model assigns the provider the marketplace or platform payment role; open it to check seller approval, account structure, funds control, balances and payouts.
Role, account, approval and funds
- Role in this product
- Platform payments
- Account / MID
- Ledger account · Withdrawal account · Full account
- Approval
- Airwallex Connected Accounts and Embedded Finance includes platform onboarding and seller verification
- Funds / settlement
- Airwallex handles merchant funds at one or more stages
- Airwallex Connected Accounts and Embedded Finance
Product categories
Merchant accounts & acquiring · Gateways
Checkout.com
Checkout.com provides merchant acquiring and online payment processing, a separate payment-gateway route for merchants that keep another acquirer, platform payments for marketplaces and payment facilitators, card and bank payouts, and card issuing. The contracting entity, sponsor bank, merchant approval, settlement route and permitted business activity depend on the country, product and agreement.
Marketplace payment products
Checkout.com Integrated Platforms
- Checkout.com Integrated Platforms
Why this option is listed
The recorded role for Checkout.com Integrated Platforms is Platform payments. Its selected platform-payments model assigns the provider the marketplace or platform payment role; open it to check seller approval, account structure, funds control, balances and payouts.
Role, account, approval and funds
- Role in this product
- Platform payments
- Account / MID
- Lite sub entity · Full sub entity
- Approval
- Checkout.com Integrated Platforms includes platform onboarding and seller verification
- Funds / settlement
- Custom platform to seller settlement
- Checkout.com Integrated Platforms
Product categories
Merchant accounts & acquiring · Gateways
dLocal
dLocal processes Payins, sends Payouts, supports marketplace and platform accounts, provides fraud-management tools, and collects cross-border invoices in emerging markets. Product availability, payment methods, contracting entity, currencies and local processing partners depend on the selected countries and commercial agreement.
Marketplace payment products
dLocal for Platforms
- dLocal for Platforms
Why this option is listed
The recorded role for dLocal for Platforms is Platform payments. Its selected platform-payments model assigns the provider the marketplace or platform payment role; open it to check seller approval, account structure, funds control, balances and payouts.
Role, account, approval and funds
- Role in this product
- Platform payments
- Account / MID
- User account · Liable account
- Approval
- dLocal for Platforms includes platform onboarding and seller verification
- Funds / settlement
- dLocal handles merchant funds at one or more stages
- dLocal for Platforms
Product categories
Platforms, wallets & payouts
Mangopay
Mangopay supplies wallet-based payment infrastructure for platforms: pay-ins enter electronic wallets, wallet transfers can allocate or split balances, verified users can receive funds, and payouts move wallet funds to registered bank recipients. Pay-ins may be acquired by Mangopay or by another approved payment service provider. Multi-currency Accounts, Identity and Payouts are also sold as distinct products. The contracting entity, regulated service, funds treatment and product access depend on the platform agreement and jurisdiction.
Marketplace payment products
Wallet-based platform payments
- Wallet-based platform payments
Why this option is listed
The recorded role for Wallet-based platform payments is Platform payments. Its selected platform-payments model assigns the provider the marketplace or platform payment role; open it to check seller approval, account structure, funds control, balances and payouts.
Role, account, approval and funds
- Role in this product
- Platform payments
- Account / MID
- Mangopay account · Per currency electronic wallet
- Approval
- Wallet-based platform payments includes platform onboarding and seller verification
- Funds / settlement
- Mangopay handles merchant funds at one or more stages
- Wallet-based platform payments
Product categories
Gateways · Platforms, wallets & payouts
Mollie
Mollie provides regulated online and in-person payment services for businesses in the European Economic Area, Switzerland and the United Kingdom. Mollie B.V. is the Dutch-regulated entity for EEA services, while Mollie UK Ltd provides the UK-regulated service and UK settlement route; UK non-card EU methods can pass first through Mollie B.V. and Stichting Mollie Payments before Mollie UK safeguards and pays out the funds. Mollie processes and settles merchant payments but its general card route connects merchants to external method acquirers and financial institutions. Mollie states that it became an iDEAL acquirer, but that method-specific role does not make Mollie a universal card acquirer, traditional merchant-account provider or dedicated-MID provider.
Marketplace payment products
Mollie Connect for Marketplaces
- Mollie Connect for Marketplaces
Why this option is listed
The recorded role for Mollie Connect for Marketplaces is Regulated marketplace payment services provider. Its selected platform-payments model assigns the provider the marketplace or platform payment role; open it to check seller approval, account structure, funds control, balances and payouts.
Role, account, approval and funds
- Role in this product
- Regulated marketplace payment services provider
- Account / MID
- Mollie organisation account · Mollie balance
- Approval
- Mollie Connect for Marketplaces includes platform onboarding and seller verification
- Funds / settlement
- Custom provider to merchant settlement
- Mollie Connect for Marketplaces
Product categories
Merchant accounts & acquiring · Gateways
Nuvei
Nuvei provides acquiring, processing, gateway, orchestration, merchant accounts, payouts, platform payments, issuing, banking and crypto services.
Marketplace payment products
Nuvei for Platforms
- Nuvei for Platforms
Why this option is listed
The recorded role for Nuvei for Platforms is Platform payments. Its selected platform-payments model assigns the provider the marketplace or platform payment role; open it to check seller approval, account structure, funds control, balances and payouts.
Check funds / settlement
Managed through Nuvei for Platforms
- Role in this product
- Platform payments
- Account / MID
- Virtual account · External account
- Approval
- Nuvei for Platforms includes platform onboarding and seller verification
- Funds / settlement
- Managed through Nuvei for Platforms
- Nuvei for Platforms
Product categories
Merchant accounts & acquiring · Gateways
Stripe
Stripe provides online payment acceptance, connected-account infrastructure for platforms, a separate merchant-of-record product for digital commerce, and card-program infrastructure. Payments, Connect, Managed Payments, and Issuing have different merchant-of-record, acquiring, loss-liability, settlement, and bank responsibilities. Business approval is product-, country-, activity-, and contract-specific.
Marketplace payment products
Stripe Connect
- Stripe Connect
Why this option is listed
The recorded role for Stripe Connect is Platform payments. Its selected platform-payments model assigns the provider the marketplace or platform payment role; open it to check seller approval, account structure, funds control, balances and payouts.
Role, account, approval and funds
- Role in this product
- Platform payments
- Account / MID
- Platform account and connected accounts
- Approval
- Stripe Connect includes platform onboarding and seller verification
- Funds / settlement
- Custom platform to seller settlement
- Stripe Connect
Product categories
Merchant accounts & acquiring · Gateways
Decision brief
Set the seller account model before building onboarding
Use this page when
A platform collects buyer payments for more than one seller and must assign approval, funds-control, loss and payout responsibilities.
Seller relationship
Choose the direct merchant, sponsored merchant, payment-account or Merchant of Record structure for each market.
Funds authority
Identify who receives buyer money, controls balances and splits, delays payouts, debits losses and closes a seller account.
Portfolio tail
Set how refunds, disputes, reserves and negative balances remain funded after a seller or the whole marketplace leaves.
Resolve before a seller goes live
- Signed seller terms with named approval, funds-control and termination parties
- Separate statuses for identity checks, payment approval, capabilities and payouts
- Written allocation of refunds, disputes, reserves, losses and closure rights
Choose the seller account and acquiring structure first
Identify whether each seller has a direct merchant agreement, is a sponsored merchant under a payment facilitator, receives a payment or wallet account, or sells through a Merchant of Record. These models allocate underwriting, card-network registration, customer-facing sale, funds control, chargebacks, and termination differently.
Ask for the acquirer, payment facilitator or platform entity, seller agreement, MID or account structure, approved MCC, descriptor, and countries for the selected product. A marketplace API can expose common onboarding screens while different legal entities and acquiring routes sit behind each market.
- Marketplace, seller, provider, acquirer, and customer contracts
- Direct MID, sponsored merchant, payment account, or MoR structure
- Seller MCC, descriptor, products, countries, and channels
- Entity with final seller approval and termination authority
Keep data collection, verification, and approval separate
Map which party collects seller and beneficial-owner data, verifies identity, checks products and licenses, assigns the MCC, reviews sanctions or fraud risk, and makes the payment-account decision. A platform can own the user experience while the provider or acquirer retains final approval.
Confirm required fields, document refresh, country and product exclusions, manual-review queues, status meanings, change notifications, and offboarding. The marketplace needs enough status detail to avoid allowing sales before the relevant payment route is active.
Do not treat onboarding as one boolean
Track platform acceptance, identity verification, payment-account approval, requested capabilities, payout activation, and any reserve or limit conditions independently.
Trace buyer funds through balances and seller payouts
Document who receives buyer funds, whether the provider creates seller balances, when a balance becomes available, how the platform fee is calculated, and who instructs the payout. A ledger entry is not necessarily a bank deposit or funds legally owned by the seller at that moment.
Confirm safeguarding or custody language, settlement and payout cutoffs, currencies, FX, payout fees, negative balances, reserves, payout holds, failed bank transfers, and account closure. If the marketplace can change the recipient or split, identify the controls and audit trail around that authority.
Allocate refunds, disputes, fraud, and losses in writing
Set out who can issue a refund, which balance funds it, who receives a dispute notice, who provides evidence, and who bears the chargeback, fee, network assessment, or negative balance. The operating workflow should match the seller agreement and the provider's account structure.
Ask how the provider monitors individual sellers and the marketplace portfolio, what thresholds can trigger reserves or payout delays, and whether one seller event can affect other sellers. Confirm appeal, remediation, suspension, and post-termination recovery rights.
Join payment reporting to seller and tax records
Use identifiers that connect buyer order, seller, payment, fee, tax, refund, dispute, balance movement, and payout. Platform reporting obligations vary. For example, DAC7 requires specified platform operators to report identification and financial information for reportable EU sellers, while EU VAT marketplace rules depend on the transaction and deemed-supplier conditions.
Before migration, confirm export of seller identity data, account status, payment tokens, balances, reserves, disputes, tax records, and payout instructions. Determine which records can move, which sellers must be re-onboarded, and how old refunds, chargebacks, and negative balances remain funded after new transactions move elsewhere.
FAQ
Common questions
Is every marketplace payment provider a payment facilitator?
No. A product may use direct seller merchant accounts, a payment facilitator structure, payment accounts, a Merchant of Record, or a market-specific combination. Confirm the selected product and country.
Does hosted seller onboarding mean the seller is approved?
No. Hosted onboarding can collect and verify data while a provider or acquirer still decides whether the seller and requested payment capabilities are approved. Use the documented status and conditions.
Who owns marketplace seller balances?
The answer depends on the account and funds structure. The contract should identify the regulated entity, account holder, safeguarding or custody arrangement, balance conditions, reserves, and payout rights.
Can a marketplace move sellers to another provider easily?
Not automatically. Seller accounts, verification, tokens, balances, reserves, disputes, and payout instructions may not be portable. Request the export and re-onboarding process before launch.