Ant International reports UAE payment and stored-value licences

The announcement

Ant International said on 14 October that it had obtained a Retail Payment Services and Card Schemes Category II licence and a Stored Value Facilities licence from the Central Bank of the UAE. Its release describes the first as a step towards Antom merchant acquiring and the second as enabling WorldFirst cross-border account services. It discusses future launches, while distinguishing existing Alipay+ acceptance through licensed local partners. The announcement does not establish a live offer for every merchant.

Independent merchant analysis: separate three buying decisions

A merchant assessing this development should separate accepting a customer payment, holding business funds and sending money onward. These functions can appear within one commercial relationship but involve different operational questions. Checkout teams may focus on payment completion, while finance cares about the account statement and treasury cares about usable balances. A proposal should explain each function independently before the business evaluates the combined experience.

Prepare a simple map of the intended flow. Identify the merchant entity selling the goods, the customer-facing checkout, the party receiving the payment and the account receiving the proceeds. Then add refunds and supplier payouts. If the same brand appears at several points, still request the relevant legal entity and contractual role at each point. A consistent logo does not by itself explain who owes the merchant money.

Do not turn permission into a launch promise

Regulatory progress and implementation readiness answer different questions. A merchant can welcome an additional prospective option without promising customers that it will be available next week. Request the provider's current onboarding status, supported channels and production requirements. Ask which functions are available under a signed agreement today and which depend on further product work. Record the answer alongside the proposed launch date.

Avoid budgeting on an assumed price or settlement schedule. An announcement rarely contains the full commercial schedule a merchant needs. Build a comparison using actual quotations for the business model, transaction sizes and customer locations submitted for review. Where an item is unknown, mark it unknown. Filling a comparison spreadsheet with optimistic assumptions can make a planned service appear more competitive than an established arrangement with complete terms.

Make customer geography specific

A UAE business serving residents, visitors and overseas customers may have several payment journeys. Analyse them separately before deciding what a new provider should improve. The relevant questions include where customers pay, which currency they see, whether fulfilment is immediate and how refunds are requested. A broad international footprint does not tell the merchant which of its particular journeys can be supported under the proposed contract.

Use transaction samples that reflect the real business. An online retailer might present domestic purchases, tourist orders delivered locally and overseas shipments as separate scenarios. A service business might need deposits followed by final balances. For each scenario, require a clear answer on acceptance, authentication, settlement currency and refund processing. Do not infer support for subscriptions or delayed delivery from a demonstration of a single immediate purchase.

Compare usable funds, not only checkout cost

Treasury should compare the entire route from customer payment to spendable business funds. A useful worked example begins with the amount charged, shows applicable deductions and conversion, and ends with the amount credited to the intended account. Identify the dates used at each stage. This allows the merchant to distinguish payment confirmation from settlement and settlement from the final availability of funds under its agreement.

If an account product is part of the proposal, ask how balances are displayed, reconciled and withdrawn. Confirm who can change beneficiary details or approve a payout. Separate employees who create instructions from those who approve sensitive changes where the business can support that control. Review access when staff leave or change roles. These are proposed operational checks, not claims about the specific features of either announced service.

Keep refunds connected to the original sale

A new checkout can look successful until the first partial refund or disputed order. Include these events in procurement testing. Ask how the original payment reference appears in the refund record and how finance matches the deduction to a customer case. If the payment method and payout account are provided by different parties, establish which party investigates a refund that remains unresolved.

Do not solve an uncertain refund by sending a separate payment to newly supplied bank details without proper verification. Customer support should know the approved alternatives when an original route cannot be used. Preserve the cancellation decision, payment evidence and execution record. A customer-facing promise should reflect the provider's confirmed process, with an escalation path for exceptions rather than an unsupported guarantee of immediate receipt.

Plan a controlled migration

Merchants evaluating an additional provider do not need to move all volume at once. A sensible pilot can start with a defined channel, customer segment and order type. Record the existing performance baseline before switching traffic. Measure completion, duplicate attempts, support contacts and settlement reconciliation for the same population. Changes in marketing or product mix should be recorded so they do not distort the comparison.

Keep the existing route available according to its contract while the new arrangement is tested. Check how saved customer credentials, recurring instructions and outstanding refunds are handled before closing any account. The implementation plan should identify obligations that remain with the old provider after new sales move elsewhere. A migration is complete only when historic customer cases and financial balances can still be explained and serviced.

Assess the operating relationship

Ask who will support the merchant during an outage, an unexpected hold or a disputed settlement amount. Obtain escalation contacts and clarify the information needed to investigate a case. Review how material business changes should be disclosed, including new products, customer markets or processing patterns. A provider's willingness to discuss these operational details is more useful than a general assurance that its platform supports growth.

Bring compliance into the assessment early. The merchant's activity and customer markets need their own review; a payment provider's licence does not supply permission for the merchant to enter a regulated sector. Keep marketing descriptions aligned with the actual approval received. If the provider's proposed scope changes during onboarding, update the implementation plan before customer traffic begins rather than relying on an earlier sales conversation.

Prepare an exit scenario alongside the launch scenario. Ask how the merchant obtains transaction history, outstanding balances and unresolved case records if it later changes providers. Identify which reports can be downloaded and whether they contain the references required by the accounting system. Review who remains responsible for refunds initiated after processing stops. This is especially important when acceptance and account services are bundled commercially but managed by different operational teams. A clear exit plan does not imply distrust; it gives the business a practical way to assess continuity and record ownership. The same exercise also helps during an internal reorganisation, when staff and systems change but historic obligations still need attention. Treat these arrangements as procurement requirements to resolve before committing customer volume to the new relationship.