Skip to Content
Platform.Ontology

Google Pay for the web

Pays with a Google Pay card through a Google button or Payment Request.

Works without askingPayments and shoppingCheckoutWeb browsersWhile you use it

In one line

Can start a Google Pay payment that you pick a card for and approve

Pays with a Google Pay card through a Google button or Payment Request.

Returns a tokenized card to the merchant's PSP after the person approves.

What it can and can't do

What the user does: You tap the Google Pay button at checkout and pick a card.

It can

  • Show the Google Pay sheet with your saved cards and addresses
  • Send the store a one time payment code once you approve
  • Share your name, email or address if you allow it

It cannot

  • See your real card number in most set ups
  • Pay without you picking a card and approving
  • Use a card you did not choose to save
  • Keep a payment going after you close the sheet

Browser support

BrowserStatusFirst versionNote
ChromeSupportedNot availableNone
EdgeSupportedNot availableNone
FirefoxSupportedNot availableJS button works
SafariSupportedNot availableJS button works
Safari on iPhoneSupportedNot availableNone
Chrome on AndroidSupportedNot availableNone
Samsung InternetSupportedNot availableNone

How a site asks for it

APIgoogle.payments.api.PaymentsClient.loadPaymentData(), or PaymentRequest method https://google.com/pay
How access is grantedprompt
What the user seesGoogle Pay sheet with card selection
Needs a secure context (HTTPS)Yes
Needs a user gestureYes
How long it lastsPer origin
How to take it backSite settings
Inside an iframeSame as top level; cross-origin iframes need a permissions policy where listed

Typical flow

  1. Call the API
  2. Browser applies its access rules
  3. Page receives the result

Data you get

What comes back: Pays with a Google Pay card through a Google button or Payment Request.
Shape: object
How often: on demand

FieldTypeUnitRangePrecision
paymentMethodData.tokenizationData.tokenstringNonePSP encrypted tokenNot listed
email, shippingAddressobjectNoneper requestNot listed

Technical limits

  • Needs Google account and saved card
  • Merchant must be approved by Google

The story

What it is

Pay with a card saved in your Google account in one tap.

For you

You tap a Google Pay button, pick a card and confirm. The shop gets a secure token and does not see your full card number.

For makers

Makers use it to cut checkout steps and card typing, which lifts sales. It works across browsers, not just Chrome.

Where you see it

TypeExampleApps
shoppingYou buy a gift on a retail site in two taps.Etsy, Shopify stores
deliveryA food order site finishes checkout with Google Pay.DoorDash
travelA booking site fills your saved card and address in one step.Booking.com
gamesA web game store buys gems with Google Pay.None named
mediaA streaming site signs you up for a plan in one tap.None named
securityA fraud team gets tokenized cards that are harder to steal.None named

Risks

  • Easy overspending
  • Shared with Google

What the platform says

Good uses and abuse

Legitimate uses

  • Checkout

Known abuse

  • None notable

Scores

ScoreValueMeaning
Sensitivity5 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction2 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2018, Chrome: Google Pay API for web launches

Sources

How well checked: Based on official documentation.

On this page