Isolated per currency
Endpoints are split by currency, so a problem in one currency stays in that currency.
Home/Technology
Three callbacks,
and a round is done.
Launch, debit, credit. However many providers you use, these are the only three requests your system receives. Below is what HIGHEND ASIA does in between, limited to what you can verify.
Round trip
How a round flows
Based on seamless wallet. Your wallet talks only to HIGHEND ASIA, and we reconcile each provider's spec in the middle.
OperatorOperator wallet
Asia HubHIGHEND
ProviderGame provider
Operator wallet · USD1,000.00
LAUNCHBETSETTLE
The highlighted box is the side receiving the current request. The operator wallet balance changes the moment each callback arrives.
wallet-callback.log · USD
- — LAUNCH
- →
POST /game/launchOperator requests game launch - →
POST /sessionConverted to provider spec, session created - ←
200 game_urlProvider returns launch URL - ←
200 game_urlGame opens on operator site - — BET
- ←
bet 5.00Bet placed at provider - ←
POST /wallet/usd/debitDebit callback to operator wallet - →
200 balanceBalance returned after debit - →
200 okResult passed to provider - — SETTLE
- ←
win 12.50Provider settles the result - ←
POST /wallet/usd/creditCredit callback to operator wallet - →
200 balanceBalance returned after credit - →
200 okRound complete
Wallet modes
Seamless by default
We integrate a seamless wallet by default, with no balance transfers. If your wallet structure is hard to change, talk to us first about the transfer model.
| Item | SeamlessDefault | TransferBy agreement |
|---|---|---|
| Where player balance lives | Operator wallet. HIGHEND ASIA only relays callbacks. | Provider wallet during play. Moved on entry and exit. |
| What the operator builds | Balance, debit and credit callbacks | Deposit and withdrawal requests |
| When balance updates | Instantly, on every bet | On transfer |
| Adding a currency | One more per-currency endpoint. | Wallet setup grows per provider. |
| Best fit | Running many providers on one wallet | When your current wallet structure can't change soon |
Specification
Technical specs
What dev teams ask before the first meeting, answered up front.
- Wallet
- Seamless callbacks — balance, debit, credit
- Endpoint
- A separate endpoint per currency, with distinct stage and production URLs.
- Currency
- MNT · JPY · CNY · PHP · VND · MYR · THB · TWD · HKD · USD · USDT. Varies by provider support.
- Access
- API calls are accepted only from registered IPs.
- Environment
- Stage and production are separate. Same spec, different URLs and keys.
- Test
- Review runs real games on the stage site with test accounts.
- Back office
- Back office accounts are split into Full · Reports · Support permissions.
- Report
- Settlement data from each provider, consolidated by currency and provider.
Reliability
Reliability and security
Instead of certification badges, here's what we actually do.
Allowed IPs only
On both the operator and provider side, we process only requests from registered addresses.
Role-based accounts
The back office is split into Full, Reports and Support permissions, so you grant only what's needed.
Stage first
New providers and spec changes reach production only after passing stage review.
Every callback logged
Each debit and credit callback is logged individually, so in a dispute we both look at the same record.
Incidents shared immediately
We report the cause, impact and recovery time as soon as we confirm them.