Not the solution you were looking for?

    Click the button to submit a support ticket

    Submit Ticket

    Google Pay™

    Google Pay™ lets your shoppers pay with the cards they have saved in their Google Account, without typing any card details. It is supported through both our Payment Page and our Seamless Checkout, and is processed by PayXpert as a Google Pay API processor.

    If Google Pay is not already enabled for your account, simply request activation by creating a support ticket requesting the payment method for your site(s) and our team will enable it for you.

    Before you begin

    Google Pay is supported for web integrations. Whichever integration you use, the Google Pay button and all Google Pay assets are rendered by our components using Google approved assets, in compliance with the Google Pay Web Brand Guidelines. You do not need to host, build or alter those assets.

    When offering Google Pay, you must:


    The following Google resources are also useful references:

    Integration paths

    Payment Page

    No integration change and no configuration are required on your side to use Google Pay with our Payment Page. Once the payment method is enabled on your account, the Google Pay button is displayed automatically on the hosted payment page to eligible shoppers.

    Transaction data (amount, currency, order reference) is supplied exactly as for any other payment method, through the regular Create a Payment call.

    Offering Google Pay through our Payment Page is subject to the Google Pay obligations listed in Before you begin.

    Seamless Checkout

    To use Google Pay with our Seamless Checkout, set the configuration parameter enableGooglePay to true:

      <!-- Inside the JSON configuration of the Seamless -->
  <script type="application/json">
    {
      "enableGooglePay": true
    }
  </script>

    Google Pay requires version 1.6.2 or later of the Seamless Checkout library. See the Seamless Checkout page for how to include the library in your checkout page.

    Our library takes care of the whole Google Pay client integration for you:

    • It loads the Google Pay API JavaScript client library onto your page.
    • It builds the IsReadyToPayRequest and PaymentDataRequest objects on your behalf, and displays the Google Pay button only when the shopper is eligible.
    • It sets gateway to the gateway identifier assigned to PayXpert by Google during our processor onboarding, and gatewayMerchantId to the identifier of your site in our system.

    As a result, you do not need to register with the Google Pay & Wallet Console and there is no Google MerchantID to provision or to enter in our library.

    If your checkout page enforces a Content-Security-Policy, make sure that the Google Pay resources loaded by the library are allowed, otherwise the Google Pay button will not be displayed.

    Using our Seamless Checkout library to offer Google Pay is subject to the Google Pay obligations listed in Before you begin.

    Authorization methods

    Google Pay provides two authorization methods, which determine the type of credentials returned in the payment payload:

    Method Description Supported
    CRYPTOGRAM_3DS Device bound token accompanied by a network cryptogram. The transaction is already authenticated: the cardholder verified their identity with the issuing bank when adding the card to the Google Wallet, so no additional 3-D Secure challenge is required. Yes
    PAN_ONLY Card credentials are passed through as a regular card transaction and typically require 3-D Secure authentication, just like a standard PAN transaction. No

    We only enable CRYPTOGRAM_3DS during our technical onboarding with Google.

    Because PAN_ONLY is not enabled, Google never returns PAN_ONLY credentials for our merchants. The 3D Secure v2 authentication flows therefore is not necessary for Google Pay transactions: authentication is carried by the cryptogram contained in the Google Pay payload. It will apply of course when the PAN_ONLY method support will be added.

    Allowed card networks

    The card networks enabled for PayXpert during our technical onboarding with Google are:

    allowedCardNetworks value Card network
    VISA Visa
    MASTERCARD Mastercard
    AMEX American Express

    Our components set allowedCardNetworks for you, so no configuration is needed on your side.

    The networks actually offered to the shopper also depend on the card networks configured on your own account. A network that is not enabled for your account will not be proposed, even though Google Pay supports it.

    Billing address

    Our integration does not request a billing address in the Google Pay payment data: BillingAddressParameters is not used, and address verification is not performed on Google Pay transactions.

    Payment data handling

    You never handle the Google encrypted payment payload yourself. The full flow is:

    1. The shopper selects Google Pay and authorizes the payment in the Google Pay sheet.
    2. Google returns the encrypted payment payload to our Payment Page or Seamless Checkout component running in the shopper’s browser.
    3. The component transmits that payload directly to our servers, where it is decrypted using the key registered with Google during our processor onboarding.
    4. The payment is then processed on your terminal, and the result is returned through the usual Payment Page or Seamless Checkout response.

    Your own servers never receive, store or forward the Google encrypted payload, which keeps this data out of your systems entirely. Transaction data (amount, currency, order reference) is supplied through the regular Create a Payment call or the Seamless Checkout flow: there is no Google Pay specific API call to implement.


    © PayXpert 2025

    Privacy Policy