CLAIM 169 QR Code Specification
Contributors Point of Contact
GitHub View Spec ↗
IANA CWT Registry Open Standard by MOSIP

Secure Identity in a Single QR Code

Claim 169 defines a standardized CBOR-based QR code format for embedding digitally-signed identity data — enabling offline biometric authentication across borders and in low-connectivity regions.

An open standard shaped by the ecosystem, for the ecosystem.
View Specification GitHub
75+
Identity Attributes
8+
Contributing Orgs
3+
POCs / Adoptions

Identity Data

  • CBOR Encoded
  • COSE Signed
  • Base45 + zlib
About

What Claim 169 is — and why it matters

The concept

What is Claim 169?

Claim 169 defines a standardized, CBOR-based QR code format for securely embedding identity data in a machine-readable optical format.

It enables:

  • Storage of identity data + photo within a QR code
  • Digitally signed credentials issued by trusted authorities
  • Offline verification without requiring connectivity
  • Facial authentication using embedded image + data
  • Compact encoding using CBOR, COSE, and CWT for QR efficiency

The design uses:

CBORRFC 8949compact binary data representation
COSERFC 9052 / RFC 9053CBOR signing and encryption framework
CWTRFC 8392CBOR Web Token claims format
Ed25519 / ECCcompact and efficient signature algorithms

This allows identity credentials to be portable, verifiable, and interoperable across systems.

Cryptographically Signed Offline-First Platform Agnostic Open Working Group

A secure, compact, and interoperable way to carry identity — in a single QR code.

Read full specification IANA CWT Registry
Why it matters

Why Claim 169?

In low-connectivity and cross-border environments, traditional identity systems often fail — leaving millions without reliable access to trusted identity.

People may:

  • Lose physical credentials
  • Lack access to smartphones
  • Depend on unreliable or unavailable networks
  • Struggle with expensive smart or plastic cards
  • Forget passwords or PINs required for verification
  • Use weak or easily guessable PINs (e.g. 0000, 1234)
  • Face challenges when credentials are damaged or compromised
  • Experience identity data exposure during verification

Making secure and reliable verification difficult when it matters most.

Bridging the identity gap

Claim 169 solves this by enabling identity to be carried in a single QR code — securely and portably.

  • Digitally signed identity data + photo
  • Usable on devices or as a printed credential
  • Verifiable without internet connectivity
  • Reduces dependency on passwords and/or smartcards
  • Enables trusted offline identity verification across systems and borders
  • Minimizes unnecessary data exposure

Even without a phone, individuals can present a printed QR code and securely access services with confidence.

By supporting both digital and non-digital use cases, Claim 169 brings together:

Accessibility Portability Privacy Trust

Enabling secure, high-assurance identity verification — anywhere, anytime.

Process

From Identity to Trusted Verification

  1. 01

    Generate QR Code

    Secure identity data is encoded and signed into a QR

  2. 02

    Issue Credential

    QR is shared digitally or printed for the individual

  3. 03

    Present QR Code

    User presents QR at verification point

  4. 04

    Scan & Decode

    Verifier scans and extracts identity data

  5. 05

    Verify Identity

    Signature validated + face match confirms presence

  6. 06

    Access Service

    Identity verified → service delivered

Explore the Full Process
Technical Specification

Claim Registry

Full data structure for Claim 169 — CBOR Map encoding identity and biometric data

Tag Number

169

Data Format

CBOR Map

Token Type

CWT

Encoding

Base45

Compression

zlib / Brotli

Signature

ED25519 / ECC

Claim 169 defines 75+ standardised identity attributes across CWT headers, demographic fields (claims 1–23), and biometric fields (claims 50–65). Each QR code encodes a cryptographically-signed CBOR structure that verifiers can authenticate without any network dependency.

v— All versions

