Skip to Content
Platform.Ontology

Secure Payment Confirmation

Authenticates a card payment with a passkey inside the browser.

Works without askingPayments and shoppingCheckoutWeb browsersWhile you use it

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

BrowserStatusFirst versionReleasedNote
ChromeSupported602017-07-25capabilities 148
EdgeSupported152017-04-05None
FirefoxNot supportedNot availableNot listedNone
SafariNot supportedNot availableNot listedNone
Safari on iPhoneNot supportedNot availableNot listedNone
Chrome on AndroidSupported532016-09-07None
Samsung InternetNot supportedNot availableNot listedNone

How a site asks for it

APIPaymentRequest with method secure-payment-confirmation, securePaymentConfirmationAvailability, getSecurePaymentConfirmationCapabilities
Permissions policypayment
Browser compat keysapi.PaymentRequest
How access is grantedprompt
What the user seesBrowser sheet showing merchant and amount; needs passkey
Needs a secure context (HTTPS)Yes
Needs a user gestureYes
How long it lastsPer origin
How to take it backSite settings
Inside an iframeSame as top level; cross-origin iframes need a permissions policy where listed

Typical flow

  1. Call the API
  2. Browser applies its access rules
  3. 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

FieldTypeUnitRangePrecision
credentialIdslistNonebinary idsNot listed
payeeOriginstringNoneoriginNot listed
totalobjectNonecurrency and valueNot 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

TypeExampleApps
bankingA bank confirms an online card payment with your fingerprint instead of an SMS code.None named
shoppingA retailer sees fewer failed checkouts because people no longer wait for a code.None named
travelAn airline confirms a high value booking with a passkey.None named
securityFraud teams get a cryptographic proof that the real card owner approved.None named
paymentsA card network lets a bank run its own check with no redirect.Visa, Mastercard
gamesA game store confirms a large purchase with your face.None named

Risks

  • Only some banks
  • Only Chromium browsers

What the platform says

Good uses and abuse

Legitimate uses

  • Strong customer authentication

Known abuse

  • None notable

Scores

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

  • 2024-07, Chrome 139: securePaymentConfirmationAvailability
  • 2026-05, Chrome 148: getSecurePaymentConfirmationCapabilities

Sources

How well checked: Based on official documentation.

On this page