How QR-V™ Works

Each QR-V code contains a structured identifier that references a registry record.

Unlike traditional QR codes, the identifier is not simply a URL. It encodes a reference that is resolved through the QR-V network.

This ensures that every scan initiates a verification process rather than a basic redirect.

• Unique record reference
• Bound to registry entry
• Not dependent on webpage content

When a QR-V code is scanned, the identifier is interpreted by the resolver.

The resolver determines how to route the request within the verification network and prepares the lookup request.

This replaces traditional redirection logic with structured resolution.

• Interprets QR-V identifier
• Routes to correct registry record
• Initiates verification request

The resolver queries the QR-V registry to retrieve the canonical record.

The registry is the source of truth and contains:

• issuer information
• record metadata
• cryptographic hash
• status (active, revoked, expired)

All verification depends on the registry record—not the QR code itself.

The verification engine evaluates the registry record.

This includes:

• hash integrity validation
• issuer verification
• timestamp validation
• status checks

This step ensures that the record has not been altered and is still valid.

The system returns a structured verification result.

This response is displayed to the user through the verification interface.

Typical output includes:

• verification status
• issuer identity
• record type
• timestamp
• metadata

The user does not need to trust the QR code—the system provides verifiable proof.

QR-V operates as a layered system where each component performs a defined role in the verification lifecycle.

Issuer → Registry → API → Verification Interface → Result

This separation ensures that trust is derived from infrastructure—not from the visual QR code itself.