1
Upload the payouts
Start with a CSV or send the batch from your own system.
Mass Payouts
Prepare a payout batch before you send it
Upload payouts by CSV or API, catch bad rows, complete any required approval, process the batch, and see the result of each payout.
CSV or API uploadRow validationBatch reviewCSV results
Provider, country, currency, payout-method, approval, and production access are confirmed for each workspace.
Four clear steps for every payout batch
Uploading and sending are separate steps. The batch stays in draft until someone reviews and processes it, with approval added where your workspace requires it.
2
Catch bad rows
Find missing fields, invalid values, and beneficiary references that do not match.
3
Review and process
Check the batch, complete any approval that applies, and process the accepted rows.
4
See results and export
Review each payout status and reason, then download the current results as CSV.
Review the row, not just the batch total
Open a payment run to see the original payout details, what happened to each row, and the reason when something needs attention.
Keep the source row beside the payout
See the original reference, beneficiary, amount, currency, and memo while you review the result.
Give every problem a clear reason
Use reason codes and plain status explanations instead of guessing from the batch total.
Keep approvals under control
If your workspace requires approval, the batch waits for the right person before the next action is available.
Go deeper on payout batches
Start with the complete batch flow, then open the payment-run guide for a closer look at individual payout results.
Frequently Asked Questions
What is a payment run?+
A payment run is a payout batch. It keeps the imported rows, individual payouts, current statuses, and downloadable results together.
Can I start with a CSV?+
Yes. Upload a CSV with the beneficiary, amount, currency, and any reference or memo your team needs. You can also send structured batch items through the API.
Does uploading a batch send the payments?+
No. Uploading creates a draft batch. Someone must review and process it, and an approval or execution step may also apply to your workspace.
What can the team review and download?+
The payment-run view can show the source reference, beneficiary, amount, payout status, reason code, and a plain explanation for each row. The current results can be downloaded as CSV.
Start with a sample payout file
Bring the columns, review steps, and approvals your team uses today. We'll map how the batch is checked, processed, and exported.
Talk through your payout flow