DEV Community: PayVectro Labs

Why a bulk send fails or reverts, and what to do

PayVectro Labs — Wed, 21 Oct 2026 18:21:03 +0000

A bulk send usually fails for one of five reasons: the token allowance is too low, the balance is short, the token does not behave like a standard ERC-20, the wallet is on the wrong network, or the transaction was replaced or dropped. A batch is all or nothing, so a reverted batch pays nobody and can be sent again.

Causes and fixes

Cause	What to check	What to do
Allowance too low	The approval was for less than the batch total, or it was spent by an earlier batch.	Approve again for the total, then resend the batch.
Balance short	The wallet holds less than the batch total, or no gas token for fees.	Top up the token or the native gas token, then resend.
Unsupported token	Fee-on-transfer and rebasing tokens change the amount in transit, so the totals do not add up.	These tokens are rejected. Use a standard token.
USDT on Ethereum	The Disperse contract does not handle tokens with missing return values.	Blocked in the interface. Send USDT another way.
Wrong network	The wallet is on a different chain than the one selected.	Switch the wallet to the selected network and resend.
Replaced or dropped transaction	You sped up or cancelled in the wallet, or the transaction never got mined.	Check the history. A batch counts as confirmed only after a success receipt. Resend the batches that are not confirmed.

Before you resend

Open the history and check which batches are confirmed. Do not resend a confirmed batch.
Look up the transaction hash on the chain's block explorer to see whether it succeeded, failed or is still pending.
Fix the cause from the table.
Resend only the batches that are not confirmed. PayVectro can resume at the next unconfirmed batch.
Export the CSV with transaction hashes when you are done.

FAQ

If a batch reverts, did anyone get paid?
No. A batch is all or nothing, so a reverted batch pays nobody in that batch.

Can I just send the whole list again?
Not safely. Check the history first and resend only the batches that are not confirmed, or a recipient can be paid twice.

Why does it say confirmed only sometimes?
History shows confirmed only after a success receipt from the chain, not when the wallet shows a pending transaction.

Does a failed send cost anything?
A reverted transaction still uses gas. PayVectro currently charges no fee.

PayVectro sends through the public Disperse contract on 9 mainnet networks and its own contract on Sepolia testnet. You sign every transaction from your own wallet.

Originally published at payvectro.com/guides/bulk-send-failed-reverted.

How to send ERC-20 tokens to multiple addresses in one transaction

PayVectro Labs — Wed, 21 Oct 2026 17:46:34 +0000

To send an ERC-20 token to many addresses, approve the batch contract for the total, then send one transaction per batch of up to 200 recipients. PayVectro asks for the exact amount in the approval by default. Check the list and the total first, wait for the receipt, then save the CSV.

The steps

Make a list. One line per wallet: address, amount. Use a CSV or paste text.
Pick the network and the token. Paste the token contract address if it is not in the list.
Check the list and the total. A wrong address is a lost payment, and a line pasted twice pays twice.
Approve the token. PayVectro requests the exact total by default. An unlimited approval is an option you have to choose.
Send. Your wallet asks you to sign once per batch.
Wait for the receipt. History shows confirmed only after a success receipt.
Save the CSV with transaction hashes.

What can go wrong

A token batch fails if the allowance or the balance is short.
Fee-on-transfer and rebasing tokens are rejected because the balances do not add up.
USDT on Ethereum is blocked in the interface because the Disperse contract does not support tokens with missing return values.
The batch is all or nothing, so a reverted batch pays nobody and can be sent again.

For token sends the gas estimate is labelled ROUGH. Test the whole list on Sepolia first.

FAQ

Can I send ERC-20 tokens to many addresses at once?
Yes. Approve the batch contract for the total, then send one transaction per batch of up to 200 recipients.

Do I have to approve the token first?
Yes. The contract moves the tokens, so it needs an allowance for the total of the batch. PayVectro requests the exact total by default.

How many addresses can I send to in one transaction?
Up to 200. Lists up to 1,000 are split into several batches, and you sign each one.

Which tokens do not work?
Fee-on-transfer and rebasing tokens, and USDT on Ethereum, which is blocked in the interface.

Does it cost a fee?
PayVectro currently charges no fee. You pay network gas.

PayVectro sends through the public Disperse contract on 9 mainnet networks and its own contract on Sepolia testnet. You sign every transaction from your own wallet.

Originally published at payvectro.com/guides/send-erc20-to-multiple-addresses.

Bulk send on Base: send ETH or tokens to many wallets

PayVectro Labs — Wed, 21 Oct 2026 17:24:50 +0000

PayVectro lets you send ETH or ERC-20 tokens to many wallets on Base (chain id 8453) from your own wallet. Paste or upload up to 1,000 recipients. They go out in batches of up to 200 per transaction and you sign each batch. Your wallet needs ETH on Base for gas.

The steps on Base

Open PayVectro Batch Send and connect your wallet.
Switch your wallet to Base (chain id 8453).
Paste or upload your list: one address and amount per line. Up to 1,000 recipients per list.
Choose ETH or paste an ERC-20 token address, then check the total and the gas estimate.
Send. Your wallet asks you to sign once per batch of up to 200 recipients.
Wait for the receipt before you close the tab. History shows confirmed only after a success receipt.
Export the CSV with transaction hashes for your records.

What to know on Base

