Stablecoin Payroll: How to Pay Contractors in USDC/USDT Compliantly

Disclosure: Xchange360 offers stablecoin payroll. Xchange360 is not an employer of record and not a tax authority. This guide is general information, not tax or legal advice.

You are probably familiar with the information-reporting requirements of the IRS. For example: if you pay a US contractor $2,000 or more for services in 2026, you have to file a Form 1099-NEC, and that is true whether you paid in dollars or in USDC. The $2,000 threshold applies to payments made after 2025 and replaces the old $600 (IRS, Instructions for Forms 1099-MISC and 1099-NEC).

The IRS treats virtual currency as property, which means a stablecoin payment is reportable at its fair market value in US dollars.

Most guides to paying people in stablecoins are written for the person being paid, but it doesn’t say much to the person that’s paying.

If you run finance, operations or HR for a company that already pays contractors across borders, you’re left wondering whether the payment was reported correctly, whether the person and wallet are screened, and whether the rules in the recipient's country allow what you are about to do. The token choice matters too, but it is the smallest of those questions.

Note: This guide assumes a US payer. If you are paying from the UK or EU, the tax sections (2, 3 and 7) will differ, but the classification, screening and record-keeping sections still apply.

1. First, is this person really a contractor?

Classification comes before the payment method. Paying in stablecoins doesn’t change whether someone is a contractor or an employee.The IRS looks at the whole relationship, grouped into behavioural control, financial control and the type of relationship. In plain terms:

• Do you control how, when and where the work is done, or only the result?
• Does the person use their own tools, work for other clients and carry their own business risk?
• Is there an open-ended relationship, benefits, or a role that looks like a staff position?

If the answers point to employment, the rest of this guide is the wrong guide. IRS Notice 2014-21 says wages paid to employees in virtual currency are taxable, subject to withholding and reportable on Form W-2 (IRS Notice 2014-21). Employee payroll is out of scope here, and it is a case for your payroll provider or employment adviser.

2. What the payment is for tax purposes

Three consequences follow from "virtual currency is property".

• For the contractor. Payment for services in virtual currency is income. Notice 2014-21 says it is measured at fair market value in US dollars on the date received, and that a contractor paid this way is generally subject to self-employment tax.
• For you, on the reporting side. If you pay a US contractor $2,000 or more in the year for services in the course of your business, you generally file a Form 1099-NEC with the IRS and furnish a statement to the contractor, both due by 31 January. Payments to most corporations are generally exempt. Your reporting is not reduced because the payment was made in tokens.
• For you, on the asset side. If you acquired the stablecoin earlier and use it to pay, you are disposing of property. Any gain or loss against what you paid for it is a separate question for your tax adviser. For a dollar-pegged stablecoin the difference is often small, but the rule is fair market value, not "it's a dollar". Record the rate you used.

3. Collect the paperwork before the first payout

Treat a stablecoin contractor like any other:

• Form W-9 for US contractors, so you hold a taxpayer identification number (TIN).
• The appropriate IRS Form W-8 for foreign contractors. Whether a payment to a non-US person is reportable depends on the facts, including where the services are performed, so confirm the treatment with your tax adviser before the first payment.
• Backup withholding. If a payee has not furnished a TIN, backup withholding can apply. If you withhold, you must file Form 1099-NEC for that person regardless of the payment amount. The rate is set out in IRS Publication 1099.

A dollar-denominated invoice is the simplest basis for all of this. State the amount in dollars, state the stablecoin and network you will pay in, and state the rate or source you will use to value it. That answers most of the questions an auditor would ask later.

4. USDC or USDT: it depends on where the money goes

Both USDT and USDC are dollar-pegged stablecoins and both are widely used for business payments but their regulatory position varies in particular places.

What the EU register shows

ESMA’s interim MiCA register has a file for issuers of e-money tokens. In the copy I analysed on 12 October 2026, it listed 50 issuer-and-white-paper entries covering 25 issuers across 14 EU/EEA home states. Because each entry pairs an issuer with a specific white paper, one issuer can appear multiple times in the file. Circle Internet Financial Europe SAS (France, supervised by the ACPR) appears twice, with white-paper links named for EURC and USDC. Nothing in the file mentions Tether or USDT.

Read this with care. The file is an interim register, and absence from it means only that no MiCA e-money token authorisation is recorded there. It does not tell you what any particular provider may do for a given customer. Check the live file yourself before relying on this (ESMA, interim MiCA register).

Two cautions

First, the European position is about what a service provider may offer to EU customers. In January 2025 ESMA and the Commission published guidance expecting crypto-asset service providers to comply with MiCA's rules on asset-referenced and e-money tokens, and expecting national authorities to ensure that compliance by the end of the first quarter of 2025 (ESMA, 17 January 2025). That is why a given token can be available through one provider and not another. Don't assume. Check the current register entry for the token and the provider's own statement of what it supports.

