Pay, balances and withdrawals
Identify the recipient, select a package, then review and pay.
The three-step recharge flow
- Identify or authorize the account using a mode enabled by the operator.
- Choose the country/currency and an available package.
- Review the recipient and total, then continue through the configured payment channel.
Recipient options
Pay supports an application-code route, app QR approval and optional direct public-ID recharge. The administrator chooses which modes to offer. Direct ID shows the recipient’s public name, ID, photo and supported frame; it does not reveal their balance, password or private conversations.
The recipient receives an official notification identifying the recharge route. If a direct-ID recharge is unrecognized, contact the operator before spending it. Detailed authorization setup remains in the private manual.
Purchase channels
Android native purchases use Google Play billing; iOS native purchases use App Store billing. The web wallet and Pay use the enabled web payment integrations. Store products, package mappings, provider accounts and actual payment verification are separate configuration tasks.
A provider redirect or a success message alone is not the final source of account credit. Review the transaction record and confirmed account balance. Unsupported or unconfigured methods should not be presented as ready to purchase.
Diamonds, earnings and statements
Diamonds support gift spending. Earnings and coin conversion follow the operator’s configured rules, with available and held amounts shown separately where applicable. Statements let users and permitted staff trace the relevant financial operations.
Withdrawal requests have their own review and processing flow. Current Pix/PayPal payout processing is simulated/manual, not automatic real-money payout. The operator remains responsible for the actual settlement and its records.
Demonstration behavior
Fixed demonstration accounts have a simulated 100,000-diamond balance that does not increase or decrease. Newly registered demo accounts have separate demo rules. This does not describe a buyer’s real wallet or payment settlement. See Demo versus your installation.
Web gateway coverage in this release
| Configured country | Web / Pay gateway options |
|---|---|
| Brazil | Mercado Pago and Stripe |
| United States, France and Italy | Stripe and PayPal |
| India | Razorpay and Cashfree |
These are the application’s configured channel options, not a guarantee that a provider will approve every merchant or transaction. Provider availability, currency, account permissions and live activation still need to match your business. Native app purchases remain separate store flows.