Ask anyone planning an online store in Dubai what they care about and you'll hear design, product photos, delivery. The payment gateway — the thing that actually moves money from your customer to your bank — usually comes up in week three, after the checkout is built. That's backwards. The gateway shapes your checkout flow, your cashflow, and more of your code than you'd expect. Choose it first.

How gateway fees work in the UAE

Every gateway operating here prices roughly the same way, in three layers. The numbers vary by provider and by what you negotiate; the structure doesn't.

  1. Setup and account fees. Some charge a one-time onboarding fee, some an annual fee, some nothing upfront but more per transaction. "Free setup" is never free — it's recovered somewhere else.
  2. Per-transaction fees. A percentage of each sale, often plus a small fixed amount per transaction, and the rate usually differs for local versus international cards. Model this against your average order value: a fixed fee stings when you sell AED 60 accessories, a percentage stings when you sell AED 6,000 furniture.
  3. Settlement. Money doesn't land in your bank the moment a customer pays. Gateways hold funds for a settlement period — days, not hours — and some add minimum payout thresholds. If you're funding inventory from sales, that delay is a cashflow decision, not a footnote.

Read the fine print on refunds and chargebacks too. Many gateways keep the transaction fee even when you refund an order, and chargebacks carry penalties of their own. Put it all in a spreadsheet before you sign, not after your first statement surprises you.

Cash on delivery is still not optional

If you're selling to the UAE or the wider GCC and your checkout only takes cards, you're turning away real orders. Cash on delivery has been part of this region's e-commerce culture from the start, for a rational reason: first-time customers don't trust a store they've never bought from. COD lets them try you at zero risk. Earn the trust, and the second order often goes on a card.

But COD is not "just another payment option" from a build perspective. It carries real costs — failed deliveries, returns, courier cash-handling fees — so a well-built store treats it as a rules engine, not a checkbox:

  • Cap it by order value, so an AED 8,000 basket can't ship on a promise.
  • Restrict it by area if your courier only handles cash in certain emirates.
  • If you charge a COD fee, calculate it at checkout — not in an argument at the door.

And if you serve Arabic-speaking customers — in the UAE, you do — the whole payment flow needs to read correctly in Arabic. A bilingual EN/AR checkout with proper RTL isn't decoration; it's the difference between a finished order and a customer messaging you to place it manually.

The takeaway: the gateway is a build decision, not a plugin you bolt on at the end. Pick it before development starts — swapping gateways inside a finished checkout is where e-commerce budgets and timelines quietly die.

What goes wrong when the site wasn't built for it

Most store horror stories aren't design problems. They're payment problems, and they trace back to a build that treated the gateway as an afterthought:

  • The redirect that kills trust. The customer clicks pay and lands on a gateway-hosted page that looks nothing like your store — different fonts, no Arabic. Some of them just close the tab.
  • Orders and money disagreeing. The gateway confirms payment via a webhook; the site never handles it. Now paid orders sit marked pending, and a spreadsheet replaces your order system.
  • Refunds done in two places. Support refunds the customer in the gateway dashboard, the store never finds out, and inventory and reports drift away from the truth.
  • A slow checkout stacked on card verification. UAE card payments routinely add a 3-D Secure step. That's fine on a fast site and fatal on a slow one — we covered the speed side in Core Web Vitals for GCC e-commerce.

Every one of these is cheap to prevent during the build and expensive to fix after launch.

Questions to ask before you sign

Two contracts matter: the one with the gateway and the one with your developer. Ask the gateway:

  • What do I actually pay on my average order — local card, international card, refunded order?
  • How long is settlement, and is there a minimum payout?
  • Do you settle in AED to a UAE bank account, or is there a currency conversion in the middle?

Then ask your developer:

  • Which gateways have you integrated before, and is mine named in the written scope?
  • Who owns the gateway account? (You. Always you — same as your domain.)
  • What happens when a webhook fails — retry, alert, or silently lost order?
  • Is COD included with rules, or is it "we can add that later"?

If they can't answer quickly, they're going to learn on your project.

Where this fits your build

At Shapes Infinity the gateway conversation happens in week one, because everything downstream depends on it. Scope, timeline and price go in writing before work starts, you pay 30% to begin and 70% on completion, and launch comes with a year of free bug fixes — which covers your payment integration too. E-commerce builds start at AED 5,999 and ship in 2–4 weeks.

Pricing a store right now? Get an instant quote — see your price in under a minute — or message us on WhatsApp and tell us which gateway you're considering. We'd rather talk you out of the wrong one before it's in your contract.