Payment Gateway UAE: An Evidence-Led Selection Guide for Merchants

No single payment gateway is best for every UAE merchant.

Choose by merchant-entity eligibility, customer payment preference, settlement and currency needs, refund and dispute operations, reconciliation, integration, and the final contract. For HaiPay, current reviewed evidence supports a UAE evaluation of Cards and Apple Pay, while VA must remain an unexpanded label pending governing product evidence. HaiPay currently does not support bank transfers in the UAE. Every option still requires account-specific confirmation; market availability is not the same as product support or merchant approval.

Start with three separate evidence questions

A UAE payment method can exist in the market without being supported by a particular provider. A provider can support a method without enabling it for every merchant account. Keep these questions separate:

Source: CBUAE describes UAE payment infrastructure and regulated payment-service categories; Apple makes merchant acceptance dependent on the payment provider; HaiPay’s public documentation exposes merchant-level configuration fields.[2][3][5][9]

What a UAE payment gateway must support in practice

The selection brief should describe the business before it names a provider. Record the contracting entity, product category, customer geography, expected transaction pattern, refund policy, integration channel, presentment and settlement requirements, and finance workflow. Treat an answer as conditional unless its source applies to the same entity, payment option, currency, flow, and date.

For a UAE-facing merchant selling digital goods, content, games, subscriptions, or ecommerce products, the practical test is whether the provider can support the complete operating path:

1. onboard the intended merchant entity and business activity;
2. present the required option to eligible customers;
3. return an authoritative payment status;
4. support the required refund and dispute lifecycle;
5. produce records that finance can reconcile;
6. settle under documented currencies, timing, adjustments, and bank-account conditions; and
7. bind the applicable price, exchange-rate arrangement, and limitations in the quote and contract.

An attractive checkout does not compensate for an unverified settlement or dispute process. Conversely, a market-wide payment statistic does not establish product capability.

Read UAE market evidence without turning it into a product claim

CBUAE’s 2025 annual report records large volumes across UAESWITCH and UAEPGS, and its payment-systems pages describe card transactions, credit transfers, direct debits, and other retail infrastructure. These sources establish that the UAE has multiple payment rails. The point-of-sale figures are not ecommerce preference data, and none of the figures proves HaiPay support or merchant eligibility.[1][2]

Merchant acquiring and payment aggregation are regulated payment-service categories in the UAE. That is a due-diligence prompt; it does not establish HaiPay’s regulatory status or the contracting model for a particular offer. Ask each shortlisted provider to identify the legal contracting party and the regulatory basis relevant to the offered service.[3]

Cards for UAE-facing merchants

HaiPay’s current public pricing page lists UAE card support for Visa and Mastercard. Use that as shortlist evidence only. Before implementation, confirm the merchant entity, card types and issuing geographies, presentment and settlement currencies, authentication configuration, transaction range, refunds, disputes, integration mode, and app-ID activation in writing.[7][9]

Do not transfer general card documentation into a UAE account claim. HaiPay publishes general card refund endpoints, but the reviewed source set does not establish UAE-specific refund behavior for every merchant configuration. A general endpoint is evidence that a capability exists somewhere in the product; the account configuration and quote must establish whether it applies here.[11]

Apple Pay is available in the UAE, but acceptance is conditional

Apple lists the UAE as an Apple Pay market and describes use in stores, apps, and online. Apple also tells merchants to work with their payment provider. Eligible cards, participating issuers, devices, merchant setup, integration, and provider configuration remain relevant.[4][5]

HaiPay’s public pricing page lists Apple Pay for the UAE, which supports inclusion in a shortlist. It does not establish automatic activation for every merchant entity or every hosted, embedded, web, app, payment-link, or recurring flow. Require account-specific evidence before describing the customer journey or refund behavior.[7][9]

Keep VA as an exact label until governing evidence defines it

The final HaiPay content work order permits VA as a UAE coverage direction. This draft deliberately does not expand the label. The governing V5.5 pricing source and HaiPay factbase v2 were unavailable during this review, and a public documentation conflict remains unresolved. Consequently, the label cannot be published as a defined capability or implemented from this guide alone.[8]

