Operator API Integration DocumentDate Update: 2024/11/18

Version Update History

Table of Contents 3

Terms of Use 4

Overview 5

Signature Validation 6

iFrame 6

Currency 6

Consistency of Bets 6

How to Start A Game 7

Transfer Wallet API 8

Register Player 10

Player Transfer - Deposit 10

Player Transfer - Withdraw 11

Get Transfer History 13

Get Game List 14

Get Bet Limit List 15

Enter Game 16

Get Player Balance 17

Get Betting Records 19

Seamless Wallet API 21

Overview 22

Game API: Get Game List 22

Game API: Get Bet Limit List 23

Game API: Enter Game 24

Game API: Get Betting Records 25

Wallet API: Verify Player Information 27

Wallet API: Get Player Balance 28

Wallet API: Bet Debit Process 29

Wallet API: Bet Payout Credit Process 32

Wallet API: Cancellation Process After Placing A Bet 34

Wallet API: Cancellation Process After Getting A Payout 37

Wallet API: Bet Resettle Process 39

Wallet API: Promotions 41

Betting Area Comparison Table 43

OG Betting Record Parameters 44

Baccarat 45

Dragon Tiger 45

Niuniu 46

Sedie 46

Money Wheel 47

Three Cards 47

Sicbo 47

Operator API Integration Table of Contents

Roulette 49 Sports 54 Code Comparison Table 56

Terms of Use

• The operator should ensure that, under any circumstances, no duplicate processing of any independent bet order number as transaction_id occurs in the operator’s wallet system.- The operator should deploy corresponding functionalities based on the Game API and Wallet API to achieve game entry, placing bets, and payouts.- As per the Game API specifications, the operator should generate and verify a token when requesting entry into the game.- The operator should verify that the player’s balance is sufficient to cover the betting amount.- When a player places a bet, our system will call the operator’s system according to the Wallet API specifications.- If the operator does not respond to this request, our system will initiate a rollback request, asking the operator to refund the betting amount for that /bulk/debit transaction.- During payout of the game, our system will call the operator’s system based on the Wallet API specifications.- If the operator does not respond to the payout request, the same request will be resent at 10-second intervals, up to three times (including the first request). This feature is disabled by default.- When a player loses money, our system will call the operator’s system based on the Wallet API specifications, where amount = 0 and winlose_amount is a negative number.- The operator can query player game records through our reporting backend.- Chip conversion functionality is not available in the single wallet mode.- Player balance account changes are not available in the single wallet mode.

We recommend that each client and each currency use a separate account to connect with the game. This approach offers several benefits:

1. Improved System Stability and Reliability: Using multiple accounts helps ensure that if one account encounters a problem, the rest of the system will continue to run smoothly. This means fewer disruptions and a more reliable experience for you.2. Flexible Client Solutions: If you have different needs, you can make individual requests through the API interface, allowing us to better meet your specific requirements.

Overview

Overview- If an operator requires multiple currencies, please apply for multiple integration accounts based on each currency.- Each integration account supports either a single wallet or a transfer wallet.- Public key and Private key are provided by OG.- Seamless wallet integration includes 2 REST API: Game API and Wallet API.- Transfer wallet integration includes 2 REST API: Game API and Transfer Wallet API.- Please use lowercase letters for all key and value of each parameter.- The Game API is responsible for handling operations related to games, such as entering games, retrieving game data, and more.- The Wallet API, on the other hand, deals with operations related to wallets, including balance inquiries, chip transfers, and bet payouts, among others.- The Transfer Wallet API is designed for operators using the transfer wallet mode, allowing operators to perform chip conversions, including deposit and withdrawal chips from player accounts, as well as retrieving player balances.

Signature Validation

Signature ValidationTo ensure that API requests have not been maliciously tampered with, we have implemented a digital signature verification mechanism in API requests. This mechanism covers various API requests such as game entry, player authentication, betting, payouts, and chip conversions.

A.How To Generate A Signature

A. How To Generate A Signature1. Sort the keys in the request parameters in alphabetical order from ‘a’ to ‘z’.2. Concatenate the sorted keys using the “&” symbol to create a string.3. Encrypt the string using the private key with MD5 encryption, resulting in a hash function.4. Use the generated hash function as the value for the “signature” key in the parameters, then send the request.

B.How To Verify The Received Signature

