Case study · Financial services
Connecting to Zambia's National Financial Switch — and making every transaction visible.
- SECTOR
- Financial services
- YEAR
- 2025 – 2026
- SERVICES
- Integration · Backend · Ops console
- STACK
- Elixir · OTP · PostgreSQL


The challenge
Money in motion, with no clear view of where it is.
Connecting to national payment infrastructure means handling inbound and outbound messages, retries and callbacks reliably — and giving operations teams a way to see, at any moment, what is pending, what failed and why.
Our approach
A resilient switch engine, and a console built for operators.
We built the integration on Elixir and OTP for fault-tolerant, high-concurrency message handling, then wrapped it in a live console: link state, queues, callbacks, wallet and settlement, reports and a full audit trail.
How it fits together
Architecture at a glance
01 · CLIENT SIDE
Core banking & wallets
Initiate outbound payments and receive inbound credits.
02 · ELEVARE NFS ENGINE
Switch engine on Elixir / OTP
03 · NATIONAL
National Financial Switch
Link with live heartbeat; traffic in both directions.
What operators get
One live view of the whole switch.
Link health
Connection state and heartbeat to the national switch, with volume and in-flight counts.
Transaction states
Pending, failed and completed — split inbound and outbound, with ZMW totals.
Callback backlog
Pending and failed deliveries surfaced before they become customer complaints.
Traffic analytics
Hourly traffic for the last 24 hours and monthly for the last 12, by direction.
Settlement net
Inbound minus outbound per cycle, across recent settlement cycles.
Security & audit
Role-based access, message logs and an audit trail for every operator action.
More of our work
Vehicle inspection, lending, logistics and more
Let's talk about the system you need.
Tell us what needs to work better. A senior engineer — not a salesperson — will take it from there.