The basic premise is to leverage your bank (who already has had to perform KYC on you to open an account) to attest to your age for age-restricted merchant sites (pornhub, gambling, etc) without sharing any more information than necessary.
Flow works like this:
1) You go to gambling.com
2) They request you to verify your age
3) You choose "Bank Verification"
4) You trigger a WebAuthn Credential Creation flow
5) gambling.com gives you a string to copy
-------------
6) You log into your bank
7) You go to bank.com/age-verify
8) You paste in the string you were given
9) The bank verifies it/you and creates a signed payload with your age-claims (over_18: true, over_21: false)
10) You copy this and go back to gambling.com
---------------
11) You paste the string back into gambling.com
12) You perform WebAuthn Auth flow
13) gambling.com verifies everything (signatures, webauthn, etc)
14) gambling.com sets a session-cookie and _STRONGLY_ encourages you to create an account (with a pass key). This will prevent you from having to verify your age every time you visit gambling.com
The mechanics might feel off, but it feels like this in the neighborhood of a way to perform anonymous age verification.
This is virtually free, and requires extremely light infra. Banks can be incentivized with small payments, or offer it because everyone else does and don't want to get left behind.
I give that to you, chases signature is valid but you can't perform webauthn auth.
Thats why you cant sell spun up credentials en masse.
I could definitely share any webauthn account with anyone of my choice if I wanted to. Just store the generated key in a shared webauthn vault.
You can go spec-incompliant and tell the browser to only accept certain types of hardware to store your credential, but unless the entire ecosystem maintains lists of compromised hardware and blocks half the desktop user base for defeated TPM mechanisms, you're going to have to deal with spoofed clients. The only reason spoofed TPM/hardware backed credential stores aren't a problem for webauthn right now is that there is no need to spoof them at the moment.