A refused payment is not the same as a prohibited one. Much of the time a bank declines a transaction that is perfectly lawful, because its own risk policy won't touch anything Russia-linked. Telling a legal block from a policy block is the first, and most important, step.
The answer is route and documentation, not persuasion. A clean contract, a documented purpose and a corridor the banks involved can actually process are what let a legitimate payment through — pressing the bank rarely is.
There is no route to find. The right response is to change the counterparty or not make the payment — an actual legal block is a stop sign, not an obstacle to engineer around.
When a bank refuses a payment to or from Russia, it can be for one of two fundamentally different reasons, and everything depends on which. Either the transaction is actually prohibited — it involves a sanctioned party or a restricted activity — or it is lawful, but the bank's own compliance policy declines to process it. These look identical from the outside: the money simply doesn't move. They call for opposite responses.
The mistake is to treat every refusal the same way — either giving up on a payment that was fine, or pushing to complete one that was genuinely blocked. The first question, always, is whether the payment is lawful. Only once that is answered does it make sense to ask what to do about the refusal.
A refused payment is either genuinely prohibited or lawful-but-declined by the bank's own policy — they look identical but call for opposite responses. Ask whether the payment is lawful before asking how to respond to the refusal. Route problems have route solutions; substance problems do not.
In practice, a large share of refused Russia-linked payments are lawful ones caught in the bank's caution. Banks manage their own risk by declining whole categories of business rather than assessing each transaction — a lawful payment is refused not because it breaks a rule, but because the bank has decided the category isn't worth the risk. The reasons stack up:
De-risking: the bank avoids Russia-linked business wholesale to keep its own exposure down, regardless of a specific transaction's legality.
Correspondent constraints: the bank's own correspondent banks won't process the flow, so it can't either, even if it wanted to.
Compliance policy: internal thresholds and documentation requirements that go beyond what the law strictly demands.
None of these is a statement that your payment is illegal. They are the bank protecting itself — which is why a lawful payment can be refused and a differently-structured, equally lawful version of the same payment can go through.
For a lawful payment refused on policy grounds, documentation is usually the lever — not argument. A bank declines what it cannot quickly satisfy itself about; give it a clear, verifiable picture and much of the friction goes.
That means a clean underlying contract, a documented and legitimate commercial purpose, evidence of who the counterparty really is and who owns it, and a transaction that plainly fits the account's expected activity. A payment that arrives with its legitimacy already demonstrated is a different proposition to one the bank has to investigate.
What documentation cannot do is change the substance. It cannot make a prohibited payment lawful, and it should never be assembled to disguise what a transaction really is. If the payment is genuinely blocked, no amount of paperwork is the answer — and trying to make it look otherwise is precisely the line a legitimate adviser will not cross.
For a lawful payment, the practical fix is often the route rather than the bank. A payment fails because it is being sent by a corridor the banks involved cannot process; the same payment, in a currency and through banks that actually handle the flow, clears. Matching the route to what both ends can process does more than any appeal to the refusing bank.
But there is a point where the problem is not the route at all — it is the counterparty or the transaction itself. If a payment is refused because of who is really behind the counterparty, changing the corridor is not the answer and would be the wrong instinct entirely. The honest response there is to change the counterparty, or not to proceed. Knowing which situation you are in is the whole point of the first question — route problems have route solutions; substance problems do not.
For a lawful payment, the fix is usually the corridor and the documentation, not pressing the refusing bank. Match the route to what both banks can process. But where the problem is who's really behind the counterparty, the answer is to change the counterparty — not the route.
The strongest position is built before the payment, not scrambled together after a refusal. If the legitimacy of a transaction — the contract, the purpose, the counterparty's real ownership — is established and documented in advance, a refusal becomes something you can respond to with evidence rather than argument, and often something you avoid altogether by structuring the payment correctly from the start.
This is also the difference between a durable arrangement and a one-off scramble. A group that documents the legality of its recurring payments up front, and routes them through corridors that work, spends far less time firefighting stuck transfers than one that discovers each problem at the moment the money fails to move.
Legitimacy documented in advance — clean contract, clear purpose, real ownership — turns a refusal into something you answer with evidence, or avoid by structuring correctly. Recurring payments documented up front firefight far less than ones fixed after they fail.
Our role is the Russian side of this. We establish the facts that determine whether a payment is lawful and processable — who the Russian counterparty really is and who owns it, whether the transaction and its documentation are sound, and which corridor and structure give a legitimate payment the best chance of clearing. On how your home regime applies to the payment, we coordinate with your OFAC or EU counsel rather than opining on their law ourselves.
What we do not do is help push a bank into a payment it has refused, or engineer a route around a genuine legal block. The value is in getting a lawful payment structured and documented so it clears on its merits — and in being straight with you when a payment is one that shouldn't be made at all.
Often, no. A large share of refused Russia-linked payments are lawful transactions that the bank declines under its own risk policy — de-risking, correspondent constraints, or internal compliance thresholds that go beyond what the law requires. A refusal is the bank protecting itself, not a ruling that your payment is illegal. The first step is establishing which kind of refusal it is, because the response is completely different.
If the payment is lawful, yes — by getting the contract, purpose and counterparty ownership documented and the payment routed through a corridor the banks can actually process. That's what lets a legitimate payment clear on its merits. If the payment is genuinely prohibited, there's no route to find, and the honest answer is to change the counterparty or not proceed — we won't help engineer around a real legal block.
Usually the route and the documentation matter more than persuasion. A bank rarely reverses a policy refusal because it's argued with; it processes a payment it can quickly satisfy itself about. So the productive path is structuring and documenting the payment so it clears — and, where the corridor is the problem, using one the banks involved can actually handle — rather than pressing the refusing bank.
By building the position before the payment, not after a refusal. Establishing and documenting the legitimacy of your recurring payments up front — the contracts, the purpose, the real ownership — and routing them through corridors that work turns a repeated firefight into a routine that clears. It's the difference between a durable arrangement and discovering each problem when the money fails to move.
Practical support for international business in Russia.