
Building a Payment Stack for a UK Marketplace: Accepting from Buyers and Paying Out to Sellers
A growing UK marketplace often hits a payment ceiling long before it runs out of demand. The buy-side gateway processes cards from fifteen countries, while a separate provider handles seller payouts across twenty more. Foreign exchange sits with a third-party bank, and reconciliation takes days of spreadsheet work each month. Every piece was reasonable on its own; together, they form an ecommerce payment solution problem that limits how far the platform can scale.
The core challenge that separates a marketplace from a single-merchant retailer is two-sided: the platform must accept payments from buyers in multiple currencies and methods, then disburse earnings to sellers in their own local currencies, all while remaining compliant with UK financial regulations. Getting this payment architecture right early determines whether the platform can expand into new markets without rebuilding its financial infrastructure from scratch.
The Two Sides of a Marketplace Payment Stack
A marketplace payment stack has three distinct layers: buyer-side acceptance, seller-side payouts, and a treasury layer that sits between the two. Each layer has its own technical, regulatory and commercial requirements. A platform that treats them as one problem, or ignores the treasury layer entirely, creates reconciliation debt that compounds with every new market.
Buyer-Side: Payment Acceptance
Buyers expect to pay in their local currency using their preferred method. For a marketplace operating across Europe, that means supporting local payment options per market rather than relying solely on international card rails. In the UK alone, open banking processed 351 million transactions in 2025, a 57 per cent year-on-year increase, with 16.5 million active user connections by December of that year, according to the Open Banking Implementation Entity’s impact report. Pay-by-bank now offers a genuine alternative to card acceptance, with lower processing costs and strong conversion rates for high-value transactions.
The buyer-side requirements for a cross-border marketplace include local payment methods per target market, multi-currency acceptance, intelligent routing to maximise approval rates, and SCA-compliant authentication flows that satisfy PSD2 obligations without creating unnecessary friction at checkout. An ecommerce payment platform built for this use case routes each transaction through the optimal acquirer based on card BIN, geography and currency, rather than sending every payment through a single channel.
Seller-Side: Payouts
Sellers need their earnings in local currency, delivered through their preferred method, on a predictable schedule. This is a fundamentally different infrastructure problem from one-off supplier payments. A marketplace payout solution must support broad country and currency coverage, ideally through local clearing rails rather than expensive international wire transfers, along with automated KYC onboarding for new sellers and configurable scheduling that accommodates instant, daily, on-demand and milestone-based payouts.
Split payments and escrow functionality are equally critical. When a buyer completes a purchase, the platform needs to programmatically divide that payment between the seller’s earnings and the marketplace’s commission, holding funds in escrow where necessary until delivery is confirmed or a dispute window closes. At scale, managing this manually is unsustainable; the payout infrastructure must handle commission splits, holds and releases automatically as part of the settlement flow.
The Treasury Layer In Between
Between pay-in and payout, the marketplace holds funds. The currency and timing of conversion is a financial decision, not a bank default. A platform accepting euros from a German buyer and paying out in pounds to a UK seller has a choice: convert immediately at the point of acceptance, hold the position and convert at payout, or batch conversions at optimal rates during the day.
When a marketplace runs two separate providers, one for acceptance and one for payouts, FX conversion often happens twice: once when funds arrive and again when they leave. A unified embedded finance platform manages this natively through multi-currency accounts, allowing the marketplace to hold balances in the original currency and convert once at a controlled rate, eliminating the double-conversion cost that erodes margins on every cross-border transaction.
Why a Unified Platform Beats Bridging Separate Providers
Marketplace founders often start by stitching together the best point solution for each function. That approach works early, but the operational cost of maintaining multiple integrations grows faster than the platform itself. A unified ecommerce payment solution offers four structural advantages over a bridged architecture:
- Reconciliation. One data model creates one source of truth. Rather than manually matching transaction records between two systems with different reference formats, settlement timelines and reporting structures, the marketplace reconciles from a single ledger.
- FX efficiency. Convert once at a controlled rate rather than absorbing markups at both the acceptance and payout boundaries. According to OpenDue’s analysis of hidden cross-border payment costs, FX spreads can add 0.5 to 5 per cent to cross-border payments and are often ten times larger than the visible transaction fee.
- Compliance simplicity. One regulated partner means one KYC and KYB framework, one AML relationship, and coverage under the partner’s licences rather than the marketplace assuming its own regulatory obligations. This reduces the compliance surface from multiple provider agreements to a single contractual relationship.
- Engineering efficiency. One integration to build, test and maintain. Two providers kept in sync require ongoing engineering attention for every API change, every settlement-cycle update and every new payment method, effort that scales linearly with each additional market.
Compliance: What a UK Marketplace Must Consider
A marketplace is not neutral for payment-regulation purposes. Under the Payment Services Regulations 2017, how funds flow between buyers and sellers determines whether the platform itself has payment-institution obligations. If the marketplace holds buyer funds on behalf of sellers, it may be conducting a regulated payment-service activity. The FCA’s approach document sets out how it interprets these obligations, including the conditions under which a commercial-agent exclusion might apply and when it does not.
The practical shortcut is to partner with an FCA-authorised provider so that payment flows run under regulated infrastructure without the marketplace itself becoming authorised. The payment partner handles KYC and KYB verification for sellers, AML screening, transaction monitoring, chargeback management and PCI-DSS compliance for cardholder data. ONERWAY operates as a fully authorised Electronic Money Institution licensed by the Financial Conduct Authority (Firm Reference No. 937049), covering buyer-side payment acceptance, seller payouts and the treasury layer through a single integration, an ecommerce payment platform built for two-sided payment architectures.
Building the Right Architecture Early
Getting the two-sided payment architecture right early determines how far a UK marketplace can scale. A unified, FCA-licensed platform consolidates buyer acceptance, seller payouts, split payments and foreign-exchange management into one integration, eliminating the reconciliation overhead, double-conversion costs and compliance complexity that come with bridging separate providers. For marketplace founders, CTOs and finance leads designing or re-platforming a payment stack, the architecture decision is not which individual components perform best in isolation; it is which platform handles both sides and the treasury layer between them without creating operational debt that compounds with every new market.
Frequently Asked Questions
What payment infrastructure does a UK marketplace platform need?
A UK marketplace needs three layers: buyer-side payment acceptance supporting local methods and multiple currencies, a seller-side payout system that disburses earnings in local currencies on configurable schedules, and a treasury layer that manages currency conversion and fund holding between the two. A unified ecommerce payment solution covers all three through one integration.
Do UK marketplaces need to be regulated to handle payments?
Not necessarily. If a marketplace holds or controls buyer funds, it may have payment-institution obligations under the Payment Services Regulations 2017. However, partnering with an FCA-authorised provider such as ONERWAY allows the marketplace to operate under regulated infrastructure without becoming authorised itself.
How do split payments and escrow work for a marketplace?
Split payments divide a buyer’s transaction between the seller’s earnings and the platform’s commission programmatically at the point of settlement. Escrow holds the buyer’s funds until a condition is met, such as confirmed delivery, before releasing the seller’s share. Both functions are handled automatically within the marketplace payout solution.
What is a marketplace payout solution?
A marketplace payout solution is infrastructure designed for paying many sellers in their local currencies on predictable schedules, using local clearing rails where possible. It differs from one-off supplier payments by supporting automated KYC onboarding, configurable disbursement timing and programmatic commission splitting at scale.
How do marketplaces pay sellers in different countries and currencies?
Through a payout platform with broad country and currency coverage, access to local clearing rails such as Faster Payments and SEPA, automated KYC and KYB onboarding for new sellers, and configurable scheduling, including instant, daily and milestone-based payouts, managed through a single API integration.
ONERWAY’s unified ecommerce payment platform is built for UK marketplaces, covering buyer-side acceptance, seller-side payouts, split payments and FX through a single FCA-licensed integration. If you are designing or re-platforming your marketplace payment stack, our UK team can map what a consolidated architecture looks like for your markets. Get in touch.
Resources
- Open Banking Implementation Entity: Open Banking in 2025: Now Part of the UK’s Everyday Financial Life
- OpenDue: FX Spreads and Hidden Cross-Border Payment Costs
- UK Government: The Payment Services Regulations 2017
- Financial Conduct Authority: Payment Services and Electronic Money: Our Approach
