Amadis
Contact Exit Conditions
The following table lists the Contact Interface Events which can trigger an Exit Condition:
ID | Bitmap | Event Description | |||||||
b8 | b7 | b6 | b5 | b4 | b3 | b2 | b1 | ||
Byte 1 – Detection and Selection Events | |||||||||
11h | Â | Â | Â | Â | Â | Â | Â | 1 | Contact Card Detected |
13h | Â | Â | Â | Â | Â | 1 | Â | Â | Get Candidate List |
14h | Â | Â | Â | Â | 1 | Â | Â | Â | Processing |
15h | Â | Â | Â | 1 | Â | Â | Â | Â | Get Final Selection FCI |
- | x | x | x | Â | Â | Â | x | Â | RFU |
Byte 2 – Processing Events (1/2) | |||||||||
21h | Â | Â | Â | Â | Â | Â | Â | 1 | Initiate Application Processing Performed (GPO) |
23h | Â | Â | Â | Â | Â | 1 | Â | Â | Read Application Data Performed |
25h | Â | Â | Â | 1 | Â | Â | Â | Â | Processing Restrictions Performed |
26h | Â | Â | 1 | Â | Â | Â | Â | Â | Offline Data Authentication (ODA) Performed |
28h | 1 | Â | Â | Â | Â | Â | Â | Â | Cardholder Verification (CVM) Performed |
- | Â | x | Â | Â | x | Â | x | Â | RFU |
Byte 3 – Processing Events (2/2) | |||||||||
31h | Â | Â | Â | Â | Â | Â | Â | 1 | Terminal Risk Management (TRM) Performed |
33h | Â | Â | Â | Â | Â | 1 | Â | Â | Terminal Action Analysis (TAA) Performed |
36h | Â | Â | 1 | Â | Â | Â | Â | Â | 1st Generate Application Cryptogram Performed (Gen AC) |
38h | 1 | Â | Â | Â | Â | Â | Â | Â | Get PIN |
- | Â | x | Â | x | x | Â | x | Â | RFU |
Byte 4 – Completion Events | |||||||||
- | x | x | x | x | x | x | x | x | RFU |
Â