Show the right details
Before paying, the customer should see the business identity, receiving account, exact total and order window. Checkout branding can improve recognition, but it does not replace payment verification.
TRUST GATEWAY · UPI PAYMENTS
Give every UPI payment request its own checkout.
A hosted checkout turns a server-created order into a readable QR and UPI app handoff. It keeps the payment request tied to a known order instead of relying on a generic QR image.
01CreateServer-side order
→02CollectHosted UPI checkout
→03ConfirmVerified business outcome
Support phone and desktop
On a phone, customers can continue to a supported UPI app. On desktop, they can scan the QR from a second device. Both paths lead to the same saved order.
Keep pending orders safe
If a customer returns from a UPI app while the order is pending, keep the purchase awaiting confirmation. Do not ask them to pay the same QR again until the original order is reconciled.
BUILD WITH CONTEXT
Use the right reference for each step.
Trust Gateway is designed around saved orders and server-side verification. Start with the documentation, then use these practical guides while you implement your checkout.
COMMON QUESTIONS
Answers before you build.
Can I use my own logo on the checkout?
Merchants can configure checkout branding. Customers should still verify the receiver and amount inside their UPI app.
Does opening a UPI app mean payment succeeded?
No. Treat app handoff as navigation only; fulfil only after server-side confirmation.
What happens when a QR expires?
An expired checkout should not accept a new attempt. Investigate any claimed late payment using the original order record first.
NEXT STEP
Open API docs ↗Test one complete order.
Create a controlled payment request, check the receiving identity, and confirm the same saved order before you use it with customers.