Skip to content

Fund Transfer

Transfer funds into or out of a player's wallet on the game provider.

Endpoint

PropertyValue
PathPOST /papi/v1/player/transfer
AuthAgent Token (Bearer)

Request Parameters

ParameterTypeRequiredDescription
providerstringYesProvider identifier
operator_codestringYesOperator code
currencystringYesCurrency code
usernamestringYesPlayer username
amountdecimalYesTransfer amount (positive = deposit, negative = withdraw)
transfer_idstringYesUnique transfer ID (idempotency control)
transfer_typestringYesTransfer type: deposit / withdraw

Request Example

json
{
  "provider": "BG",
  "operator_code": "OP001",
  "currency": "CNY",
  "username": "player_001",
  "amount": 500.00,
  "transfer_id": "TXN20260326001",
  "transfer_type": "deposit"
}

Response Fields

FieldTypeDescription
transfer_idstringTransfer ID
usernamestringPlayer username
amountdecimalActual transfer amount
balance_beforedecimalBalance before transfer
balance_afterdecimalBalance after transfer
statusstringTransfer status: success / failed / pending

Response Example

json
{
  "code": 0,
  "message": "success",
  "data": {
    "transfer_id": "TXN20260326001",
    "username": "player_001",
    "amount": 500.00,
    "balance_before": 1000.00,
    "balance_after": 1500.00,
    "status": "success"
  },
  "timestamp": 1711411200000,
  "request_id": "req_ghi789"
}

Seamless Wallet Mode

SA and WM use Seamless wallet mode where fund changes are handled automatically via provider callbacks. Manual transfer calls are generally not needed. BG and GSC support active transfer mode.

Provider Mapping

ProviderAPINotes
BGopen.operator.user.transferJSON-RPC 2.0, positive = deposit / negative = withdraw
GSCseamless/withdraw + seamless/depositSeparate APIs, withdraw = deduction, deposit = credit
SASeamless wallet modeHandled via callbacks, no manual transfer needed
WMSeamless wallet modeHandled via Webhook pointInout

VCT Gaming Integration Platform