Treasury Bank Connectivity: SWIFT vs Host-to-Host vs API vs EBICS

Corporate treasury connects to banks through four main channels — SWIFT, host-to-host, API and EBICS. SWIFT gives multi-bank reach through one standardized connection; host-to-host is a direct, efficient link to a single bank; APIs bring real-time balances and payment status; and EBICS is a regional standard used mainly in parts of Europe. There's no single best choice — you pick per bank and per need, and most treasuries run a mix. The important thing is not to confuse the channel (how the message travels) with the format (what it says).

What bank connectivity does

Whatever the channel, connectivity does two jobs: bring bank statements in (so you can build the cash position and reconcile) and send payment instructions out (and get their status back). Everything below is a different way to move those two flows.

SWIFT

SWIFT is the global bank-messaging network. For a corporate, connecting to SWIFT (directly or, more commonly, through a service bureau or a bank's channel) means one standardized connection that reaches many banks. That's its strength: instead of a separate integration per bank, you speak one network. The trade-offs are cost and complexity — it's an investment that pays off when you have many bank relationships across regions, and is often overkill for a handful.

Host-to-host (H2H)

Host-to-host is a direct, secure file exchange between your systems and one specific bank — typically automated file transfer (SFTP and similar). It's efficient and reliable for a small number of strategic, high-volume relationships: once set up, statements and payment files flow automatically. The catch is that it's per bank — every host-to-host link is its own setup, so it scales poorly across many banks.

API

Bank APIs bring real-time, request-response connectivity — fetch a balance now, submit a payment and get its status immediately, rather than waiting for a batch file. They're the modern direction of travel and shine where immediacy matters: intraday positioning, instant payments, real-time status. Maturity and coverage still vary by bank, and like host-to-host, they're bank-by-bank, so breadth takes effort.

EBICS

EBICS (Electronic Banking Internet Communication Standard) is a bank-connectivity standard used mainly in parts of Europe (notably Germany, France and neighbours). Where your banks support it, it's a standardized way to exchange statements and payments. Its relevance is largely regional — essential in some European landscapes, not applicable elsewhere.

Comparison

How to choose

Work from your bank landscape and needs, not a preference for one technology:

• Many banks, many regions? SWIFT's single multi-bank connection avoids integrating each bank separately.
• A few strategic, high-volume banks? Host-to-host is efficient and robust for those relationships.
• Need real-time balances or payment status? APIs, where your banks support them.
• European banks that use EBICS? Use it where it applies.
• Reality: most treasuries combine channels — SWIFT or a bank portal for breadth, host-to-host for a few core banks, APIs where immediacy pays.

What usually goes wrong

• Underestimating onboarding. Every channel and bank is a setup with agreements, formats and testing; connectivity is almost always the critical path, not the software.
• One channel for every bank. Forcing all relationships through a single channel when a mix fits better — SWIFT for reach, H2H for the core few.
• Confusing channel and format. Agreeing "we'll use SWIFT" without settling the statement and payment formats (MT940, camt.053, pain.001) — you need both, per bank.
• No monitoring. A feed failing silently until a position is wrong or a payment is missed.

Pick channels per bank and need, agree the formats alongside them, start early, and monitor every link — and connectivity stops being the thing that holds go-live.

Part of the Treasury Systems Architecture guide. See also the reference architecture. The newsletter sends one finance-systems pattern, product decision or build lesson every two weeks.