Skip to main content

Seamless Wallet Integration

In the seamless model, the player's balance stays in the operator wallet. PHL invokes a set of operator-hosted callback endpoints (getBalance, placeBet, cancelBet, settle) on a callbackURL registered by the operator.

Launch Game Flow​

Figure 2: Seamless Wallet Integration Overview
Figure 2: Seamless Wallet Integration Overview

Retry Mechanism(s)​

Following describes the retry mechanism of seamless wallet API.

Cancel Bet​

Figure 3: Cancel Bet Overview
Figure 3: Cancel Bet Overview

Trigger Point(s)​

Scenario where cancel bet will be triggered:

  • Cancel Bet request timeout.
  • Cancel Bet not returning HTTP status code 200 or code 8000.
  • Game cancellation.

Frequency​

  • System to retry to continue send cancel bet request every 5 minutes for 3 hours.
  • Manual processing required after 3 hours if still failing.

Exit Criteria(s)​

  • When cancel bet is return HTTP code 200 and code = 8000.
  • Retry more than 3 hours.

Settle​

Figure 4: Settle Overview
Figure 4: Settle Overview

Trigger Point(s)​

Scenario where settle retry will be triggered:

  • Settle request timeout.
  • Settle not returning HTTP status code 200 or code 8000.

Frequency​

  • System to retry to continue send settle request every 5 minutes for 3 hours.
  • Manual processing required after 3 hours if still failing.

Exit Criteria(s)​

  • When Settle return HTTP code 200 and code = 8000.
  • Retry more than 3 hours.

Environment​

Base URL​

  • https://prod.phl8268.com/panel/api/integration

API Secret Key​

  • API Secret Key will be given to invoke PHL endpoints.