Banking Connectivity & E-Invoicing
SWIFT, EBICS T/TS, API DSP2, SFTP, ISO 20022, CFONB: I build and run international banking connectivity — country-specific payment formats, new payment rails (ACH, BACS, CHAPS, SEPA, MT101).
What I do
Connectivity protocols
- SWIFT
- EBICS T/TS
- API / PSD2
- SFTP (Host-to-Host)
Payment formats
- ISO 20022
- MTxxx
- CFONB
Local adaptation
Adapting payment files to each country’s specifics — formats, mandatory fields, local regulatory constraints.
New payment rails
Leading the rollout of new rails: ACH, BACS, CHAPS, SEPA, MT101.
Why my track record proves it
I launched the payments department of a treasury fintech, from scratch.
Building international banking connectivity isn’t something you learn from a book: it’s done by dealing directly with banks, one by one, country by country.
Hundreds of banks, across dozens of countries — that’s the volume of direct exchanges it took to build, test, and make reliable this department’s banking connections, from the first file format all the way to the payment rail in production.
Track record
Launching the payments department of a treasury fintech.
Context
The fintech was born 100% European (France and Germany), with no international banking connectivity. The first clients expanding internationally paid through “centralizing banks”: a detour through a French bank, relayed via SWIFT. It worked, but it was expensive and slow to set up.
The trigger
Clients with subsidiaries in the United States were paying $10 to $15 per domestic wire, while an ACH transfer costs $0.50. That triggered the build-out of country-specific formats, SWIFT, and Host-to-Host connections (direct SFTP with the bank).
The real obstacle
The first US launch failed: connectivity was too costly against the US market. A no-go decision, followed by a year of rebuilding rather than patching things up. The direct ACH rail was then rebuilt, and the model replicated country by country.
E-invoicing
E-invoicing runs on the same logic as banking connectivity: standardized formats and cross-system exchanges (ISO 20022, CFONB on one side; Factur-X and the flows through dematerialization platforms like Chorus Pro / PDP on the other). It’s a natural extension of my expertise in structured banking flows — not yet a quantified track record as of today.