Payment methods / market fit
Local choice without a fragmented cashier.
Method coverage is planned by player market, currency, operating model, deposit behavior, refund support, payout destination, commercial terms, and provider approval.
WalletsThe cashier a player already recognizes.
In the markets this platform covers, the default is a wallet the player opens every day — bKash and Nagad in Bangladesh, JazzCash and Easypaisa in Pakistan, eSewa and Khalti in Nepal, M-Pesa in Kenya. Evaluate each on redirect behavior, repeat use, per-route limits, and whether it also supports approved withdrawals.
Bank railsAccount-based deposits and transfers
Consider market reach, confirmation timing, bank coverage, refunds, and whether the rail can support approved withdrawals.
UPI and QRIntent, QR, link and push
UPI alone comes in several shapes in India, and scan-to-pay QR appears again as Bangla QR, FonePay and LKR QR. Assess in-flow experience, currency handling and duplicate protection.
Live availabilityFit before count
A smaller market-relevant mix beats a long global logo wall. Availability and per-route floors and ceilings are published by the platform and change, so read them rather than hardcode them.
PayoutsA second integration, not a button
Withdrawals never run through a hosted cashier page. Map approved payout routes, account ownership checks, operator-side review, rejection, release, and the notification that confirms the money left.