Identity verification and AML screening. Every know your customer check and source of funds request on the platform runs through Sumsub.
What each integration actually does
Eight technology partners are wired into the platform. This page says what each one covers and where it sits in the flow.
An ecosystem, not a closed box
Every provider the platform is wired to
Specialist providers brought into one operating environment, from payments and games to identity, infrastructure and player support.
Game providers
Technology and operating partners
Payments
Identity and compliance
Player support
A mark appears only where the partner has supplied one. Every partner is named in full on the partners page.
The eight integrations, and what each covers
Each one has its own page saying what it does inside the platform, what it removes, and what stays with you.
8 integrations shown.
Identity and compliance
Verification, source of funds and screening, feeding the compliance tier that gates money.
Payments
Fiat and crypto rails, plus the payment signal behind a withdrawal decision.
Fiat payments and e-wallet. MiFinity is the fiat side of the hybrid wallet that sits beside crypto in one reconciled ledger.
Crypto payment processing. Deposits arrive over major crypto rails, convert at the quoted rate and credit the wallet on confirmation.
Payments intelligence. Yaspa adds signal to the payment picture that a raw transaction record on its own does not carry.
Game aggregation
One integration carrying the studio catalogue into every brand on the platform.
Game aggregation. One integration that carries a large studio catalogue into every brand on the platform and keeps it in sync.
Player support
The layer that answers payment, bonus and account questions before a human sees them.
TUGI AI, the AI player support layer that answers payment, bonus, KYC and account questions and escalates what it should not answer.
Infrastructure and security
What the deployments run on, and the security programme they are run under.
CloudWalker
Infrastructure
Infrastructure. CloudWalker is the hosting layer underneath both shared and dedicated deployments of the platform.
Space Admins
Security
The ISO/IEC 27001 partner behind the information security management system the platform is built and operated under.
An integration is finished when the platform can show what it did
A provider returns an answer. The platform writes that answer into the record your staff already work in, and writes the event behind it into the same trail as every other action on the deployment.
The result lands in the platform record
A verification, a payment or a support answer is written against the player it belongs to, not left in the provider's own console.
The event carries the actor and the moment
Each entry names who or what acted, their role, where they acted from and when, including automated callbacks from a provider.
One trail, whichever provider produced it
Provider events and staff actions read in the same list, so nobody reconciles two histories after an incident.
Adding a provider that is not on this page
From a request to a working connection
A provider you need but do not see here goes through the same sequence as the eight above. The scope is written down before anyone starts.
Provisioning takes hours. Getting to a live, trading casino also depends on licence approval, payment onboarding and content agreements, which we sequence with you. Integration scope, sequencing and commercial terms depend on the provider and on your deployment. They are agreed during discovery rather than promised on this page.
Confirm the provider and the product
Providers sell several. We settle which one you use, which markets and currencies it has to cover, and what it replaces on your side.
Read the documentation and the sandbox
A documented API and a real test environment decide whether the work can be planned around you or around the provider's release calendar.
Build against the platform record
The connection is written so the provider's result lands in the player, wallet or catalogue record it belongs to, with its audit entry.
Validate on both sides
Tested against the provider's sandbox, then against a controlled environment on your deployment, before anything reaches a player.
Enable it per brand
Switched on for the brands that need it, from the back office, with the change recorded against the person who made it.
What we need before we can scope a new one
An integration is engineering with another company on the other end of it. These answers are what let us give you a real estimate rather than an optimistic one.
About the provider
The provider and the specific product
Providers usually sell several. The one you already use is rarely the one on the front page of their site.
The markets and currencies it has to cover
Coverage is the first thing that turns a straightforward integration into a long one.
Whether there is a documented API and a sandbox
Without a test environment the work is scheduled around the provider rather than around you.
Who owns the relationship on their side
A named technical contact at the provider shortens every integration we have done.
About your operation
Which route you are on
White Label and Turnkey Platform put the commercial relationship with the provider in different places.
Which brands it has to reach
One brand, some of them, or every brand on the deployment, now and later.
What it replaces, if anything
Adding a provider beside an existing one is a different job from swapping one out mid-operation.
When you need it working
A date we can plan against, and what happens on your side if it moves.
Tell us which provider you need
If it is not on this page, say so. We will come back with what integrating it involves before you commit to anything.
An integration is scoped before it is quoted, and the scope is written down before anyone starts.
