Bulk Crypto Payments: Recipient Lists, Safe Approvals and Batch Recovery

Prepare a payment run, understand Safe approvals and distinguish a confirmed batch from an unfinished recipient list.

Separate the payment list from the transaction

A recipient list describes who should receive an asset and how much. A proposal describes a particular action by a particular Safe on a selected network. Importing a CSV or saving a draft does not send funds, approve spending or reserve balances. Before preparing a proposal, inspect the Safe and confirm the owner wallet, token contract and amounts.

Prepare a list that can be reviewed

Bitpont’s Safe payment editor accepts up to 500 distinct EVM recipients with one asset per run. Use the address,amount CSV columns, plain decimal amounts and no ENS names. Duplicate recipients, zero addresses and unsupported decimal precision require correction. A familiar ticker is not proof that a token is authentic; inspect the exact contract before using a custom ERC-20.

For example, 120 recipients receiving 10 USDC each create a 1,200-USDC payment list. The Safe workflow divides it into 50, 50 and 20 recipients. That is three separately tracked proposals, not one atomic transaction. Gas and any approval requirements are additional to the recipient total.

Approval is not payment

A Safe’s owners approve a proposal under its current threshold and nonce. Execution is a separate step. A prepared proposal, collected approvals or a submitted transaction hash is not evidence that the recipients have been paid. Bitpont checks current owners, balances and proposal identity again before execution; review changed conditions before signing.

Continue after an interruption

Open the saved payment run and check each batch. If the first batch completed, restarting the original list could pay those recipients again. Resume the unfinished batch instead. If another owner executed the Safe transaction, use the exact execution hash for reconciliation. A pending or unverified request must be checked before another execution is attempted.

Choose the right payment tool

Solana bulk payments use a separate wallet and transaction flow. Do not import Solana addresses into a Safe EVM list. Payment streams distribute value over time and continue until stopped; distribution pools allocate units among members. Neither is equivalent to a one-off recipient list.