UPI was never the missing piece — it's been sitting in the payment gateway all along. The actual gap was what happened between the customer saying yes on WhatsApp and the payment landing: a link, a browser, a page that isn't WhatsApp anymore.
Here's the part of “pay by WhatsApp” that nobody advertises: the customer says yes in the chat, and then leaves it. A link arrives. It opens a browser tab. The page it lands on doesn't look like the conversation they were just having — different branding, a different feel, sometimes a moment of "wait, is this actually rePUSHTI, or the hotel, or the agent, or something else entirely." They pay, then have to come back and confirm they did. Every one of those steps is a place a customer can stall, get distracted, or simply not bother finishing.
Where the money actually moves in a travel business
Payment collection in travel isn't one flow — it's several, and all of them tend to happen in the same place: a WhatsApp conversation.
- A B2C customer completing a booking directly with an OTA or travel seller
- A concierge or offline booking, arranged in conversation rather than through a storefront
- A B2B agent topping up their own account credit, to keep booking without a delay
In every one of those, the conversation and the payment are the same moment for the customer — right up until the platform makes them two separate ones.
UPI was already there. The friction wasn't UPI.
UPI has been one of the payment methods available through rePUSHTI's gateway for a while — rePUSHTI's partnership with PayU already put UPI, cards and net banking into a payment link sent straight into a WhatsApp conversation. That was a real improvement over emailing a separate checkout page. But it was still a link — tap it, and the customer leaves WhatsApp for a browser to actually pay.
The method was never the bottleneck. The handoff was.
What “native” actually means here
rePUSHTI has built UPI checkout that runs inside the WhatsApp conversation itself. Not a link that opens a browser. Not a redirect to a page hosted somewhere else that the customer has to trust is legitimate. The payment happens in the same thread the quote and the yes happened in — nothing to open, nothing to leave, nothing that looks unfamiliar at the one moment a customer is about to hand over money.
UPI checkout running entirely inside a WhatsApp conversation.
Why this matters more in travel than most industries
Travel runs on thin margins and awkward timing — a quote can go stale in minutes, and every extra step between "yes" and "paid" is a place a booking can fall through. It's also an industry that already lives on WhatsApp more than most: a concierge arranging a same-day request, an agent needing credit topped up before they can make their next booking, a traveller confirming a price on their phone from an airport lounge. None of those moments have a browser tab already open and waiting.
The booking happened in a conversation. The payment should never have needed to happen somewhere else.
Built on the same partnership, taken further
This runs on the same rePUSHTI–PayU partnership behind UPI, card and net-banking payments generally — nothing about the underlying rails changed. What changed is that UPI specifically no longer needs to leave WhatsApp to be collected. Cards and net banking still route through a checkout page, for the ordinary reason that neither has a native in-chat equivalent the way UPI does.
As far as we've seen, no other platform serving travel businesses has built this — every version of “pay by WhatsApp” we've come across still hands the customer off to a browser at the exact moment they're meant to pay. This is the version that doesn't.
