On this page
verified_user
Verify Tap Honesty — Block Fake or Copied NFC Taps (Beta)
Use the Verify Tap Honesty step to continue an interaction only when a Kitetag was genuinely tapped by a phone — blocking copied URLs and spoofed taps.
**Beta:** Verify Tap Honesty is marked **Beta** in the step catalog. Its behavior may change. Test it with your tags before relying on it in production.
**TL;DR:** Verify Tap Honesty is a silent security step that lets the flow continue **only if the Kitetag was genuinely tapped by a smartphone** — helping block fake taps from copied URLs and spoofing.
What does it do?
A Kitetag tap opens a URL. If someone copies that URL and shares it, the link still works — which is undesirable for access, authenticity, or anti-counterfeit use cases. Verify Tap Honesty checks signals that distinguish a real, physical NFC tap from a replayed or copied link, and only then allows the interaction to proceed. It runs silently in the Security category of the Interaction Builder.
When should you use it?
- Authenticity / anti-counterfeit — prove a product tag was physically present
- Gated content — only show the next steps to someone who actually tapped
- Proof-of-presence — confirm a person was at the tag, not just sent its link
How do you set it up?
- In the Interaction Builder, click Add Step.
- Under the Security category, choose Verify Tap Honesty.
- Place it early in the flow — before the steps you want to protect.
- Publish and assign the interaction to a Kitetag Group.
- Test by tapping a real tag, then by opening the copied URL, and confirm the protected steps only appear for the genuine tap.
This is an advanced, evolving capability. For straightforward "is this tag claimed and working" checks, use [Test Flight](/docs/apps/test-flight/) instead.
Next steps
- See all step types in the Interaction Builder guide.
- Combine with a Display Information Table that only genuine taps can reach.
Last updated 16 May 2026, 22:33 -0700 .