Ziina for business: fees, payouts and setup checks

Understand Ziina payment links, business onboarding, integrations, fees and payouts, with practical UAE workflows and clearly scoped limitations.

Faisal Karkoh · 10 Oct 2026 · 6 min read

A small service business can lose more time asking “has the client paid?” than it spends taking the payment. The useful test for Ziina is whether a payment link closes that loop: the customer pays, the business identifies the invoice, and the money reaches the right bank account.

I would consider Ziina for a UAE business that wants a straightforward way to collect payment without building a checkout first. An online shop has more to test: order status, refunds, wallet support and the connection to accounting. This guide is based on official documentation reviewed on 9 October 2026, rather than experience operating a Ziina merchant account.

Start with the payment you need to collect

Ziina offers business payment collection through links, QR codes and website integrations. Its payment-acceptance guidance also covers cards and wallets, including Apple Pay and Google Pay. A payment link suits a consultant requesting a deposit or a business taking orders through messages. A store integration connects the payment to an order that already exists.

Those are different operating problems. For an appointment deposit, a clear invoice reference might be enough. For a store selling the last item in stock, staff need a dependable payment state before releasing the order. Decide which problem you have before choosing an integration.

Collection need	Likely fit	Do not proceed until you can
Invoice, deposit or message-based order	Payment link or QR code	Put the invoice reference on the request and reconcile the transaction ID, fee and payout.
Online store checkout	Store integration or API	Confirm paid, failed, refunded and abandoned orders without relying on a customer screenshot.
Subscriptions, marketplace payouts or special local methods	Shortlist alternatives as well	Confirm the exact payment method, recurring-change and fund-flow requirements before setup.

Who can open an account, and where can the money go?

Ziina's FAQ says account creation requires a valid Emirates ID and a UAE mobile number. That is the starting point for registration, not a promise that every business activity will be accepted. Explain the actual activity, expected transaction sizes and how you sell; supply the business and identity evidence requested for your account.

There is a useful detail in the cash-out guidance updated on 24 September 2026: a Ziina Business user can cash out to a personal bank account whose beneficiary name matches the linked Emirates ID. A verified business account can also cash out to a company bank account under its registered name. It would therefore be inaccurate to describe a company account as a universal technical requirement for every Ziina Business user.

For a company, I would still agree the receiving account with the accountant before taking customer money. Being able to send a payout somewhere does not settle how the company should record it. The Dubai payments setup guide explains the wider invoice-to-bank workflow.

The published fee needs one clarification

Ziina's business-fee article lists 2.6% plus AED 1 per received payment, with an additional 1.5% for an international card or a payment in a non-AED currency. It describes the fees as VAT-inclusive. The separate fees page says displayed fees are subject to 5% VAT. Those statements do not establish a single verified VAT-inclusive merchant charge.

For an illustrative AED 1,000 domestic payment, the stated formula produces AED 27. If that includes VAT, the fee remains AED 27. If VAT must be added, it becomes AED 28.35. Neither number should be presented as your final merchant charge until Ziina confirms which treatment applies. The example excludes disputes, refunds, bank charges and any store-platform fees.

Ask for one written fee schedule covering domestic and overseas cards, non-AED payments, refunds and payouts. Also ask whether overlapping international-card and currency conditions trigger one surcharge or more in your particular flow. Do not resolve unclear wording by adding percentages yourself. I would treat the fee position as usable only when you can answer four questions from the written terms: what is charged on a domestic AED card payment, what changes for an international card, what changes for a non-AED payment, and what happens to the original fee when you refund.

From a paid invoice to usable cash

The gateway page advertises settlement in one to two business days for AED 25,000 or less. That is a scoped product statement, not a guarantee about a first payout, larger collection or bank arrival in every case. Confirm how it applies to your transaction size and account before promising suppliers a payment date.

Consider a hypothetical design consultant collecting the AED 1,000 deposit above. I would give that payment a reference such as DESIGN-014, send a link alongside the invoice, and keep four values together: invoice amount, transaction ID, fee and bank deposit. If the bank receives a net amount, it must still be possible to explain the difference from the gross invoice. A dashboard balance alone is not that explanation.

Agree the service, deposit and refund terms with the client.
Create the invoice and payment request using the same reference.
Confirm the payment inside the provider account rather than accepting a customer screenshot as proof.
Match the payout and fee record to the bank entry.
Before broader rollout, complete an authorized test refund and document what happens to the original fee.

Adding Ziina to a store

Ziina's gateway page links to setup instructions for Shopify, WooCommerce and WordPress/other websites. Use those current links, then check the exact store country, checkout configuration and refund behavior. A logo in an integration directory does not prove that every feature is available to your account.

A developer working with the Ziina API should demonstrate successful and failed payments, repeated notifications and an interrupted return to the store. The order system needs to confirm payment independently of the browser landing on a success page. That is an acceptance criterion for the implementation, not a claim that I have tested Ziina's API here.

For sign-off, use a small test matrix rather than a single happy-path payment: one paid order updates inventory and accounting, one failed order does not reserve stock, one duplicate notification does not create a duplicate order, and one interrupted browser return is recovered from the provider-side payment status.

The fixed fee also changes the comparison for small collections. Using the 2.6% plus AED 1 reference above, ten AED 100 payments cost AED 36 before resolving the stated VAT ambiguity; one AED 1,000 payment costs AED 27 on the same basis. The AED 9 difference is the nine extra fixed fees, not a higher percentage. Use the number and size of your actual invoices when budgeting, and do not combine invoices merely to save a fee if that makes customer records harder to reconcile.

If you have not chosen the store itself, settle the operating model in Shopify versus WooCommerce first. Then compare the complete cost of the platform and gateway.

Where I would shortlist it

Ziina deserves a close look when the business is based in the UAE, collections are relatively simple, and staff would benefit from links and a single transaction view. Its appeal is less clear if your main requirement is a particular regional payment method, complicated subscription changes or marketplace fund distribution.

For local-method coverage, compare the account-specific offer in the Tap guide. For subscription or platform infrastructure, read Stripe for Business. The existing Ziina–Tap comparison keeps the choice between those two providers in one place. My first step would remain small: get the commercial terms clarified, then follow one payment all the way into the accounts.

Information checked: 9 October 2026. Official sources are linked beside the relevant claims.