Ecommerce payments for Online marketplaces.
Online marketplaces connect buyers and sellers at scale and live or die on payments.
Cardflo provides marketplace-specific orchestration: split payments at authorisation, automated multi-vendor payouts, escrow flows for marketplace-of-record models, KYB onboarding for sellers, and global acquiring under a single integration so platform operators can scale onto new corridors without rewiring the stack.
- Industry
- Online marketplaces
- Category
- Ecommerce
- Cardflo support
- Yes
The overview
Online marketplaces operate as intermediaries. They connect many independent sellers and buyers.
This necessitates a payment architecture. It differs significantly from standard direct-to-consumer ecommerce.
The primary complexity lies in the movement of funds. A single checkout session may involve items from multiple vendors.
The payment gateway or orchestrator must split the gross transaction value. This happens at the point of authorisation.
This process must account for platform commissions. It also covers tax obligations.
And it calculates the net payout due to each sub-merchant. Managing these flows involves navigating complex regulatory frameworks.
An example is PSD2 in Europe. This often requires marketplaces to hold a payment institution licence.
Alternatively, they can use a regulated service provider. This avoids being in possession of third-party funds.
Operators can implement specific marketplace logic. This is done within the payment stack.
They can then automate the reconciliation of pay-ins to pay-outs. They also manage risks associated with sub-merchant defaults.
And chargebacks are managed. And anti-money laundering requirements are covered.
How it works
Sub-merchant onboarding and KYB
Sellers undergo Know Your Business (KYB) checks. This happens before they receive funds. These checks verify identities and beneficial ownership. This stage establishes a unique sub-merchant identifier (SMID). This SMID is within the system. It ensures all subsequent transactions and payouts are correctly attributed. This is for the specific entity. It covers tax and compliance purposes.
Multi-vendor cart authorisation
A buyer checks out with multiple items. The payment request includes metadata. This identifies the split logic. The acquirer authorises the total amount. However, the orchestration layer dictates how that sum is divided. This division includes the platform's commission. It covers the seller's portion. And it includes any applicable tax or shipping fees.
Funds hold and reconciliation
Authorised funds are typically held. They are in a regulated escrow or specific nodal account. This prevents the marketplace from taking direct possession of seller money. This is before the fulfilment criteria are met. The system matches incoming settlement files from the acquirer. It checks these against the internal ledger. This ensures accuracy.
Automated payout execution
The system initiates payouts. This is based on predefined triggers. Examples include delivery confirmation or a set cooling-off period. Payouts are made via local clearing houses or real-time rails. This step deducts any refund reserves. It also deducts subscription fees owed by the seller to the marketplace platform.
Why it matters
Operational efficiency through automation
Manual reconciliation of thousands of sub-merchant transactions is prone to error. It also does not scale. Marketplace operators can use automated ledgering. They can also use split-payment logic. This helps them manage high volumes of transactions. They do not need to increase back-office headcount. This automation ensures sellers are paid accurately and on time. This is a critical factor in merchant retention. It also affects the overall health of the marketplace ecosystem.
Regulatory compliance and risk
Marketplaces often fall under regional payment services directives. Failing to structure fund flows correctly can lead to classification as an unlicensed money transmitter. Implementing a formal marketplace payment structure ensures funds are handled through regulated entities. This reduces legal liability. Assigning chargebacks directly to the responsible sub-merchant protects the platform's overall merchant identification number (MID). It also protects its financial stability.
Regulatory notes
PSD2 Agent and Licence Exemptions
In the European Economic Area, marketplaces must ensure compliance. They must not fall foul of the 'commercial agent' exemption restrictions.
The exemption is rarely applicable now. This is following the implementation of PSD2.
This applies if the platform acts for both the buyer and the seller. Most operators must now use a payments partner.
This partner provides a regulated framework. This avoids the requirement of obtaining their own full banking or payment institution licence.
Global Tax Compliance (1099-K and VAT)
Marketplaces are increasingly responsible for tax reporting and collection. In the US, the IRS requires 1099-K reporting for sellers.
This applies over certain thresholds. In the EU and UK, Marketplace Facilitator laws exist.
These often require the platform to collect and remit VAT. This is on behalf of overseas sellers.
Payment systems must capture and export transaction data. This is necessary to support these recurring regulatory filings.
Use cases
Service booking platforms
Platforms for professional services require payments to be held. This is until the service is delivered. Split logic ensures the platform takes a lead-generation fee. The service provider receives the balance after completion.
Physical goods aggregators
Retail marketplaces manage basket fragmentation. One order contains three different sellers. The system ensures each seller receives their specific portion. It also handles individual shipping cost distributions automatically.
Software-as-a-Service marketplaces
App stores or plugin directories use these flows. They manage recurring commissions. Users renew subscriptions. The system then automatically distributes monthly royalties to developers. It also retains the platform's percentage.
By the numbers
This is the standard delay for cross-border marketplace payouts. It occurs after settlement. It depends on the rail used. It also depends on the sub-merchant's risk profile.
This is the typical proportion of sub-merchant applications. They can be verified via automated databases. This is before manual intervention by compliance teams is needed.
This is the average threshold. Marketplaces generally begin to offboard sub-merchants at this point. This helps maintain healthy standing with card schemes.
Related terms
Book a scoping call to see how Cardflo would set you up.
What's included.
- Programmatic splitting of transaction revenue between the platform and multiple third-party sub-merchants.
- Automated Know Your Business verification to ensure compliance with global anti-money laundering regulations.
- Support for marketplace-of-record models to simplify tax and VAT collection across different jurisdictions.
- Dynamic payout scheduling including daily, weekly, or performance-based triggers for seller disbursements.
- Direct chargeback attribution to specific sub-merchants to protect the platform's primary acquirer relationship.
- Regional payout support using local schemes such as SEPA, ACH, and Faster Payments.
- Maintenance of rolling reserves at the sub-merchant level to mitigate financial risk from returns.
- Granular ledger reporting for transparent reconciliation of platform fees and gross merchandise volume.
- Integrated subscription billing for seller listing fees or premium marketplace membership tiers.
- Global currency management allowing buyers to pay in local tender while sellers receive domestic currency.
Talk to an acquiring specialist about your MID setup.
Common questions.
What is the difference between a marketplace-of-record and a payment aggregator?
A marketplace-of-record (MoR) takes legal responsibility for the transaction, including tax liabilities and compliance, acting as the entity and merchant name that appears on the cardholder's statement.
A payment aggregator or PSP model typically facilitates the movement of funds between the buyer and the sub-merchant but may not be the legal seller of the goods or services.
The choice depends on the desired level of control over the customer experience and the extent of the platform's tax and regulatory obligations across different international markets.
How does PSD2 affect online marketplaces in the UK and Europe?
Under PSD2, marketplaces that act as intermediaries between buyers and sellers are generally prohibited from receiving funds on behalf of both parties unless they hold a Payment Institution licence.
To remain compliant without a licence, marketplaces must use a regulated payment service provider that offers specific marketplace accounts.
These providers ensure that the marketplace operator never has 'possession' of the funds, as the money flows directly through regulated accounts until it is split and disbursed.
Can a single transaction be split between more than two parties?
Yes, advanced marketplace logic allows for n-way splitting. This means a single authorised transaction can be divided into a platform fee, a primary seller's net total, a secondary seller's portion, and even payments to third-party affiliates or logistics providers.
Each destination is tracked on a ledger to ensure that the total settlement from the acquirer exactly matches the sum of the individual payouts and retained fees.
How are chargebacks handled in a multi-seller marketplace environment?
In a robust marketplace setup, chargebacks are linked to the specific sub-merchant whose goods or services were disputed.
While the acquirer may debit the platform's main account, the payment system should automatically reconcile this by deducting the amount from the sub-merchant's future payouts or their rolling reserve.
This protects the marketplace's revenue and ensures that sellers are held accountable for their own fulfilment performance and product quality.
What is the role of a rolling reserve for marketplace sellers?
A rolling reserve is a percentage of a sub-merchant's sales that is held by the platform or processor for a set period, such as 30 or 60 days.
This acts as a financial buffer to cover potential chargebacks or refunds if the seller's account has insufficient funds.
For marketplaces with high-risk products or long lead times, reserves are an essential risk management tool to prevent the platform from incurring losses due to seller insolvency.
How does KYB differ from standard KYC for marketplace onboarding?
Know Your Business (KYB) is the verification of a legal entity rather than an individual. While KYC focuses on the identity of a single person, KYB involves verifying the company's registration, its physical address, and its Ultimate Beneficial Owners (UBOs).
This is more complex than standard KYC and is mandatory for marketplaces to ensure they are not inadvertently facilitating money laundering or doing business with sanctioned entities.
Related guides.
Ready for velocity?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.