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 |