Crypto Payroll: Pay Your Team in USDC
Swaps Payroll is an execution-only way to pay contractors and teams. You prepare a pay run, fund it once, pay each recipient to a bank account or an external USDC wallet, and reconcile every row. It runs on Bridge rails, requires a verified individual or business payer, and is currently a private beta.
This is a request-access launch. Swaps Payroll is not generally available yet. The product engine is gated behind holder verification, so a verified individual or business payer joins the beta rather than signing up self-serve. If you pay contractors or a distributed team and want stablecoin payroll or USDC payouts, you can request beta access on the Payroll page.
What "execution-only" means
Swaps Payroll handles the payout step, and only the payout step. It is the layer between an approved pay run and money actually arriving — not a full HR or employment platform.
That means Swaps Payroll does not do any of the following:
- It does not calculate payroll taxes.
- It does not issue legal payslips.
- It does not file payroll with any authority.
- It does not act as an employer of record (EOR).
Keep payroll taxes, filings, payslips, and employment status with your existing accountant, HR platform, or EOR. Swaps Payroll executes the payout once you have decided who gets paid, how much, and where.
How a pay run works
A pay run moves through four explicit steps, and nothing executes until each one is satisfied.
Prepare the run. Upload a CSV or build rows manually with recipient, worker type, amount, currency, memo, and payout preference.
Approve and lock it. A verified pay run owner approves the run, which freezes the payout snapshot before any funding.
Fund once. The payer funds the whole run after verified provider instructions are available. An unfunded run never executes.
Reconcile each row. Every recipient payout has its own status, evidence, and retry path, so one returned payout does not hide the rest.
The reconcile step is the point of the product. A returned bank payout or a wallet that bounced shows up as its own row with its own status, instead of failing the whole batch silently.
Pay contractors in USDC or to a bank account
Each recipient can be paid one of two ways, depending on what the run supports:
- External USDC wallet. Eligible pay runs can pay an external USDC wallet destination, with an FX estimate on Bridge rails.
- Bank account. Bank payouts use provider-verified external accounts. Swaps never asks a recipient to paste raw bank credentials into support chat.
Recipients keep their own destination readiness, country, and payout history, so a returning contractor does not re-enter the same details every cycle. You can also duplicate a past run into a reusable weekly or monthly template while keeping every execution explicitly approved.
What you need to join the beta
Because Swaps Payroll moves money to real people, access is gated. To use it you need:
- A verified individual or business payer — creators and solo founders can use Payroll where their Bridge route is eligible.
- Recipients with a ready bank destination or eligible external USDC wallet.
- Funding for the full pay run before it executes.
Payout availability also depends on provider rails, currency, and your workspace capability for a given run. The Payroll page is the discovery surface; the actual run tells you what is available for your specific recipients.
Where Swaps Payroll fits
If you already run payroll through an accountant or EOR but struggle with the payout step — paying global contractors in USDC, getting money to a bank account in another market, keeping a clean per-recipient trail — that is the gap Swaps Payroll fills. It is the execution layer, not a replacement for your HR stack.
Related pages worth reading next:
- Swaps Payroll — the product page and where to request beta access.
- Crypto payroll — stablecoin and USDC payroll framing.
- Contractor payouts — paying contractors and freelancers.
- Payment Links — one-off invoices and getting paid, the inbound counterpart to payouts.
- Fees — how Swaps pricing works.
Frequently Asked Questions
Is Swaps Payroll generally available?
Not yet. It is a private beta gated behind Bridge verification. A verified individual or business payer requests beta access rather than signing up self-serve. You can request access on the Payroll page.
Does Swaps Payroll handle payroll taxes and filings?
No. Swaps Payroll is execution-only. It does not calculate payroll taxes, issue payslips, file payroll, or act as employer of record. Keep those with your accountant, HR platform, or EOR.
Can I pay contractors in USDC?
Yes, where the run supports it. Eligible pay runs can pay an external USDC wallet destination with an FX estimate, or pay a provider-verified bank account. Availability depends on the recipient, currency, provider rails, and your workspace.
Do I need a business account?
Yes. Swaps Payroll can support a verified individual or business payer where the route is eligible. A company is not required for a creator or solo founder to start.
What happens if one payout fails?
Each recipient row has its own status, evidence, and retry path. A returned payout shows up as its own row instead of failing or hiding the rest of the run.
Bottom line
Swaps Payroll is the execution layer for paying contractors and teams in USDC or to a bank account: prepare a run, fund once, pay each recipient, reconcile every row. It is execution-only, runs on Bridge rails, and is a private beta for verified individual or business payers.
Request beta access on the Payroll page.
Related Pages