The German ID card works something like that. The fields you as a vendor are approved for, you can make either required or optional server-side. The user can then choose what they want to add or to abort process. It can be read either with a pin that's printed on it, or with your Personal six digit pin, depending on use case.
You can tell it to just do an age check (has completed nth year) or a place check (lives in community with x ID) and it'll just return yes or no. There's also a pseudonym function that returns a unique ID per card+vendor combination (so the same vendor can tell it's the same ID again, but a different vendor would receive a different ID).
I can't see it used in night clubs though. There's a staggering amount of requirements you have to meet in order to receive certification to go to one of the handful of service providers that meet even more requirements to run a secure server that are connected to the PKI allowed to talk to the ID card.
You can tell it to just do an age check (has completed nth year) or a place check (lives in community with x ID) and it'll just return yes or no. There's also a pseudonym function that returns a unique ID per card+vendor combination (so the same vendor can tell it's the same ID again, but a different vendor would receive a different ID).
I can't see it used in night clubs though. There's a staggering amount of requirements you have to meet in order to receive certification to go to one of the handful of service providers that meet even more requirements to run a secure server that are connected to the PKI allowed to talk to the ID card.