WhatsApp payments in Kuwait: a link, not a button

Search for WhatsApp payments and you'll see a pay button inside the chat, a card saved in WhatsApp, and money moving without leaving the conversation. That feature exists, but not here. Meta documents in-chat payments for businesses in India, Brazil and Mexico. Gallabox documents them for India and Singapore. No GCC country is on either list.

So for a business in Kuwait, taking payment on WhatsApp means something more modest and perfectly workable: the chat sends a link, the customer pays on a secure page run by your payment gateway, and the chat is told when the money arrives. The customer barely notices the difference — one tap out, one tap back.

It is worth being clear about this before you plan a campaign or a bot around it. A flow designed around a button that doesn't exist here has to be rebuilt; one designed around a link works from day one.

The link comes from your gateway — the one that already handles your website or the links you send today. Kuwaiti gateways such as MyFatoorah and Tap Payments have no built-in Gallabox integration, and neither does KNET itself, so we connect them by link or by a custom build. The customer picks KNET or a card on the gateway's page, if your gateway offers them, and your settlement stays exactly as it is.

For a one-off, an agent creates the link in the gateway's dashboard and pastes it into the chat. For volume, the link is created automatically: a bot step or a small service asks your gateway for a link for that order's amount and sends it as a message with a button. Gallabox documents a Network International hosted checkout for the Middle East and Africa, and Stripe is in its integration catalogue. Both are useful if you already have an account, but check that the gateway serves your company's country before you plan around it.

Set an expiry on each link where your gateway allows it, and send a fresh one when a customer comes back later, rather than reusing an old link with an old amount.

WhatsApp doesn't know whether the customer paid. Your gateway does. To close the loop, the gateway sends a webhook — an automatic notice — when a payment succeeds or fails, and something has to receive it.

That something is a small custom build. We set up a service that receives the gateway's webhook, matches it to the order and the customer, and calls Gallabox's API to send the receipt, update the contact's tags and, where needed, alert the team in the inbox. Basic includes Gallabox's message and contact API, which covers sending the receipt; the full API, and the bot step that calls outside systems, start on Essential.

Without that build, the fallback is manual: someone checks the gateway dashboard and confirms by hand. That's fine at low volume and painful at high volume, and a customer who paid at 11pm waits until morning to hear back.

Until 30 September 2026, a utility template sent inside the 24-hour window is free. From 1 October 2026 it is charged, and Kuwait becomes its own pricing market on the same day, with a utility rate of $0.044 per message before the provider's markup. Gallabox's rate card adds 15%, which puts it at $0.0506.

Order and payment confirmations are usually utility templates, so every automatic receipt now has a price. A free-form reply inside the window is a service message instead: it draws on the 1,000 free service messages each number gets a month, then costs Kuwait's service rate, which is also $0.044. When the customer has just paid and the chat is still open, a plain reply can be the cheaper receipt; when the payment lands after the window has closed, only a template will do.

Chats that began from a Click-to-WhatsApp ad follow different rules: once you reply within 24 hours, every message for the next 72 hours is free, templates included, so an ad-to-payment journey that finishes inside that window costs nothing in Meta fees. Keep receipts short and factual as well. A receipt that slips in a promotion can be reclassified by Meta as marketing, which costs more.

Links work best where the price is known and the customer is already talking to you: a deposit for a clinic or salon booking, the balance on a custom order, a delivery order confirmed in the chat, a course fee, a renewal. A reminder template the day before a payment is due, with the link on a button, is often all a service business needs.

Cash on delivery is still common in Kuwait, and the chat helps there too: confirm the order and the amount before the driver leaves, and offer a link to anyone who would rather pay now. It cuts down on surprises at the door.

Links are not the right tool for everything. Card details should never be typed into a chat, by the customer or by your team, and we don't build flows that ask for them.