Odds and settlement
Every bet type settles exactly as the published rules say, at the odds the player took.
SANS 1718 compliance testing
SASFA tests bookmakers' and betting operators' software against SANS 1718, the South African standard, and reports clause by clause what passed, what failed and the evidence. One standard, one kind of software, one question: does the player get what they were promised?
What a test covers
Every bet type settles exactly as the published rules say, at the odds the player took.
Where a product generates its own result, such as virtuals or numbers bets, the generator is isolated, statistically tested and unbiased.
Every wager stored with stake, odds, selection, time and result, append-only, and shown back to the player.
Balances, deposits, withdrawals, deposit and loss limits and self-exclusion enforced by the system, not by a policy document.
The build in production is the build that was tested, proved by hash.
A lost connection or power cut mid-bet ends in a settled or refunded bet, never a lost one.
How it works
A SASFA report is not a certificate or a licence. The SABS publishes the standard, a SANAS-accredited laboratory tests, the NRCS certifies and a provincial board authorises. SASFA sits before the laboratory. The certification path and the standard, explained.
Beyond the standard
Seven draft standards for the things SANS 1718 does not cover but a bettor still depends on: what they are told, how advertising behaves, how a dispute is resolved. Tested alongside the SANS clauses on request.
Most of the software South Africans bet on is built and tested somewhere else. A betting platform that can be tested here, against the standard that applies here, is one more layer of the industry whose value stays in the country.
Why that mattersFrom the blog
How to read the odds, check the operator, watch your own behaviour and find help.