Agnos Framework supports both contact and contactless transactions. The difference between the configuration paradigms is:
In contact (acronyms K or CT), configurations are AID driven. There are 2 files: TERMINAL (RAW or TLV format), and PROCESSING (RAW or TLV format)
In contactless (acronym CL), configurations are KAT driven. KAT stands for Kernel Id / AID Id / Transaction Type id. There are 5 files: TERMINAL (RAW or TLV format), PROCESSING (RAW or TLV format), ENTRY_POINT (RAW or TLV format), SUPPORTED AID (RAW format only), COMBINATION (RAW format only), and UPDATE CONDITIONS (TLV format)
For more details, see:
SUPPORTED_AID (deprecated. RAW format only)
COMBINATION (deprecated RAW format only)
UPDATE CONDITIONS (where <update conditions> ::= UC + '_' + 'C' + <kernel id>)
Data Model
...
That section presents how different abstractions related to the system’s configuration are linked all together. These abstractions are usually part of a TMS system and downloaded onto the point of acceptance, i.e. the terminal running Agnos. There are different perspectives attached to a data model:
...
The transportation model is not presented in that document because it’s specific to the infrastructure integrating Agnos. Depending on the acquirer/processor TMS system, the data model may be transported using XML files, a series of protocol messages (like EPAS NEXO TMS or ISO8583), or even proprietary structures (there might be no model at all).
...
Note: If a L3 Application uses OLA, the persistent model depends on the payment application. In the other words, the way to store the configuration data is the responsibility of the integrators. As a reference, Agnos uses the following values for data configuration:
Data Model
Agnos Framework supports both contact and contactless transactions. The difference between the configuration paradigms is:
In contact (acronyms K or CT), configurations are AID driven. There are 2 files: TERMINAL (RAW or TLV format), and PROCESSING (RAW or TLV format)
In contactless (acronym CL), configurations are KAT driven. KAT stands for Kernel Id / AID Id / Transaction Type id. There are 5 files: TERMINAL (RAW or TLV format), PROCESSING (RAW or TLV format), ENTRY_POINT (RAW or TLV format), SUPPORTED AID (RAW format only), COMBINATION (RAW format only), and UPDATE CONDITIONS (TLV format)
For more details, see:
SUPPORTED_AID (deprecated. RAW format only)
COMBINATION (deprecated RAW format only)
UPDATE CONDITIONS (where <update conditions> ::= UC + '_' + 'C' + <kernel id>)
Contact Kernel Settings
Conctact configurations are made of list of AID. Each AID comes along with a set of EMV parameters.
...