Paying a contractor in Russia in 2026 is, first and foremost, a sanctions question, not a tax question. The tax mechanics are simple; the hard part is that most cross-border banking rails into Russia are closed, and getting the payment path wrong carries serious legal risk. This page describes what is legally possible and what the compliance reality is — it is general information, not legal advice, and contains no guidance on evading sanctions.
The sanctions constraint
After 2022, major Russian banks were cut from SWIFT, and by late 2024 the US had sanctioned the bulk of the banking sector — including Gazprombank, the last major USD conduit, added to the SDN list in November 2024 (Treasury, checked 2026-07-17). The practical result:
- Paying an individual Russian contractor for services is not itself the target of US sanctions — but the money must not touch an SDN-listed bank or Russia’s SPFS system, and the service must not be sanction-restricted.
- The EU separately prohibits supplying IT, software, consulting and related services to Russian legal entities (Reg. 833/2014 art. 5n) — this targets entities, not natural persons, but the payment-rail restrictions still bite.
- You must screen every party and every bank in the chain against the OFAC SDN list, on an ongoing basis, and take qualified sanctions counsel.
The contractor’s side (simple)
Most Russian contractors are самозанятые on the NPD regime (4% from individuals, 6% from legal entities, via the «Мой налог» app, cap RUB 2.4M/yr) or ИП on the simplified system (6% of revenue). They issue a чек and typically a contract + акт. The contractor handles their own tax; a foreign payer generally does not withhold. Under the Civil Code Part IV, the exclusive right transfers only by an explicit written assignment (договор об отчуждения) — include one for software and all deliverables.
What rails actually work
| Rail | Reality in 2026 |
|---|---|
| Domestic (СБП, Мир, bank transfer) | Work normally inside Russia |
| SWIFT USD/EUR from US/EU | Largely closed to sanctioned banks; only non-sanctioned banks, and screening is on you |
| Wise / PayPal | Exited Russia (2022), not resumed |
| Payoneer / Deel | Restricted — no new Russia clients; limited legacy functionality, RUB-only, heavy screening |
| Crypto / USDT (P2P) | Widely used in practice, but outside the authorised regime — real legal + account-freeze risk |
Crypto in Russia is property, not legal tender; domestic payment in crypto is banned, and cross-border settlement was legalised only under a narrow experimental regime for approved participants. USDT P2P is a market reality, not a compliant channel.
The compliant options
- Relocation (the common one). Many Russian developers moved to Armenia, Georgia or Kazakhstan and now bank there. Once residency and banking are genuine, you pay into a non-sanctioned jurisdiction through normal rails — dramatically lower risk. A third-country account used as a pass-through to someone actually in Russia can itself be a violation, so the relocation must be real.
- A provider that legally handles the corridor — see the contractor payouts rating and the regional CIS guide. Confirm it screens sanctions and excludes SDN banks.
- Convert or employ elsewhere via an EOR where the person has relocated.
Honest caveats
This is one of the highest-compliance-risk corridors in this directory. Sanctions rules shifted materially through 2024–2026 and continue to change. Screen every counterparty and bank against the SDN list before paying, keep a W-8BEN on file for US tax (it does nothing for sanctions), and retain qualified sanctions and local-tax counsel. Do not structure payments to disguise a blocked bank or restricted service.