Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.paynext.com/llms.txt

Use this file to discover all available pages before exploring further.

Google Pay allows customers to make payments using any credit or debit card saved to their Google Account, including those from Google Play, YouTube, Chrome, or an Android device.

​
Payment Method Details

Customer locationsWorldwide
Supported currenciesAll currencies
Recurrent payments✓
Manual capture support✓
Refunds✓
Supported processorsStripe Braintree Unlimit Worldpay

​
Overview

PayNext exposes Google Pay wherever your checkout runs as soon as a connected processor supports it. Stripe, Braintree, and Unlimit all provide Google Pay capabilities; PayNext decrypts Google Pay ECv2 tokens server-side in a secure isolated environment, re-encrypts sensitive fields (card number, network token, cryptogram), and routes the result to your processor.

​
Prerequisites

​
Enable Google Pay with your processor

  • Stripe: Activate Google Pay under Payments → Payment methods in the Stripe Dashboard. Stripe automatically provisions the Google Pay merchant ID.
  • Braintree: Follow Braintree’s Google Pay onboarding (including registering your domain if prompted) and enable the method for the merchant account that PayNext uses.
  • Unlimit: Ask your Unlimit account manager to turn on Google Pay for the wallet connected to PayNext.
No additional configuration is required inside PayNext—once the processor reports Google Pay as enabled, the method appears automatically in the dashboard and checkout experiences.

​
Token processing

When a customer authorizes a Google Pay payment:
  1. The SDK sends the raw ECv2 token directly to PayNext
  2. PayNext decrypts the token server-side in a secure isolated environment
  3. Sensitive fields are re-encrypted before entering the standard payment pipeline
  4. PayNext routes the tokenized result to your processor

​
Configure Google Pay

Set up your Google Pay merchant credentials in the Dashboard.
1

Open Checkout settings

Go to Dashboard → Checkout and select Google Pay from the payment methods list.
2

Enter your Google Pay merchant credentials

Provide your Merchant Name and Merchant ID in the Google Pay Settings section. These values come from the Google Pay & Wallet Console — your Merchant ID appears in the top-right corner of the console after you create your Business Profile. This is the Google-issued merchantInfo.merchantId, not a processor-specific identifier such as gatewayMerchantId.
3

Publish changes

Click Publish to apply the configuration. The SDK picks up the new setting on the next checkout load.
Test in Sandbox before enabling in Production. Verify that payments complete successfully and 3DS triggers as expected.

​
Checkout Implementation

The PayNext Checkout SDK handles the entire Google Pay integration — including token acquisition, tokenizationSpecification parameters, supported card networks, and authentication methods (PAN_ONLY, CRYPTOGRAM_3DS). No direct interaction with the Google Pay API is required.
PayNext currently supports Visa and Mastercard through Google Pay. Other card networks (such as Amex or Discover) are not supported at this time.
The SDK automatically sets gateway to paynext and gatewayMerchantId to your PayNext merchant identifier inside the tokenizationSpecification. These values tell Google Pay to route the encrypted token through PayNext’s gateway. You do not need to configure or override them — if you inspect the PaymentMethodTokenizationSpecification in the browser, these are the values you will see. Google Pay buttons render automatically when PayNext detects support from at least one connected processor and the customer’s device meets Google Pay requirements. You control the checkout experience at a high level through configuration passed to the mount method — see Getting Started for the mounting flow and Customize Checkout Behavior for available options.

​
Testing

​
Switch to Sandbox

  1. In the Dashboard, switch the environment to Sandbox using the environment toggle in the bottom-left corner.
  2. In the SDK, pass environment: 'sandbox' to the mount method — see Getting Started for details. The SDK automatically sets Google Pay to TEST mode when running in Sandbox.
In TEST mode, the Google Pay payment sheet displays mock test cards instead of real cards. No actual charges are made.

​
Test card suite

Google provides a built-in test card suite that appears automatically in the TEST environment. These test cards return mock PAN_ONLY or CRYPTOGRAM_3DS tokens depending on your configuration. For processor-specific test cards, refer to your processor’s documentation:

​
Verification

  • Use Chrome (Desktop) or an Android device to complete test payment flows
  • Confirm the currency matches your merchant account configuration
  • Verify that PayNext records the Google Pay wallet in the payment timeline and that Workflows execute as expected (including 3DS, where applicable)
  • Review the Google Pay Web integration checklist before going to production

​
3DS Behavior

Google Pay behavior depends on how the card is tokenized:
  • CRYPTOGRAM_3DS (device-tokenized cards on Android): 3DS is embedded natively with biometric authentication. The first charge includes a wallet-generated 3DS cryptogram, and all subsequent payments use exemptions. is not supported, as these flows rely on MIT exemptions. No additional 3DS configuration is required for these tokens.
  • PAN_ONLY (raw card data): These tokens contain raw card credentials without embedded 3DS. 3DS is not applied by default — PayNext only runs 3DS when a Workflow rule explicitly enables it. Configure your 3DS rules in Dashboard → Workflows, where each rule includes a mode (No 3DS, Adaptive 3DS, or Frictionless 3DS). When a PAN_ONLY token matches a rule with 3DS enabled, PayNext runs interactive 3DS authentication before processing the payment. If no Workflow rule matches or all rules are set to No 3DS, the payment proceeds without 3DS. See Workflows for setup instructions.
See the 3D Secure guide for full details on wallet authentication behavior and Workflows for configuring 3DS rules.

​
Resources