The problem: WhatsApp Pay does not exist here
In a few countries WhatsApp has native in-chat payments. Pakistan is not one of them. So however good your WhatsApp selling is, the chat ends with "send cash with the rider" or "transfer to this account and send a screenshot".
Both of those cost you real money. Cash on delivery brings refusals, rider float and days of settlement lag. Manual bank transfers bring a second problem: somebody on your team has to match screenshots to orders, and screenshots are trivially faked.
The practical answer is a payment link generated from the order itself — the customer stays in WhatsApp, taps a button, pays with a card, wallet or Raast, and your system learns about it automatically rather than by someone reading a screenshot.
How the pieces fit together
The important property of that chain is that the amount is computed from structured order data and the confirmation comes from the payment rail. Nobody is reading a screenshot, and nobody is retyping a total.
- Catalogue. Your products or menu live in the WhatsApp catalogue attached to your WhatsApp Business Account, so customers browse and add to a cart inside the chat.
- Order. The customer sends the cart. WhatsApp delivers it to your system as a structured order — line items, quantities and prices — not a block of free text.
- Total. Your system totals the order from those line items rather than trusting anything typed in the chat.
- Pay link. The bot replies with a "Pay now" button that opens a hosted checkout for that exact amount, tied to that exact order.
- Confirmation. When the payment completes, the order is marked paid and your system is notified — so the kitchen, the warehouse or the ERP can act on a confirmed order.
What a restaurant flow actually looks like
Restaurants are the clearest case, because most Pakistani restaurants already take orders on WhatsApp and the pain is specific and measurable.
| Step | Today, typically | With catalogue + pay link |
|---|---|---|
| Customer sees the menu | PDF or photo of a menu card | Tappable catalogue in the chat |
| Order is placed | Typed out, or a voice note | Structured cart with items and quantities |
| Order is read | Staff retype it into the POS | Arrives as data your system can use |
| Payment | Cash to the rider | Paid before the kitchen starts |
| Wrong or fake orders | Rider dispatched, food wasted | No payment, no dispatch |
| Reconciliation | Count cash at close | Already matched to the order |
The money saved is less about card fees and more about the orders you stop losing: the refused delivery, the prank order on a busy Friday night, the rider holding cash, and the thirty seconds per order your staff spend transcribing a voice note into the POS while the phone rings.
It also changes the kitchen trigger. When the order is paid before it is cooked, "order received" and "order confirmed" become the same event, which is exactly what a busy kitchen wants.
Other businesses this fits
- Home and small-batch brands — bakers, clothing, cosmetics — already running entirely on WhatsApp with no website at all.
- Clinics and salons — booking plus a deposit to cut no-shows.
- Tuition centres and academies — monthly fees collected against a parent message instead of a cash envelope.
- Distributors — repeat orders from retailers who already message rather than email.
- Service businesses — quote in chat, send a pay link for the deposit, start work.
What you need before you start
- A WhatsApp Business Account on the Cloud API — not the consumer WhatsApp Business app. A number already registered in the normal app cannot simultaneously run on the Cloud API, so plan which number does what before you begin.
- A catalogue set up with your products or menu, with correct prices — the totals come from these.
- A payment gateway account that can mint a checkout link per order and tell your system when it is paid.
- Somewhere for the confirmation to land — a webhook endpoint, or simply the merchant portal if you do not have a system to integrate.
Chatbot or human: pick deliberately
A bot is excellent at the mechanical parts — sending the catalogue, taking the cart, issuing the pay link, confirming payment, answering where-is-my-order. It is poor at the things that actually keep customers: a substitution when an item is out, a complaint, anything unusual.
The arrangement that works is a bot that handles ordering and payment and hands off cleanly to a person for everything else. One practical warning from running this ourselves: a number registered on the Cloud API cannot also be answered in the WhatsApp app on a phone, so your bot number and your human support number need to be different numbers.
How Rapid Gateway does it
Rapid Gateway runs WhatsApp Commerce against your own WhatsApp Business Account — you keep your number, your catalogue and your customer relationships. When a customer sends a cart, the order webhook is matched to your account, the total is computed from the line items, and the bot replies with a "Pay now" button pointing at a hosted checkout for that order.
The checkout accepts cards, Raast and Raast QR, JazzCash and easypaisa wallets and bank transfer — which matters here, because the customer who orders on WhatsApp is usually a wallet user rather than a cardholder.
On payment, the order is reconciled automatically and your system receives signed whatsapp.order.created and whatsapp.order.paid events, so your kitchen display, ERP or order sheet can act on confirmed orders without anyone watching the chat. Your WhatsApp credentials are stored encrypted.
⚠️ Setup is guided rather than self-serve today: connecting your WhatsApp Business Account to Rapid Gateway is something we do with you, not a one-click install. Talk to our team if you want it switched on for your shop or restaurant.
Frequently asked questions
Can customers pay inside WhatsApp in Pakistan?
Not natively — WhatsApp in-chat payments are not available in Pakistan. The workable approach is a payment link sent into the chat: the customer taps a button, pays on a hosted checkout, and returns to the conversation. From the customer side it is two taps and they never leave the thread for long.
Do I need a website?
No. That is a large part of why this suits Pakistani sellers — plenty of businesses run entirely on WhatsApp and Instagram with no site at all. The catalogue is the storefront and the pay link is the checkout.
Can I keep using my existing WhatsApp number?
A number can run on the Cloud API or in the WhatsApp app, not both. Most businesses move their public ordering number to the API and keep a separate number for staff to answer personally. Decide this before migrating, because moving a number is disruptive to customers who have it saved.
What happens if the customer never pays?
The order simply stays unpaid and nothing is dispatched. That is the point: with cash on delivery an abandoned order still costs you a rider and the food, whereas an unpaid pay link costs you nothing.
Is this the same as a WhatsApp broadcast tool?
No. Broadcast and marketing tools push messages out. This is about taking an order and collecting the money for it. They can coexist, but be careful with marketing blasts — WhatsApp penalises businesses that generate blocks and reports, and losing the number hurts far more than a campaign gains.
The bottom line
You almost certainly already sell on WhatsApp. The gap is that the conversation ends in cash. A catalogue plus a pay link closes it — the customer pays before you cook or ship, and your system finds out without anyone squinting at a screenshot. Talk to our team about enabling it, or read how to integrate a payment gateway in Pakistan if you also sell on a website.