This section is DEPRECATED.
...
From Agnos Framework 2.x, it’s possible to use an .ini file to generate a set of binary data files (i.e. the persisted model) that are used by the framework to initialize internal structures (i.e. the instanciated model). Framework 3.2.x now provides a standard component, AgnosGE, that is optionnaly integrated at Level3.
INI File Structure
[Config] section
The following key is used:
...
Terminal=myTERMINAL
Processing=myPROCESSING
Entrypoint=myENTRY_POINT
Aid=myAID
Combination=myCOMBINATION
[Terminal] section
The following keys are used:
...
CountryCode=56
ProvideCardholderConfirmation=Yes
TerminalType=22
EMVContact=Yes
TerminalCapabilities=E0B0C8
AdditionalTerminalCapabilities=7000F0A001
EMVContactless=Yes
Magstripe=No
PinTimeOut=15
BatchManaged=Yes
AdviceManaged=Yes
PSE=Yes
Autorun=No
PredefinedAmount=0
PINByPass=0
ReferralManaged=0
DefaultTACSupported=0
TACDefault=0000000000
TACDenial=0000000000
TACOnline=0000000000
RTSNotSupported=0
VCNotSupported=0
CDAType=2
Clipping=No
SRED=No
[AID:kernelId] section
As an example, the following keys are used for a dual AID:
...
Note: AID shall be set to a value so that the section is parsed like [A0000000041010:2] where AID = A0000000041010 andd KernelId = 2
INI File Configuration
Contact
Contact configurations use only 2 files:
...
All possible tags are defined in Tags section.
Contactless
Implementing and certifying contactless payment application led to the following statement: there is a great functional inconsistency between all the brands generating a difficult integration level and complex user experience design. For examples, a brand might support torn transactions whereas the others don’t. This is the same for the support of the 2nd GenAC or the EMVCo risk management. Furthermore, each brand has specified its own tags where management rules may differs (for example one brand may allow private tags redundancy whereas others don’t). One could also discuss on data storage which suffers of a great lack of standardization.
...