Sending a UPI checkout through WhatsApp can be convenient for a small business, but the chat message is only the invitation to pay. The payment order and its verified status must remain in your merchant records. A “paid” reply, forwarded screenshot or blue tick does not settle an invoice.
Create a clear payment request
In the Trust Gateway merchant workspace, create a payment link with a short title and a fixed amount when you know the price. You can add a description and optional expiry. The link creation route stores the amount so the public checkout cannot simply replace a fixed price from the browser. An active merchant subscription and supported receiving setup are required for live use.
Keep your own invoice or job reference beside the link. The link title should help the buyer recognize the request, but avoid putting sensitive personal details in a public URL or title. See the payment links guide for the normal creation flow.
Write a message the customer can verify
Include your business name, what the payment is for, the quoted INR amount and the official trustgateway.in link. Ask the buyer to inspect the payee and exact amount in their UPI app before approving. Keep the message short enough to read on a phone. Never ask for a UPI PIN, OTP or remote screen access. A customer should be able to verify the request without trusting a logo in a chat message alone.
Decide what forwarding means
WhatsApp messages are easy to forward. If the payment is for a particular customer, store that association in your own order or invoice system. A public fixed-amount link is not automatically bound to the phone number that first received it. Do not grant a digital product to the last person who opens or forwards the URL. For private purchases, create a distinct local purchase and map each resulting checkout order to the intended buyer.
When several customers owe the same amount, distinguish their gateway order references instead of matching payments by amount alone. The buyer mapping guide discusses the same ownership principle for chat-based sales.
Check status before closing the conversation
After the buyer says they paid, open the corresponding order in your merchant dashboard or verify it from your server through the authenticated status API. Compare the saved order reference and exact payable amount. A matching adjustment can make the checkout total differ slightly from the price in the initial message, so the customer should pay the total shown by checkout. Only mark the invoice paid after verified confirmation.
If status is pending, tell the buyer you are checking rather than asking them to pay twice. Ask for their UTR only when needed to investigate, and do not treat a typed UTR as automatic proof. Use the manual review checklist for mismatches and late updates.
Keep a usable support trail
Record when you shared the link, the customer or invoice it belonged to, the gateway order ID, payment status and fulfilment decision. Do not keep the API key in the chat or customer-facing receipts. If the link expires, check the earlier order before creating another payable request. That audit trail lets you answer a customer accurately even when the chat is deleted or moved to another agent.