Payment gateway integration in the UAE means connecting your website, app or POS to a provider such as Telr, Network International (N-Genius), PayTabs or Stripe so customers can pay by card, Apple Pay or buy now, pay later in AED. The gateway is only half the job. This guide covers how to choose one, which checkout design to use, and what your back office needs so refunds, reconciliation and VAT receipts work.
Which payment methods do UAE customers expect?
Customers in the UAE expect Visa and Mastercard, Apple Pay on iPhone, and increasingly an instalment option such as Tabby or Tamara for larger baskets. Which of these you need depends on what you sell and to whom.
Business-to-business portals often need card payment plus bank transfer with a clear invoice reference. Consumer stores selling higher-value items tend to benefit from instalment options. Service businesses that charge after the job, such as maintenance or rentals, may need saved cards or pre-authorisations. Start from your customers and your cash flow, then pick the methods, then pick the provider.
Think about where payments happen, too. A website checkout, an in-app payment, a payment link sent by WhatsApp or email, and a card terminal in a shop may all need to feed the same order records. Choosing a provider that covers several of these channels can simplify reconciliation, but it is not essential if your software brings the data together.
How do you choose between Telr, N-Genius, Stripe and others?
Choose on fit, not on headline fees alone. The right gateway supports your payment methods, settles to your bank on terms you can live with, and has a technical interface your platform can use cleanly.
- Payment methods supported: cards, Apple Pay, Google Pay, and whether BNPL providers can be offered through the same checkout
- Eligibility for your business type and licence, and how long onboarding takes
- Settlement timing, currency and which bank account receives funds
- Fees for transactions, refunds, chargebacks and currency conversion, confirmed in writing
- Support for saved cards, recurring payments, pre-authorisation and partial capture if you need them
- Quality of the sandbox, documentation, webhooks and plugins for your platform
- Dashboard and reports your finance team will use for reconciliation
- Support hours and how disputes are handled
Fees and terms are set by each provider and change over time, so request a written offer from more than one. From a development point of view, we integrate with the gateway you choose; the commercial relationship is between you and the provider.
Hosted payment page, embedded fields or in-app SDK?
A hosted payment page is the simplest and keeps card data away from your servers. Embedded fields and in-app SDKs give a smoother experience but take more work to build and test.
With a hosted page, the customer is sent to the provider's secure page and returned to your site afterwards. Your obligations under the card industry's PCI DSS rules are lighter, because card numbers never touch your systems. Embedded fields keep the customer on your page while the provider still handles the card data. Mobile apps usually use the provider's SDK, which also makes Apple Pay smoother. Ask the provider which option they recommend for your platform, and confirm your PCI DSS obligations with them.
How should buy now, pay later fit into checkout?
Tabby and Tamara are usually offered as separate payment options at checkout, either through their own integration or through a gateway that supports them. The BNPL provider decides whether to accept the customer, and you are paid according to that provider's merchant terms.
Plan the details early. Show instalment messaging on product pages only where the provider allows it. Handle the case where a customer is declined and returns to choose another method. Make sure full and partial refunds flow back correctly, because a refund on an instalment purchase is handled differently from a card refund. Finance teams also need a clear report of BNPL settlements, since they arrive separately from card settlements.
What must the back office handle?
The back office must record every payment status reliably, even when the customer closes the browser at the wrong moment. Most payment problems in live systems come from missing status updates, not from the checkout screen.
- Webhooks or server-to-server notifications to confirm payments, rather than trusting the browser redirect
- Protection against duplicate orders when a customer clicks twice or a notification arrives twice
- Full and partial refunds from your admin panel, with reasons recorded
- Daily reconciliation of orders against gateway and BNPL settlement reports
- Receipts and tax invoices that show prices in AED and 5% VAT where it applies
- Clear handling of failed, pending and expired payments, with customer messages
- Logs that let support staff trace any payment without seeing full card numbers
Ask your accountant how receipts and invoices should be formatted for your VAT position, and design the templates to match. If you will be affected by e-invoicing for business customers, plan for it at the same time.
What does a typical integration look like?
For example, a Dubai retailer with shops and an online store might sell through a website, take orders by phone and run a POS in each branch. A practical integration would put one gateway behind the website and a payment link feature for phone orders, add Apple Pay and one BNPL option at checkout, and feed every payment into the same order and stock system the shops use. Refunds could then be issued from one admin panel, whichever channel the sale came from.
This joined-up approach avoids a common problem: online sales, phone payments and shop sales sitting in different systems that finance has to match by hand. If your shops need a POS that shares stock and orders with the website, see our POS software for the UAE.
How is a payment integration project usually run?
Payment work follows a careful sequence: discovery, written scope, sandbox build, testing of every path, then a controlled go-live. We run it as part of our web development and app projects.
Discovery in video-call workshops confirms payment methods, the order lifecycle, refund rules and the reports finance needs. The written scope lists each flow and each edge case. Work runs in two-week sprints with a demo at the end of each, and a named lead engineer owns the integration. Testing covers successful, declined, cancelled, refunded and partially refunded payments in the provider's sandbox, then a small number of live transactions before full launch. Our quality assurance team tests on real devices, including Apple Pay. At handover, code and cloud accounts are registered to you, and the gateway account stays in your company's name.
What drives the cost of a payment integration?
The number of payment methods and channels, and the depth of back-office work, drive cost. A single hosted payment page on one website is a small task. Several providers across website, app and POS, with refunds and reconciliation, is a substantial piece of work.
Other factors include whether your platform has a maintained plugin for the gateway, whether you need saved cards or recurring billing, and how much reporting finance needs. Read more about how we work with businesses in Dubai, Abu Dhabi and Sharjah on our UAE web development page.
Frequently asked questions
Can we use more than one payment gateway?
Yes. Some businesses use one gateway for cards and add BNPL providers separately, or keep a second gateway as a fallback. Each extra provider adds integration, testing and reconciliation work.
How long does gateway approval take?
It depends on the provider and on how complete your documents are. Apply early, in parallel with development, so approval does not delay launch.
Do we need to store card details?
Usually not. Providers can store cards on your behalf and give you a token to charge later, which keeps card numbers out of your systems.
Can customers pay in currencies other than AED?
Many gateways can accept foreign cards and some offer multi-currency pricing. Check settlement currency, conversion fees and how this affects your invoices with the provider and your accountant.
If you are choosing a gateway or fixing a checkout that loses orders, talk to us about your payment flows.
This guide was researched and drafted with the help of AI tools, then checked for accuracy against our editorial rules. Laws, tax rules and prices change: confirm current requirements with your adviser before you decide.
Working on something similar?
See our Web Development Company for GCC & US Businesses page, or talk it through with us, with no obligation.
