Request a title-level catalogue for your actual markets.
Test retries, reversals and reconciliation in a sandbox.
Price the complete operating model, including third-party dependencies.
Ask for the catalogue you can actually use
A total game count does not tell you what can appear in your lobby. Request a dated, title-level export identifying studio, game identifier, format, supported configuration and the restrictions relevant to your business. Separate games available now from planned additions. Agree how title removals and configuration changes will be communicated.
Which titles are available through our proposed contract and platform?
Which certifications, currencies and languages need separate confirmation?
Test the wallet under failure, not only success
An integration that launches a game successfully has passed only the first test. Public operator API documentation provides examples of wallet calls, retries and transaction handling. Build a sandbox test pack around duplicate requests, delayed responses, interrupted rounds, insufficient funds and reversals. Define which ledger is authoritative and who investigates mismatched outcomes.
Does retrying a transaction change the player balance twice?
What happens when a round completes after an earlier request timed out?
Document security and release ownership
Have engineering review request validation, signing, credential rotation and access controls. Establish separate test and production environments and a process for changing credentials without losing service. Record who approves API or game-version changes and which regression tests must pass. Do not send live credentials or player records in a procurement brief.
Who owns integration monitoring and out-of-hours incident response?
How are breaking changes and rollback instructions delivered?
Make promotions a separate acceptance decision
Free spins, tournaments and jackpots can introduce eligibility rules, extra balance states and commercial costs. Ask which functions work with each selected game rather than assuming a catalogue-wide capability. Define campaign approval, player exclusions, cancellation behaviour and the reporting needed to reconcile promotional spend.
Which tools require a separate contract or front-end implementation?
How are unfinished bonuses and interrupted campaigns settled?
Reconcile the commercial and technical records
Request sample game-round, settlement and invoice exports. Check whether they share stable identifiers and compatible time zones. Assign an owner to differences between operator, aggregator and studio records. Compare monthly fees, revenue-linked charges, content agreements, minimums and support obligations in the same model; an inexpensive interface can still carry substantial operating work.
Can finance trace an invoiced amount back to its underlying rounds?
Which studio agreements, taxes and costs sit outside the aggregator quote?
Use a shortlist with explicit exclusions
Build the shortlist from documented requirements, then ask candidates to confirm the gaps. A studio portfolio, a full operating platform and a content aggregator are not interchangeable products. The company profiles below explain their published offering; inclusion here is not proof that any particular title or service is available to your operator.
Casino aggregation: wallet acceptance checks
Use these scenarios to prepare an operator sandbox test log. Hub88’s published API illustrates the behaviours below; another aggregator may use different identifiers, statuses and recovery rules. Agree the expected result against the exact API version before testing. IGW³ has not run these tests against the suppliers.
| Scenario | Sandbox action | Evidence to collect |
|---|---|---|
| Duplicate transactions | Repeat a successful bet, then reuse its transaction identifier with a different amount. Include simultaneous duplicates. | One debit for an identical duplicate, and the documented duplicate-transaction error for conflicting reuse. Keep the ledger entries and both responses. |
| Request authentication | Send a valid signed request, then change its body without updating the signature. | The changed request fails signature verification. Check that rejection leaves the ledger unchanged; retain the error and verification log without secrets. |
| Settlement after session expiry | After an accepted bet, expire the player session and submit its legitimate win or rollback. | Hub88 says wins and rollbacks must not depend on token validity. Verify settlement while retaining the required signature and transaction checks. |
| Win without a valid prior bet | Submit a win referring to an unprocessed bet; repeat for a bet already rolled back. | Record the documented missing-transaction response for these win cases. Specify missing-reference rollback behaviour separately with the supplier. |
| Lost acknowledgement | Commit a bet, simulate a lost response, and observe retry and rollback processing. | Trace one original debit and its eventual reversal without duplicate balance changes. Confirm retry rules and distinguish bet recovery from provider-dependent win recovery. |
| Currency and precision | Send a mismatched wallet currency, then test valid amounts using the API’s integer scaling. | Capture the currency error and exact ledger arithmetic. Confirm each chosen provider’s supported currencies and amount format rather than assuming catalogue-wide support. |
Continue the research
Company evidence, not a paid ranking.
These profiles illustrate different products and operating models. Confirm the exact market, service and contract fit before treating any company as a qualified candidate.
EveryMatrix
Consider EveryMatrix when evaluating a platform migration or a modular casino or sportsbook addition that must connect to existing operational systems.
Read the company evidence
SOFTSWISS
Consider SOFTSWISS when comparing an integrated operating stack with individual casino, sportsbook or aggregation modules for an existing business.
Read the company evidence
Relax Gaming
Consider Relax Gaming when a casino wants both proprietary content and a multi-studio distribution relationship, with common front-end requirements to assess.
Read the company evidence
Games Global
Consider Games Global when a casino is assessing a multi-studio content catalogue with branded titles and progressive jackpot games.
Read the company evidence
Lightning Box
Consider Lightning Box when comparing casino content distributed through Light & Wonder. Start with a named title and its available configuration, then confirm the commercial and technical route for the intended market.
Read the company evidence
GameArt
Consider GameArt when comparing a slot supplier with jackpot options or several casino game formats through one content relationship. Confirm the specific portfolio available through the intended integration route.
Read the company evidence
Kalamba Games
Consider Kalamba when comparing a slot-content addition with a separate requirement for studio hosting, distribution and promotional tooling.
Read the company evidence
Evoplay
Consider Evoplay when an operator wants to assess instant games alongside slots and table content, with promotional tools included in the product discussion.
Read the company evidence
Endorphina
Consider Endorphina for a slot-content shortlist where classic fruit presentations and feature-led variations are both relevant to the casino lobby.
Read the company evidence
Pragmatic Play
Consider Pragmatic Play when comparing a multi-format casino-content supplier with its own live games and configurable promotional tools.
Read the company evidencePut the questions to work
Build a more useful shortlist.
Start with this guide’s ready-to-edit brief in Pulse. Add your company, markets and non-negotiable requirements. Nothing is sent until you review and submit the form.
Prepare a private briefSources and scope
Product documentation supports the capability examples. Procurement questions and assessments are IGW³ editorial analysis, not supplier endorsements. Sources reviewed 2026-09-30; check the linked originals for later changes.
Hub88: response statuses and settlement rulesHub88: operator API overview and request handlingHub88: wallet API referenceSOFTSWISS: Game Aggregator product scopeCompare the same requirements across suppliers and record evidence, tests and unresolved gaps. The editable workbook starts with no supplier results or approvals.
Get the free supplier evaluation worksheetThis educational guide is independent, free to access and designed as a practical starting point. Regulatory and legal requirements should always be confirmed with the relevant authority and qualified advisers.
Our evidence methodology