Why should South Africa only be a market?

Where the money actually goes

A single bet touches a stack of software. Almost every layer of that stack is a commercial relationship with a supplier, and in South Africa most of those suppliers are not South African. Each one is a real cost, contracted in a foreign currency more often than not, and recurring for as long as the operator trades.

1. 01 Platform and sportsbook software The engine that prices markets, settles bets, runs the wallet and holds the player account. Usually licensed from an offshore vendor on a revenue share or a monthly fee.
2. 02 Game content and studios Slots, live tables and crash games. Almost entirely supplied by international studios, with a cut of every wager routed back to them.
3. 03 Payments and settlement Acquiring, gateways, wallets, card scheme fees and cross-border settlement. Each hop has a price, and several of those hops are priced in a currency that is not ours.
4. 04 Identity and verification KYC, age assurance, document checks and fraud scoring, often charged per verification to an overseas provider.
5. 05 Data, odds and feeds Live scores, pricing and streaming rights, bought from a small number of global suppliers.
6. 06 Testing and certification Laboratory testing of games and random-number generators, historically done abroad because that is where the labs are.

None of this is illegitimate. Suppliers build good products and charge for them. The question SASFA is asking is narrower and more uncomfortable: why is a country that builds world-class banking and payments software not building this software?

Be precise about the money, or the argument collapses

It is tempting to say that offshore software siphons tax revenue out of South Africa. It is also wrong, and saying it makes the rest of the case easy to dismiss.

Gambling taxes and provincial levies are paid here, by the licensed operator, whatever software it runs. So is company tax on the operator's own profit, and VAT where it applies. Those do not leave.

What leaves is the technology and service fee. The platform licence. The revenue share on every spin of a game built elsewhere. The per-check verification charge. The data feed. The gateway margin. These are imports of services, paid in rands that are converted and sent out, and they recur every month for the life of the business. That is a current-account item and an economic-participation question, not a tax scandal.

The distinction matters because it is the accurate one, and because an organisation that intends to publish verifiable standards cannot afford to be loose with a number when it suits the argument.

What stays when the technology is built here

• The margin. A licence fee paid to a Cape Town company is revenue in Cape Town.
• The intellectual property. Whoever owns the engine owns the asset, and can sell it into other markets.
• The skills. Platform, payments, cryptography and high-volume transactional engineering are transferable far beyond gambling.
• The employment. Not call-centre headcount: engineering, mathematics, testing, security and product work.
• The ability to export. South African software sold into Africa and beyond is an export, and the flow runs the other way.
• The ability to audit. Technology built and tested here can be examined here, which is the whole point of the standards.

Transactions, too

The same argument applies to money movement. Every deposit and withdrawal passes through acquiring, a gateway and settlement, and each of those layers prices its service. Where that infrastructure is domestic, the fee stays in the domestic financial system. Where it is not, it does not.

South Africa has genuinely strong payments technology. There is no structural reason gambling transactions should be routed through, and priced by, infrastructure outside the country.

What has to change

Local suppliers do not fail to win this work because they cannot build it. They fail to win it because there is no established route from "we have built it" to "it is certified, and an operator can adopt it without taking a regulatory risk". That route is made of standards, independent testing and a certification methodology somebody trusts.

Which is why SASFA treats this as the same problem as fairness and player protection, rather than a separate economic hobby-horse. A published standard that a South African studio can build to, and be tested against, is industrial policy as much as it is consumer protection.

1. South African developer
2. South African software
3. South African operator
4. South African player
5. Value that stays in South Africa

If you build this

SASFA is looking for South African engine developers, game studios, payments companies, identity providers, testing laboratories and researchers. If you are building any layer of this stack in South Africa, or want to, get in touch. The standards being drafted now are the ones you will eventually be tested against, and it is considerably better to help write them.