Read Your Passport's NFC Chip With Your Phone, Safely

Yes — your phone can read your passport's NFC chip. It's meant to. Apple Wallet, Google Wallet, and a handful of dedicated apps all lean on the same ICAO-standard handshake to do it, entirely on-device, and nobody else can skim the chip from across a room while they're at it.

Quick answer

Modern e-passports carry a small NFC chip — an eMRTD, short for electronic Machine Readable Travel Document — storing your data-page information and a digital photo. It's part of ICAO Document 9303, the same international standard that defines the printed machine-readable zone (MRZ) at the bottom of your data page. The chip won't hand that data to just anything that taps it. It only unlocks once the reader proves it already knows the MRZ, which is the same protection covered in more general terms in what's actually stored on an NFC chip. In practice you've got two routes: an official wallet app (Apple or Google) if you want a phone-based ID, or a dedicated reader app if you just want to verify the chip is genuine.

Step-by-step

Reading it with Apple Wallet (iPhone)

You'll need an iPhone 11 or later on the latest iOS, plus an unexpired US passport. Follow the onscreen prompt to place your phone on the chip — usually near the spine or the data page, depending on the issuer — then take a selfie so Apple can confirm you're really the person in the photo. Apple's instructions describe this read-then-verify flow, and the resulting Digital ID works at TSA checkpoints, in apps, and online, though it doesn't fully replace the physical passport everywhere. It's the same pattern as adding a car key to Apple Wallet: the wallet app owns the entire read, and you never see the raw chip data yourself.

Reading it with Google Wallet (Android)

On Android you'll need Android 9 or higher and a valid US passport. Google Wallet runs the steps in the reverse order from Apple's — camera-scan the data page first, confirm the parsed info, then scan the security chip. The ID pass that comes out of it works at TSA checkpoints and for some domestic-travel identity checks.

What's actually happening underneath: BAC vs. PACE

Both flows lean on the same handshake. Before the chip releases anything, the reader has to complete Basic Access Control (BAC) — proving it already knows the MRZ-derived key: birth date, expiry date, document number. PACE is the newer, stronger version. It does everything BAC does, plus supports Card Access Numbers and PINs, and it's required on newer passports and every EU document. The upshot: nobody can tap your passport in your bag and pull data off it, because the document has to be physically open, and the MRZ already known, before the chip says anything at all.

Common problems and fixes

Chip not detected on the first tap? Take off a thick case and hold the phone steady over the antenna area for a few seconds — the antenna loop is small, so alignment matters more here than it does for most NFC tags. If Apple Wallet or Google Wallet complains the MRZ couldn't be read, rescan the data page in even light and keep glare off the laminate. And if a passport won't read at all, even flat on the table, check the cover for a metal-mesh Faraday shield — some countries, including the US, build this in specifically so a closed passport can't be read wirelessly. That's expected behavior, not a fault. For more on why the handshake exists in the first place, see NFC sniffing and replay risks.

Doing this on NFCore specifically

NFCore doesn't read passport chips. NFCore is built for the NFC tags you own and control — NDEF stickers, NTAG chips, MIFARE Ultralight cards — not the ICAO BAC/PACE handshake eMRTD chips require, and there's no point pretending otherwise. For your passport, stick with Apple Wallet, Google Wallet, or a purpose-built ID-verification app. Where NFCore comes in is everything after: inspecting, writing, or managing the tags you actually own. Get NFCore on the App Store or Google Play to see what that looks like.

Frequently Asked Questions

Can I read someone else's passport chip without their permission?

No — the chip won't release data to a reader that doesn't already know the printed MRZ, so it needs the physical passport open in hand. Reading a document you don't own or don't have permission to handle isn't something this guide covers.

Is it safe to scan my passport chip with a random NFC app?

Stick to apps that are explicit about processing the scan on-device and never uploading it — Apple Wallet, Google Wallet, and reputable ID-verification apps like ReadID Me all state the data never leaves your phone. Skip anything that wants an account or a server upload of the chip data.

Why won't my phone read the chip on the first tap?

The antenna loop is small, and BAC/PACE only unlocks after the reader supplies the exact MRZ-derived key, so alignment and MRZ-scan accuracy both matter. Removing a case, holding still for a few seconds, and rescanning the data page if the MRZ was misread usually fixes it.

Does NFCore read passport chips?

No. NFCore handles user-owned NFC tags — NDEF, NTAG, MIFARE — not the ICAO BAC/PACE handshake eMRTD chips require. Use Apple Wallet, Google Wallet, or a dedicated ID-verification app for your passport; NFCore is the right tool once you're back to inspecting your own tags.

Conclusion

Reading your own passport's NFC chip is a standard, ICAO-defined handshake, and Apple Wallet and Google Wallet both handle it safely, entirely on-device. That same BAC/PACE logic is exactly why nobody can skim your passport from across a room without the physical document already open in hand.