NFC ID Reader: Chip ID Card
Everyone
info
0+
Downloads
Everyone
Learn more
About this app
NFC ID Reader opens the chip inside a Vietnamese citizen ID card (CCCD gắn chip) and shows you, in plain language, exactly what that chip stores about you.
Everything happens on the phone. No internet permission, no database, no analytics. Leaving the result screen wipes the data from memory.
HOW IT WORKS
The chip is not an open book. Following ICAO Doc 9303 — the standard e-passports use — it refuses every command until the reader proves it knows what is printed on the card: the 6-digit CAN, or the ID number plus date of birth and date of expiry. That is what stops a card being read through a pocket, so no app can skip it. What an app can skip is the typing.
1. Hold the card in front of the camera. The QR code on the front and the machine-readable lines on the back both carry what the chip asks for, and the app reads either. Poor light? Use a still photo, or type the numbers.
2. Hold the card flat against the back of the phone.
3. The app negotiates PACE, falls back to BAC, and reads the chip.
4. Close the screen; it is gone.
The camera only starts after you confirm the card is yours. No frame is saved anywhere: text recognition runs on the phone.
WHAT YOU SEE
• Portrait photo stored in DG2, decoded on the device
• Vietnamese details from DG13 with full diacritics — name, ID number, date of birth, sex, nationality, place of origin, place of residence, issue and expiry dates
• The raw ordered list from the chip beside the labelled view, because Vietnam does not publish the DG13 layout and the labels are a best guess
• The machine-readable zone from DG1 exactly as it is printed
• Which protocol opened the card, which data groups the chip declares, and how long the read took
WHAT WAS ACTUALLY PROVEN
Every read opens with a panel separating the two things people confuse: reading a card, and proving one. Each row is green, red, or unanswerable.
• The chip opened — the access key worked. A copied chip opens just as well, so alone this proves nothing, and the app says so.
• Data matches EF.SOD — every data group read hashes to the value in the chip's own signed index.
• EF.SOD signature is valid — checked against the document signer certificate inside the card, which is then shown in full: signer, issuer, serial, key size, algorithms, validity dates.
• The chip is not a copy — Active Authentication has the chip sign eight random bytes with a private key it never reveals; Chip Authentication repeats the proof while rekeying the channel. A byte-for-byte clone cannot do either.
• Issued by Vietnam — always marked as something this app cannot check, on any card: proving it needs Vietnam's root certificate (CSCA), which governments exchange between themselves and do not publish. A well-made forgery carrying its own keys would still pass every green row above.
MRZ check digits are recomputed too, including the case that trips up most readers: a 12-digit CCCD number does not fit the nine slots the format allows, and spills into the optional field.
WHAT IT DOES NOT DO
• It cannot read fingerprint or iris data (DG3/DG4), which are locked behind a certificate issued by the Ministry of Public Security.
• It never uploads card data. No file, no database, no server.
WRITE A TAG
A second screen writes a standard NDEF record onto a blank NFC tag you supply: a link, text, a Wi-Fi credential, a contact, a phone number, a geo point, an SMS or an email.
Contact, phone, SMS and email records need a phone number or an email address. That is the only data here that leaves the phone, and it goes onto the tag in your hand — never to a server. An NFC tag is plaintext by design, so write only what you would let a finder read. Play's Data safety form lists those two fields for that reason.
BEFORE YOU USE IT
Read your own card, or one whose holder has agreed. Vietnamese law (Luật Căn cước 2023, Nghị định 70/2024/NĐ-CP) treats identity data as sensitive personal data and requires consent.
Requires a phone with NFC hardware, Android 6.0 or newer.
Everything happens on the phone. No internet permission, no database, no analytics. Leaving the result screen wipes the data from memory.
HOW IT WORKS
The chip is not an open book. Following ICAO Doc 9303 — the standard e-passports use — it refuses every command until the reader proves it knows what is printed on the card: the 6-digit CAN, or the ID number plus date of birth and date of expiry. That is what stops a card being read through a pocket, so no app can skip it. What an app can skip is the typing.
1. Hold the card in front of the camera. The QR code on the front and the machine-readable lines on the back both carry what the chip asks for, and the app reads either. Poor light? Use a still photo, or type the numbers.
2. Hold the card flat against the back of the phone.
3. The app negotiates PACE, falls back to BAC, and reads the chip.
4. Close the screen; it is gone.
The camera only starts after you confirm the card is yours. No frame is saved anywhere: text recognition runs on the phone.
WHAT YOU SEE
• Portrait photo stored in DG2, decoded on the device
• Vietnamese details from DG13 with full diacritics — name, ID number, date of birth, sex, nationality, place of origin, place of residence, issue and expiry dates
• The raw ordered list from the chip beside the labelled view, because Vietnam does not publish the DG13 layout and the labels are a best guess
• The machine-readable zone from DG1 exactly as it is printed
• Which protocol opened the card, which data groups the chip declares, and how long the read took
WHAT WAS ACTUALLY PROVEN
Every read opens with a panel separating the two things people confuse: reading a card, and proving one. Each row is green, red, or unanswerable.
• The chip opened — the access key worked. A copied chip opens just as well, so alone this proves nothing, and the app says so.
• Data matches EF.SOD — every data group read hashes to the value in the chip's own signed index.
• EF.SOD signature is valid — checked against the document signer certificate inside the card, which is then shown in full: signer, issuer, serial, key size, algorithms, validity dates.
• The chip is not a copy — Active Authentication has the chip sign eight random bytes with a private key it never reveals; Chip Authentication repeats the proof while rekeying the channel. A byte-for-byte clone cannot do either.
• Issued by Vietnam — always marked as something this app cannot check, on any card: proving it needs Vietnam's root certificate (CSCA), which governments exchange between themselves and do not publish. A well-made forgery carrying its own keys would still pass every green row above.
MRZ check digits are recomputed too, including the case that trips up most readers: a 12-digit CCCD number does not fit the nine slots the format allows, and spills into the optional field.
WHAT IT DOES NOT DO
• It cannot read fingerprint or iris data (DG3/DG4), which are locked behind a certificate issued by the Ministry of Public Security.
• It never uploads card data. No file, no database, no server.
WRITE A TAG
A second screen writes a standard NDEF record onto a blank NFC tag you supply: a link, text, a Wi-Fi credential, a contact, a phone number, a geo point, an SMS or an email.
Contact, phone, SMS and email records need a phone number or an email address. That is the only data here that leaves the phone, and it goes onto the tag in your hand — never to a server. An NFC tag is plaintext by design, so write only what you would let a finder read. Play's Data safety form lists those two fields for that reason.
BEFORE YOU USE IT
Read your own card, or one whose holder has agreed. Vietnamese law (Luật Căn cước 2023, Nghị định 70/2024/NĐ-CP) treats identity data as sensitive personal data and requires consent.
Requires a phone with NFC hardware, Android 6.0 or newer.
Tap your Vietnamese chip ID card and read what its chip stores. Offline.
Updated on
Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time.
- No data shared with third partiesLearn more about how developers declare sharing
- This app may collect these data typesPersonal info
- Data isn’t encrypted
- You can request that data be deleted
What’s new
New: "What was actually proven" — a verdict panel at the top of every read.
• Active and Chip Authentication: the chip signs a random challenge with a key it never reveals, so a byte-for-byte copy is caught.
• The EF.SOD signature is verified against the signer certificate inside the card, and that certificate is shown in full.
• MRZ check digits are recomputed, including 12-digit CCCD numbers.
The last row always says what cannot be checked, and why.
• Active and Chip Authentication: the chip signs a random challenge with a key it never reveals, so a byte-for-byte copy is caught.
• The EF.SOD signature is verified against the signer certificate inside the card, and that certificate is shown in full.
• MRZ check digits are recomputed, including 12-digit CCCD numbers.
The last row always says what cannot be checked, and why.
Everyone
Learn moreApp support
About the developer
Tran Trung Hieu
trunghieu4121993@gmail.com
Thôn Nga Mãn Phổ Cường, Thị xã Đức Phổ, Quảng Ngãi
Quảng Ngãi
700000
Vietnam
