Payment Request API
Opens the browser's native pay sheet with saved cards and addresses.
In one line
Can open the browser's pay sheet with saved cards and addresses you pick
Opens the browser's native pay sheet with saved cards and addresses.
The site sees only what the person approves: card or wallet token, shipping, email and phone if requested.
What it can and can't do
What the user does: You tap Pay or a wallet button at checkout.
It can
- Show a pay sheet with your saved cards, wallets and addresses
- Ask for your name, email, phone and shipping address
- Send the store the details you approve
It cannot
- See all your saved cards at once
- Pay without you tapping Pay in the sheet
- Work the same in every browser; some show a limited sheet
- Keep the details after the payment ends
How it differs between platforms: Chrome, Edge, Safari and Samsung Internet show it. Firefox shows only a partial version.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 60 | 2017-07-25 | None |
| Edge | Supported | 15 | 2017-04-05 | None |
| Firefox | Behind a flag | 55 | Not listed | Behind a flag |
| Safari | Supported | 11.1 | 2018-04-12 | None |
| Safari on iPhone | Supported | 11.3 | 2018-03-29 | None |
| Chrome on Android | Supported | 53 | 2016-09-07 | None |
| Samsung Internet | Supported | 6.0 | 2017-08-23 | Chrome Android 53 |
How a site asks for it
| API | new PaymentRequest(methodData, details, options).show(), canMakePayment(), hasEnrolledInstrument() |
| Permissions policy | payment |
| Browser compat keys | api.PaymentRequest |
| How access is granted | prompt |
| What the user sees | Browser payment sheet listing cards, addresses and wallets |
| 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: Opens the browser's native pay sheet with saved cards and addresses.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
methodName | string | None | basic-card (removed), https://google.com/pay, https://apple.com/apple-pay, secure-payment-confirmation | Not listed |
details | object | None | token or card data | per handler |
shippingAddress | object | None | country, region, city, postalCode, recipient, phone | if requestShipping |
payerEmail / payerPhone / payerName | string | None | free text | if requested |
Technical limits
- Must be called from a user gesture
- Only methods the browser supports
- Merchant never sees the full card number from Chrome autofill without CVC
The story
What it is
The browser shows its own pay sheet with your saved cards and address.
For you
A pay sheet pops up from the browser with your saved cards and address. You pick, confirm and you are done without retyping.
For makers
Makers get faster checkouts and fewer typing errors. The browser holds the card, so the shop can lean on it for trusted wallets like Google Pay and Apple Pay.
Where you see it
| Type | Example | Apps |
|---|---|---|
| shopping | A store opens the browser pay sheet and finishes your order in one step. | Shopify stores |
| delivery | A takeout site fills your address and card from the browser. | None named |
| travel | A booking site reads your name and email from the sheet. | None named |
| games | A game store buys coins with a saved card. | None named |
| security | A shop only sees a token and not the full card number. | None named |
| media | A news site sells an annual pass in one tap. | None named |
Risks
- Easy overspending
- Shares contact details
What the platform says
- Mozilla: Payment Request API. MDN says the API gives a consistent checkout flow, with the browser handling the payment sheet.
Good uses and abuse
Legitimate uses
- One tap checkout
Known abuse
- Skimmers if site is compromised
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
- 2016, Chrome 53: Payment Request ships on Chrome Android
- 2017, Chrome 60: Desktop
- 2017-09, Safari 11.1: Safari via Apple Pay
- 2022, Chrome: basic-card deprecated; Google Pay and other handlers remain
Sources
How well checked: Checked against real behavior.