Every hop between "I will pay" and "payment received" is a place the money stops moving.
Why collection improves on WhatsApp
An emailed invoice requires the customer to find the email, open the PDF, find the link and pay. Each of those steps loses people, and none of them happen on the phone they are holding.
A payment request in a chat with a pay button collapses that into one tap, and the reminder arrives on a channel where it will actually be seen.
Order details templates
This is the format Meta designed for the job: an itemised order with amounts and a native pay button. It is a utility template, so it is approved before use and charged at the lower utility rate.
Order status templates handle the follow-up as the payment or order moves, which is what stops the customer messaging to ask.
Connecting a gateway
- Razorpay connects to WhatsApp native pay
- PhonePe connects to the payments ecosystem
- Stripe is available as a payment step inside automation flows
- Where native pay is unavailable, a payment link is sent in the chat instead
Three flows worth building
- Dues campaign: a payment request to every contact with an outstanding amount, personalised by amount and due date.
- In-conversation payment: the bot takes the order, then asks for payment in the same thread.
- Failure recovery: a payment that fails triggers an immediate message with a retry link rather than silence.
The failure path is where the money is
Most teams build the success path and forget the failure one. A failed payment with no follow-up is a customer who intended to pay and did not, which is the easiest revenue there is to recover.
Both outcomes can trigger their own message or an entire bot flow, so a failure can ask whether it was a card problem or a change of mind and route accordingly.