GB Agboola on Flutterwave and Africa's Payment Superhighway

Why Flutterwave was built as infrastructure, not a feature

Agboola frames Flutterwave's origin as a response to a structural problem rather than a product gap. Every African country, he argues, has its own rails, rules and ecosystems, but they are closed, leaving a continent that is "not offline" but "disconnected from itself". His insight was that Africa does not need one currency to trade like one market; it needs infrastructure that connects everything together.

That reframing set the ambition. Rather than build another incremental fix, Flutterwave set out to unify payment acceptance, settlement and connectivity so that African businesses could reach the continent's roughly one billion people and "suddenly start to perform like they are global". Cracking payments, Agboola argues, unlocks trade, commerce, logistics, remittances and capital flows in one move, a multiplier effect that lifts entire ecosystems. The hardest problems, in his words, "create the deepest moots, if you get it right".

Why Nigeria was the deliberate starting point

Flutterwave started in Nigeria, and Agboola is clear it was a choice rather than an accident of geography. Small problems, he says, do not move continents, and Nigeria is both "the toughest market" and "the best teacher". Building a payments company there forced the young firm to contend with diverse payment behaviour, multiple rails, regulatory intensity and, in his phrase, unrelenting customer demand for reliability.

The strategic logic was that resilience learned in Nigeria would travel. Surviving Nigerian scale and complexity, Agboola argues, prepared Flutterwave for Ghana, South Africa, Egypt, Rwanda and eventually the UK and US. He also points to Nigeria's high GDP and adoption rates, and to a simpler founder calculation: it was the one market where he had an unfair advantage. His advice to other founders follows directly from this: go where you can get the best mileage and the most unfair advantage, because that is what carries a startup through the hardest problems.

How local support and Y Combinator opened the funding door

Agboola credits Flutterwave's early survival to a stack of support that was both homegrown and global. A young 2016 company with no capital raised could still apply for and win a licence, he says, because Nigeria's regulatory environment was professional and world-class, and that licence became a passport: everywhere else Flutterwave went, the first question was whether its own country had licensed it.

Bank backing mattered as much as regulation. Agboola, who had previously worked in banking, names Access Bank and its late former chief executive Herbert Wigwe, alongside Standard Bank and Sterling Bank, among institutions that "came to the table" with rails and support as Flutterwave scaled. On the investor side, he credits Y Combinator as the "major factor" in accessing US and international capital, placing Flutterwave inside a community of global founders, with early backing from firms including CRE Ventures. His broader argument is pointed: Africa needs to back Africa first, because local investors understand a complexity that non-African VCs, for whom these payment problems simply do not exist, struggle to price.

Supported by

Silicon Overdrive Founders Series

Visit Silicon Overdrive↗

Where Flutterwave is heading: enterprise, SMBs and consumers

Flutterwave's roadmap is built around three customer segments, and Agboola describes each in turn. For enterprises, the company has built what he calls the biggest named virtual account infrastructure in Africa, helping global companies get paid locally through account-based rather than card payments. In a single quarter, he says, Flutterwave processed one billion dollars for one segment of global companies with customers in Nigeria, Ghana and South Africa, a number he notes has since grown. The stated goal is to go "deeper, not even wider".

For small and medium businesses, the pitch is market access. Agboola describes an SMB in Cairo who could not easily sell to a customer in Lagos, with payment as the barrier, and positions Flutterwave as removing that friction so currency conversion and settlement happen seamlessly. For consumers, the focus is diaspora remittances and, increasingly, blockchain payments; Flutterwave has partnered with Polygon and is building stablecoin infrastructure, with a pilot for a few select customers planned before the end of the year.

Why stablecoins are treated as payment, not speculation

Agboola positions stablecoins firmly as a payment form factor rather than a regulatory shortcut. Cross-border settlement is shifting, he says, with global suppliers telling clients they will ship faster if paid in stablecoin: settlement can be near-instant, against roughly five days for SWIFT and two to three days for wires, because the money no longer has to route through New York on its way between African cities.

Crucially, he insists stablecoins do not mean the absence of rules. Flutterwave, which he describes as "the most licensed non-bank entity in Africa", treats stablecoin as just another payment type alongside cards, to be processed within the confines of relevant regulation. The customer benefit he stresses is simplicity: businesses on Flutterwave do not need to find a separate stablecoin vendor to convert fiat, because that conversion happens on the platform, where permitted. In his framing, stablecoin does not sidestep regulation so much as enforce it.

[CHAPTERS]

What is PAPS, and why is Flutterwave betting on it?

PAPS is the Pan-African Payment and Settlement System, an Afreximbank platform that Agboola calls "literally the future" of cutting cross-border cost and speed. It works by getting central banks to sign bilateral agreements country by country, so money can move directly from, say, Lagos to Accra rather than routing through New York. The Nigeria to Ghana link is already live, he says, with companies transacting on it, and Flutterwave is currently integrating PAPS, expecting customers to see faster and cheaper transfers from the first quarter of next year. The deeper prize, he argues, is that by keeping money on the continent and making flows transparent, PAPS could give regulators confidence to relax exchange controls that were built to stop money leaving.

Is enough being done to unify African payments?

Not yet at full scale, but the right approach is to start small, in Agboola's view. He agrees with Colin Iles that a continent-wide solution ultimately needs collaboration across governments, central banks, regulators and the global schemes, but argues that a problem this hard has to be solved incrementally. PAPS, he says, is doing exactly that: proving the model on Nigeria and Ghana first, then adding countries step by step, on the expectation that visible progress between a few live corridors will accelerate everyone else.

What is the hardest part of scaling a startup into infrastructure?

The hardest shift, Agboola says, is personal: moving from "the person who does everything to the person who enables people who do everything". In the early days he wrote product specs, sold, and dealt with banks himself; scaling meant surrendering control while keeping accountability, and moving from speed to structure. He now describes himself as "chief enabler" rather than chief doer, and lists his real learnings plainly: invest in talent earlier, hire fast and fire fast on culture fit, over-communicate the mission relentlessly, treat the regulator as a stakeholder rather than an adversary, and build multiple independent sources of truth so that, as he puts it, reality is forced to meet you every day.