Skip to Content
Platform.Ontology

Stored payment and address data

Saved cards and addresses a browser, wallet or the site itself can fill at checkout.

Works without askingPayments and shoppingCheckoutWeb browsersWhen you are signed inWhile you use it

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

BrowserStatusFirst versionReleasedNote
ChromeSupported602017-07-25None
EdgeSupported152017-04-05None
FirefoxNot supportedNot availableNot listedAutofill only
SafariSupported11.12018-04-12:Apple Pay only
Safari on iPhoneSupported11.32018-03-29:Apple Pay only
Chrome on AndroidSupported532016-09-07None
Samsung InternetSupported6.02017-08-23None

How a site asks for it

APIPayment Request API: new PaymentRequest(methods, details).show(); autocomplete tokens cc-number, shipping address
Permissions policypayment
Browser compat keysapi.PaymentRequest
How access is grantedprompt
What the user seesBrowser or wallet payment sheet
Needs a secure context (HTTPS)Yes
Needs a user gestureYes
How long it lastsSaved in the browser profile or wallet until deleted; merchant tokens until revoked
How to take it backClear site data, browser privacy settings
Inside an iframeNot listed

Typical flow

  1. Site calls PaymentRequest.show from a click
  2. Browser shows saved cards and addresses
  3. Person approves
  4. 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

TypeExampleApps
shoppingYour saved address and card fill the form in one tap on a store.Amazon, Etsy
deliveryA takeout app remembers your address and card for next time.DoorDash, Uber Eats
travelA booking site fills passenger info and your card.Booking.com
mediaA subscription site bills you every month from the saved card.Netflix, Spotify
securityA skimmer script on a checkout page tries to read the filled fields.None named
paymentsA wallet app offers its saved cards across many shops.PayPal, Shop Pay

Risks

  • Skimmer scripts
  • Data kept long term

What the platform says

Good uses and abuse

Legitimate uses

  • Fast checkout

Known abuse

  • Harvesting hidden autofilled fields, card testing

Scores

ScoreValueMeaning
Sensitivity5 of 5How revealing the data is
Utility5 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

  • 2016-09, Chrome 53: Payment Request shipped
  • 2017-01, all: Autofill phishing demo with hidden fields (Kuosmanen)

Sources

How well checked: Based on official documentation.

On this page