July 7, 2026
A single cross-border payment can pass through three or four correspondent banks, each adding fees, delays, and a point where your payment can freeze. That is how the system works without direct Swift access. Read on for the real cost of operating without it and how a modern PSP with a dedicated IBAN keeps B2B payments moving.
For most businesses, Swift feels like a given, the backbone of international business payments and the standard way to move money across borders. Yet for a surprisingly large number of companies, direct Swift access remains out of reach for various reasons:
The result is the same: a business that needs to pay suppliers, partners, or employees in other countries cannot do so directly.
Without direct Swift, international payments become an exercise in guesswork: money disappears into correspondent chains, with no visibility on arrival, double conversion reducing the amount, and delays stretching from days to weeks, with no one to call for an update. It helps to look at how a Swift payment actually works: it takes one to five business days, largely because around 75% of cross-border transactions rely on correspondent banks, with an average of 1.3 intermediaries per transfer, each adding processing time, compliance checks, and fees.
A Swift report from 2025 found that while 75% of payments reach the beneficiary bank within 10 minutes, over 80% of total delays occur in the final leg of the journey, after the payment leaves the Swift network. So if you wonder how long a Swift transfer takes, the honest answer is that it depends entirely on the chain: the root causes include regulatory reporting requirements, currency controls, lack of real-time infrastructure, and manual compliance checks. For a business routing payments through multiple correspondent banks, these delays multiply at every stop.
Without direct Swift, every transaction runs through infrastructure that was not built for speed or transparency. And the cost of that shows up directly on the bottom line of any company managing global business payments at scale. Direct Swift access is a major advantage for any business and is arguably one of the most cost‑effective solutions for international payments available on the market. When a bank refuses to provide it, however, the company is forced to go through intermediaries and ends up paying significantly more in fees.
The risks of relying on correspondent banking chains go beyond delays and fees: when one bank in the chain has compliance problems, every payment passing through it becomes suspect.
The Danske Bank Estonia scandal illustrates the risks clearly. Between 2007 and 2015, approximately 200 billion euros of suspicious payments flowed through the bank's Estonian branch, and Danske later pleaded guilty to bank fraud conspiracy, agreeing to pay over $2 billion to resolve investigations into its failures, where even a routine AML check had been quietly bypassed for years. The bank had processed $160 billion on behalf of nonresident customers through U.S. banks.
The fallout extended far beyond Danske itself, with correspondent banks including Deutsche Bank and JPMorgan terminating their relationships with Danske's Estonian branch and financial compliance departments across the system tightening their scrutiny as a result.
Innocent businesses that had never dealt with Danske suddenly found themselves with a frozen bank account or closed relationship simply because their transfers had once passed through part of the chain, leaving them to prove the legitimacy of their transactions while losing time and money.
Another case shows how routine transfers can get stuck in correspondent chains. In March 2024, a customer initiated a Swift transfer of $239,107 from a Citibank UK account, but the transfer was rejected because the correspondent bank needed additional checks. Citibank contacted the correspondent bank multiple times between April and August 2024, yet the funds were not returned until late August.
As a result, the customer waited over five months for the funds to be returned, even though they should have been sent to the partner within days. The complaint eventually reached the UK Financial Ombudsman, which found Citibank not at fault because the delay was caused by the correspondent bank.
This highlights a crucial reality: when a payment travels through correspondent chains, the originating bank has limited control over what happens downstream, and the business that sent the payment has even less.
What a payment service provider actually does is handle one of the core tasks banks are meant to perform: moving money from sender to recipient quickly, without hidden pitfalls or negative consequences. Under the hood of a PSP payment lies a systematic infrastructure that we can break down into parts.
The fundamental difference is architectural: where banks route payments through chains of correspondent banks, each with its own compliance checks and processing times, PSPs offer direct settlement rails that carry a payment from sender to recipient along a shorter, more transparent route. Fewer stops mean fewer opportunities for delays, fees, or compliance flags, and settlement completes in near real-time payments against the multi-day correspondent route. The difference is structural, not marginal.
For any company that depends on B2B cross-border payments, this architecture is the difference between hours and weeks. COLIBRIX ONE is a good example of a PSP that solves banking problems in one go: the platform offers direct Swift access in EUR, USD, and PLN within a single dedicated IBAN issued in the company's name. Payments go directly from the company to its counterparties, and the need to open separate bank accounts in each new jurisdiction simply disappears. Moreover, COLIBRIX ONE holds principal partnerships with VISA and Mastercard, and its support team responds many times faster than bank employees.
Operating without direct Swift access forces businesses into a web of correspondent banking chains, where each link adds cost, delay, and risk: a payment that should take hours can stretch into days or weeks, fees accumulate at every stop, and when any bank in the chain faces a compliance problem, innocent businesses can find their payments frozen or their accounts closed. The Danske Bank scandal is a stark reminder that companies which never dealt with Danske still felt the impact because their payments passed through banks that had.
COLIBRIX ONE remove these risks by offering clear cash flow solutions: direct Swift through a dedicated IBAN, without long correspondent chains or intermediaries. The choice is clear: accept the delays and risks of traditional correspondent banking, or switch to a provider that eliminates them entirely. For companies relying on international business payments, this decision shapes both cash flow and supply chain reliability.
Open your account →
Choosing a payment processor is a strategic foundation for startups that directly impacts cash flow, customer conversion, and long-term...
Choose the ideal payment processor for startups to enhance cash flow, ensure security, and scale effortlessly...
At scale, secure international payments depend on a predictable, automated operating model rather than manual human oversight...
At COLIBRIX ONE, we’re a team of innovators reshaping how businesses experience payments. Have a question? Send it through the form below.
© 2026 COLIBRIX ONE
