The Legal Architecture of Marketplace Platforms: Part 2: How Payment Architecture Becomes a Legal Control Mechanism in the UAE
Here is a scenario every marketplace platform in the region eventually faces. A transaction goes wrong. A buyer disputes the charge and demands a refund. By the time anyone with authority to resolve the dispute actually looks at it, the money has already moved — released in full to the seller, no longer within reach. On a different platform, facing an identical dispute, the funds are still sitting, held, awaiting review.
Same dispute. Two different outcomes. The difference has nothing to do with what either platform's terms of service say — it comes down to how each platform designed its payment flow, and whether UAE payment regulation permits it to hold funds at all.
This is the second article in our series on the legal architecture of marketplace platforms operating in the UAE and Lebanon. Part 1 looked at why platform liability follows conduct rather than contract language. This part looks at a specific and underexamined form of that conduct: control over the movement of money.
Payment as a Legal Lever, Not a Finance Function
Founders default to treating payment processing as operational plumbing — pick a licensed processor, configure the integration, move on. In the UAE, that instinct is a structural mistake with regulatory consequences attached. The design choices sitting inside the payment layer — who holds funds, for how long, and under what conditions they are released — set the terms of legal leverage well before any dispute clause is ever invoked. Hand those decisions to a product or engineering team with no legal input, and a platform has allocated liability without realising it has done so.
The UAE's Payment Regulatory Framework
Control over payment flow in the UAE is not a purely contractual matter — it sits inside a licensing regime administered by the Central Bank of the UAE (CBUAE). Two regulations matter most for marketplace platforms:
The Stored Value Facilities (SVF) Regulation, issued by the CBUAE in November 2020, governs facilities where a customer pays money to an issuer in exchange for the storage of that value — the regulatory category that captures many in-app wallets and prepaid balances used on marketplace and gaming platforms.
The Retail Payment Services and Card Schemes (RPSCS) Regulation, issued by the CBUAE in July 2021, establishes the licensing framework for retail payment services across nine defined categories, including payment account issuance, merchant acquiring, and payment aggregation. No person may provide these services in the UAE without the relevant CBUAE licence, other than banks and licensed finance companies operating under specific conditions.
The practical implication for marketplace platforms is direct: a platform that holds buyer funds, operates an internal wallet, or controls when and whether a seller gets paid is very likely performing a function this framework regulates — regardless of whether the platform describes itself as a payments business. Structuring a payment flow without asking whether it triggers an SVF or RPSCS licensing requirement is one of the more common — and more expensive — mistakes we see in early-stage platform builds.
Where Liability Attaches in Payment Flows
The exposure differs sharply depending on the structural choices built into the flow:
Custody versus pass-through changes the platform's regulatory and liability position outright. A platform that never takes custody of funds sits in a materially different position from one that holds them, even briefly, in an omnibus or wallet account.
Timing of release is often the whole game. Release funds to a seller immediately, and the platform's practical ability to intervene in a dispute disappears with the money. Delay release, and that ability survives — at the cost of seller liquidity and, in the UAE, potential SVF/RPSCS licensing implications depending on how long and under what conditions funds are held.
Reliance on a third-party processor does not make exposure disappear — it relocates it, and can obscure exactly where control sits if the platform's own terms still grant it a unilateral right to instruct refunds or holdbacks.
There is no universal template here. Each design choice reallocates risk differently between platform, seller, and buyer, and each should be made deliberately — with legal input, not simply inherited from whatever a payment processor ships by default.
Withholding Rights as Structural Power
Few elements of platform design carry as much practical consequence, and receive as little scrutiny, as the ability to withhold funds. Withholding enables dispute management — the practical ability to pause disbursement while an investigation runs, instead of relying purely on recovery after the fact. It also gives suspension and investigation rights actual teeth, rather than leaving them as language in a terms-of-service document with no operational counterpart.
Strip out the ability to withhold, and a platform's practical control over disputes shrinks dramatically — whatever its terms of service claim. This connects directly to the recharacterization risk discussed in Part 1: the same operational facts that establish payment control tend to establish control over the transaction itself.
The E-Commerce Law's Payment-Adjacent Consumer Rights
Federal Decree-Law No. 14 of 2023 on Trading by Modern Technological Means, the UAE's core e-commerce statute, intersects with payment design in a way platforms often overlook. It gives UAE courts jurisdiction over disputes arising from digital contracts, while permitting arbitration where the parties have agreed to it — subject to a threshold restriction: a digital contract worth less than AED 50,000 cannot carry a mandatory arbitration clause. For a high-volume, low-average-order-value marketplace, this means a meaningful share of disputes will default to court jurisdiction regardless of what the platform's terms specify, which should inform how aggressively a platform relies on holdback and offset rights as its primary practical remedy rather than litigation.
Settlement Timing and Leverage
Timing decides who is holding the risk during the window a dispute might open. Immediate payout hands that risk to the platform, or to whoever is left chasing recovery once the money is already gone. Delayed settlement keeps the platform's ability to intervene alive, at the cost of friction and seller liquidity. Rolling reserves — a portion of each seller's proceeds held back on an ongoing basis — provide a continuous buffer rather than a one-off window. Conditional release, tied to delivery confirmation or a defined dispute period, aligns settlement timing with the transaction's actual risk profile.
None of these is the universally "correct" answer. Each is a different allocation of risk between platform, seller, and buyer, and the right structure depends on the platform's specific model, its regulatory posture under CBUAE rules, and the categories of goods or services it carries.
Payment Architecture Versus Contractual Rights
This is where otherwise carefully drafted marketplace agreements fall apart in practice. A right to recover funds, to charge back, to enforce an indemnity clause of the kind discussed in Part 4 of this series — none of it is worth more than the platform's actual ability to retain or redirect the money in question. A strong indemnity clause with no holdback mechanism, and a seller already paid in full, leaves a legal right that is real but often not worth pursuing: the cost of enforcement can exceed what is recoverable, particularly if the counterparty is judgment-proof in any practical sense. Legal rights without control of funds are, more often than platform founders like to admit, economically irrelevant.
Currency and Cross-Border Complexity for Lebanon-Linked Platforms
Payment structuring for platforms operating in or through Lebanon carries an additional layer of complexity that UAE-only platforms do not face to the same degree. Since 2019, Lebanon's banking sector has operated under informal capital and currency restrictions that materially affect how quickly funds can move, and in what currency. A marketplace settlement structure built only for a stable single-currency environment is poorly suited to a model that needs to survive currency volatility or restricted convertibility. Platforms with a Lebanon leg to their operations should design settlement timing and reserve structures with this instability treated as the baseline assumption, not an edge case.
Practical Design Choices for MENA Platforms
For founders building a marketplace, escrow-style, or wallet-based platform in the region, the design sequence should run: confirm whether the intended payment flow triggers CBUAE SVF or RPSCS licensing; decide custody versus pass-through deliberately, with legal and product input together; align settlement timing (immediate, delayed, rolling reserve, or conditional) with the platform's actual dispute profile; and build any withholding or offset right into both the payment architecture and the underlying contract, since a right that exists only in the contract and not in the payment flow is not a functioning remedy.
Frequently Asked Questions
Does a UAE marketplace platform need a Central Bank licence to hold buyer funds? Often, yes. Holding customer funds, even briefly, in a wallet or omnibus account can bring a platform within the Stored Value Facilities Regulation or the Retail Payment Services and Card Schemes Regulation, both administered by the Central Bank of the UAE. Whether a specific flow triggers licensing depends on its structure and should be assessed before launch, not after.
Can a UAE marketplace platform withhold a seller's payout during a dispute? It depends on how the payment flow and the underlying contract are structured together. A withholding right written only into the terms of service, with no corresponding mechanism in the payment flow, is difficult to exercise in practice once funds have already settled to the seller.
How does Lebanon's currency situation affect marketplace payment design? Since 2019, informal capital and currency restrictions in Lebanon's banking sector have made stable-currency assumptions unreliable for platforms with a Lebanon-facing payment leg. Settlement structures should be built to anticipate currency volatility and convertibility constraints rather than assume a single, stable unit of account throughout the transaction lifecycle.
Looking Ahead
Payment control is one form of operational control — but it is not the only one, and it is often not the most visible. Part 3 of this series turns to a broader question: how control across the full transaction lifecycle, not just the payment layer, determines whether a business is legally treated as a platform or as an operator under UAE law.
DISCLAIMER: This article is for general informational purposes only and reflects our understanding of the law as of the date of publication. It does not constitute legal advice and should not be relied upon as a substitute for advice tailored to your specific circumstances.