Page Comparison

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)

...

• TERMINAL

• PROCESSING

• ENTRY POINT

• SUPPORTED_AID (deprecated)

• COMBINATION (deprecated)

• UPDATE CONDITIONS (where <update conditions> ::= UC + '_' + 'C' + <kernel id>)

...

Persistent Model

The persistent model is specific to Agnos. It’s important to learn that model because it’s used by the framework to get ready to process transactions. That model is built from the transportation data and stored onto the terminal. From Agnos Framework 2.x.x, there are 2 persistent models:

1. The legacy RAW files including TERMINAL, PROCESSING, ENTRY_POINT, AID, and COMBINATION. The structures of these files are documented in Appendixes.

2. The TLV files including TERMINAL, PROCESSING, and ENTRY_POINT. The structures of these files are documented in Appendixes.

Note1: Agnos Framework architecture uses the same data model as for ACE (client and server parts). ACE is optional to develop and to certify Agnos applications. But, the transportation layer (ACE2P protocol) that is used maps the persistent model to ease the integration.

Note2: Knowing ACE2P, ACE may be used without Agnos to certify any EMV stacks on any terminal. This allows a terminal to fetch configuration data required for certification sessions (CAPK, list of AIDs and underlying parameters …).

...

Note: Agnos Framework supports up to 255 kernel identifiers to comply with EMVCo Book B certification requirements.

...