On this page
A SUN message is the tap-unique output of an SDM-enabled NDEF payload. Typical mirrored items include the tag UID, a tap counter, cryptographic MAC and optional encrypted PICC data, depending on configuration.
The phone reads NDEF; it does not perform SUN verification. Your backend must parse the URL or discrete fields, retrieve the correct diversified key material and execute the MAC or decryption steps defined for your deployment.
What a verification service checks
- Decode mirrored or encrypted fields according to the configured SDM template
- Validate the message authentication code using the correct key material
- Enforce replay, counter, revocation and product-association policy
- Return a controlled verification outcome without exposing secret keys
Replay and counter policy
A captured SUN URL can contain a historically valid MAC. A verifier should track the accepted read-counter state for the relevant tag or chip reference and decide how to handle duplicates, delayed requests and concurrent scans.
Counter validation is a backend policy, not an automatic rejection by the chip. Offline access, multiple verification regions and recovery from missed taps require an explicit consistency model.
Test cases for integration
- Verify a valid tap using the issuing profile and its matching keys.
- Modify the MAC or encrypted PICC field and confirm rejection.
- Submit a previously accepted URL and confirm the configured replay outcome.
- Check revoked and unrecognized tag references without disclosing key material.
What a valid SUN result does not prove
A verified SUN message authenticates configured chip data. It does not independently prove product contents, ownership, packaging integrity or that the tag remains attached to the intended item.