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.

Wallets

The 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 rails

Account-based deposits and transfers

Consider market reach, confirmation timing, bank coverage, refunds, and whether the rail can support approved withdrawals.

UPI and QR

Intent, 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 availability

Fit 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.

Payouts

A 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.

Method scorecard

Every method is evaluated in both directions.

Payment method evaluation criteria
DecisionDepositPayout
EligibilityCan the player and operator use it?Can funds return to an approved destination?
State modelPending, approved, failed, reversedRequested, held, approved, sent, returned
OperationsRetry, support, dispute, refundReview, release, failure, reconciliation
CommercialsProcessing, method, conversionPayout, transfer, conversion

Currency and settlement

Acceptance is not the same as settlement.

The player may pay in one currency while processing, conversion, balance reporting, and settlement happen in another. The route design documents the currency the player pays in, the currency the route settles in, conversion ownership, fees, and reconciliation references. A settlement is requested from the merchant account rather than pushed on a fixed timetable, and no holds or rolling reserves sit against the balance in the meantime.

No currency or market is promised until the operating entity, licence position, payment partners, and commercial terms have been reviewed.

Build a payment method mix around real player behavior.

Share your operating model, markets, methods, and payout needs. We will use them to scope eligibility and the technical route.

Request gateway access