How it works
The remote gambling device, (often the game server), must regularly verify that its software components – and any other element that could impact the outcome of a game – are authentic and unchanged.
This is done via a cryptographic method, such as SHA checksums, which generate a unique fingerprint for files. This must be matched with the checksum provided in the game certificate issued by the testing lab.
The idea is simple: if a file has been tampered with or changed, the checksums won’t match, and the casino will have to remove the game since it is no longer verified.
These are usually run daily, and it is absolutely vital they are conducted reliably.
Introducing St8’s checksums API
That’s why St8 has introduced our Checksums API, which has been specifically designed to not only ensure compliance, but make it a simple, seamless procedure to fulfil your obligations.
Direct supplier checksums and simple delivery
Unlike most aggregators, we gather checksums directly from all our suppliers, and match them with our own game codes, before returning them to the operator via a single API.
And with peace of mind, you’ll be able to focus on delivering the best possible experience to your users.