1. The catalog and who decides what you see
Ask: Which studios and games are listed? Who decides which of them my account sees? Can I recognize the same game across studios? How do I keep my lobby in step with changes?
WGC's answer. The provider directory lists 184 studios: 182 are connected and two are available on request. A studio's entry does not mean that all of its games are open to every client. The games issued to your account are decided by your WGC manager, studio by studio, and your platform sees exactly those games.
Each game has a publicId that identifies it in your catalog and a universalId that is the same for the same game across the catalog. The games request returns 200 games per page and can be filtered by type: slot, live dealers, table, fast games, lottery, sport or other. After the first full download you ask only for changes, and a full sync at least once a day is recommended. Restricted countries and unavailable currencies are listed per game.
2. The wallet model and what happens on repeats
Ask: Where does the player's money live? What happens when my answer is late or a call arrives twice? How are bets cancelled?
WGC's answer. WGC uses a seamless wallet model: the player's money stays on your platform and WGC does not store player wallets. WGC calls your Callback URL with three commands, one to read the balance, one to record a bet with its win, and one to cancel a bet. If a studio sends the bet and the result separately, WGC joins them into one round.
A bet is recorded once per transaction id, so a repeated call does not debit the player twice. Calls are signed with HMAC-SHA256, and WGC waits three seconds for your answer. If it does not arrive in time, the bet is refused to the studio and WGC asks you to cancel it with a rollback, repeated on a schedule for up to 30 days. You can read the details on the seamless wallet page. A fair comparison should ask every candidate the same questions about repeats and cancellations.
3. Documentation and a test mode
Ask: Can I read the API description before I have access? What is the policy on changes? Can I test the whole path without real money?
WGC's answer. The description of the API is public: an OpenAPI file and a documentation page, both open without a key. If they differ, the file is right. A version does not break without notice: a field is removed or changes its meaning only after a deprecation notice and not earlier than 90 days later.
Testing starts with a test key, which opens a test game, WGC Test Slot. It makes real calls to your Callback URL without money, commission or ledger entries, and an option to lose the answer checks your rollback. In the back office, an integration check shows a live log of every call, and an integration test runs 14 checks of your wallet. Handlers in Node.js, PHP and Python, a check script and a go-live checklist of 14 points are public. See demo and test mode.
4. Reports and control of money
Ask: What reports do I get, for which periods, and can I export them? How is the commercial relationship with the aggregator tracked? What protects me from unusual wins?
WGC's answer. Reports show turnover, wins, GGR, RTP and commission for a period, with rounds, sessions, players and games, and an export to CSV. The commercial balance and the credit limit of each client are shown with their history, and credits and debits move up and down the chain of accounts. Sixteen alert rules are checked every five minutes, and critical ones also arrive on the phone app. Win limits let you place stop lines for suspicious wins within the boundaries of the platform.
5. A back office for partners
Ask: If I serve clients of my own, can I manage them? Who sees what? What is recorded?
WGC's answer. Accounts form a tree: a partner can create its own clients and sub-partners, and every client has its own users, rights, issued games, prices and currencies. A subordinate account never gets more than its parent, and one account cannot read another's branch; this is checked on the server. The Logs page shows who changed what in your branch. Two-factor protection works with an authenticator app or the WGC phone key and is on for superusers.
The back office is adapted to phones, and there is an Android app whose link your manager issues personally.
6. Support while you connect
Ask: Who helps when my calls fail? Where do I find answers while I am connecting?
WGC's answer. Ask WGC, the assistant in the back office, answers from the documentation and cites its source. With the integration right, its integration mode reads a limited snapshot of your own integration from the last seven days, without secrets or request bodies, and explains why your calls fail. Live support works inside the back office; when you write to it, quote the request id, transaction id, round id and the time in UTC.
What WGC does not do
A comparison is fair only if it names what you do not get. WGC is not a casino for players: it does not hold player balances and does not register players. Access to the client area is issued personally by a manager, and there is no self-service sign-up. You build and run a Callback handler yourself, and what each game supports, such as RTP settings, varies and is shown in the game's flags.
A simple way to run the comparison
- Write the six criteria as rows and the candidates as columns.
- Read each candidate's public documentation and note what is missing.
- Open a test environment, and make the wallet fail on purpose: a late answer, a repeated call, a cancellation.
- Ask what a refusal looks like when it reaches your platform.
- Ask who decides which games your account sees.
The game aggregator page and the integration steps show how WGC answers each of these. For the approach itself, read direct provider integration vs aggregator.