CodeB’s Identity and Document Verification NFC Ident marks a significant advancement in the realm of customer onboarding. This innovative technology is designed to onboard a higher number of authentic customers efficiently. It distinguishes itself by providing a swift, convenient, and user-friendly experience. This approach not only enhances user engagement but also plays a crucial role in increasing conversion rates, reducing fraud, and boosting operational efficiency for businesses.
The CodeB Authenticator app, a cornerstone of this solution, transcends the capabilities of standard Time-based One-Time Password (TOTP) applications. It features an integrated Near Field Communication (NFC) ID Card Reader, enabling it to interface with various NFC-enabled documents, such as eIDAS tokens, ID cards, and passports. Remarkably, the app’s utility is not confined to official government documents; it also supports Health Professional Cards like the German Health Professional Card (HBA) and Health Insurance Cards like the German Electronic Health Card (eGK).
Users of supported NFC cards can choose to utilize the certificates embedded in these cards with CodeB. This feature allows them to not only digitally sign documents such as PDFs but also to create and sign OpenID Connect Java Web Tokens (OIDC JWTs) using the card’s certificates instead of those from the mobile device.
While traditional Identity and Document Verification systems rely on Optical Character Recognition (OCR) combined with AI-powered automation – an effective yet probabilistic approach – CodeB introduces a deterministic method for verifying identities and documents. This method involves establishing a secure channel via the mobile device’s NFC to the card’s NFC chip, serving as proof of possession. Personal data is then extracted from the card’s certificates and the Machine Readable Zone of the ID card, digitally signed by the card’s certificate. This digital signature can subsequently be used to sign a PDF eForm displaying the validated data or an OIDC JWT.
Depending on the card’s features, different types of signatures can be applied. If the card includes a Qualified Signature Application and the user signs a PDF document, the Qualified Signature is employed. Conversely, when signing an OIDC JWT, the card’s Authentication Certificate is used.
CodeB’s technology, compliant with standard APIs, is designed for seamless integration into any solution supporting OpenID Connect. Moreover, CodeB offers a comprehensive array of straightforward APIs and web servers. For instance, users can directly request a signed JWT Token from a user’s ID card, provided they have the user’s mobile number and Binding PIN.
The Binding PIN, set up in the CodeB Application, adds an extra layer of security. It must be shared with the validator to allow the sending of a validation PIN, enhancing encryption and protecting users from unsolicited validation requests.
Try it out via: https://nfcident.com/ident
Users with supported cards can explore CodeB’s APIs at:
https://auth.codeb.io/ws/mobile.asmx?op=Token
For those uncertain about the compatibility of their cards or passports, CodeB encourages contact for clarification. Alternatively, users can access the “Card Reader” Activity in the CodeB Authenticator App, enter their Card Access Number (CAN), and place their mobile device over the card. The app’s green progress bar indicates the process of establishing a secure channel to the card, and upon successful reading of the card’s Machine Readable Zone, the retrieved data is displayed.
