Skip to main content
GCash is a mobile wallet used by customers in the Philippines. Customers pay from their GCash account and confirm each payment in the GCash app or on the GCash website. Payrails processes GCash through two payment service providers (PSPs). The flow is the same with each one, but the required request fields differ. Pick a PSP below for its setup steps and request examples.

How a GCash payment works

GCash is a redirect payment method:
  1. The customer selects GCash at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to GCash.
  3. The customer logs in and confirms the payment in the GCash app or on the GCash website.
  4. GCash 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 GCash payments immediately, so a successful payment is final. To return funds, refund the payment.

Supported currencies and countries

GCash supports PHP (Philippine peso) as its only presentment currency.

Integrate GCash

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

Checkout.com

GCash via Checkout.com

dLocal

GCash via dLocal

Compare PSPs

Neither PSP supports Save Instruments or merchant-initiated transactions (MIT) for GCash.

Ways to integrate GCash

  • Payrails SDK: the Web SDK shows GCash when your workflow returns it as a payment option, and redirects the customer to GCash. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with gCash as the paymentMethodCode. Each PSP guide lists the meta 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 2, 2026