Stored payment and address data
Saved cards and addresses a browser, wallet or the site itself can fill at checkout.
In one line
Can fill in saved cards and addresses at checkout, if you choose them
Saved cards and addresses a browser, wallet or the site itself can fill at checkout.
Browser autofill fills a saved card only after the person picks it, and often asks for the CVC. Apple Pay and Google Pay give the merchant a tokenised card, not the card number. Sites that store cards keep tokens from a payment provider.
What it can and can't do
What the user does: You tap a field at checkout, pick a saved card or address, or tap a wallet button.
It can
- Fill your name, address and card from the browser, a wallet or the site
- Offer a saved card from your account on that site
- Fill a billing or shipping address in one tap
It cannot
- See all your saved cards without you choosing one
- Fill your security code (CVC) without asking you in many browsers
- Share your saved cards with other sites
- Fill anything if you turned autofill off
How it differs between platforms: Chrome and Safari fill saved cards and addresses. Firefox only fills addresses in many cases.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 60 | 2017-07-25 | None |
| Edge | Supported | 15 | 2017-04-05 | None |
| Firefox | Not supported | Not available | Not listed | Autofill only |
| Safari | Supported | 11.1 | 2018-04-12 | :Apple Pay only |
| Safari on iPhone | Supported | 11.3 | 2018-03-29 | :Apple Pay only |
| Chrome on Android | Supported | 53 | 2016-09-07 | None |
| Samsung Internet | Supported | 6.0 | 2017-08-23 | None |
How a site asks for it
| API | Payment Request API: new PaymentRequest(methods, details).show(); autocomplete tokens cc-number, shipping address |
| Permissions policy | payment |
| Browser compat keys | api.PaymentRequest |
| How access is granted | prompt |
| What the user sees | Browser or wallet payment sheet |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | Yes |
| How long it lasts | Saved in the browser profile or wallet until deleted; merchant tokens until revoked |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Typical flow
- Site calls PaymentRequest.show from a click
- Browser shows saved cards and addresses
- Person approves
- Site receives token and address
Data you get
What comes back: Card token, billing and shipping address
Shape: object
How often: per checkout
No individual data fields. The signal is the access itself.
Technical limits
- Merchant gets a device token (DPAN) with Apple Pay not the card number
- Payment Request needs a user gesture and HTTPS
- Autofill phishing: hidden fields can be filled after one click on a visible field
The story
What it is
Saved cards and addresses can be filled in at checkout.
For you
Checkout forms fill your name, address and card in a tap. It saves time, but your data sits in your browser, wallet or the shop's account.
For makers
Makers get faster checkouts and fewer typing mistakes, which lifts sales. Shops that keep cards on file also get easy repeat buying and subscription billing.
Where you see it
| Type | Example | Apps |
|---|---|---|
| shopping | Your saved address and card fill the form in one tap on a store. | Amazon, Etsy |
| delivery | A takeout app remembers your address and card for next time. | DoorDash, Uber Eats |
| travel | A booking site fills passenger info and your card. | Booking.com |
| media | A subscription site bills you every month from the saved card. | Netflix, Spotify |
| security | A skimmer script on a checkout page tries to read the filled fields. | None named |
| payments | A wallet app offers its saved cards across many shops. | PayPal, Shop Pay |
Risks
- Skimmer scripts
- Data kept long term
What the platform says
- Google: Payment and address form best practices. web.dev teaches how saved cards and addresses help people check out faster and make fewer errors.
Good uses and abuse
Legitimate uses
- Fast checkout
Known abuse
- Harvesting hidden autofilled fields, card testing
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 5 of 5 | How revealing the data is |
| Utility | 5 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-09, Chrome 53: Payment Request shipped
- 2017-01, all: Autofill phishing demo with hidden fields (Kuosmanen)
Related capabilities
Related
- Account profile fields. Can keep the details you typed when signing up, such as name, email and address
- Purchase history and loyalty data. Can see what you bought, when and for how much, once you are signed in
Sources
How well checked: Based on official documentation.