Bulk payouts
A payout file that is validated before anybody approves it, approved as a batch, and reports per row — so one bad line does not fail the payroll and does not get paid twice on the retry.
Employers running payroll, NGOs distributing stipends, cooperatives paying members, platforms paying sellers.
Part of the platform itself: it is present wherever BitriPay runs.
The problem
A file of two hundred payments either fails entirely on one malformed line, or part-succeeds and leaves somebody guessing which half to re-run — and re-running the wrong half pays people twice.
How it works
- Upload the file; it is validated and the errors are reported before anything is approved.
- Fix the rows that are wrong and re-upload, or proceed without them.
- Approve the batch; approval is a deliberate act, separate from uploading.
- The batch executes and reports per row: paid, failed, with the reason.
What you can check
Facts about the running platform rather than adjectives. Each one is visible in the product, the API reference or the ledger.
- The file is validated before approval, so errors are found while nothing has moved.
- Outcomes are per row, so a failure is attributable to a line rather than to the file.
- Approving is separate from uploading, so nobody pays two hundred people by pressing the wrong button once.
- A batch has a bounded number of rows and a documented column layout, so a file either conforms or is rejected with a reason.
- Batch events are published, so a payroll system can react to the outcome rather than polling somebody’s inbox.
What it costs
Payouts are priced individually at the ordinary rate for the rail; there is no separate charge for sending them as a batch.
Questions
One row failed. Do I re-run the file?
No — and this is the mistake that causes double payments. Outcomes are reported per row, so you re-run only the rows that failed. The file is not an all-or-nothing object.
Who can approve a batch?
Approving is a separate action from uploading, so the person preparing payroll is not necessarily the person releasing it. For most organisations that separation is the point.
What happens if my file is wrong?
You are told which rows and why, before anything is approved and before any money moves. Fix them and re-upload, or proceed without them.
Read next
Withdrawals and payouts
A payout that is held against your balance the moment you request it, executed under four eyes above a threshold, and reversed on the ledger if the rail refuses — so money is never both spent and still spendable.
Team and roles
Staff get their own sign-in with a role the software enforces every time, including a refund limit the owner sets — so delegating the counter does not mean handing over the business.
Signed webhooks
Deliveries you can verify two independent ways, replay yourself from the dashboard, and receive on a built-in inbox if you have nowhere to host an endpoint yet.