Second, the GENIUS Act timing above comes from a law-firm summary, not the statute text, and it is still being implemented. Check the current position before you build a process around it.

Choose the token your provider can lawfully settle in both your country and the recipient's, and write that down. Don't pick the token first and look for a route afterwards.

5. Sanctions screening and wallet controls

Sanctions law applies to digital-asset payments as it does to any other. OFAC's Sanctions Compliance Guidance for the Virtual Currency Industry (OFAC, October 2021) sets out the expectation that businesses use a risk-based compliance programme, including screening and attention to geography and wallet addresses.

For a contractor payout programme that means, at a minimum:

1. Screen the person before onboarding and periodically after. Sanctions screening configuration covers how matching thresholds affect results.
2. Screen the wallet address before the first payment and on any change of address. A name that clears does not clear the wallet.
3. Verify control of the address. Ask the contractor to prove they control the address, for example with a small test transfer they confirm. Stablecoin transfers are hard to reverse, and a mistyped address is a loss, not a dispute.
4. Pay to a named, onboarded recipient. Don't pay to an address someone in a chat gives you.
5. Know what your provider does. Where a provider handles the transfer, ask what identity checks and KYC it performs, and whether travel rule data is exchanged on transfers where that rule applies. If you pay through a regulated provider, some of these checks are theirs. If you pay from your own wallet, they are all yours.

6. The contractor's side: off-ramp and local rules

Your obligation ends at the payment, but your programme does not work if the contractor can't use the money. Before you offer stablecoin payment to someone, ask them:

• Can they convert to local currency through a provider that operates in their country? (On-ramps and off-ramps explained)
• Does their country restrict receiving or holding stablecoins, or require reporting of foreign-currency income?
• Are they comfortable with the price risk between receiving and converting? Most stablecoins are designed to hold a peg, but a peg is not a guarantee.

The freelancer's view of the same questions is a useful read for whoever manages contractor relationships. Offer stablecoin payment as an option, not a requirement, unless local law and the contractor's situation clearly support it.

7. DAC8: what your provider may report about your contractors

If your contractors are EU residents and your payment route runs through a crypto-asset service provider, expect the provider to collect and report data about them. DAC8, the EU's tax-reporting directive for crypto-assets, applies from 1 January 2026. Providers collect information on reportable transactions for EU-resident users from that date, report it to their national tax authority in the following calendar year, and national authorities exchange it with the investor's country of residence. For the first reporting year (2026), exchange between member states is due by 30 September 2027. The scope includes stablecoins, including e-money tokens (European Commission, DAC8).

As a payer, your EU-resident contractors' crypto activity is increasingly visible to their tax authority. That is a reason to make sure your own invoices and records match what they will declare, not a reason to avoid crypto payments.

8. Controls and records

Auditors and tax authorities ask for evidence, not intentions. Keep, per payment:

• the signed contract or statement of work and the invoice;
• the W-9 or W-8 on file;
• the screening result for the person and the wallet address, with the date;
• the token, network, amount, transaction hash and timestamp;
• the dollar value and the source of the rate used;
• the approval trail: who requested, who approved, who released.

Separate duties so the person who adds or changes a payee wallet is not the person who releases payment. Stablecoin transfers are hard to reverse, so a changed or mistyped address is the point where a control matters most.

9. Contractor-payout compliance checklist

Use this before the first payout, then once a year.

Classification

• Reviewed the working relationship against the IRS factors and decided contractor status.
• Confirmed payroll is not the right route for this person.

Tax and paperwork

• W-9 (US) or the appropriate W-8 (non-US) collected before payment.
• Invoice states the dollar amount, token, network and the rate source.
• Payments tracked against the $2,000 Form 1099-NEC threshold and the 31 January filing date.
• Backup withholding process in place for a missing TIN.
• Tax adviser has confirmed treatment of the stablecoin you hold, where you pay from your own balance.

Token and route

• Checked the token's current regulatory status for your country and the recipient's.
• Confirmed your provider can lawfully settle that token in both jurisdictions.
• Recorded why you chose this token and route.

Screening and control

• Person screened against sanctions lists, with date recorded.
• Wallet address screened, and ownership verified.
• Separation of duties between adding a payee and releasing payment.

Recipient

• Contractor has a working off-ramp in their country.
• Local restrictions and the contractor's own reporting needs discussed.
• Stablecoin payment offered as an option where there is any doubt.

Records

• Contract, invoice, screening result, transaction hash, valuation and approvals stored together per payment.

Decision aid

If you can answer yes at every step, the payout is straightforward. If any step fails, the fix is almost always upstream of the token.

Recommended reading: Get paid in crypto as a freelancer, USDT vs USDC for business payments, MiCA stablecoin rules for EMTs and ARTs, Stablecoin vs bitcoin for business payments, KYC for crypto payments onboarding