WhatsApp payments: collect UPI inside the chat, at your catalogue price
The moment a customer says yes is the moment a link to another site loses them. Linkubit puts the payment where the conversation is: a card in the WhatsApp thread, priced from your catalogue, paid by UPI or card into your own account. The deal closes itself when the money lands, and a person is told when it does not.
The assistant or a rep requests a payment naming products and quantities; the amount is the catalogue price times quantity, never a figure from the chat. On a WhatsApp number with a payment configuration, inside the 24-hour window, the request is Meta's in-chat order card — UPI, cards, net banking. Anywhere else it is a payment link from your own Razorpay account. A paid request writes the receipt into the thread, closes the deal at the paid amount, and the money goes to your gateway account, never through Linkubit.
The price is the catalogue's
A payment request is products and quantities, nothing else
The assistant cannot invent an amount. It names product keys and quantities, and the total is priced from the catalogue — the same catalogue it quotes from. A rep may type a custom amount, because a person decided it. What the customer said they would pay is kept beside it, as they said it.
- A figure without a currency is asked about once, and the deal is written in yours
- Half a credit per request; Meta and your gateway bill their own fees to you, unchanged
quote_rates blocked — volume not captured yet
Sales Agent
Paid means won
The deal closes when the money lands
A payment outcome arrives from Meta or Razorpay, the thread gets a "Paid ₹1,299 by UPI" line, the deal is closed at the paid amount, and the revenue is recorded against the touchpoints that produced it. A failed or expired payment is a task for a person, not a silent gap.
- Captured never regresses: a late webhook cannot reopen a paid order
- A payment is not a message — it does not reopen the WhatsApp window
Qualifying
Sundaram Textiles
24 TEU/mo · FOB pending
Quoted
Drop refused
Won
Move to Quoted refused — Incoterm is required to enter this stage
The rest of it
Two rails, chosen by the situation
Meta's in-chat card needs a WhatsApp number with a payment configuration, an Indian-rupee amount and an open window. When any of those is missing, a Razorpay payment link from your own account is sent instead — the same request, the same closing of the deal.
Your gateway, your money
Linkubit is never in the flow of funds. The in-chat rail uses the payment configuration you made in WhatsApp Manager; the link rail uses your own Razorpay keys, stored where only the sender can read them. A refund is yours to make in your gateway.
One request, one send
A request is claimed before it is sent, so the assistant's attach, a retry and a rep's resend cannot all reach the customer. A link left unsent because the sender lacked the key is picked up by the next sweep.
A failed or lapsed payment is an event, not a gap
A declined payment is written into the thread and publishes an event a workflow can act on — a task for the owner, a message to the customer. A request that passes its expiry is marked expired by the sweep, so a rep sees what lapsed rather than a request that looks pending forever.
What it is made of
Take the payment inside WhatsApp
Customer’s ready, a UPI card with your catalogue price appears in the chat, they pay, and the deal is marked won with the revenue recorded. Money goes straight to your account.
Deals open themselves, priced from the catalogue
When a lead qualifies, the products they showed interest in become one open deal at your list price. The value is never a figure the assistant said in a chat — those are unverified — it is what the catalogue says.
It can only quote prices from your catalogue
The assistant cannot invent a number. A price it states has to come from a product it just looked up. Same for photos: only a product it actually read this turn.
A figure without a currency is asked about, once
A customer who says “around 5,000” gets asked whether that is rupees or dollars — once, not every turn. What they said is kept as they said it; the deal is written in your currency so every forecast adds up.
Questions people ask
Do I need a payment gateway account?
You need your own — the in-chat card uses the payment configuration you set up in WhatsApp Manager with a gateway Meta supports, and the link uses your own Razorpay account. Linkubit stores the name of the configuration and your Razorpay key pair, and holds no money at any point.
Can the assistant discount the price?
Not on its own. The amount is the catalogue price; a discount past the limit you set is drafted as an approval for a person, and a rep can type a custom amount because a person decided it.
What if the customer pays outside WhatsApp?
The link rail covers email and Instagram, and a WhatsApp chat whose 24-hour window has closed. The receipt, the deal close and the revenue are recorded the same way whichever rail carried it.
Is the in-chat card available to every business?
Meta enables WhatsApp Payments in India per app and per business, and the settings screen reads what Meta offers rather than letting you type a name. If Meta has not enabled the card on your number, a payment link is sent instead, so collecting never waits on it.
Read next
Ready to put your sales on autopilot?
Start freeNo coding required. No credit card required.