B. How To Verify The Received Signature1. Sort the keys (excluding the signature) from the received request parameters alphabetically from ‘a’ to ‘z’.2. Concatenate the sorted keys (excluding the signature) using the “&” symbol to create a string.3. Encrypt the string using MD5 encryption and the same private key used for creating the signature, resulting in a hash function.4. Compare the hash function obtained from the above steps with the value of the signature in the original request to verify if they match.

Operator API Integration Signature Validation, iFrame, Currency And Consistency of Bets

The keys must be sorted in alphabetical order from ‘a’ to ‘z’; otherwise, it will result in different hash functions being generated.

A hash function is one- way, meaning it’s not possible to reverse- engineer the original data from the hash value.

iFrame

Operators can utilize iFrames to run games in desktop browsers; however, it’s not supported on iOS or Android systems.

• iFrame supports: Desktop- iFrame does not support: iOS, Android (Live games opens in a new page; otherwise, it is not supported)

Currency

The game supports all currencies except PHP and HKD. Currently the virtual currency only supports USDT, VND, IDR, INR, MMK support 1:1 and 1:1000

• In order to use 1:1. Please use VND, IDR, INR, MMK for the currency field.- In order to use 1:1000. Please use VNDK, IDRK, INRK, MMKK for the currency field.

Consistency of Bets

In order to ensure the consistency and uniqueness of bets, when all requests includes a transaction_id field, OG will ensure that all transaction_ids will only be processed once, and if there are repeated bet requests, OG will ignore the request and will not process them again.

7 | OG OPERATOR API INTEGRATION DOCUMENT

How to Start A Game

Workflow:

After you have obtained all the information, you need to follow the following steps:

1. The game_id can be obtained from {{OG_Host }}/api/v2/platform/game/game-list. Note: This feature will directly affect players entering the lobby or designated tables.
   
2. The betlimit can be obtained from {{OG_Host }}/api/v2/platform/operator/betlimit.
   
3. Use the Token and redirect the player to the game. The Token is generated by the Operator to verify the player’s information.
   
4. Only using {{Operator_Host }}/api/v2/operator/security/authenticate OG will authenticate player information to the Operator.
   
5. When OG receives S-100 verification from Operator {{Operator_Host }}/api/v2/operator/security/authenticate, the player can then enter the game
   
6. The operator should select an appropriate code from the Response Code list provided by us and return it accordingly.
   
7. For request (3), if the signature verification fails, the operator should return response_code = E-103 in step (4).
   
8. For request (3), if the token is invalid or does not exist, the operator should return response_code = E-106 in step (4).
   
9. For request (3), if the player is disabled, the operator should return response_code = S-105 in step (4).

Transfer Wallet

Register Player

POST - /api/v2/platform/transfer-wallet/register

The operator requests to register a player (before registering a player, this interface can verify whether the player exists)

Parameters:

Request Example:

1 curl - - location - - request POST ‘http://xyz.pwqr820. com:9003/api/v2/platform/transfer- wallet/register’  2 - - header ‘key: {public_key}’  3 - - header ‘operator- name: {operator_name}’  4 - - data- raw ‘{ 5 “player_id”: “tyrion_12345”, 6 “nickname”: “iamtyrion12345”, 7 “timestamp”: 1689765296 8 }’

Successful Response Example:

Existing Player Response Example:

Player Transfer - Deposit

POST - /api/v2/platform/transfer-wallet/deposit

The operator deposits the amount specified by the player from the operator’s system wallet to the OG platform

Note: You must register the player before calling this interface

Parameters:

Request Example:

1 curl - - location - - request POST ‘http://xyz.pwqr820. com:9003/api/v2/platform/transfer- wallet/deposit’   2 - - header ‘key: {public_key}’   3 - - header ‘operator- name: {operator_name}’   4 - - header ‘Content- Type: application/json’   5 - - data- raw ’  6 “player_id”: “tyrion_12345”, 7 “transaction_id”: “6e75a8385497d325bf76da4184d1eb94”, 8 “transfer_amount”: 7395.00, 9 “timestamp”: 1689015741, 10 “signature”: “2afd17914a74ce7b4425fefe8e2d2f75” 11 }

Successful Response Example:

1 { 2 “rs_code”: “S- 100”, 3 “rs_message”: “success”, 4 “balance”: 12345.67 5 }

Player Does Not Exist Response Example:

Duplicate transaction_id Response Example:

Player Transfer-Withdraw

POST - /api/v2/platform/transfer-wallet/withdraw

The operator transfers the amount specified by the player from the OG platform to the operator’s system wallet.

Parameters:

Request Example:

