Amadis

Exit Conditions (Events)

Owned by Daniel Boucher (Unlicensed)
Last updated: Aug 19, 2021
2 min read

Exit Conditions allows Kizis to get control when specific Events occur during the L2 Payment Transaction

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:

Sample Exit Condition Flow during a L2 Payment Transaction

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.