Exit Conditions allows Kizis to get control when specific Events occur during the L2 Payment Transaction
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
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
...
...
Kizis can interrupt the execution of a Transaction in Agnos to get the Status about specific Events, some example of Registered Events:
Get Pre-Processing Result
Get Card Detection Result
Get PPSE Selection Result
Get Build Candidate List Result
Get Final Selection Result
…
Kizis can set interruption of such Events through Exit Conditions, the Exit Conditions for the Contact interface are listed in <> and in <> for the Contactless Interface
Kizis sets the Exit Conditions (Events) that will interrupt the normal Payment Transaction execution
An Exit Condition is not a Callback in the sense that the execution of Agnos is interrupted, whereas a Callback puts Agnos in a pending state until we return from the Callback
Each time AgnosSP sends back an Exit Condition Response instead of the START L2 PAYMENT TRANSACTION Response, Kizis needs to reactivate AgnosSP by sending a RESUME L2 PAYMENT TRANSACTION Request
(i.e. execution of AgnosSP (Agnos) is totally interrupted by the Exit Condition)
The RESUME L2 PAYMENT TRANSACTION Command automatically brings back the execution of AgnosSP (Agnos) where it left off by the Exit Condition
Exit Condition Flow
The following sequence diagram illustrates exchanges performed when Exit Conditions are triggered on Registered Events:
...
In this scenario, Kizis initialized the following Events to trigger Exit Conditions (these Exit Conditions can be set through the SET PARAMETER Command):
GET PRE-PROCESSING RESULT Event
GET CANDIDATE LIST Event
GET FINAL SELECT FCI Event
REMOVE CARD Event
For each Event, AgnosSP is returning details of each Exit Condition instead of returning the START L2 PAYMENT TRANSACTION Response right away.
This allows Kizis to take the appropriate actions and can include Exit Condition specific data to be sent back the AgnosSP through the RESUME L2 PAYMENT TRANSACTION Command.