Google Pay for the web
Pays with a Google Pay card through a Google button or Payment Request.
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
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Supported | Not available | None |
| Edge | Supported | Not available | None |
| Firefox | Supported | Not available | JS button works |
| Safari | Supported | Not available | JS button works |
| Safari on iPhone | Supported | Not available | None |
| Chrome on Android | Supported | Not available | None |
| Samsung Internet | Supported | Not available | None |
How a site asks for it
| API | google.payments.api.PaymentsClient.loadPaymentData(), or PaymentRequest method https://google.com/pay |
| How access is granted | prompt |
| What the user sees | Google Pay sheet with card selection |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | Yes |
| How long it lasts | Per origin |
| How to take it back | Site settings |
| Inside an iframe | Same as top level; cross-origin iframes need a permissions policy where listed |
Typical flow
- Call the API
- Browser applies its access rules
- 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
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
paymentMethodData.tokenizationData.token | string | None | PSP encrypted token | Not listed |
email, shippingAddress | object | None | per request | Not 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
| Type | Example | Apps |
|---|---|---|
| shopping | You buy a gift on a retail site in two taps. | Etsy, Shopify stores |
| delivery | A food order site finishes checkout with Google Pay. | DoorDash |
| travel | A booking site fills your saved card and address in one step. | Booking.com |
| games | A web game store buys gems with Google Pay. | None named |
| media | A streaming site signs you up for a plan in one tap. | None named |
| security | A fraud team gets tokenized cards that are harder to steal. | None named |
Risks
- Easy overspending
- Shared with Google
What the platform says
- Google: Google Pay API for the web. Google says the Google Pay API lets customers pay with cards saved to their Google Account.
Good uses and abuse
Legitimate uses
- Checkout
Known abuse
- None notable
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 5 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 2 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2018, Chrome: Google Pay API for web launches
Sources
How well checked: Based on official documentation.