Beyond the data model and the underlying persistent files, there are 3 other data files used by Agnos Framework to support specific EMV features:

1. CAKeys in order to support ODA (SDA, DDA, and CDA)

2. CRL in order to support revocated keys

3. EFL in order to support exception files list (not EMV related however)

CAKeys is mandatory and the GPI/DEVICE must implement the logic to interface to its structures. Howver, its structure can be reviewed as long as the GPI/DEVICE access services are adapted accordingly.

The 2 other files are optional and their presence depends on the ICS.

Public Keys Certificates Format (CAKeys file)

Following data are used only when EMV ODA is supported (for offline card authentication). These files are usually retrieved from acquirer’s or processor's host and transportation format is always specific. File format as described below presents how information shall be persisted in the terminal in order to allow Agnos library to work as designed. Related GPI primitive (see HSM/cacertificates.c/gpiGetEMVCertificate) may be overloaded to support a specific format different from the one below. For example, CAKeys file may be split up into different files sorted by RID.

Note: Concerning the transportation format, there is an additional 20 byte SHA-1 trailing at the end of the keys (when keys are received from ACE). But, this integrity trailer is not stored into CAKeys file.

Revocated Keys Format (CRL file)

Following data are used only when CRL is mandatory. This file is usually retrieved from acquirer’s / processor's host and transportation format is always specific. File format as described below presents how information shall be persisted in the terminal in order to allow Agnos library to work as designed. Related GPI primitive (see HSM/cacertificates.c/gpiGetEMVCRL) may be overloaded to support a specific format different from the one below.

Exception File List Format (EFL file)

Note: Agnos Framework specifies this format because this kind of file might be required to go to L2 TA (depends on ICS). However, it is a L3 consideration and it shouldn’t be part of the L2 definition. Agnos Framework provides callback mechanism to extend the card processing at L3 integration time with this requirement

Following data are used only when EFL is mandatory. This file is usually retrieved from acquirer’s / processor's host and transportation format is always specific. File format as described below presents how information shall be persisted in the terminal in order to allow Agnos library to work as designed. Related GPI primitive (see HSM/cacertificates.c/gpiFindPANFromEFL) may be overloaded to support a specific format different from the one below.