Hi team,
I am a solution architect evaluating MOSIP for a government engagement where the client expects an NFC enabled physical ID card in addition to the digital credential. Before I scope the NFC layer as fully custom work on our side, I would like to confirm what the platform already gives me and what I have to build.
What I have already checked:
- Registration Client and Android Registration Client docs. Device integration goes through MDS and SBI, and it covers biometric devices, document scanners and GPS. I found no interface, spec or SDK for a contactless reader.
- digital-card-service. It generates a digital card once the registration packet is processed, and the output is a digital card carrying a QR code. Chip encoding for physical cards appears to sit entirely with the print or personalisation partner.
- Inji Wallet component list. The documented sharing transports are Tuvali for BLE, PixelPass for QR and the VCI client with OpenID4VP. There is no NFC library or module alongside them.
- Inji Verify. Verification happens through QR codes and cryptographic proofs.
- Inji roadmap for 2025 and the items carried into 2026. Everything listed is credential format and protocol work, so SD-JWT, mDoc and mDL, Claim 169 QR and CWT country QR. NFC is not mentioned anywhere.
- MOSIP Marketplace. The only NFC related entry I could find is a partner solution for contactless authentication between a smartcard and a smartphone, positioned as complementing Inji Wallet.
My questions:
- Is my reading correct, that MOSIP core and the Inji stack currently ship no software for NFC read or write, at any point in the flow, whether registration, issuance or presentation?
- Is there any published specification on the MOSIP side for what goes onto a contactless chip, in the way that the QR code specification and the ID schema are published? If not, is the chip data model treated as entirely an implementer decision?
- Does MOSIP provide any SDK, library or test tool for contactless cards, comparable to what the Compliance Toolkit does for biometric devices? I want to be sure I am not missing something that exists but is not surfaced in the main docs.
- Is NFC on any internal roadmap or under discussion, even informally, for either the core platform or the Inji stack?
- ISO 18013-5 defines NFC as one of the device retrieval transports. When the planned mDoc and mDL work lands, will the NFC transport be part of the scope, or is the intent to support the credential format with QR and BLE retrieval only?
- Is there a recommended pattern for writing an Inji Certify issued credential onto a contactless chip so that the chip credential and the digital credential validate against the same issuer key or DID? Chip space is limited, so I am looking at CBOR-LD and CWT style compaction rather than raw JSON-LD.
- Have any adopting countries already put a verifiable credential on a chip in a MOSIP deployment, and is any of that documented publicly or shareable?
What I plan to do with the answer: it determines whether we quote the NFC layer as custom scope in a client proposal, and how we structure the trust model between the chip credential and the wallet credential.
Happy to write up whatever we work out, and if there is appetite for it I would be glad to contribute a draft chip profile specification or a reference implementation back to the community.
Thanks!