Loading the latest published specification…

    Use Cases

    In Practice: Ecosystem Evolution & Adoption

    Live deployments demonstrating trusted offline identity verification across national and sectoral contexts.

    Ecosystem Evolution

    Philippines — PhilSys & Financial Inclusion

    PhilSys, the Philippines' national digital ID system built on MOSIP, enabled millions of previously unbanked residents to open bank accounts for the first time, significantly advancing financial inclusion. As adoption expanded into low-connectivity and assisted-service environments, the need for trusted offline identity verification became increasingly evident, helping shape the evolution of the Claim 169 QR code specification for secure, portable, offline-verifiable credentials.

    Financial Inclusion Offline Verification Portable Credentials Digital Identity

    Country Implementation

    Ethiopia — Fayda Digital ID

    Ethiopia's national ID system enables offline identity verification using QR-based credentials and biometrics. Supported by TECH5, it powers secure authentication and service access across public and private sectors.

    Offline Verification Biometric Authentication National ID

    Country Implementation

    Uganda — Digital Identity Ecosystem

    Uganda is modernizing its identity systems using MOSIP-based approaches to enable secure, interoperable identity verification across services, with growing support for offline and portable credentials using Claim 169.

    Interoperable Biometric Identity Government Services

    Where Claim 169 can be Used

    Potential use cases enabling trusted offline identity verification across humanitarian, government, and development contexts.

    • Humanitarian

      Refugee & Displaced Person ID

      UNHCR and partner agencies use Claim 169 QR codes on physical cards for displaced populations who lack internet access. A single scan verifies identity, biometrics, and entitlements offline.

      UNHCR PartnerOffline

    • Government

      National ID Cards

      National ID programs embed Claim 169 QR codes on physical cards, allowing authorities to verify identity during power outages, in rural areas, or at land border crossings without network access.

      Physical CardRural AccessBorder Control

    • Healthcare

      Proof of Vaccination

      Individuals can present QR codes to verify vaccination status at checkpoints, travel hubs, or healthcare facilities — even without connectivity. Digitally signed data ensures authenticity, while optional biometric verification confirms the right individual receives care.

      No Connectivity

    • Cross-border

      International Travel

      Travelers crossing borders in regions with limited digital infrastructure can be verified by scanning the Claim 169 QR code. Works even when central databases are unreachable.

      Border ControlOffline

    • Sectoral ID

      Sectoral Identity Credentials

      Claim 169 enables issuance of trusted, sector-specific IDs that can be verified across services — ensuring secure, interoperable access even without connectivity.

      InteroperableTrusted Identity

    • Financial Inclusion

      Unbanked Population Onboarding

      Financial service providers can onboard unbanked individuals using Claim 169 credentials, enabling KYC verification without requiring document uploads or real-time API calls.

      KYCFinancial Access

    • And More…

      Claim 169 is adaptable to any context requiring secure, offline-capable identity verification.

    Claim 169 addresses the global identity gap — serving populations that traditional digital identity systems have failed to reach.

    Get Involved

    Use Claim 169

    Claim 169 — an open standard designed by and for the global identity ecosystem. Here's how you can start using it.

    Experiment with real credential issuance and verification workflows.

    Build, test, and integrate using interactive playgrounds, SDKs, and reusable UI components.

    SDKs

    Java, Kotlin, Swift, JavaScript

    Components

    Scanner & Generator UI components

    Playground

    Live issuer and verifier playgrounds

    Try the Playground →

    How to Use Claim 169

    Implement in Your Platform

    Integrate Claim 169 into any ID issuance platform using the open specification. The CBOR-based structure and standard encoding pipeline work with any technology stack.

    Read the Specification

    Build a Verifier App

    Create a scanner or verifier application that reads Claim 169 QR codes. The open standard means any compliant verifier can read any compliant credential, anywhere.

    View on GitHub

    Deploy for Cross-border Use

    Adopt Claim 169 for humanitarian, government, or development programmes where offline identity verification across borders is needed for underserved populations.

    Explore Use Cases

    Resources

    Talks, podcasts, articles, and webinars on Claim 169 — everything we've published to help you learn, build, and adopt the spec.

    • Articles
    • Videos
    • Podcasts
    • Webinars
    Explore Resources →

    How to Contribute

    Ready to get started?

    The standard is open, and the Working Group welcomes contributions from across the ecosystem.

    Participate in discussions, review proposals, and help shape Claim 169. You can also contribute directly by proposing new fields, raising issues, reviewing pull requests, or improving documentation.

    Read the Spec The full latest specification Raise an Issue on GitHub Report bugs or propose changes View Working Group Notes Browse iteration discussions Contact Us Email the working group directly

    Your involvement helps build interoperable and inclusive identity systems.

    Contributors

    Claim 169 is developed collaboratively by a global working group of identity experts, humanitarian organizations, and technology partners.

    Specification Authors

    MTMahammed TaheerMOSIP
    RCResham ChuganiMOSIP
    SGSasikumar GMOSIP

    Organizations

    GetGroup1 member

    Identity Solutions

    • Aiman Tarek
    GIZ2 members

    Development Cooperation

    • Anita Mittal
    • Aisha Merhebi
    Inji4 members

    Digital Credentials

    • Preeti Hongal
    • Ramesh Narayanan
    • Sanchi Singh
    • Swati Goel
    MOSIP10 members

    Platform & Coordination

    • Janardhan BS
    • Mahammed Taheer
    • Mayura Deshmukh
    • Pragya Kumari
    • Reeba Thomas
    • Resham Chugani
    • Sasikumar Ganesan
    • Sivanand Lanka
    • Varaniya Selvaraja
    • Vishwanath V
    Ooru2 members

    Digital Public Infrastructure

    • Rounak Nayak
    • Priyank Trivdei
    OpenSPP1 member

    Social Protection

    • Jeremi Joslin
    PWC1 member

    Consulting & Governance

    • Chaitanya Giri
    Tech53 members

    Biometric Technology

    • Bejoy Ak
    • Nelson Branco
    • Rahul Parthe
    UNHCR3 members

    Humanitarian Identity

    • Norbert Trosien
    • Samantha Eisenhauer
    • Sam Jefferies

    Have questions about Claim 169?

    Explore key concepts, security, and privacy details in our Frequently Asked Questions.

    View FAQs ›

    Point of Contact

    For questions about the specification, working group participation, or implementation guidance:

    Resham Chugani — resham@mosip.io