# How to pay a contractor in a country your bank will not wire to
A practical guide for finance teams, settlement agents, and deal professionals navigating the compliance barriers that block standard wire transfers to dozens of countries.
---
The work is done. The deliverable is approved. The invoice is sitting in your inbox. And your bank's international wire screen will not let you proceed — or if it does, the transfer bounces back four days later with a terse rejection code that tells you almost nothing useful.
This is not an edge case. It is a structural reality of the correspondent banking system in 2026, and it is catching more businesses off guard than ever before. If you work in settlement, deal structuring, project finance, real estate closings across borders, or any kind of multi-party arrangement that involves professional services in emerging or restricted markets, you need a working mental map of why this happens and what the legitimate, auditable paths forward look like.
This article builds that map.
## Why banks block international wires — and why it is getting worse
To understand the problem, you have to understand how a wire actually travels. Cross-border financial transfers typically rely on a system known as correspondent banking. Your bank hands the payment to a correspondent bank, which hands it to another, which finally credits the beneficiary. Each hop adds a fee, a cutoff time, and a compliance checkpoint. That chain is not just slow — it is increasingly fragile.
Correspondent banking — the network of relationships that enables cross-border payments — continues to contract in ways that threaten financial inclusion. The Bank for International Settlements reports that the number of active correspondent banking relationships has declined by 25% since 2011, with the steepest reductions affecting developing economies in Africa, the Pacific Islands, and the Caribbean. In 2026, this trend shows no sign of reversing. De-risking — the wholesale termination of correspondent relationships with entire regions or categories of respondent banks — remains the default response for many global banks facing uncertain regulatory expectations and disproportionate compliance costs.
The practical result: your bank may have no correspondent relationship with any bank in a given country. The wire simply cannot route. Even when a relationship exists, it may be constrained.
Then there is the sanctions and watch-list dimension. Sanctions enforced by OFAC can cause wire transfers to be rejected. Transfers involving Iran or other restricted regions may be blocked. Banks must comply with legal restrictions and cannot act as a substitute for sanctioned transactions. Beyond hard OFAC prohibitions, the FATF blacklist and grey list create softer but equally real friction. The FATF blacklist is reserved for countries with the most severe and persistent AML/CFT deficiencies. The distinction matters operationally: grey-listed countries require closer monitoring, while blacklisted countries can trigger outright restrictions on correspondent banking relationships, additional reporting obligations, and in some cases a near-total unwillingness among Western banks to process transactions tied to the jurisdiction at all.
Three countries sit on the FATF blacklist as of June 2026 — Democratic People's Republic of Korea, Iran, and Myanmar — while 22 jurisdictions face increased monitoring. As of June 2026, grey-listed jurisdictions include Angola, Bolivia, Bosnia and Herzegovina, Bulgaria, Cameroon, Côte d'Ivoire, Democratic Republic of the Congo, Haiti, Iraq, Kenya, Kuwait, Laos, Lebanon, Monaco, Nepal, Papua New Guinea, and several others. The June 2026 plenary added Iraq and Bosnia to the grey list while removing Algeria and Namibia.
Being on the grey list affects banking access; being on the blacklist can trigger outright de-risking by correspondent banks. Correspondent banks impose enhanced due diligence and often restrict wire transfers to grey-listed jurisdictions. Enhanced Due Diligence under FATF Recommendation 19 means banks must obtain senior management sign-off for any new accounts or transactions tied to grey-list jurisdictions. This approval step alone can add 30–90 days to deal timelines.
For a project with a payment deadline tied to a closing, 30 to 90 days is not an inconvenience. It is a deal-breaker.
Russia sits in a distinct category. In March and July 2025, pursuant to international and multilateral action to intensify financial sanctions against Russia, specialised financial messaging providers such as SWIFT were prohibited from providing services to designated entities under EU Council Regulation (EU) 833/2014. The regulation prohibits all EU legal operators from facilitating or entering into any business or financial transactions with designated entities. As SWIFT is incorporated under Belgian law and must comply with EU regulation, SWIFT disconnected all designated entities from the SWIFT network.
There is also a quieter category of restriction that surprises many finance teams: individual banks simply choosing to stop wiring to certain countries based on internal risk models, without any OFAC or FATF compulsion. Some banks are unable to receive or send international wire transfers from certain countries due to regulatory, compliance, or banking partner constraints — and those constraints are their own, not necessarily mandated by law. A community bank in the US Midwest may have zero correspondent infrastructure for Southeast Asian corridors not because of a sanction, but because the volume never justified building one.
Some financial institutions will not accept or process any wire transfers, whether incoming or outgoing, to or from high-risk countries. They comply with all sanctions implemented by the U.S. Department of Treasury's OFAC. Additional countries may be added to the prohibited list at any time.
Put all of this together and the list of jurisdictions where a standard wire will fail — either at the outset or mid-transit — is longer than most finance professionals expect.
## The four corridors where this problem is most acute
Understanding the specific geography of payment failure helps you triage faster. These are the four corridor types that generate the most friction in 2026:
**1. OFAC-comprehensively-sanctioned jurisdictions.** Iran, North Korea, and Cuba sit under comprehensive US sanctions that make standard wire transfer impossible regardless of which bank you use. Engaging a licensed sanctions attorney before any payment structure is attempted here is not optional — it is the starting point.
**2. SWIFT-disconnected Russian banks.** In regions under sanctions, SWIFT doesn't function, and many financial services that supported business processes are inaccessible. For counterparties at Russian banks designated under EU or US measures, the messaging layer itself is gone. Payments may be legal in a strict contractual sense but are operationally impossible through standard rails.
**3. FATF grey-listed countries with active correspondent de-risking.** This is the largest and fastest-growing category. Countries like Kenya, Lebanon, Bolivia, Vietnam, and Bulgaria now carry grey-list status that causes many correspondent banks to apply internal restrictions regardless of the individual counterparty's clean record. Some correspondent banks pre-emptively restrict volume to newly listed corridors before formally requesting enhanced due diligence, so early conversation reduces the risk of unexpected payment delays.
**4. Countries with thin or absent correspondent infrastructure.** Parts of sub-Saharan Africa, the Pacific Islands, and certain Caribbean jurisdictions have seen correspondent relationships collapse entirely. A contractor in Lagos, Manila, or Buenos Aires submits work, you approve it, and then the money takes four business days, loses a significant percentage to intermediary bank fees, and sometimes bounces back with a cryptic SWIFT rejection you can't decode.
Knowing which category your destination falls into determines which solution applies.
## What doesn't work (and why)
Before describing the paths that do work, it is worth being honest about the ones that fail, because teams waste weeks on dead ends.
**Trying multiple banks.** If the problem is OFAC sanctions, no US-regulated bank can help you. If the problem is a collapsed correspondent corridor, calling five banks typically surfaces the same missing infrastructure. The bottleneck is systemic, not specific to your bank.
**Payment platforms with geographic restrictions.** Services like PayPal have geographic limits that track closely with correspondent banking risk. PayPal can freeze funds for reviews, delaying payouts without notice. Some markets restrict PayPal for business payouts or require workarounds that add fees. Fintech platforms are convenient but often come with transaction fees and may not be supported in all countries. They route through banks eventually, and when the bank layer breaks, the platform breaks too.
**Informal cash arrangements.** These create accounting nightmares, tax exposure, and potentially serious compliance liability. They are not a solution for any professional context — and in most jurisdictions they are not a solution at all.
**Waiting.** Project timelines, milestone payments, and closing schedules do not pause while a wire spirals through a compliance review. Finding out your bank has rejected your wire transfer request is never fun. If the request was particularly time-sensitive, it can also be stressful to find out the money isn't where it needs to be.
## The paths that work: a structured decision tree
Here are the legitimate, auditable methods that finance professionals are actually using in 2026. They are not equally suitable for every situation — the right choice depends on the corridor, the amount, the number of parties receiving payment, and your organisation's appetite for operational setup.
### Path 1: Local payment intermediaries and in-country agents
For grey-listed or thin-infrastructure jurisdictions where the contractor is a legitimate, non-sanctioned individual or entity, the most direct approach is routing through a locally licensed payment or settlement agent. The agent receives a wire from you in a supported corridor (typically USD into a US account or EUR into a European account), then disburses in local currency to the contractor.
This is expensive — agent margins on emerging-market corridors can run 2 to 4% on top of FX — and it adds a party whose AML procedures you are implicitly relying on. But it is legal, documentable, and used routinely by project finance teams, NGOs, and professional services firms operating in restricted corridors. International payments are often scrutinised under anti-money laundering and financial crime laws. Depending on the payment amount, destination country, and method, you may need to provide additional documentation to your bank or payment processor.
For deal professionals managing multi-party distributions — a closing where several service providers in different countries are owed simultaneous payments — this path becomes operationally complex fast. Each local agent operates differently, settles on different timelines, and gives you no single view of whether all parties have actually been paid.
### Path 2: Contractor banking relocation
The one rail that works everywhere else — a plain international wire — reliably breaks for anyone based in Russia or Belarus. Paying them is legal in most cases; getting the money there is a separate problem. One common structural solution: the contractor themselves opens a bank account in a supported jurisdiction — Georgia, Armenia, Turkey, Serbia, and the UAE are frequently used for Russian contractors — and receives payment there.
This places the compliance work on the contractor, which may or may not be practical depending on your relationship, their situation, and local regulations. It is not a solution you can impose; it requires the contractor's willingness and capability. And it takes time — weeks, sometimes months — to establish properly.
### Path 3: Stablecoin payment with an OTC desk for onramp or offramp
This is where the payment landscape has fundamentally shifted since 2023. One of the most promising new fintech advances is the use of stablecoins. They combine blockchain's efficiency with fiat currency's predictability, enabling funds to reach contractors within minutes rather than days, with lower intermediary fees and fewer conversion losses.
The mechanics in practice: you convert USD (or AUD) to a stablecoin such as USDC or USDT through a regulated OTC desk or exchange, transfer onchain to the contractor's wallet address, and the contractor converts to local currency through a local exchange or OTC desk in their country. B2B stablecoin payments are commercial transactions between businesses settled in dollar-pegged tokens, typically USDC or USDT, on public blockchains rather than through bank wires, ACH, or SWIFT.
USDT has the deepest liquidity globally, particularly across Asia, Latin America, and emerging markets, and is the default rail on exchanges and OTC desks in those regions. USDC is issued by a US-regulated entity with monthly attestations and is often preferred by companies with US banking relationships, auditors, or compliance teams that want a more conservative reserve and reporting structure.
A stablecoin OTC desk is an over-the-counter trading venue that intermediates large stablecoin orders bilaterally, outside central order books, with negotiated pricing and settlement terms. An OTC desk can help businesses convert larger amounts between fiat and crypto before or after a cross-border payment. The OTC desk supports the conversion, not the transfer itself. For amounts above USD $50,000 (approximately AUD $76,000), going through a regulated OTC desk rather than a retail exchange is standard practice — it avoids price slippage and gives you proper documentation for your accounts.
### Path 4: Employer of Record or global payroll service
For longer-term contractor relationships — not one-time deal payments — an Employer of Record (EOR) or global payroll platform can absorb the corridor complexity. Services like Playroll simplify international contractor payments, ensuring compliance with local laws and handling taxes. These platforms maintain local entities or banking relationships in dozens of countries, receive your wire in a supported currency, and disburse locally.
The tradeoff is cost and classification risk. EOR services are priced for ongoing payroll, not one-time milestone payments, and re-classifying a project contractor as an employee for compliance purposes can have downstream legal consequences in some jurisdictions.
## The multi-party problem: when one deal has four contractors across four countries
Single-contractor scenarios are manageable with any of the paths above. The problem becomes significantly harder when a deal involves simultaneous payments to multiple parties across multiple jurisdictions — which is routine in structured transactions, commercial real estate closings, software development projects with international subcontractors, and media productions with global talent.
Consider a concrete scenario: a US-based project manager coordinates a deliverable involving a legal analyst in Kenya, a technical architect in Bulgaria, and a data scientist in Vietnam.
| Party | Based in | Fee (USD) | Fee (AUD) |
| --- | --- | --- | --- |
| Project manager | United States | $12,000 | $18,300 |
| Legal analyst | Kenya | $4,000 | $6,100 |
| Technical architect | Bulgaria | $7,500 | $11,450 |
| Data scientist | Vietnam | $5,000 | $7,630 |
| **Total** | **Four countries** | **$28,500** | **$43,480** |
Kenya, Bulgaria, and Vietnam are all FATF grey-listed jurisdictions as of 2026. Each wire requires enhanced due diligence. Each hits a different correspondent banking relationship. Each has a different cutoff time and a different likelihood of delay.
The deal closes. The client sends one payment. But disbursing it sequentially across four corridors means four opportunities for delay, four separate reconciliation entries, and no guarantee that all parties are paid simultaneously — which matters enormously when payment obligations are tied to milestone delivery.
This is precisely the problem that onchain payment routing is designed to solve. Settlement compresses from days to seconds, fees fall to single-digit cents on most chains, and the dollar balance becomes programmable, meaning a payment can carry conditions and chain into longer treasury workflows.
shaka.deal is built specifically for this structure. A single inbound payment — in stablecoin — enters the deal route. Preset share allocations are configured in advance: each party receives the USD share in the table above. When the payment arrives, all four wallets receive their allocations in the same transaction, simultaneously, with finality. No sequential wiring. No float. No question about whether everyone has been paid.
Shaka.deal is non-custodial — it routes, it does not hold. Funds do not sit in an intermediate account awaiting manual distribution. The routing is the settlement. Each party receives their share the moment the transaction confirms on Ethereum, and that confirmation is immutable. Onchain payment settlement does not carry the risk of reversal that plagues traditional wire environments — settlement is final at the moment it posts to the ledger, without the ambiguity of clearing windows.
The clearing agents, brokers, and settlement professionals managing these deals do not lose their role in this structure. Their role is to design the deal, verify the parties, manage the documentation, and ensure compliance. shaka.deal handles the mechanical distribution with the precision and speed that manual wiring cannot match. The settlement professional remains central — they just stop spending hours chasing wire confirmations across four corridors.
## The documentation layer: what your accounts team needs regardless of method
However the payment moves, your finance and compliance team needs a coherent paper trail. This is not just good practice — it is what protects you if the payment is ever reviewed by a tax authority, auditor, or regulator.
For every international contractor payment, you need:
**A proper invoice.** Dated, denominated in the agreed currency, referencing the specific deliverable. For US companies paying foreign contractors whose work is performed entirely outside the United States, there is generally no withholding obligation — there's no US restriction on engaging a contractor abroad, and where the services are performed entirely outside the United States the income is foreign-source, which means no Form 1099, no chapter 3 withholding, and no 1042-S. But that determination requires verification of the contractor's status, which means collecting the appropriate form before payment moves.
**Foreign status documentation.** Collect a W-8BEN (for foreign individuals) or W-8BEN-E (for foreign entities) before the first disbursement runs. These confirm the contractor's foreign status and applicable treaty withholding rates.
**A sanctions screen record.** Before any payments are released, a critical check must be performed: screening all contractors against global watchlists, such as the OFAC sanctions lists. Sending a payment to a sanctioned individual, even by accident, can have legal and financial repercussions. Screen every payee against OFAC and global watchlists at both onboarding and immediately before each payment executes. A contractor who clears initial onboarding can be flagged months later, and a single disbursement to a sanctioned party after status changes creates unrecoverable exposure.
**The rate at payment.** For stablecoin payments, the fair market value of the stablecoin at the moment of transfer is the tax-relevant figure. Most jurisdictions tax crypto payments at the fair market value on the date of settlement. The IRS treats virtual currency wages as ordinary income. Stablecoins do not avoid tax — they replace the wire, not the W-2. Document the rate at settlement, not at invoice date.
**Proof of receipt.** With onchain routing, this is automatic — the transaction hash is permanent, public, timestamped, and auditable by any party with the wallet address. That beats chasing a wire confirmation SWIFT MT103 from a correspondent that may take 48 hours to respond.
## Practical checklist for the professional facing a blocked wire
If you are staring at a wire rejection or anticipating one, work through this in order:
Blocked wire checklistFrom identifying the block to confirming receipt
Identify the specific blockIs this OFAC sanctions (the destination country or individual is comprehensively blocked), FATF-driven enhanced due diligence (the wire can proceed with documentation), or a correspondent banking gap (no routing exists at all)? Each requires a different response.
Consult your legal or compliance team before attempting workaroundsEspecially for Russia, Iran, North Korea, Myanmar, and Cuba. The distinction between "payment is legal but wire is blocked" and "payment is prohibited" is not always intuitive. Paying a Russia- or Belarus-based contractor may be restricted by OFAC, EU, and UK measures aimed at specific banks, entities, and individuals, and you should check current designations and loop in counsel before real money moves.
Map the counterparty's access to alternativesDoes the contractor have a wallet? Do they have access to a local exchange that can receive USDC or USDT and offramp to local currency? Do they have a bank account in a third country that can receive your wire? The solution space depends on the contractor's infrastructure as much as yours.
Choose the payment rail based on amount and frequencyFor a one-time payment under USD $5,000 (AUD $7,630), a fintech platform with the right corridor coverage may be adequate if their geographic restrictions do not apply. For larger amounts, or for deals with multiple simultaneous payees, stablecoin routing through a verified onchain tool like shaka.deal becomes the more efficient and auditable option.
Document everything before money movesInvoice, foreign status form, sanctions screen, FX rate at time of payment. The compliance layer must be complete before settlement, not assembled afterward.
Confirm receiptWith stablecoin payments on Ethereum, receipt is verifiable by any party instantly. With wire alternatives, confirm receipt explicitly with the contractor before marking the obligation closed.
## Why the settlement professionals using these structures are ahead
The finance teams and settlement agents who have built fluency with stablecoin-based payment routing are not doing something exotic. They are solving a concrete operational problem: the correspondent banking system cannot reliably reach dozens of countries, and that gap is widening, not narrowing. When deciding how to pay contractors, consider the trade-offs between speed, fees, and compliance requirements. For professionals managing multi-party deal closings, those trade-offs resolve clearly in favour of onchain routing once the amounts, the number of parties, and the corridor complexity cross certain thresholds.
The stablecoin market itself reflects this shift. Stablecoin transfer volume reached USD $27.6 trillion in 2024, exceeding Visa and Mastercard combined, per Artemis and Dune data published in January 2025. Stablecoin settlement volume is forecast to reach USD $33 trillion in 2026. This is not speculative activity — it is commercial payment flow migrating to a more reliable rail.
shaka.deal sits at the specific slice of that rail that matters most for deal professionals: multi-party, simultaneous, preset-share distribution. One incoming payment, configured splits, instant routing to every party in the same transaction, with finality and a permanent onchain audit trail. The settlement agent does their job — structures the deal, verifies the parties, ensures the documentation is complete — and the routing handles itself.
For the contractor in Lagos, Tbilisi, Sofia, or Buenos Aires waiting for payment that their client's bank cannot send, this is not an abstraction. It is the difference between being paid this week and waiting indefinitely while wire systems sort themselves out. For the finance professional managing that payment obligation, it is the difference between a closed deal and an open liability.
The correspondent banking system will not get faster on its own. The professionals who learn to route around the gaps — legally, documentably, and with precision — are the ones whose deal timelines will not be held hostage to the next unexpected wire rejection.
*This article is for informational purposes and does not constitute legal or compliance advice. Sanctions regulations change frequently. Always verify current OFAC, FATF, and local regulatory requirements with qualified legal counsel before structuring cross-border payments.*