1 curl - - location - - request POST ‘http://xyz.pwqr820. com:9003/api/v2/platform/transfer- wallet/withdraw’  2 - - header ‘key:{public_key}’  3 - - header ‘operator- name:{operator_name}’  4 - - data- raw  5 “player_id”: “tyrion_12345”, 6 “transaction_id”: “6e778fbdafb0af9b28a0b8ebc771982d”, 7 “transfer_amount”: 22070.00, 8 “timestamp”: 1689138141, 9 “signature”: “ed5324d1fe5c99281df6a8e2d2641b85” 10 }

Successful Response Example:

Insufficient Balance Response Example:

Duplicate Response With Transfer Number Example:

Get Transfer History

GET - /api/v2/platform/transaction/transfer-history

Operator requests player balance history

Parameters:

Request Example:

1 curl - - location - - request GET ‘http://xyz.pwqr820. com:9003/api/v2/platform/transaction/transfer- history?fetch_id=1& limit=8000’   2 - - header ‘key: {public_key}’   3 - - header ‘operator- name: {operator_name}’

This interface is suitable for the following scenarios:

Retrieving transfer records for data queries. In cases where a transfer fails or times out due to unforeseen factors during the transfer process, this interface can be used to retrieve the transaction number and check if it exists in the platform system.

If unexpected factors also lead to failures or timeouts with this interface, manual inquiry to the platform is necessary. Do not associate this interface with the transfer interface for simultaneous confirmation.

Successful Response Example:

1 { 2 “rs_code”: “S- 100”, 3 “rs_message”: “success”, 4 “last_fetch_id”: 2019, 5 “records”: [ 6 { 7 “fetch_id”: 2020, 8 “player_id”: “1175sbons41194674”, 9 “transaction_id”: “t10053053400005406863”, 10 “transaction_time”: 1694144197, 11 “transaction_type”: “deposit”, 12 “currency”: “THB”, 13 “transfer_amount”: 321.67, 14 “operator_name”: “testoperator” 15 }, 16 { 17 “fetch_id”: 2021, 18 “player_id”: “1175sbons41194674”, 19 “transaction_id”: “t10053053400005406864”, 20 “transaction_time”: 1694144197, 21 “transaction_type”: “withdrawn”, 22 “currency”: “THB”, 23 “transfer_amount”: 1000, 24 “operator_name”: “testoperator” 25 } 26 ], 27 }

No Data Found Response Example:

1 { 2 “rs_code”: “S- 115”, 3 “rs_message”: “no data found” 4 }

Get Game List

GET - /api/v2/platform/game/game-list

Display the list of games available for operators to use. In order to keep the information up to date, the operators should regularly get the game list by calling this URL.

Parameters:

Request Example:

1 curl - - location - - request GET ‘http://xyz.pwqr820. com:9003/api/v2/platform/game/game- list’  2 - - header ‘key: {public_key}’  3 - - header ‘operator- name: {operator_name}’

Successful Response Example:

The game_id associated with the game is not the same between the production environment and stage environment. Operators should pay attention when deploying in the production environment.

The availability of games may change based on operational needs. Therefore, operators should dynamically display the list of available games accordingly.

16 | OG OPERATOR API INTEGRATION DOCUMENT

Get Bet Limit List

GET - /api/v2/platform/operator/betlimit

Display the list of available bet limit groups for operators to use. In order to keep up the information, operators should keep updating through calling this endpoint regularly.

Parameters:

Fetch All Bet Limit Sets Request Example:

1 curl - - location - - request GET ‘http://xyz.pwqr820. com:9003/api/v2/platform/operator/betlimit’   2 - - header ‘key: {public_key}’   3 - - header ‘operator-name: {operator_name}’

Fetch Bet Limit Set With Given id Request Example:

1 curl - - location - - request GET ‘http://xyz.pwqr820. com:9003/api/v2/platform/operator/betlimit?id=19683’   2 - - header ‘key: {public_key}’   3 - - header ‘operator-name: {operator_name}’

Successful Response Example:

1 { 2 “rs_code”: “S- 100”, 3 “rs_message”: “success”, 4 “records”: [ 5 { 6 “id”: 109, 7 “min_limit”: 20000, 8 “max_limit”: 200000000 9 } 10 { 11 “id”: 110, 12 “min_limit”: 25000, 13 “max_limit”: 350000000 14 } 15 } 16 }

The id associated with the bet limit is not the same between the production environment and stage environment. Operators should pay attention when deploying in the production environment. Operators can allocate appropriate bet limit groups based on different player requirements.

17 | OG OPERATOR API INTEGRATION DOCUMENT

