NearID logoNearIDPresence verification
PartnerRequest demo
PartnerRequest demo
Physical presence verification platform

A receiver-backed presence signal for the software you already use.

NearID answers a narrow question: was a linked device observed by an organization-managed receiver at a trusted place and time? Your attendance, access, payroll, or workflow system decides what to do with that result.

See the platformView documentation
Verification path
Mobile token → receiver → backend → customer system

Rotating BLE tokens avoid stable identifiers in the air. Receivers submit authenticated observations; backend rules validate timing, replay, device, receiver, and organization context.

Tokens
Rotating BLE payloads
Receivers
On-site observation points
Backend
Validation and records
Integrations
APIs and signed webhooks
What NearID verifies
Linked device signal
The observed token is checked against a device linked through the NearID workflow.
Trusted receiver context
The observation is associated with an organization-managed receiver and configured site.
Time-bounded observation
Short token windows and anti-replay checks constrain when an observation can be accepted.
How physical presence verification works
1. A mobile device rotates BLE tokens
The app broadcasts short-lived tokens without placing a stable user identity in the BLE payload.
2. An on-site receiver observes the token
A provisioned receiver scans locally and sends an authenticated report to the NearID backend.
3. Backend rules validate the report
NearID checks receiver identity, organization context, token timing, duplicates, and replay conditions.
4. Your system receives the result
Read APIs and signed webhooks let the customer system apply its own attendance, access, or workflow policy.
Product boundaries

Useful proof starts with honest limits.

NearID strengthens a physical-presence decision, but it does not turn radio proximity into absolute truth. The deployment, device-linking process, receiver placement, and customer policy still matter.

Not GPS-level location assurance
NearID does not claim precise coordinates or exact physical distance.
Not identity or KYC
External systems remain responsible for identity and user authorization.
Not a complete attendance or access system
NearID supplies a presence signal; customer systems own the business decision.

Built for integration

Use NearID beneath workforce, education, field-service, access, or other software where a receiver-backed physical-presence signal improves the workflow.

Explore the APIRead the guide