← Back to the chapter · Next detail →

Technical detail · How NFC Taps Work

Trace evidence across the four NFC handoffs

Field to target. A successful coupling test covers the tested distance, orientation, antenna, phone, case, surface, and materials. It proves neither payload safety nor credential validity or application authorization. Retest after changes to the label, enclosure, mounting surface, phone fleet, reader antenna, protective case, or tap-zone marking.

Activation to mode. Activation shows that the expected tag technology, reader/writer behavior, card-emulation exchange, or peer-to-peer handoff can start. It does not give that mode the trust boundary of another NFC mode or RFID family. Retest after changes to mode, tag family, secure element, wallet, reader firmware, app entitlement, or operating-system behavior.

Payload to parser. The app reads a bounded NDEF record, memory value, reference, or protocol response and rejects unsupported input. That does not establish that the object is current, the host is trusted, the user is authorized, or copied content is harmless. Retest after payload schema, host, version, encoding, length, lock state, replacement-process, or parser-rule changes.

Policy to action. The application or verifier turns the selected object or credential into an allowed workflow decision. This says nothing about whether future roles, revocation state, fallback handling, privacy rules, or support procedures remain valid. Retest after changes to the role model, credential lifecycle, backend state, privacy policy, audit rule, workflow, or support ownership.

Together these boundaries locate the last supported claim. Keep physical coupling, activation, parsing, credential handling, application state, privacy, fallback, and operational evidence available rather than allowing the approval to expand beyond the tests.

← Back to the chapter · Next detail →