How freelancers and contractors actually get paid in stablecoins

If you run a finance team, you have probably had the conversation. Someone says they want to pay a freelancer in stablecoins. Someone else asks whether that person is actually a contractor. A third person mentions payroll and suddenly everyone is talking about employees, tax forms, and compliance rules that do not apply to the person in question.

The confusion is understandable. Freelancer, contractor, consultant, employee: the words get used interchangeably in Slack and in contracts, but they mean different things for payments. Employees sit under employment law, local salary rules, and payroll systems built for that relationship. Freelancers and contractors invoice you. They are businesses paying businesses, even when the business is one person with a laptop. That distinction is why stablecoin payments work differently for a contractor in Lisbon than for a salaried engineer in Paris.

This article is about the second group: people who invoice you for work, often from another country, and who increasingly ask to be paid in USDC or USDT. Getting paid in stablecoins is the easier half. Living on them is where it usually falls apart.

Freelancer or contractor, is there a difference?

In practice, not much that matters for payments.

In the US, contractor usually means someone engaged under a services agreement, often with a defined scope and no employment benefits. Freelancer is the habit word for the same arrangement when the person works alone: the designer, the developer, the writer billing by project or by month. In the UK, freelancer is the register people use on invoices and tax returns; contractor often implies a limited company or a longer engagement, but the payment mechanics are the same. You receive an invoice, you pay it, you keep a record.

For a finance team, the useful line is not freelancer versus contractor. It is employee versus everyone else. If the person invoices you, stablecoin settlement is a B2B payment question, not a payroll question. See our crypto payroll guide for where payroll and contractor payments diverge.

Why this became a payments problem

Globalisation did not rewrite employment law, but it rewrote who companies work with. A twenty-person software company in the US might have its core team in Denver, a backend contractor in Argentina, a QA freelancer in Nigeria, a designer in Vietnam, and a marketing consultant in Portugal. None of them are on US payroll. All of them submit invoices.

Paying that group through traditional banking was never designed for this shape of team.

The correspondent bank chain takes a cut at every hop. An outgoing wire from a US business account does not travel directly to a recipient in Lagos or Buenos Aires. It passes through intermediary banks, each with a fee or a spread baked in. The finance team often sees one line on the statement and never sees the full chain.

Delays are measured in business days, and business days have weekends. Send a wire on Friday afternoon and the contractor may not see it until Wednesday. That is normal, not exceptional. For someone invoicing monthly, it means living in uncertainty about when rent money lands.

FX is priced into the rate, not shown as a fee. The recipient receives a local currency amount converted at the bank's spread. There is no separate line item that says "we took 2.3% here." It just arrives light.

Fixed wire fees punish small invoices. A $25 wire fee on a $4,000 invoice is annoying. On a $400 invoice it is untenable. Finance teams start batching payments or switching to informal tools, which creates its own reconciliation mess.

Some destinations are simply hard to reach. Banking rails that work cleanly for Western Europe or the US do not work the same way for every corridor. Contractors in certain markets spend disproportionate time chasing payments that stalled somewhere in the middle.

Then the motivation flips on the contractor's side, especially in high-inflation economies. The problem is no longer only "the wire is slow and expensive." It is "by the time pesos or naira land in my account, they are worth less than when I invoiced." Contractors in Argentina, Nigeria, Turkey, and similar markets started asking for dollars or stablecoins not as a crypto preference but as a savings decision. The company’s payment problem and the contractor’s currency problem became the same conversation.

Which is where stablecoins came in

Stablecoins did not fix employment classification or tax reporting. They fixed settlement.

A USDC or USDT transfer on a supported network settles in seconds, not business days. The cost is roughly flat whether you are moving $400 or $4,000, which changes the economics of paying small invoices regularly. The amount that arrives is the amount that was sent, pegged to the dollar, without a correspondent bank chain taking bites along the way.

For the company paying, stablecoins look like a better rail. For the contractor receiving, they look like a way to hold value until converting locally on their own schedule. Both sides had a reason to try it.

The part nobody warns freelancers about

The UK consultant case is the one we keep coming back to because it is so common.

