API Reseller
Payment Gateway API
Order creation, payment capture, refunds and settlement reporting. The webhook is authoritative rather than the browser redirect, because a customer who closes the tab after paying is the normal case, not the edge case.
What you get
- One integration for cards, UPI, net banking and wallets
- Idempotent order creation keyed on your own reference
- Signed webhooks with replay protection
- Full and partial refunds against an original payment
- Settlement reports that reconcile to a single bank credit
The contract
- Auth
- Issued credentials per key pair, over TLS. Signed requests where the rail requires it.
- Idempotency
- Keyed on your own order reference. A repeat returns the original order rather than creating a second.
- Authority
- The webhook, not the browser redirect. A customer who closes the tab still settles correctly.
- Webhook
- Signed, with replay protection. Retried until your endpoint returns 2xx.
- Refunds
- Full or partial against the original payment, each independently tracked.
- Settlement
- Reports reconcile to a single bank credit per cycle.
- Environments
- Sandbox mirrors production semantics, including failures.
FAQ
About payment gateway api
The customer paid but closed the tab before returning. What does my system see?
The webhook, which is the authoritative record. The browser redirect is a convenience and will not always arrive, so an integration that treats the redirect as confirmation will miss real payments. Reconcile against the webhook and the settlement report, never against the return URL.
Can I retry a failed order with the same reference?
Yes, and you should. Order creation is idempotent on your own reference, so a retry returns the original order rather than creating a duplicate. Generating a fresh reference on retry is how a customer ends up with two open orders for one purchase.