Polygon zkEVM Recurring Payroll Batch Sender

WHAT IT DOES

This tool enables organizations to batch process recurring payroll payments to multiple employees in a single transaction on Polygon zkEVM. Instead of sending tokens to each employee individually and paying gas for every transfer, it combines all payroll payments into one call to a shared batch-sender contract. The tool reads your token balance, allowance, and the current gas price before submitting the transaction. You specify the token contract address, the decimals, an optional payroll period label, and a list of employee addresses with per-employee payment amounts. The tool computes the total tokens to send, checks your balance, verifies you have sufficient allowance for the sender contract, and submits one transaction that distributes payroll to all employees atomically. If allowance is insufficient, the tool automatically requests approval before sending. This is a true push distribution — employees receive their payments directly without any claim action required. The tool works with any ERC-20 token on Polygon zkEVM, making it ideal for payroll, contractor payments, and recurring employee distributions.

HOW TO USE

Connect your EVM wallet via the BotGentz wallet bridge. Select Polygon zkEVM (chain ID 1101) from the network dropdown (or any EVM chain where your token is deployed). Enter the token contract address and its decimals. Optionally enter a payroll period label for record-keeping. In the text area, list each employee on a separate line with their address and the amount of tokens to pay, separated by a comma. Amounts should be in base units (not including decimals). Click "Review payroll" to see your token balance, allowance, the sender contract fee, and the total amount being distributed. The tool will display a warning if your allowance is insufficient. If everything looks correct, click "Process payroll" — your wallet will first ask you to approve the token spend if needed, then to confirm the batch transaction. Once confirmed, the tool shows progress and the final transaction hash with a link to the Polygon zkEVM block explorer. This is ideal for monthly payroll, contractor payments, and recurring employee distributions.

TECHNICAL MECHANISM

This tool uses the BotGentz shared bulk-sender contract registry, keyed by chain ID and ERC standard. It looks up `BULKSEND[String(chainId)].erc20` to get the sender contract address for the current chain. For Polygon zkEVM (chain 1101), the sender contract is `0x956D760F8665358Ea1a9F11b82913020e5479376`. The tool creates a contract instance using `BGWallet.getSigner()` connected to the current chain's provider. It calls `fee()` and `owner()` on the sender contract live — no values are cached. It also instantiates the token contract using the ERC-20 ABI and checks `balanceOf()`, `allowance()`, and `decimals()` for your wallet. The tool computes the total token amount from the employee list and verifies both your token balance and native balance (for the sender contract fee) are sufficient. If allowance is insufficient, it sends an approval transaction for the exact total amount (not unlimited) before the batch transfer. The batch transfer uses `batchSend20(address token, address[] recipients, uint256[] amounts)` on the sender contract, sending the contract fee as `msg.value` in native tokens. The sender contract then iterates the employee list and transfers tokens atomically within the same transaction using `transferFrom` from your wallet. After confirmation, it logs gas usage using `receipt.effectiveGasPrice`.

WHAT IT CANNOT SEE

This tool cannot verify employee eligibility, employment status, or whether the payroll has been properly approved through the organization's workflow. It cannot confirm recipient wallet readiness or guarantee that employees can receive ERC-20 tokens. The tool does not validate that the token contract implements the ERC-20 standard or has the required `transferFrom` function. It cannot detect front-running or mempool congestion. It cannot provide a cross-chain receipt or rollback mechanism. It also cannot verify that the decimals value you entered matches the actual contract decimals — the tool warns but does not automatically correct discrepancies. Organizations should ensure proper payroll approval and employee verification before using this tool.

PLEASE NOTE

This tool is EVM-only. It works on Polygon zkEVM and other EVM chains where the BotGentz registry has an erc20 entry. It does not support Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, or XRP. The tool requires the token contract to be deployed on the chain and for the sender contract to have an erc20 entry in the registry. Always test with a small amount and a single employee before processing full payroll. The sender contract charges a fee in native tokens — ensure you have enough native balance to cover the fee. This is a push distribution — the sender pays all gas, employees receive tokens without any action. Organizations should always maintain proper payroll records and approval documentation separately.