Skip to main content
GrabPay is a mobile wallet in the Grab app, used by customers in Singapore and Malaysia. Customers pay from their GrabPay balance and confirm each payment in the Grab app. Payrails processes GrabPay through two payment service providers (PSPs). The flow is the same with each one, but the required request fields and the supported countries differ. Pick a PSP below for its setup steps and request examples.

​
How a GrabPay payment works

GrabPay is a redirect payment method:
  1. The customer selects GrabPay at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to GrabPay.
  3. The customer logs in and confirms the payment in the Grab app.
  4. GrabPay sends the customer back to your returnInfo URL.
  5. Payrails receives the final result from the PSP and updates the payment.
Each payment is single-use: the customer confirms every payment on its own. Payrails captures GrabPay payments immediately, so a successful payment is final. To return funds, refund the payment.

​
Supported currencies and countries

GrabPay supports SGD (Singapore dollar) for customers in Singapore and MYR (Malaysian ringgit) for customers in Malaysia. Adyen supports both. dLocal supports MYR. GrabPay is available to customers based in:
RegionsCountries
Asia Pacific🇲🇾 Malaysia🇸🇬 Singapore

​
Integrate GrabPay

Choose the PSP that processes GrabPay for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

Adyen

GrabPay via Adyen

dLocal

GrabPay via dLocal

​
Check PSPs

WorkflowAdyendLocal
Payrails SDK✔✔
Payrails API✔✔
Delayed / Manual Capture✖✖
Instant Capture✔✔
Cancel / Void✖✖
Refund / Reverse✔✔
Save Instruments✖✖
Merchant Initiated Transaction (MIT)✖✖

​
Ways to integrate GrabPay

  • Payrails SDK: the Web SDK shows GrabPay when your workflow returns it as a payment option, and redirects the customer to GrabPay. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with grabPay as the paymentMethodCode. Each PSP guide lists the fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 16, 2026