Separate hasEnrolledInstrument() calls should be used to query whether a user has a Google Pay wallet and whether they have cards in the autofill database. This ability is supported without letting sites iterate payment instruments within these locations. Previously Chrome would reject PaymentRequest.hasEnrolledInstrument() with NotAllowedError if a website queried different payment methods or different payment method specific parameters within a span of 30 minutes.

Status in Chromium

Blink>Payments


Origin trial (tracking bug) in:

  • Chrome for desktop release 74
  • Chrome for Android release 74

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No signal
  • No signal
  • No signal
  • Strongly positive

Owner

Comments

Now Chrome allows querying different payment methods, as long as the payment method specific parameters remain the same. This allows the website to query user wallets (e.g., to present wallet-branded buttons on the webpage), but not to iterate individual instruments in a wallet.

Last updated on 2020-11-09