Skip to main content

Payroll

Pay your whole team in one transaction with one signature - and keep the roster so next month is a single click.

Open Business → Payroll.

Set up your team​

  1. Click Add team member
  2. Enter a name, their wallet address or @name, and salary per pay run
  3. The form stays open, so you can enter the whole team back-to-back

Aruvi validates as you go: bad addresses, duplicate wallets, and your own wallet are caught before they reach the roster. Edit or remove anyone at any time.

Your roster stays private

Names, wallets, and salaries are saved in your browser only, keyed to your employer wallet - they never touch a server or the blockchain. Only the payments themselves are on-chain. Moving to a new machine? Export downloads the roster as a file, Import loads it anywhere - save the team once, carry it everywhere.

Run payroll​

The page shows your team size, the total per run, and your balance up front. If your wallet can't cover the total, the run button is replaced with exactly how much you're short.

Click Run payroll and everyone is paid through atomic multiSend batches. Teams up to 100 settle in a single transaction; bigger teams are split into batches of 100 automatically, each one signature, settling back to back in under a second apiece. If a batch ever fails mid-run, the page shows exactly how many people were already paid and the button becomes Resume payroll for the rest - nobody can be paid twice. The batch memo is stamped with the pay period (e.g. Payroll · July 2026).

History and receipts​

Every pay run appears in the history card, read straight from chain events:

  • Date, headcount, and total per run
  • Expand a run to see each person by name with their amount
  • A receipt link to the transaction on ArcScan

Because history is on-chain, it survives clearing your browser - only the roster is local.

Costs​

A batch of 100 salaries costs a few cents in USDC gas and settles in under a second, so even a thousand-person team pays fractions of a dollar in total fees. See Multi-Send for the underlying mechanics, and Refunds if a payment needs to come back.