| Table of Contents |
|---|
...
tPaymentContext (paymentMW.h)
Information provided by Level3: these data members must be filled up by the payment application integrating Agnos API. These data members are provided by a TRD trigggered by a sales system or a test environment (ACE)
Information set by Payment System:
mEMVContact/mEMVContactless/mMagstripe: these data members are initialized from TERMINAL file by AgnosEP at enpInitialize calling time. They are mandatory only when integrating a CL acceptance system supporting contact and/or magstripe
Tags 9F3A/9F3C/9F3D (meant for contact only): not used yet
Tag 5F57, account type (meant for contact and contacless): this data is used to set AgnosDB with from a TRD trigggered by a sales system or a test environment (ACE). If missing or lenth invalid 5F57 is systematically set to empty
Tag 9F39, POS entry mode (meant for contact and contactless):
Magstripe: set by payment application to MAG_MODE = 0x90
Contact: set by payment application to MAG_MODE = 0x05
Fallback from Contact to Magstripe: set by payment application to FALLBACK_MODE=0x80
Contactless: set by contactless card processing to EMV_CL_MODE=0x07 or MAG_CL_MODE=0x91
Tag 9F41, Transaction Counter (meant for contact only): this data member is used by emvco.c to demonstrate that each subsequent transsction can be indexed by a counter (for the purpose of L2 TA)
mARC (meant for contact and contactless): this data member is set by payment application just before completion from issuer response. It is used to set mCID to TC or AAC
mUnableToGoOnline (meant for contact only): this data member is set by payment application just before completion to indicate how to manage risk at GenAC2 time
Information set by Payment Application (from Agnos primitives):
mRID:
mADF:
mADFOrder:
Information set by EMV Library:
mSession
mCID
Information calculated by Level3: these data members are set automatically on at pmwSetEMVResult calling time. It shall be called at the end of any EMV contact transactions by payment application. It is systematically called by AgnosEP at the end of any contactless transaction
Level3<->Level2 communication: this data member is only meant for contactless transaction when supporting data exchange. Even if it is mandatory for few payment schemes during L2 TA, it is not mandatory to support it in production
...