CASE STUDIES
Outcome-led case studies for the open-source libraries and product programmes that show up in the article archive. Each entry leads with externally verifiable rigour signals — never adopter counts I can't back up.
CASE STUDY
Corporate treasury teams receive bank statements in CAMT, PAIN.001, MT940, OFX, CSV, and scanned PDFs from dozens of banks. Each format carries different field semantics, encodings, and ambiguities. Most teams hand-build…
CASE STUDY
As AI agents and MCP tools start calling edge APIs at scale, banks need a perimeter that survives autonomous traffic without trading away DORA-grade audit evidence. Existing CDNs offer either marketing language or opaque…
CASE STUDY
Corporate treasury teams demand programmable access to cash management, liquidity, and payments rails inside a Tier-1 bank — without giving up the regulatory evidence layer the bank itself has to produce. …
CASE STUDY
Banks face a November 14, 2026 SWIFT structured-address cutover and a longer NIST post-quantum migration window. Existing PQC implementations ship as policy papers, lab code, or proprietary HSM black boxes — none of whic…
CASE STUDY
The global MT → MX migration forces every bank and corporate treasury to produce structured pain.001 messages. Most teams hand-roll brittle XML or buy opaque proprietary translators. Both routes ship payment errors into …