Wallet payment sheet (Apple Pay, Google Pay)
Takes a card payment through the OS wallet with biometric confirm.
In one line
Can charge you through Apple Pay or Google Pay without seeing your card number
Takes a card payment through the OS wallet with biometric confirm.
A merchant gets a payment token, not the card number. The wallet also reveals shipping and contact details the person chooses to share.
What it can and can't do
What the user does: You tap Apple Pay or Google Pay at checkout and confirm with Face ID, fingerprint or PIN
It can
- Receive a payment token instead of your card number
- Ask for shipping and contact details that you choose to share
- Take one payment each time you confirm the sheet
- Use it for physical goods and services
It cannot
- Charge you without your Face ID, fingerprint or PIN
- See your other cards in the wallet
- Get the details you hold back on the sheet
How it differs between platforms: Apple Pay on the web in Safari uses the same sheet; Android uses the Google Pay sheet with fingerprint or PIN.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| First version | Android 5.0 (API 21) | iOS 8.0 |
| Permission or entitlement | None; Google Pay merchant profile and API | com.apple.developer.in-app-payments (merchant ID) |
| Protection level | none | entitlement |
| How access is granted | prompt | prompt |
| What the user sees | Google Pay sheet with fingerprint or PIN | Apple Pay sheet with Face ID; shipping and contact fields |
| How long it lasts | Per transaction | Per transaction |
| How to take it back | Google Wallet > Payment methods | Wallet & Apple Pay settings |
| Store policy | Play: Payments policy; physical goods are not charged a store commission | App Review 3.1.5 allows physical goods and services via Apple Pay |
| API | Google Pay API (com.google.android.gms.wallet), PaymentsClient | PassKit PKPaymentAuthorizationController, PKPaymentRequest |
| Notes | Used for physical goods and services outside Play Billing. | Apple Pay via the web in Safari uses the same sheet. |
Data you get
What comes back: Payment token
Shape: object
How often: per transaction
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
token | binary | encrypted | per merchant | n/a |
Technical limits
- Digital goods must use IAP on Apple and Play Billing on Google unless an exception applies
The story
What it is
A phone pop up that pays with a saved card using Face ID, a fingerprint or a PIN.
For you
A sheet slides up showing your card, shipping address and total. You look at the phone or tap a finger to confirm. It feels much faster than typing card numbers.
For makers
Checkout becomes one step, which means fewer abandoned carts. The shop gets a one time token instead of the card number, which lowers fraud and the cost of storing card data. It can also hand over your name, email and address if you allow it.
Where you see it
| Type | Example | Apps |
|---|---|---|
| shopping | You buy shoes on a shop's app and finish checkout with Face ID in two seconds. | Nike, Amazon |
| rideshare | You pay for a ride at the end of the trip with a saved card and no card fields. | Uber, Lyft |
| delivery | You order a pizza and the sheet fills in your address from your wallet. | DoorDash, Domino's |
| games | You buy a battle pass in a mobile game without typing a card number, so the impulse purchase is easy. | Roblox |
| travel | You book a hotel and pay in a tap, with the receipt sent to the email the wallet shared. | Booking.com |
| payments | You split a dinner bill or tip a street musician online with a wallet button. | None named |
| security | The bank checks that the phone and the face match before it approves the payment. | None named |
Risks
- Easy impulse buying
- Shares name and address
- Card tokens still linked to you
Android and iPhone in short
- Android: Google Pay is also used for physical goods and services outside Google Play's own billing.
- iPhone: Apple Pay on the web in Safari uses the same sheet, so the experience matches across devices.
What the platform says
- Apple: Apple Pay. A safer, faster way to pay in apps and on websites using Face ID or Touch ID. The shop never sees your card number.
- Google: Google Pay. Pay with cards saved to your Google account in apps, on websites and in stores.
Good uses and abuse
Legitimate uses
- E-commerce checkout
- Ride hailing
Known abuse
- Card testing with stolen tokens
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 | 1 | Rough identifying entropy, when known |
History
- 2014-09, iPhone iOS 8: Apple Pay in apps
- 2015-09, Android Android Pay: Android Pay launched; became Google Pay 2018
Related capabilities
Related
- In-app purchase (StoreKit 2, Play Billing). Can sell digital items and subscriptions, after you approve each purchase
- Default contactless payment app. Can answer when you tap to pay, after you pick it as the default wallet
Same idea on the web
- Apple Pay on the web (ApplePaySession). Can start an Apple Pay payment that you confirm with Face ID or Touch ID
- Google Pay for the web. Can start a Google Pay payment that you pick a card for and approve
- Payment Request API. Can open the browser's pay sheet with saved cards and addresses you pick
Sources
How well checked: Checked against real behavior.