Magento UAE: Payment Gateways, VAT & RTL Checklist

If you are running Magento (Adobe Commerce) for the UAE or the wider GCC, five things decide whether the store actually converts locally: regional payment gateways and BNPL, courier integrations that reach the last mile here, an Arabic storefront that mirrors correctly, multi-currency across markets, and 5% UAE VAT with FTA-compliant invoices. A generic international build gets each of these subtly wrong, and every mistake shows up as an abandoned cart, a failed delivery, or an incorrect VAT return. Here is what each area needs in practice, the pitfalls I see most, and why these are exactly the checks in a Dubai-based Magento audit.

Payment gateways UAE shoppers expect

International merchants ship with Stripe or PayPal and wonder why conversion is flat. Local shoppers pay with local rails: cards processed by a regional acquirer, GCC debit, and increasingly buy-now-pay-later. The providers that matter here:

• Telr and PayTabs - full card gateways with local acquiring and multi-currency; a good default when you sell across several GCC countries.
• Network International (N-Genius) - a UAE acquirer, so for a UAE-domiciled merchant it is often the shortest and cheapest processing hop.
• Tabby and Tamara - the two dominant BNPL providers. In this market BNPL is not a nice-to-have; a meaningful share of shoppers expect it and it lifts basket size.

Practical guidance: run at least one card gateway plus one BNPL, keep each module on the vendor's official Magento 2 extension (not a community fork), and test the full 3-D Secure flow on a real UAE-issued card. Common pitfalls: leaving PayPal as the primary method, hard-coding the currency so BNPL quotes in the wrong denomination, and skipping webhook verification so paid orders sit stuck in "pending payment".

Logistics: Aramex and local couriers

Shipping is where UAE stores quietly lose money. The rate table has to reflect real local pricing, and fulfilment has to talk to a courier that actually delivers here.

• Aramex - the regional default; its Magento integration generates the airway bill, pushes label data and returns tracking, which you surface in the customer account and shipping emails.
• Last-mile couriers - Quiqup, local aggregators and Emirates Post cover same-day and domestic parcels. Many stores run Aramex for GCC and cross-border shipments and a local courier for intra-UAE delivery.
• Address realities - the UAE has no universal postal-code system, so a checkout that hard-requires a valid ZIP will block orders. Make postcode optional and add emirate and area fields instead.

Pitfall: flat international shipping rates that ignore free-zone versus mainland pickup, and no COD surcharge, so the courier's cash-handling fee quietly eats the margin.

Arabic and RTL storefront correctness

Arabic is not a translation drop-in; it is a right-to-left layout. Done properly, the whole storefront mirrors.

• Layout mirroring - set the store view to RTL so Magento loads the mirrored stylesheet and flips direction; the nav, product grid, breadcrumbs and icons all move to the right. Hyva and Luma both support RTL, but custom components frequently hard-code left / margin-left and break the mirror.
• Fonts - Latin webfonts render Arabic poorly. Ship a proper Arabic face (Cairo, Tajawal or Noto Naskh Arabic) and self-host it rather than pulling it from an external @import.
• Checkout and forms - field labels, validation messages and the numeric keypad all need the Arabic store view. Test the full checkout in RTL, not just the homepage.
• Indexing - each language belongs on its own store view with distinct URLs, a self-referencing canonical, and hreflang pairs (for example ar-AE and en-AE). Machine-translated Arabic that search engines treat as thin content is a real ranking risk; have it reviewed by a human.

Multi-currency and multi-store across the GCC

Selling into more than one GCC country is a store-hierarchy decision, not a currency dropdown.

• AED and SAR as base currencies - run each country as its own Magento website with its own base currency (AED for the UAE, SAR for KSA) rather than converting on the fly, so prices are deliberate and rounded cleanly.
• Website per market - a separate website per country lets you vary catalog price, payment methods, courier and tax independently, which you need, because the tax rules differ.
• Currency display - allow the local currency per store view and set sensible rounding; auto-FX rates that leave prices at 37.14 AED read as amateur.

Pitfall: one global website with a currency switcher. It collapses the moment two markets need different VAT rates or different gateways.

UAE VAT (5%) configured correctly

This is the area a generic build most often gets wrong, and the one with legal consequences. UAE VAT is 5%, administered by the Federal Tax Authority. In Magento it comes together from several settings:

• Tax zones and rates - create a 5% rate for the United Arab Emirates under Stores > Tax Zones and Rates.
• Tax classes - assign a product tax class (standard-rated) and customer tax classes (retail versus B2B), then bind them in a tax rule so the right rate applies to the right combination.
• Price display - decide whether catalog prices are entered including or excluding tax, and set cart, catalog and invoice display to match. Getting "catalog prices include tax" wrong either double-applies or omits the 5%.
• Compliant tax invoices - the FTA expects the words "Tax Invoice", your TRN, a sequential invoice number, the VAT amount per line and the total in AED. Magento's default invoice PDF carries none of the TRN detail out of the box, so the template needs work.
• Zero-rated versus standard-rated - exports outside the GCC VAT area are typically zero-rated, and cross-border B2B can fall under reverse charge. Model these as separate tax rules; do not just switch the rate off per order.

Rates also differ across the region - KSA is 15%, not 5% - which is another reason each market wants its own website and tax configuration.

Where this gets checked

Every item above - gateway coverage, courier and COD reconciliation, RTL correctness, currency and website structure, and VAT rules and invoices - is part of a regional Magento audit. A Dubai-based audit adds the local layer a generic technical review skips: it verifies the store is actually built for how the UAE and GCC pay, ship, read and file tax, not just that the code is clean.