Skip to main content

Introduction

GrabPay uses a redirect-based payment flow. When a customer selects GrabPay at checkout, they are redirected to GrabPay’s app or web interface to authenticate and confirm their payment, then redirected back to your website or app upon completion. GrabPay is a single-use payment method where customers must authenticate each payment. This guide explains the process of integrating GrabPay into your app or website using Payrails.

Pre-requisites

Before you start accepting GrabPay payments with Payrails, there are a few requirements you must meet:

Ways to integrate GrabPay

Payrails SDK

Server-to-server integration

Parse GrabPay from lookup response

Pass GrabPay payment method in request to authorize payment with Payrails

Note on amountsPHP uses 2 decimal places. Amounts should be provided in the smallest currency unit—for example, 50000 for ₱500.00.
GrabPay is a redirect-based, single-use payment method. After calling the authorize endpoint, the customer will be redirected to GrabPay’s app or web interface to authenticate and confirm the payment. Once confirmed, the customer will be redirected back to the returnInfo.success URL. Make sure to provide valid returnInfo URLs in your authorization request.

Handle the redirect response

Supported currencies

GrabPay via dLocal supports the following presentment currencies:
  • PHP — Philippine Peso
  • MYR — Malaysian Ringgit

Supported regions / countries

Customer regions

GrabPay is available to customers based in:
  • Philippines 🇵🇭
  • Malaysia 🇲🇾

Merchant regions

Merchants enabled for the Philippines or Malaysia can accept GrabPay payments via dLocal.

Supported workflows and services

Last modified on September 28, 2026