Stablecoin Payroll: How to Pay Your Latin America Team in Digital Dollars

In short

Stablecoin payroll means paying salaries in digital dollars (USDC) to each employee's wallet, instead of firing off international transfers one by one. Payment lands in minutes and does not depend on banking hours.
Every employee needs their own identity verification. When you add them, they automatically receive their KYC link by email, and their wallet is created once KYC is approved. No approved KYC, no payment.
Three modes: a one-off batch, scheduled biweekly or monthly payroll (Growth+), and CSV import (Growth+) in email,amount format.
With dual approval (Enterprise) the button changes to "Send for approval": whoever prepares the batch cannot execute it alone — a second administrator confirms it. That is the maker-checker scheme.
There are two real limits: employees per plan (Startup 10 · Growth 50 · Enterprise 100) and the combined monthly volume of sends plus withdrawals ($200,000 · $400,000 · $1,000,000). A batch exceeding your available volume for the month will not execute.
The part nobody tells you: paying salaries in stablecoins carries labor and tax implications that depend on each employee's country. The tool executes the payment; the legal fit is yours and your advisor's.

The problem it solves

Any company with a team spread across Latin America knows the scene: every month-end, a separate international transfer per person, each with its own fee, exchange rate, timeline and odds of bouncing over a mistyped field. Multiply that by twenty people in five countries and payroll becomes a monthly project.

The alternative described here changes the unit of work: instead of N international transfers, one batch paying N wallets in digital dollars. The money reaches each person in the same currency the salary was agreed in, and each of them decides what to do with it afterwards.

Worth stating up front what it does not solve: it doesn't remove local hiring, it doesn't replace an employment contract, and it doesn't by itself turn a payment into regulatory compliance. We cover that at the end, without varnish.

Step 1: onboarding employees

Under Employees → Add employee you enter three fields:

Full name
Email address
Wallet network: Base (recommended), Ethereum, Polygon or Arbitrum

On save, the employee automatically receives their KYC verification link by email — you can also copy the link and send it through whatever channel you use. Their wallet is created when KYC is approved, not before.

The employee table shows each person's status at all times: Unverified, Incomplete, Under review, Approved or Rejected. Only Approved employees can be paid. Two actions are available per employee: Resend KYC if they stalled halfway, and Delete, which removes them from payroll while preserving their payment history.

The employee cap depends on your plan: Startup 10, Growth 50, Enterprise 100. On reaching it the app warns you and you can upgrade.

A practical sequencing tip: start the team's KYC with room to spare, not on payment day. Verification takes minutes per person, but it depends on them actually doing it; an employee sitting at Incomplete on payroll day simply won't make the batch.

Step 2: building and running the batch

Under Payroll you select employees with approved KYC, assign each one an amount in USD, and choose how to pay:

Mode	What it does	Plan
One-off	The batch executes on confirmation	All plans with the panel
Biweekly / Monthly	Scheduled payroll: the system runs it each cycle	Growth+
CSV import	Bulk upload in `email,amount` format	Growth+

On scheduled payroll, employees are re-validated before every run: if someone is no longer approved, the system catches it at that moment rather than in next month's report. You can see the next payment or cancel the schedule under Scheduled payrolls.

The panel always shows your plan's available monthly volume as "{spent} of {total}". That cap is the combined total of sends plus withdrawals in the calendar month — $200,000 on Startup, $400,000 on Growth, $1,000,000 on Enterprise — and if a batch exceeds it, it will not execute. Worth checking before confirming a large payroll, especially if there were already withdrawals that month.

The applicable fee is the send fee: 0.40%, identical across plans. Network fees are on us: ~$0.00 in gas.

Step 3: control — dual approval and traceability

On Enterprise you can require that no payment leaves on a single signature. With Approvals active, the payment button becomes "Send for approval" and the batch is held until a second approver confirms it:

