Exit Conditions allows Kizis to get control when specific Events occur during the L2 Payment Transaction
Further explanations on Exit Conditions can be found in the Section Basic Concepts
Contactless Exit Conditions
The following table lists the Contactless Interface Events which can trigger an Exit Condition:
ID | Bitmap | Description | |||||||
b8 | b7 | b6 | b5 | b4 | b3 | b2 | b1 | ||
Byte 1 – START-A Events | |||||||||
16h |
|
| 1 |
|
|
|
|
| Get Pre-Processing Result |
- | x | x |
| x | x | x | x | x | RFU |
Byte 2 – START-B Events | |||||||||
22h |
|
|
|
|
|
| 1 |
| Ready to Read Status |
24h |
|
|
|
| 1 |
|
|
| Contactless Collision Detected |
27h |
| 1 |
|
|
|
|
|
| Contactless Card Detected |
- | x |
| x | x |
| x |
| x | RFU |
Byte 3 – START-C Events | |||||||||
32h |
|
|
|
|
|
| 1 |
| Get PPSE FCI |
34h |
|
|
|
| 1 |
|
|
| Get Candidate List |
37h |
| 1 |
|
|
|
|
|
| Get Final Selection FCI |
- | x |
| x | x |
| x |
| x | RFU |
Byte 4 – START-D Events | |||||||||
41h |
|
|
|
|
|
|
| 1 | Processing Status (GPO) |
44h |
|
|
|
| 1 |
|
|
| Read Application Data Performed |
45h |
|
|
| 1 |
|
|
|
| Card Read Successfully Status |
46h |
|
| 1 |
|
|
|
|
| See Phone Requested |
47h |
| 1 |
|
|
|
|
|
| Card Removal Procedure |
- | x |
|
|
|
| x | x |
| RFU |