Documentation
Batched Payout
Explaining what and how batched payout works
What is it?
Withdrawal routing converts each deposit to Monero on its own, then pays your exit wallets together in one outbound swap.
On Activity, that can look like one Batched payout card with several deposits inside. Inbound is per deposit; shield and outbound are shared.
Batching is always on
Firewallet always batches outbound payouts. You do not enable or disable it.
Fewer outbound swaps means lower swap fees for you, and it is harder to link multiple deposits to the same exit wallets.
“Minimum deposits before payout” — privacy enforcement only
The slider under Outbound payout does not turn batching on. Batching already happens.
It only enforces a minimum: Firewallet will not start the next outbound payout until at least that many conversions are ready after their privacy delay.
| Setting | Effect |
|---|---|
| 1 deposit | No enforced minimum — payout as soon as one conversion is ready. |
| 2 deposits (recommended) | Enforces a short wait so payouts combine more conversions — better privacy. |
| 3–5 deposits | Enforces a stricter minimum — even more privacy, longer waits. |
Think of it as a privacy floor, not a batching switch.
Why do I see a batch if I set it to 1?
Because batching is built in, not optional. You will still see batches when:
- Several deposits trigger routing around the same time
- Conversions overlap during the privacy delay
- Combined XMR is still below the exchanger minimum (Firewallet waits until one swap is possible)
Setting the slider to 1 only removes the extra enforced wait. It does not stop automatic batching.
Inbound vs outbound
- Inbound — always separate per deposit
- Outbound — batched whenever Firewallet can combine conversions
A solo activity card means that deposit paid out alone or is still in the inbound phase.