Our Android Drop-in renders GrabPay in your payment form, and redirects the shopper to GrabPay to complete the payment.
Requirements
| Requirement | Description |
|---|---|
| Integration type | Make sure that you have built an Advanced flow Android Drop-in integration. |
| Setup steps | Before you begin, add GrabPay in your Customer Area. |
Show GrabPay in your payment form
Drop-in uses the countryCode and the amount.currency from your /paymentMethods request to show the available payment methods to your shopper.
To show GrabPay in your payment form, specify in your /paymentMethods request:
| Country/region | countryCode | amount.currency |
|---|---|---|
| Malaysia | MY | MYR |
| Singapore | SG | SGD |
| Philippines 1 | PH | PHP |
1 GrabPay PayLater is not available in Philippines.
The response contains the corresponding paymentMethod.type grabpay_XX where XX is the country code.
Collect additional information in your payment form
Collecting additional information is only needed for GrabPay PayLater payments. However, we highly recommend collecting this information in your initial integration for GrabPay Wallet because it will help save development resources if you plan to enable GrabPay PayLater afterwards.
Collect the following details from the shopper:
- deliveryAddress: The address where the purchased goods should be delivered, including the country, city, street, house number, and postal code.
- lineItems: Price and product information about the purchased items, to be included on the invoice sent to the shopper.
Pass the collected data to your server because you will need it when making a payment. This information will be used by GrabPay to perform risk checks.
Make a payment
When the shopper proceeds to pay, Drop-in returns the paymentComponentData.paymentMethod. Depending on the type of GrabPay payment, Wallet or PayLater, you need to provide different parameters in the /payments request.
Check the payment result
Drop-in redirects the shopper to complete the payment. When the shopper returns back to your app, Drop-in provides the actionComponentData object.
From your server, make a POST /payments/details request providing:
details: TheactionComponentData.detailsobject from Drop-in.
You receive a response containing:
resultCode: Use this to present the payment 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/detailsrequest. - 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.