← Back to the chapter · Previous detail · Next detail →

Technical detail · NFC Real-World Applications

Cryptograms, tokenization, and verifier policy

19.8 Cryptograms, Tokenization, And Verifier Policy

Two independent protections stack up in tokenized contactless payment flows:

  • Dynamic cryptogram: for each transaction, the card or phone computes a unique authorization cryptogram from transaction data and a secret key. Depending on the transaction, the terminal verifies an offline cryptogram or the issuer verifies an online cryptogram. Replaying a previous tap fails because its cryptogram is stale.
  • Tokenization: a tokenized wallet stores a device account number or payment token, not the underlying card PAN. Purchases run on the token, which is bound to that device; if it leaks, the underlying card is not exposed and the token can be revoked without reissuing the card.

Together they mean a tokenized contactless credential has transaction-specific proof without exposing the underlying PAN. A reviewer should look for the same pattern in any high-value NFC flow: the tap should produce bounded evidence, and the verifier should reject copied, stale, malformed, revoked, or wrong-context evidence.

For a facility access badge, the checklist is different from a poster tag. The reader should identify the credential type, pass the observed value or response to the access controller, check door rights, time window, revocation, offline rule, duplicate-tap behavior, and audit logging, then decide whether to unlock. If the system only says “UID seen, unlock,” it is treating a readable identifier as credential proof.

For public tags, the practitioner work is about content and operations rather than issuer-grade cryptography. A smart poster should use an approved host, short payload, write protection, privacy-reviewed analytics, and a replacement procedure. A maintenance tag should store an asset reference, not a role or command, and the app should reject unknown hosts, excessive payload length, unexpected record types, and retired schema versions.

← Back to the chapter · Previous detail · Next detail →