Avtor CryptoCard337 v1

3B 98 10 81 31 FE 43 30 41 56 54 ?? ?? ?? 02 ??
mask: FFFFF0FFFFFFFFFFFFFFFF0000000200
← All cards
2
Total reports
0%
Success rate
2020
First report
2020-02-20
Last report
ATR Analysis ISO 7816-3 · local Full analysis on smartcard-atr.apdu.fr ↗
Convention
direct
Protocol
T=1
IFSC (TA3, T=1)
254 bytes
Waiting times (TB3, T=1)
CWI=3 (CWT=19 etu), BWI=4 (BWT≈5,713,920 etu)
Historical bytes
30415654??????02
Proprietary / unstructured
TCK checksum
✗ invalid 00
# Byte Name Description
0 3B TS Direct convention (TS = 3B)
1 98 T0 Format byte: 8 historical bytes, Y1=0b1001 (TA1=present, TB1=absent, TC1=absent, TD1=present)
2 10 TA1 TA1: Fi=372, Di=RFU
3 81 TD1 TD1: T=1 protocol indicator, Y2=0b1000 (TA2=absent, TB2=absent, TC2=absent, TD2=present)
4 31 TD2 TD2: T=1 protocol indicator, Y3=0b0011 (TA3=present, TB3=present, TC3=absent, TD3=absent)
5 FE TA3 TA3: IFSC=254 (max information field size for card)
6 43 TB3 TB3: CWI=3 (CWT=19 etu), BWI=4 (BWT≈5,713,920 etu)
7 30 T1 Historical byte 1
8 41 T2 Historical byte 2
9 56 T3 Historical byte 3
10 54 T4 Historical byte 4
11 ?? T5 Historical byte 5 masked
12 ?? T6 Historical byte 6 masked
13 ?? T7 Historical byte 7 masked
14 02 T8 Historical byte 8
15 ?? TCK Check byte: XOR(T0…TCK) = F4 → ✗ INVALID masked
⚠ TCK check failed — ATR may be corrupted or masked

4 bytes are shown as ?? because the ATRMask at those positions is 00 — these bits are variable across card instances and were not recorded. The analysis above is based on the known bytes only. Use smartcard-atr.apdu.fr with your card's real ATR for a complete decode.

Software compatibility

Software Version Reports Success rate
EIDAuthenticate 1.2.6.0 2
0%
Details

Operating system compatibility

OS Architecture Service pack Reports Success rate
Windows Server 2012 x64 — 2
0%
Details

Provider / middleware compatibility

Provider DLL Version Company Reports Success rate
Microsoft Base Smart Card Crypto Provider avC337d1.dll 1.8.3.0 AVTOR LLC 2
0%
Details