← Back to the directory

Payment channel profile

GrabPay

Wallet / user payment entry · Malaysia

MalaysiaPrimary marketMain service market
Wallet / user payment entryRole / typeDigital wallet
Medium, verify entity and documentsEntity requirementOnboarding conditions
T+1SettlementPayout timing

Overview

GrabPay is listed as digital wallet in the LocalPayMap public directory. Use this page to prepare due-diligence questions; product availability and terms must be verified directly.

This is a market-specific GrabPay record, not a duplicate of the brand overview and not the only official onboarding or pricing route. The brand page aggregates related countries and PSP contact leads; this page keeps the local payment scenario visible.

Role in the payment stack

Wallet / user payment entry

This is usually a wallet or consumer payment entry. Foreign merchant access often depends on a PSP, aggregator, platform partnership, or local entity setup.

Merchant usage and connection route

GrabPay in the payment stack

GrabPay matters for merchants targeting consumers in Grab's Southeast Asia ecosystem, especially where wallet checkout, app-linked promotions, ride or delivery users, and offline QR behavior may influence conversion. Assess it alongside local wallets, bank QR schemes, cards, BNPL, and PSP coverage for each target country.

Connection route

Connection can be direct through Grab merchant/business channels or indirect through PSPs, gateways, ecommerce platforms, or local aggregators that include GrabPay in a broader payment-method bundle. Merchants should verify the country, product surface, settlement owner, refund flow, and reporting format.

Verification questions

  • Which country, online checkout, app, POS, QR, or marketplace flow requires GrabPay acceptance?
  • Is the route direct with Grab or through a named PSP, gateway, platform, or aggregator?
  • Which refunds, partial refunds, charge adjustments, reconciliation files, and customer support processes are available?
  • Does the provider support the merchant's entity, category, currencies, and expected transaction model?
  • How are wallet promotions, discounts, or loyalty-funded campaigns treated in settlement and reporting?

Merchant caveats

  • GrabPay scope can differ by country and channel.
  • Consumer app visibility does not prove direct merchant onboarding availability.
  • Promotion mechanics, refunds, and reconciliation should be reviewed before campaign planning.
  • Provider examples are discovery examples only, not recommendations or support evidence.

Provider examples to verify

GrabPayWitpay

Related markets

MalaysiaPhilippinesSingaporeThailand

Keep researching

This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.

Sources

What merchants should confirm

  • Whether the product is available to merchants incorporated outside the target country.
  • Whether a local entity, local bank account, licence, or local tax registration is required.
  • Supported checkout flows, currencies, refunds, disputes, reconciliation fields, and payout options.
  • Industry restrictions, reserve policies, onboarding documents, and implementation support.

Merchant eligibility

Merchant eligibility and entity requirements must be confirmed with the provider.

Pricing and settlement

Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.

Settlement timing, payout currency, foreign exchange, reserves, and withdrawal rules must be confirmed with the provider.

Capability verification checklist

Use this public checklist before you ask for a quote or implementation access. Treat unknown fields as questions to verify, not as unsupported features.

  • Confirm who owns onboarding, KYB review, pricing, settlement, refunds, disputes, reconciliation, reserves, and support for the route you will use.
  • Open the official pricing, developer, support, or website links where available, then verify the exact production terms with the provider or PSP.
  • Do not treat public notes as final approval, final pricing, settlement timing, or a guarantee that your merchant entity can go live.

Official links to open

Commercial terms to confirm

Pricing modelwallet acceptance or psp priced
Pricing basisprovider quote required
Fields still to confirm
  • Fee range: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • FX markup: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Chargeback fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Payout fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Reserve policy: confirm with the provider, acquirer, PSP, or official documentation before launch.

Integration route to confirm

API / checkout routepsp wallet enablement
Fields still to confirm
  • SDK languages: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Sandbox: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Webhooks: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Idempotency: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • PCI scope: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • 3-D Secure: confirm with the provider, acquirer, PSP, or official documentation before launch.

Operational features to confirm

No public field in this group is complete enough to treat as confirmed. Use it as a due-diligence prompt.

Fields still to confirm
  • Recurring billing: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Marketplace split: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Partial refund: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Preauth / capture: confirm with the provider, acquirer, PSP, or official documentation before launch.

Public pricing signals are for initial screening only. Actual quotes can vary by country, industry, transaction volume, settlement currency, integration route, and contract terms.

Visit the official website