Collect
A customer pays on your storefront, app or link. UPI, cards and net banking arrive on one checkout, each request carrying an order reference from the first second.
See the payment gatewayOne platform
Recharge or settlement, ticket or payout — every route shares the same ledger, the same references and the same sandbox. The rest of the platform is below.
Demos on this site run in a sandbox. No real money moves.
Our services

Prepaid mobile plans for every operator and circle.

Electricity, water, gas, broadband and FASTag.

Search trains, compare classes, hold a seat with a PNR.

Compare fares with every charge itemised before you pay.

Rooms by the night with a booking voucher.

Vendor payouts and settlements, each with a UTR.
Chapter 02 · Every day
A recharge before the metro, the electricity bill on the 5th. Enter the details, review the amount, and keep a receipt with a reference you can look up later.
Sandbox demonstrations — nothing is charged.
Chapter 04 · Collections
Checkout opens, the request is validated and routed, and a result comes back with an order id and a receipt. Here it runs as a labelled simulation.
Simulated checkout — no real authorisation happens on this site.
Chapter 05 · Money out
Payouts move through created, approved, sent and credited. Settlements arrive in batches with a UTR you can trace back to every order, fee and tax line.
All figures shown are illustrative sample values.
Chapter 06 · For builders
Create a test order against the sandbox host with a key that starts with pv_test_, then listen for the webhook. The examples document the shape of the flow.
Documentation samples — not a live integration.
Chapter 07 · When it matters
Receipts you can look up, account checks before a payout leaves, and a support portal where every issue keeps an id, a desk and a visible timeline.
Chapter 08 · The junction
Recharge or settlement, ticket or payout — every route shares the same ledger, the same references and the same sandbox. The rest of the platform is below.

How it works
Every request takes the same route through the junction, whether it is a ₹299 recharge or a month of settlements. Here is what happens at each stop.
A customer pays on your storefront, app or link. UPI, cards and net banking arrive on one checkout, each request carrying an order reference from the first second.
See the payment gatewayThe junction validates the request, formats it for the rail it needs and hands it over — a bank transfer, a biller, an operator. One switch, many tracks.
See how payouts are routedEvery hop reports back. Nothing is marked done until the other side confirms, and every attempt keeps a reference you can look up or hand to support.
Open the support portalCaptured amounts are batched and sent to your bank account with a UTR on every credit, so the money and its paperwork travel together.
See how settlement worksOrders, fees and credits line up on one statement. Match a UTR to its batch and the batch to its orders without leaving the dashboard.
See the operating modelFor businesses
Read it like a timetable: the situation you are in, the surface that handles it, and where to go next. The same junction serves all six.
Not sure which row you are? Start with the wizard — it ends with a sandbox key, not a commitment.
For developers
One request against the sandbox host. Keys that start with pv_test_ never move money.
curl -X POST https://api.payvendors.example.invalid/v1/payments \ -H "Authorization: Bearer pv_test_0000_sandbox_only" \ -H "Idempotency-Key: demo_idem_7f3a21" \ -H "Content-Type: application/json" \ -d '{ "amount": 125000, "currency": "INR", "order_id": "demo_order_0001", "customer": { "contact": "+919876540000" } }'{ "id": "demo_pay_7K3Q9Z1", "status": "created", "amount": 125000, "currency": "INR", "order_id": "demo_order_0001", "sandbox": true}Try the junction
Pick a service, choose a provider, read the itemised fare and authorise. Four hops later you hold a receipt. Nothing here is real.
Demo environment — no real transaction is performed.
Step 1 of 5
Demo only — no money moves. Providers are neutral sample options, not partners.
How we earn trust
You will not find uptime figures, partner logos or certificates on this page. You will find four things you can check yourself, every time.
The amount, any fee and the total sit on separate lines on the review screen. What you read there is what you authorise — nothing is added afterwards.
Read the refund policySample values
Each attempt gets a reference the moment it is created, successful or not. Look it up later, quote it to support, or match it to a bank credit by UTR.
Look up a receiptReference
SBX-1EPRU1T
Issued at creation, kept forever
Working hours, an email address and a registered office are published on the contact page. Support tickets keep a visible timeline so you never repeat yourself.
Go to the contact pageEvery demonstration on this site carries the Sandbox badge, a disclosure line and a SANDBOX stamp on its result. If it is simulated, it says so.
What the badge meansDashed frame · badge · disclosure line · stamp
Questions
The short version of what people ask before they try a demo or integrate. The full list lives on the FAQ page.
Ready when you are
Nothing here asks for a card or a commitment. Try the demos, read the policies and talk to a person when you want to go further.
Sandbox keys never move money.