SASFA, South African Software Fairplay Audit

Regulatory pathway

A test report is one step, not the whole approval

South African bookmaker software moves through distinct standards, testing, certification and provincial approval steps. Each body issues a different record and none should be represented as another.

From SANS 1718 to licensed deployment

  1. 01

    SABS

    Develops and maintains SANS 1718

    The applicable national standard and its published parts and editions.

  2. 02

    Licensed testing agent

    Tests the named system and build

    A laboratory test report recording scope, methods, evidence and results.

  3. 03

    NRCS

    Evaluates the certification submission

    The Letter of Certification when the applicable requirements are satisfied.

  4. 04

    Provincial licensing authority

    Considers the deployment

    An approval tied to the licensee, product, conditions and jurisdiction.

  5. 05

    Licensed bookmaker

    Deploys the approved system

    Operation under the bookmaker’s licence and the authority’s conditions.

Source: National Gambling Board Gambling Product Value Process and the NRCS gambling submission process.

Where SASFA intends to sit

SASFA is being built for the licensed testing-agent step, with a specialist focus on online bookmaker wagering and record-keeping software. It is not yet authorised to perform that statutory role. When the status changes, the site will publish the exact accreditation scope and licence evidence.

What the public registry will preserve

A SASFA report record will identify the system and exact build tested. Separate fields will record the NRCS Letter of Certification and each provincial approval only after those external facts have been verified. A missing external record will remain missing; it will never be inferred from the laboratory result.

A provider is not certified in the abstract

A supplier can own several products, and a bookmaker can deploy several systems. Testing and certification attach to defined systems and versions; licensing and deployment approval attach to legal entities and regulatory decisions. The planned report registry models those relationships explicitly.