A module for paying out at scale
Mass payouts is now available as an optional module in both the tenant manager and the merchant panel. It is designed for teams that need to send many payouts in one motion instead of releasing them individually. A batch can be created from an upload or through an API call, so the same batch workflow applies whether an operator is preparing a file by hand or a merchant's own system is submitting payout instructions directly.
A batch is checked as a whole before anything moves
Before a batch can proceed, it is validated as a unit rather than item by item. That validation covers currency, wallet coverage, method availability and per-merchant limits. Checking the whole batch up front means issues are caught before release, instead of surfacing gradually as individual payouts start failing against a provider.
Review and release are two separate rights
A validated batch does not move on its own — it waits for an operator who holds the specific permission to release it. Review and release are kept as two distinct rights in the permission system, so the four-eyes control that payout operations rely on is enforced by who can do what in the panel, not by a separate policy document that has to be remembered and followed by hand.
A batch reports the mix, not one status
Once a batch is released, each item in it succeeds or fails against its provider individually. Rather than collapsing the whole batch into a single pass or fail result, the batch reports the actual mix of outcomes across its items. If a handful of items in a large batch fail, those failures become their own separate work items to resolve — there is no need to re-run the entire batch to deal with a partial failure.
Where it fits and how it's switched on
Because mass payouts sits in both the tenant manager and the merchant panel, the same batch review and release logic applies whether an operator is working on behalf of several merchants or a merchant is managing its own payout runs. The module is enabled per billing plan, and the routes behind it are both entitlement-gated and permission-gated — a tenant only sees mass payouts if its plan includes it, and within the module, only operators with the matching review or release rights can act on a batch.
