100HP
  1. General
100HP
  • 100HP API for partners v2.9.1
    • General
      • Overview
      • FAQ
        • Rollback and billing resolver general flow
        • HTTP status codes and custom error codes
        • IP Whitelisting
    • Integration
      • Preparation for integration
      • General API provision
    • 100HP Gaming API
      • Game list
      • Launch game url
      • Video replay
    • 100HP Game flow API
      • Player authorization
      • Get balance
      • Withdrawal money
      • Deposit money
      • Rollback money
    • Implementation Guide
      • YourCasino.js
      • Casino.js
      • TestCasino.js
      • DDL-example
        • mongodb.js
        • mysql.js
        • postgres.js
    • Testing
      • Automated Test Service
    • API INFO
      • API Changelog
  1. General

Overview

Glossary
General Description
Financial model of our system
Core Financial Operations
Transactions
Transaction Lifecycle
Transaction Types
Schematic example of a transaction life cycle
Integration scheme
API Changelog

Glossary#

TermDefinition
PartnerA side that integrates 100hp’s games onto its website.
100HP GamingA side that acts as an intermediary between Partner and Casino. Stores games, settings and etc.
CasinoA side that stores players, their balances and confirms transactions.

General Description#

The system works by using web services that are JSON data based.
100HP Gaming is a company specializing in developing and providing its games to online casinos and gaming aggregators.
The current document is intended for technical specialists and describes the following:
A way to get a list of games and a method to get a link to launch the game.
Methods that manage financial transactions during the game and use the player's account.
JSON format is used as the format of methods.

Financial model of our system#

The financial model of our games is built around a simple flow: the player places a bet and then receives a payout (or receives nothing if the round is lost). The pair “bet → round completion” represents a single game iteration.
In addition to regular gameplay, the system supports a free bet mode — a bet made using bonus funds. In this mode, no money is deducted from the user’s balance, and if the player wins, only the winnings amount is credited through a special operation.
The system also includes protection against cases when a game fails to properly issue the win. If no winning operation is received within a specified time after a bet is placed, the system automatically initiates a wager rollback.

Core Financial Operations#

The system uses four basic types of operations. Each one represents a specific financial action within a single game iteration.
1. withdrawal
Purpose: Deduct funds from the user’s balance.
Triggered when: The player places a bet.
2. deposit
Purpose: Credit winnings to the user’s balance.
Triggered when: The round ends and the result is calculated.
Note: If the player loses, a deposit is still sent, but with amount 0.
3. rollback
Purpose: Cancel a previously performed withdrawal.
Triggered when: An error occurs during round completion, or the system is technically unable to credit the winnings.

Transactions#

A transaction is an aggregate entity that combines all financial operations within a single game iteration (bet → result).
A transaction guarantees:
integrity of the operation set
correct execution order
a single point of storage and state control
In practice, a transaction is a container that fully describes the user’s financial activity within one in-game session.
Transactions are formed by linking operations via a shared identifier, referred to as txID.

Transaction Lifecycle#

A transaction describes the complete financial path of a game iteration—from the moment funds are deducted to the moment winnings are credited or the bet is rolled back.
It consists of one or two operations, capturing both their sequence and the final outcome.
A transaction always begins with an opening operation and ends with a closing operation. Depending on the situation, several transaction types are possible.

Transaction Types#

NameCompositionDescriptionOperation roles
Regular Game Transactionwithdrawal → depositThe player places a bet and the system performs a withdrawal. After the round ends, the game sends the result. Based on the result, the system performs a deposit, which closes the transaction. If the player loses, the deposit amount is zero.Opening: withdrawal Closing: deposit
Transaction with Payout Errorwithdrawal → rollbackThe transaction starts with a withdrawal. If the system does not receive the round result (for example, the game never sends a win), the auto-rollback mechanism is triggered. The system executes a rollback, canceling the withdrawal and closing the transactionOpening: withdrawal Closing: rollback

Schematic example of a transaction life cycle#

Typical game iteration

Integration scheme#

Partner and Casino communicate with 100HP Gaming API via HTTP requests by calling the methods described in this document.
Modified at 2026-01-28 14:29:22
Previous
General
Next
FAQ
Built with