API & Integration2024

FinConnect Payment Hub

Unifying M-Pesa, Stripe & Flutterwave into one reconciliation engine.

Start Your Project Back to Our Work

Client

FinConnect Africa

Industry

Fintech & Payments

Duration

12 weeks

Year

2024

The Challenge

What the client was up against

FinConnect Africa processed payments across M-Pesa, Stripe, and Flutterwave, but each gateway had separate dashboards, different data models, and no shared reconciliation layer. The finance team spent three full days each month manually matching transactions — an error-prone process that regularly surfaced discrepancies running into hundreds of thousands of shillings.

Disconnected processes

Manual data entry

No real-time visibility

Error-prone reconciliation

Our Solution

How we solved it

We designed a unified Payment Hub — a Node.js orchestration layer with a normalised transaction schema that ingests webhooks from all three gateways, applies idempotency guards, and writes to a single PostgreSQL ledger. A React reconciliation dashboard gives the finance team real-time status on every transaction, automated daily reconciliation reports, and an exception-handling queue for failed or disputed payments. All API credentials are stored in AWS Secrets Manager with automatic rotation.

Discovery & planning

Agile development sprints

Rigorous QA & testing

Smooth go-live & support

The Outcome

Results that matter

Monthly manual reconciliation time dropped from three days to under two hours.

3 days → 2 hrs

Monthly reconciliation time

99%

Reduction in discrepancy incidents

50K+

Transactions processed per month

< 200ms

End-to-end transaction latency

Monthly manual reconciliation time dropped from three days to under two hours. Transaction discrepancy incidents reduced by 99%, and the finance team now runs reconciliation reports themselves without engineering support. The system processes over 50,000 transactions per month at sub-200ms latency.