Our Android Drop-in renders GCash in your payment form, and redirects the shopper to the GCash's website where they can complete the payment.
Before you begin
This page explains how to add GCash to your existing Android Drop-in integration. The Android Drop-in integration works the same way for all payment methods. If you haven't done this integration yet, refer to our Drop-in integration guide.
Before starting your GCash integration:
Show GCash 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 GCash in your payment form, specify in your /paymentMethods request:
Make a payment
When the shopper proceeds to pay, Drop-in returns the
paymentComponentData.paymentMethodto your server.
From your server, make a /payments request, specifying:
paymentComponentData.paymentMethodfrom your client app.
returnUrl: URL to where the shopper should be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters. Get this URL from the Component in the
The /payments response contains an
action object with the information needed to redirect the shopper.
If your integration is set up correctly, the
action object is passed from your server to the client.
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
From your server, make a POST /payments/details request providing:
actionComponentData.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.
Present the payment result
resultCode values you can receive for GCash are:
|resultCode||Description||Action to take|
|Authorised||The payment was successful.||Inform the shopper that the payment has been successful.|
|Cancelled||The shopper cancelled the payment while on GCash's website.||Ask the shopper whether they want to continue with the order, or ask them to select a different payment method.|
|Error||There was an error when the payment was being processed.||Inform the shopper that there was an error processing their payment. The response contains a
|The shopper has completed the payment but the final result is not yet known.||Inform the shopper that you've received their order, and are waiting for the payment to be completed.
To know the final result of the payment, wait for the AUTHORISATION webhook.
|Refused||The payment was refused by the GCash.||Ask the shopper to try the payment again using a different payment method.|
|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.|
Recurring paymentsGCash supports recurring transactions. To make recurring transactions, you need to:
Create a token
To create a token, include in your /payments request:
- shopperReference: Your unique identifier for the shopper (minimum length three characters).
When the payment has been settled, you receive a webhook containing:
pspReferenceof the initial payment.
pspReference: This is the token that you need to make recurring payments for this shopper.
Make sure that your server is able to receive RECURRING_CONTRACT as part of your standard webhooks. You can enable the RECURRING_CONTRACT event code in the webhook settings page.
Make a payment with a token
To make a payment with the token, include in your /payments request:
pspReferencefrom the RECURRING_CONTRACT webhook.
You can also get this value by using the /listRecurringDetails endpoint.
shopperReference: The unique shopper identifier that you specified when creating the token.
recurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.
Test and go live
To test successful GCash live payments, you need to use a real mobile number registered with a GCash account.
If you are encountering issues with testing GCash payments, contact our Support Team.
Check the status of GCash test payments in your Customer Area > Transactions > Payments.
Before you can accept live GCash payments, you need to submit a request for GCash in your live Customer Area.