LogoLogo
Knowledge BaseDeveloper DocsProduct NewsChangelogStatusHub88 home
Developers Docs
Developers Docs
  • Hub88 APIs
    • Fundamentals
    • Core API flow
    • Request structure
    • Code samples
  • Operator API Reference
    • Getting Started - Technical Integration
    • 🎲Operator API Overview
      • Error codes
      • Seamless Wallet response statuses - Operator API
    • Games API
    • Wallet API
    • TransferWallet API
    • Transactions API
    • Freebets API
    • Recommendations API
    • OnDemand API
  • Supplier API Reference
    • Supplier API Overview
      • Seamless Wallet response statuses - Supplier API
    • Games API
    • Wallet API
    • Freebets API
Powered by GitBook
LogoLogo

Hub88

  • HubWallet
  • HubMarket
  • Suppliers

Hub88

  • News
  • Status
  • Privacy Policy

Contact

  • sales@hub88.io

Follow us

  • LinkedIn
  • Telegram

Copyright © 2025. All Rights Reserved.

On this page

Was this helpful?

  1. Operator API Reference
  2. Operator API Overview

Seamless Wallet response statuses - Operator API

As a part of the Wallet API, the following response status codes need to be implemented by the Operator, to respond to Hub88 requests.

Status Code
Description

RS_OK

Successful response. The request has been accepted and processed without any errors.

RS_ERROR_UNKNOWN

General error status, for cases without a special error code.

RS_ERROR_INVALID_PARTNER

Operator or their sub_partner is disabled or incorrect sub_partner_id is sent.

RS_ERROR_INVALID_TOKEN

Token is unknown to Operator's system. Note that there is a different status for expired tokens.

RS_ERROR_INVALID_GAME

Unknown game_code. NB! In case of game Suppliers with game lobby (Live Dealers), user can switch games within one game session. Such changes are tracked and a corresponding game_code is sent to specify, which game the user is currently playing. game_code may change multiple times within one game session.

RS_ERROR_WRONG_CURRENCY

The transaction currency is different from user's wallet currency.

RS_ERROR_NOT_ENOUGH_MONEY

Not enough money on User's balance to place a bet. Please send the actual balance together with this status.

RS_ERROR_USER_DISABLED

The user is disabled or locked and can't place any new bets.

RS_ERROR_INVALID_SIGNATURE

The Operator couldn't verify signature on request from Hub88.

RS_ERROR_TOKEN_EXPIRED

The session with the specified token has expired. NB! Token validity most not be validated in case of wins and rollbacks, since they might come after the bet has been played.

RS_ERROR_WRONG_SYNTAX

The received request doesn't match expected request form and/or syntax.

RS_ERROR_WRONG_TYPES

The type of parameters in the request body don't match expected types.

RS_ERROR_DUPLICATE_TRANSACTION

A transaction with same transaction_uuid was sent, but there was a different reference transactionID, amount, currency, round, user or game.

RS_ERROR_TRANSACTION_DOES_NOT_EXIST

Returned when the bet referenced in win request can't be found on Operator's side (wasn't processed or was rolled back).

RS_ERROR_LIMIT_REACHED

The daily request limit is reached for the player.

PreviousError codesNextGames API

Last updated 5 months ago

Was this helpful?

🎲