Sales
Banks left WhatsApp in the UAE. Here is how merchants keep selling in chat and take the payment safely
Since May 2026, UAE-licensed financial institutions may not process transactions, send one-time codes or exchange customer financial data on messaging apps. Merchants were not the addressees, but every chat sale ends with a payment that touches a bank. This guide explains what was reported and how to build a chat-to-checkout journey that keeps the conversation and moves the money to regulated infrastructure.
MonoChat Team Updated: 8 min read
On this page
- What was reported
- What it means for a merchant
- Who else should read this
- How a chat-to-checkout journey works
- What MonoChat does
- Set it up in MonoChat, step by step
- Message examples
- The WhatsApp rules still apply
- Where your data is stored
- Questions to settle with your provider
- The short version
- Sources
The Central Bank of the UAE (CBUAE) told the banks, insurers, exchange houses and finance companies it licenses to stop handling customers’ financial matters on WhatsApp and other messaging apps. Merchants were not the addressees. But for any business that sells in a chat, in the UAE or into it from elsewhere in the Gulf, the payment at the end of that chat touches a bank or a payment provider, and that is where the change reaches you. The answer is a chat-to-checkout journey: the conversation stays in WhatsApp, and the money moves on a licensed provider’s own page.
This guide explains what was reported, what a merchant can keep doing, and how to build that journey in MonoChat. It is a summary to plan with, not legal advice; we could not find the circular’s own text, and everything below comes from the sources we cite.
What was reported
Gulf News reported on 29 April 2026 that the CBUAE directed “all licensed financial institutions” to “stop using instant messaging platforms”, WhatsApp included, to communicate with customers. According to the report, institutions may not use messaging apps to:
- request or share customer data;
- initiate or process transactions;
- authenticate customers, for example with one-time passwords or verification codes;
- start new interactions that rely on instant messaging.
The CBUAE cited fraud, identity theft, account takeovers and social engineering, and the risk of customer data being accessed or stored outside the UAE. Institutions must ensure customer data and transaction records are “securely stored within the UAE”, and had to submit compliance updates by 30 April. Banks then began telling customers by SMS, email and app alerts that they would no longer use messaging platforms for correspondence or service requests.
Hadef & Partners, a UAE law firm, wrote on 8 May 2026 that, according to media reports, the directive was issued on 17 April and took effect on 1 May 2026.
What it means for a merchant
The law firm’s note for e-commerce retailers is the useful part. Retailers may keep using WhatsApp for sales and engagement, but “the financial leg of any transaction must now be completed outside that environment”. It expects that “banks and payment service providers will inevitably impose stricter controls” on the merchants they serve, and sums the model up as “conversational commerce at the front end; regulated financial infrastructure at the back end.”
For a shop, a salon, a clinic, a tour operator or a B2B seller, that splits a chat sale into two kinds of steps:
| Keep doing in the chat | Move out of the chat |
|---|---|
| Answering questions, sending photos, catalogues and prices | Asking for card numbers, CVVs or online banking logins |
| Agreeing the order, the quote or the booking | Asking customers to forward one-time codes |
| Sending a link to your payment provider’s checkout page | Accepting card photos or bank statement screenshots as proof |
| Confirming the order once the provider reports the payment | Confirming a bank transaction on a bank’s behalf |
| Sending the receipt, delivery and booking updates | Keeping payment details in chat notes |
Hadef & Partners lists six steps for retailers: audit existing customer journeys and payment flows; segregate financial interactions from conversational channels; review and strengthen payment infrastructure; update customer-facing terms, policies and disclosures; train and brief customer-facing teams; and future-proof the digital commerce strategy. The second and fifth are where a messaging platform does the work for you.
Who else should read this
The directive is UAE-specific. Nothing in the reports says it covers Saudi Arabia, Qatar, Kuwait, Bahrain or Oman, which have their own central banks. Two cases still matter outside the UAE:
- Sellers abroad with UAE customers. If your payment provider or acquiring bank is UAE-licensed, its controls follow you, wherever your team sits.
- Gulf groups with one process for every country. A chain with branches in Dubai, Riyadh and Doha usually wants one way of taking payments in chat. Building it to the stricter UAE expectation once is simpler than running two.
And the habits the CBUAE wants to end (card numbers typed into a chat, codes forwarded to a “bank agent”) are what fraudsters exploit everywhere. A clean chat-to-checkout journey protects customers in any market.
How a chat-to-checkout journey works
- The customer asks, compares and decides in the chat.
- Your agent, your flow or your AI agent sends a payment link for the exact amount.
- The customer opens it and pays on the payment provider’s own page, with the provider’s card checks and the payment methods your account offers.
- The provider tells MonoChat that the payment went through.
- The chat continues by itself: a confirmation, the receipt, the delivery or booking details.
Nothing financial is typed into the conversation, and the payment record lives with the licensed provider.
What MonoChat does
Every payment provider MonoChat connects to works this way: MonoChat creates the order with the provider and sends a link to the provider’s hosted payment page. For Gulf businesses that means:
- Checkout.com (since MonoChat 3.8.46): the order is marked paid only after Checkout.com confirms the captured payment. See Checkout.com payment links on WhatsApp.
- MyFatoorah: since MonoChat 3.8.48 (10 November 2026), a payment system takes your MyFatoorah account’s country and calls that country’s API address, and the link opens MyFatoorah’s invoice page with every method enabled on the account, such as KNET, Benefit, mada, Apple Pay and cards.
- N-Genius, Telr, PayTabs, Tap, HyperPay and Paymob for cards, Ziina and Mamo for small-business payment links.
- Tabby and Tamara for instalments, covered in our guide to buy now, pay later on WhatsApp.
- Stripe and PayPal for customers worldwide; see PayPal payment links on WhatsApp.
MonoChat is an official Meta Business Partner and connects your own number to the WhatsApp Business API. The same payment links work in Instagram, Messenger and web chat conversations.
Set it up in MonoChat, step by step
1. Connect your payment provider. Go to Settings › Payment › Payment Systems, click Create, choose your provider, give it a title and paste the credentials from the provider’s dashboard. If you use several, mark the usual one with Set As Default. Test with the provider’s sandbox or a small real payment before going live.
2. Send the link from a flow. In your flow, add a Send Payment Request node where the customer agrees to buy. Choose the payment system, enter the amount (a flow variable is allowed, so it can come from a quote or an order) and the currency. Write your own message with {{paymentLink}} where the link goes. If the amount is not a positive number or no payment system is set up, the node takes its failed output and nothing is sent.
3. Keep the link for later. Turn on Save Flow Variable in the same node so a reminder an hour later can reuse the order and the link.
4. Continue when the money arrives. Start the next part of the flow from New Payment Received: the thank-you, the receipt, a tag for the fulfilment team, or an HTTP Request node that tells your order system. Payment Amount conditions let you treat a deposit differently from a full payment.
5. Let agents do it by hand. An agent can send a link from the Wallet widget beside the chat with Create Payment Order, so nobody is tempted to “just take the card number”.
6. Give your team the words. Save a short reply for the moment a customer offers card details in the chat, and train the team to use it every time.
7. Handle refunds with the provider. Refunds are made in your payment provider’s dashboard; tell the customer in the chat when it is done.
Message examples
The payment link after the customer decides
Thank you, Fatima. Your total for the two abayas is AED 1,240. You can pay securely on our payment provider’s page here: {{paymentLink}} For your safety, please do not send card details in this chat. We will confirm here as soon as the payment arrives.
When a customer offers card details
Thank you for trusting us. For your security we never take card numbers or codes on WhatsApp. Please use this secure payment page instead: {{paymentLink}}
The confirmation after New Payment Received
Payment received, thank you! Your order is confirmed for delivery to Al Barsha tomorrow between 2 and 6 pm. We will send the courier details here.
Instalments
You can split this order into four payments with Tabby. Open this link to see your options and pay on Tabby’s page: {{paymentLink}}
The names, amounts and addresses are illustrative.
The WhatsApp rules still apply
- Inside the 24-hour customer service window you can send the link as a normal message.
- After it closes, only an approved template can go out. A reminder about one specific order is a utility template; add an offer and it becomes marketing. See WhatsApp payments in chat for the full picture.
- Meta bills message fees directly, in the currency of your WhatsApp account, and MonoChat adds no markup.
Where your data is stored
The circular is about financial institutions, but it reflects a wider question about where customer conversations are kept. When you connect a WhatsApp number on the Cloud API in MonoChat, you can choose the UAE as its storage region; that covers Meta’s stored copy of the messages, and not numbers connected with coexistence. Businesses that need the whole platform on their own infrastructure can run MonoChat on their own servers. Our UAE site explains what the storage region covers, and monochat.ae has more guides for UAE businesses, in English and Arabic.
Questions to settle with your provider
- Does it have its own rules for payment links sent in chat apps, such as link expiry or amount limits?
- Which payment methods does the link page show for your account?
- How are refunds and disputes handled, and what does the customer see?
- What does it need in your terms and checkout disclosures?
The short version
Keep selling on WhatsApp. Take the money on a licensed provider’s page. Write the rule into your terms, train the team, and let a flow or an agent send the link and continue once the provider confirms. MonoChat’s Basic plan is free and Growth is $120 a month; payment providers charge their own fees. Start for free at app.monochat.ai.
Sources
- Gulf News: UAE Central Bank bans WhatsApp, messaging apps in financial customer communications (updated 29 Apr 2026, opened 11 Nov 2026)
- Hadef & Partners: UAE Central Bank Restricts WhatsApp for Banking Communications, Implications for E-Commerce Retailers (8 May 2026, opened 11 Nov 2026)
- MonoChat help center: Payment Systems and Flows (opened 11 Nov 2026)
- MonoChat changelog: versions 3.8.46 (Checkout.com) and 3.8.48 (MyFatoorah in every country it serves)
Put this into practice with MonoChat