home

Zuora Payments

Zuora BillingZuora PaymentsZuora PlatformZuora CPQZephrZuora RevenueAccounts ReceivableRelease NotesBasicsEntitlementsSupport and policies
Zuora BillingZuora PaymentsZuora PlatformZuora CPQZephrZuora RevenueAccounts ReceivableRelease NotesBasicsEntitlementsSupport and policies

Welcome to Zuora Product Documentation

Explore our rich library of product information

Show Contents

thumbnailZuora Payments

Adyen Payment Gateway

GCash payments for Adyen Integration v2.0

Use Zuora's Adyen Integration v2.0 to process GCash one-time and recurring payments, manage tokens, and understand supported and unsupported features.

GCash is one of the most popular e-wallets in the Philippines. Zuora's Adyen Integration v2.0 supports GCash transactions in PHP. You can implement a hosted payment page through Payment Pages 2.0 to support GCash one-time and recurring payment flows.

One-time payment flow

On the hosted payment page, a QR code is displayed. End customers can follow the instructions on the page to complete the authorization. The following table describes the workflows after Zuora receives a successful or failed response from the Adyen asynchronous payment API.

ResponseWorkflow
Successful response

  1. Zuora creates the following items:

    • A payment with Payment status = Processed and Gateway State = Submitted

    • A GCash payment method record

  2. A QR code is displayed. End customers can follow the instructions in the dialog to complete the authorization.

  3. After end customers complete the authorization, the GCash payment results are returned to the callback response of the hosted payment page. You can implement your customized logic to handle the success or failure case.

  4. On the backend, Zuora listens to Adyen's webhook events. Zuora updates Gateway State according to the returned webhook:

    • If AUTHORIZATION is true, Gateway State is set to Settled.

    • If AUTHORIZATION is false or OFFER_CLOSED is true, Gateway State is set to FailedToSettle.

  5. If the payment status consistently remains unavailable, you are recommended to proactively query the transaction status to check whether it is Settled or FailedToSettle.

Failed responseZuora throws an error on the hosted payment page with the error response message received from Adyen.

The created GCash payment method can be retrieved through the Zuora UI and API operations. In the Electronic Payment Methods section of the customer account page, you can also retrieve the token information described in the following table. Token ID and Second Token ID will be used in subsequent recurring payments.

Zuora UI fieldValue
Token IDshopperReference
Second Token IDrecurringDetail
Third Token IDpspReference

After a payment is processed, the Reference ID field is populated with a UUID and mapped to pspReference. If you want Reference ID to be populated with the payment number mapped to the merchantReference field in Adyen, submit a ticket at Zuora Global Support.

Recurring payments flow

Recurring payments are processed with the stored tokens. For details about the recurring payment flow for the end customers, see Adyen's documentation.

Supported and unsupported features

The following table lists the supported and unsupported operations and features for GCash on Adyen Integration v2.0:

SupportedUnsupported

  • Payment

  • One-time payment processing

  • Recurring payment processing

  • Standalone payment method validation

  • Payment method creation without making a one-time payment

  • Referenced refund

  • Real-Time Reconciliation

  • Support idempotency for retrying payment and refund transactions

  • Payment cancel (void)

  • Non-referenced refund

  • Delayed Capture

  • Stored Credential Transactions framework and the sharing NTI feature

  • Creation of GCash payment method through UI or API operation

  • Batch Gateway Reconciliation

Last updated: June 15, 2026