Release Note

For EMV Library

Version 657
CONTENTS
1. Release Note ............................................................................................. 3
2. Applicable Products.................................................................................... 8
3. How to use linkF_XXX_LIB_vxxx.so and libF_XXX_LIB_vxxx.so ................ 9
1. Release Note

Date Version Note Author

2017.11.13 V650 1. Support Public library. Litun
2018.01.11 V650_01 1. Fixed the issue of using Litun
libF_EMV_LIB_PayDroid.so unsuccessfully.
2. Increase the Max AID number of candidate
list for F Serial libraries to be 17 to keep
compatibility with old version before v650.
3. Update the document <PAX EMV Kernel API
Programming Guide.pdf>.
4. For prolin platform, Add callback functions
cEMVPedVerifyPlainPin and
cEMVPedVerifyCipherPin in ApiMap_F to
keep compatibility with old version before
v650.
5. Update the document <PAX API Programming
Guide for emvlib.pdf>
2018.02.06 V650_02 1. Fix the issue of PBOC that the setting of Lijian
electronic cash transaction tag 9F7A was
inconsistent with the version before v650.
2. Update emvlib.c, For Prolin platform amend
callback functions DEVICE_SetCallback to fix
the issue that cEMVPedVerifyPlainPin and
cEMVPedVerifyCipherPin cannot be called
successfully.
3. Update emvlib.c, For PaxMe platform,
Initialize the CAPK list from file in
EMVCoreInit to fix the issue that CAPK
cannot be gotten after rebooting the
terminal.
2018.03.27 V651 1. According to the mandatory requirement of Zhengyq
EMV specification, change the default value
of ucUseTermAIPFlg and aucTermAIP of
EMV_II_TERMPARAM to support “TRM is
performed irrespective of card AIP”
2. Add return code description for
cEMVPedVerifyPlainPin
and cEMVPedVerifyCipherPin
3. The parameter pucPINCnt of
EMV_II_StartCVM won’t be increased 1
 anymore.
4. Fix a compatibility issue, change the AID
gotten by calling EMVGetFinalAppPara
from terminal AID to card AID finally
selected.
2018.05.03 V651_01 1. Add a new function for EMVSetExtendFunc Litun
and EMV_II_SetExtendFunc to change the
result of the Terminal Action Analysis.
2. Update the document <PAX API Programming
Guide for emvlib.pdf>
3. Update the document <PAX EMV Kernel API
Programming Guide.pdf>.
2018.06.15 V651_02 1. The transaction will not be terminated if the Litun
storage space of the unknown tag overflow.
2018.06.29 V651_03 1. The result of Terminal Analyze can only be Litun
changed from TC to ARQC by
EMV_II_SetExtendFunc and
EMVSetExtendFunc
2. Application could get the value of 5F2D by
using EMVGetTLVData after
EMV_II_AppSelect.
3. For prolin platform, Add callback functions
cEMVIccIsoCommand in emvlib.c to keep
compatibility with old version before v650
2018.08.25 V651_04 1. Fix an issue that the transaction was not Litun
terminated in time if the card has been
removed when there are multiple AIDs in the
candidate list.
2018.09.06 V652 1. From v650 on, please note that EMVCoreInit Litun
shall be called firstly for every transaction to
avoid memory overflow.
2. Add two new APIs: EMV_II_GetCandList
and EMV_II_SetCandList.
2018.10.25 V652_01 1. Fix the issue that PSE select method can’t be Litun
used normally.
2. Update the emvlib.c to fix the issue for
contactless PBOC can’t get the aid
information from entry.
2018.11.19 V652_02 1. Fix the issue that global variable gl_aucSN is Litun
conflicted between EMV_LIB_v652_01 and
ClsslibFlash_v201.
2018.11.27 V652_03 1. Fix the issue that EMV_II_SetTLVDataList Litun
can’t be used normally.
2019.03.22 V652_04 1. Optimize a temporary variable of candidate Zhengyq
list to reduce stack space.
2. Update the emvlib.c to fix the issue that
transaction log can’t be recorded correctly
when total number is over 8.
Note: If A_EMV_LIB_vxxx.a is used, the
Macro definition _D180_TERM shall be
defined in the application project
configuration or EmvIIApi.h to ensure the
value of MAX_APP_ITEMS is 5 for the
application.
2019.05.14 V652_05 1. DEVICE_CALLBACK related processing is Litun
added in EMVAppSelect in ApiMap_A. If this
function is required,
DEVICE_CALLBACK_ENABLE shall be defined
by the application project before
compilation.
2. Add a new function EMVGetExtendFunc in
ApiMap_F to get the value of the tag 9F11 for
every application in candidate list.
2019.07.18 V652_06 1. Fix an issue that CVM result cannot be gotten Litun
correctly.
2019.09.19 V653 1. Add a new function in Litun
EMV_II_SetExtendFunc to set the kernel type
to switch different processing for EMV, PBOC,
NSICCS.
2. Add processing of three bytes proprietary tag
in EMV_II_SetTLVDataList and
EMV_II_GetTLVDataList.
2019.11.08 V653_01 1. According to special requirement, if the Litun
candidate list is empty, EMVAppSelect and
EMV_II_AppSelect will return EMV_NO_APP
to indicate the detailed reason to terminate
transaction.
2020.10.30 V654 1. Add terminal type checking in Litun
EMV_II_FinalSelect to ensure that terminal
type value set by application is in the scope
defined by EMV specification.
2. Extend the Issuer Script device limit from 128
bytes to 256 bytes.
3. Support EMV Specification Bulletin
“SB-234-DOL-and-Constructed-Data-Objects”
Please note that v654 must be compiled with
 public library v109 or above.
