Google Pay

Accept Google Pay through Ecrypt's hosted checkout products.

Google Pay lets shoppers check out with any credit or debit card saved to their Google Account. Ecrypt handles the wallet flow on our hosted pages, allowing you to enable Google Pay without building or certifying the wallet integration yourself.

At a glance

Where Google Pay is available in Ecrypt

Google Pay is currently offered only through Ecrypt's hosted checkout surfaces. When a shopper lands on one of these pages from a compatible device and browser, the Google Pay button renders automatically alongside the standard card form:

• Dynamic Checkout: full-featured, hosted checkout page created with the /v1/dynamiccheckout endpoint.
• Hosted iFrame: Populate Google Pay in Ecrypt's hosted iFrame underneath card fields.
• Payment Links: shareable URLs that accept a single payment or kick off a subscription.
• Invoices: customer-facing invoice pages with a pay-now action.

No domain registration needed

Some processors require merchants to register every domain that displays a Google Pay button. Because the button renders on pages served from Ecrypt's own domain, you don't need to register anything. You can embed Dynamic Checkout in an iframe on your own site, email a Payment Link, or send an Invoice, and Google Pay will show up without additional setup.

Accepting inbound international payments

Ecrypt accepts Google Pay from shoppers in any country where Google Wallet operates. The cardholder selects their saved Google Wallet card, and Ecrypt processes it as a standard card transaction. Settlement happens in USD to your merchant account, following your normal funding schedule.

For an up-to-date list of countries where shoppers can use Google Wallet, see Google's supported countries list.

Recurring billing and subscriptions

Google Pay works with Ecrypt subscriptions. When a customer completes their first payment through Dynamic Checkout that includes a subscription object, the resulting payment credential is saved to the customer's wallet and reused for each recurring charge on the cycle you define.

Once the initial Google Pay charge succeeds, Ecrypt stores the customer's tokenized payment method and handles every subsequent billing cycle automatically. No extra work is needed on your end to flag the payment as recurring Ecrypt marks the stored credential appropriately so follow-on charges run as merchant-initiated transactions.

For details on cycle types and billing dates, see the Subscriptions reference.

Post-payment operations

Google Pay transactions settle as standard card transactions in Ecrypt, so you can manage them exactly like any other credit card charge. Refunds (full or partial), voids on unsettled authorizations, and chargeback responses all run through the same endpoints and dashboard workflows you already use for card payments. Google Pay transactions also appear in reporting with the paymentNetwork set to the underlying card brand (Visa, Mastercard, and so on), making them easy to reconcile alongside your other card volume.

Data Verification

Payment Data
Ecrypt handles the generation of the PaymentDataRequest and manages the encrypted payloads securely. Merchants are not required to manually configure variables like gateway IDs, card networks, authorization methods, etc.

Billing Address Data
Ecrypt automatically configures the BillingAddressParameters within the Google Pay payment sheet. Dynamic Checkout collects the buyer's billing address directly and securely for address verification. No additional code or custom billing address configuration is required on the merchant's end to process these transactions.

Testing

To test the Google Pay flow end-to-end:

1. Generate a Dynamic Checkout, Payment Link, or Invoice in your Ecrypt sandbox environment.
2. Open the resulting URL on a physical Android device, or in Chrome on a desktop logged into a Google account that has at least one card saved to Google Wallet.
3. Complete the flow using Google's test card suite or a real card saved to your Google Wallet (sandbox charges are not settled).

Google Pay will only render on devices and browsers that meet Google's own eligibility rules: an HTTPS connection, a supported browser, and a Google account with a saved card. If the button doesn't appear, those are the first things to check.

Embedding Dynamic Checkout in an iFrame

If you're testing Dynamic Checkout inside an <iframe> on your own page, the Google Pay sheet opens in a pop-up that runs scripts and forms from Google's domain. Browsers will block it unless your iFrame's sandbox attribute grants the right permissions. At minimum, include:

<iframe
  src="https://shop.ecrypt.com/..."
  allow="payment *"
  sandbox="allow-popups allow-popups-to-escape-sandbox allow-same-origin allow-scripts allow-forms"
  title="Checkout page"
  width="400"
  height="300">
</iframe>

• allow-popups and allow-popups-to-escape-sandbox let the Google Pay window open and operate on Google's domain.
• allow-same-origin is required so Ecrypt's checkout page can talk to its own origin.
• allow-scripts and allow-forms are required for the page itself to function.
• allow="payment" enables the Payment Request API that Google Pay relies on.

The simplest option is omitting the sandbox attribute entirely. This gives the iFrame full permissions. Only use sandbox if you have a specific reason to restrict what the frame can do.

Turn Google Pay on

The Ecrypt team activates Google Pay by request. Reach out to your Ecrypt account representative or contact support to get started.

Merchants using Ecrypt's hosted checkout with Google Pay enabled are required to adhere to the Google Pay and Wallet API's Acceptable Use Policy and accept the Google Pay API Terms of Service.

Resources from Google Pay

• Google Pay Web Developer Documentation
• Google Pay Web Integration Checklist
• Google Pay Web Brand Guidelines