GCash via Adyen
This feature is currently a Private Beta release. Contact Chargebee Support to enable GCash via Adyen for your live and test sites.
GCash is the leading digital wallet in the Philippines that enables customers to authorize payments through the GCash app. Chargebee supports GCash as a payment method through the Adyen payment gateway.
When customers select GCash at checkout, they are redirected to GCash to authorize the payment. The payment is processed asynchronously by Adyen, and the final status is confirmed through webhooks. After the initial authorization, Adyen stores a token that enables merchant-initiated charges for subsequent billing cycles, making GCash suitable for recurring subscriptions.
Supported countries and currencies
GCash via Adyen supports the following country and currency. Refer to the Adyen GCash documentation for the latest details.
| Country | Currency |
|---|---|
| Philippines | PHP |
Prerequisites
To accept GCash payments using Chargebee, you must:
- Have an active Adyen account with GCash enabled as a payment method in your Adyen Customer Area. Learn more
- Ensure PHP (Philippine Peso) currency is enabled for your Chargebee account.
- Ensure the Adyen payment gateway and webhooks are configured in your Chargebee account. Learn more
- Have a Merchant Account configured for GCash in Adyen, with API credentials and webhooks enabled.
Configure GCash in Chargebee
Follow these steps to enable GCash via Adyen in your Chargebee site:
- Log in to the Chargebee app.
- Navigate to Settings > Configure Chargebee > Payment Gateways.
- Select the required Adyen gateway instance.
- On the Configure Adyen page, enable GCash under the supported payment methods.
- Click Apply to save the configuration.
Configure Smart Routing for GCash
When you configure GCash through Adyen, smart routing for the PHP currency is automatically enabled. Check the Smart Routing settings, and if another gateway is already designated for the PHP currency, adjust the Smart Routing settings manually to allocate GCash to it.
Follow these steps to modify Smart Routing settings:
- Log in to the Chargebee app.
- Go to Settings > Configure Chargebee > Payment Gateways.
- Click Manage Rules under Smart Routing.
- Go to the GCash section and click Add a Gateway for PHP. If you already have a payment gateway assigned to it, click Edit.
- From the Choose a payment gateway drop-down menu, select the relevant Adyen instance with GCash enabled.
- Click Save.
Payment workflow
Your customer performs the following steps during checkout using GCash via Adyen:
- The customer reviews the order on the Your cart page and selects Proceed to Checkout.
- The customer enters their Account Details and Billing Address, selects GCash, and selects Pay & Subscribe.
- On the Pay with GCash screen, the customer enters their GCash-registered mobile number and selects Next.
- The customer enters the 6-digit authentication code sent to their mobile number.
- The customer enters their MPIN to authorise the payment.
- The customer reviews the merchant details and selects Confirm to complete the payment.
- The customer is redirected back to Chargebee, and the order confirmation page appears once the payment is processed.
Note
The screenshots above are from Adyen's test environment. In production, the GCash screens show live branding and the customer receives a real OTP on their registered mobile number to authorise the payment.
Testing
Sandbox testing
Refer to Adyen's GCash testing documentation for instructions on testing GCash in the Adyen test environment.
Ensure webhooks are configured to receive AUTHORISATION updates for recurring charges and REFUND / CANCEL_OR_REFUND updates for refund settlement.
Production testing
Before going live:
- Ensure GCash is enabled in your Adyen live account.
- Verify webhook configuration is complete (required for recurring charge and refund settlement updates).
- Perform end-to-end testing using a real GCash-enabled wallet account and a mobile device with the GCash app installed.
Reconciliation
For financial reconciliation between Chargebee and Adyen:
- Use the Chargebee transaction field id_at_gateway, which maps to the pspReference in Adyen.
Follow these steps to reconcile transactions:
- Retrieve the id_at_gateway value from the Chargebee transaction details.
- Locate the corresponding pspReference in Adyen reports for GCash transactions.
- Match transactions using this reference to ensure financial consistency.
Payment features
The following are the features for this integration and details about them:
| Feature | Description | Supported | Default state | Configuration / behavior |
|---|---|---|---|---|
| Integration sync mode | Defines how payment requests are processed and statuses are communicated between Chargebee and Adyen. | Yes (Asynchronous) | Asynchronous | Adyen processes GCash payments asynchronously. Chargebee receives the final payment status through Adyen webhooks. Webhook configuration is mandatory and is used to receive AUTHORISATION updates for recurring charges and REFUND / CANCEL_OR_REFUND updates for refund settlement. |
| Capture settings | Payment processing involves two stages: Authorization and Capture. Capture settings determine when funds are collected after authorization. | Yes | Auto capture | Auto capture is the default and only supported capture setting for GCash via Adyen. No additional configuration is required. |
| Verification modes | Defines how payment methods are verified before processing. | Yes | Enabled | The customer authorizes the payment within the GCash app using mobile number, OTP, and MPIN. No separate verification configuration is required in Chargebee. |
| Statement descriptor | Displays the business name on the customer's bank or wallet statement, helping them recognize charges and reducing disputes. | Yes | Disabled | Configure this under Settings > Configure Chargebee > Transaction Descriptor. |
| Chargeback management | Handles chargeback events and applies configured actions on invoices and subscriptions. | No | NA | GCash does not support chargebacks for this integration. Refunds must be issued manually if needed. |
| Fraud management | Uses gateway fraud signals to identify and flag high-risk transactions. | No | NA | No GCash-specific fraud configuration is available in Chargebee. |
| Transaction initiation type | Identifies whether a transaction is customer-initiated (CIT) or merchant-initiated (MIT). | Yes | Supported | The initial GCash payment is customer-initiated through the GCash app. Subsequent recurring charges are merchant-initiated using the stored Adyen token. |
| Error intelligence | Provides standardized categorization of payment failures. | Yes | Enabled | Available through Adyen payment and refusal responses. No configuration is required. |
| Gateway transaction details | Provides access to raw gateway responses for transactions. | Yes | Enabled | Available on the transaction page under Error details. No configuration is required. |
| Addition of payment methods in Chargebee dashboard | Allows a payment method to be added in Chargebee when details are collected outside checkout. | No | NA | Customers must complete the GCash checkout flow. GCash cannot be added from the Chargebee dashboard. |
Supported token formats
This section is relevant if you are building a custom checkout or migrating payment methods from another provider to Adyen.
| Token type | Description | Supported | Token field | Token format |
|---|---|---|---|---|
| Chargebee Payment Intent | Recommended token format when building a custom checkout using Chargebee JS. | Yes | payment_intent[id] | payment_intent_id |
| Chargebee token | Legacy token format supported for selected payment methods and gateways with Chargebee JS. Not recommended for new implementations. | No | token_id | NA |
| Gateway permanent token | Permanent reference provided by Adyen and used for subsequent recurring GCash payments. | Yes | payment_method[reference_id] | shopper_reference_id/recurring_detail_reference_id |
| Gateway temporary token | Short-lived token format that can be converted to a permanent token. | No | NA | NA |
Limitations and important points
- GCash cannot be added as a payment method via the customer portal or the Chargebee app. Customers must complete the GCash checkout flow.
- The initial transaction requires explicit customer authorization via redirect. Subsequent recurring charges are processed as merchant-initiated transactions without customer intervention.
- GCash is exclusively available for PHP (Philippine Peso) transactions.
Was this article helpful?