Engineering Journal
Nigerian Fintech Isn't Ready for Customers That Are Machines
Two shifts are arriving at once. Software is being bought and operated by autonomous AI agents, and the products they buy are increasingly SaaS - billed by the month, the seat, or the request. Both assume a payment system that a machine can drive, programmatically, at any hour, in small amounts, with a verifiable receipt. Much of Nigerian fintech is still built for a human tapping a card and reading an OTP. That gap is about to matter a great deal.
An agent cannot read your OTP
Nigerian payments leapfrogged the world once already - cards, USSD, transfers, and slick checkout flows that work brilliantly for a person with a phone in hand. But look closely at how they work: a redirect to a bank page, a one-time code sent by SMS, a tap to approve, a human eye confirming an amount. Now hand that flow to an autonomous agent buying a subscription on its owner's behalf. It cannot read the SMS. It cannot click the bank's redirect. It cannot pass a human-shaped fraud check designed to prove a person is present. The entire happy path assumes exactly the one thing that is no longer there.
The agent does not get frustrated and try again. It fails silently and picks a provider it can actually pay.
What is HTTP 402, and why does it suddenly matter?
There is a status code that has sat reserved and mostly unused for the entire life of the web: 402 Payment Required. It was always meant for the day machines would need to pay each other inline. That day is arriving. A service can answer a request with 402, state the price and how to settle it, and an agent can pay programmatically and retry - no redirect, no OTP, no human in the loop. New protocols are wiring stablecoins and instant rails behind exactly this pattern, so an agent can settle a few naira for a single API call as easily as a person pays for lunch.
This is not a crypto sideshow. It is the missing checkout for the agent economy: small amounts, machine-negotiated, instantly settled, with a receipt both sides can verify. Whoever offers African businesses a clean 402-style rail becomes the default way agents pay across the continent. Whoever does not becomes a wall agents route around.
The SaaS boom already exposed the same weakness
You do not even need agents to see the gap - the SaaS wave is already testing it. Subscription software runs on recurring billing, metered usage, per-seat plans, proration, dunning, retries, and instant developer-first payouts. That is a very different job from capturing one card payment once. Too many local processors are still excellent at the single human transaction and thin on the programmatic machinery a SaaS business lives on: reliable card mandates, usage-based charging, idempotent retries, clean webhooks, and APIs a developer can actually build a billing system against without fighting the platform.
So Nigerian SaaS founders quietly reach for foreign processors to bill properly, and the local ecosystem loses the most valuable, most recurring revenue in software to providers abroad. The agent shift will widen that same crack, not open a new one.
What does an agent-ready, SaaS-ready rail actually need?
The requirements are not exotic. Programmatic authorisation with scoped keys and mandates instead of a human OTP. A machine-negotiable payment step - the 402 pattern - so software can pay software without a screen. Micropayments and metering, because agents transact in small, frequent amounts. Instant, final settlement rather than a T+1 promise. Idempotency, so a retry never double-charges. Verifiable receipts, so both parties and any auditor can prove what happened. And delegation: a way for an agent to pay as a verified principal, with limits, so a mistake is bounded and a fraud is catchable.
Every one of those is buildable today. Most of them are simply not prioritised, because the current business is a human at a checkout, and that business still looks healthy - right up until the buyers stop being human.
We run into this wall on purpose
This is not theory from the outside. On SortAm we protect payments and hold funds in escrow with explicit release conditions, and the hard parts are always programmatic: reconciliation, idempotent movement, verifiable wallet history. In the Partner Hub we treat every earning as a ledger entry that can explain itself. And with Africa Connect, our Model Context Protocol gateway, we are deliberately building the surface where AI agents discover and transact with verified African businesses - which means we meet the payments gap head-on, every time an agent is ready to pay and the rail underneath was only ever designed for a person.
The takeaway
Nigerian fintech has done the hard thing before: it built modern payments for a market the rest of the world underestimated. The next version of that work is not prettier checkout. It is rails a machine can drive - 402-native, subscription-native, settled instantly, provable end to end - so that when discovery and purchase are run by agents, African businesses are reachable instead of skipped.
At Mpaukwu, we build products for that future now, and we would rather our payment partners meet us there than watch the agent economy quietly route around the continent.
Mpaukwu Trading builds founder-led SaaS products, automation systems, and production-ready platforms for African businesses, including SortAm, MediSeen HMS, and StoreBase. Read more from the Engineering Journal or start a project.