The market's data, arriving as it plays.
Operators, game providers and payment gateways send their data over secured APIs. Every request passes Cloudflare first, only senders you have whitelisted get through, and each one can send only its own data.
Data feeds
OperatorsGame providersPayment gateways
01CloudflareThe first stop: attacks are stopped at the edge
02Whitelisted senders onlyAnyone you haven't whitelisted is turned away
03Signed, single-use requestsEach signed with the sender's own key, timed, and never accepted twice
04Their own data onlyA sender can only send data about itself
Your iRegulate.AIin your country or the cloud
What comes in
Four kinds of data, one market.
Operators' feedsBets, wins and players' money, sent as the play happens.
Game providers' dataThe play each provider served, to check against the operator's own.
Casino floor countsDaily table counts from each premises.
Applications and documentsOnline or scanned from paper. Scans, Word and Excel files are read so their words can be searched.
What happens to it
Matched, checked and watched, as it lands.
- 01MatchedEach bet is tied to its licensed operator, its website and its game. Games nobody registered are listed, not lost.
- 02ConvertedFeeds in another currency are converted to yours.
- 03WatchedAlert rules run on it, and a feed that goes quiet is flagged.
- 04KeptIt becomes the basis of each month's statement, and stays on the record.
For your IT team
Every connection and job, in plain view.
Administrators see the background work behind the platform: scheduled jobs, the queues they run in, and each connection, with what ran and what failed.
Background work
JobsWhat runs, and when it last ran
QueuesWork waiting, running and failed
ConnectionsEach feed and service, and whether it's answering
Connecting your operators?Tell us what your operators send today, and we'll show you how it comes in.
Ask about data feeds