80

Response Message Template Format 1 is the older, more compact of the two ways a card can answer GET PROCESSING OPTIONS: a single primitive value with no internal tags at all, where the first two bytes are always the Application Interchange Profile (82) and everything after that is the Application File Locator (94), in that fixed order, both already covered individually in this dictionary. There's no flexibility in this format - a terminal parsing 80 doesn't read tags, it reads byte positions, which makes it fast and simple but also fragile: any card that needs to return anything beyond exactly AIP-then-AFL cannot use this format at all and has to use its more flexible sibling, Response Message Template Format 2 (77, referenced alongside it), instead. A terminal library that assumes every GPO response comes back tagged, because it only ever tested against 77-style cards, will silently mis-parse a card that legitimately answers with 80, treating its raw AIP-plus-AFL bytes as if they were TLV-structured data they never were. See EMV Contactless Book C-2.