Justus at 08:10, 13 February 2026

2026-02-13T08:10:05Z

← Older revision		Revision as of 08:10, 13 February 2026
Line 54:		Line 54:
	T1...Tk: 04 09 22 02</pre>		T1...Tk: 04 09 22 02</pre>

	~~Maintainer '''luu176''' meanwhile said that they found the following ''ATR'':~~

	~~<pre>3B 88 80 01 04 02 00 20 00 71 C1 40 DF</pre>~~
	Meanwhile, a friend gave me a newer T-Money card. Flipper Zero prints the following dump for this card:		Meanwhile, a friend gave me a newer T-Money card. Flipper Zero prints the following dump for this card:

Line 75:		Line 72:
	T1...Tk: 0E 51 31 01</pre>Notice the difference in the <code>T1...Tk</code> bytes. The older card has <code>04 09 22 02</code> and the newer card has <code>0E 51 31 01</code>.		T1...Tk: 0E 51 31 01</pre>Notice the difference in the <code>T1...Tk</code> bytes. The older card has <code>04 09 22 02</code> and the newer card has <code>0E 51 31 01</code>.

	I refer to the '''Smart card ATR parsing'''<ref>[https://smartcard-atr.apdu.fr/ Smart card ATR parsing] ''smartcard-atr.apdu.fr''</ref> tool and enter luu176's ATR. The tool gives the following response<ref>[https://smartcard-atr.apdu.fr/parse?ATR=3B+88+80+01+04+02+00+20+00+71+C1+40+DF "Parsing ATR: 3B 88 … result"] ''smartcard-atr.apu.fr''</ref>:		Maintainer '''luu176''' meanwhile said that they found the following ''ATR'':

			<pre>3B 88 80 01 04 02 00 20 00 71 C1 40 DF</pre>I refer to the '''Smart card ATR parsing'''<ref>[https://smartcard-atr.apdu.fr/ Smart card ATR parsing] ''smartcard-atr.apdu.fr''</ref> tool and enter luu176's ATR. The tool gives the following response<ref>[https://smartcard-atr.apdu.fr/parse?ATR=3B+88+80+01+04+02+00+20+00+71+C1+40+DF "Parsing ATR: 3B 88 … result"] ''smartcard-atr.apu.fr''</ref>:

	* TS = 0x3B - Direct Convention		* TS<ref>TS 開始キャラクタ (initial character) https://kikakurui.com/x6/X6320-3-2009-01.html#:~:text=TS,character</ref> = 0x3B
	* T0 = 0x88 Y(1): b1000, K: 8 (historical bytes)		** Direct Convention
	* TD(1) = 0x80 Y(i+1) = b1000, Protocol T=0		* T0<ref>T0 構成表示バイト (format byte) https://kikakurui.com/x6/X6320-3-2009-01.html#:~:text=T0,byte</ref> = 0x88
	* ----		** Y(1): b1000, K: 8 (historical bytes)
	* TD(2) = ~~0x01~~ Y(i+1) = b0000, Protocol T=1		* TD(1) = 0x80
	* ~~----~~		** Y(i+1) = b1000, Protocol T=0
	* ~~Historical bytes~~ 04 02 00 20 00 71 C1 40		* TD(2) = 0x01
	* Category indicator byte: ~~0x04~~ (proprietary format) ".. .q.@"		** Y(i+1) = b0000, Protocol T=1
	* TCK = ~~0xDF '''~~correct checksum~~'''~~		* Historical bytes
			** 04 02 00 20 00 71 C1 40
			* Category indicator byte: 0x04
			** (proprietary format) ".. .q.@"
			* TCK<ref>TCK 検査キャラクタ (check character) https://kikakurui.com/x6/X6320-3-2009-01.html#:~:text=TCK,character</ref> = 0xDF
			** correct checksum
	<references />		<references />

Justus: Created page with "Here's what I see when I run Metroflip[https://github.com/luu176/Metroflip Metroflip] ''github.com'' with the ufbt cli attached, running the command log debug:

… 518343 [D][Iso14443_4aPoller] Read ATS success … 518432 [D][Type4TagPoller] Select application 518437 [E][Type4TagPoller] APDU failed: 6A82 518465 [D][Iso14443_4aPoller] Read ATS success 518467 [D][EMVPoller] Send select PPSE 518473 [E][EMVPoller] Failed to parse ap..."

2026-02-13T07:43:10Z

Created page with "Here's what I see when I run Metroflip<ref>[https://github.com/luu176/Metroflip Metroflip] ''github.com''</ref> with the <code>ufbt cli</code> attached, running the command <code>log debug</code>: <pre>… 518343 [D][Iso14443_4aPoller] Read ATS success … 518432 [D][Type4TagPoller] Select application 518437 [E][Type4TagPoller] APDU failed: 6A82 518465 [D][Iso14443_4aPoller] Read ATS success 518467 [D][EMVPoller] Send select PPSE 518473 [E][EMVPoller] Failed to parse ap..."

New page

Here's what I see when I run Metroflip<ref>[https://github.com/luu176/Metroflip Metroflip] ''github.com''</ref> with the <code>ufbt cli</code> attached, running the command <code>log debug</code>:

<pre>…
518343 [D][Iso14443_4aPoller] Read ATS success
…
518432 [D][Type4TagPoller] Select application
518437 [E][Type4TagPoller] APDU failed: 6A82
518465 [D][Iso14443_4aPoller] Read ATS success
518467 [D][EMVPoller] Send select PPSE
518473 [E][EMVPoller] Failed to parse application
518487 [I][NfcScanner] Detected 1 protocols
518489 [I][Metroflip:Scene:Auto] test
518594 [I][Metroflip:Scene:Auto] proto: 2
518596 [I][Metroflip:Scene:Parse] Parse scene entered - card_type: atr, data_loaded: false
518601 [I][Metroflip:Scene:Parse] Tag is either T-Mobilitat or T-Money
518605 [I][Metroflip:Scene:Parse] Card is valid, loading plugin for: atr
…
518680 [D][Iso14443_4aPoller] Read ATS success
518695 [I][Metroflip:Scene:Parse] Wrong card event received - switching to unknown scene
…</pre>
Meanwhile on the Flipper Zero screen, Metroflip prints the following:

<pre>atr

This card is currently
unsupported / fully locked</pre>

In <code>scenes/metroflip_scene_parse.c</code> the following conditional determines if a card is T-money:

<syntaxhighlight lang="c">void metroflip_scene_parse_on_enter(void* context) {
// ...
} else if (app->hist_bytes[0] == 0x04 && app->hist_bytes[1] == 0x09) {
// This branch is not hit.
// the program then assumes that the card is "locked"
// ...</syntaxhighlight>
The program skips this conditional because the ''hist_bytes'' don't line up with the T-Money card from 2018 that I've used in Seoul.

In my original pull request<ref>https://github.com/luu176/Metroflip/pull/77 “Implement T-Money balance parsing”</ref> I’ve reported the following information as dumped by the Flipper Zero's NFC app:

<pre>Filetype: Flipper NFC device
Version: 4
# Device type can be ISO14443-3A, ISO14443-3B, ISO14443-4A, ISO14443-4B, ISO15693-3, FeliCa, NTAG/Ultralight, Mifare Classic, Mifare Plus, Mifare DESFire, SLIX, ST25TB, NTAG4xx, Type 4 Tag, EMV
Device type: ISO14443-4A
# UID is common for all formats
UID: XX XX XX XX
# ISO14443-3A specific data
ATQA: 00 04
SAK: 20
# ISO14443-4A specific data
T0: 78
TA(1): 80
TB(1): B0
TC(1): 02
T1...Tk: 04 09 22 02</pre>

Maintainer '''luu176''' meanwhile said that they found the following ''ATR'':

<pre>3B 88 80 01 04 02 00 20 00 71 C1 40 DF</pre>
Meanwhile, a friend gave me a newer T-Money card. Flipper Zero prints the following dump for this card:

<pre>Filetype: Flipper NFC device
Version: 4
# Device type can be ISO14443-3A, ISO14443-3B, ISO14443-4A, ISO14443-4B, ISO15693-3, FeliCa, NTAG/Ultralight, Mifare Classic, Mifare Plus, Mifare DESFire, SLIX, ST25TB, NTAG4xx, Type 4 Tag, EMV
Device type: ISO14443-4A
# UID is common for all formats
UID: XX XX XX XX
# ISO14443-3A specific data
ATQA: 00 04
SAK: 20
# ISO14443-4A specific data
T0: 78
TA(1): 77
TB(1): C1
TC(1): 02
T1...Tk: 0E 51 31 01</pre>Notice the difference in the <code>T1...Tk</code> bytes. The older card has <code>04 09 22 02</code> and the newer card has <code>0E 51 31 01</code>.

I refer to the '''Smart card ATR parsing'''<ref>[https://smartcard-atr.apdu.fr/ Smart card ATR parsing] ''smartcard-atr.apdu.fr''</ref> tool and enter luu176's ATR. The tool gives the following response<ref>[https://smartcard-atr.apdu.fr/parse?ATR=3B+88+80+01+04+02+00+20+00+71+C1+40+DF "Parsing ATR: 3B 88 … result"] ''smartcard-atr.apu.fr''</ref>:

* TS = 0x3B - Direct Convention
* T0 = 0x88 Y(1): b1000, K: 8 (historical bytes)
* TD(1) = 0x80 Y(i+1) = b1000, Protocol T=0
* ----
* TD(2) = 0x01 Y(i+1) = b0000, Protocol T=1
* ----
* Historical bytes 04 02 00 20 00 71 C1 40
* Category indicator byte: 0x04 (proprietary format) ".. .q.@"
* TCK = 0xDF '''correct checksum'''
<references />

T-Money - Revision history

Justus at 08:10, 13 February 2026