2020.11.23 V654_01 1. Starting from this version, there is no limit to Zhengyq
the number of AID supported.
2020.12.14 V654_02 1. Fixed an issue caused by terminal type Zhengyq
setting.
2021.01.11 V654_03 1. Fix the issue caused by strcpy in emvlib.c . Litun
2021.03.11 V654_04 1. Fix the issue of V654_03 that unknown tag MabelCheng
added by application can not be filled in GPO
command successfully.
2021.11.10 V654_05 1. Fix the issue of V654_04 that kernel do not Litun
set TVR Byte3 bit8 when the bypass pin
happen.
2. Add new function for
EMV_II_SetExtendFunc and
EMVSetExtendFunc to check the app block
when building candidate list.
2022.01.20 V655 1. Support Issuer Identification Number MabelCheng
Extended (Tag 9F0C).
2. Add new function EMV_II_Checksum to
get EMV Kernel Checksum.
3. Add macro definition MEM_SMALL_TERM to
define the value of MAX_APP_ITEMS as 5 for
small memory product. It is suggested to
define MEM_SMALL_TERM or _D180_TERM
in EmvIIApi.h if MAX_APP_ITEMS is used by
applicaiton which uses A_EMV_LIB_vxxx.a.
4. For PBOC path, delete dual currency
electronic cash functionality related data
elements according to specification update.
5. Release library R_XXX_LIB.a for RunthOS
platform products. Please do not use any
ApiMap for RunthOS platform.
2023.09.07 V656 1. Extended the functions of ZhengRuiJia
EMV_II_GetExtendFunc to get response data LiZijia
of the final selection command and get
version number of the public library.
2. Supported to process script with length more
than 128 Bytes.
3. Optimized memory processing.
4. Text Content Revision
2024.04.28 V657 1. Updated MAX_APP_ITEMS to support 22 Zhengyq
candidate applications for F and R libraries.
2. Optimized data processing.
3. Supported EMV specification v4.4.
4. ucUseTermAIPFlg and aucTermAIP of
structure EMV_II_TERMPARAM were out of
use.
2. Applicable Products

The applicable products for different libraries shall be checked according to the
table below.
Libraries OS name L2 Kernel Name
A_XXX_LIB_vxxx.a PaxMe III A XXX LIB
F_XXX_LIB_vxxx.a PaxMe F XXX LIB
Or
libF_XXX_LIB_vxxx.so with
linkF_XXX_LIB_vxxx.so together.
libF_XXX_LIB_vxxx.so Prolin F XXX LIB
libF_XXX_LIB_PayDroid.so PayDroid F XXX LIB
libF_EMV_LIBC_PayDroid.so
R_XXX_LIB_vxxx.a RunthOS R XXX LIB
XXX: Kernel name, such as Entry, MC, WAVE, AE and so on.
vxxx: Kernel version.

APIMap_F and APIMap_A: There is an architecture adjustment from v604 to

v650; v650 has more detailed APIs then v604 that bring more flexibility.
However, in order to maintain the compatibility with the old architecture,
APIMap_F and APIMap_A are offered by v65x to convert the new APIs to the
old APIs,
 If v65x is updated for an old application, please include the corresponding
APIMAP files into the application project. APIMAP_F is used with the F
series library. While APIMAP_A is used with the A series library.
 If compatibility is not necessary for the application. Please don’t use these
two files. Since The APIs defined in EmvIIApi.h have more flexibility, and
the library will occupy less memory space without APIMAP.
3. How to use linkF_XXX_LIB_vxxx.so and
libF_XXX_LIB_vxxx.so

Note: All L2 libraries have the same compilation method. EMV / QPBOC / MC /
WAVE / AE / JCB / DPAS / FLASH / EFT / PURE / MIR/ WISE/ JT, etc.

Compile the application with gcc4.10 (Monitor Plus):

 Take the linkF_XXX_LIB_vxxx.so as dynamic library when compiling the
application as below:

 Download libF_XXX_LIB_vxxx.so along with the application by using the

PCLoader tool (both public So and private So are acceptable):
 Add libF_XXX_LIB_vxxx.so in the Prolin SDK for GCC Linker, notice that
it is
necessary to remove the prefix ‘lib’ and the postfix ‘.so’: