Introduction#
Using the extraordinary power of Neuromorphic Computing, research scientists at aiQ have successfully been able to engineer a groundbreaking neuromorphic biometric technology (code-named 'aiDX') that is able to interpret personal identity, independently of who the person claims to be, even if he/she is able to support his/her claim to identity with some form of ‘proof’ (identity document, passport, driver’s license…) - the result is a far more accurate, a much simpler and a completely secure personal identification technology solutionQiD does not require end-users to be onboarded, nor does QiD require an end-user to supply any personal informationQiD obviates the need for all forms of identity artefacts (identity books/cards, passports, driver's licenses…) and renders all identity claims (login names, passwords, PINs…) completely redundantAs a neuromorphic technology solution that is uniquely able to determine personal identity on the one device we all carry with us all the time - a standard, off-the-shelf mobile phone (even low-end phones) inside a standard browser connected to the Internet (no app downloads, no SDKs, no special libraries…), QiD promises to arrest the out-of-control scourge of identity theftMore information about aiDX and QiD can be accessed on-line here...The QiD Process Flow#
In order for an entity to use the QiD Service, the entity needs to be registered as a Principal Subscriber (register on-line here)The Principal Subscriber is issued a unique Principal ID which needs to accompany every QiD Service requestThe QiD process flow can briefly be illustrated as follows:A: Using a (tiny) URL, a '3D selfie' of the subject is captured inside a browser instance (typically as an iFrame);
B: The '3D selfie' is converted into a 3D rendering of the subject from which the subject's personal identity is neuromorphically determined
C: The subject's identity a mathematically expressed as a complex, irreversible, de-identifiable 512-alpha/numeric cryptographic hash ('QiD') representing the subject's own, unique identity for life.
D: The subject's QiD is assigned a unique 128-bit UUID ('aiDX UUID') for use by the Principal Subscriber to either record the subject as a new customer/employee... or to identify the subject as an existing customer/employee...
QiD API WorkFlow#
The QiD API workflow can briefly be illustrated as follows:
A: The Principal Subscriber’s mobile app (deployed on a mobile phone) issues a secure QiD Service request to the Principal Subscriber’s own server.
B: The Principal Subscriber’s server securely relays the QiD Service request to the QiD API from a registered static IP address.
C: If the QiD Service request checks out, the QiD API instantly responds with a tiny URL (eg https://aidx.bio/6GtRdjIG) comprised of three parts: D: The Principal Subscriber's server notifies the mobile app of the URL.
E: Using the URL as a reference, an in-app (iFrame) browser instance is launched - no SDK needs to be embedded.
F: Using the front/‘selfie’ camera on the end-user’s own mobile phone, QiD captures a single ‘3D selfie’ of the subject - the capture procedure is normally completed in less than 3 seconds.
While QiD allows normal use of the device, the end-user is given 3.5 seconds to capture a ‘3D selfie’ - should the end-user fail to capture a ‘3D selfie’ within the allotted time, QiD immediately gives the end-user a contextual specific response to guide and assist the end-user.
If after two failed attempts the end-user has not successfully managed to capture a ‘3D selfie’, the capture process is automatically terminated and the QiD Service request is cancelled.
G: aiDX processes the QiD Service request in three parts:
• Part 1: A series of image quality control checks (IQCs) are applied to ensure that the captured ‘3D selfie’ qualifies as acceptable.
• Part 2: If required by the Principal Subscriber, a liveness check of the ‘3D selfie’ is performed to ensure that the image was captured of a real/live subject.
• Part 3: A semantic search of the subject is performed
If the subject is not already on record with the QiD Service:
• aiDX converts the ‘3D selfie’ into a 512-alpha/numeric character cryptographic hash ('QiD');
• a unique 128-bit UUID (‘aiDX UUID’) is assigned to identify the end-user - an end-user's aiDX UUID is only exposed to the Principal Subscriber.
If the end-user already happens to be on record with the QiD Service:
• the end-user’s aiDX UUID is simply looked up.
H: The QiD Service returns the end-user’s aiDX UUID to the Principal Subscriber's server via a webhook.
I&J: As a unique identifier, the Principal Subscriber uses the aiDX UUID as the key to establish/lookup a unique account record for the end-user - the Principal Subscriber feeds the mobile app with whatever user information the Principal Subscriber has on record for the end-user.
Modified at 2025-07-04 12:02:48
