01
For businesses
Collect, pay out, settle and support — from one junction.
A payment gateway, payouts, settlement statements and a support portal that share one ledger, one set of ids and one sandbox. Everything on these pages runs as a labelled demonstration.
Five pillars
Each product is a stop on the same route.
Orders, payouts, settlements and tickets all carry the same synthetic ids in the sandbox, so what you learn on one page applies to the next.
02
Payouts
03
Settlement
04
Support portal
05
Get started
Instead of metrics
We show you a ledger, not a scoreboard.
Marketing pages often print success rates and volumes nobody can check. This card shows the shape of the data a merchant dashboard holds — with sample values.
What your ledger would show
Sandbox demoDemo environment — no real transaction is performed.
Sample entries only. Add an order to see the tiles move; nothing here reflects real volume.
| Type | Reference | Amount | Status |
|---|---|---|---|
| Order | demo_order_0784b2r | ₹1,250.00 | Captured (simulated) |
| Order | demo_order_07i3wrq | ₹18,450.00 | Captured (simulated) |
| Settlement | SBX26101500A1 | ₹26,780.40 | Settled (simulated) |
| Payout | SBX1IBJGXY1QHSAN | ₹42,300.00 | Processed (simulated) |
Integration at a glance
Create a test order in a few lines.
All samples point at a sandbox host that cannot move money. Keys that start with pv_test_ are the only kind the wizard issues.
# Sandbox endpoint — illustrative, never moves moneycurl -X POST https://api.payvendors.example.invalid/v1/orders \ -u pv_test_7k3q9z1a2b3c4d5e6f7g8h9j: \ -H "Content-Type: application/json" \ -H "Idempotency-Key: demo_order_7k3q9z1" \ -d '{ "amount": 125000, "currency": "INR", "receipt": "shop-1042", "notes": { "customer": "Test customer" } }'What happens to the request
- ReceivedDone
- ValidatedDone
- RoutedDone
- ConfirmedDone
Operating model
Who does what at each stage.
A timetable rather than a promise: the actions on your side, the work on ours, and the record you receive.
| Stage | You do | Payvendors does | You get |
|---|---|---|---|
| Collect | Create an order and open the checkout | Validates, routes and captures the payment | A payment id, a webhook and a receipt |
| Pay out | Add a beneficiary and request a payout | Verifies the account and sends it on the chosen rail | A UTR and a payout record |
| Settle | Nothing — batches run on the configured cycle | Nets fees and taxes, credits your account | A settlement statement keyed by UTR |
| Support | Raise a ticket with the order or UTR | Routes it to the right desk and keeps the timeline | A ticket id and visible status |
Ready to see it with your own numbers?
Walk through the onboarding wizard and come back with a sandbox key.
Prefer a conversation first?
Our contact page lists the office, hours and a form routed to the right desk.
FAQ
Questions, answered plainly.
The business questions we hear most, with the sandbox caveats spelled out.
The gateway is designed for UPI, cards, net banking and wallets through one checkout. The payment gateway page walks through the checkout experience and the integration steps; the checkout there is a sandbox and does not process payments.
Ready when you are
Start in the sandbox. Go live when it's right.
The wizard takes a few minutes and ends with a test key.
Sandbox keys never move money.
