Collecting payments on WhatsApp: UPI, links, reminders and receipts
The invoice that gets paid is the one that arrives where the customer already is, with a button. Linkubit sends a payment request in the WhatsApp thread — an in-chat UPI card where the number supports it, a link from your own gateway otherwise — writes the receipt into the conversation, and reminds about a balance or a renewal before it is due.
Linkubit sends a payment request on WhatsApp at the price on your catalogue, as an in-chat UPI card or a payment link from your own gateway account, records the payment against the deal when it lands, writes the receipt into the thread, and reminds about balances, instalments and renewals with a link. The money goes to your account; Linkubit is never in the flow of funds.
What it asks for
- What is being paid for — the catalogue item and quantity
- Full payment or a balance, and by when
- GST details for the invoice, where needed
- Preferred method — UPI, card, net banking
- Who to send the receipt to
None of this is hardcoded. It is a schema you edit, which is why a completely different business runs on the same system.
Paid without leaving the chat
An in-chat UPI card, or a link from your own gateway
On a number with WhatsApp Payments enabled the request is a card the customer pays with any UPI app. Otherwise it is a link from the Razorpay account you connected. Either way the outcome lands in the thread as a receipt.
- The payment closes the deal at the paid amount
- A failed or expired request is retried once and then flagged
Step 1 · Introduction
Sent · opened twiceStep 2 · Case study
Sent · repliedReply received
“Interested — can you call Tuesday?”
Step 3 · Break-up email
cancelledReminders that are not nagging
A balance is reminded a few days ahead, with the link
Instalments, renewals, the balance before a departure — reminded once before the date with the amount and a button, matched automatically when the customer says "already paid", and escalated to a person after the date rather than repeated.
- Reminders are utility templates about a transaction the customer started
- A 'paid' reply is checked against the gateway, not taken on trust
Last inbound message · yesterday, 6:12 pm
Free-form replies are locked — send an approved template
The rule that holds
The amount is a catalogue price, never a number from the chat
A payment request names products and quantities; the amount is worked out from your price list. A customer who negotiated in the thread is charged what a person entered on the dashboard, not what the model understood. The money goes to your gateway account; Linkubit holds no funds.
Anything else goes to a person
A topic you named, a value above a threshold, a customer who asks for a human, or a question the assistant cannot answer from what you gave it — the conversation is handed over before a reply is written, with the whole thread and every field captured so far.
From agreed to paid, in the thread
What collection looks like when the request, the receipt and the reminders are handled, and a person decides any amount that is not on the list.
The agreement becomes a request
"Two sessions, ₹4,000 — pay here." The amount comes from the catalogue; the assistant sends the card or the link and tells the customer what it covers.
Paid, and written down
The gateway confirms; the deal closes at the paid amount; a receipt with the reference goes into the thread; a person is notified only if you asked to be.
A balance, reminded before it is due
Five days out, one message with the amount and the link. On the day, one more. After that, a person — never a fifth reminder.
"Already paid" is checked
The assistant matches the claim against what the gateway received and says so, rather than arguing or apologising.
Renewal and repeat
A membership, a plan, an annual service — reminded before expiry with the renewal amount and the link, as a consented message with a STOP line.
The templates it sends
6 WhatsApp message templates from the industry packs that carry this use case, each written the way Meta's review reads it. Open one for its variables, a filled example and what gets it rejected.
| Template | Category | When it goes out |
|---|---|---|
| Invoice due | Utility | Three days before an invoice is due, and once on the day. |
| Fee due | Utility | An instalment is due in five days. |
| Balance due | Utility | A balance is outstanding after a visit. |
| Balance due | Utility | The balance is due in seven days. |
| Instalment due | Utility | A construction-linked instalment is due in five days. |
| Booking amount received | Utility | The token or booking amount has landed. |
Each template opens on its own page with the variables, a filled example and what Meta’s review objects to. Utility and authentication templates cost ₹0.115 a message in India, marketing ₹0.8631 — the pricing guide has the rest.
Questions people ask
Where does the money go?
To your own account. The in-chat card uses the payment configuration you made in WhatsApp Manager; the link comes from the Razorpay account you connected. Linkubit stores no card details and holds no funds.
Can the AI decide a discount?
No. The amount is the catalogue price times quantity. A rep can type a custom amount on the dashboard — a person decided it — and the assistant sends that.
Does it send invoices?
It sends the payment request and a receipt with the gateway reference. An invoice PDF you attach is sent alongside; the GST details it asked for are on the record for it.
What if a customer pays outside WhatsApp?
Mark the request paid on the dashboard, or let the assistant match it when the gateway reports it. Either way the reminders stop and the receipt is sent.
Read next
Ready to put your sales on autopilot?
Start freeNo coding required. No credit card required.