Create one order
Use your private API key from the server with a price calculated from your product catalogue. Save the returned order ID, requested amount and exact payable amount against your own business order.
Your server creates an order. Your customer pays at a hosted QR checkout. Your server checks the same order before it delivers a product or marks an invoice paid.
Use your private API key from the server with a price calculated from your product catalogue. Save the returned order ID, requested amount and exact payable amount against your own business order.
Use the returned hosted checkout URL. It shows the receiver, payment total, QR code and UPI app handoff. A QR scan or browser redirect does not mark an order paid.
Your backend reads the authenticated order status and checks the exact saved order ID and amount. Make the local fulfilment action idempotent so repeated status checks never issue a product twice.
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.
Use a server or serverless function. A browser bundle must never contain a merchant API key.
No. An authenticated status check works as a recovery path; webhooks can notify your app sooner when configured.
Store the gateway order ID with your own order and allow only one atomic transition from unpaid to fulfilled.
Create a controlled payment request, check the receiving identity, and confirm the same saved order before you use it with customers.