Your code stays as it is however many vendors are added. Here is how GG Labs is put together to keep that promise — only the parts you can verify.
Shown in seamless mode. Your platform talks to GG Labs alone, and the layer in the middle absorbs the per-vendor differences.
Transfer mode has no callback at the bet step. Balance moves to the vendor wallet when the player enters a game and comes back when they leave. Either way, the only spec you implement is ours.
Your wallet structure decides which. Switching mid-operation does not mean re-integrating vendors.
| Seamless | Transfer | |
|---|---|---|
| Where the balance sits | The partner platform wallet. GG Labs only relays. | The vendor wallet during play. Transferred on entry and exit. |
| What the partner implements | Three callbacks: balance, debit, credit | Two APIs: deposit and withdrawal |
| Balance updates | Real time, every bet | At transfer |
| Fits when | You run several vendors at once and want player balance managed in one place | Your wallet structure is hard to change, or you need to open quickly |
| Switching modes | Possible while live. You add or remove callbacks on your side; the vendor integrations stay as they are. | |
What partner engineering teams want to know before the first meeting.
| Protocol | REST (JSON) request and response, game and transaction events over WebSocket |
|---|---|
| Authentication | Per-partner API key with request signing (HMAC). IP allowlist required in production |
| Environments | Sandbox and production separated. Same spec, different keys |
| Documentation | OpenAPI specification, callback examples, test scenarios. Readable before signing |
| Events | Bet settlement, payout and game state changes delivered by webhook |
| Currencies | KRW, USD, JPY, PHP, THB, VND. Varies with vendor support |
| Settlement data | Daily report files and API queries. Per-vendor formats converted to a single schema |
| Monitoring | Per-vendor response time and error rate watched continuously. Partners alerted when thresholds are crossed |
Instead of certification badges, what we actually do.
We watch response time and error rate per vendor continuously. Cross a threshold and you hear from us before you notice.
Cause, blast radius and expected recovery shared the moment it is filed, with a report once it closes.
Audit logs kept per bet and per settlement. If a dispute arises, partner and vendor look at the same record.
TLS on every hop, encryption for stored data. Keys are managed separately from the service.
Console, API and operational access separated by role, with every access logged.
Regular backups and recovery rehearsals. The recovery time objective goes into the contract as a number.