Preparing the payment: any role with payroll permission — Administrator or Finance.
Deciding: only an Administrator.
Approving a one-off payment executes the batch there and then; approving a biweekly or monthly payroll creates the schedule.
Each request shows its type, employee count, date and requester; resolved ones stay in history as Approved or Rejected.

On traceability, Payroll history keeps every batch with its status: Processing, Sent, Partial (some payments failed) or Failed. Partial is the one to actually watch: it means part of the team got paid and part didn't, and it demands immediate action.

Each run also fires the Integrations webhooks (Enterprise) if you have them configured, so payroll lands in your own accounting system without copy-paste.

What the employee actually receives

This is the point worth explaining properly to the team before changing how they're paid, because it's where misunderstandings start.

The employee receives USDC in their wallet, not a deposit in their bank account. USDC is a stablecoin equivalent 1:1 to the dollar: it holds dollar value, but it is not a bank deposit and is not covered by the FDIC, SIPC, Fogafín or any deposit or investor insurance.

From there, what each person does with that balance — hold it in dollars, send it, or move it to their local bank — depends on their own account and on the rails available in their country, which are enabled progressively. If your team is in Mexico, a CLABE withdrawal takes 1–2 business days; the country-by-country picture is in our guides to SPEI, Pix and Bre-B.

An implementation recommendation, based on how these migrations actually fail: don't switch the whole payroll at once. Run one cycle with two or three volunteers, verify that withdrawal to their bank works end to end in their country, and only then roll it out. An employee who cannot convert their salary to local currency the day they need it is an HR problem, not a treasury one.

What this does not solve (the legal part)

Bluntly, because this is the section that decides whether it fits your company:

Paying salary in stablecoins is not automatically valid as payroll in every country. Many labor codes require salary to be paid in legal tender, or impose conditions on the portion payable another way. That is a question for your employment lawyer in every country where you have people, not for an article.
Tax and social security obligations do not change because the payment method changed. Withholdings, contributions and filings remain yours and your employee's as applicable.
Employees and contractors are not the same thing. The module executes payments; it does not determine the nature of the working relationship, and paying someone this way doesn't turn a legal employee into a contractor or vice versa.
The tool does not issue payslips or calculate withholdings. It records payments, generates transaction receipts and fires webhooks into your system; payroll calculation stays where it lives today.

D-ONE CASH is a product of DIGITALROCKETS LLC. We are not a bank, a payroll provider, or legal, tax or employment advisors. What this article describes is what the tool does, verified against its product documentation.

Frequently asked questions

What is stablecoin payroll?

It is paying your team's salaries in digital dollars — USDC, equivalent 1:1 to the dollar — into each employee's wallet, in a single batch, instead of issuing individual international transfers. Payment completes in minutes and does not depend on banking hours.

What does each employee need in order to be paid?

Approved identity verification (KYC). When you add them with name, email and wallet network, they automatically receive their verification link by email, and their wallet is created once KYC is approved. Only employees in Approved status make it into a payroll batch.

Can payroll be scheduled to run on its own?

Yes, on Growth plans and above: biweekly or monthly payroll executes automatically each cycle, with employees re-validated before every run. You can check the next payment or cancel the schedule under "Scheduled payrolls".

How many employees can I pay, and for how much?

Employees depend on the plan: 10 on Startup, 50 on Growth, 100 on Enterprise. The amount depends on monthly volume, which is the combined cap on sends plus withdrawals in the calendar month: $200,000, $400,000 and $1,000,000 respectively. A batch exceeding the month's available volume will not execute.

How do I stop one person from being able to run payroll alone?

With Enterprise dual approval. The payment is sent for approval and does not execute until a second Administrator confirms it; an Administrator or Finance role can prepare it, but only an Administrator decides. Every request stays in history as Approved or Rejected.

Is it legal to pay salaries in stablecoins?

It depends on each employee's country and it isn't something we can answer for you. Many labor codes require salary to be paid in legal tender or limit the portion payable otherwise, and tax and social security obligations don't change because the payment method did. Check with your employment and tax advisors in every jurisdiction where you have staff.