Create a clear request
Use a specific title, fixed amount, and optional expiry. Keep the business context in your own invoice or client message so both sides can identify what the payment is for.
TRUST GATEWAY · UPI PAYMENTS
Share a payment request your client can understand.
A payment link is useful when you want to collect a fixed amount without embedding a checkout in your own website. The merchant creates it in the dashboard, shares the URL, then checks the result before closing an invoice.
01CreateServer-side order
→02CollectHosted UPI checkout
→03ConfirmVerified business outcome
Share the hosted URL
Send the link through your normal client channel. The recipient can open a hosted checkout and pay through a UPI QR or app handoff without receiving your merchant credentials.
Reconcile before closing work
Check the payment order and your receiving record before marking work complete. A client message, screenshot, or return-page visit can start an investigation but is not final payment evidence.
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 set an expiry on a payment link?
Yes. An expired link should not be treated as a fresh payment request; create a new one after checking the earlier attempt.
Can one link replace an invoice?
The link collects the amount. Keep your own invoice, scope and client agreement as the business record.
Should I ask a client for their UPI PIN or OTP?
Never. Those are secrets and are not needed to check a merchant order.
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.