Appearance
Providers and settings
The brand-level controls behind payments: which providers are available, the manual bank accounts players pay into, the master switches for deposit and withdrawal methods, and the per-player blocks. Day-to-day crediting and withdrawal review live on their own pages — Crediting and debiting a player and Reviewing withdrawals.
Providers
The platform routes deposits and withdrawals through a set of integrated providers, plus manual bank transfer. Which ones a given player sees depends on the brand, the player's currency and country, and the master switches below.
| Provider | Kind | Notes |
|---|---|---|
| PayZeasy | Fiat and crypto, multi-method | QR, UPI, IMPS and intent-based methods; India-facing |
| YumGo | Fiat gateway | Multi-method, multi-currency |
| AlphaPo | Crypto | Deposits and payouts |
| TektikPay | Fiat | Turkish market (TRY) |
| Banco SANTS | Fiat, regional | Latin America, including PIX |
| SANS GetirSin | Fiat and crypto | — |
| Manual bank transfer | Bank transfer | Operator-confirmed; see below |
This list reflects the integrations present in the code
Which of these a brand actually runs, and the commercial terms behind each, are configured per brand and not derivable from the platform alone. Treat this as the set that can be enabled, not the set that is enabled for your brand. Provider-level method lists, callbacks and fees are not documented in this handbook.
Master switches for methods
Brand-wide, deposits and withdrawals can each be turned on or off by broad category:
| Deposits | Withdrawals |
|---|---|
| Crypto on/off | Crypto on/off |
| Local-currency (fiat) on/off | Local-currency (fiat) on/off |
| Manual bank on/off | — |
These are the master switches. Turning a category off removes it for every player on the brand, regardless of provider or individual settings. Reach for these when a method needs to go dark platform-wide; use per-player controls below for one account.
Manual bank accounts
Manual bank transfer needs at least one brand bank account for players to pay into. Each account holds:
- Bank name, and the account details — account number, account holder and IFSC code. The three sensitive fields are stored encrypted.
- Currency — the currency this account accepts.
- Deposit and withdrawal minimum and maximum amounts — checked when a player transacts. The maximum of each pair must be at or above its minimum.
- Instructions shown to the player, a display order, and an active switch.
Only active accounts are offered to players. An account is removed by a soft delete, which also deactivates it, rather than being erased — so it stays available for the history of past transfers.
Creating, viewing, editing and deleting these accounts are each gated by their own manual-bank management permission. See Roles and access.
Per-player controls
Independently of the brand-wide switches, a single player can be blocked from depositing, withdrawing, or both, from their restrictions. Use this for one account — a player under investigation, a self-exclusion, a support hold — without touching anyone else.
A per-player block and a master switch are different tools: the master switch takes a method away from the whole brand; the per-player block takes deposits or withdrawals away from one person across all methods. Reach for the narrower one first.
Not yet documented
Per-player payment limits — as opposed to outright blocks — and how they interact with the account-level minimums and maximums above have not been written up. If you need them, ask the team that set up your brand.
Permissions at a glance
| Capability | Roughly who |
|---|---|
| Credit a player (deposit) | Finance, senior support |
| Debit a player (manual withdrawal) | Finance |
| Approve / reject withdrawals and manual bank requests | Finance |
| Manage manual bank accounts | Finance / admin |
| Change master payment switches | Admin |
The exact permission-to-role mapping is set per brand. See Roles and access for how access works and how to request a change.