| Table of Contents |
|---|
Developer’s References
GPI implementation is a very important stage of a project integrating Agnos Framework. An appropriate platform shall be selected, and it must supports EMV processing, security requirements, and performance depending on a given context (See[1]).
Interface | Description |
|---|---|
gpi.h | All services related to administrative functions like logging |
gpicad.h | All services related to card device acceptance being contact, contactless, or magstripe |
gpidisplay.h | All services related to graphical or textual user interface including also leds and beeper |
gpihsm.h | All services related to cryptographic |
gpiplatform.h | All services related to platform OS like files management, random number generation, … |
gpisped.h | All services related to user key entry including the PIN |
gpilog.h | All services related to tracing in Agnos |
gpierrors.h | All constants related to errors encoding |
gpiutils.h | Few primitives for miscellaneous conversions |
...
Standard GPI versions that are delivered as an example target PC platform using PCSC readers
For the purpose of Agnos internal development process, GPI is integrated onto Agnos Automation, uses replay mechanisms and time stamping (See Compilation Options)
Agnos Framework is a generic software allowing certifying rapidly and efficiently a payment acceptance system without going through a full implementation of an EMVCo kernel and/or CL applications. The framework is provided along with code examples (GPI and Kizis). In these examples, Kizis uses the primitive gpiMain with 8 parameters:
...
to support other kind of GPI options that could be useful for any L3 (GPI/Platform).See also GPI Primitives References page
Additional information are available on demand from Developer’s Guide with limited accesses for confidentiality reasons. Contact us for more details.