Google Pay

Offer eligible online customers a familiar digital-wallet checkout through a compatible NMI integration.

Google Pay with NMI lets customers select an eligible payment credential from their Google Wallet instead of manually entering card details. NMI receives the wallet data through a supported integration, tokenizes or processes it through the gateway workflow, and submits the transaction to a compatible processor.

VCCP can help confirm whether Google Pay fits your checkout, processor and recurring-payment requirements. Implementation still requires a compatible ecommerce integration and, in most cases, a qualified developer or platform provider.

Why Add Google Pay?

  • Faster data entry: Eligible customers can choose a wallet credential without typing the full card number and expiration date.
  • Familiar checkout: A recognized Google Pay button can complement card entry for supported browsers, devices and customer accounts.
  • Tokenized collection: Compatible NMI components return a payment token or supported wallet payload instead of exposing raw payment credentials to the checkout.
  • Optional contact data: Compatible integrations can request supported billing, shipping, phone or email fields when the checkout needs them.
  • One-time and eligible recurring use: Supported NMI products and processors can use Google Pay for immediate purchases and properly configured stored or recurring relationships.

Recommended Integration Paths

NMI Payment Component and REST API

NMI recommends its current Payment Component for new integrations. It can present cards, ACH, Apple Pay and Google Pay within a tokenized payment experience and submit payments through the NMI REST API.

Collect.js for Existing Integrations

Existing Collect.js integrations can render a Google Pay button and return a single-use payment token for a compatible NMI Payment API request. Collect.js can also request supported billing and shipping details.

Direct Wallet-Payload Integration

Qualified developers may pass supported encrypted or decrypted Google Pay data through an applicable NMI API workflow. This path requires careful implementation of Google and NMI requirements.

How the Checkout Works

  1. The checkout determines that Google Pay is available for the customer’s browser, device, region and wallet.
  2. The customer selects Google Pay and reviews the transaction in the Google payment sheet.
  3. Google returns an encrypted wallet payload to the supported NMI integration.
  4. The integration creates or submits the applicable tokenized payment data to NMI.
  5. NMI sends the transaction through the configured compatible processor and returns the authorization result to the application.

Setup and Compatibility

Google Pay is available without a separate Google Pay account in supported NMI integrations, but it is not automatically compatible with every processor, shopping cart, checkout product or transaction type. VCCP should confirm the processor and integration path before development begins.

  • Use a supported NMI payment component, Collect.js implementation or wallet-data API workflow.
  • Confirm processor, card-network, region, currency and transaction-type compatibility.
  • Request only the billing, shipping and contact fields the checkout actually requires.
  • Test successful, declined, canceled and unavailable-wallet scenarios before launch.
  • Keep the integration and checkout libraries current as NMI and Google requirements evolve.

Recurring and Stored-Payment Use

Eligible Google Pay credentials can support NMI subscriptions, Customer Vault records and merchant-initiated card-on-file payments when both the product and processor support digital-wallet recurring. Confirm a one-time Google Pay transaction first, preserve the original setup Transaction ID and follow the current NMI recurring-wallet requirements.

Recurring wallet support is not the same across every NMI checkout product. NMI currently identifies the Payment API and Collect.js as supported recurring-wallet paths, while Virtual Terminal, QuickClick and Collect Checkout are not supported for this recurring-wallet workflow.

Important Limitations

  • Google Pay availability depends on the customer’s device, browser, country, wallet setup and eligible payment method.
  • A wallet token does not guarantee authorization; the issuer and processor can still decline the transaction.
  • Processor support varies, particularly for recurring, stored-credential and cryptogram-based transactions.
  • Merchants remain responsible for checkout security, privacy disclosures, order validation, fraud controls and applicable PCI DSS obligations.
  • Google Pay complements card entry; it does not replace a complete checkout, refund, dispute or reconciliation process.

Related NMI Tools


Choose the Wallet Path That Fits the Checkout

Tell VCCP how your checkout is built, which processor you use and whether you need one-time, stored or recurring payments. We can help identify the appropriate NMI path before development begins.

Google Pay availability, processor compatibility, integration requirements, transaction support, pricing and approval depend on the merchant account, NMI configuration, region, card network and connected services. VCCP does not guarantee wallet availability or transaction authorization.