Documentation under development…
This is a new features brought by AGF 3.5.x. Documentation under development…While callback mechanism is interesting to extend L2 logic and to control the processing card flow from the L3, it has a major drawback: the calling stack is not empty the time the flow exits the L2 logic. Should the L3 need to stop the transaction during the callback, it needs to come back to the L2. That alternative is not always possible depending on the architecture. Exit Conditions is an answer to that constraint.
Exit Conditions mechanismdefines a series of events depending on the technoloogy:
For contact, it is possible to stop the EMV card flow ateach EMV step and resume it
Fonr contactless.
CONTACT EVENTS | |
EC_CNT_EVENT_GET_PSE_FCI | |
EC_CNT_EVENT_GET_CANDIDATE_LIST | |
EC_CNT_EVENT_PROCESSING | |
EC_CNT_EVENT_GET_FINAL_SELECT_FCI | |
EC_CNT_EVENT_GET_GPO | |
EC_CNT_EVENT_APP_DATA_AVAILABLE | |
EC_CNT_EVENT_RESTRICTION_PERFORMED | |
EC_CNT_EVENT_ODA_PERFORMED | |
EC_CNT_EVENT_CVM_PERFORMED | |
EC_CNT_EVENT_TRM_PERFORMED | |
EC_CNT_EVENT_TAA_PERFORMED | |
EC_CNT_EVENT_CAA_PERFORMED | |
EC_CNT_EVENT_GET_FIRST_GEN_AC | |
EC_CNT_EVENT_GET_PIN | |
EC_CNT_EVENT_ISSUER_SCRIPT_1_RESULTS | |
EC_CNT_EVENT_GET_SECOND_GEN_AC | |
EC_CNT_EVENT_ISSUER_SCRIPT_2_RESULTS | |
CONTACTLESS EVENTS | |
EC_CTLSS_EVENT_GET_PRE_PROCESSING_RESULT | |
EC_CTLSS_EVENT_STATUS_READY_TO_READ | |
EC_CTLSS_EVENT_COLLISION_DETECTED | |
EC_CTLSS_EVENT_CARD_DETECTED | |
EC_CTLSS_EVENT_GET_PPSE_FCI | |
EC_CTLSS_EVENT_GET_CANDIDATE_LIST | |
EC_CTLSS_EVENT_GET_FINAL_SELECT_FCI | |
EC_CTLSS_EVENT_STATUS_PROCESSING | |
EC_CTLSS_EVENT_APP_DATA_AVAILABLE | |
EC_CTLSS_EVENT_STATUS_CARD_READ_SUCCESSFULLY | |
EC_CTLSS_EVENT_SEE_PHONE | |
EC_CTLSS_EVENT_REMOVE_CARD | |