In this article
An export deal closes. The buyer's wire is on its way. Then the receiving bank suspends the inbound foreign-currency credit, asks for documentation, and the funds sit in limbo for days — or weeks. The exporter cannot pay the freight forwarder. The settlement agent cannot distribute proceeds. The broker's commission is stuck behind the same blockage. Everyone on the deal is waiting on a system that nobody in the room controls.
This is not a hypothetical. It is a structural feature of the current correspondent banking environment, and it is happening with more frequency in 2026 than it did five years ago. Understanding why it happens, what alternatives exist at each stage of the chain, and how modern onchain routing changes the calculus for settlement professionals is the subject of this piece.
Elapsed times come from the worked export deal later in this article; the volume figure is the 2025 total cited in the onchain routing section.
Why banks freeze inbound FX in the first place
Before reaching for an alternative, it is worth understanding the machinery behind the freeze.
Correspondent banking refers to formal agreements between banks to provide payment services for each other, and it underpins the vast majority of cross-border payments in the international financial system. The problem is that this chain introduces multiple points of discretion. If a direct bilateral relationship does not exist between the buyer's local bank and the seller's receiving bank, the funds must route through one or more correspondent banks — and each institution in that chain applies its own proprietary compliance logic.
Those compliance filters have tightened considerably. Correspondent banks may bear regulatory and reputational risk for AML-CTF violations by the respondent banks. As a result, concerns about compliance with AML and customer due diligence requirements have led some banks to shed their correspondent banking relationships with smaller banks, often in emerging markets viewed as high-risk. This phenomenon is known as "de-risking," and according to the Bank for International Settlements, rising costs and uncertainty about how far due diligence should go to avoid regulatory sanction are cited by banks as among the main reasons for it.
The practical consequence is that the sharp decline in correspondent banking relationships, triggered by growing regulatory compliance costs, is hindering firms' ability to engage in international trade — and abrupt increases in regulatory scrutiny can unintentionally disrupt vital correspondent banking networks, resulting in significant and lasting negative impacts on firms' export opportunities.
For exporters, the freeze can take several forms. The most common:
- Straight suspension: The bank issues a "funds pending review" notice and holds the credit until the exporter submits additional documentation — commercial invoice, bill of lading, customs declarations, sometimes a written explanation of the business relationship.
- Return without advice: The correspondent bank returns the funds to the originating bank without telling the beneficiary why, leaving the exporter unaware that the money has bounced.
- Partial credit: The bank credits a portion of the inbound wire but deducts "lifting fees" charged by intermediate institutions, leaving a shortfall that breaks the settlement arithmetic.
- Regulatory hold: A central bank or financial intelligence unit flags the transaction, triggering a freeze that can last weeks and is outside the commercial bank's power to lift unilaterally.
Banks demand that exporters supply concrete proof that funds being received correspond directly to legitimate, verifiable trade activities. When a buyer in a foreign jurisdiction initiates a wire transfer, the transmitting bank, the correspondent banks, and the receiving bank all bear regulatory liability.
The documentation burden is not a formality. It is the first practical lever the exporter has.
Step one: Document before the wire moves
The single most reliable way to avoid an FX freeze is to make the transaction legible to every institution in the correspondent chain before the money moves.
Exporters must transition their operational mindset from merely securing sales to meticulously documenting the entire lifecycle of the transaction. Every commercial invoice, shipping manifest, and customs declaration acts as a vital data point that correspondent banks evaluate before clearing international remittances.
In practice, this means three things:
1. Pre-advice the receiving bank. Notify the receiving bank in writing — email to the trade finance desk or a formal SWIFT pre-advice — that an inbound wire of a specific amount, in a specific currency, from a specific originating institution is expected on a specific date. Attach the commercial invoice and a copy of the underlying contract. Banks that see an inbound credit matching a pre-advised transaction have far less reason to suspend.
2. Include structured remittance data in the wire instructions. Ask the buyer to populate all SWIFT fields completely: invoice reference in field 70, purpose of payment code, and beneficiary address. Truncated or ambiguous remittance data is one of the most common triggers for automated compliance holds.
3. Maintain a standing trade file at the receiving bank. For regular export corridors, keep an updated file with the trade finance or compliance team: master agreements, counterparty profiles, sample invoices. Relationship continuity reduces the probability that any single inbound wire is treated as anomalous.
This sounds basic, and it is. Yet banks and payment intermediaries often handle FX conversions differently, with limited visibility for businesses — and without upfront rate transparency, companies may face hidden costs that are only revealed after payment. Documentation reduces ambiguity at every node in the correspondent chain.
Step two: Open a foreign currency account in a stable jurisdiction
If the receiving bank is consistently problematic — either because it is in a jurisdiction subject to heightened scrutiny or because it lacks the correspondent relationships needed to receive the relevant currency cleanly — the structural answer is to receive the payment somewhere else.
A foreign currency account (FCA) held at a bank in a low-friction jurisdiction allows the exporter to receive USD (or AUD) directly, avoiding the conversion step that often triggers regulatory flags at the domestic bank. While inbound foreign exchange controls have not historically been as developed as the framework governing outbound flows, recent regulatory shifts represent a move towards tighter controls overall. Receiving in an offshore FCA sidesteps domestic conversion requirements until the exporter chooses to repatriate.
The mechanics for this vary by country. In India, for example, exporters are permitted to open and maintain foreign currency accounts with banks located in IFSCs, and export proceeds received in such accounts may be retained for up to three months from the date of receipt of funds. This measure is expected to enhance operational flexibility for exporters and promote IFSCs as preferred hubs for international trade settlement.
For exporters in markets with persistent FX restrictions, receiving in a Singapore, UAE, or UK-regulated FCA — and then deciding when and how to repatriate — is a legitimate operational strategy that settlement agents and trade finance attorneys have been deploying for years.
Step three: Instruct the buyer to pay in a different currency or via a different institution
When the problem is not the exporter's receiving bank but the buyer's originating bank — or the specific currency being sent — renegotiating the payment instruction is sometimes the fastest resolution.
The change of payment currency can be particularly useful for trade with countries that face shortages of dollars or difficulties accessing established international payment systems. Rupee settlement, for example, can reduce currency conversion costs and give exporters and overseas buyers an alternative to settling every transaction in the US dollar.
For exporters transacting in USD with buyers in markets where the dollar is tightly regulated, invoicing in a third currency — euro, Singapore dollar, UAE dirham — sometimes resolves the bottleneck entirely. The correspondent chain for that currency may be shorter or less scrutinized than the USD chain serving that corridor.
The practical negotiation with a buyer: "Our bank is experiencing delays on USD inbounds from your jurisdiction. Can you instruct your bank to remit in EUR from your EUR account, to our EUR account at [institution]?" In many cases, the buyer has exactly that flexibility, and the deal closes without any substantive change to the economic terms.
Step four: Use a regulated payment institution as the receiving layer
For many businesses looking to trade internationally, there is a persistent bottleneck in legacy banking infrastructure. Traditional institutions, often weighed down by outdated processes, are struggling to match the pace of modern commerce.
Regulated non-bank payment institutions — electronic money institutions (EMIs) in the EU, money service businesses (MSBs) in the US, and their equivalents in other jurisdictions — can receive inbound international wires on behalf of exporters, hold balances in multiple currencies, and then pay out to domestic bank accounts in local currency. They maintain their own correspondent relationships, often in corridors that are problematic for traditional banks, and their compliance architecture is purpose-built for cross-border flow.
In some regions, poor banking infrastructure can delay transfers or require local intermediaries, adding to the cost and complexity of payments. EMIs with local banking networks in the buyer's jurisdiction resolve precisely this problem: they receive the wire domestically (or in a well-connected hub), handle the conversion, and remit onward.
The limitation of this layer is that the exporter still faces sequential settlement. The proceeds land in one account, then need to be distributed outward to freight forwarders, brokers, agents, and co-exporters — each requiring a separate manual transfer, a separate FX conversation, a separate settlement timeline. When the deal involves multiple parties, this is where things break down even when the initial receipt is clean.
The multi-party settlement problem
Receiving the payment is only the first challenge. Distributing it correctly — across every party on the deal, in the right proportions, without delay — is the second, and it is where most trade finance workflows develop their sharpest friction.
Consider a straightforward export deal: an Australian manufacturer (AUD 750,000 / USD 485,000) ships machinery to a buyer in Southeast Asia. The settlement structure involves the manufacturer, a local freight forwarder, an international freight forwarder, a customs broker, and a commission agent. Each party has a different bank, a different jurisdiction, and a different currency preference. The manufacturer receives the full USD wire, then faces four separate outgoing transfers — each with its own FX conversion, correspondent chain, and compliance review. By the time the commission agent in the buyer's country receives their share, three to four additional business days have elapsed, and the FX rate applied to their USD-to-local-currency conversion is whatever the market happened to be doing that morning.
This is not a technology problem in the abstract. It is a workflow architecture problem. The current architecture assumes a single receiving entity who then redistributes — sequentially, manually, with all the slippage that implies.
Each market has its own reporting requirements and regulatory rules for cross-border transactions, adding to the administrative burden. Legacy infrastructure and over-reliance on correspondent banks and outdated treasury systems slows settlement and increases exposure windows. These challenges make it difficult to forecast costs or guarantee outcomes.
Where onchain routing changes the settlement architecture
This is where the nature of the problem shifts from "how do I receive the payment" to "how do I design the settlement so that every party receives simultaneously, with certainty, in a single transaction."
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. Settlement compresses from days to seconds, fees fall to single-digit cents on most chains, and the dollar balance becomes programmable.
The market for this infrastructure has matured rapidly. Stablecoin settlement has crossed from pilot to production in cross-border payments. Stablecoin payment volume doubled to roughly $400 billion in 2025, about 60% of it B2B. Visa expanded its settlement platform to USDC, EURC, and PYUSD across Ethereum, Solana, Stellar, and Avalanche, then launched USDC settlement for US banks in December 2025.
For the settlement agent managing a multi-party export deal, the significant development is not stablecoin settlement per se — it is programmable settlement that executes all distributions within a single transaction.
This is what shaka.deal is built to do. It operates as an onchain payment router on Ethereum. The buyer (or the buyer's on-ramp provider) sends one payment — the total deal amount — to a preset routing contract. That contract, configured in advance with the agreed shares for each party, distributes to every wallet simultaneously in a single transaction. The exporter receives their portion at the same moment the freight forwarder, the commission agent, and the settlement attorney receive theirs. There is no sequential redistribution. There is no second FX conversion moment. The routing is non-custodial: shaka.deal routes the funds, it never holds them.
The finality is definitive. An onchain settlement, once confirmed, cannot be recalled or reversed. Unlike a bank wire — which can be returned by a correspondent, recalled under certain regulatory conditions, or reversed by the originating institution — an executed onchain transaction is complete. For settlement agents and closing professionals who operate in the space between "funds in transit" and "deal done," this is a material change in certainty.
How a settlement agent structures an onchain distribution for an export deal
Walk through the mechanics concretely.
The deal: A USD 500,000 / AUD 770,000 export of agricultural equipment, with the agreed distribution below.
| Party | Agreed share | Amount (USD) |
|---|---|---|
| Exporter | 82% | 410,000 |
| International broker | 7% | 35,000 |
| Domestic agent | 5% | 25,000 |
| Freight and documentation coordinator | 4% | 20,000 |
| Settlement attorney's professional fee account | 2% | 10,000 |
| Total | 100% | 500,000 |
The traditional path: Buyer wires USD 500,000 to the exporter's bank. The bank holds it for compliance review (2-3 days). The exporter then initiates four outgoing wires. Each wire carries its own FX spread, correspondent fee, and compliance exposure. The settlement attorney receives their share last, after all other transfers have cleared. Total elapsed time from buyer wire initiation to full distribution: 5-9 business days. Total FX slippage: variable and unpredictable.
The onchain path: Before the deal closes, the settlement attorney deploys (or configures via shaka.deal) a routing contract with the five addresses and their precise percentage allocations — 82%, 7%, 5%, 4%, 2%. The contract address is published in the sale agreement as the payment destination. The buyer's treasury team (or their stablecoin payment provider) sends USDC 500,000 to that single address. The smart contract executes the distribution instantly and simultaneously to all five addresses in one transaction. Every party receives their share at the same block. The settlement attorney can confirm completion by reading the transaction hash — a public, immutable record. Total elapsed time: seconds. FX slippage risk: eliminated for the onchain leg, because all parties receive in the same asset at the same moment.
The settlement attorney's role in this architecture is exactly what it has always been: ensuring that the contractual terms are correctly reflected in the payment mechanism, that every party's address has been verified, and that the distribution schedule is documented and agreed before execution. The expertise does not diminish. The uncertainty does.
Practical considerations for the first onchain export deal
Counterparty readiness. The buyer needs to be able to send stablecoin. In 2026, this is increasingly a question of treasury infrastructure rather than willingness — B2B crypto payments have evolved from experimental technology to practical treasury infrastructure, with 60% of stablecoin volume now flowing through business transactions. Buyers who cannot send USDC directly can use a stablecoin on-ramp provider to convert their fiat instruction to an onchain transfer.
Stablecoin selection. The stablecoins most frequently used for B2B transactions are Tether (USDT), USD Coin (USDC), PYUSD, USDG, and FDUSD — reflecting the assets with the strongest liquidity, regulatory alignment, and enterprise adoption. For most export deals denominated in USD, USDC on Ethereum is the practical default: it is regulated, fully attested, and broadly accepted by off-ramp providers in virtually every jurisdiction. As of 2026, USDC is registered across more than 30 chains, including Ethereum, Solana, Base, Arbitrum, and Avalanche, and holds full regulatory recognition under the EU's MiCA framework.
Off-ramp for each party. Parties who need local fiat need an off-ramp — a regulated provider who converts USDC to domestic currency and credits a bank account. This market is deep in major corridors. In thinner corridors, the off-ramp selection needs to be part of the deal structuring conversation, not an afterthought. The settlement agent's job includes confirming that every party has a confirmed off-ramp before the routing contract is deployed.
Documentation and accounting. The onchain transaction hash serves as the payment receipt. It is timestamped, immutable, and publicly verifiable. For accounting and trade documentation purposes, this is equivalent to — and in some respects more reliable than — a SWIFT confirmation. Export documentation, customs declarations, and invoice matching still need to reference the correct payment event. The transaction hash should be filed alongside all other settlement documents.
Compliance perimeter. Compliance requirements — sanctions screening, AML monitoring, invoice matching, accounting treatment, and the requirement that the supplier either accept the token directly or have an off-ramp partner that converts it to local fiat — do not change. The rail is faster; the compliance perimeter around it is not lighter. Settlement attorneys and agents who manage the compliance documentation for traditional wire settlements perform exactly the same function in an onchain settlement workflow.
The hybrid model: onchain distribution, domestic fiat receipt
Not every exporter needs to hold USDC. Not every counterparty is ready for a fully onchain workflow on day one. The hybrid model handles this:
- Fiat to USDCThe buyer's payment provider converts fiat to USDC and initiates the onchain transfer.
- Simultaneous routingshaka.deal routes and distributes to all party addresses simultaneously.
- Local off-rampEach party's off-ramp provider — whether that is an EMI, an OTC desk, or a regulated exchange — converts their USDC share to local fiat and deposits it to their domestic bank account.
In this model, the "freeze" risk is shifted from the critical settlement moment to the off-ramp leg — and the off-ramp leg is jurisdictionally local, meaning it is governed by the domestic bank's relationship with the party, not by an international correspondent chain. A domestic bank in Australia receiving an AUD transfer from a local licensed payment provider faces none of the correspondent scrutiny that the same bank faces receiving a USD SWIFT wire from a Southeast Asian institution.
The correspondent bank de-risking problem, which has been triggered by growing regulatory compliance costs and is hindering firms' ability to engage in international trade, is structurally bypassed — because the international leg is onchain, and the domestic leg is a simple local transfer.
What settlement professionals should take from this
The frozen inbound FX problem is not going away. The challenge for regulators and the industry alike is to develop a framework that preserves the integrity of the correspondent banking network while ensuring that compliance costs and supervisory expectations are proportionate to actual risk — and the gap between policy aspiration and operational reality remains significant.
In that environment, settlement agents, brokers, trade finance attorneys, and OTC desks who understand the onchain distribution option are offering their clients something genuinely different: a settlement architecture where the question of "did everyone get paid?" has an answer that is verifiable in seconds, not days.
The approach is layered:
- Documentation first: Make every inbound wire legible to the correspondent chain before it moves.
- Banking layer second: Optimize the receiving jurisdiction and account structure for the corridors that matter most.
- Alternative rails third: Stablecoin settlement for the international leg, local off-ramp for the domestic leg.
- Onchain routing for multi-party deals: One incoming payment, preset shares, simultaneous payout — in a single transaction with finality.
That last layer is the one that changes what multi-party export settlement can look like. shaka.deal is the infrastructure that executes it: the routing contract takes the full deal amount and distributes it instantly to every party at their agreed share, in one transaction, with no funds held in transit and no sequential redistribution delay.
For the settlement professional managing a deal where every party is watching a different bank account and waiting for a different wire, the value is not abstract. It is the difference between a closing that finishes in seconds and one that finishes in a week — assuming the correspondent chain cooperates at all.
In a world where it increasingly does not, that difference is the deal.
