Security that resists replication
TrueTap is built on challenge�response cryptography anchored to provisioned hardware. The architecture is designed to remain secure when chip data is observable - duplication of chip data does not reproduce authentication capability.
Technology stack
Four integrated layers from silicon to application - each designed with explicit security and operational properties.
Provisioned NFC silicon
Standard and secure NFC chip families with on-chip secure element. Unique key material is written at provisioning and cannot be read back in cleartext. Physical tamper response is supported on relevant form factors.
Challenge�response authentication
Each tap initiates a fresh cryptographic challenge from the verification service. The chip responds using on-chip key material. The response is valid for a single session; replay attacks are structurally prevented.
The protocol does not require the chip to be online, but the reader or device must reach the verification service to complete authentication.
Verification and key management services
Server-side key operations are performed in hardware security modules (HSMs). Verification events are logged with cryptographic integrity guarantees. The service tier is stateless for verification and supports horizontal scaling for high-throughput deployment contexts.
APIs, SDKs, and programme management
REST verification API and mobile SDKs (iOS, Android) for integration with existing systems. Programme administration portal for lifecycle management, analytics, and audit access. Webhook delivery for real-time event integration.
Non-negotiable security properties
The TrueTap architecture guarantees specific security properties regardless of deployment context. These properties hold even if an attacker captures NFC traffic or obtains a legitimate chip for analysis.
Anti-cloning
Key material cannot be extracted from provisioned chips. A physical duplicate does not yield a chip that passes verification.
Anti-replay
Challenge freshness means intercepted NFC sessions cannot be replayed to obtain a subsequent verification.
Non-repudiable logging
Every verification event is logged with a tamper-evident signature. Event records cannot be modified without detection.
Revocation
Programme operators can revoke chip identities in real time. Revoked chips return a deterministic negative result on verification.
Offline verification (constrained mode)
For field environments, verification can operate against cached validation data with defined staleness bounds.
Infrastructure configurations
The platform topology is selected based on data residency requirements, operational independence, and programme scale.
Managed multi-tenant
Fastest deployment path. Platform infrastructure operated by HSA with programme-level data segregation. Suitable for commercial programmes without specific residency constraints.
Dedicated cloud tenancy
Isolated infrastructure within a defined cloud region. Addresses data residency requirements for regulated programmes while retaining managed operations.
On-premises sovereign deployment
Platform deployed within the programme operator's infrastructure perimeter. Key management infrastructure transferred to programme control. Required for air-gapped and classified environments.
Hybrid edge deployment
Verification edge nodes deployed within the programme perimeter; key management and audit infrastructure retained in a controlled zone. Common for border and enforcement contexts.
Request an architecture review
The TrueTap technical team is available for structured architecture briefings with programme security officers and integration engineers.