Skip to content

Payouts

Pay vendors, partners and staff on a schedule you can see.

Single or batch payouts to bank accounts and UPI IDs, with account verification before the first rupee moves and approvals that match the amount. Every simulator on this page is labelled and reversible.

Run a payout simulationSee the API
Your accountVendorStaffPartner
Illustrative. Routes and banks are schematic.

Monitor

What the disbursal screen shows.

A table of payouts with their rail, status and UTR. Below, a feed advances sample rows so you can see statuses change — it is explicitly simulated and pausable.

Disbursal monitor

Sandbox demo

Demo environment — no real transaction is performed.

Six sample payouts moving through queued → sent → processed. The feed is a timer over fixed rows; it is not live traffic.

Simulated feed · playingFeed playing
Available balanceSandbox demo
₹83,05,401Sample float
In flightSandbox demo
3Queued or sent to bank
Processed this runSandbox demo
20 feed ticks
  • Test Merchant SuppliesProcessed (simulated)
    Amount
    ₹1,84,500.00
    Rail
    IMPS
    UTR
    SBX1PZ3U1PHIL54O
  • Sample Logistics LLPSent to bank
    Amount
    ₹42,300.00
    Rail
    NEFT
    UTR
    —
  • Customer refund · demo_order_a1b2c3dProcessed (simulated)
    Amount
    ₹2,499.00
    Rail
    UPI
    UTR
    SBX1PF4MNRU5GBBE
  • Placeholder TextilesQueued
    Amount
    ₹3,25,000.00
    Rail
    RTGS
    UTR
    —
  • Sandbox Farm ProduceReturned
    Amount
    ₹12,000.00
    Rail
    IMPS
    UTR
    —
  • Demo Traders and SonsQueued
    Amount
    ₹58,000.00
    Rail
    NEFT
    UTR
    —

Rails

A timetable, not a promise.

The bank transfer rails a payout can use, described by their operating window and what they suit. Limits are shown in the dashboard rather than quoted here.

Payout rails
RailOperating windowTypical timingGood forNotes
IMPSRound the clockWithin minutesUrgent vendor and refund payoutsPer-transaction limit shown in your dashboard
NEFTRound the clock, in batchesNext batch, usually under an hourScheduled salary and supplier runsBatch timing depends on the receiving bank
RTGSBank working hoursNear real time during the windowHigh-value transfersMinimum amount applies; shown before you confirm
UPIRound the clockWithin secondsPayouts to a UPI ID instead of an accountDaily caps depend on the beneficiary's bank

Try it

One payout, start to UTR.

Verify the account, collect approvals, disburse. Try IFSC SBXB0004321 with account 221133445566 and the name “Sample Logistics LLP” to see an exact name match.

Single payout

Sandbox demo

Demo environment — no real transaction is performed.

Verify the account with a simulated ₹1 deposit, collect the approvals your tier needs, then disburse and receive a UTR.

Compared with the name the bank returns.

9 to 18 digits.

11 characters, e.g. SBXB0001234. A sample label appears when it is well-formed.

₹

Tier shows once you enter an amount.

No deposit is made.

1 · Verification

Fill the form and verify. The registered name from the bank appears here.

Bulk

Five rows in, five UTRs out — or a clear list of what failed.

Batch files are validated row by row before anything is queued. Break a row in the sample to see how errors are reported.

Batch payouts

Sandbox demo

Demo environment — no real transaction is performed.

Paste a CSV with the columns name, account_number, ifsc, amount, purpose — or load the five-row sample. Invalid rows are reported and skipped, never silently dropped.

Header row first. Amounts in rupees.

Validation summary and results appear here.

name

text

Beneficiary name as held at the bank

account_number · ifsc

digits · 11 chars

Or a vpa column for UPI payouts

amount · purpose

rupees · enum

Amount in rupees here; the API takes paise

Approvals and limits

Maker, checker, and a third pair of eyes when the amount warrants it.

Tiers are configured per account. This configurator runs the same rule the simulator above uses.

Approval tiers configurator

Set a limit per tier and how many approvers it needs. Enter an amount to see who must sign off.

Sandbox demo
Tier 1
₹
Tier 2
₹
Tier 3
₹
₹
Tier 2₹2,50,000 needs 2 approvers
  1. MakerDone
  2. CheckerDone
  3. ReleasedWaiting

API

Create a payout in one request.

Sandbox host, pv_test_ key, amounts in paise. Send an Idempotency-Key so a retried request never pays twice.

Webhook verification
Sandbox demo
# Sandbox endpoint — illustrative, never moves moneycurl -X POST https://api.payvendors.example.invalid/v1/payouts \  -u pv_test_7k3q9z1a2b3c4d5e6f7g8h9j: \  -H "Content-Type: application/json" \  -H "Idempotency-Key: demo_po_a1b2c3d" \  -d '{    "amount": 1845000,    "currency": "INR",    "mode": "IMPS",    "purpose": "vendor_payment",    "beneficiary": {      "name": "Test Merchant Supplies",      "account_number": "100200300411",      "ifsc": "SBXB0001234"    }  }'

Request anatomy

amount
integer (paise)₹18,450.00 is 1845000
mode
IMPS · NEFT · RTGS · UPIOmit to let routing choose
purpose
enumvendor_payment, salary, refund, commission…
beneficiary
objectname, account_number, ifsc — or a vpa for UPI
Idempotency-Key
headerRetries with the same key return the same payout

FAQ

Questions, answered plainly.

All questions

A small deposit (typically ₹1) sent to the beneficiary account so the bank returns the registered name. You compare it with the name you were given before releasing the real payout. The simulator here returns role-based sample names.

Ready when you are

Pay out from the same ledger you collect into.

Create a sandbox key, then run your first test payout from the dashboard or the API.

Create a test API keySee how settlement works

Sandbox keys never move money.