Automated SWIFT gpi Universal Confirmation platform (MTUC)
Challenge
The branch's SWIFT gpi Universal Confirmation flow ran on an undocumented Fiorano ESB integration that had failed, leaving MT103 payments without the MT199 confirmations the gpi rulebook requires and no reliable record of what had already been sent.
Approach
Reverse-engineered the flow from Oracle and message-archive evidence, recovering and analysing 7,932 historical confirmations to derive production rules rather than assumptions. Replaced a legacy query that expanded to roughly 243 million rows (about 31,109x amplification) with auditable deduplicated selection and explicit ambiguity handling, so unresolved identities fail closed. Built an autonomous Python/Oracle service with byte-exact MT199/FIN serialisation, UETR handling, acknowledgement reconciliation, no-resend-without-evidence controls and evidence-gated database writes, staged a 1,713-transaction backfill and productionised the runtime as hardened Windows services.
Technology & domain
- Python 3.12
- Oracle / python-oracledb
- SWIFT gpi · MT199 / MT103 · UETR
- Finastra SWIFT interface
- Windows Services / pywin32
- DPAPI
- SQLite WAL
- Idempotent state machine
Outcome
Approximately 2,000 live confirmations delivered with zero SWIFT-interface rejections. Post-go-live reliability engineering across eight production incidents added bounded database timeouts, progress-based watchdogs, snapshot-scoped Oracle reads and recovery tooling, backed by 12 automated regression suites and 45 design and forensics documents.