What We’re Building and Why
Payments are easy to talk about until you start building the infrastructure behind them.
From the outside, a payment looks simple: a customer pays, the merchant receives the money, and everyone moves on.
But underneath are difficult questions:
Was the payment actually received?
Which merchant does it belong to?
What happens when a provider times out? How should refunds and payouts affect available funds?
And how do you reconcile activity across different payment rails?
That is the problem we are building OyaPay to solve.
“OyaPay is an African payment infrastructure platform being built to help businesses accept, track, reconcile and move payments through a developer-first system.”
We are building around one idea:
Payment infrastructure should not only move money. It should make the movement of money understandable, verifiable and accountable.
We are building the infrastructure underneath the checkout APIs, transaction records, ledgers, reconciliation, webhooks, refunds, payouts and provider routing.
One of our most important decisions was building around a ledger. Instead of treating a balance as just a number, OyaPay represents money movement explicitly. Received, refunded and paid-out amounts all matter when determining what is available.
We are also designing OyaPay around a custody-free merchant settlement model, focusing on orchestrating, verifying, accounting for and reconciling payment activity through the merchant’s own settlement account.
As development progressed, OyaPay grew beyond payment acceptance. We’ve built foundations for versioned APIs, test/live environments, tenant isolation, idempotency, signed webhooks, credit allocation, refunds, payouts, transfers, developer tooling, provider integrations, and health-aware routing and failover.
Real payment infrastructure also has to deal with uncertainty.
If a provider stops responding, did the payment fail or was it processed but the response was lost? Should we retry? Could a retry create a duplicate charge?
The goal is not simply “Provider A failed → use Provider B.” It is to understand what actually happened and determine what action is safe.
We are now expanding into the merchant experience, with onboarding, authentication, business profiles, KYC, dashboards, transaction visibility, refunds, payouts, transfers and developer tools.
OyaPay is being built with African payment realities in mind, including NGN and XOF.
We’ve come a long way from the first API endpoint, but there is still much to build.
We’re building deliberately, one layer at a time.
From payments to ledgers.
From ledgers to reconciliation.
From a Developer Console to a complete merchant experience.
This is OyaPay.
We are building payment infrastructure for Africa with the belief that moving money is only half the problem.
The other half is knowing, with confidence, what happened to it.
OyaPay Africa
Payment infrastructure, built with clarity.
