Google Pay can be used in Recurly.js to generate a Recurly token for checkout flows where your payment gateway is configured to accept Google Pay transactions. This article covers common setup pitfalls and how to troubleshoot when the Google Pay button does not appear or payments fail.
Key takeaway: Google Pay availability depends on gateway enablement, merchant IDs, and browser/device support.
Known limitation
Google Pay is not supported on Recurly Checkout or Hosted Payment Pages. It is intended for Recurly.js implementations.
Prerequisites checklist
- Gateway support: Your configured gateway must be enabled for Google Pay.
- Merchant IDs: You need a valid Google Merchant ID (and gateway-specific configuration such as Braintree authorization, if applicable).
- Browser/device support: Customer must use a compatible browser/device for Google Pay on the web.
- HTTPS: Your checkout must be served over HTTPS.
- Token lifetime: Google Pay tokens follow standard Recurly token reuse windows; create and use the token promptly.
Symptoms and fixes
Google Pay button does not render
- Cause: Browser/device not supported or customer not “ready to pay.”
- Fix: Test with Chrome on a supported device with Google Wallet set up and an eligible card.
- Cause: Gateway not enabled for Google Pay.
- Fix: Confirm Google Pay is enabled at both the gateway and Recurly configuration level.
- Cause: Missing/incorrect merchant identifiers.
- Fix: Validate your Google Merchant ID and gateway-specific keys/authorizations.
Customer can click Google Pay but payment fails
- Cause: Gateway declines / issuer declines.
- Fix: Check the transaction error details in Recurly and the gateway dashboard for the decline reason.
- Cause: Configuration mismatch between environments (sandbox vs production).
- Fix: Ensure your merchant IDs/credentials correspond to the environment being tested.
- Cause: Using a return-customer flow that bypasses Recurly.js.
- Fix: For customer-initiated Google Pay transactions, use Recurly.js to collect the necessary device-related data.
Intermittent failures or “it works on my machine”
- Cause: WAF/CDN blocking third-party requests or strict browser privacy settings.
- Fix: Review browser console errors, network requests, and any blocked scripts/resources.
- Cause: Long delays between token creation and API usage.
- Fix: Generate the token right before submitting your create subscription / purchase request.
What to gather before contacting Support
- Recurly site subdomain and environment (sandbox or production)
- Gateway name and confirmation that Google Pay is enabled at the gateway
- Timestamp of the attempt and the Recurly account code
- Browser/device details (Chrome version, OS, mobile/desktop)
- Console/network errors (screenshots) and any transaction error messages shown in Recurly
Comments
0 comments
Please sign in to leave a comment.