Open Banking in South Africa: How Stitch and FinFlux Make Float Possible

Open banking in South Africa is not a single regulatory mandate. It is a combination of voluntary API infrastructure, regulatory intent, and commercial agreements between fintechs and traditional banks. The key players building this ecosystem are Stitch and FinFlux, and understanding what they actually do helps explain what is possible for products like Float.

What Open Banking Means in the South African Context

In the United Kingdom and European Union, open banking is mandated. Banks must expose standardised APIs under PSD2 and the Open Banking Standard. Consumers can authorise third parties to read their account data and, in some cases, initiate payments on their behalf.

South Africa has no equivalent regulatory mandate yet. The SARB and the Financial Sector Conduct Authority (FSCA) have published position papers supporting open finance principles, but banks are not legally required to expose their data to third parties. What exists is market-driven: banks that want to participate in the open banking ecosystem build or allow integrations. Banks that do not, do not. Their choice.

In our tracking, approximately 4 major South African banks now support some form of API-based data access, though the depth and reliability of those integrations varies considerably.

Stitch: The Payment Infrastructure Layer

Stitch is a Cape Town-based fintech that provides payment and financial data APIs for South Africa. Its product set covers three main areas: instant EFT payments (allowing users to pay from their bank account without entering card details), account data access (reading transaction history and balance with user consent), and payment collection infrastructure.

For Float, Stitch's payment APIs are relevant as a potential alternative or complement to card-based collection. Where DebiCheck handles authenticated recurring debit orders, Stitch's instant EFT can handle one-time or variable payment flows. The two serve different use cases. Stitch's bank coverage in South Africa includes Absa, FNB, Standard Bank, Nedbank, Capitec, and Investec, covering the overwhelming majority of South African credit card holders.

Stitch has processed billions of rands in transaction value since its 2021 launch. It is not experimental. It is live and used by significant South African merchants and fintechs.

FinFlux: The Card Statement Intelligence Layer

FinFlux operates at a different layer of the stack. Its speciality is reading and structuring credit card statement data. For a product like Float that needs to identify eligible purchases on a user's credit card and present them for splitting, clean statement data parsing is essential.

FinFlux provides APIs that can, with user consent, access credit card transaction histories, categorise transactions, and surface specific purchases by merchant, amount, and date. Fact: credit card statement formats differ significantly across South African banks. What Absa calls a merchant code, FNB structures differently, and Standard Bank uses its own taxonomy. FinFlux normalises these into consistent data objects.

This matters more than it sounds. Without reliable statement parsing, Float would need to ask users to manually enter purchase details. That friction dramatically reduces adoption. API-based access that surfaces "here are your eligible purchases from the last 30 days, pick one" is a radically better experience.

The Regulatory Frame for Account Access

Using Stitch or FinFlux to access a user's bank account data requires explicit user consent under POPIA. The consent must be informed and specific: what data is accessed, for how long, and for what purpose. Float's privacy policy and data collection flow are built around these requirements.

The consent is also revocable. Users can withdraw access at any time through either the Float app or directly through their bank, depending on the integration model. Not theoretical. Not optional. It is technically enforced through the token-based authentication that underpins both Stitch and FinFlux integrations.

What Is Still Missing

Honestly, the South African open banking ecosystem is strong in payment initiation and weak in data portability compared to the UK or Australia. Read access to credit bureau scores via API is limited. Real-time affordability data from all credit bureaux (TransUnion, Experian, XDS, CompuScan) is not universally accessible via clean APIs. These gaps affect any product trying to build smart, low-friction credit risk management in South Africa. Real constraints.

The trajectory is positive. The SARB's work on a payment ecosystem roadmap includes open data as a pillar. We expect progress over the next two to three years, though the South African regulatory process moves at its own pace.

For more on how Float uses payment infrastructure, see the PayFast integration article or read about Float's technical approach.