Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

Agnos Framework Wiki is meant to help technical teams to integrate, and to implement payment solutions using Agnos Framework. It provides a global perspective of the framework, and may be read in conjunction with the GPI integration & certification guide [1], the Agnos EMV library API specification [2], and Sample Codes [3] in order to get more details on each architecture's layer:

...

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).

...

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 around a standard Agnos porting project plan with the following main sections:

  1. Architecture Model: a 3-tiers model depicts the EMV project structure used by Agnos

  2. Integration Model: 3+1-level model of integration (GPI, ACE, Level3 + CL Kernel) explains how to specialize Agnos Framework

  3. Configuration Model: a data model is presented along with all specific tags's values to be used

  4. Testing Model: 2 test tools are documented to present how Agnos Framework may be qualified and certified

  5. Deployment Model: a deployment is proposed to run Agnos Framework on a production environment

Context

Getting Started