She had spent two years in Australia, built a client base there, and moved back to the UK with the relationships intact. She invoiced through a UK limited company, as her accountant recommended. The Australian client was happy to pay in USDC twice a month. On paper, everyone won.

In practice, she hit a wall none of the stablecoin cheerleaders mention on Twitter.

No UK exchange would open a business account for her company at the volume she was running. The ones that would wanted personal accounts, which her accountant ruled out. Her high-street bank accepted inbound local currency without much drama and refused inbound transfers whose origin was clearly crypto, which is exactly what USDC payouts look like on a bank statement. She could get paid. She could not easily live on what she was paid without a conversion path her bank would accept.

She tried three routes. Each solved one problem and created another.

Centralised exchange. Open an account, receive USDC, convert to GBP, withdraw to a personal bank account. Works until your bank asks where the money came from, or until the exchange flags a business receiving client payments into a personal profile. Compliance friction, account freezes, and the constant sense that one large inbound transfer would trigger a review.

Self-custody wallet. Full control, no intermediary holding the coins. Also no invoice attached to the transaction, no clean PDF for the accountant, and no straightforward path to pay a supplier or HMRC from the same balance without another round of conversions and manual records.

Crypto-friendly bank. Better than a traditional bank for holding and moving digital assets, but often built for individuals or for companies with simpler flows. Invoicing, client matching, and the monthly reconciliation pack an accountant expects still live somewhere else.

The shared gap across all three: money in one place, paperwork in another. The USDC arrived. The invoice lived in email. The bank statement showed a lump sum. Her accountant asked which client paid which invoice, and the answer required a spreadsheet she maintained by hand.

That gap is not a edge case. It is what happens when you treat stablecoin receipt as a wallet problem instead of an operations problem.

What we built for this

The Request Business Account is built to be the bridge between those worlds.

A contractor or small company opens a Business Account, completes KYB, and receives dedicated account details plus stablecoin wallet addresses. When a client pays, the payment can land with the invoice attached: who paid, how much, for what. When the consultant needs to pay a software subscription or a subcontractor, she pays from the same platform. When she needs GBP in her bank account, she moves stablecoins out through the off-ramp at a time she chooses.

The argument reduces to three things a working freelancer or contractor company actually needs:

1. A way to get paid that clients can use without friction. 2. A way to spend it on business costs without round-tripping through personal accounts. 3. A record connecting the two that an accountant can audit without a custom spreadsheet.

Centralised exchanges give you the first, awkwardly. Wallets give you the second, badly. Neither gives you the third in a form that survives an annual review.

Request Finance is designed for the third as much as the first. Invoices, incoming stablecoin and bank payments, outgoing supplier payments, and exports that tie back to the same ledger. Pricing is a flat monthly subscription plus a percentage when you move stablecoins out to your bank account, and the current rates are on our pricing page.

We built it because the UK consultant case is not exotic. It is the default outcome when finance teams and freelancers treat stablecoins as a receipt rail without building the operational layer around it.

If you are setting this up

A few practical rules if you are a freelancer, contractor, or finance team enabling one.

Invoice in the currency you want to be paid in, and say so in the contract. If you want USDC, the invoice should say USDC and the agreement should say the client may settle in stablecoin to the wallet or account details you provide. Ambiguity here is how disputes start.

Keep the invoice and the payment linked from day one. Do not plan to match them up at year end. The matching should happen when the payment lands, the same way you would expect from a bank transfer with a reference field.

Check what your accountant needs before you need it. Some want monthly transaction exports. Some want client-by-client breakdowns. Some care deeply about how foreign income is reported. Ask in advance, not in March. One note that catches people off guard: the Request Business Account is denominated in USD for operational purposes, even when the settlement rail is USDC or USDT. Your accountant may treat that differently from holding coins in a personal wallet. That is their call, not ours.

The contractor model is not going back in the box. Companies will keep hiring globally. Contractors will keep invoicing across borders. Stablecoins will keep showing up as a settlement option because they are faster and cheaper than wires for many corridors. The question is whether you run that flow with a wallet and a spreadsheet, or with an account built for how freelancers and small companies actually work.