Skip to main content

Non-Seamless Transfer Wallet Integration

In the non-seamless (transfer wallet) model, the player's funds are transferred between the operator wallet and the PHL wallet. The operator launches the game via API_001 Player Login, tops up / withdraws with API_006 Transfer Player Balance, and periodically synchronizes betting records from PHL.

Launch Game Flow​

Figure 1: Transfer Wallet Integration Overview
Figure 1: Transfer Wallet Integration Overview

Get Transactions Flow​

Fetch Outstanding Transactions​

Generally, operator would leverage on API_007 Get Transaction Records to fetch outstanding transactions and API_008 Remove Transaction Records to update provider side that the particular records are all synced.

Fetch Settled Transactions​

Operator would leverage on API_009 Get Settled Transaction Records to fetch settled transactions and API_010 Remove Settled Transaction Records to update provider side that the particular records are all synced.

Polling pattern

Both "get" APIs return the earliest 1000 records (configurable) in ascending time order. Always call the matching "remove" API after you have persisted the fetched records, otherwise the same earliest records are returned on every call.