Module optionnel
Mass payouts
Batch payouts with a review step that means something
Ce que cela résout
Paying out one at a time does not survive contact with payroll-shaped volume. Paying out in bulk without a review step is how a single bad file becomes an incident.
Comment ça marche
Batch intake
A payout batch is created from an upload or API call and validated as a unit — currency, wallet coverage, method availability, per-merchant limits.
Explicit release
A validated batch waits for an operator with the right permission to release it. Review and release are separate rights.
Per-item outcomes
Items succeed or fail individually against their provider, and the batch reports the mix rather than collapsing to one status.
L'avantage
Volume without headcount
Payout throughput stops being a function of how many operators are at their desks.
A real four-eyes control
The separation between preparing and releasing a batch is enforced by permissions, not by policy documents.
Partial failure is survivable
Twelve failed items in a batch of four thousand are twelve work items, not a re-run.
Disponibilité
Enabled per billing plan. Mass payout routes are entitlement-gated and additionally permission-gated.