Bank cashiers and the clearing team
Bringing XNETT live at PremiumTrust Bank
Problem
Cheques and electronic transfers had to clear through the national clearing house and post correctly into core banking, branch by branch.
How it works
- XNETT Pay moves transfers and collections in real time, with maker-checker approvals before anything leaves.
- A transfer starts in EFT. A cheque is scanned at the branch in CTS, and its image is stored with its data.
- XNETT exchanges it with the national clearing house.
- The cleared item posts into FLEXCUBE, and it has to match exactly: cheque number, customer name, amount. Then the customer gets an E-Alert.
What I did
- Took XNETT live 10+ times across the bank's 6 branches, and demoed every release to the bank's stakeholders and project managers before it went out.
- Listened to the cashiers, service managers and clearing team, and turned what they said into product: transaction limits compliance could control themselves, direct debit as a new clearing instrument for the bank, and a clearer interface for the clearing team.
- Built those changes in Flask (Python), Angular, TypeScript and Oracle SQL.
- Checked every transaction from XNETT into FLEXCUBE, down to the scanned cheque images in the database.
- When direct debits failed in production, traced it to malformed XML from empty database results, fixed it, and verified it before the next settlement window.
- Ran L2 support, resolving incidents in 10 to 60 minutes by severity. Once, that meant getting the head branch's cheque scanner back up.
- Customised the E-Alert messages PremiumTrust customers get after every transaction.
- Wrote the deployment, migration and rollback docs, so the consultants after me could set up servers and deploy without me.
Result
10+
go-lives, as the bank grew from 6 branches to 37.
A bank growing that fast needs clearing and payments that keep up. XNETT kept up. The platform was FASYL's. Making it work at the counter, and keeping it working, was mine.