Bulk payouts require a process, not only a send button: reason, register, validation, approval, execution and reconciliation. Actual MulenPay payout capabilities, countries, timing and partners must be confirmed separately.
From payout reason to register
Define who receives funds and why: marketplace sellers, instructors, partners or contractors.
Register fields
| Field | Purpose | Risk if missing |
|---|---|---|
| recipient | identification | wrong recipient |
| amount | calculation control | reconciliation mismatch |
| reason | business explanation | recipient dispute |
| unique ID | duplicate protection | repeated payout |
Roles and approval
One person prepares the register, another validates it and a third approves it. This reduces accidental changes and duplicates.
Errors and repeated payouts
Incorrect details, duplicates and partial execution should be tracked as process states, not corrected manually without a trace.
Reconciliation
After execution, compare register, statuses and financial report. Commercial scenarios belong on transfers and payouts or contacts.
FAQ
What are bulk payouts?
A process for sending payouts to many recipients based on a register or similar structure.
Which fields are needed?
Recipient, amount, reason, unique ID and status.
How can duplicates be avoided?
Use unique identifiers and separated approval roles.
When should statuses be checked?
Before sending, after execution and when errors occur.