Before release, obtain the approved definition, merchant eligibility, checkout and confirmation flow, limits, refund and dispute handling, reconciliation output, settlement behavior, integration dependency, and written contract treatment. If those items are not supplied, keep VA out of customer-facing capability copy even though it remains in this editorial evidence matrix as a blocked row.

HaiPay bank-transfer non-support is a product boundary, not a market statement

HaiPay currently does not support bank transfers in the UAE. The current HaiPay pricing matrix states that boundary, and the final work order uses the same direction.[7][8]

The UAE market itself does have account-based payment infrastructure. CBUAE describes credit-transfer and direct-debit systems, while Al Etihad Payments describes Aani and provider-dependent merchant enrolment. These market facts must not be rewritten as HaiPay capability.[2][6]

If UAE bank transfer is a mandatory checkout or collection requirement, remove HaiPay from the shortlist for that requirement unless a later, governing HaiPay source explicitly changes the product position.

Ask for the full commercial and settlement model

HaiPay’s public card pricing starts at 2.5% + US$0.30 per eligible transaction. This is general published starting pricing, not a UAE quote. Availability and actual terms depend on the contracting entity, market, volume, transaction quality, product configuration, and final contract.[7]

Request a written UAE-specific quote that answers:

The applicable exchange-rate arrangement is locked under the merchant contract and confirmed in the quote.

This guide does not publish a UAE tax treatment or outbound-fee figure because the required approved HaiPay evidence was not available for this review.

Verify merchant entity, underwriting, and contract fit

Market availability and technical integration do not establish onboarding eligibility. Ask for a written decision covering:

• the contracting merchant entity and incorporation country;
• ownership and required verification records;
• business model, goods or services, and activity classification;
• website or app, fulfilment, refund, and customer-support policies;
• expected ticket size, frequency, volume, customer geography, and currencies;
• settlement bank-account name, country, and currency conditions;
• restricted or conditionally reviewed activities;
• reserve, review, suspension, and termination conditions; and
• the owner and escalation path for unresolved onboarding questions.

Community discussions from UAE merchants repeatedly ask about licence, bank-account, gateway, and underwriting sequencing. Those discussions reveal questions worth answering, but they are not evidence of HaiPay eligibility or a universal UAE onboarding order.

Verify integration, refunds, disputes, settlement, and reconciliation together

HaiPay’s public documents describe hosted payment URLs, a JavaScript-based embedded card pattern, direct API integration, asynchronous notifications, status queries, and a merchant-configuration query. The configuration response can expose app-ID-level payment methods, limits, fee rate, settlement, and refund support. These are useful verification paths, not proof that an option is enabled for a particular UAE merchant.[9][10][12]

Use one acceptance record for the full lifecycle:

Visa’s public dispute material is useful for understanding scheme-level roles, but it does not document HaiPay’s UAE dispute workflow. Obtain the provider process and contract instead of importing a scheme overview into a product claim.[14]

UAE Payment Acceptance Evidence Matrix

The matrix separates market availability, HaiPay availability, and merchant-account applicability. “Confirmation required” is not a zero value; it means the reviewed evidence does not establish that field for the exact account.

Source: CBUAE, Apple, AEP, HaiPay Pricing, the final HaiPay content work order, and current HaiPay product documentation; all reviewed on 25 August 2026.[1][2][4][5][6][7][8][9][10][11][12]

The selectable table above is the authoritative asset. The evidence map is a visual summary and must not replace the table or its limitations.

Follow the UAE Payment Gateway Selection Flow

1. Confirm merchant-entity eligibility. Identify the contracting entity, business activity, ownership, customer geography, risk profile, and bank-account requirements.
2. Define customer payment preference. Use customer and checkout evidence for the intended audience; do not treat a market-wide statistic as the answer.
3. Test Cards, Apple Pay, and VA separately. For HaiPay, retain only options supported by governing product evidence and the merchant account. Exclude bank transfer from the HaiPay path.
4. Require the needed refund and dispute lifecycle. Reject or hold any option whose operating process cannot be documented and tested.
5. Confirm settlement and currency requirements. Bind currencies, schedule, cutoff, calendar, adjustments, reserves, and bank conditions.
6. Prove integration and reconciliation readiness. Test the actual configuration, final status, repeat events, refund records, join keys, reports, and exceptions.
7. Approve the quote and contract. Check that commercial terms and operational evidence apply to the same entity, option, configuration, and date.

