HomeProduct DocsAPI ReferenceChangelog
RecurlyAPI GuidesRecurly.jsWebhooksAPI ReferenceSupportBook demo
Product Docs
RecurlyAPI GuidesRecurly.jsWebhooksAPI ReferenceSupportBook demo

Google Pay™

Accept Google Pay™ payments on Recurly through Stripe, Adyen, Braintree, Worldpay, CyberSource, Commerce Hub, or Chase Orbital — available in Google Chrome on web and Android devices.

Google Pay™ lets customers pay using preferred payment methods stored in their Google account — without entering card details each time. It works in Google Chrome on the web and on Android devices, and integrates with Recurly via Recurly.js.
Available on all Recurly plans
1Definition 2Key details

Prerequisites

Limitations

  • Google Pay™ works in Google Chrome only — other browsers are not supported.
  • Google Pay™ is not currently supported on Recurly Checkout or Hosted Payment Pages.

Definition

Google Pay™ is a digital wallet payment method that lets customers complete transactions using payment details stored in their Google account. It simplifies checkout on Google Chrome (web) and Android devices. Recurly integrates Google Pay™ via Recurly.js — see the Recurly.js Google Pay documentation for integration details.
Note The Google Pay standalone app was deprecated by Google on June 4, 2024. This does not affect the payment method itself — customers can continue to pay with Google Pay through the Google Wallet app.

Key details

Use cases

Web purchases — Customers can use Google Pay™ for transactions in Google Chrome without entering card details.

Android transactions — Customers on Android devices can pay quickly using their stored Google Pay credentials.

Token types

FPAN — Funding Primary Account Number

The actual credit card number physically printed on the card. Also referred to as PAN.

DPAN — Device Primary Account Number

A tokenized card number created when a consumer adds a card to a device wallet (e.g., Google Wallet). DPANs are sent to gateways in place of the actual FPAN.

  • Tied to a specific device (e.g., a specific Android phone or tablet) and accompanied by a Cryptogram when the customer is in session.
  • DPANs are full card numbers with different digits from the FPAN, and can appear on receipts and other UI elements.
  • DPANs are invalidated when a consumer removes the card from their device. If they re-add the same card or add a new one, a new DPAN is created. Subscriptions using a DPAN can fail due to this consumer-driven behavior and are non-recoverable.
Cryptogram

A one-time authentication value generated during a Google Pay transaction. Cryptograms are not stored and must be sent on all customer-initiated transactions.

Best practices

  • Return customers — Use Recurly.js even when an existing account code or billing info is already on file. Recurly.js collects the device-related data (cryptograms) required for customer-initiated Google Pay transactions.

Updated 7 days ago

Did this page help you?