Building for Constant Change: Africa’s Next FinTech Chapter
In this episode, “Building for Constant Change: Africa’s Next FinTech Chapter”, of Talking Success, The Best Fintech Podcast, Darren Franks sat down with Kevin Odudoh from Vodacom Business and Tapfuma Mvere from XLink to dig into a reality every African FinTech leader knows well: you have to build for a moving target without breaking customer experience.
What follows isn’t a recap. It is a playbook. It distills how compliance-by-design, sovereign AI clouds, and an API-first orchestration layer can help product teams keep shipping, even as rules and rails keep shifting. It also sets up the runway to Pretoria for the South African FinTech Awards and the African FinTech Festival, where these ideas meet the operators building the continent’s next decade of growth.
Compliance is not a blocker. It is the blueprint.
Taps’ first principle is simple: treat compliance as a design constraint from day one. If regulation will change, product and architecture should expect it and absorb it without forcing customers to relearn the journey.
That mindset changes the build order:
- Start with policy models. Capture the rules that govern a transaction type or corridor and express them as modular policy objects. When the rule changes, you update the object, not the entire flow.
- Make the UI do the explaining. If a cross-border payment requires extra fields due to exchange control, surface them contextually with short, plain-language guidance. Don’t outsource understanding to a PDF. Put it in the journey.
- Instrument the edges. Log decisions and data at each control point so audit trails aren’t a forensic project later. Good logging is insurance against rework and regulatory surprises.
The outcome is counterintuitive but important. When product and engineering teams adopt compliance-by-design, regulatory shifts become a chance to improve experience rather than a reason to pause releases.
Design for volatility: product architecture that bends without breaking
If your payment flows cross borders, volatility is the rule. New payment methods arrive. Local rails evolve. Corridor rules change. The architecture needs to flex at three layers.
Policy and workflow. Build configurable workflows that reference policy objects. When a threshold, KYC step, or proof requirement changes, you reconfigure rather than refactor.
Integration. Sit behind a switching layer that abstracts partners, acquirers, schemes and wallets. New method in the market? You add a connector and map it to a common transaction model, not a bespoke journey.
Data and observability. Centralise events and telemetry. When a regulator asks how you enforce rule X in corridor Y, you should answer with evidence in minutes, not a sprint.
As Taps put it, “These are enablers, not inhibitors.” Done well, they shorten your delivery cycle and keep customers shielded from back-end churn.
Multi-cloud, sovereign AI and why location still matters
Kevin’s perspective adds the scale piece. Many teams want the agility of hyperscale with the control of local hosting. The answer is multi-cloud with a sovereign option. In practice, this looks like:
Right-location compute. Run sensitive workloads in-country to meet data residency requirements, while using hyperscale services for burst capacity or specialised tooling.
Sovereign AI cloud. Keep model training and data within the market where the business operates. You retain control over data governance, lineage and access, while still unlocking AI for risk, fraud and service.
Weeks, not months, to stand-up. The value is as much operational as it is technical. If a FinTech can get a compliant environment live in weeks, experiments move from slideware to production.
Kevin referenced a recent throughput jump from thousands to tens of thousands of transactions per second after an upgrade. The headline isn’t the number. It is the repeatability. When the platform pattern is repeatable, performance is a knob you can turn without rewriting the engine.
For product teams, this matters. You get an environment where data sovereignty isn’t in conflict with scale, and where AI capabilities can be adopted responsibly rather than bolted on later.
One size doesn’t fit anyone: how to serve startups and scale giants at once
African payments ecosystems are barbell-shaped. On one end, early-stage FinTechs are testing propositions with limited volume. On the other, established players push traffic at national scale. Kevin’s point is that the same provider can serve both, if the operating model is software-defined.
- Segment of one, for enterprises. Telcos learned to personalise at consumer scale. The enterprise analogue is policy-driven configuration, automation and analytics that tailor services to each client’s footprint.
- Try-and-buy for the cloud. If you want smaller teams to access advanced AI features, make it an operating expense with clear usage limits. Let them prototype and pay only for what they use.
- Elasticity by default. When a client moves from pilot to production or from local to cross-border, the platform scales before the commercial does. That is how you keep cost-to-serve sustainable.
The common thread is automation. Without it, you either over-engineer for startups or under-serve the giants. With it, you can meet both where they are today and where they’ll be in six months.
Orchestration is where the value exchange actually happens
Walk into any major retailer in South Africa and you will see twenty plus ways to pay. Add loyalty, QR, closed-loop wallets, SRC, pay-by-bank, BNPL, card present and card not present. Now add new rails such as PayShap locally or mobile-money rails across the region. This is where XLink’s philosophy is pragmatic and customer-first.
Offer breadth, decide intelligently. The goal is to present the best option for a given merchant and consumer pairing. That requires an orchestration layer that understands context and can route accordingly.
API-first, but not API-only. Some clients want a full white-label front end. Others want to embed just the capability. The platform needs to support both and still guarantee settlement, visibility and compliance behind the scenes.
Switching as a product. Merchants don’t want to care how many hops a transaction takes. They want reliability, speed, cost predictability and dispute clarity. The switching layer should hide the chaos and expose the control.
In practical terms, this reduces the integration burden for banks and FinTechs. You integrate once to the orchestrator, then opt into methods and corridors as your strategy evolves.
Trust, again. Because it never stops mattering.
Trust is the unfair advantage. A known brand, proven uptime, and visible compliance posture remove friction from adoption. It is easier to convince a CFO, a CIO or a risk committee to back a product when the partners behind it are familiar and have been tested at scale.
This is where Vodacom Business Services and XLink align well. One brings the network, the cloud and the governance muscle. The other brings the switching layer, the merchant empathy and the developer ergonomics. Together, they allow clients to focus on what differentiates them instead of the plumbing that should be invisible.
Focus beats scope: advice for founders and product leaders
Toward the end of the conversation, a story lands a useful lesson. An ambitious founder wants to build a bank that does everything on day one. Deposits, savings, investments, crypto, microfinance and point of sale. The reality is stark. Licensing is expensive and slow. Compliance is heavy. Product sprawl dilutes execution.
The alternative is better. Focus on the core job your customer needs from you first. Partner for the rest. Use the ecosystem to assemble capabilities that are not your differentiator. Get to market with a sharp value proposition and a reliable backend. Then expand. That is how you compound trust and avoid shipping half-finished features that create operational debt.
Questions every CIO should ask before signing anything
Taps offered a practical checklist that leaders can take to their next vendor call. Ask yourself:
- What keeps my team busy that isn’t core to our value proposition? If connectivity, power continuity or dispute tooling are consuming cycles, move them to partners who live there.
- What needs to be sovereign for us? Decide which data and models must stay in-country. Map that to the multi-cloud footprint up front.
- How fast can we adapt to a rule change? Have the vendor show how a corridor rule change is handled without a code freeze or a journey redesign.
- What happens when volume doubles? Ask for evidence. Not a slide, an environment. If the answer is a hardware order, keep probing.
- If a method or partner disappears, what breaks? The right answer is that routing shifts and the UI doesn’t change.
These questions are not theoretical. They protect delivery timelines and customer trust when the market moves.
A networked ecosystem, not a solo sport
None of this works if firms try to build alone. The African FinTech market rewards teams that partner well and know when to assemble instead of invent. That spirit is exactly what the South African FinTech Awards and the African FinTech Festival aim to celebrate in Pretoria. It is also the ethos behind the conversations we host on the Talking Success podcast at TITC.
The point is not to pick one cloud or one rail or one vendor for everything. The point is to pick partners that make change safer, faster and cheaper to absorb. If your architecture and operating model can do that, you will keep shipping while others write memos.
What’s next
We will be unpacking a deeper product dive in an upcoming session with Kevin and Taps, including concrete patterns for payment orchestration, AI-assisted risk, and real-world examples of multi-cloud deployments in African markets. If you are a founder, CIO or head of payments, bring your toughest corridor and compliance questions.
In the meantime, explore the work behind the partnership at Vodacom Business Services and XLink, and join us in Pretoria for the South African FinTech Awards to meet the teams building this future.
FAQ's
Vodacom Business provides the digital infrastructure that fintechs need to scale – from secure cloud hosting and data connectivity to compliance-ready platforms. Their FinTech Cloud and sovereign AI capabilities allow startups and enterprises to innovate while meeting local data and regulatory requirements.
XLink acts as a payments orchestration layer, connecting merchants, banks, and payment service providers across Africa. It simplifies the complexity of multiple payment methods and ensures secure, compliant transactions locally and cross-border.
Compliance-by-design means embedding regulatory requirements directly into system architecture and product design – not adding them later. This makes it easier for fintechs to adapt to new regulations without disrupting customer experience or product delivery.
A sovereign AI cloud ensures that all customer and transaction data stays within the country of operation, giving organisations full control over data governance. This is crucial for financial institutions and fintechs operating under strict data residency and privacy laws.
Through try-and-buy models, scalable cloud offerings, and orchestration-as-a-service, smaller fintechs can access enterprise-grade infrastructure and AI tools without upfront capital investment. This levels the playing field, allowing startups to compete with larger incumbents in speed, compliance, and reliability.