Cross-border payroll from the Gulf: a flow-of-funds walkthrough
Lukasz Dec
Co-founder and Chief Executive Officer

Stablecoin payroll is one of the most-cited use cases in the industry and one of the least precisely described. In the Gulf it is also one of the most misunderstood, because the region's domestic payroll is among the most tightly regulated in the world - the UAE has required electronic, dirham-denominated salary payment through approved institutions since 2009, and every other GCC state runs a version of the same system. So let's be precise. This piece separates the payroll flows that can lawfully run on stablecoin rails from those that can't, and walks through - step by step - how the money moves for the ones that can.
First, what stablecoin payroll is not (in the Gulf)
It is not replacing domestic salaries. The UAE's Wage Protection System (WPS) requires private-sector employers to pay wages electronically, in dirhams, through banks and exchange houses approved by the central bank, with each transfer reported to the labour ministry; Saudi Arabia, Qatar, Kuwait, Oman and Bahrain operate parallel systems. This is deliberate policy protecting a workforce that is overwhelmingly expatriate - around nine in ten private-sector employees in the UAE - and it is not going anywhere. A UAE employee's salary is a WPS transaction, and under the PTSR domestic payment in anything other than dirhams - or licensed dirham tokens through the proper channels - isn't on the table.
Any vendor telling a Gulf employer to "pay staff in USDT" is selling a compliance problem.
What it is: the three flows that qualify
Where stablecoin rails genuinely fit is the money that leaves the Gulf to pay people who aren't on a local payroll:
1. Foreign contractors and freelancers. A Dubai company paying a designer in Lisbon, a developer in Singapore, or an agency in Manila is not making a WPS payment, it's making a cross-border commercial payment to a non-employee. Today that runs on correspondent banking or a payout provider; it can run on stablecoin rails.
2. Distributed remote teams employed abroad. Staff employed through a foreign entity or an employer-of-record are paid by that entity, in that country. The Gulf parent's job is to fund the foreign payroll - a treasury transfer, not a salary - and that transfer is exactly the flow stablecoins compress.
3. Subsidiary and inter-company funding. A GCC group funding its Egyptian, Turkish, or European operating company's payroll account each month is moving working capital across borders. It's a treasury flow with a payroll deadline attached, and deadlines are where correspondent banking's 2–5 days hurt most.
All three share a shape: the Gulf leg is a business paying out; the destination leg lands in a bank account or a locally regulated wallet. That shape is what the flow-of-funds is built around.
The flow of funds, step by step
Take the archetype: a UAE company funding a monthly contractor payout to a team spread across Europe and Singapore - both regulated endpoints - through a licensed settlement layer.
Step | What happens | Where the money is | Compliance touchpoint |
|---|---|---|---|
1. Fund | Company transfers AED from its bank account to the settlement provider's safeguarded client account | Fiat, UAE bank | KYB on the company; source-of-funds; the transfer is an ordinary domestic bank payment |
2. Convert | AED is converted to the settlement token - dirham token where the corridor supports it, or the appropriate currency token | Licensed conversion perimeter | Payment token conversion under licence; sanctions screening; transaction monitoring |
3. Move | Tokens transfer on-chain to the destination-side conversion point - minutes, not days, with an auditable trail | On-chain, in transit | Travel Rule data attached; wallet screening on both sides |
4. Convert out | Tokens are converted to EUR / SGD at the destination-side licensed partner | Fiat, destination | Destination-side licensing (MiCA / MAS); beneficiary KYC via the payout partner |
5. Pay out | Funds land in each contractor's bank account or regulated local wallet in local currency | Recipient's account | Local payout regulation; the recipient never touches a token unless they choose to |
Two things to notice. First, the contractor receives euros or Singapore dollars in a bank account - stablecoins are the transport layer, invisible to the person being paid. That's the version that works at scale; the "everyone gets a wallet" version is a niche. Second, every step has a licence attached to it. Steps 2 and 3 are precisely the payment-token conversion and custody & transfer activities the UAE licenses; step 4 is the destination regime's. A flow with a gap in that chain isn't a stablecoin payroll product - it's an unlicensed one.
What changes for the finance team
Correspondent banking | Stablecoin rails (licensed) | |
|---|---|---|
Settlement time | 2–5 business days; cut-offs and weekends | Minutes to hours; 24/7 |
Cost structure | Layered intermediary fees + FX spread; retail benchmarks above 6%, wholesale lower but opaque | Conversion spread + provider fee; one or two legs, visible |
Visibility | Opaque until arrival | On-chain trail per payment |
Batching | Batch by cut-off | Continuous; pay when due |
FX exposure | Often two conversions (via USD) | One where direct pairs exist; dollar leg minimized as depth grows |
Reconciliation | Bank statements, days later | Per-transaction references, immediately |
The honest constraints
Three, and they decide the corridors:
Destination regulation. The flow works where the destination side has a licensed way to convert tokens to local currency and pay out - Europe, Singapore, and a growing list. Where it doesn't, the destination leg reverts to fiat and the stablecoin rail stops at the last regulated point. That is why corridor-by-corridor analysis matters more than corridor-agnostic enthusiasm - and why we won't describe flows into markets without stablecoin regulation.
Employment classification. Whether someone is a contractor, an EOR-employed worker, or a foreign-subsidiary employee is a labour-law question in their country, not a payments question. Stablecoin rails don't change classification; get it right first.
Liquidity at size. A payroll run is a large, deadline-bound ticket in a possibly thin pair. Depth and routing - not chain speed - determine whether it clears cleanly.
Get those three right and payroll becomes what it should have always been: a treasury flow that lands when it's due, at a cost the finance team can see. That's the settlement problem, not a crypto problem - and it's ours.
Frequently asked questions
Can a UAE company pay employees in stablecoins?
Not for domestic salaries. UAE private-sector wages must be paid in dirhams through the Wage Protection System via approved institutions. Stablecoin rails apply to cross-border payments to foreign contractors, funding of foreign payrolls, and inter-company transfers.
Is stablecoin payroll legal in the UAE?
Cross-border payouts using licensed conversion and custody & transfer services are within the PTSR perimeter; domestic salary payment is governed by the WPS. The legality question is really a licensing question at each step of the flow.
Does the contractor need a crypto wallet?
No. In a licensed flow the recipient receives local currency in a bank account or regulated local wallet; stablecoins are the transport layer between the two fiat endpoints.
How much faster is stablecoin payroll?
Cross-border settlement compresses from 2–5 business days to minutes or hours, available 24/7, with per-transaction traceability - provided both endpoints are regulated and the pairs are liquid enough for the ticket size.
Which countries can Gulf companies pay into on stablecoin rails?
Those with a licensed destination-side conversion and payout path - Europe under MiCA, Singapore under MAS, and a growing list. Where the destination lacks stablecoin regulation, the token leg ends at the last regulated point and fiat completes the journey.
