Skip to main content
ZBD detects a player’s country automatically from their IP address. This determines which payout options they see and what withdrawal limits apply. In most cases this works correctly — but there are situations where you’ll need to override it manually:
  • A player is using a VPN and their detected country is wrong
  • A player is traveling and their IP doesn’t match their home country
  • A player is in an unsupported region but you want to whitelist them for testing
  • Your QA team needs to test from a region other than their own
Use this page for those cases. Access it via dashboard.zbdpay.com under SDK User Support.

Find a player

Search by any of the following:
  • rewardsUserId — the player’s SDK identifier, returned by GetUserStatus. Loads the player directly.
  • Support ID — a player-facing identifier shown in the ZBD modal, used when a player contacts your support team.
  • Gamertag — the player’s ZBD gamertag.
Click Load Data to search. The User Data card shows the player’s withdrawal limit, rewards balance, detected country, and transaction history.

Change country code

Override a player’s detected country — for example if their IP is flagged incorrectly due to a VPN or proxy, or if they’re traveling.
  1. Click Change next to the country code field
  2. Search for the correct country
  3. Click Save
Changing a player’s country code affects their payout options and withdrawal limits immediately. Only override when you’re confident the detected country is incorrect.

Whitelist a player

Whitelisting allows a specific player to access your rewards program from a region that would otherwise be blocked — for example, a member of your QA team based in an unsupported country.
  1. Go to the Whitelist User card below the SDK User ID card
  2. Enter the player’s Support ID
  3. Select the Rewards App Name tied to that Support ID
  4. Click Whitelist
Whitelisting bypasses regional restrictions for that player only. Use it for testing and support purposes, not as a general workaround for regional coverage. See the coverage page for the full list of supported regions.