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:
...
Kernel | Kernel Identifier | Kernel Default Setting |
|---|---|---|
n/a | 1 | |
Mastercard Contactless | 2 | |
Visa VCPS | 3 | |
American Express ExpressPay | 4 | |
JCB J/Speedy | 5 | |
Discover DPAS | 6 | |
CUP Overseas | 7 | |
Interac Flash | 8 (Agnos Framework 3.1.x) or 65 (from Agnos Framework 3.2.x) | |
RuPay qSPARC | 13 (from Agnos Framework 3.2.x) | |
EFTPOS | 66 (from Agnos Framework 3.2.x) | |
Gemalto PURE | 67 (from Agnos Framework 3.2.x) | |
Idemia Wise | 68 (from Agnos Framework 3.2.x) | |
Bancomat | 69 (from Agnos Framework 3.2.x) |
Note: Agnos Framework supports up to 255 kernel identifiers to comply with EMVCo Book B certification requirements.
...
The persistent model may be generated using INI files. See INI File Management page.