This section presents the reference values used to qualify Agnos L2 stack for all payment networks depicted below.
ICS stands for Implementation Conformance Statement. It corresponds to a series of card processing features that may be optional or mandatory depending on different factors including regulatory ones. In practice, these features correspond to business requirements that shall be certified at the “L2” and made available to “L3”.
For all the ICS references below, and Agnos' options:
Optional means that the option may be set to Yes or No for a given ICS
Conditional means that the option shall be set to Yes if the condition is met
Variable means that the option is discrete
Mandatory along with Yes/Fixed means that Agnos cannot be set differently
Mandatory along with No or a discrete value means that Agnos doesn't support the option yet. Contact us for more details
For all the ICS references below, and Agnos options comments:
L3 perspective means that current Agnos implementation doesn't prevent the addition of the option after L2 certification (i.e. option is out of card processing/L2 scope)
For all the ICS references below, and Agnos options recommendations:
Wiki presents possible choices independently from platforms and customers requirements. Hence, it presents most frequent settings
For all the ICS references below, and default Agnos options values:
See Configuration Model page for each payment network
Brand | ICS Reference |
|---|---|
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
RuPay | NPCI's specifications. Contact us |
 | |
 | |
 | This kernel has no L2 certification decorrelate from L3 integration. Contact us |
 | Idemia’s Wise specifications. Contact us |
 | This kernel has no L2 certification decorrelate from L3 integration. Contact us |
 | European CPACE specifications. Under development… |
 | NSPK’s specifications. Under development… |