Following cards can't be supported for various reasons. This is not definitive as somebody might come up with novel approach to support them.

Until we have a reliable way to crack MiFare Plus operating in SL3 mode or agency agrees to allow reading, following cards can't be read:

• Kyiv metro cards manufactured in 2016 or later
• Minsk metro card
• Washington, DC SmarTrip cards issued in 2012 or later
• Wellington Snapper "classic" cards
• Reloadable BakuCard/Bakikart (single-ride cards are MFU and readable)

Until we have a reliable way to crack DESFire or agency agrees to allow reading, following cards can't be read:

• BEM Card (Thailand)
• Breeze (Atlanta, GA, USA) (Nextfare MFD)
• Christchurch Metrocard second-generation (DESFire) cards
• London Oyster second-generation (DESFire) cards
• Prague OpenCard/Litacka
• Madrid Red Card
• NY/NJ PATH SmartLink
• Thailand Rabbitcard
• Compass multi-trip, Vancouver (Nextfare MFD)

While there are known DESFire attacks, the needed hardware is in hundreds to thousands of dollars.

Following cards look like containing just a high-entropy blob:

• Pittsburgh's "PortAuthority Connectix", single trip (Mifare Ultralight) and stored value (Mifare Classic, encrypted by parts)
• Single-trip Ekarta in Yekaterinburg, Russia (Mifare Ultralight)

Note: it may turn out that the encryption is weak or even just an obfuscation and can be decrypted. But more dumps with detailed annotations are needed to figure it out.

Reading magstripe tickets requires additional hardware for most phones, and these tickets are being replaced by RFID-based cards, so it is not a priority.

Examples of magstripe-only tickets:

• Adelaide and Hobart's Crouzet tickets (replaced)
• New York MetroCard (Cubic)