National Automated Clearing House (NACH)
NPCI's system for high-volume, repetitive bank transfers — bulk credits such as salaries and dividends, and debits against mandates such as loan instalments.
AI-Powered Financial InfrastructureGlobal PaymentsSecure & Trusted
Pay & Move Money · Bulk PayoutsPay a whole batch in one action — and track every payout in it.
Submit a batch of transfers to bank accounts and UPI IDs in one action, from the dashboard or in a single API request, and follow each payout in the batch from initiated to completed.
- One batch, one action
- Bank and UPI
- Tracked per payout
- Failures you can fix
In short
Bulk Payouts is how Paynancial Payouts handles many payments at once: you submit a batch of transfers — to bank accounts or UPI IDs — in one action from the dashboard or in a single API request, and each payout in the batch is tracked individually, with a clear reason for any that fail.
Overview
What bulk payouts mean on Paynancial.
Paying many people one transfer at a time is slow, and it is easy to miss one or pay one twice. Bulk payouts turn a list of payments into a single batch you submit once.
On Paynancial, bulk payouts are part of Payouts. The batch is submitted in one action, but every payout in it keeps its own status — so a single failed transfer does not hold up the rest, and you can see exactly which one needs attention.
How it works
Step by step.
- 01Prepare the batch
List the beneficiaries — saved bank accounts or UPI IDs — and the amount for each.
- 02Submit once
Submit the batch in one action from the dashboard, or in a single API request.
- 03Processed
Paynancial processes each transfer and returns a status for each.
- 04Track each payout
Follow every payout from initiated to completed; failed ones come with a clear reason.
- 05Fix and report
Correct and retry any failures, then find the completed batch in your payout report.
Capabilities
What you can do.
- Batch submission
- Submit a batch of transfers in one action or a single request.
- Per-payout status
- Each payout in the batch is tracked individually.
- Failure reasons
- A failed payout comes with a clear reason so it can be corrected and retried.
- Saved beneficiaries
- Reuse bank and UPI details you have already saved.
- Duplicate protection
- An idempotency key on each payout means re-running a batch after a timeout never pays anyone twice.
- Payout events
- Payout webhooks tell your systems as each payout changes state.
Where it lives
Across the Paynancial platform.
Bulk Payouts is not a separate system — it runs through the products and tools you already use.
| Where | What you get |
|---|---|
| Dashboard | Submit and follow a batch without writing code. |
| API | Submit a batch in a single request. The published example shows one payout on POST /payouts with an idempotency key; ask developer support for the batch request format. See the API Reference. |
| Webhooks | An event as each payout in the batch changes state. See Webhooks. |
| Payout report | Completed payouts appear in your payout report. See Payment Analytics. |
Compliance in India
The RBI and NPCI rules around bulk payouts in India.
A plain-language guide to the frameworks that apply. It is general information, not legal advice, and not a statement of Paynancial's own licences or authorisations.
Immediate Payment Service (IMPS)
NPCI's round-the-clock instant interbank transfer service, to a bank account or mobile number.
UPI procedural guidelines and circulars
NPCI operates UPI and sets its rules for member banks, UPI apps and other participants through procedural guidelines and circulars, including transaction limits, dispute handling and security requirements.
Turn Around Time (TAT) for failed transactions
Sets the time within which failed digital transactions — for example, a customer debited without the merchant being credited — must be reversed or resolved across authorised payment systems such as UPI, cards and IMPS, and the compensation due to the customer when that time is missed.
Regulators update these rules by circular, so always check the current text at the source: Reserve Bank of India · NPCI. For Paynancial's own security and compliance posture, see the Trust Center.
Good practice
Getting it right.
- 01One idempotency key per payout
Use a key built from your run ID and the beneficiary, so re-submitting a batch is always safe.
- 02Handle failures individually
Fix and retry the failed payouts only — the rest of the batch has already moved.
- 03Check the batch before you submit
Totals and beneficiaries are easier to correct before money moves than after.
FAQ
Bulk Payouts questions.
What are bulk payouts?
Paying many beneficiaries at once. With Paynancial Payouts you submit a batch of transfers in one action from the dashboard, or in a single API request, and each payout in the batch is tracked individually.
Can a bulk payout include both bank and UPI transfers?
Payouts can be sent to bank accounts and UPI IDs. Ask our team how to structure a mixed batch for your business.
What happens if one payout in a batch fails?
It fails with a clear reason and can be corrected and retried. The other payouts in the batch are unaffected.
How do I avoid paying someone twice if I re-submit a batch?
Send an idempotency key with each payout. Re-submitting with the same key returns the original payout instead of creating a new one.
Talk to us about bulk payouts.
Tell us how your business takes and moves money, and we will show you how it fits.