Skip to main content

Google Pay™

Google Pay™ lets users pay with their cards stored in their Google account, providing a fast and secure checkout experience. When offering Google Pay™ as a payment method, you must use the official Google Pay™ logo and button assets in compliance with Google Pay Web Brand Guidelines, without modifications to the Google Pay™ asset colors, proportions, or appearance.

Google Pay™ is available via the following JustiFi checkout options:

Google Pay™ is not available in the Tokenize Payment Method web component or via API.

Prerequisites​

Implementation Resources​

For detailed implementation guidance, refer to the following Google Pay documentation:

Processing Google Pay™ Payments​

You must complete the following essential steps to enable Google Pay™ functionality:

Adhere to Google policies: When using Google Pay™ with JustiFi checkout components, merchants must adhere to the Google Pay and Wallet API's Acceptable Use Policy and accept the terms defined in the Google Pay API Terms of Service.

Content Security Policy (CSP) settings: If your application uses Content Security Policy, you may need to update your CSP settings to allow the Google Pay™ SDK to function properly. Ensure your CSP allows connections to Google Pay™ domains and scripts.

Enable Google Pay™ in your account: Ensure that Google Pay™ is enabled in your JustiFi merchant account dashboard. Contact your account representative if you need assistance enabling this feature.

Hosted Checkout and Unified Fintech Checkout​

Once Google Pay™ is enabled in your JustiFi merchant account dashboard, the Google Pay™ button will automatically appear as a payment option in your Hosted Checkout and Unified Fintech Checkout forms. No additional code is required.

For more information on setting up hosted checkout, see our Hosted Checkout documentation.

Modular Checkout​

To add Google Pay™ to the Modular Checkout web component, include the Google Pay sub component in the Modular Checkout as the example below shows. For more details refer to the Modular Checkout docs.

<justifi-modular-checkout
  auth-token="your-auth-token"
  checkout-id="your-checkout-id"
>
  <justifi-google-pay />
</justifi-modular-checkout>

JustiFi will create a payment method record (ID starting with pm_) for each transaction processed via Google Pay™.

Implementation Details​

Gateway Configuration​

As a supported payment service provider with the Google Pay™ API, our integration lets you as a merchant use Google Pay™ API's gateway integration type, where we handle all of the decryption on your behalf.

When using JustiFi checkout components with Google Pay™, the following values are automatically set in the TokenizationSpecification object. No merchant configuration or code is required — the checkout component handles this entirely:

  • gateway: Set to justifi automatically.
  • gatewayMerchantId: Set using {sub_account_id} which is the sub account the checkout is configured to process payments for.

Here is an example of what the checkout component passes when initializing the Google Pay™ button:

{
  "tokenizationSpecification": {
    "type": "PAYMENT_GATEWAY",
    "parameters": {
      "gateway": "justifi",
      "gatewayMerchantId": "acc_m9IjrorZoehPX9BA7kIrn"
    }
  }
}

Authorization Methods​

Google Pay™ provides two different authorization methods: PAN_ONLY and CRYPTOGRAM_3DS. Our Google Pay™ integration supports both types of card credentials:

  • PAN_ONLY: Physical card details stored in Google Pay™.

    • Supported countries: United States
    • These are cards manually added to a user's Google account
    • Standard fraud detection and authorization checks apply to all PAN_ONLY transactions

  • CRYPTOGRAM_3DS: Tokenized virtual card stored on device.

    • Authentication is performed by Google Pay™
    • Supported countries: United States
    • These are cards tokenized to Android devices with cryptographic verification
    • Provides an additional layer of security through device-level authentication

Authentication note: JustiFi does not currently support standalone 3D Secure (3DS) authentication for PAN_ONLY credentials. However, CRYPTOGRAM_3DS transactions include built-in authentication performed by Google Pay™ at the device level. For merchants who require enhanced authentication, we recommend encouraging customers to use device-tokenized cards (CRYPTOGRAM_3DS) when available, as these provide stronger security guarantees through Google Pay™'s native authentication.

Supported Card Networks​

We support the following card networks with the Google Pay™ API. These values are all passed to the allowedCardNetworks property automatically and find the appropriate values in Google Pay's web developer documentation:

  • VISA
  • Mastercard
  • American Express
  • Discover

Billing Address Requirements​

A billing address is not required for Google Pay™ payments processed through JustiFi checkout components.

Handling Google Pay™ Payment Data​

When a customer pays with Google Pay™ through a JustiFi checkout component, the entire payment data lifecycle is handled automatically. The checkout component:

  1. Receives the encrypted payment data from Google Pay™
  2. Extracts the token from the paymentMethodData.tokenizationData.token property
  3. Sends the token securely to the JustiFi backend
  4. Tokenizes the payment data into a JustiFi payment method
  5. Completes the checkout

No merchant action is required to process or handle the Google Pay™ payment data. The checkout component manages the complete flow from customer authorization through checkout completion.

For more information on completing checkouts, see our Checkout API documentation.

See Also​

  • Apple Pay - Learn about Apple Pay integration with JustiFi