| Table of Contents |
|---|
To start, here is a standard definition of a framework:
“In general, a framework is a real or conceptual structure intended to serve as a support or guide for the building of something that expands the structure into something useful. In computer systems, a framework is often a layered structure indicating what kind of programs can or should be built and how they would interrelate. Some computer system frameworks also include actual programs, specify programming interfaces, or offer programming tools for using the frameworks. A framework may be for a set of functions within a system and how they interrelate; the layers of an operating system; the layers of an application subsystem; how communication should be standardized at some level of a network; and so forth. A framework is generally more comprehensive than a protocol and more prescriptive than a structure”
Introduction
These Wiki pages provide a global perspective of the framework, To start:
See Overview page.
See Integration Model page.
Furthermore, EMVCo reference documents (books I to IV for contact and books A/B/D for contactless) may be used to get information related to EMV standard (https://www.emvco.com/document-search/).
This document is the main source of information to help using Agnos Framework developers. Also, .h files should be used in priority to get detailed information on the API.
Warning
Agnos Framework Wiki pages don’t aim to describe Payment Network requirements. For more details on payment applications and kernels specifications, please refer to relevant documents (including books Cx from EMVCo, and current Payment Networks specifications).
Kizis application (Level3) is dedicated to:
EMVCo contact L2 certification test requirements (i.e. book IV)
Payment Network contactless “kernels” certification test requirements (i.e. books Cx)
This example doesn’t aim to match a set of specific merchant/acquirer/processor needs. Hence, a new software application analysis/design shall be initiated in regards with specific regional requirements. Sample codes may be reused to structure the new applications to be developed.
Wiki's Organization
This wiki has been organized from a standard Agnos porting project plan.
See All Models.