[{"data":1,"prerenderedAt":412},["ShallowReactive",2],{"blog-\u002Fblog\u002Ftreasury-bank-connectivity-swift-host-to-host-api-ebics":3,"blog-surround-\u002Fblog\u002Ftreasury-bank-connectivity-swift-host-to-host-api-ebics":391,"blog-related-\u002Fblog\u002Ftreasury-bank-connectivity-swift-host-to-host-api-ebics":400},{"id":4,"title":5,"audience":6,"body":9,"cluster":357,"date":358,"description":359,"draft":360,"extension":361,"factCheckedAt":362,"faq":363,"featured":360,"language":362,"meta":373,"navigation":374,"order":347,"originalAsset":362,"path":375,"pillar":376,"primaryKeyword":377,"relatedProject":362,"releaseScope":362,"reviewCycle":378,"reviewStatus":379,"reviewedBy":380,"searchIntent":381,"seo":382,"sources":362,"stem":383,"tags":384,"type":389,"updated":358,"__hash__":390},"blog\u002Fblog\u002Ftreasury-bank-connectivity-swift-host-to-host-api-ebics.md","Treasury Bank Connectivity: SWIFT vs Host-to-Host vs API vs EBICS",[7,8],"treasury-system-lead","solution-architect",{"type":10,"value":11,"toc":345},"minimark",[12,35,40,51,55,62,66,81,85,105,109,116,120,239,243,246,284,288,319,322,325],[13,14,15,19,20,25,26,30,31,34],"p",{},[16,17,18],"strong",{},"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 ",[21,22,24],"a",{"href":23},"\u002Fblog\u002Febics-european-bank-connectivity","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 ",[27,28,29],"em",{},"channel"," (how the message travels) with the ",[27,32,33],{},"format"," (what it says).",[36,37,39],"h2",{"id":38},"what-bank-connectivity-does","What bank connectivity does",[13,41,42,43,46,47,50],{},"Whatever the channel, connectivity does two jobs: bring ",[16,44,45],{},"bank statements in"," (so you can build the cash position and reconcile) and send ",[16,48,49],{},"payment instructions out"," (and get their status back). Everything below is a different way to move those two flows.",[36,52,54],{"id":53},"swift","SWIFT",[13,56,57,58,61],{},"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 ",[16,59,60],{},"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.",[36,63,65],{"id":64},"host-to-host-h2h","Host-to-host (H2H)",[13,67,68,69,72,73,76,77,80],{},"Host-to-host is a ",[16,70,71],{},"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 ",[16,74,75],{},"strategic, high-volume"," relationships: once set up, statements and payment files flow automatically. The catch is that it's ",[16,78,79],{},"per bank"," — every host-to-host link is its own setup, so it scales poorly across many banks.",[36,82,84],{"id":83},"api","API",[13,86,87,88,91,92,95,96,100,101,104],{},"Bank APIs bring ",[16,89,90],{},"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 ",[16,93,94],{},"immediacy"," matters: ",[21,97,99],{"href":98},"\u002Fblog\u002Freal-time-treasury","intraday positioning",", instant payments, real-time status. Maturity and coverage still vary by bank, and like host-to-host, they're ",[16,102,103],{},"bank-by-bank",", so breadth takes effort.",[36,106,108],{"id":107},"ebics","EBICS",[13,110,111,112,115],{},"EBICS (Electronic Banking Internet Communication Standard) is a ",[16,113,114],{},"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.",[36,117,119],{"id":118},"comparison","Comparison",[121,122,123,141],"table",{},[124,125,126],"thead",{},[127,128,129,132,134,137,139],"tr",{},[130,131],"th",{},[130,133,54],{},[130,135,136],{},"Host-to-host",[130,138,84],{},[130,140,108],{},[142,143,144,164,183,201,220],"tbody",{},[127,145,146,152,155,158,161],{},[147,148,149],"td",{},[16,150,151],{},"Reach",[147,153,154],{},"Many banks, one connection",[147,156,157],{},"One bank per link",[147,159,160],{},"One bank per API",[147,162,163],{},"Banks supporting EBICS",[127,165,166,171,174,177,180],{},[147,167,168],{},[16,169,170],{},"Mode",[147,172,173],{},"Messaging \u002F files",[147,175,176],{},"File exchange",[147,178,179],{},"Real-time request-response",[147,181,182],{},"Files \u002F messaging",[127,184,185,190,193,196,199],{},[147,186,187],{},[16,188,189],{},"Real-time",[147,191,192],{},"Generally batch",[147,194,195],{},"Batch",[147,197,198],{},"Yes",[147,200,192],{},[127,202,203,208,211,214,217],{},[147,204,205],{},[16,206,207],{},"Best for",[147,209,210],{},"Multi-bank, multi-region",[147,212,213],{},"Few high-volume banks",[147,215,216],{},"Immediacy: intraday, instant",[147,218,219],{},"European landscapes",[127,221,222,227,230,233,236],{},[147,223,224],{},[16,225,226],{},"Effort \u002F cost",[147,228,229],{},"Higher setup; scales across banks",[147,231,232],{},"Per-bank setup",[147,234,235],{},"Per-bank; maturity varies",[147,237,238],{},"Regional standard",[36,240,242],{"id":241},"how-to-choose","How to choose",[13,244,245],{},"Work from your bank landscape and needs, not a preference for one technology:",[247,248,249,256,262,268,274],"ul",{},[250,251,252,255],"li",{},[16,253,254],{},"Many banks, many regions?"," SWIFT's single multi-bank connection avoids integrating each bank separately.",[250,257,258,261],{},[16,259,260],{},"A few strategic, high-volume banks?"," Host-to-host is efficient and robust for those relationships.",[250,263,264,267],{},[16,265,266],{},"Need real-time balances or payment status?"," APIs, where your banks support them.",[250,269,270,273],{},[16,271,272],{},"European banks that use EBICS?"," Use it where it applies.",[250,275,276,279,280,283],{},[16,277,278],{},"Reality:"," most treasuries ",[16,281,282],{},"combine"," channels — SWIFT or a bank portal for breadth, host-to-host for a few core banks, APIs where immediacy pays.",[36,285,287],{"id":286},"what-usually-goes-wrong","What usually goes wrong",[247,289,290,301,307,313],{},[250,291,292,295,296,300],{},[16,293,294],{},"Underestimating onboarding."," Every channel and bank is a setup with agreements, formats and testing; connectivity is ",[21,297,299],{"href":298},"\u002Fblog\u002Fwhy-tms-implementations-fail","almost always the critical path",", not the software.",[250,302,303,306],{},[16,304,305],{},"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.",[250,308,309,312],{},[16,310,311],{},"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.",[250,314,315,318],{},[16,316,317],{},"No monitoring."," A feed failing silently until a position is wrong or a payment is missed.",[13,320,321],{},"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.",[323,324],"hr",{},[13,326,327],{},[27,328,329,330,334,335,339,340,344],{},"Part of the ",[21,331,333],{"href":332},"\u002Ftopics\u002Ftreasury-systems-architecture","Treasury Systems Architecture guide",". See also the ",[21,336,338],{"href":337},"\u002Fblog\u002Freference-architecture-for-corporate-treasury","reference architecture",". The ",[21,341,343],{"href":342},"\u002Fnewsletter","newsletter"," sends one finance-systems pattern, product decision or build lesson every two weeks.",{"title":346,"searchDepth":347,"depth":347,"links":348},"",2,[349,350,351,352,353,354,355,356],{"id":38,"depth":347,"text":39},{"id":53,"depth":347,"text":54},{"id":64,"depth":347,"text":65},{"id":83,"depth":347,"text":84},{"id":107,"depth":347,"text":108},{"id":118,"depth":347,"text":119},{"id":241,"depth":347,"text":242},{"id":286,"depth":347,"text":287},"connectivity","2026-07-23","SWIFT, host-to-host, API and EBICS — how corporate treasury connects to banks, compared on reach, cost, real-time capability and setup effort.",false,"md",null,[364,367,370],{"question":365,"answer":366},"What is the difference between SWIFT, host-to-host and API bank connectivity?","SWIFT is a shared network that reaches many banks through one standardized connection — good for multi-bank reach, higher in cost and complexity. Host-to-host is a direct, secure file exchange between your systems and one specific bank — efficient for a few high-volume relationships. API connectivity is real-time and modern, bank-by-bank, best where you need instant balances or payment status. EBICS is a standard used mainly in parts of Europe. Most corporates use a mix, chosen by bank and need.",{"question":368,"answer":369},"Which bank connectivity method is best for corporate treasury?","It depends on your bank landscape. If you deal with many banks across regions, SWIFT's single multi-bank connection is attractive. If you have a few strategic banks with high volumes, host-to-host is efficient. Where real-time balances or instant payment status matter, APIs are the direction of travel. In Europe, EBICS is common. There is no single best answer — most treasuries combine channels.",{"question":371,"answer":372},"Is connectivity the same as file format?","No, and confusing them causes trouble. Connectivity is the channel — how the message travels (SWIFT, host-to-host, API, EBICS). The format is the content — what the message says (MT940 or camt.053 for statements, pain.001 for payments). You choose a channel and a format per bank, and both have to be agreed and tested.",{},true,"\u002Fblog\u002Ftreasury-bank-connectivity-swift-host-to-host-api-ebics","treasury-systems-architecture","SWIFT vs host to host vs API","annual","reviewed","Tan Gravam","informational",{"title":5,"description":359},"blog\u002Ftreasury-bank-connectivity-swift-host-to-host-api-ebics",[385,386,387,388],"treasury","architecture","bank-connectivity","integration","text","oAFIJ-0EilnPTH5-fr5uObSIzDvpXswvSheucbkNYSk",[392,396],{"title":393,"path":394,"stem":395,"type":389,"language":362,"draft":360,"children":-1},"Trapped Cash and Cash Repatriation","\u002Fblog\u002Ftrapped-cash-and-cash-repatriation","blog\u002Ftrapped-cash-and-cash-repatriation",{"title":397,"path":398,"stem":399,"type":389,"language":362,"draft":360,"children":-1},"The Treasury Data Model","\u002Fblog\u002Ftreasury-data-model","blog\u002Ftreasury-data-model",[401,404,408],{"path":23,"title":402,"description":403},"EBICS Explained: European Bank Connectivity","What EBICS is — an internet-based European standard for exchanging payment and statement files with banks — and where it fits alongside SWIFT and host-to-host.",{"path":405,"title":406,"description":407},"\u002Fblog\u002Fbank-statement-formats-mt940-camt053-bai2","Bank Statement Formats: MT940 vs camt.053 vs BAI2","MT940, camt.053 and BAI2 are the main bank statement formats treasury imports: legacy SWIFT, modern ISO 20022, a US format. How they differ and which to use.",{"path":409,"title":410,"description":411},"\u002Fblog\u002Fiso-20022-payments-pain-001-pain-002","ISO 20022 Payments Explained: pain.001, pain.002 and the camt Family","ISO 20022 is the global XML standard for financial messaging. For payments, pain.001 is the instruction you send and pain.002 the status back. What they are.",1785182343099]