# Dubai Pay: what the government gateway actually is, and who needs it
Dubai Pay is the Government of Dubai's own payment gateway, run as a shared service so that residents, visitors and companies can pay government fees online. DEWA bills, Dubai Municipality charges, licence-related fees, fines. Money moves one direction through it: from you into a government entity's account. There is no merchant sign-up, no settlement into your company IBAN, and no checkout module you can drop onto your Shopify store.
If you landed here because you want to take card payments from customers, Dubai Pay is the wrong door. You need a commercial gateway. Reported UAE rates sit between roughly 2.49% and 3.5% of the transaction plus a fixed fee of AED 0.50 to AED 1, and every provider will ask for a trade licence and a corporate bank account in the same legal name before switching you on.
We collect payments for a Dubai studio group through a commercial gateway wired into WhatsApp and a CRM, and we pay our own government fees through the DubaiPay rails like everyone else. The two systems have never touched each other.
What Dubai Pay actually is
DubaiPay is described by Digital Dubai as a Dubai Government-owned and operated payment gateway, offered as a shared service to government entities and service providers. It carries PCI DSS Level 1 certification, held since 2014, and ISO 27001 compliance.
It started life in 2003 under the name ePay, launched by what was then Dubai eGovernment and later Smart Dubai Government Establishment. The rebrand to DubaiPay came with the wider Digital Dubai consolidation. Dubai's Department of Finance sits over the payment side of it, which is why announcements about new payment methods come from Dubai Finance rather than from a commercial processor.
Scale, in the figures that have been published: DubaiPay collected around AED 13 billion across 9.4 million transactions in 2017, roughly a 17% rise on the prior year, with more than 40 entities connected at the time, split between government and non-government service providers. Newer totals do not appear to be published in the same format, so treat the 2017 figures as the last clean public benchmark rather than today's number.
How it works: entities, services and channels
A government entity integrates with DubaiPay once, and then exposes its fees through whichever channel the customer prefers. Digital Dubai lists websites, mobile, and physical kiosks as the supported channels. Practically, that means you might pay the same fee from a department's own portal, from a smart app, or from a machine in a service centre, and the transaction lands in the same place.
On methods, Digital Dubai's own service page lists credit card, net banking, the noqodi wallet, and Apple Pay. That list has widened. On 28 October 2025 Dubai Finance announced activation of a broad set of global and regional digital wallets for government service fees across all Government of Dubai entities, naming Apple Pay, Samsung Pay, Google Pay, Alipay and Alipay+, RuPay, Diners, Discover, China UnionPay, WeChat Pay, NPCI QR (UPI), and SoftPOS or tap-to-pay. Tabby has also been integrated as a payment option, which puts a buy-now-pay-later product on government fees.
What you will not find anywhere in that stack is a merchant application form. The integration path runs through Digital Dubai's partner portal and is open to government entities and approved service providers, not to a business that wants to sell trainers online.
Dubai Pay vs DubaiNow: they are not the same thing
DubaiNow is the app. Dubai Pay is the payment layer underneath it, and underneath dozens of other government front ends.
DubaiNow gives residents one place to reach government services: bill payments, transport, health, housing, and so on. Published service counts vary by page and by date, running from "more than 250 services from over 35 entities" on some official listings to "over 320 services from 50+ entities" on others, with a further 180 services announced for addition by the end of February 2027. That inconsistency is normal for a platform that adds integrations continuously. Take any single count as a snapshot.
The relationship is simple. You browse and trigger the service in DubaiNow or on an entity's own site, and when the fee is charged, DubaiPay processes it. Deleting the app would not remove the gateway. Neither one gives a private company a way to collect from its own customers.
Who Dubai Pay is genuinely for
Two groups.
Government and semi-government entities in Dubai use it as their collection infrastructure. They avoid building and certifying a gateway each, and they inherit the PCI DSS Level 1 posture and the wallet coverage centrally. That is the correct use of the platform.
Businesses use it as payers. Your operations manager renewing a licence, settling a municipality fee, or clearing a DEWA bill for the office is using Dubai Pay whether or not anyone in the company knows its name. That is the entire extent of a private company's relationship with it. The receipt matters to your bookkeeping, and the payment itself belongs in your expense records like any other outgoing.
If your interest in Dubai Pay is "how do I get paid faster by clients", nothing in the platform touches that problem.
Who needs a commercial merchant gateway
Anyone taking money from customers. A clinic charging for consultations, a studio taking booking deposits, an e-commerce store, a consultancy invoicing retainers, a gym running monthly memberships.
The commercial gateway sits between the card networks and your bank account. It authorises the card, carries the merchant of record relationship or passes it to an acquirer, holds funds through settlement, and then pays out to your IBAN. It also handles the parts nobody enjoys: refunds, chargebacks, recurring billing, and payment links you can send into a chat.
Our comparison of UAE gateways by fee model goes deeper on choosing between them. The short version sits in the table below.
Dubai Pay vs the commercial gateways, side by side
| Platform | Direction of money | Reported rate | Settlement to your bank | Can a private business sign up | |---|---|---|---|---| | Dubai Pay | Payer into a Dubai government entity | No merchant rate published; the payer sees the fee | Not applicable | No | | PayTabs | Customer into your business | ~2.85–2.9% + AED 1 | T+1 local debit, T+3 cards, up to T+5 by category | Yes | | Telr | Customer into your business | ~2.49–2.69% + AED 0.50, Pro plan ~AED 99/mo | T+3 to T+5 typical | Yes | | Network International | Customer into your business | Negotiated, roughly 1.9–3.5%; often ~2.4–2.9% + AED 1 for new merchants | Around T+5 | Yes, heavier underwriting | | Stripe | Customer into your business | ~2.9% + a fixed fee reported between AED 1 and AED 2 | Rolling payouts, slower on a new account under review | Yes | | Checkout.com | Customer into your business | Enterprise, no public rate card | Negotiated | Volume-dependent |
Every commercial figure above is a reported band, not a quote. UAE gateway pricing moves with your monthly volume, your merchant category, and how hard you push during onboarding. International cards, Amex and cross-currency transactions price above the domestic band at every provider on that list, so pull one real month of transactions and calculate your blended rate before you compare anyone.
What you actually need to open a commercial gateway
The onboarding is a bank KYC process wearing a payment company's branding. The acquirer carries the risk if the business turns out to be something other than what it claimed.
| Requirement | Detail | Where it usually breaks | |---|---|---| | Valid trade licence | Current, showing the activity you genuinely sell | Licence says consultancy, website sells supplements | | Corporate bank account | UAE account, same legal name as the licence, with IBAN | Account name differs from entity name, payout fails later | | Signatory documents | Emirates ID, passport, residence visa page for signatory and beneficial owners | Expired visa stops the file dead | | Live website or app | Visible pricing, refund policy, delivery terms, contact details | Placeholder pages submitted before launch | | Constitutional documents | MOA and Articles, or free zone equivalent | Old version that predates a shareholding change |
Timelines, realistically: the corporate bank account is the slow part, commonly quoted at two to four weeks for a clean file and longer where ownership is complex. Gateway approval on top of that runs about three to five working days for a straightforward SMB application. Technical integration is the fast bit, usually 24 to 48 hours once credentials land.
Where getting paid meets WhatsApp and the CRM
Here is the gap I see in almost every Dubai SME that has already solved the gateway question. The gateway collects fine. The business around it still moves by hand.
Someone opens the processor dashboard in the morning, matches payments against orders, updates the CRM, and forwards receipts. A customer asks to pay at 22:40 on a Friday and waits until Sunday for a link, by which point the intent has cooled. A client who paid two days ago still gets chased by an automated follow-up because nothing told the sequence to stop.
What closes it is unglamorous. A payment link generated by API with amount and reference pre-filled, so it can be issued the second the customer asks. An agent that posts it into the same thread, which is what our WhatsApp sales agent does, including the nudge when the link goes unopened. A status webhook, caught and verified, that flips the deal to paid, timestamps it, and stops every sequence pointed at that contact.
Wiring one process end to end like that runs from AED 6,000 to build and AED 1,200 a month to keep running on our automation setup. If you want to see where your own enquiry-to-payment flow stops moving on its own, a growth audit starts at AED 3,000 and maps it against your actual chat and CRM history.
