GrabPay for API only

Add GrabPay to an existing API-only integration.

Accept GrabPay payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.

Requirements

Select the server-side flow that your integration uses:

Build your payment form for GrabPay

To show GrabPay in your payment form, you need to:

Include GrabPay in the list of available payment methods.
After the shopper selects GrabPay, pass the payment method type to your server:
- grabpay_MY if the shopper is in Malaysia and is paying with Malaysian Ringgit.
- grabpay_PH if the shopper is in the Philippines and is paying with Philippine Peso.
- grabpay_SG if the shopper is in Singapore and is paying with Singapore Dollars.

We provide a GrabPay logo which you can use on your payment form. For more information, refer to Downloading logos for details.

You can also get the paymentMethod.type from the /paymentMethods response as explained in the API-only integration guide. In your /paymentMethods request, specify:

Country/region	countryCode	amount.currency
Malaysia	MY	MYR
Singapore	SG	SGD
Philippines ¹	PH	PHP

¹ GrabPay PayLater is not available in Philippines.

Get the corresponding paymentMethod.type from the response.

Make a payment

Depending on the type of GrabPay payment, Wallet or PayLater, you need to provide different parameters in the /payments request.

Handle the redirect

To complete the payment, redirect the shopper to the action.url returned in the /payments response, taking into account the following recommendations:
- When using the HTTP GET method:
  For security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.
- Redirection for mobile integrations:
  For mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.
After the shopper is redirected back to your website, check the payment result by making a POST /payments/details request, specifying:
- details: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.
In the response note the following:
- resultCode: use this to present the result to your shopper.
- pspReference: our unique identifier for the transaction.

For GrabPay PayLater, the response also contains additionalData.paymentMethodVariant — the Adyen sub-variant of the payment method used for the payment request. Possible values:

For GrabPay Wallet: grabpay_wallet_SG, grabpay_sg, grabpay_wallet_MY, grabpay_my, grabpay_wallet_PH, grabpay_ph
For GrabPay PayLater: grabpay_postpaid_SG, grabpay_instalment4_SG, grabpay_postpaid_MY, grabpay_instalment4_MY.

Present the payment result

Use the resultCode that you received in the /payments/details response to present the payment result to your shopper.

The resultCode values you can receive for GrabPay are:

resultCode	Description	Action
Authorised	The payment was authorised. You will receive the funds in a number of days.	Inform the shopper that the payment was successful.
Cancelled	The shopper cancelled the payment before it was completed, for example while in the GrabPay app.	Ask the shopper whether they want to continue with the order, or ask them to select a different payment method.
Refused	The payment was refused by the shopper's card issuer.	Ask the shopper to try the payment again using a different payment method or card.
Pending or Received	The shopper has completed the payment but the final result is not yet known. You will receive the final result of the payment in an AUTHORISATION webhook.	Inform the shopper that you have received their order, and are waiting for the payment to be processed.

If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for GrabPay are:

eventCode	success field	Description	Action to take
AUTHORISATION	false	The transaction failed.	Cancel the order and inform the shopper that the payment failed.
AUTHORISATION	true	The shopper successfully completed the payment.	Inform the shopper that the payment has been successful and proceed with the order.
OFFER_CLOSED	true	The shopper did not complete the payment.	Cancel the order and inform the shopper that the payment timed out.

Test and go live

You can test your GrabPay integration in two ways: with the Adyen Payment Simulator, or directly with GrabPay.

Test with Adyen

Use the Adyen Payment Simulator to verify that your GrabPay integration works correctly with Adyen. You can test during development, before you go live, and after launch. The simulator does not recreate the shopper's journey through the GrabPay app or website.

This testing option is available by default when you add GrabPay in your test Customer Area. The payment method type is grabpay_SG.

To test a redirect payment:

Start a payment as usual in your integration. The shopper is redirected to an Adyen-hosted simulator page.
Select the payment outcome that you want to test.
Wait for the simulator to return the shopper to your website, then complete the payment as usual. For an Advanced flow, make a /payments/details request.
Confirm that your integration handles the outcome that you selected, and that the payment appears in your Customer Area > Payments > Payment list.

Test directly with GrabPay

To test directly with GrabPay:

Contact our Support Team for your test wallet credentials.
In the simulator, log in to Grab with the phone number you registered, and specify the one-time password that you receive on that phone number.

Check the status of direct GrabPay test payments in your Customer Area > Payments > Payment list.

Before you can accept live GrabPay payments, you need to submit a request for GrabPay in your live Customer Area.