Vendor Payment Batch Sender (Base)

WHAT IT DOES

This tool enables businesses, procurement teams, and accounts payable departments to pay vendors in a single batched transaction on Base. Instead of sending 50 individual transactions and paying gas 50 times, you paste a list of vendor addresses and payment amounts, and the BotGentz bulk-sender contract distributes everything in one go. It supports ERC-20 tokens, ERC-721 NFTs, and ERC-1155 multi-tokens, plus native ETH through the same interface. The tool reads on-chain balances, verifies that your wallet holds enough of each asset to cover the total payments plus the contract's fee, and checks your transaction history to flag duplicates. It displays the contract's live fee, owner, and address before you sign anything so you know exactly what you are approving. This is designed specifically for vendor payment processing—covering supplier payments, contractor invoices, service provider settlements, freelancer payouts, and recurring vendor expenses—but it works for any bulk payment need. Whether you run a small business with a handful of vendors or a large enterprise with hundreds of suppliers, this tool streamlines accounts payable operations.

HOW TO USE

Connect your EVM wallet via the BotGentz bridge. The tool automatically detects Base (chain ID 8453) and looks up the correct bulk-sender contract from the BotGentz registry. Enter the token contract address, choose the token type (ERC-20, ERC-721, or ERC-1155), and paste your vendor list as one address and payment amount per line. Optionally include invoice references for your records. Click "Parse list" to validate addresses and preview the total payments. The review panel shows the number of vendors, total payments, token address, and the contract fee in ETH. When you click "Send batch," the tool performs a balance check per sender, not per row, ensuring the entire batch can complete before the first transfer. It then approves the sender contract for the exact total amount, not unlimited, and sends the batched transaction. Progress is shown throughout, including transaction confirmation. All state is in-memory and lost on reload—no data is stored. The tool handles vendor payment cycles with multiple suppliers, making bulk payments practical and cost-efficient on Base's low-fee infrastructure.

BULK SENDER CONTRACT MECHANISM

Unlike claim-based airdrops where each recipient pays their own gas to withdraw, this is a true bulk-send tool: the sender pays once for the entire batch. The BotGentz registry provides per-chain, per-standard contract addresses. The tool reads the fee() and owner() methods live from the contract each time—never hardcoding fees because the owner can change them. It uses the contract's sendERC20, sendERC721, and sendERC1155 methods, passing the recipient arrays, amounts or token IDs, and the required fee as msg.value. The fee covers the contract's operational costs and is separate from network gas. The tool checks balances comprehensively: native ETH balance must cover the fee, and ERC-20 balance must cover the total payments. It walks through approvals sequentially and awaits each transaction, avoiding nonce conflicts that would occur if sends were fired concurrently. Post-EIP-1559, it uses receipt.effectiveGasPrice for accurate cost reporting rather than tx.gasPrice. For chains with different log limits, it chunks reads appropriately, halving ranges on failure. The contract owner is shown so you can verify the deployer before signing. The tool also reads token decimals dynamically and supports multi-token vendor payments where different vendors receive different assets based on their contracts. The batch size is limited only by block gas limits, suitable for vendor payment runs with hundreds of recipients on Base's high-capacity network.

WHAT IT CANNOT SEE

This tool cannot verify off-chain vendor invoices, delivery fulfillment, work quality, or payment eligibility. It cannot prove that recipient addresses are correct, that vendors are legitimate, or that the same person is not receiving multiple payments via different identities. It cannot detect Sybil attacks or duplicate vendor identities. It cannot access private vendor payment preferences, contract terms, or financial records. It cannot recover funds sent to wrong addresses—the blockchain is final. It cannot see past the current block, and it cannot enforce business rules beyond what is expressed in the payment list. It does not store any data; all state is in-memory and lost on reload. It cannot verify that goods or services were actually delivered, that invoices are legitimate, or that payment amounts match contractual agreements. It cannot automatically import invoice data from accounting systems or calculate payments based on purchase orders. It cannot handle multi-currency payments, tax withholdings, or payment terms beyond what you manually enter. It cannot verify that vendors are in good standing, that they have valid tax IDs, or that they are not on sanctions lists. It cannot enforce approval workflows, payment limits, or internal controls beyond what you manually enter. It cannot verify that the payment complies with applicable financial regulations, tax laws, or corporate governance requirements. It cannot handle partial payments, payment holds, or dispute resolution mechanisms.

PLEASE NOTE

This tool works only on Base (chain ID 8453) with the BotGentz bulk-sender contract deployed. Other EVM chains like Ethereum L1, Optimism, Arbitrum, Polygon, BNB Chain, and others are supported by sibling tools—this specific tool is restricted to Base. Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. Always double-check the contract address displayed in the tool against the official BotGentz registry before sending. The tool is free and open-source; the contract fee is set by the owner and displayed live. Use at your own risk—you are responsible for verifying all addresses, payment amounts, and vendor eligibility before signing any transaction. For businesses with significant payment volumes, consider implementing a formal review process, using a multi-signature wallet, and consulting with legal and financial advisors to ensure compliance with applicable regulations.