Settlement
Know exactly when money reaches your account.
Every settlement batch carries the UTR your bank prints, a statement that lists each order, fee and tax line, and a net you can match to the rupee. Try the lookup with the sample UTRs.
Settlement ledger (sample)
Three days, three batches
- 14 Oct 2026
- SBX26101500A1 · ₹26,849.04
- 13 Oct 2026
- SBX26101400B7 · ₹88,705.94
- 15 Oct 2026
- SBX26101600C3 · ₹31,112.01
Perforated like a real statement: every line can be torn off and matched.
Try it
From a bank reference to the orders behind it.
Paste a UTR and get the batch, its orders and the fee lines. Unknown references return a clear not-found state instead of a pretend match.
UTR lookup
Sandbox demoDemo environment — no real transaction is performed.
Enter the bank reference printed on your statement. The sandbox recognises the three sample UTRs below and answers “not found” for anything else.
The settlement route
Orders become a batch; the batch becomes a credit.
Four stages, each with a record you can see in the dashboard and fetch from the API.
- CapturedPayment succeeds; order marked paid
- BatchedGrouped at the cut-off for the cycle
- SettledBank credits your account with a UTR
- ReconciledStatement lines match your records
Cycles
T+1 is a description, not a guarantee.
Cycles are configured per account and depend on the payment method and the bank. We describe the options and point you to where your actual cut-off is shown.
| Cycle | What it means | Cut-off | Notes |
|---|---|---|---|
| T+1 | Captured today, credited the next working day | Shown in your dashboard | Common default for card and UPI collections |
| T+2 | Credited two working days after capture | Shown in your dashboard | Used where an extra review window is configured |
| Same day | Multiple batches within the day | Per batch | Configurable for eligible accounts; never assumed |
| On hold | Batch paused pending a check | — | You see the reason on the batch and in the support portal |
- Gross
- ₹1,250.00
- Fee (sample 2%)
- − ₹25.00
- Tax on fee (as applicable)
- − ₹4.50
- Net
- ₹1,220.50
Illustrative rates. Your pricing is agreed before you go live and printed on each statement.
# Sandbox endpoint — illustrativecurl https://api.payvendors.example.invalid/v1/settlements?utr=SBX26101500A1 \ -u pv_test_7k3q9z1a2b3c4d5e6f7g8h9j:Reconciliation
One statement, three places it lines up.
Dashboard columns, statement columns and API fields use the same names so your finance team and your developers reconcile the same thing.
| Dashboard | Statement column | API field |
|---|---|---|
| Settlement ID | settlement_id | settlement.id |
| Bank UTR | utr | settlement.utr |
| Order | order_id | order.id |
| Payment | payment_id | payment.id |
| Gross amount | gross | payment.amount |
| Fee | fee | payment.fee |
| Tax on fee | tax | payment.tax |
| Net credited | net | settlement.net_amount |
What the sample file contains
When numbers differ
FAQ
Questions, answered plainly.
Statements can lag the credit by a few hours. If the UTR is still missing after the next cycle, raise a ticket with the amount and date — the settlement desk can match it from the bank side.
Ready when you are
Reconcile with confidence from day one.
Create a sandbox key and pull a sample settlement from the API.
Sandbox keys never move money.