← Back to industry scenarios

Industry scenario

Mobility, delivery and on-demand services payment route checklist

How should a ride-hailing, delivery, local services, rental, or on-demand platform evaluate local payments and worker payouts?

Priority markets

Merchant entry sequence

  • Map customer payment, dispatch timing, cancellation, tip, refund, partner payout, and chargeback flows before selecting providers.
  • Group markets by mobile wallet, QR, bank-transfer, card, and cash-adjacent expectations using the input country candidates.
  • Ask providers to review on-demand risk, partner payout needs, delayed confirmation, refund rules, and reporting fields.
  • Test order acceptance, payment failure, cancellation fee, tip adjustment, partial refund, and payout reconciliation.
  • Keep method labels conservative until operational tests show the route works for the live flow.

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 provider-confirmed 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 provider-confirmed 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

  • Will you review mobility, delivery, and on-demand services for the merchant's exact product model, content category, entity, and buyer countries before integration work starts?
  • Which of the priority markets can be evaluated first for this use case: Brazil, Mexico, India, Indonesia, Philippines?
  • Can the current merchant entity apply for each target country, or should we evaluate a local PSP, global PSP, acquirer, gateway, wallet operator, or merchant-of-record style route?
  • Which customer-facing methods can be considered for one-time payments, recurring payments, payment links, invoices, refunds, and failed-payment recovery in this category?
  • What documents, website disclosures, product descriptions, prohibited-category checks, and compliance review steps are needed before method activation?
  • How do API events and reports represent payment attempts, pending states, captures, refunds, partial refunds, chargebacks, reversals, webhook retries, and manual adjustments?
  • Can reports include merchant order ID, customer or account ID, country, currency, FX fields, fee components, refund status, dispute status, payout or settlement batch, and provider reference?
  • How should operations handle this stated need: Low-friction app checkout for rides, delivery orders, bookings, deposits, cancellation fees, tips, wallet top-ups, and refunds.?
  • How should finance and support handle this stated need: Local wallets, QR payments, instant bank transfers, cards, mobile money, payment links, and in-person fallback routes through provider-reviewed PSP, acquirer, gateway, or wallet-operator integrations.?
  • Which claims about method availability, settlement, coverage, onboarding, support channels, or compliance status should remain unpublished until confirmed in writing?

Risk and compliance notes

  • On-demand models often combine customer checkout, driver or courier payouts, tips, refunds, cancellations, and surge adjustments that must reconcile cleanly.
  • Delayed payment confirmation can create dispatch, inventory, route assignment, or service-start issues if orders move forward too early.
  • Driver, courier, merchant, or partner payouts may require separate verification, tax, sanctions, and payout-route review from customer payment acceptance.
  • Refunds, partial refunds, cancellations, no-shows, failed deliveries, tips, and chargebacks need clear ledger and support ownership.
  • High dispute volume, cash-adjacent flows, restricted goods, alcohol, pharmacy, or regulated transport categories may trigger additional provider review.
  • Reconciliation should connect order ID, trip ID, rider or courier ID, merchant ID, tip, promotion, refund, dispute, payout, and settlement batch.
  • Do not state that a local wallet, QR route, or bank transfer is available for this model until provider review covers the on-demand flow.

Suggested internal links