Employees and payroll
To add or remove employees, resend their verification, pay, schedule, sign a pending cycle, send for approval, approve or reject payroll, you need your passkey and PIN set up in Settings → Security and payment confirmation (if you're a team member, go through Security settings › at the bottom of the panel); without them you can't get into the panel, because we ask for them when you sign in. Canceling a scheduled payroll or a pending cycle doesn't ask you to confirm it with your passkey and PIN on that action. While your account is in access recovery you can't do any of this, nor cancel anything, and for 72 hours after a PIN change you can't pay, schedule, sign, send for approval, approve, reject or cancel payroll; in both cases, the payrolls you scheduled are held until it ends, without counting as a failure. See Payment confirmation.
Employees
Every employee you add gets their own wallet to receive payroll, after verifying their identity.
- In Employees → Add employee, enter the full name and email address. Use the employee's personal email; the same email can't be registered twice as an employee in your company. Their wallet is always on the Base network, and that's where payroll payments are sent. Confirm the new employee with your PIN and your passkey.
- The employee automatically receives their KYC verification link by email (you can also copy the link and send it yourself).
- Their wallet is created once KYC is approved. The table shows each status: Not verified, Incomplete, Pending, Under review, Approved, Rejected.
Per-employee actions: Resend KYC (if they haven't completed verification) and Remove (you'll be asked to confirm) — they're removed from your payroll, but their payment history is kept. If they were part of a scheduled payroll, that schedule stops paying everyone in it: cancel it and create it again without them.
Employee limit per plan: Professional 1 · Startup 10 · Growth 50 · Enterprise 100 (every registered employee counts, verified or not). When you reach it, the app lets you know and you can upgrade.
Payroll
In Payroll you select employees and assign each amount in USD (up to 100 payments per batch). Only employees with Approved KYC can get paid: if you include someone who isn't approved yet, no payment in the batch is sent; unselect them and try again. Each employee goes only once per batch: if you're paying them for two things, add both into their amount. Then you choose how to pay:
- One time — with no date, the batch is paid when you press "Pay N employee(s)"; with a date, it's scheduled for that day (see Payment date).
- Biweekly (every 14 days) / Monthly (same day every month) — scheduled payroll (Growth+): the system leaves each cycle ready for you to sign (see below); you can see the next run or cancel it under "Scheduled payrolls".
- Payment date (optional) (Growth+) — pick a day from tomorrow onwards. With One time, on that day the cycle is left ready for you to sign (just once), and the schedule closes once you sign it. With Biweekly, the first cycle is ready that day and the next ones every 14 days; with Monthly, that day becomes the payday of every month (if a month doesn't have that day, it's the last day of the month). With no date, recurring payrolls start on the next cycle: in 14 days or in a month. With dual approval (Enterprise), the date travels with the request: if it's approved after that date, the cycle is ready to sign on the next daily run.
- Import CSV (Growth+) — loads the amounts in one go with the format
email,amount(one line per employee;;also works). Only employees who are already registered are filled in: review the selection and pay or schedule as usual.
A scheduled payroll no longer pays itself: every cycle waits for your signature. On the scheduled
day, the system checks that you're still on Growth or higher and that every employee in the schedule is
still registered with approved KYC. If that's in order, it leaves the cycle ready under Pending
signatures (inside Payroll) with the list of payments and the total, and emails whoever can sign it.
Nobody gets paid yet: for the money to move, someone with permission has to open it, review it, and
press Sign with their passkey and PIN — only then are the balance, your monthly volume and possible
duplicates checked. The cycle expires after 30 days if nobody signs it; it's discarded and never
paid, but the schedule keeps generating its next cycles normally. You can cancel a pending cycle
without canceling the whole schedule, as long as it hasn't expired and isn't under review (see below); if
someone is signing it at that moment, the cancellation doesn't go through and we let you know.
What happens when you sign. If all the payments go out, or some do and we know the rest didn't, the
cycle is no longer pending; if any failed, we let you know and you'll see it in the history. If all of them fail without
any money moving, the cycle stays pending signature: check your balance and the payroll history
—where the failed attempt shows up— and sign it again. If we can't confirm whether any payment went out,
the cycle stays under review: it can't be signed or canceled, and our team reviews it. Don't pay it
again or create a new payroll for those amounts in the meantime.
If something stops the cycle from being prepared (for example, an employee without approved KYC),
nothing is generated that day and it's retried the next day; "Scheduled payrolls" shows the last run and
the reason for the last failure. After 3 failures like that in a row, the schedule is Paused and we
email you; a paused schedule can't be resumed on its own: cancel it and create it again once you've fixed
the issue. If instead what stops preparation is your plan being downgraded or your account being
suspended, it doesn't count as a failure, doesn't pause the schedule and doesn't email you — upgrade your
plan (or resolve the suspension with support) and the next cycle is generated normally.
If a payroll was already paid in the last 24 hours, the app warns you before a new immediate payment: it
shows you the earlier payment (amount, number of payments, date and who made it) and, if it really is a
different payment, you can confirm it with Yes, pay anyway — that payment asks for your passkey and
PIN like any other. When signing a cycle, on the other hand, if a payroll with the same total and the same
number of payments was already paid in the last 24 hours, signing stops so your employees aren't paid
twice and it can't be confirmed from the cycle: you can sign it once those 24 hours have passed or, if it
really is a different payment, make it as an immediate payment.
The panel always shows your plan's available monthly volume ("{spent} of {total}"): if a batch exceeds your month's available amount, it won't run. Volume adds up transfers and withdrawals in the calendar month.
Each payroll payment carries the transfer fee (0.40%) — see Fees.
For now, payroll can't be paid from accounts based in the European Economic Area (the European Union, Iceland, Liechtenstein and Norway).
On Enterprise, dual approval is mandatory. The payment button changes to "Send for approval" and no payment —immediate, dated or recurring— goes out until an administrator other than the person who sent it approves it. If nobody else in your company can approve, the app won't let you send it: invite another administrator from Team. For a recurring payroll, approval is requested once, when the schedule is created; every cycle it generates afterwards still waits pending signature, and if your company has dual approval on, signing it also requires approval permission (having payroll access alone isn't enough). See Approvals and treasury.
History
Payroll history keeps the latest batches with their status: Processing, Sent, Partial (some payments failed) or Failed. Each run also fires the webhooks in Integrations if you have them configured.
Next steps
Updated 12 days ago