On this page
Secure Dynamic Messaging lets NTAG 424 DNA mirror selected file contents or derived fields into an NDEF URI or text record when the tag is read. The result can change on every tap while the physical label stays the same.
SDM is a chip configuration and personalization feature. Parsing the NDEF string on a phone is straightforward; determining whether the mirrored values are authentic requires keys, algorithms and policy in your verification service.
SDM versus SUN
Secure Dynamic Messaging (SDM) is the configured mechanism that mirrors dynamic fields during an NDEF read. Secure Unique NFC (SUN) describes the resulting tap-specific message used by an authentication workflow. Neither term means the phone has validated the cryptography.
Depending on the file configuration, the URL may contain encrypted PICC data, a read counter and an SDM MAC. The verifier must interpret the actual enabled options rather than assume every field is always present.
Personalization and URL template
- Define the NDEF URL template, mirrored-field offsets and expected encoded lengths.
- Configure file access rights and the SDM keys needed by the chosen message format.
- Personalize a test tag and compare its read output against the approved template.
- Verify the message with matching server-side key material before production.
What the backend must verify
- Parse mirrored or encrypted data according to the exact issuing profile.
- Reconstruct and validate the SDM MAC using the applicable key and protocol.
- Apply counter, replay and revocation policy after cryptographic validation.
- Resolve product data only after the chip reference is registered and bound.
Common integration failures
Incorrect mirror offsets, URL encoding changes, mismatched keys or a verifier using a different SDM configuration can invalidate an otherwise readable URL. Test against real tags and capture both successful and deliberately modified messages.
A replayed URL may still carry a valid historical MAC. Detecting reuse requires backend state and a documented counter policy; cryptographic verification alone is not replay protection.