Receive a signed event
Configure an HTTPS webhook destination and validate the documented signature in constant time. Match the order ID and amount to your own database before changing a purchase state.
TRUST GATEWAY · UPI PAYMENTS
Automate payment updates without trusting the browser.
A webhook can tell your server that a payment event is ready to process. The status API lets your server check a saved order when a webhook is late, missed, or being investigated. Use both as server-side signals.
01CreateServer-side order
→02CollectHosted UPI checkout
→03ConfirmVerified business outcome
Use status as recovery
Your server can fetch the status of a known order with its merchant key. This is useful when a callback is delayed, a customer returns to your site, or a background reconciliation job runs.
Fulfil once
A webhook can be retried and a status endpoint can be called many times. Use a unique gateway-order record and an atomic local fulfilment update so one successful payment creates one business outcome.
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 fulfil an order using only the browser success page?
No. Browser-controlled signals can be changed or interrupted. Use a verified server-side status check or validated webhook.
What should my webhook handler do first?
Validate the signature, locate the stored local order, compare its ID and amount, then make the fulfilment action idempotent.
What if a webhook is missed?
Use the authenticated status API against the same saved gateway order; do not create a replacement order blindly.
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.