Priority markets
Payment needs
- Low-friction app checkout for rides, delivery orders, bookings, deposits, cancellation fees, tips, wallet top-ups, and refunds.
- Local wallets, QR payments, instant bank transfers, cards, mobile money, payment links, and in-person fallback routes through approved PSP, acquirer, gateway, or wallet-operator integrations.
- Payouts to drivers, couriers, service providers, restaurants, merchants, or fleet partners with separate verification for payout rails and sub-merchant onboarding.
- Real-time order-state handling for authorized, pending, failed, cancelled, partially refunded, disputed, tipped, and split transactions.
- Reconciliation across customer ID, order ID, worker/provider ID, location, route, merchant, platform fee, tip, refund, payout, country, currency, FX, and settlement batch.
Recommended route categories
- Evaluate app-ready PSPs and gateways for customer checkout, then separately evaluate payout providers or marketplace payment features for worker and merchant disbursements.
- For Southeast Asia, compare wallet and QR acceptance through PSP, wallet-operator, and gateway routes rather than assuming every wallet has direct platform onboarding.
- For Africa, verify mobile money collection and disbursement through licensed operators, PSPs, or aggregators that support business use cases.
- For Latin America, compare instant transfer, cash collection, wallet, local card, and payment-link routes, with clear rules for pending or failed payments.
- If there is no local entity, ask whether the platform can onboard as a foreign merchant and whether driver, courier, restaurant, or service-provider payouts require local licensing, tax registration, or bank accounts.
Provider selection questions
- Do you support mobility, delivery, rentals, local services, tips, cancellation fees, deposits, split payments, and worker or merchant payouts?
- Which checkout methods are available through your PSP, acquirer, gateway, wallet-operator, or mobile-money route in each market?
- Which payout methods are available for drivers, couriers, restaurants, service providers, or fleet partners, and what KYC/KYB is required?
- Can webhooks and reports carry order ID, customer ID, provider ID, location, platform fee, tip, refund, payout status, country, currency, FX, and settlement batch?
- How do you handle fraud, account takeover, disputed rides/orders, refunds, chargebacks, negative balances, reserves, and support escalation?
Risk and compliance notes
- On-demand platforms combine consumer checkout, platform balances, tips, refunds, and worker payouts, so provider review can be closer to marketplace or payment-facilitator underwriting than simple ecommerce.
- Cash, wallet, QR, and mobile-money availability must be verified through provider routes; do not present payment methods as direct merchant accounts.
- Stored value, driver wallets, instant payouts, tips, and multi-party settlement may raise licensing, tax, labor, and AML questions.
- For Russia, Venezuela, and Myanmar, publish only risk warnings and do not recommend specific onboarding paths.
Suggested internal links
- /en/knowledge-center/payment-gateway-vs-payment-aggregator-vs-local-acquirer/
- /en/knowledge-center/mobile-money-payments-in-africa-how-merchants-get-paid/
- /en/knowledge-center/qr-code-payments-in-southeast-asia/
- /en/knowledge-center/refund-dispute-questions/
- /en/countries/indonesia/
- /en/countries/kenya/
- /en/payment-channels/qris/
- /en/payment-channels/m-pesa/