Platform & infrastructure · Security & compliance · Delivery engineering · Systems integration

A savings and credit platform, pre-launch

At Zyntrix Technologies Limited, for Anchor Cooperative

Pre-launch · architectural guarantees, not production outcomes

Focus: Platform & infrastructure · Security & compliance · Delivery engineering · Systems integration
Evidence: 4 documented guarantees
Decision record: Firsthand trade-off included

The brief

What was built

Infrastructure, delivery pipeline, security posture and observability for a member-owned cooperative — a modular FastAPI monolith over PostgreSQL, packaged to move to EKS without a rewrite. Unrelated to the fintech of a similar name.

Evidence

Architectural guarantees

Transaction, ledger entries and the outbox event commit in one database transaction — a recorded payment cannot outlive a failed ledger write, and no event is lost when the queue is down
Idempotency keys enforced by a uniqueness constraint on every endpoint that can create a financial transaction, covering client double-taps, mobile network retries and load-balancer retries
Four independent pipelines — web, mobile, API, infrastructure — each gated on SAST, dependency, secret and container scanning before staging, with production behind an explicit approval
Collection and disbursement run on the rails members already use — Paystack direct-debit mandates, a per-member virtual NUBAN through Moniepoint and OPay, loan disbursement to the member's bank account by API — and every settlement reconciles against the ledger entry it belongs to rather than by hand

Decision record

It manages money without being allowed to hold any

The surprising constraint was that the platform could not behave like a bank simply because it manages financial workflows. Member funds remain with approved banks and licensed payment providers; the platform records operations, accounting, approvals and evidence without claiming a banking or payment licence. That boundary changed the architecture. Consequential actions need immutable audit records. Financial writes and outbox events commit together. NDPA obligations — lawful basis, retention, data-subject rights, processor records, a DPIA — are part of the platform design rather than a policy bolted on. Staging is production-shaped and contains no real member data.

Return to all work