The Challenge
The operator cleared payments across three jurisdictions using a single banking rail and a spreadsheet for reconciliation. Settlement took two to four days, FX was applied inconsistently, and roughly one in twenty transactions broke reconciliation — each break taking an analyst hours to resolve. A single provider outage could halt settlement entirely.
The Solution
We rebuilt settlement on the Baalvion Operating System with automated multi-rail routing, server-computed FX, and a double-entry ledger that records every movement as a balanced transaction. Every payment carries an idempotency key, so a retried request can never double-settle. A transactional outbox guarantees that once a settlement is committed, it is delivered to the rail exactly once.
- Multi-rail routing with automatic failover between providers.
- Idempotent settlement so retries are always safe.
- Server-side FX applied at the ledger boundary for consistent valuation.
- Double-entry ledger as the single financial source of truth.
Architecture
The settlement service writes the intent and the outbox entry in one database transaction. A relay then publishes to the chosen rail, retrying on failure and failing over to an alternate provider if needed. The ledger consumes settlement events and posts balanced entries, with FX conversion applied at the moment of posting. This pattern is detailed in trade finance automation and building multi-tenant SaaS.
Technology Stack
A transactional outbox for guaranteed delivery, idempotency keys for safety, an FX engine for conversion, a double-entry ledger for integrity, and adapters for multiple payment rails. The capability is part of our automation and cloud solutions practice.
Results
Average settlement latency fell by 40%, reconciliation breaks dropped by 95%, and a provider outage no longer stops the business — traffic fails over automatically. Finance closed its books in hours instead of days.
Lessons Learned
Idempotency and the outbox pattern are the foundation of trustworthy money movement. Applying FX at the ledger boundary eliminated an entire class of valuation disputes. And multi-rail failover turned a fragile single point of failure into a resilient, self-healing path.