Google Pay™ on PayCaps hosted checkout

PayCaps Technology LLC SPC · October 2026

Google Pay™ lets a customer pay with a card saved in their Google Account, or with a tokenized card on their device.

PayCaps is a payment facilitator. Google Pay is offered on the PayCaps hosted payment page, on the PayCaps domain. PayCaps renders the official Google Pay button, collects the Google Pay payment credential, and completes the payment.

Merchants use the same hosted checkout request they already use for cards. There is no Google Pay JavaScript, no Google Pay sheet, and no Google Pay token on the merchant website.

PayCaps does not currently offer a merchant-direct Google Pay Web or Android integration. Google Pay is available through the PayCaps hosted payment page.

What the merchant does

1. Follow the Google Pay and Wallet API Acceptable Use Policy and accept the Google Pay API Terms of Service. These terms apply whenever Google Pay is offered on PayCaps hosted checkout.
2. Ask PayCaps to enable Google Pay on hosted checkout for the merchant profile and settlement currency.
3. Keep using the existing PayCaps hosted payment request. Redirect the customer to the PayCaps payment page. No new Google Pay fields, libraries, or APIs are added on the merchant website.
4. After payment, read the standard PayCaps hosted-checkout result on the merchant return URL.

Merchants do not register in the Google Pay & Wallet Console, load the Google Pay JavaScript on their website, build a PaymentDataRequest, set gateway or gatewayMerchantId, or place the PayCaps payment page in an iframe for Google Pay.

Existing hosted checkout

The payment request, secure hash, amount format, and response validation stay the same as the PayCaps payment gateway integration guide.

Redirect the customer in the same browser window. PayCaps hosted Google Pay is a full-page redirect. It is not an iframe component on the merchant site.

Required request fields are unchanged: APP_ID, ORDER_ID, RETURN_URL, HASH, AMOUNT, and CURRENCY_CODE. Amount is still sent in minor units. For example, AED 1200.23 is 120023.

How the customer pays

1. The customer is redirected from the merchant website to the PayCaps payment page.
2. When Google Pay is enabled for that merchant, the payment page shows Google Pay next to the other PayCaps methods.
3. The customer selects Google Pay. PayCaps opens the Google Pay sheet from the PayCaps domain.
4. PayCaps processes the payment. For PAN_ONLY, PayCaps starts 3D Secure automatically. For CRYPTOGRAM_3DS, no extra 3D Secure step is required.
5. The customer is returned to the merchant RETURN_URL with the usual PayCaps payment result.

The Google Pay payload stays on the PayCaps payment page. Merchants never extract it and never post it to PayCaps. PayCaps returns only the standard hosted-checkout payment result. Merchants never receive the Google Pay token or raw card credentials.

Branding

PayCaps renders the official Google Pay button on the PayCaps payment page with the Google Pay API createButton helper, in line with the Google Pay Web Brand Guidelines. Button colour, proportions, and appearance are not modified.

A Google Pay mark on the merchant website, before the redirect to PayCaps, is optional. If a merchant shows that mark, the artwork must follow the same brand guidelines. The mark is not required for Google Pay to work on PayCaps hosted checkout.

• Google Pay Web developer documentation
• Google Pay Web integration checklist
• Google Pay Web Brand Guidelines

Gateway tokenization

PayCaps uses Google Pay API gateway tokenization (PAYMENT_GATEWAY) on the payment page. Merchants do not copy this configuration into their application.

{
  "tokenizationSpecification": {
    "type": "PAYMENT_GATEWAY",
    "parameters": {
      "gateway": "paycaps",
      "gatewayMerchantId": "<set by PayCaps>"
    }
  }
}

Authorization methods and 3D Secure

PayCaps enables both methods on the hosted page. Merchants do not switch these on or off.

Supported card networks

On the PayCaps payment page, allowedCardNetworks is Visa and Mastercard. Other card networks are not enabled. See Google Pay Web CardParameters.

Billing address

PayCaps does not request Google Pay billingAddressParameters on the hosted payment page. Merchants do not collect or submit a Google Pay billing-address object. Customer fields already supported on the hosted payment request remain optional, as described in the integration guide.

Payment result

PayCaps posts the result to the merchant RETURN_URL using the same response parameters as any other hosted checkout payment. Validate HASH before treating the payment as successful. For a successful payment, RESPONSE_CODE is 000 and STATUS is Captured or Approved.

Google Pay payments are identified on that result as follows:

The response also includes the usual fields, including ORDER_ID, TXN_ID, PG_REF_NUM, AMOUNT, CURRENCY_CODE, RESPONSE_MESSAGE, AUTH_CODE, RRN, and HASH. The full list is in the integration guide.

Google Pay on PayCaps hosted checkout is complete from the merchant side once PayCaps has enabled it on the merchant account. The customer pays on the PayCaps payment page. PayCaps handles the Google Pay credential and returns the standard hosted-checkout result.

Enable Google Pay

Google Pay appears on the hosted payment page only after PayCaps enables it for that merchant. Contact PayCaps integration support or your relationship manager and share the merchant APP_ID and settlement currency.

Support: support@paycaps.com

Google Pay is a trademark of Google LLC. PayCaps Technology LLC SPC.