Cross-border payments at sub-second settlement
Re-architected ledger and reduced settlement time by 92%.
- Custom Software
- DevOps & Cloud
- QA
- Go
- Postgres
- Kafka
- Kubernetes
- OpenTelemetry
February 12, 2026
The starting point
Northwind's monolithic ledger had become the company's largest reliability risk: a single Postgres primary handling cross-border payments for 14 corridors with 6-second p99 settlement.
Compliance requirements were tightening, and the team had no path to add a new corridor without a multi-week project per addition.
How we worked
We rebuilt the ledger as an event-sourced core in Go, with strict ACID boundaries and Kafka-backed reconciliation.
Migration ran shadow-mode for eight weeks: every payment was processed by both systems, with output diffs continuously evaluated before cutover.
Observability was built first — every state transition is traced end-to-end with OpenTelemetry, surfaced in a Datadog dashboard the on-call team helped design.
What changed
Settlement p99 dropped from 6.4s to 480ms in the first week post-cutover.
Adding a new corridor is now a config change with eight tests — not a project.
The ops team reports the platform as the most stable component in their stack, replacing a monthly incident cadence with zero pages over the last 90 days.
“Official Byte ran the entire rebuild of our payments backbone. Two quarters in, settlement is faster, costs are down, and our team finally trusts the platform.”
More from the same shelf
AI triage assistant deployed across 38 clinics
Cut intake time by 41% with HIPAA-compliant LLM workflows.
Real-time fleet visibility for 12,000 vehicles
Replaced legacy SAP layer with a modern event-driven core.
From design tool to platform — onboarding rebuilt in 8 weeks
Doubled activation rate without growing headcount.
Have a similar project?
We've shipped this kind of work before — let's talk about how the lessons apply to yours.
Posted 2026-02-12 by Official Byte. Read more on case studies.