Stop at any node where a mandatory field remains unverified. A provider should not advance because another provider’s information is also incomplete.

Where HaiPay may fit

HaiPay may merit evaluation when the merchant needs UAE Cards or Apple Pay and is willing to confirm the exact entity, configuration, customer flow, lifecycle, settlement, and quote. Its public documentation provides practical paths for checking an app ID’s configured methods and for evaluating hosted, embedded-card, and API integration patterns.[7][9][12]

For VA, evaluation should pause until HaiPay supplies the governing definition and complete product evidence. Use the exact label only; do not convert it into another payment category.

Start with the broader international payment gateway guide, compare routing models in local acquiring versus cross-border acquiring, and review the current HaiPay pricing page. Then ask HaiPay to confirm the actual UAE offer for the merchant.

Where HaiPay may not fit

Remove or hold HaiPay for the relevant requirement when:

• UAE bank transfer is mandatory;
• the merchant entity or business activity is not approved in writing;
• the required Cards, Apple Pay, or VA configuration is not visible in account-level evidence;
• the necessary refund, dispute, settlement, or reconciliation workflow cannot be documented;
• the integration model cannot support the required customer and finance lifecycle; or
• the quote and contract do not bind the required currency, schedule, adjustments, and operational responsibilities.

Review HaiPay local payment and credit-card acceptance as product discovery pages, not substitutes for account evidence. If the required proof is available, contact HaiPay for merchant-specific confirmation and a quote.

Methodology and editorial disclosure

HaiPay publishes this guide and is a provider discussed in it. The method does not rank HaiPay first or declare a winner. It separates UAE market availability, HaiPay product evidence, and merchant-account applicability; it records unverified operational fields rather than filling them from industry convention. Sources were opened and checked on 25 August 2026. Community material informed question selection only and was not used to substantiate provider performance, pricing, eligibility, or settlement claims.

The five-query Google UAE desktop review found a mixed field of provider product pages and comparison pages. That result supports an evidence-led Guide with a comparison matrix, not an unsupported provider ranking.

Sources

1. Central Bank of the UAE, Annual Report 2025. Accessed 25 August 2026. Market infrastructure and transaction context; POS data is not ecommerce preference evidence.
2. Central Bank of the UAE, Payments and Settlements. Accessed 25 August 2026. UAE systems and retail-payment categories; not HaiPay capability evidence.
3. Central Bank of the UAE, Licensing and Retail Payment Services and Card Schemes Regulation notice. Accessed 25 August 2026. Regulatory categories only.
4. Apple Support, Countries and regions that support Apple Pay. Accessed 25 August 2026; page dated 4 August 2026.
5. Apple UAE, Apple Pay. Accessed 25 August 2026. Merchant acceptance remains provider- and eligibility-dependent.
6. Al Etihad Payments, Aani and Aani Help. Accessed 25 August 2026. UAE market rail and provider-dependent merchant enrolment; not HaiPay support.
7. HaiPay, Pricing. Accessed 25 August 2026. Current public starting price and UAE method matrix; account applicability remains conditional.
8. HaiPay, Final content work order, 29 July 2026. Internal governing source. The V5.5 and factbase sources required to close the VA row were unavailable in this review; replace this internal reference before publication.
9. HaiPay Docs, Merchant payment configuration. Accessed 25 August 2026. Account-level verification fields; not proof of a particular account’s settings.
10. HaiPay Docs, AED collection application and AED collection query. Accessed 25 August 2026. API path and status fields; not method eligibility or complete reconciliation evidence.
11. HaiPay Docs, Card refund application and card refund query. Accessed 25 August 2026. General product capability; UAE account applicability requires confirmation.
12. HaiPay Docs, Integration process guide, integration guide, and end-to-end testing. Accessed 25 August 2026. General integration patterns and testing paths.
13. HaiPay, International Payment Gateway. Accessed 25 August 2026. Parent-guide scope and current public wording.
14. Visa, Dispute resolutions. Accessed 25 August 2026. Scheme-level context only; not HaiPay’s UAE workflow.