Accepting Online Payments at Your Café in the UAE

Two very different models — and the difference is your money

If you want customers to pay online, you'll meet two arrangements. They look similar from the outside and behave very differently when something goes wrong.

The platform collects, then pays you. The ordering platform is the merchant. Customers pay the platform. The platform takes a commission and transfers what's left to you — weekly, fortnightly, on their schedule. This is how most delivery apps work.

You collect directly. You have your own merchant account with a payment gateway. The ordering system simply sends the customer to your gateway. The money goes from the customer to your account. The software never touches it.

The second is better for a café, for reasons that only become obvious later:

You're not waiting on someone else's payout schedule. Your cash flow is your own. There's no commission skimmed per order beyond what your gateway charges. If you stop using the software, your payment arrangement isn't affected. And if the platform has a bad month — or disappears — your money isn't sitting inside it.

The trade-off is that you have to set up your own gateway, which takes some paperwork. It's a one-time cost for a permanent advantage.

What you need to accept card payments in the UAE

Realistically, three things:

A licensed business. A payment gateway will ask for your trade licence. This is non-negotiable — you can't take card payments as an unregistered business.

A bank account in the business's name. Settlements go here. The gateway will verify that the account and the licence match.

A payment gateway account. In the UAE the common options include PayTabs, Telr, and Network International, along with the banks' own offerings. They differ on fees, settlement speed, and how much setup they require.

Expect the application to ask for the trade licence, the bank IBAN in the business name, and identification for the owner (passport and Emirates ID, plus residence visa if you're not a national). Approval isn't instant — plan for days, not minutes.

How the payment actually flows

Worth understanding, because it explains why a good setup is safer than it sounds:

The customer finishes their order and chooses to pay by card. Instead of typing their card number into your website, they're sent to the gateway's own secure payment page. They enter their card there. The bank may ask them to confirm with an OTP — this is standard in the UAE and is handled entirely by the gateway.

When the payment succeeds, the gateway notifies your ordering system directly, server to server. Only then is the order marked paid. The customer comes back to a confirmation page.

The important detail: card numbers never touch your system. They go straight to the gateway. That's not just convenient — it's what keeps you out of the heaviest card-security compliance obligations. Any ordering system that asks customers to type card details into its own form should make you cautious.

The part most people get wrong

Ask one specific question of any ordering system: how does the order get marked as paid?

The right answer is "the gateway tells our server directly." The wrong answer is "when the customer returns to the site."

The reason: customers close browsers. Their phone loses signal on the way back. If the system marks an order paid only when the customer's browser returns, then a successful payment can be lost, and a clever customer could fake a return. Server-to-server confirmation is the only trustworthy version.

You don't need to build anything for this — but knowing to ask is how you avoid a system that gets it wrong.

Should you offer cash as well?

Yes. Cash on delivery is normal in the UAE and some customers prefer it — for delivery and car-side especially. Offering both is not a compromise; it's just meeting people where they are.

What matters is that your staff can tell at a glance which is which. An order that's already paid and an order that needs collecting cash should look different on the screen, or someone will eventually ask a customer to pay twice.

Fees, and what to compare

Gateways charge per transaction — typically a percentage plus a small fixed amount, and sometimes a setup or monthly fee. When comparing, look past the headline rate at:

• Settlement time (how many days until the money is in your account)
• Whether there's a monthly minimum
• Whether refunds cost you anything
• Whether digital wallets (Apple Pay, Google Pay, Samsung Pay) are included

That last point is worth weighting. A significant share of UAE customers will pay by wallet if it's offered — it's faster than typing a card number on a phone, and it noticeably reduces abandoned checkouts.

Common questions

Do I need a trade licence just to take online orders? For cash orders, no. To accept card payments, yes — the gateway requires it.

How long until the money reaches me? Depends on the gateway; commonly a few working days. Ask before signing up.

Can I test before going live? Any decent gateway offers a sandbox with test cards, so the whole flow can be tried with no real money.

What about Apple Pay? Usually supported through the gateway, often needing a domain verification step. It appears as an option on the payment page rather than as separate software.

Is it safe to take payments if I'm a small café? Yes — because with hosted payment pages, you're not storing card details. The gateway handles the sensitive part.