Secure Payment Confirmation
Authenticates a card payment with a passkey inside the browser.
In one line
Can confirm a card payment with a passkey that you approve in the browser
Authenticates a card payment with a passkey inside the browser.
Binds a WebAuthn credential to a payment so banks can confirm the person approved this exact amount.
What it can and can't do
What the user does: You tap Pay, then confirm with your fingerprint, face or device PIN.
It can
- Show the shop name and amount before you confirm
- Check you with a passkey that your bank set up
- Send the bank proof that you approved this payment
It cannot
- Take payment without your passkey
- Work before you set up a passkey with your bank
- Work in Safari, Firefox or on iPhone
- See your card number
How it differs between platforms: Chrome and Edge support it. Safari and Firefox do not.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 60 | 2017-07-25 | capabilities 148 |
| Edge | Supported | 15 | 2017-04-05 | None |
| Firefox | Not supported | Not available | Not listed | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Supported | 53 | 2016-09-07 | None |
| Samsung Internet | Not supported | Not available | Not listed | None |
How a site asks for it
| API | PaymentRequest with method secure-payment-confirmation, securePaymentConfirmationAvailability, getSecurePaymentConfirmationCapabilities |
| Permissions policy | payment |
| Browser compat keys | api.PaymentRequest |
| How access is granted | prompt |
| What the user sees | Browser sheet showing merchant and amount; needs passkey |
| 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: Authenticates a card payment with a passkey inside the browser.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
credentialIds | list | None | binary ids | Not listed |
payeeOrigin | string | None | origin | Not listed |
total | object | None | currency and value | Not listed |
Technical limits
- Chromium only
- Needs registered credentials
The story
What it is
Confirm a card payment with a passkey or fingerprint, right in the browser.
For you
At checkout, a sheet shows the shop and amount and asks for your fingerprint or face. It replaces text message codes you have to type.
For makers
Banks and card networks want it because it makes card fraud harder and cuts abandoned checkouts. It is part of the 3D Secure rules for online card payments.
Where you see it
| Type | Example | Apps |
|---|---|---|
| banking | A bank confirms an online card payment with your fingerprint instead of an SMS code. | None named |
| shopping | A retailer sees fewer failed checkouts because people no longer wait for a code. | None named |
| travel | An airline confirms a high value booking with a passkey. | None named |
| security | Fraud teams get a cryptographic proof that the real card owner approved. | None named |
| payments | A card network lets a bank run its own check with no redirect. | Visa, Mastercard |
| games | A game store confirms a large purchase with your face. | None named |
Risks
- Only some banks
- Only Chromium browsers
What the platform says
- Google: Secure Payment Confirmation. Chrome's docs say it lets banks confirm a card payment with a passkey, with a consistent, secure pay sheet.
Good uses and abuse
Legitimate uses
- Strong customer authentication
Known abuse
- None notable
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 3 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
- 2024-07, Chrome 139: securePaymentConfirmationAvailability
- 2026-05, Chrome 148: getSecurePaymentConfirmationCapabilities
Sources
How well checked: Based on official documentation.