Gas is paid in ETH. Base charges a layer 2 execution fee plus a layer 1 security fee that covers posting data to Ethereum (docs.base.org/specifications/transactions/network-fees).
The contract is the public Disperse contract at 0xD152f549545093347A162Dce210e7293f1452150, the same address PayVectro uses on its other supported mainnets. PayVectro checks the contract code hash before every send.
You can look up each transaction on basescan.org.
The gas estimate for token sends is labelled ROUGH. Send a small batch first to see the real cost.
A batch is all or nothing. If it reverts, nobody in that batch is paid and you can send it again.

FAQ

Can I bulk send ETH on Base?

Yes. Paste or upload a list of addresses and amounts, choose Base, and send in batches of up to 200 recipients per transaction. Your wallet needs ETH on Base for gas.

What do I pay gas in on Base?

ETH. Base charges a layer 2 execution fee plus a layer 1 security fee that covers posting data to Ethereum.

Can I send ERC-20 tokens on Base?

Yes, with an approval first. PayVectro asks for the exact amount by default.

How many wallets can I pay per transaction on Base?

Up to 200 per transaction and up to 1,000 per list. Longer lists are split into several batches.

Does PayVectro charge a fee on Base?

PayVectro currently charges no fee. You pay network gas.

Where can I check the transaction?

On basescan.org, using the hash PayVectro shows and exports in the CSV.

Originally published at payvectro.com.

How to bulk send USDC to many wallets

PayVectro Labs — Wed, 21 Oct 2026 17:22:07 +0000

To bulk send USDC, pick the network, paste the USDC token address for that network, approve the total, then send in batches of up to 200 recipients per transaction. Take the address from Circle's own list, because the same token has a different address on every chain and some chains also have bridged copies.

The steps

Choose the network where your recipients expect USDC.
Open Circle's USDC contract address page (developers.circle.com/stablecoins/usdc-contract-addresses) and copy the address listed for that network.
In PayVectro Batch Send, paste that address as the token. Check the token name and symbol it shows before you go on.
Add your list: one address and amount per line, up to 1,000 recipients. See the CSV format guide for the exact rules.
Approve the total. PayVectro asks for the exact amount by default.
Send. Your wallet asks you to sign once per batch of up to 200 recipients.
Wait for the receipt, then save the CSV with transaction hashes.

What can go wrong

A wrong token address sends the wrong token. Copy it from Circle's page, not from a search result or a message.
Bridged copies of USDC are separate tokens with separate addresses. Circle's page lists the Circle-issued address for each chain.
You need the network's gas token in the wallet as well as the USDC. Gas is paid in the native token of the chain.
A batch is all or nothing. If it reverts, nobody in that batch is paid and you can send it again.
USDT on Ethereum is blocked in PayVectro. USDC is a different token and is not affected by that block.

Test the whole list on Sepolia first. PayVectro currently charges no fee. You pay network gas.

FAQ

Can I send USDC to multiple wallets at once?

Yes. Pick the network, paste the USDC token address for it, approve the total, then send in batches of up to 200 recipients per transaction. You sign each batch from your own wallet.

Where do I get the USDC address for my network?

From Circle's USDC contract address page at developers.circle.com/stablecoins/usdc-contract-addresses. Check it on the chain's block explorer as well.

Do I need to approve USDC first?

Yes. The batch contract moves the tokens, so it needs an allowance for the total. PayVectro requests the exact total by default.

How many recipients can I pay per transaction?

Up to 200 per transaction and up to 1,000 per list. Longer lists are split into several batches.

Does PayVectro charge a fee for USDC sends?

PayVectro currently charges no fee. You pay network gas.

Originally published at payvectro.com.

CSV format for a bulk crypto send: address, amount

PayVectro Labs — Tue, 20 Oct 2026 04:48:25 +0000

A bulk crypto send starts with a clean list. In PayVectro a list has two columns: a recipient address and an amount. One recipient per line, separated by a comma, semicolon, tab, pipe or space. A header row is optional.

The format

Columns: exactly two, address and amount. Extra columns are rejected.
Header row: optional. If used, it may contain only address (or wallet, or recipient) and amount (or value).
Separators: comma, semicolon, tab, pipe or plain whitespace. Do not mix two kinds on one line.
Address: a valid address with a correct checksum, or an ENS name ending in .eth. The zero address is rejected.
Amount: plain decimal text such as 1.5. Thousands separators and currency symbols are rejected.
Blank lines and comments: blank lines and lines starting with # or // are skipped.
Duplicates: the same address on several lines is merged into one recipient and the amounts are added.
Errors: one invalid line blocks the whole import and the line number is shown.

A safe way to prepare the file

Put address in column A and amount in column B, with a header row.
Format the amount column as text so the spreadsheet does not round or localise the numbers.
Export as CSV, or paste the two columns straight in.
Import the list and fix every line the importer flags.
Check the total and the recipient count against your source before you send.
Send a small test batch on Sepolia first.

Limits to remember

Up to 1,000 recipients per list and 200 per transaction. Longer lists are split into batches and you sign each one.
Every recipient needs a nonzero amount.
A wrong address is a lost payment. The importer checks the format and checksum, not who owns the address.

FAQ

Can I use ENS names? Yes, names ending in .eth are accepted.

Why was my whole file rejected? One invalid line blocks the import. PayVectro shows the line number and the reason.

Does it cost a fee? PayVectro currently charges no fee. You pay network gas.

Originally published at payvectro.com. The tool is at payvectro.com.