Enter Game

GET - /api/v2/platform/games/launch

When players access the selected game on the operator’s website, the operator should send a request with necessary information.

Parameters:

Request Example:

1 curl - - location - - request GET ‘http://xyz.pwqr820. com:9003/api/v2/platform/games/launch?player_id=tyrion1&timestamp=1689672707389&nickname= Tyrion&token=f43dcc09- b617- cc14- bdac- 94179d41b038&lang=zh&game_id=1&bextimit=1&signature=6438af1a5f27b82479b774bf3adcb77b’\2 - - header ‘key: {public_key}’\3 - - header ‘operator- name: {operator_name}’

Successful Response Example:

1 {2 “game_link”: “https://live- api- test.oriental- game.com:18088/play?token=f43dcc09- b617- cc14- bdac- 94179d41b038&player_code=428_ tyrion1&currency=CNY&lang=zh&game_code=og- lobby&pool_id=1&bextimit=1&nickname=Tyrion.tsai&timestamp=1689672707389&gameTypes=baccarat%2Cdragontiger%2Cmoneywheel%2Croulette%2Cthreecards%2Cniuniu%2Csicbo%2Csedie&tables=og- lobby&signature=1419c138c35ec48debccdd2eaab1da73”, “rs_code”: “S- 100”, “rs_message”: “success”3 }

Get Player Balance

GET - /api/v2/platform/transfer-wallet/get-balance

The operator requests the chip balance of a specified player.

Parameters:

Request Example:

1 curl - - location - - request GET ‘http://xyz.pwqr820. com:9003/api/v2/platform/transfer- wallet/get- balance?player_id= Tyrion_12345’  2 - - header ‘key: {public_key}’  3 - - header ‘operator- name: {operator_name}’

Successful Response Example:

Player Not Available Response Example:

Get Betting Records

GET - /api/v2/platform/transaction/history

The operator can retrieve the gaming records of affiliated players.

Parameters:

Request Example:

1 curl - - location - - request GET ‘http://xyz.pwqr820. com:9003/api/v2/platform/transaction/transfer- history?fetch_id=1& limit=8000’   2 - - header ‘key: {public_key}’   3 - - header ‘operator- name: {operator_name}’

“records” is JSON array

Successful Response Example:

1 { 2 “rs_code”: “S- 100”, 3 “rs_message”: “success”, 4 “last_fetch_id”: 316, 5 “records”: [ 6 { 7 “fetch_id”: 2247, 8 “player_id”: “xdl24234324ddsfsd”, 9 “transaction_id”: “1005679720000838606123_1”, 10 “game_id”: 13, 11 “round_id”: 567972451, 12 “bet_place”: “p”, 13 “result_url”: “https://og- plus.oss- accelerate.aliyuncs.com/results/20240912/E120240912567972451. html”, 14 “debit_amount”: “10.00”, 15 “credit_amount”: “0.00”, 16 “winlose_amount”: “- 10.00”, 17 “currency”: “CNY”, 18 “secondary_info”: { 19 “balance”: “2188.50”, 20 “bet_amount”: “10.00”, 21 “detain_amount”: “0.00” 22 }, 23 “other_info”: { 24 “ip”: “52.192.117.253”, 25 “result”: “banker,small,banker_bonus”, 26 “browser”: “Safari”, 27 “roundno”: “32- 7”, 28 “game_name”: “baccarat”, 29 “deviceType”: “mobile”, 30 “game_information”: { 31 “bankerCards”: “KC,9h,”, 32 “playerCards”: “10S,3S,” 33 } 34 }, 35 “debit_at”: 1726124784, 36 “rollback_at”: ““, 37”credit_at”: 1726124795, 38 “cancel_at”: ““, 39”resettled_at”: ““, 40”game_name”: “SPEED BACCARAT”, 41 “transaction_type”: “credit”, 42 “remark”: {}, 43 “effective_amount”: “0.50” 44 } 45 } 46 }

No Data Response Example:

1 { 2 “rs_code”: “S- 115”, 3 “rs_message”: “no data found” 4 }

Seamless Wallet

Overview

OverviewSeamless wallet API is composed of two REST APIs, namely Game API and Wallet API.

• Game API: Mainly used for player game records, red limit groups, game jumps and providing game lists. Provided by OG.- Wallet API: Deployed by Operator based on the API specifications provided by OG, allowing OG games to add or subtract players’ balances.

Game API

Get Game List

GET - {{OG_Host}}/api/v2/platform/game/game-list

The operator needs to assign the selected game table to the player in the returned URL. There are various ways to assign the table to the player:

1. Embed the game URL into the website using iframe to start the game2. Open the game URL on the original page3. Open a new tab on the browser to start the game

The game IDs of the production environment and stage environment are different. Operators should pay attention when deploying the production environment. Operators can access corresponding games according to their needs.

Parameters:

Request Example:

1 curl - - location - - request GET ‘http://xyz.pwqr820. com:9003/api/v2/platform/game/game- list’  2 - - header ‘key: {public_key}’  3 - - header ‘operator- name: {operator_name}’

23 | OG OPERATOR API INTEGRATION DOCUMENT

Response Example:

1 { 2 “rs_message”:“success”, 3 “rs_code”: “S- 100”, 4 “records”: [ 5 { 6 “game_id”: 1, 7 “game_type”: “Live Game”, 8 “game_name”: “og- lobby” 9 “image”: “https://live- test.oriental- game.com/ogplus/login/img_logoPlus.png”, 10 “vendor_name”: “og” 11 1 12 { 13 “game_id”: 28, 14 “game_type”: “Live Game”, 15 “game_name”: “P1_baccarat” 16 “image”: “https://og- plus.oss- cn- hongkong.aliyuncs.com/v6/dealer/blue/aedrt.png”, 17 “vendor_name”: “og” 18 1 19 1 20 }

Get Bet Limit List

GET - {{OG_Host}}/api/v2/platform/operator/betlimit

The bet limit IDs of the production environment and stage environment are different. Operators should pay attention when deploying the production environment. Operators need to select the minimum/maximum bet limit suitable for the player and use it when the player logs in to the game.

Parameters:

Requesting All Bet Limit Example:

1 curl - - location - - request GET ‘http://xyz.pwqr820. com:9003/api/v2/platform/operator/betlimit’  2 - - header ‘key: {public_key}’  3 - - header ‘operator- name: {operator_name}’

Requesting a Single Bet Limit Example:

1 curl - - location - - request GET ‘http://xyz.pwqr820. com:9003/api/v2/platform/operator/betlimit’  2 - - header ‘key: {public_key}’  3 - - header ‘operator- name: {operator_name}’  4 - - data- raw ‘{ 5 “id”: “1” 6 }’

Successful Response Example:

Enter Game

GET - {{OG_Host}}/api/v2/platform/games/launch

When a player wants to log in to the game, the operator needs to provide relevant requests that match the player’s information. OG will use {{Operator_Host}}/api/v2/operator/security/authenticate to confirm that the player is legitimate.

Parameters:

Request Example:

curl - - location - - request GET ‘http://xyz.pwqr820. com:9003/api/v2/platform/games/launch?player_id=test2&timestamp=1689532295&nickname=Tyrion.tsai&token=9NO2_OG8q&lang=zh&game_id=1&signature=12510b8cad931a6efe10c7d580bf7892&betlimit=85’ * header key: {public key} - - header ‘operator- name: {operator_name}’

Successful Response Example:

1 { 2 “rs_code”: “S- 100”, 3 “rs_message”: “success” 4 “game_link”: “https://live- api.oriental- game.com:18088/play?token=235e09eb- 6941- 4c14- 8d7e- 17b8ff2a9094 Mobile IDR&player code=test2&currency=IDR&lang=id&game_code=og- lobby&pool_id=1&betlimit=30 9&nickname=Hnrico&timestamp=1689532005&tables=og- lobby%2CC12%2CG10%2CP1%2CP2%2CP7%2CP17%2CP19%2CP20%2CM1%2CM2%2CM3%2CM5%2CM6%2CM7%2CM8%2Cm88 lobby&gameTypes=baccarat%2Cblackjack%2Cdragonti ger%2Cfantan%2Ckeno%2Cmoneywheel%2Cniuniu%2Croulette%2Csedie%2Csicdb%2Cthreecards&signature=fdc7804cc1 5 8f817f41c2f0f8fd7cfe58” 1

Get Betting Records

GET - /api/v2/platform/transaction/history

Operator can use this function to fetch player’s betting records.

Parameters:

Request Example:

curl - - location - - request GET ‘http://xyz.pwqr820. com:9003/api/v2/platform/transaction/history?fetch_id=1&limit=8000&game_type_id=1’  - - header ‘key:{public_key}’  - - header ‘operator- name:{operator_name}’

Successful Response Example:

1 { 2 “rs_code”: “S- 100”, 3 “rs_message”: “success”, 4 “last_fetch_id”: 316, 5 “records”: [ 6 { 7 “fetch_id”: 316, 8 “player_id”: “Ashu_test001”, 9 “transaction_id”: “1005545960000767179713_1”, 10 “game_id”: 13, 11 “round_id”: 554596470, 12 “bet_place”: “p”, 13 “result_url”: “https://og- plus.oss- accelerate.aliyuncs.com/results/20240526/E120240526554596470. html”, 14 “debit_amount”: “10.00”, 15 “credit_amount”: “0.00”, 16 “winlose_amount”: “- 10.00”, 17 “currency”: “CNY”, 18 “secondary_info”: { 19 “balance”: “337.16”, 20 “bet_amount”: “10.00”, 21 “detain_amount”: “0.00” 22 }, 23 “other_info”: { 24 “ip”: “61.245.19.169”, 25 “result”: “banker,super_jsix,big,banker_bonus”, 26 “browser”: “Edge”, 27 “roundno”: “28- 26”, 28 “game_name”: “baccarat”, 29 “deviceType”: “desktop”, 30 “game_information”: { 31 “bankerCards”: “2S,4D”, 32 “playerCards”: “JC,10C,AS” 33 } 34 }, 35 “debit_at”: 1716708750, 36 “rollback_at”: ““, 37”credit_at”: 1716708769, 38 “cancel_at”: ““, 39”resettled_at”: ““, 40”game_name”: “SPEED BACCARAT”, 41 “transaction_type”: “credit”, 42 “remark”: }, 43 “effective_amount”: “10.00” 44 } 45 } 46 }

No data response:

1 { 2 “rs_code”: “S- 115”, 3 “rs_message”: “no data found” 4 } 5 - - header ‘key: {public_key}’   6 - - header ‘operator- name: {operator_name}’

Verify Player Information

POST - {{Operator_Host }}/api/v2/operator/security/authenticate

When a player enters the game, OG will call this API. The operator is required to verify the accuracy and existence of the player’s information. Upon successful verification, the API will return the necessary response parameters to OG, and the player will be directed to the selected game.

Parameters:

Request Example:

1 curl - - location - - request POST ‘http://xyz.pwqr820. com:9003/api/v2/operator/security/authenticate’   2 - - header ‘key: {public_key}’   3 - - header ‘operator- name: {operator_name}’   4 - - data- raw ‘{ 5 “player_id”: “tester2”, 6 “timestamp”: 1645771135235, 7 “token”: “7a66ec6ecd1e27da02ba565b9c982db9”, 8 “signature”: “12510b8cad931a6efe10c7d580bf7892” 9 }’

28 | OG OPERATOR API INTEGRATION DOCUMENT

Successful Response Example:

1 { 2 “rs_message”: “success”, 3 “rs_code”: “S- 100”, 4 “player_status”: “activate”, 5 “token”: “7a66ec6ecd1e27da02ba565b9c982db9” 6 }

Get Player Balance

GET - {{Operator_Host }}/api/v2/operator

Requested when a player’s balance needs to be confirmed. The operator needs to provide the player’s balance to OG.

Parameters:

Request Example:

1 curl - - location - - request GET ‘http://operator- domain/api/v2/operator/player/balance?player_id=tester2&timestamp=1645771135235&signature=12 510b8cad931a6efe10c7d580bf7892’

Successful Response Example:

29 | OG OPERATOR API INTEGRATION DOCUMENT

Bet Debit Process

POST - {{ Operator_Host }}/api/v2/operator/transaction/bulk/debit

This API is called when a player places a bet. Players can bet on multiple betting areas at the same time. Each betting area has a corresponding bet transaction number. The operator needs to deduct the player’s betting amount and return the player’s latest amount at the same time.- The bet transaction number of each bet is a unique value. The operator needs to confirm that this bet transaction number has not been processed before deducting the player’s quota.- If one of the bets in the multi- bet fails, all bets in the entire multi- bet will be treated as failed. The operator needs to return the corresponding result according to the setting of the parameter code table.

Parameters:

Request Example 1: other_info is an empty array

Request Example 2: The order of other_info values is: device type, ip, browser

1 curl - - location - - request POST ‘http://xyz.pwqr820. com:9003/api/v2/operator/transaction/bulk/debit’  2 - - data- raw ’{ 3 “player_id”: “tester2”, 4 “timestamp”: 1689539717, 5 “total_amount”: “30000.00”, 6 “transaction_type”: “debit”, 7 “game_id”: 44, 8 “round_id”: “530539663”, 9 “currency”: “KRW”, 10 “called_at”: 1689539717, 11 “signature”: “80c56648940f9e4dfa85059702a615fb” 12 “records”: [ 13 { 14 “amount”: “10000.00”, 15 “transaction_id”: “16053053900005407381781”, 16 “bet_place”: “tie”, 17 “secondary_info”: { 18 “bet_amount”: “10000.00”, 19 “detain_amount”: “0.00” 20 } 21 “other_info”: { 22 “desktop”, 23 “115.238.108.2”, 24 “Safari” 25 } 26 “remark”: { 27 } 28 { 29 “amount”: “20000.00”, 30 “transaction_id”: “14053053900005407381791”, 31 “bet_place”: “d”, 32 “secondary_info”: { 33 “bet_amount”: “20000.00”, 34 “detain_amount”: “0.00” 35 } 36 “other_info”: { 37 “desktop”, 38 “115.238.108.2”, 39 “Safari” 40 } 41 “remark”: { 42 } 43 ] 44 }

Seamless Wallet API Wallet API: Bet Debit Process And Bet Payout Credit Process

Successful Response Example:

1 { 2 “rs_code”: “S- 100”, 3 “rs_message”: “success”, 4 “player_id”: “3547487040”, 5 “total_amount”: “30000.00”, 6 “updated_balance”: “2180000.00”, 7 “billing_at”: “1689539718”, 8 “records”: “{\”amount\“\10000.00\”_id\“\16053053900005407381781},\”amount\“\20000.00", \”transaction_id\“\14053053900005407381791}}] 9 }

Bet Payout Credit Process

POST - {{ Operator_Host }}/api/v2/operator/transaction/credit

This API is called when the game ends Each bet transaction is unique. The operator needs to confirm that this bet transaction has not been processed yet before returning the player’s credit.

Parameters:

Request Example:

1 curl - - location - - request POST ‘http://xyz.pwqr820. com:9003/api/v2/operator/transaction/credit’  2 - - data- raw ’{ 3 “player_id”: “tester2”, 4 “timestamp”: 1689540272, 5 “amount”: “0.00”, 6 “effective_amount”: “10000.00”, 7 “winlose_amount”: “- 10000.00”, 8 “transaction_id”: “16053054000005407408561”, 9 “transaction_type”: “credit”, 10 “round_id”: “530540003”, 11 “game_code”: “P7”, 12 “game_id”: 33, 13 “bet_place”: “tie”, 14 “result_url”: “https://og- plus.oss- accelerate.aliyuncs.com/results.html”, 15 “currency”: “KRW”, 16 “secondary_info”: {}, 17 “other_info”: {}, 18 “remark”: {}, 19 “called_at”: 1689540272, 20 “signature”: “0c0d2781a8b9b07a152560d8a46347b2” 21 }

Successful Response Example:

1 { 2 “rs_code”: “S- 100”, 3 “rs_message”: “success”, 4 “player_id”: “tester2”, 5 “amount”: “0.00”, 6 “transaction_id”: “16053054000005407408561”, 7 “updated_balance”: “1610000.00”, 8 “billing_at”: 1689540273157 9 }

Seamless Wallet API Wallet API: Cancellation Process After Placing A Bet

Cancellation Process After Placing A Bet

POST - {{Operator_Host}}/api/v2/operator/transaction/bulk/debit

This API will be requested when the bet fails to initiate a rollback of the debit transaction.

The operator is responsible for verifying whether the request has not been previously processed before making adjustments to the player’s balance.

Once confirmed, the operator should proceed to return the money back to the player’s balance. Upon successful completion, the operator is expected to return the updated balance of the player.

Parameters:

Request Example:

Seamless Wallet API Wallet API: Cancellation Process After Placing A Bet

Request Example:

Successful Response Example:

1 { 2 “rs_code”: “S- 100”, 3 “rs_message”: “success”, 4 “player_id”: “tester2”, 5 “total_amount”: “30000.00”, 6 “updated_balance”: “2180000.00”, 7 “billing_at”: “1689253494”, 8 “records”: “[\”\25000.00\”_id\”\5005303560000538238639_1”，\”\”\5000.00", \”_id\”\50053035600005382386321”]”] 9 }

36 | OG OPERATOR API INTEGRATION DOCUMENT

Seamless Wallet API Wallet API: Cancellation Process After Getting A Payout

Cancellation Process After Getting A Payout

POST - {{Operator_Host}}/api/v2/operator/transaction/bulk/credit

This API will be requested when the payout amount needs to be taken back.

The operator is responsible for verifying whether the request has not been previously processed before making adjustments to the player’s balance.

Once confirmed, the operator should proceed to deduct the payout amount back from the player’s balance. Upon successful completion, the operator is expected to return the updated balance of the player.

Parameters:

Request Example:

Seamless Wallet APIWallet API: Cancellation ProcessAfter Placing A Bet

Request Example:

“other_info”: {}, “remark”: {}, “called_at”: 1689540272, “signature”: “0c0d2781a89507a1525608a46347b2” }

Successful Response Example:

1 { 2 “rs_code”: “S- 100”, 3 “rs_message”: “success”, 4 “player_id”: “tester2”, 5 “total_amount”: “30000.00”, 6 “updated_balance”: “2180000.00”, 7 “billing_at”: “1689253494”, 8 “records”: [“":”25000.00", _id": “5005303560000538238639_1”}, ": “5000.00", _id": “50053035600005382386321}]” 9 }

Resettle Process

POST - {{Operator_Host}}/api/v2/operator/transaction/bulk/credit This API will be requested when the bet needs to be resettled.

The operator is responsible for verifying whether the request has not been previously processed before making adjustments to the player’s balance.

Once confirmed, the operator should proceed to deduct the payout amount back from the player’s balance. Upon successful completion, the operator is expected to return the updated balance of the player.

Parameters:

Request Example:

Seamless Wallet APIWallet API: Cancellation ProcessAfter Placing A Bet

Request Example:

“other_info”: {}, “remark”: {}, “called_at”: 1689540272, “signature”: “0c0d2781a895b07a1525608a46347b2” }

Successful Response Example:

1 { 2 “rs_code”: “S- 100”, 3 “rs_message”: “success”, 4 “player_id”: “tester2”, 5 “total_amount”: “30000.00”, 6 “updated_balance”: “2180000.00”, 7 “billing_at”: “1689253494”, 8 “records”: [“amount":”25000.00\“_id":“5005303560000538238639_1”},\“":”5000.00", \“_id":“50053035600005382386321"}] 9 }

Promotions

POST - {{Operator_Host }}/api/v2/operator/transaction/reward

This API will be requested when there is a promotion

Parameters:

Request Example:

1 curl - - location - - request POST ‘http://xyz.pwqr820. com:9003/api/v2/operator/transaction/reward’  2 - - data- raw ‘{ 3 “player_id”: “tester2”, 4 “timestamp”: 1689540272, 5 “amount”: “200.00”, 6 “transaction_id”: “1605305400000540740856”, 7 “game_code”: “P1”, 8 “game_id”: 33, 9 “round_id”: “530540003”, 10 “result_url”: “https://og.plus.os- accelerate.aliyuncs.com/results.html”, 11 “currency”: “KRW”, 12 “secondary_info”: {}, 13 “other_info”: {}, 14 “remark”: {}, 15 “called_at”: “1689540272, 16”signature”: “0c0d2781a8b9b07a152560d8a46347b2” }’

Successful Response Example:

1 { 2 “rs_code”: “S- 100”, 3 “rs_message”: “success”, 4 “player_id”: “tester2”, 5 “amount”: “200.00”, 6 “transaction_id”: “1605305400000540740856”, 7 “updated_balance”: “7800.00”, 8 “billing_at”: 1689540272 9 }

ComparisonTable

OG Betting Record Parameter Comparison Table

Baccarat (including: ordinary baccarat, commission-free baccarat, speed baccarat)

Dragon Tiger (including: classic dragon tiger, new dragon tiger)

Niuniu

Sedie

Money Wheel

ThreeCards

Sicbo

Roulette

Sports

Other Info Parameter

Bet List Parameter List*

Sportsbet_selection_status*

• The operator needs to set the return of each corresponding message on the wallet API.- E-000 means the format of the API request is wrong.- S-000 means that some parameters in the API request are incorrectly set.- If the operator cannot find suitable return content in the following returns, please use E-000 or S-000.- When the operator receives a return message of S-106, it means that the game has not been opened. Please contact customer service personnel to handle it.- All return messages need to be set according to the following table

Live GameSuggested GameArrangement

Suggested Game Arrangement

We strongly suggest the game arrangement as follows:

Images can be downloaded here: https://docs.google.com/spreadsheets/d/19- 42h3t9Q7fw3UeknEEA- GdhqTc_N9tfEIDV3cVLI7s/edit?gid=1074503219#gid=1074503219