Gaspard LEZIN
Merchant of Record UAE: A Practical Guide for Sellers
Merchant of Record UAE. Learn what a merchant of record in the UAE means, how VAT and licensing work, and how to evaluate MoR services
A founder signs a UAE customer, the contract is live, and the money still has nowhere sensible to go. The buyer wants a clean checkout, the finance team wants the right tax treatment, and legal wants to know who is responsible if the structure gets challenged. In the UAE, those are three separate problems, not one.
That's the mistake many teams make with merchant of record UAE discussions. They treat tax, licensing, and payout mechanics like a bundled service, then get surprised when the regulator, the tax file, or the bank account asks for different answers. The smarter approach is to separate the three layers, then decide whether a Merchant of Record, a local entity, or a hybrid setup fits the sale.
Table of Contents
Selling into UAE Cross-Border
A SaaS founder in Singapore lands a $40,000 annual contract with a UAE customer and thinks the job is done. It isn't. The work starts when someone has to decide who is the merchant, who files VAT, and where the money settles.
The three questions that matter
A UAE sale only looks simple at checkout. Under the surface, it splits into licensing, tax, and settlement, and each layer has its own rules.
The licensing question comes first. The UAE's payment framework got much clearer in July 2021 when the Central Bank issued the Retail Payment Services and Card Schemes Regulation, and it explicitly covers merchant acquiring, payment aggregation, domestic and cross-border fund transfers, and payment tokens. If your MoR controls checkout or settlement, you are operating inside that licensing environment. Central Bank of the UAE regulation
The VAT question sits beside it. In many cross-border digital sales, the customer sees one checkout amount, but the tax treatment depends on whether the buyer is a business or a consumer, and whether the supply is taxable in the UAE. If that classification is wrong, the refund process does not fix the underlying problem.
Then comes settlement. Founders often assume a card payment to a foreign entity can land in a normal USD account. In the UAE, that is often too simplistic. Local payout rails, AED reconciliation, and currency conversion all affect how cleanly the transaction closes, which is why payout design matters as much as checkout design. For a practical settlement overview, see the AED payout flow Suby documents for merchants.
Practical rule: if a UAE sale touches checkout, tax, and payout, treat each layer as a separate decision. If one of them is vague, the whole structure is weak.
What matters is who legally sells, who is tax-accountable, and where the money lands. That is the lens you need for the rest of this guide.
What a Merchant of Record Actually Means
A Merchant of Record is the legal seller in the transaction. Think of it as a resale model, the MoR buys the service from the underlying seller, then resells it to the end customer and becomes the buyer's counterparty. That's different from a payment facilitator, which mainly processes payments while the underlying merchant still owns the sale.
The rights an MoR actually takes on
An MoR normally assumes three core rights. It can invoice the customer, it can collect and remit VAT, and it can receive the gross payment before paying out the seller net of fees and tax obligations. That's the operational value of the model, not just “tax handled for you.”
A direct seller keeps the legal sale, the customer relationship, and the VAT filing burden. A payment facilitator sits in the middle of the payment flow, but that doesn't make it the legal seller. In UAE vendor marketing, those labels get blurred on purpose. They shouldn't be.
Dimension | Merchant of Record | Payment Facilitator | Direct Seller |
|---|---|---|---|
Legal seller | MoR | Seller remains the merchant | Seller remains the merchant |
VAT collection | MoR handles it | Usually seller's responsibility | Seller handles it |
Customer invoice | MoR issues or controls it | Seller issues it | Seller issues it |
Settlement model | Gross in, net out | Payment flow only | Funds go to seller |
Compliance exposure | MoR carries more of it | Shared, but seller still exposed | Seller carries most of it |
There's also a term problem. Some vendors talk about “reseller of record,” “seller of record,” and “merchant of record” as if they're interchangeable. They're not. In the UAE, the contractual chain matters because tax treatment and licensing obligations follow the structure, not the marketing copy.
An MoR is useful because it absorbs legal responsibility. That same feature is why you need to inspect the licence, the tax chain, and the settlement mechanics before you sign.
UAE Licensing and Payment Rules
The UAE doesn't treat payments as a casual back-office function. The Central Bank's payment regulation covers the core activities that matter to an MoR, and it explicitly names merchant acquiring and payment aggregation. If a provider wants to control checkout or settlement in the UAE, it needs the right licence category or a lawful operating structure under one. Central Bank payment regulation
What the licence question means in practice
A foreign seller can't assume a reseller agreement gives it a UAE payments licence. It doesn't. The licensed entity behind the MoR matters, and due diligence should start there, not with the checkout demo. If the provider can't name the licence category it operates under, the offer is incomplete.
The Central Bank framework also requires payment service providers to keep personal and payment data records for 5 years and comply with AML/CFT obligations. That tells you the compliance burden is real, not decorative. It also means any MoR pitch that ignores recordkeeping and fund controls is leaving out the part regulators care about most. Central Bank payment regulation
For operators, the practical distinction is simple. Category 1 style activity, including payment processing and merchant acquisition, sits closer to the full-stack checkout model. Lighter-touch arrangements may only cover a narrower function. If the MoR is taking payment, holding funds before payout, or reconciling settlement, you need to know which side of that line it sits on.
If you want a concise external reference on the bank-account side of UAE settlement, the BankStatementWizard Emirates NBD resource is useful because it shows how teams often organize bank evidence around local reconciliation. That matters when you're trying to prove that merchant inflows, payouts, and local settlement all line up.
Suby's payment-provider overview for the UAE is the kind of document I'd expect a serious seller to compare against any MoR pitch, because it forces the same question, who is licensed, and under what structure?
UAE VAT and Digital Services
A UAE digital sale is simple on paper and messy in practice. The rule is 5% VAT on most taxable electronic services, and non-resident suppliers are expected to register and charge VAT on consumer sales in the country. The hard part is not the rate, it is deciding who the customer is and where the service is used and enjoyed. UAE VAT guidance on digital services
B2B and B2C are not the same
For B2B flows, the reverse-charge mechanism can apply, which means the buyer may self-account for the tax instead of the seller collecting it at checkout. For B2C flows, the seller or MoR generally needs to collect the 5% at the point of sale. Your checkout architecture has to identify customer type before it finalizes the invoice.
Clean checkout does not make a sale compliant. The system has to classify the buyer, tag the invoice, and keep evidence that supports the tax treatment. If the service is electronic, the records matter as much as the payment.
What foreign sellers should care about
Foreign sellers need to test whether they have crossed AED 375,000 and should treat registration as a live issue. Once a seller is in scope, the operational burden shifts fast. The UAE tax authority's own guidance on digital services makes that point clear, and the registration check should be part of your launch process, not an afterthought.
Tax residency certificates are not a substitute for a proper TRN when the transaction needs one. If you are claiming that a sale is outside UAE VAT or zero-rated as an export, you need evidence. The place-of-supply analysis depends on where the service is used, not just where the contract was signed or paid.
Suby's VAT payment guide is worth reviewing if you are building a checkout that has to separate taxable from non-taxable flows without forcing the customer into a manual tax correction later.
Scenario | Tax treatment | Who collects VAT | Seller's exposure |
|---|---|---|---|
UAE B2C digital supply | Usually 5% VAT | MoR or seller at checkout | High if classification is wrong |
UAE B2B digital supply | Reverse charge may apply | Buyer self-accounts in many cases | Lower, but evidence still matters |
Cross-border electronic service used in UAE | Depends on place of supply | MoR or seller, depending on structure | High if records are weak |
Exported digital service | May be outside UAE VAT if evidence supports it | None in the UAE if properly treated | High if zero-rating is unsupported |
The VAT Chain in a UAE MoR Setup
A UAE MoR setup only works if the paperwork, licence status, and settlement flow line up. Before signing, inspect the provider's Central Bank licence category, validate their TRN, and review the settlement terms. Those three items decide whether the structure can survive an FTA review.
The invoice chain is where liability sits
A US SaaS company selling into the UAE through an MoR needs a clean contract chain. The underlying seller invoices the MoR at the base price, then the MoR invoices the UAE customer at checkout with the correct VAT treatment. That customer-facing invoice is the one auditors will focus on.
A sloppy reseller agreement creates real risk. If the original seller still looks like the legal counterparty on the documents, VAT exposure can stick to the wrong entity even if the checkout flow says otherwise. Contract language and money movement need to tell the same story.
If your team also needs a clear explanation of the buyer-side mechanics, the Escrow Consulting Group VAT guide is a useful reference on how reverse charge treatment changes the VAT obligation.
What auditors usually care about
FTA review requests usually come back to three items, the contract chain, the invoice trail, and proof that the VAT treatment was correct. Refunds and currency conversion sit in the same chain because they change the net amount the MoR keeps and the amount it remits. Weak records here make the defence easy to challenge.
Operator takeaway: in a MoR setup, margin, VAT, refunds, and FX sit in one accounting story. Separate them too early, and you make the audit trail harder than it needs to be.
Pros, Cons and Common UAE Use Cases
The appeal of an MoR in the UAE is obvious. It can get you into market faster, spare you from setting up a local entity on day one, and take a large part of VAT administration off your team. It also helps when you want a cleaner settlement model across currencies and don't want every market to require its own payment stack.
Where the model helps
For a cross-border seller, the biggest upside is speed. You can test demand in the UAE without building local infrastructure first, and that matters when the market is active but your internal team is small. The UAE e-commerce market jumped by 53% in 2020 to $3.9 billion in sales, equal to 10% of total retail sales, which is why sellers keep paying attention to it. U.S. International Trade Administration UAE e-commerce report
A second advantage is that the MoR can centralize customer billing, VAT handling, and settlement logic. That keeps finance from juggling separate tax workflows for every region. It's also a better fit when the product is digital and the billing motion is repeatable.
Where the model hurts
The downside is cost and control. MoR fees usually compress margin, and sellers give up part of the direct customer relationship. Refund handling and dispute handling can also be narrower than what a direct seller would want. If the provider changes its risk appetite, your deplatforming risk becomes real.
Who should use it
SaaS and software teams, especially if they sell cross-border subscriptions and don't want to build a UAE tax stack first.
Digital product sellers, when the main need is fast international checkout and a simpler compliance path.
Online communities and gated content businesses, when the sale is tied to access rather than physical delivery.
B2B platforms, only if the invoicing and buyer classification logic is strong enough to survive a real tax review.
If you're looking at a tool rather than a legal structure, Suby is one option to review because it offers card and crypto acceptance through one API, plus native integrations with Discord and Telegram for paid access use cases. I'd still compare any such tool against your licensing and VAT requirements first.
Practical Checklist and Next Steps
Don't sign a UAE MoR contract until you've checked the boring parts. That's where the risk lives. A polished checkout demo tells you almost nothing about whether the provider is licensed, whether the VAT chain is clean, or whether your payouts will reconcile without a mess.
What to verify before you commit
Confirm the licence. Ask which Central Bank category the provider operates under, and don't accept a free-zone trade licence as a substitute.
Check the tax identity. Validate the provider's TRN and confirm how VAT appears on the customer invoice.
Review settlement terms. You need to know whether funds land in AED, USD, or another currency, and what FX margin applies.
Read the payout cadence. Settlement timing, refund windows, and chargeback handling should all be in the contract.
Inspect the exit terms. If you later move to a direct seller model, you need a clean termination path and data handover language.
The parts most teams forget
Data handling is one of them. The UAE's payment rulebook requires long record retention, and contract language should also address how customer data is handled if the relationship ends. You should ask the provider how it handles disputes, what evidence it will provide if the FTA asks questions, and whether the operational model still works if your market mix changes.
A simple legal read before signing can save days of back-and-forth. If you want a practical way to sanity-check contract language before a lawyer redlines it, the AI legal assistant for business owners can help you organize the questions you should be asking.
Shortlist two licensed MoR providers, request sandbox access or test invoices, and run one B2B and one B2C checkout before you decide. Compare the net proceeds, the VAT handling, and the payout path against a local entity model. Then choose the structure that gives you the least regulatory ambiguity, not the prettiest sales pitch.
If you're evaluating a payments stack for UAE sales, Suby lets businesses accept card or crypto through one API, and it also supports native integrations with Discord and Telegram for subscriptions, paid access, and online communities. Visit Suby if you want to compare how one product can handle customer payment choice while still giving the business control over settlement.
