How I Would Set Up Payments for a New Dubai Business

A practical Dubai payments workflow: company, business bank, gateway, payment links, checkout, Apple Pay, invoicing and monthly reconciliation.

By Faisal Karkoh · Published: 2026-10-05T14:35:30.356Z · Last updated: 2026-10-05T14:35:30.356Z

Information checked: 2026-10-05

Review due: 2026-11-04

I would start a new Dubai service business with an approved company bank account, a clear invoice and a payment link. I would add website checkout when the sales process needs it. The first milestone is not seeing a successful card payment. It is matching that payment to an invoice, a bank payout and the books.

This is the workflow I would build, not a claim that I have personally launched this exact stack. The provider comparisons cover product choices; this guide covers the gaps between them.

The sequence

UAE company and permitted activity.
Activated business bank account.
Approved payment gateway.
Payment links for the simplest sale.
Website checkout when needed.
Cards and Apple Pay verified on the actual checkout.
Invoices connected to each sale.
Accounting and reconciliation through to the bank.

Set the invoice template and accounting rules early, even though reconciliation happens last. Otherwise the first sale creates a cleanup job rather than a repeatable process.

1. Get the company and activity right

Write a plain description of the product, customer countries and how the sale happens. Use it consistently in licence, bank and gateway applications. A gateway approving one business model does not automatically approve a different one later.

Start with the Dubai business setup guide; use the free-zone shortlist if the licensing route is still undecided. Keep the issued licence, ownership documents and signing authority together. Do not start by building checkout and hope the legal entity will fit it afterwards.

2. Open the bank and verify the payout destination

For a small digital company, I would start with Wio, subject to eligibility. The Wio operating review covers how I would organise it. The Mashreq comparison is the next stop when a different mandate, transfer pattern or banking requirement changes that choice.

Use the company's approved bank details and legal name in the gateway application. Confirm that the account is operational, not merely assigned an IBAN, and that the provider accepts the payout currency and account. Keep customer receipts separate from personal spending.

I would also keep enough operating cash to cover the gap between a sale and settlement. A gateway balance is not money available for payroll. Wio's onboarding guidance and Mashreq's key facts are the checks behind that banking step.

3. Pick one gateway for the first sales model

My default is Ziina for a UAE service business using links. I would start with Tap when specific GCC payment methods are important. For an online store, confirm the currently supported platform integration before committing. The Ziina vs Tap comparison contains the product and fee detail.

Ziina's public VAT wording remains inconsistent between its business-fee help article and general fees page. I would request a written VAT-inclusive quote; I am not choosing either interpretation here. A small apparent fee advantage is not a reason to ignore that uncertainty.

Request a merchant-specific summary covering enabled methods, currencies, payout timing, fees, refunds, disputes and reserves. Tap's UAE terms are a reference, not a substitute for the agreement offered to your company. Do not promise suppliers a payout date from a marketing headline.

4. Start with a payment link and a stable reference

Ziina's acceptance guide covers links and card/wallet collection. Tap's business guide includes goCollect links. For a quoted service, I would use this route before commissioning a custom integration.

Create the invoice or order reference first. Associate the link and provider transaction with that reference, using supported fields or a controlled record. Make the amount, currency, business name and terms clear. If the link can be paid more than once, have a check for duplicate payments.

WhatsApp can deliver the link, but it should not be the only record of the sale. The Gulf WhatsApp automation guide is useful here: bring the conversation into an operating process instead of leaving payment evidence scattered across chats.

5. Add website checkout when it removes real work

A store needs the order, stock, delivery and payment states connected. A consultancy taking a few agreed invoices may not. I would add checkout when manual linking creates errors or slows a self-service sale, not just because a website feels unfinished without it.

First put the domain and business email under company control using the .ae setup guide. Then use the provider's current supported plugin or integration for your platform. Keep the secret keys on the server and separate test from live credentials.

For a custom build, start with Ziina's developer documentation or Tap's integration guide. Ask the developer to demonstrate final payment verification, retries and duplicate-event handling. A browser redirect to “success” must not, by itself, release an order.

6. Verify Apple Pay and cards on the actual customer journey

Confirm which methods are enabled for your merchant account, channel and devices. Tap's method directory is a starting point, not a guarantee that every regional method is available to a UAE entity.

Test cards and Apple Pay separately in the supported environments, including a declined payment and a customer closing the page. For a website, complete any required domain verification. Check the business descriptor a customer will recognise on their statement.

Use verified server-side status to update the order. Tap's webhook documentation explains why post-payment notifications matter even when the customer does not return to the site. Handle repeat notifications without sending the product twice, and reconcile missing events through the provider's supported status checks.

7. Make invoices part of the system

A payment receipt and an invoice serve different purposes. Have the accountant approve the invoice template, numbering, currency treatment and tax fields. Use the FTA's tax-invoice guidance for applicable requirements rather than treating the gateway receipt as automatically sufficient.

Check the UAE e-invoicing programme with the accountant and software provider too. A PDF emailed to a customer is not the same thing as structured e-invoicing. Confirm your company's scope and implementation obligations; do not assume a small or newly formed business can ignore the programme.

I would keep one authoritative invoice record and connect payment, refund and credit-note references to it. Do not let the bank, checkout and automation each independently issue a different invoice for the same sale.

8. Reconcile gross sales to net cash

Use a gateway clearing account in the accounting workflow so the net bank deposit is not mistaken for total revenue. Match the provider's settlement report to the bank, then match the underlying transactions to invoices and orders.

As a deliberately simplified example, AED 1,000 of collected payments less AED 30 of fees produces AED 970 in the bank. The AED 30 is invented for this example, not a Ziina or Tap quote. Tax treatment is omitted here and must be recorded correctly in the actual books. With refunds, reserves, disputes or currency conversion, there are more lines to reconcile.

I would review unmatched items weekly and close the month with the accountant. Check pending payouts separately from failed ones; timing differences are not always missing money. Save fee invoices, settlement reports and refund evidence, not just a screenshot of the balance.

The launch test and the automation boundary

Follow the provider's test process first. Once approved, run a permitted, controlled live payment and refund and verify the resulting bank and accounting entries. Test partial refunds where relevant, duplicate notifications, abandoned checkout and a delayed payout. Assign an owner to each exception before increasing volume.

Then automate reminders and matching with something like the n8n invoicing workflow. Keep human approval for consequential actions such as refunds, beneficiary changes and supplier payments. An AI summary can flag an exception; it should not improvise a financial decision.

For subscriptions, this basic flow needs renewals, failed-payment recovery and cancellation handling. The Stripe Billing guide covers that architecture, but its US pricing examples are not UAE rates. Return to the Dubai hub for the rest of the operating stack.