TELIUM SDK

SDK Release Notes Archive

Ingenico - 190-192 avenue Charles de Gaulle - 92200 Neuilly-sur-Seine

Tél. 33(0)1 46 25 82 00 - Fax 33 (0)1 47 72 56 95 - [email protected]
 Release Note

Contents
SDK8.2.1 Technical Information Bulletin _____________________________________3
SDK8.2 Technical Information Bulletin _____________________________________ 13
SDK8.1.2 Technical Information Bulletin ___________________________________ 26
SDK8.1.1 Technical Information Bulletin ___________________________________ 36
SDK8.1 Technical Information Bulletin_____________________________________ 46
SDK8.0.2 Technical Information Bulletin___________________________________ 56
SDK8.0.1 Technical Information Bulletin ___________________________________ 64
SDK8.0 Technical Information Bulletin _____________________________________73
SDK7.6.1 Technical Information Bulletin ___________________________________ 85
SDK7.6 Technical Information Bulletin ____________________________________ 94
SDK7.5.2 Technical Information Bulletin ___________________________________ 107
SDK7.5.1 Technical Information Bulletin ___________________________________ 111
SDK7.5 Technical Information Bulletin ____________________________________ 117
SDK7.4.2 Technical Information Bulletin ___________________________________ 126
SDK7.4.1 Technical Information Bulletin ___________________________________ 131
SDK7.4 Technical Information Bulletin ____________________________________ 136
SDK7.3.2 Technical Information Bulletin ___________________________________ 147
SDK7.3.1 Technical Information Bulletin ___________________________________ 153
SDK7.3 Technical Information Bulletin ____________________________________ 159

For additional information, please contact your R&D Regional Interface

 Release Note

SDK8.2.1 Technical Information Bulletin

1. Standard development platforms

This SDK release is compatible with the following products.

1.1. List of terminals

1.1.1. Wireless
Telium 2:

iWL220B, iWL220G,

iWL250B, iWL250G ,

iWL250 3G,

iWL250 2SCR, 2SCR stands for 2 Smart Card Reader,

iWL280 (signature capture),

iWL350 (for development only)

Telium 1:

EFT930 colour,

EFT930 black and white.

1.1.2. Countertop terminals

Telium 2:

iCT220, iCT250,

iCT2xx PCI V3

E532

Telium 1:

EFT SMART Plus,

EFT SMART,

EFT30

1.1.3. Signature capture terminals (Retail pinpads)

iSC250,

iSC350

1.1.4. Pinpads
Telium 2:

iPP320, iPP350,

iPP3xx used as a smart card reader (Pinpad emulation mode).

Telium 1:

ML30, ML30 color, ML30 color contactless.

For additional information, please contact your R&D Regional Interface

 Release Note

‘Booster only’ pinpads:

iPP220, iPP250, iPP280, PPC30, PPR30, P30, P30 Contactless, PP30, PP30S.

iPP2xx PCI V3

1.1.5. Unattended
See UCM add-on package for the exhaustive list.

1.1.6. Satellite terminals

Telium 2:

iST150.

Telium 1:

TeliumPass Plus.

1.1.7. Mobile payment

Telium 2:

iMP3xx (only hardware V4 are supported since SDK 8.0.1),

SPM (iPA280).

1.1.8. French health care

TWINs.

1.2. Terminals certified PCI V3

The following terminals are certified for PCI V3:

iWL220 Since SDK 8.0.1

iWL250 Since SDK 8.0.1
iWL280 Since SDK 8.0.1
iSC250 Since SDK 8.0.1
iPP320 Since SDK 8.1
iPP350 Since SDK 8.1
iMP350 Since SDK 8.2
iCT2xx Since SDK 8.2
iPP2xx Since SDK 8.2

1.3. Public Key Infrastructure

This release supports PKI V3.

For additional information, please contact your R&D Regional Interface

 Release Note

2. What’s new?
Issues solved are detailed in paragraph 4.
Here are main evolutions coming with this Telium SDK release compared to the release 8.2.

2.1. Fixes
• It was not possible to use the SDK 8.2 on CAD30 range of product. During the start-up of these
terminals, a reset occurred while opening of the backlight device. This issue is fixed.

• Improvements of performance in GPRS mode

3. Highlighted points
3.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response;

Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC is not limited to banking cards. Direct communication to
other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection)

3.2. Contactless

3.2.1. Best practices for Contactless

3.2.1.1. Field on/off

The contactless field is to be activated only when a contactless card is waited by the terminal. It must be
stopped when the management of the contactless card is finished.

For additional information, please contact your R&D Regional Interface

 Release Note

If the contactless field is opened all the time:

On wireless terminals, product battery autonomy is reduced a lot;

The contactless module and antenna are highly stressed and reliability could decrease quickly
with time;
Applications have to manage the opening and the closing of the field according their business logic.

3.2.1.2. Implicit selection

Following terminals having the contactless feature inside are concerned: iWL2xx, iCT250, iSC2xx, iSC3xx,
EFT930 GCC, EFT930 BCC, iPP3XX, iPA280 (SPM), ML30C and P30C.

Implicit selection is not recommended and must be managed with caution.

Due to physical reason, implicit selection can lead to unexpected issues, for example, at the beginning
of the swipe, the card would possibly enter the antenna field and contactless chip would be handled
instead of magnetic track.

3.2.1.3.Use of PSTN modem with contactless activated

The electro-magnetic field created when the contactless is activated, on an integrated terminal,
prevents the usage of the PSTN modem with contactless activated.
This is not a software issue, and no software solution exists. The contactless field shall not be activated
at the same time as the modem.

Currently, the issue exists only on the iCT250, which is the only Ingenico integrated terminal with
contactless and PSTN modem.
(For instance, on EFT930BCC or EFT930GCC with modem, it works, because the modem is on the cradle,
and the distance between the modem and the contactless field is sufficient).

3.2.2. Add-on Contactless

The add-on contactless doesn’t exist anymore.
All components provided previously in this package are now by default since Telium SDK 8.1. It concerns

TPass library and component;

Entry point component;

GTL library;

Contactless sample.

3.2.3. Card supported

The list of cards supported by this SDK is given in the paragraph Erreur ! Source du renvoi introuvable.:
Erreur ! Source du renvoi introuvable. .

Recommendation:
Even if a card is managed since an old SDK or Add-On Contactless, usage of a recent SDK is strongly
recommend because bugs could have been fixed.

3.3. Family name

The family name, defined in the descriptor used to sign the binary, must follow the pattern
“<NAME><VV><AA>” where:

NAME is the radical of application (maximum 7 ASCII characters);

VV is the version (2 number);

AA is the amendment (2 number)

For additional information, please contact your R&D Regional Interface

 Release Note

3.4. Pinpad system

To avoid problems when a non mock-up pinpad is linked to a mock-up terminal, the terminal mock-up
catalogues don’t include pinpad systems. So, you have to load the pinpad system (located in the
directory “Component\OS”) according to the pinpad you are using.

3.5. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

3.6. Reserved numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.
Tag numbers used by applications must be taken in the range 9FA000-9FAFFF.

3.7. EFT930 embedding 8MB of flash

It is possible to use this SDK on EFT930 which has only 8 MB of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

For SDK 8.0.x, SDK 8.1 and SDK 8.1.1:

It is forbidden to load a catalogue designed for 8MB terminals on a terminal loaded with a generic
catalogue (that is to say non-8 MB). You must contact the Ingenico support for the rules of this
migration.

For additional information, please contact your R&D Regional Interface

 Release Note

4. Issues solved in this release by component

See table in chapter 6 “Versions of components” for the list of

versions of components provided in this Telium SDK.

4.1. Telium System

Main points delivered in this release are listed below.

4.1.1. System Thunder

Internal
SUPTEL Description
tracker
iMP3xx: In case of low battery level (<5%), the product goes automatically in
10866 "Limited Service" as for IWL products. In this case the Telium Manager
displays a pop-up information to plug the ISMP to a power Supply
11182
11191 GPRS functionality improved
11197

4.2. Telium Manager

4.2.1. Evolutions
Following points are delivered in this release.

Internal
SUPTEL Description
tracker
It was not possible to use the SDK 8.2 on CAD30 range of product.
10418 During the start-up of these terminals, a reset occurred while opening
of the backlight device. This issue is fixed.
GPRS dysfunction in Georgia with iCT220 fixed : time out value adapted
10830 SUPTEL-2922
to new SIM cards
11156 SUPTEL-3305 No more reboot on iWL 3G if 3G connection not established

4.3. Security

4.3.1. DLL Security

No evolution.

For additional information, please contact your R&D Regional Interface

 Release Note

4.3.2. Security Extend library

No evolution.

4.3.3. DLL E2EE

4.3.3.1. Overview
Binary is included in the Telium Manager catalogue.

It is provided for the following terminals:

iWL220, iWL250, iWL280,

iSC250, iSC350,

iMP350,

iPP320, iPP350,

iCT220, iCT250,

SPM.

4.3.3.2. Evolutions
No evolution.

4.3.4. Schemes
Last schemes certified are included in this SDK.

4.4. Communication

4.4.1. Link Layer

No evolution.

4.4.2. Pack IP
No evolution.

4.4.3. FTP
No evolution.

4.4.4. SNMP
No evolution.

4.4.5. SSL
No evolution.

4.5. Display

4.5.1. DLL Image

No evolution.

For additional information, please contact your R&D Regional Interface

 Release Note

4.5.2. Fonts
No evolution.

4.5.3. CGUI / CGUI tools

No evolution.

4.5.4. Plug-in Signature Capture

No evolution.

4.5.5. Plug-in Multimedia

No evolution.

4.6. Contactless

4.6.1. DLL TPass

No evolution.

4.6.2. Entry Point

No evolution.

4.6.3. TeliumPass
No evolution.

4.7. Applications

4.7.1. Incendo Online browser

Technical documentation and the Incendo SDK are provided with Ingedev (from version 7.8.0).

4.7.1.1. Memory
Before deploying this solution, please check the memory usage of your terminals.

4.7.1.2. Migration to this version

4.7.1.2.1. Migration from a version before 3.0.4

Incendo Online smart browser was previously delivered as an independent package (up to version
3.0.3). It was designed to be signed with region security keys.
The version in this Telium SDK is signed with manufacturer key. So the application type is different
between these two versions. If you have already deployed the browser, to migrate to the version
included in a Telium SDK, you must manage the change of application type. For further details, please
contact the Incendo support.

For additional information, please contact your R&D Regional Interface

 Release Note

4.7.1.3. Compatibility

4.7.1.3.1. Terminals managed

Minimal hardware prerequisites are:

Terminal is Ethernet or GPRS;

Terminals is Ingetrust ready;

Minimum of 16 MB of Flash is mandatory;

16 MB of RAM are recommended but not mandatory. 8 MB is possible if terminal is Incendo
Online only (no other applications).

Incendo Online is compatible with the following terminals:

EFT930 Color (Booster 2 type),

iCT220, iCT250,

iWL220, iWL250
You must not use it on other terminals.

Support of iSC250 and iSC350 will be available in a future release.

4.7.1.3.2. EMV packages compatibility

Incendo smart Browser is compatible with the following EMV packages:

Version 19 or 20.1

4.7.1.4. Evolutions
No evolution.

4.7.2. Image Loader

At the end of the Telium SDK setup you can choose to install Image Loader on your PC. Documentation
is available in this installed package.

4.7.2.1. Evolutions
No evolution.

4.8. AVL
AVL stands for Added Value Libraries.
No evolution.

4.9. Full configuration for local download for iPP320 in pinpad

emulation mode
A binary concatenates the Telium system (including contactless driver) and the Telium manager for an
iPP3 used in pinpad emulation for local download mode. It is delivered in the directory:
Component\iPP3_EmulationPinpad\Package
Please see description in the CHM help file of the Telium SDK (SDK General Documentation > HOW TO
DEVELOP user guide > How to use iPP3xx as a smart card reader).

For additional information, please contact your R&D Regional Interface

 Release Note

4.9.1. DLL PPLoad evolution

The DLL PPLoad is present in the host terminal and allows the loading of the full configuration to the
iPP3.
No evolution.

4.10. SDK features

Following points are delivered in this release.

Internal
SUPTEL Description
tracker
In the CHM help file provided in SDK 8.2, the search by index didn't work
11092
for some functions.

5. Add-ons to Telium SDK

The following table presents the versions of recommended add-ons to use with this SDK.

Recommended
Add on Comment
version to use with this SDK
Easy Path To EMV 20.1
Components previously in this
Add On Contactless (New
Removed add-on are in the Telium SDK
architecture) since 8.1
Easy Path To Contactless 3. 07

Add On PCL for iPA280 1.17

Add On PCL for iWP 1.15

Add On PCL for iMP3xx 1.01

Add On Morpho 1.06

Add On Telicapt 2.17

Add On UCM 2.06.01

Add On SPDH 1.01

Add On APACS 40 Generic 1.08

Add On ISO8583 Generic 3.02

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK8.2 Technical Information Bulletin

6. Standard development platforms

This SDK release is compatible with the following products.

6.1. List of terminals

6.1.1. Wireless
Telium 2:

iWL220B, iWL220G,

iWL250B, iWL250G ,

iWL250 3G (for production),

iWL250 2SCR, 2SCR stands for 2 Smart Card Reader,

iWL280 (signature capture),

iWL350 (for development only)

Telium 1:

EFT930 colour,

EFT930 black and white.

6.1.2. Countertop terminals

Telium 2:

iCT220, iCT250,

iCT2xx PCI V3

E532 (for production)

Telium 1:

EFT SMART Plus,

EFT SMART,

EFT30

6.1.3. Signature capture terminals (Retail pinpads)

iSC250,

iSC350

6.1.4. Pinpads
Telium 2:

iPP320, iPP350,

iPP3xx used as a smart card reader (Pinpad emulation mode).

Telium 1:

ML30, ML30 color, ML30 color contactless.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

‘Booster only’ pinpads:

iPP220, iPP250, iPP280, PPC30, PPR30, P30, P30 Contactless, PP30, PP30S.

iPP2xx PCI V3

6.1.5. Unattended
See UCM add-on package for the exhaustive list.

6.1.6. Satellite terminals

Telium 2:

iST150.

Telium 1:

TeliumPass Plus.

6.1.7. Mobile payment

Telium 2:

iMP3xx (only hardware V4 are supported since SDK 8.0.1),

SPM (iPA280).

6.1.8. French health care

TWINs.

6.2. Terminals certified PCI V3

The following terminals are certified for PCI V3:

iWL220 Since SDK 8.0.1

iWL250 Since SDK 8.0.1
iWL280 Since SDK 8.0.1
iSC250 Since SDK 8.0.1
iPP320 Since SDK 8.1
iPP350 Since SDK 8.1
iMP350 Since SDK 8.2

6.3. Public Key Infrastructure

This release supports PKI V3.

7. What’s new?
Issues solved are detailed in paragraph 4.
Here are main evolutions coming with this Telium SDK release compared to the release 8.1.2.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

7.1. New terminals

• IWL350 (for development only)
• IWL 250 3G is now delivered for production

7.2. Main evolutions

• New PID/VID managed,
• Improvements for iMP3xx,
• Swipe improvement on booster 3 terminals.

8. Highlighted points
8.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response;

Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC is not limited to banking cards. Direct communication to
other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection)

8.2. Contactless

8.2.1. Best practices for Contactless

8.2.1.1. Field on/off

The contactless field is to be activated only when a contactless card is waited by the terminal. It must be
stopped when the management of the contactless card is finished.
If the contactless field is opened all the time:

On wireless terminals, product battery autonomy is reduced a lot;

The contactless module and antenna are highly stressed and reliability could decrease quickly
with time;

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Applications have to manage the opening and the closing of the field according their business logic.

8.2.1.2. Implicit selection

Following terminals having the contactless feature inside are concerned: iWL2xx, iCT250, iSC2xx, iSC3xx,
EFT930 GCC, EFT930 BCC, iPP3XX, iPA280 (SPM), ML30C and P30C.

Implicit selection is not recommended and must be managed with caution.

Due to physical reason, implicit selection can lead to unexpected issues, for example, at the beginning
of the swipe, the card would possibly enter the antenna field and contactless chip would be handled
instead of magnetic track.

8.2.1.3. Use of PSTN modem with contactless activated

The electro-magnetic field created when the contactless is activated, on an integrated terminal,
prevents the usage of the PSTN modem with contactless activated.
This is not a software issue, and no software solution exists. The contactless field shall not be activated
at the same time as the modem.

Currently, the issue exists only on the iCT250, which is the only Ingenico integrated terminal with
contactless and PSTN modem.
(For instance, on EFT930BCC or EFT930GCC with modem, it works, because the modem is on the cradle,
and the distance between the modem and the contactless field is sufficient).

8.2.2. Add-on Contactless

The add-on contactless doesn’t exist anymore.
All components provided previously in this package are now by default since Telium SDK 8.1. It concerns

TPass library and component;

Entry point component;

GTL library;

Contactless sample.

8.2.3. Card supported

The list of cards supported by this SDK is given in the paragraph Erreur ! Source du renvoi introuvable.:
Erreur ! Source du renvoi introuvable. .

Recommendation:
Even if a card is managed since an old SDK or Add-On Contactless, usage of a recent SDK is strongly
recommend because bugs could have been fixed.

8.3. Family name

The family name, defined in the descriptor used to sign the binary, must follow the pattern
“<NAME><VV><AA>” where:

NAME is the radical of application (maximum 7 ASCII characters);

VV is the version (2 number);

AA is the amendment (2 number)

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

8.4. Pinpad system

To avoid problems when a non mock-up pinpad is linked to a mock-up terminal, the terminal mock-up
catalogues don’t include pinpad systems. So, you have to load the pinpad system (located in the
directory “Component\OS”) according to the pinpad you are using.

8.5. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

8.6. Reserved numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.
Tag numbers used by applications must be taken in the range 9FA000-9FAFFF.

8.7. EFT930 embedding 8MB of flash

It is possible to use this SDK on EFT930 which has only 8 MB of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

For SDK 8.0.x, SDK 8.1 and SDK 8.1.1:

It is forbidden to load a catalogue designed for 8MB terminals on a terminal loaded with a generic
catalogue (that is to say non-8 MB). You must contact the Ingenico support for the rules of this
migration.

9. Issues solved in this release by component

See table in chapter 11 “Version of components” for the list of

versions of components provided in this Telium SDK.

9.1. Telium System

Main points delivered in this release are listed below.

9.1.1. System Thunder

Internal
SUPTEL Description
tracker
9741 [CLESS] Possibiliy to allow driver Mifare to leave encrypted mode
9948 [CLESS] New cless driver for ASK cards. support CTS 512 and CTS 256 cards
[CLESS] Driver Mifare is now able to authenticate Mifare classic cards with 7
10515 SUPTEL-2912
bytes UID

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

[CLESS] global Mifare Classic authentication timeout is now 4 ms.

10605 SUPTEL-2955
add enhanced GPRS filtering GPRS
10526 fake reading detected even with magnetic head suitly connected to main board
GND
10717 Delivery = GPRS immunity improvement
Fixes terminal reset when SWP:ERC[FFFFFFF7] diagnostic found in
10338 SUPTEL-2775 BOOSTER.DIA file
Fixes some randoms ghost swipe card issues
10602 SUPTEL-2874 Swipe software improvement.
10743 SUPTEL-2874 [ICT220] Improvement in MagStripe reading
7752 Speed-up non-responding GPRS modem detection
SUPTEL-2194 et USBDEV_FIOCTL_START_HID and USBDEV_FIOCTL_STOP_HID are deprecated.
9452/10409 SUPTEL-2649 Use USBDEV_FIOCTL_SET_MODE to define the usb device mode
Adding SWI int PppSetDefaultOptions(struct PPP_IF *interface); that can be
9510 SUPTEL-2269 used for reseting PPP parameters
9748 [GPRS] Integration of the new module Hilo 3G
9915 Added image file for product ISCxxx to display in LLT mode
9996 LIFECOUNTER.DIA : SystemFioctl SYS_FIOCTL_RESET_LIFE_COUNTER added
10263 corrections in the documentation
Add possibility to load not signed video files and play it during the
10282 idle state to GROUP signed applications
10362 Functions added:SysParamIsString, SysParamGetString and SysParamSetString
Between 60 and 70 seconds, the standby delay didn't work properly (-> no
10368 SUPTEL-2823 standby).
10370 SWI Functions added: Reader_Mount and Pinpad_Mount
Fix for issue with TMA application (manufacturer software) and wireless
10390 terminal.
[iWL220][BlueTooth]:SET/CLEAR DTR managed, Modem ISDN TA is now
10402 supported
Added SystemFioctl SYS_FIOCTL_FTPS_DISABLE = 0x810F
Fioctl used to disable FTP server. This SystemFioctl must be called each time
10419 SUPTEL-2812 terminal reboots, for example in after_reset function
Bug fix when updating fonts (old naming fonts to STANDARD new naming
fonts): ISO1 to 844216vvrr ISO2 to 844216vvrr ISO3 to 844218vvrr ISO5 to
10464 SUPTEL-2870 844219vvrr ISO6 to 844213vvrr ISO7 to 844220vvrr ISO15 to 844221vvrr
New SystemFioctl : SYS_FIOCTL_GET_PRODUCT_FULL_REFERENCE
Used to read product ref (Level 3) string
10506 (for ex ICT220-01T1076C, Telium II and III only)
10524 SUPTEL-2738 [GPRS] switch back to automatic mode
10529 Documentation only
Unwanted characters removed from the start of IMSI (\r\nOK...) ; side effect on
10632 SUPTEL-2995 SDK 8.1 and SDK 8.1.x.
10679 [iWL220] Too dark printing if battery connected in running state fixed
10691 SUPTEL-3037 [GPRS] Clamp the radio level to 5, no matter what
Api added : SYS_FIOCTL_GET_PRODUCT_FULL_SERIAL_NUMBER to get the
10728 SUPTEL-3063 long serial number
SUPTEL-3064 +
10754 2943 Improvement in checking base status
10808 Improvement in PPP connection time

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

[iWL280] Low power procedure fixed to avoid reset when fopen

10877 SUPTEL-3095 ("CAM0","rw") is called just after shutdown();

Nota: FT 6833 (French healthcare: when SYS_FIOCTL_USB_DEVICE_SERIAL_NUMBER_ENABLE is used

in iWL terminal, USB serial number is also returned by blue tooth base) is fixed in SDK 8.1.3 but not in
SDK 8.2.

9.2. Telium Manager

9.2.1. Evolutions
Following points are delivered in this release.

Internal
SUPTEL Description
tracker
10831 [IWL280] behaviour of Manager menu improved

Fix for entry point GIVE_YOUR_SPECIFIC_CONTEXT while there is more

3702 2835 + 3094
than 15 applications
The terminal can perform an auto detection of pinpad in the menu
6928 pinpad type or when the terminal is started if the parameter pinpad is
set to yes
6990 Documentation improvement for entry functions
TFU4699 SBU
7549 French domain only. Doesn't format anymore TMS identifier with space
/ TFU4793 FR
8379 New product IWL350 screen and keyboard management
8539 SUPTEL-2210 Displays only pinpads allowed in the pinpad initialization menu.
USBDEV_FIOCTL_SET_VID and USBDEV_FIOCTL_SET_PID are
deprecated. Use USBDEV_FIOCTL_SET_MODE to define the usb device
9136 SUPTEL-1537
mode.
See HWCNF.PAR in CHM
10010 [IWL280] Restores user screen after SIM code entry
New menu to print/display current SDK in the terminal.
Message can be:
- "SDK x.x.x" when the terminal is loaded with Telium System and
Telium Manager coming from a SDK.
10026/10027
- "SDK unknown" when the terminal is not loaded with a SDK
(independant components).
- "SDK x.x.x Customized" when Telium System or Telium Manager had
been customized after the loading of a SDK
10108 New product iWL350 management
10127 Use "SEPA technology selection" into EMV selection.
On STATE ticket (via F > CONSULTATION / State). Replace "Flash Free"
10208 SUPTEL-2653
by "Code Free"
10328 SUPTEL-2818 Improvement for contactless documentation
Improved documentation for SLC_Ecart_heure() and
10343 SUPTEL-2752
USQ_Enlevermnsec()
10367 [iWL280] Hide mouse cursor at startup (default value).
10443 SUPTEL-2865 Function ConnectedToPower() added. It returns the charger state

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

10450 SUPTEL-2871 Complex key sequence to activate maintenance menu

10462 SUPTEL-2866 Documentation only
10492 SUPTEL-2182 SLSQ_GetSupportedLanguages function returns right value
Menu to enter "SIM CODE" is now available when both GSM and GPRS
10508
function are enabled
10510 SUPTEL-2836 Documentation for TAB_ENTRY_STRING added
10520 Bug in PrintPolice API fixed
10528 Documentation only
10553 Change header look for IWL280. Date field is bigger and centered.
10590 Add confirmation for pinpad emulation menu
10599 USB enum in mode "Terminal Ingenico" right
10626 GetPackInfos is now reentrant
Use "file_name" field of object_info_t structure instead of "name" field
to manage licence. !!!
File name format must be : <NAME><VV><AA> :
10640 SUPTEL-3000
1) NAME : radical of application (max 6 ASCII characters).
2) VV : amendment (2 number)
3) AA : version (2 number)
10642 SUPTEL-2953 New sample into CHM for _PrintBmpXY function
all G_Affiche_XXX functions have been translated in english.
#define G_DisplayMSGcust G_AfficherMSGcust
#define G_DisplayMSG G_AfficherMSG
#define G_DisplayMSGnum G_AfficherMSGnum
#define G_DisplayPprMSG G_AfficherPprMSG
10649 #define G_DisplayPprMSGnum G_AfficherPprMSGnum
#define G_DisplayC30MSG G_AfficherC30MSG
#define G_DisplayC30MSGnum G_AfficherC30MSGnum
#define G_Display G_Afficher
#define G_DisplayPpr G_AfficherPpr
#define G_DisplayC30 G_AfficherC30e_XXX
10657 SUPTEL-3018 New menu to disable Footer.
SendToAllApplication,SendToApplication,SendToTask must return
10658 SUPTEL-3011
FALSE when mailbox is full.
New menu to change PUK code of SIM. Only available when GPRS
10659 SUPTEL-2947 driver return DGPRS_SIM_PUK_REQUIRED at startup. !!! New sim code
will be "0000"
Automatic connexion to GPRS : time out value adapted to new SIM
10830 SUPTEL-2922
cards
Improvement in displaying the software configuration application :
10880 SUPTEL-2952
nameNumber of responses to IS_NAME is checked
10884 SUPTEL-3113 [iWL250] In the Header the bitmap 3G replace the bitmap GPRS
Sample dll 4595xxyy.LGN or 3595xxyy.SGN is no longer delivered as
10885 SUPTEL-3154
unnecessary

9.3. Security

9.3.1. DLL Security

Following point is delivered in this release.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Internal
SUPTEL Description
tracker
10107/10416 New product iWL management

9.3.2. Security Extend library

No evolution.

9.3.3. DLL E2EE

9.3.3.1. Overview
Binary is included in the Telium Manager catalogue.

It is provided for the following terminals:

iWL220, iWL250, iWL280,

iSC250, iSC350,

iMP350,

iPP320, iPP350,

iCT220, iCT250,

SPM.

9.3.3.2. Evolutions
No evolution.

9.3.4. Schemes
Last schemes certified are included in this SDK.

9.4. Communication

9.4.1. Link Layer

No evolution.

9.4.2. Pack IP
Following points are delivered in this release.

Internal
SUPTEL Description
tracker
10661 New api : PPPSetDefaultOptions function exported

9.4.3. FTP
Internal evolution only

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

9.4.4. SNMP
No evolution.

9.4.5. SSL
Following points are delivered in this release.

Internal
SUPTEL Description
tracker
10647 SUPTEL-3009 CHM documentation
10773 SUPTEL-3047 Improvement in SSL DLL when low memory size available in terminal
10835 SUPTEL-3047 Correct memory leak when SSL connection failed with an error of DNS
Add verification of the server name and the CommonName in server
10874
certificate

9.5. Display

9.5.1. DLL Image

No evolution.

9.5.2. Fonts
No evolution.

9.5.3. CGUI / CGUI tools

No evolution.

9.5.4. Plug-in Signature Capture

No evolution.

9.5.5. Plug-in Multimedia

No evolution.

9.6. Contactless

9.6.1. DLL TPass

No evolution.

9.6.2. Entry Point

Following point is delivered in this release.
Internal
SUPTEL Description
tracker
[CLESS] Buffer overflow during random number generation on products without
10374 Booster (iST150 in intelligent mode or CAD30 without a pinpad or chip reader
connected)

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

9.6.3. TeliumPass
No evolution.

9.7. Applications

9.7.1. Incendo Online browser

Technical documentation and the Incendo SDK are provided with Ingedev (from version 7.8.0).

9.7.1.1. Memory
Before deploying this solution, please check the memory usage of your terminals.

9.7.1.2. Migration to this version

9.7.1.2.1. Migration from a version before 3.0.4

Incendo Online smart browser was previously delivered as an independent package (up to version
3.0.3). It was designed to be signed with region security keys.
The version in this Telium SDK is signed with manufacturer key. So the application type is different
between these two versions. If you have already deployed the browser, to migrate to the version
included in a Telium SDK, you must manage the change of application type. For further details, please
contact the Incendo support.

9.7.1.3. Compatibility

9.7.1.3.1. Terminals managed

Minimal hardware prerequisites are:

Terminal is Ethernet or GPRS;

Terminals is Ingetrust ready;

Minimum of 16 MB of Flash is mandatory;

16 MB of RAM are recommended but not mandatory. 8 MB is possible if terminal is Incendo
Online only (no other applications).

Incendo Online is compatible with the following terminals:

EFT930 Color (Booster 2 type),

iCT220, iCT250,

iWL220, iWL250
You must not use it on other terminals.

Support of iSC250 and iSC350 will be available in a future release.

9.7.1.3.2. EMV packages compatibility

Incendo smart Browser is compatible with the following EMV packages:

Version 19 or 20.1

9.7.1.4. Evolutions
This release includes the following main points:

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

• Simplification of TML language: Incendo Online 3.1 proposes a couple of enhancements in the
TML syntax to simplify operations on strings and lists.
• Improvement of user-interface: “full-color” and transparency modes are now supported,
resulting in brighter and colourful background and user-interface.
• Other new functionalities extending Incendo Online capabilities, such as the ability to send
batches of HTTP Get requests in order to increase overall speed of service.

See details in document provided with the application IncendoBrowser.

9.7.2. Image Loader

At the end of the Telium SDK setup you can choose to install Image Loader on your PC. Documentation
is available in this installed package.

9.7.2.1. Evolutions
No evolution.

9.8. AVL
AVL stands for Added Value Libraries.
No comment: only internal change

9.9. Full configuration for local download for iPP320 in pinpad

emulation mode
A binary concatenates the Telium system (including contactless driver) and the Telium manager for an
iPP3 used in pinpad emulation for local download mode. It is delivered in the directory:
Component\iPP3_EmulationPinpad\Package
Please see description in the CHM help file of the Telium SDK (SDK General Documentation > HOW TO
DEVELOP user guide > How to use iPP3xx as a smart card reader).

9.9.1. DLL PPLoad evolution

The DLL PPLoad is present in the host terminal and allows the loading of the full configuration to the
iPP3.

9.10. SDK features

Following points are delivered in this release.

Internal
SUPTEL Description
tracker
8918 Added information about SWIs in the Telium SDK help file
10456 SUPTEL-2870 Fonts provided with this SDK are compatible with ZKA terminals
10027 SDK release available in Software Configuration menu

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

10. Add-ons to Telium SDK

The following table presents the versions of recommended add-ons to use with this SDK.

Recommended
Add on Comment
version to use with this SDK
Easy Path To EMV 20.1
Components previously in this
Add On Contactless (New
Removed add-on are in the Telium SDK
architecture) since 8.1
Easy Path To Contactless 3. 07

Add On PCL for iPA280 1.17

Add On PCL for iWP 1.15

Add On PCL for iMP3xx 1.01

Add On Morpho 1.06

Add On Telicapt 2.16

Add On UCM 2.06.01

Add On SPDH 1.01

Add On APACS 40 Generic 1.08

Add On ISO8583 Generic 3.02

11. Version of components

The following table compiles the versions of components provided in this version of the SDK and in the
previous ones.
In this table, grey cells correspond to evolution of the component.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK8.1.2 Technical Information Bulletin

12. Standard development platforms

This SDK release is compatible with the following products.

12.1. List of terminals

12.1.1. Wireless
Telium 2:

iWL220B, iWL220G,

iWL250B, iWL250G ,

iWL250 3G (for development only),

iWL250 2SCR, 2SCR stands for 2 Smart Card Reader,

IWL280 (signature capture).

Telium 1:

EFT930 colour,

EFT930 black and white.

12.1.2. Countertop terminals

Telium 2:

iCT220, iCT250,

E532 (for development only)

Telium 1:

EFT SMART Plus,

EFT SMART,

EFT30

12.1.3. Signature capture terminals (Retail pinpads)

iSC250,

iSC350

12.1.4. Pinpads
Telium 2:

iPP320, iPP350,

iPP3xx used as a smart card reader (Pinpad emulation mode).

Telium 1:

ML30, ML30 color, ML30 color contactless.

‘Booster only’ pinpads:

iPP280, iPP250, iPP220, PPC30, PPR30, P30, P30 Contactless, PP30, PP30S.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

12.1.5. Unattended
See UCM add-on package for the exhaustive list.

12.1.6. Satellite terminals

Telium 2:

iST150.

Telium 1:

TeliumPass Plus.

12.1.7. Mobile payment

Telium 2:

iMP3xx (only hardware V4 are supported since SDK 8.0.1),

SPM (iPA280).

12.1.8. French health care

TWINs.

12.2. Terminals certified PCI V3

The following terminals are certified for PCI V3:

iWL220 Since SDK 8.0.1

iWL250 Since SDK 8.0.1
iWL280 Since SDK 8.0.1
iSC250 Since SDK 8.0.1
iPP320 Since SDK 8.1
iPP350 Since SDK 8.1

12.3. Public Key Infrastructure

This release supports PKI V3.

12.4. Location for system components

System for iMP3xx is located in Component\OS_iMP3xx
System for iWL280 is located in Component\OS_iWL280

13. What’s new?

Issues solved are detailed in paragraph 4.
Here are main evolutions coming with this Telium SDK release compared to the release 8.1.1.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

13.1. Terminals

This release is compatible with IWL280. It was not compatible with the SDK 8.1.1.

13.2. Fixes

API returning VID is fixed

G_List_Entry() now uses Telium Manager fonts (_SMALL_,_MEDIUM_,...)

DLL CB2A: new rule for IPDU LONGUE

MAC address returned was wrong on iWL 250 Bluetooth associated with an Ethernet base

14. Highlighted points

14.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response;

Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC is not limited to banking cards. Direct communication to
other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection)

14.2. Contactless

14.2.1. Best practices for Contactless

14.2.1.1. Field on/off

The contactless field is to be activated only when a contactless card is waited by the terminal. It must be
stopped when the management of the contactless card is finished.
If the contactless field is opened all the time:

On wireless terminals, product battery autonomy is reduced a lot;

The contactless module and antenna are highly stressed and reliability could decrease quickly
with time;

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Applications have to manage the opening and the closing of the field according their business logic.

14.2.1.2. Implicit selection

Following terminals having the contactless feature inside are concerned: iWL2xx, iCT250, iSC2xx, iSC3xx,
EFT930 GCC, EFT930 BCC, iPP3XX, iPA280 (SPM), ML30C and P30C.

Implicit selection is not recommended and must be managed with caution.

Due to physical reason, implicit selection can lead to unexpected issues, for example, at the beginning
of the swipe, the card would possibly enter the antenna field and contactless chip would be handled
instead of magnetic track.

14.2.1.3. Use of PSTN modem with contactless activated

The electro-magnetic field created when the contactless is activated, on an integrated terminal,
prevents the usage of the PSTN modem with contactless activated.
This is not a software issue, and no software solution exists. The contactless field shall not be activated
at the same time as the modem.

Currently, the issue exists only on the iCT250, which is the only Ingenico integrated terminal with
contactless and PSTN modem.
(For instance, on EFT930BCC or EFT930GCC with modem, it works, because the modem is on the cradle,
and the distance between the modem and the contactless field is sufficient).

14.2.2. Add-on Contactless

The add-on contactless doesn’t exist anymore.
All components provided previously in this package are now by default since Telium SDK 8.1. It concerns

TPass library and component;

Entry point component;

GTL library;

Contactless sample.

14.2.3. Card supported

The list of cards supported by this SDK is given in the paragraph Erreur ! Source du renvoi introuvable.:
Erreur ! Source du renvoi introuvable. .

Recommendation:
Even if a card is managed since an old SDK or Add-On Contactless, usage of a recent SDK is strongly
recommend because bugs could have been fixed.

14.3. Family name

The family name, defined in the descriptor used to sign the binary, must follow the pattern
“<NAME><VV><AA>” where:

NAME is the radical of application (maximum 6 ASCII characters);

VV is the version (2 number);

AA is the amendment (2 number)

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

14.4. Pinpad system

To avoid problems when a non mock-up pinpad is linked to a mock-up terminal, the terminal mock-up
catalogues don’t include pinpad systems. So, you have to load the pinpad system (located in the
directory “Component\OS”) according to the pinpad you are using.

14.5. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

14.6. Reserved numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.
Tag numbers used by applications must be taken in the range 9FA000-9FAFFF.

14.7. EFT930 embedding 8MB of flash

It is possible to use this SDK on EFT930 which has only 8 MB of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

For SDK 8.0.x, SDK 8.1 and SDK 8.1.1:

It is forbidden to load a catalogue designed for 8MB terminals on a terminal loaded with a generic
catalogue (that is to say non-8 MB). You must contact the Ingenico support for the rules of this
migration.

15. Issues solved in this release by component

See table in chapter 11 “Version of components” for the list of

versions of components provided in this Telium SDK.

15.1. Telium System

Main points delivered in this release are listed below.

15.1.1. System Thunder

Internal
SUPTEL Description
tracker
Management of iWL280 :

Touch screen improvement;

Swipe improvement.
For ISC250 and ISC350 on SDK8.1.1 , issue about USBDEV_FIOCTL_SET_VID
10699 SUPTEL-3014
fixed

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

15.2. Telium Manager

15.2.1. Evolutions
Following points are delivered in this release.

Internal
SUPTEL Description
tracker
Improvement of the delay between amount entry and message requesting
6934 SUPTEL-3024
card when using "card entry" customization.
Standby Delay was 1 minute maximum on iWL when contactless was
10527 SUPTEL-2837
activated
MAC address returned was wrong on iWL 250 Bluetooth associated with an
10560
Ethernet base
For development only: it is possible to use the DLL SDI with this Manager.
10586 DLL SDI allows the intelligent update of an iST150 via the host terminal.
This feature will be officially released in the SDK 8.2
9976 SUPTEL-3083 IsRadio3G() function added to know if a terminal is 3G compatible
10639 DLL CB2A: new rule for IPDU LONGUE
10635 SUPTEL-2977 G_List_Entry() now uses Telium Manager fonts (_SMALL_,_MEDIUM_,...)
9440 SUPTEL-2253 Fix for the MMI allowing to know if IP address has been obtained

15.3. Security

15.3.1. DLL Security

No evolution.

15.3.2. Security Extend library

No evolution.

15.3.3. DLL E2EE

15.3.3.1. Overview
Version 4.0.1 of DLL E2EE, which is included in this SDK, is certified PCI-V3.
Binary is included in the Telium Manager catalogue.

It is provided for the following terminals:

iWL220, iWL250, iWL280,

iSC250, iSC350,

iMP350,

iPP320, iPP350,

iCT220, iCT250,

SPM.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

15.3.3.2. Evolutions
Internal
SUPTEL Description
tracker
When function E2EE_Format_And_Cipher() was called, if the CVV was not
10802 SUPTEL-3099
provided with the PAN, there was a terminal reset.

15.3.4. Schemes
Last schemes certified are included in this SDK.

15.4. Communication

15.4.1. Link Layer

Following points are delivered in this release.

Internal
SUPTEL Description
tracker
LL_Network_GetStatus() returned a wrong value when an Ethernet cable
10512 SUPTEL-2900
was connected
10135 SUPTEL-2639 Synchro frames were sent after a timeout on an SSL session
Mistake fixed in the sample "Ethernet configuration with SSL" of the CHM
10641 SUPTEL-3008
help file
New driver taken into account for iSC250 when le tag
10357 SUPTEL-2721
LL_PHYSICAL_V_CONVERTER_USB_RS232 is used

15.4.2. Pack IP
No evolution.

15.4.3. FTP
No evolution.

15.4.4. SNMP
No evolution.

15.4.5. SSL
No evolution.

15.5. Display

15.5.1. DLL Image

No evolution.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

15.5.2. Fonts
No evolution.

15.5.3. CGUI / CGUI tools

No evolution.

15.5.4. Plug-in Signature Capture

No evolution.

15.5.5. Plug-in Multimedia

No evolution.

15.6. Contactless

15.6.1. DLL TPASS

Internal
SUPTEL Description
tracker
8338 / Fix for compatibility between DLL Tpass and previous version of Telium
9749 Manager

15.7. Applications

15.7.1. Incendo Online browser

Technical documentation and the Incendo SDK are provided with Ingedev (from version 7.8.0).

15.7.1.1. Memory
Before deploying this solution, please check the memory usage of your terminals.

15.7.1.2. Migration to this version

15.7.1.2.1. Restriction
If you migrate a previous version to this one, the Incendo parameters will be lost.

15.7.1.2.2. Migration from a version before 3.0.4

Incendo Online smart browser was previously delivered as an independent package (up to version
3.0.3). It was designed to be signed with region security keys.
The version in this Telium SDK is signed with manufacturer key. So the application type is different
between these two versions. If you have already deployed the browser, to migrate to the version
included in a Telium SDK, you must manage the change of application type. For further details, please
contact the Incendo support.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

15.7.1.3. Compatibility

15.7.1.3.1. Terminals managed

Minimal hardware prerequisites are:

Terminal is Ethernet or GPRS;

Terminals is Ingetrust ready;

Minimum of 16 MB of Flash is mandatory;

16 MB of RAM are recommended but not mandatory. 8 MB is possible if terminal is Incendo
Online only (no other applications).

Incendo Online is compatible with the following terminals:

EFT930 Color (Booster 2 type),

iCT220, iCT250,

iWL220, iWL250
You must not use it on other terminals.

Support of iSC250 and iSC350 will be available in a future release.

15.7.1.3.2. EMV packages compatibility

Incendo smart Browser is compatible with the following EMV packages:

Version 18

Version 19

15.7.1.4. Evolutions
No evolution.

15.7.2. Image Loader

At the end of the Telium SDK setup you can choose to install Image Loader on your PC. Documentation
is available in this installed package.

15.7.2.1. Evolutions
No evolution.

15.8. AVL
AVL stands for Added Value Libraries.
No evolution.

15.9. Full configuration for local download for iPP320 in pinpad

emulation mode
A binary concatenates the Telium system (including contactless driver) and the Telium manager for an
iPP3 used in pinpad emulation for local download mode. It is delivered in the directory:
Component\iPP3_EmulationPinpad\Package
Please see description in the CHM help file of the Telium SDK (SDK General Documentation > HOW TO
DEVELOP user guide > How to use iPP3xx as a smart card reader).

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

15.9.1. DLL PPLoad evolution

The DLL PPLoad is present in the host terminal and allows the loading of the full configuration to the
iPP3.

15.10. SDK features

No evolution.

16. Change of API

16.1. Fct_Cless()
There is a change of API between this SDK and the previous one.
Due to parameters not used in the function:

Before SDK 8.1.2 prototype was typedef int (*Fct_Cless)(int x,int y);

Since SDK 8.1.2 prototype is typedef int (*Fct_Cless)(void);
This API exists since SDK 8.0.

17. Add-ons to Telium SDK

The following table presents the versions of recommended add-ons to use with this SDK.

Recommended
Add on Comment
version to use with this SDK
Easy Path To EMV 20.1
Components previously in this
Add On Contactless (New
Removed add-on are in the Telium SDK
architecture) since 8.1
Easy Path To Contactless 3. 07

Add On PCL for iPA280 1.17

Add On PCL for iWP 1.15

Add On PCL for iMP3xx 1.01

Add On Morpho 1.06

Add On Telicapt 2.15

Add On UCM 2.06.01

Add On SPDH 1.01

Add On APACS 40 Generic 1.08

Add On ISO8583 Generic 3.02

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK8.1.1 Technical Information Bulletin

18. Standard development platforms

Terminals based on Thunder 3 (iSC250, iSC350 and iWL280) are not supported by this SDK.
The Telium SDK 8.1.1 will support them.

This SDK release is compatible with the following products.

18.1. List of terminals

18.1.1. Wireless
Telium 2:

iWL220B, iWL220G,

iWL250B, iWL250G , iWL250 3G,

iWL250 2SCR, 2SCR stands for 2 Smart Card Reader,

IWL280 is not supported by this SDK.

Telium 1:

EFT930 color,

EFT930 black and white.

18.1.2. Countertop terminals

Telium 2:

iCT220, iCT250,

E532 (for development only)

Telium 1:

EFT SMART Plus,

EFT SMART,

EFT30

18.1.3. Signature capture terminals (Retail pinpads)

They are not supported by this release.

18.1.4. Pinpads
Telium 2:

iPP320, iPP350,

iPP320 used as a smart card reader (Pinpad emulation mode).

Telium 1:

ML30, ML30 color, ML30 color contactless.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

‘Booster only’ pinpads:

iPP280, iPP250, iPP220, PPC30, PPR30, P30, P30 Contactless, PP30, PP30S.

18.1.5. Unattended
See UCM add-on package for the exhaustive list.

18.1.6. Satellite terminals

Telium 2:

iST150.

Telium 1:

TeliumPass Plus.

18.1.7. Mobile payment

Telium 2:

iMP3xx (only hardware V4 are supported since SDK 8.0.1),

SPM (iPA280).

18.1.8. French health care

TWINs.

18.2. Terminals certified PCI V3

The following terminals are certified for PCI V3:

iWL220 Since SDK 8.0.1

iWL250 Since SDK 8.0.1
iWL280 Since SDK 8.0.1
iSC250 Since SDK 8.0.1
iPP320 New in SDK 8.1
iPP350 New in SDK 8.1

18.3. Public Key Infrastructure

This release supports PKI V3.

19. What’s new?

Issues solved are detailed in paragraph 4.
Here are main evolutions coming with this Telium SDK release compared to the release 8.1.

19.1. New terminals

Following terminals are now supported in the SDK:
 iWL250 3G (for development only),

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

 iWL250 2SCR, 2SCR stands for 2 Smart Card Reader,

 iPP3xx are certified PCI PTS V3.

19.2. New features

 New version of DLL E2EE PCI V3 (list of terminal supported is in the paragraph 26.3.3: DLL E2EE),
 Local download mode is now available for iPP3 in pinpad emulation,
 Maximum number of AID managed by one application is increased to 100.

19.3. General points

 Integration of driver Contactless in the Telium SDK (Add-on contactless will be no more
provided, see below for details),
 Many improvements of documentation.

20. Highlighted points

20.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response;

Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC is not limited to banking cards. Direct communication to
other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection)

20.2. Best practices for Contactless

20.2.1. Field on/off

The contactless field is to be activated only when a contactless card is waited by the terminal. It must be
stopped when the management of the contactless card is finished.
If the contactless field is opened all the time:

On wireless terminals, product battery autonomy is reduced a lot;

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

The contactless module and antenna are highly stressed and reliability could decrease quickly
with time;
Applications have to manage the opening and the closing of the field according their business logic.

20.2.2. Implicit selection

Following terminals having the contactless feature inside are concerned: iWL2xx, iCT250, iSC2xx, iSC3xx,
EFT930 GCC, EFT930 BCC, iPP3XX, iPA280 (SPM), ML30C and P30C.

Implicit selection is not recommended and must be managed with caution.

Due to physical reason, implicit selection can lead to unexpected issues, for example, at the beginning
of the swipe, the card would possibly enter the antenna field and contactless chip would be handled
instead of magnetic track.

20.2.3. Use of PSTN modem with contactless activated

The electro-magnetic field created when the contactless is activated, on an integrated terminal,
prevents the usage of the PSTN modem with contactless activated.
This is not a software issue, and no software solution exists. The contactless field shall not be activated
at the same time as the modem.

Currently, the issue exists only on the iCT250, which is the only Ingenico integrated terminal with
contactless and PSTN modem.
(For instance, on EFT930BCC or EFT930GCC with modem, it works, because the modem is on the cradle,
and the distance between the modem and the contactless field is sufficient).

20.3. Add-on Contactless

The add-on contactless doesn’t exist anymore.
All components provided previously in this package are now by default in the Telium SDK. It concerns

TPass library and component;

Entry point component;

GTL library;

Contactless sample.

20.4. Pinpad system

To avoid problems when a non mock-up pinpad is linked to a mock-up terminal, the terminal mock-up
catalogues don’t include pinpad systems. So, you have to load the pinpad system (located in the
directory “Component\OS”) according to the pinpad you are using.

20.5. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

20.6. Reserved numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.
Tag numbers used by applications must be taken in the range 9FA000-9FAFFF.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

20.7. EFT930 embedding 8Mo of flash

It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

21. Issues solved in this release by component

See table in chapter 11 “Version of components” for the list of

versions of components provided in this Telium SDK.

21.1. Telium System

Following main points are delivered in this release.

21.1.1. System Thunder

Internal
SUPTEL Description
tracker
10072 SUPTEL-2128 On IWL2XX, SWIPE detection improved when GPRS emitter operates.
On IWL2XX, SWIPE detection improved when noisy device operates
10091
(PRINTER and GPRS).
9696 SUPTEL-2362 It is now possible to display 8 Cyrillic characters.
10097 Change of coupler frequency from 3,57MhZ to 4,76MHz is now possible
10104 SUPTEL-2646 Update help concerning __inet_addr
10154 SUPTEL-2615 Adding synchronous shutdown function
10157 SUPTEL-2690 COM_SEND_EMPTY empty event was not fired on COM0
10158 SUPTEL-2631 Disable SET_DTR and CLEAR_DTR on Bluetooth remote modem.
10233 SUPTEL-2739 Added "#define ftruncate eft_ftruncate" in "cpp_e.h" file
Removed FS_dskdelete function (it was not possible to use it by
10236 SUPTEL-2726
application)
Improved error codes set during LLT connexion when trying to load 2
7996 TFU 5088
applications with the same application type
USB_PRESENT is now right returned by status() function for MOUSE and
8288
KEYBUSB.
Add management of CAM and SWIPE Leds for iPP3 in pinpad emulation
8567
(The module 8201030205 must be loaded on the host terminal (iCT...))
TFU 5597
8669 Const added before const string parameters of the FFMS functions
SUPTEL-1884
9373 SUPTEL-2154 Increase SWAP size from 8 to 16 MB (if enough memory is available)
9494 Interface with link layer
Now maximum of threads managed is 150 (80 threads for an application)
9666
Now maximum of mailboxes managed is 150.
9748 Hilo 3G is now managed
9753 Twin 33 connected only over USB now works with LLT 4.4.4

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

9792 Improved connexion of iWL to TMS

9868 Exit 134 (TOO_MANY_FILE) fixed for CAD30 UPT with SDK 7.6.1
9913 New USB identification for E532 (LLT>=4.4 must be used)
9960 Thunder system version added in APPRESET.DIA
It is now possible to display a picture in LLT mode started from Telium
9985
Manager
It fixes iWL250B resets when SWP:ERC[FFFFFFF7]
10338 SUPTEL-2775
It improves swipe detection
It is now possible to call fioctl(PRINTER_PRINT_ULIGNE,…) while there is
10339 SUPTEL-2815
no paper

21.2. Telium Manager

21.2.1. Start-up address

To simplify the diagnostic for forbidden memory access, the start-up address of the Telium Manager is
now 0x1000 instead of 0x00.

21.2.2. Evolutions
Following points are delivered in this release.

The GPRS configuration for TMS is updated as soon as an application

3241
modify GPRS parameters
The manager will call SELECT_AID_EXTENDED even when there is only one
10155
AID in the Candidate List.
New APIs are provided :
DisplayFooter ( int state ) // state _ON_ ou _OFF_
10168 SUPTEL-2530
DisplayHeader ( int state ) // state _ON_ ou _OFF_
DisplayLeds ( int state ) // state _ON_ ou _OFF_
10223 SUPTEL-2520 Empty lines in MANAGER.PAR file are now allowed
10245 Conflict between PrintBMPxy() and pprintf8859() solved
10249 Ignored non significant 0 when keying amount in GetAmount() function
10298 Improvement for PushCGUIContext() and PopCGUIContext()
New APIs are provided :
10334 StopBacklightManagment() to disable BACKLIGHT management
RestartBacklightManagment() to restore old value
10337 Possibility added to force refresh with PushCGUIContext
8651 Display improvement for QVGA screen in portrait mode
Improvements for
9454
G_List_Entry,G_Numerical_Entry,G_Alphanumerical_Entry
Implementation of the mechanism allowing to update the link APPLI<----
9760 SUPTEL-2430
>"mode".
9814 SUPTEL-2397 Improvement of function _pprintf8859XY()
9822 SUPTEL-2449 Use Manager current language in the configuration menus hardware
9853 Fonts _PoliceX_Y_ are now usable by all functions
To simplify the diagnostic for forbidden memory access, the start-up
9857
address of the Telium Manager is now 0x1000 instead of 0x00
9892 Maximum number of AID managed by one application is increased to 100.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Improvement fot SUPTEL-2118 (Possibility to customize footer on non-color

9144 SUPTEL-2118
device with SetFooterBmp())
Improvement fot SUPTEL-2166 (Manager display message "WELCOME" on
9381 SUPTEL-2166
PP30S when it waits for card after amount entry)
Improvement for SUPTEL-2253 (USQ_EthernetConfig() returns the last
9440 SUPTEL-2253
"REAL" address negotiated)

21.3. Security

21.3.1. DLL Security

No evolution.

21.3.2. Security Extend library

No evolution.

21.3.3. DLL E2EE

Version 4.0.1 is certified PCI-V3.
Binary is included in the Telium Manager catalogue.

It is provided for the following terminals:

iWL220, iWL250, iWL280,

iSC250, iSC350,

iMP350,

iPP320, iPP350,

iCT220, iCT250
SPM is not supported by the DLL E2EE PCI-V3.

21.3.4. Schemes
Last schemes certified are included in this SDK.

21.4. Communication

21.4.1. Link Layer

Following points are delivered in this release.

8055 SUPTEL-1593 Tailgate cash register protocol managed

9724 Several radio types managed in the same terminal
9751 Management by Link Layer of iWL 3G
10162 Management by Link Layer of Bluetooth terminals without base

21.4.2. Pack IP
Following points are delivered in this release.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

9636 Updated documentation for PCI V3

21.4.3. FTP
No evolution.

21.4.4. SNMP
No evolution.

21.4.5. SSL
Following points are delivered in this release.

9847 SUPTEL-2114 Add SSL_GetAlertError() function to get SSL alert error.

Add compatibility with certificate without carriage return at the end of the
9962 SUPTEL-2513
file.
Add compatibility with X509 certificate using UTF8Strings elements in
10237 SUPTEL-2684
distinguish name.

21.5. Display

21.5.1. DLL Image

No evolution.

21.5.2. Fonts
No evolution.

21.5.3. CGUI / CGUI tools

No evolution.

21.5.4. Plug-in Signature Capture

No evolution.

21.5.5. Plug-in Multimedia

No evolution.

21.6. Applications

21.6.1. Incendo Online browser

Technical documentation and the Incendo SDK are provided with Ingedev (from version 7.8.0).

Following point is delivered in this release.

10377 OE-1576 Support of several gateways IP addresses and port numbers

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Warning: Migration from a previous version to this one result in parameters lost.

21.6.1.1. Memory
Before deploying this solution, please check the memory usage of your terminals.

21.6.1.2. Migration to this version

Incendo Online smart browser was previously delivered as an independent package. It was designed to
be signed with region security keys.
The version in this Telium SDK is signed with manufacturer key. So the application type is different
between these two versions. If you have already deployed the browser, to migrate to the version
included in this SDK, you must manage the change of application type. For further details, please
contact the Incendo support.

21.6.1.3. Compatibility

21.6.1.3.1. Terminals managed

Minimal hardware prerequisites are:

Terminal is Ethernet or GPRS;

Terminals is Ingetrust ready;

Minimum of 16 MB of Flash is mandatory;

16 MB of RAM are recommended but not mandatory. 8 MB is possible if terminal is Incendo
Online only (no other applications).

Incendo Online is compatible with the following terminals:

EFT930 Color (Booster 2 type),

iCT220, iCT250,

iWL220, iWL250
You must not use it on other terminals.

Support of iSC250 and iSC350 will be available in the future.

21.6.1.3.2. EMV packages compatibility

Incendo smart Browser is compatible with the following EMV packages:

Version 18

Version 19

21.6.1.4. Evolutions
No evolution.

21.6.2. Image Loader

No evolution.

21.7. AVL
No evolution.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

21.8. Full configuration for local download for iPP320 in pinpad

emulation mode
This is a new component.
This binary concatenates the Telium system (including contactless driver) and the Telium manager for
an iPP3 used in pinpad emulation for local download mode. Please see description in the CHM help file
of the Telium SDK (SDK General Documentation > HOW TO DEVELOP user guide > How to use iPP320 as
a smart card reader).

21.9. SDK features

Following points are delivered in this release.

Update of the "How To use iPP3 as a Smart Card Reader" documents

22. Add-ons to Telium SDK

The following table presents the versions of recommended add-ons to use with this SDK.

Recommended
Add on Comment
version to use with this SDK
Easy Path To EMV 20.1 New version
Components previously in this
Add On Contactless (New
Removed add-on are now in the Telium
architecture) SDK
New version
Easy Path To Contactless 3. 07

Add On PCL for iPA280 1.15

Add On PCL for iWP 1.15

Add On PCL for iMP3xx 1.00

Add On Morpho 1.06

Add On Telicapt 2.14

Add On UCM 2.06.01 New version

Add On SPDH 1.01

Add On APACS 40 Generic 1.08

Add On ISO8583 Generic 3.02

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK8.1 Technical Information Bulletin

23. Standard development platforms

Terminals based on Thunder 3 (iSC250, iSC350 and iWL280) are not supported by this SDK.
The Telium SDK 8.1.1 will support them.

This SDK release is compatible with the following products.

23.1. List of terminals

23.1.1. Wireless
Telium 2:

iWL220B, iWL220G,

iWL250B, iWL250G , iWL250 3G,

iWL250 2SCR, 2SCR stands for 2 Smart Card Reader,

IWL280 is not supported by this SDK.

Telium 1:

EFT930 color,

EFT930 black and white.

23.1.2. Countertop terminals

Telium 2:

iCT220, iCT250,

E532 (for development only)

Telium 1:

EFT SMART Plus,

EFT SMART,

EFT30

23.1.3. Signature capture terminals (Retail pinpads)

They are not supported by this release.

23.1.4. Pinpads
Telium 2:

iPP320, iPP350,

iPP320 used as a smart card reader (Pinpad emulation mode).

Telium 1:

ML30, ML30 color, ML30 color contactless.
‘Booster only’ pinpads:

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

iPP280, iPP250, iPP220, PPC30, PPR30, P30, P30 Contactless, PP30, PP30S.

23.1.5. Unattended
See UCM add-on package for the exhaustive list.

23.1.6. Satellite terminals

Telium 2:

iST150.

Telium 1:

TeliumPass Plus.

23.1.7. Mobile payment

Telium 2:

iMP3xx (only hardware V4 are supported since SDK 8.0.1),

SPM (iPA280).

23.1.8. French health care

TWINs.

23.2. Terminals certified PCI V3

The following terminals are certified for PCI V3:

iWL220 Since SDK 8.0.1

iWL250 Since SDK 8.0.1
iWL280 Since SDK 8.0.1
iSC250 Since SDK 8.0.1
iPP320 New in SDK 8.1
iPP350 New in SDK 8.1

23.3. Public Key Infrastructure

This release supports PKI V3.

24. What’s new?

Issues solved are detailed in paragraph 4.
Here are main evolutions coming with this Telium SDK release compared to the release 8.1.

24.1. New terminals

Following terminals are now supported in the SDK:
 iWL250 3G (for development only),
 iWL250 2SCR, 2SCR stands for 2 Smart Card Reader,

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

 iPP3xx are certified PCI PTS V3.

24.2. New features

 New version of DLL E2EE PCI V3 (list of terminal supported is in the paragraph 26.3.3: DLL E2EE),
 Local download mode is now available for iPP3 in pinpad emulation,
 Maximum number of AID managed by one application is increased to 100.

24.3. General points

 Integration of driver Contactless in the Telium SDK (Add-on contactless will be no more
provided, see below for details),
 Many improvements of documentation.

25. Highlighted points

25.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response;

Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC is not limited to banking cards. Direct communication to
other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection)

25.2. Best practices for Contactless

25.2.1. Field on/off

The contactless field is to be activated only when a contactless card is waited by the terminal. It must be
stopped when the management of the contactless card is finished.
If the contactless field is opened all the time:

On wireless terminals, product battery autonomy is reduced a lot;

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

The contactless module and antenna are highly stressed and reliability could decrease quickly
with time;
Applications have to manage the opening and the closing of the field according their business logic.

25.2.2. Implicit selection

Following terminals having the contactless feature inside are concerned: iWL2xx, iCT250, iSC2xx, iSC3xx,
EFT930 GCC, EFT930 BCC, iPP3XX, iPA280 (SPM), ML30C and P30C.

Implicit selection is not recommended and must be managed with caution.

Due to physical reason, implicit selection can lead to unexpected issues, for example, at the beginning
of the swipe, the card would possibly enter the antenna field and contactless chip would be handled
instead of magnetic track.

25.2.3. Use of PSTN modem with contactless activated

The electro-magnetic field created when the contactless is activated, on an integrated terminal,
prevents the usage of the PSTN modem with contactless activated.
This is not a software issue, and no software solution exists. The contactless field shall not be activated
at the same time as the modem.

Currently, the issue exists only on the iCT250, which is the only Ingenico integrated terminal with
contactless and PSTN modem.
(For instance, on EFT930BCC or EFT930GCC with modem, it works, because the modem is on the cradle,
and the distance between the modem and the contactless field is sufficient).

25.3. Add-on Contactless

The add-on contactless doesn’t exist anymore.
All components provided previously in this package are now by default in the Telium SDK. It concerns

TPass library and component;

Entry point component;

GTL library;

Contactless sample.

25.4. Pinpad system

To avoid problems when a non mock-up pinpad is linked to a mock-up terminal, the terminal mock-up
catalogues don’t include pinpad systems. So, you have to load the pinpad system (located in the
directory “Component\OS”) according to the pinpad you are using.

25.5. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

25.6. Reserved numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.
Tag numbers used by applications must be taken in the range 9FA000-9FAFFF.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

25.7. EFT930 embedding 8Mo of flash

It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

26. Issues solved in this release by component

See table in chapter 11 “Version of components” for the list of

versions of components provided in this Telium SDK.

26.1. Telium System

Following main points are delivered in this release.

26.1.1. System Thunder

Internal
SUPTEL Description
tracker
10072 SUPTEL-2128 On IWL2XX, SWIPE detection improved when GPRS emitter operates.
On IWL2XX, SWIPE detection improved when noisy device operates
10091
(PRINTER and GPRS).
9696 SUPTEL-2362 It is now possible to display 8 Cyrillic characters.
10097 Change of coupler frequency from 3,57MhZ to 4,76MHz is now possible
10104 SUPTEL-2646 Update help concerning __inet_addr
10154 SUPTEL-2615 Adding synchronous shutdown function
10157 SUPTEL-2690 COM_SEND_EMPTY empty event was not fired on COM0
10158 SUPTEL-2631 Disable SET_DTR and CLEAR_DTR on Bluetooth remote modem.
10233 SUPTEL-2739 Added "#define ftruncate eft_ftruncate" in "cpp_e.h" file
Removed FS_dskdelete function (it was not possible to use it by
10236 SUPTEL-2726
application)
Improved error codes set during LLT connexion when trying to load 2
7996 TFU 5088
applications with the same application type
USB_PRESENT is now right returned by status() function for MOUSE and
8288
KEYBUSB.
Add management of CAM and SWIPE Leds for iPP3 in pinpad emulation
8567
(The module 8201030205 must be loaded on the host terminal (iCT...))
TFU 5597
8669 Const added before const string parameters of the FFMS functions
SUPTEL-1884
9373 SUPTEL-2154 Increase SWAP size from 8 to 16 MB (if enough memory is available)
9494 Interface with link layer
Now maximum of threads managed is 150 (80 threads for an application)
9666
Now maximum of mailboxes managed is 150.
9748 Hilo 3G is now managed
9753 Twin 33 connected only over USB now works with LLT 4.4.4

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

9792 Improved connexion of iWL to TMS

9868 Exit 134 (TOO_MANY_FILE) fixed for CAD30 UPT with SDK 7.6.1
9913 New USB identification for E532 (LLT>=4.4 must be used)
9960 Thunder system version added in APPRESET.DIA
It is now possible to display a picture in LLT mode started from Telium
9985
Manager
It fixes iWL250B resets when SWP:ERC[FFFFFFF7]
10338 SUPTEL-2775
It improves swipe detection
It is now possible to call fioctl(PRINTER_PRINT_ULIGNE,…) while there is
10339 SUPTEL-2815
no paper

26.2. Telium Manager

26.2.1. Start-up address

To simplify the diagnostic for forbidden memory access, the start-up address of the Telium Manager is
now 0x1000 instead of 0x00.

26.2.2. Evolutions
Following points are delivered in this release.

The GPRS configuration for TMS is updated as soon as an application

3241
modify GPRS parameters
The manager will call SELECT_AID_EXTENDED even when there is only one
10155
AID in the Candidate List.
New APIs are provided :
DisplayFooter ( int state ) // state _ON_ ou _OFF_
10168 SUPTEL-2530
DisplayHeader ( int state ) // state _ON_ ou _OFF_
DisplayLeds ( int state ) // state _ON_ ou _OFF_
10223 SUPTEL-2520 Empty lines in MANAGER.PAR file are now allowed
10245 Conflict between PrintBMPxy() and pprintf8859() solved
10249 Ignored non significant 0 when keying amount in GetAmount() function
10298 Improvement for PushCGUIContext() and PopCGUIContext()
New APIs are provided :
10334 StopBacklightManagment() to disable BACKLIGHT management
RestartBacklightManagment() to restore old value
10337 Possibility added to force refresh with PushCGUIContext
8651 Display improvement for QVGA screen in portrait mode
Improvements for
9454
G_List_Entry,G_Numerical_Entry,G_Alphanumerical_Entry
Implementation of the mechanism allowing to update the link APPLI<----
9760 SUPTEL-2430
>"mode".
9814 SUPTEL-2397 Improvement of function _pprintf8859XY()
9822 SUPTEL-2449 Use Manager current language in the configuration menus hardware
9853 Fonts _PoliceX_Y_ are now usable by all functions
To simplify the diagnostic for forbidden memory access, the start-up
9857
address of the Telium Manager is now 0x1000 instead of 0x00
9892 Maximum number of AID managed by one application is increased to 100.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Improvement fot SUPTEL-2118 (Possibility to customize footer on non-color

9144 SUPTEL-2118
device with SetFooterBmp())
Improvement fot SUPTEL-2166 (Manager display message "WELCOME" on
9381 SUPTEL-2166
PP30S when it waits for card after amount entry)
Improvement for SUPTEL-2253 (USQ_EthernetConfig() returns the last
9440 SUPTEL-2253
"REAL" address negotiated)

26.3. Security

26.3.1. DLL Security

No evolution.

26.3.2.Security Extend library

No evolution.

26.3.3.DLL E2EE
Version 4.0.1 is certified PCI-V3.
Binary is included in the Telium Manager catalogue.

It is provided for the following terminals:

iWL220, iWL250, iWL280,

iSC250, iSC350,

iMP350,

iPP320, iPP350,

iCT220, iCT250
SPM is not supported by the DLL E2EE PCI-V3.

26.3.4. Schemes
Last schemes certified are included in this SDK.

26.4. Communication

26.4.1. Link Layer

Following points are delivered in this release.

8055 SUPTEL-1593 Tailgate cash register protocol managed

9724 Several radio types managed in the same terminal
9751 Management by Link Layer of iWL 3G
10162 Management by Link Layer of Bluetooth terminals without base

26.4.2. Pack IP
Following points are delivered in this release.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

9636 Updated documentation for PCI V3

26.4.3. FTP
No evolution.

26.4.4. SNMP
No evolution.

26.4.5. SSL
Following points are delivered in this release.

9847 SUPTEL-2114 Add SSL_GetAlertError() function to get SSL alert error.

Add compatibility with certificate without carriage return at the end of the
9962 SUPTEL-2513
file.
Add compatibility with X509 certificate using UTF8Strings elements in
10237 SUPTEL-2684
distinguish name.

26.5. Display

26.5.1. DLL Image

No evolution.

26.5.2. Fonts
No evolution.

26.5.3.CGUI / CGUI tools

No evolution.

26.5.4. Plug-in Signature Capture

No evolution.

26.5.5.Plug-in Multimedia
No evolution.

26.6. Applications

26.6.1. Incendo Online browser

Technical documentation and the Incendo SDK are provided with Ingedev (from version 7.8.0).

Following point is delivered in this release.

10377 OE-1576 Support of several gateways IP addresses and port numbers

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Warning: Migration from a previous version to this one result in parameters lost.

26.6.1.1. Memory
Before deploying this solution, please check the memory usage of your terminals.

26.6.1.2. Migration to this version

Incendo Online smart browser was previously delivered as an independent package. It was designed to
be signed with region security keys.
The version in this Telium SDK is signed with manufacturer key. So the application type is different
between these two versions. If you have already deployed the browser, to migrate to the version
included in this SDK, you must manage the change of application type. For further details, please
contact the Incendo support.

26.6.1.3. Compatibility

26.6.1.3.1. Terminals managed

Minimal hardware prerequisites are:

Terminal is Ethernet or GPRS;

Terminals is Ingetrust ready;

Minimum of 16 MB of Flash is mandatory;

16 MB of RAM are recommended but not mandatory. 8 MB is possible if terminal is Incendo
Online only (no other applications).

Incendo Online is compatible with the following terminals:

EFT930 Color (Booster 2 type),

iCT220, iCT250,

iWL220, iWL250
You must not use it on other terminals.

Support of iSC250 and iSC350 will be available in the future.

26.6.1.3.2. EMV packages compatibility

Incendo smart Browser is compatible with the following EMV packages:

Version 18

Version 19

26.6.1.4. Evolutions
No evolution.

26.6.2. Image Loader

No evolution.

26.7. AVL
No evolution.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

26.8. Full configuration for local download for iPP320 in pinpad

emulation mode
This is a new component.
This binary concatenates the Telium system (including contactless driver) and the Telium manager for
an iPP3 used in pinpad emulation for local download mode. Please see description in the CHM help file
of the Telium SDK (SDK General Documentation > HOW TO DEVELOP user guide > How to use iPP320 as
a smart card reader).

26.9. SDK features

Following points are delivered in this release.

Update of the "How To use iPP3 as a Smart Card Reader" documents

27. Add-ons to Telium SDK

The following table presents the versions of recommended add-ons to use with this SDK.

Recommended
Add on Comment
version to use with this SDK
Easy Path To EMV 20.1 New version
Components previously in this
Add On Contactless (New
Removed add-on are now in the Telium
architecture) SDK
New version
Easy Path To Contactless 3. 07

Add On PCL for iPA280 1.15

Add On PCL for iWP 1.15

Add On PCL for iMP3xx 1.00

Add On Morpho 1.06

Add On Telicapt 2.14

Add On UCM 2.06.01 New version

Add On SPDH 1.01

Add On APACS 40 Generic 1.08

Add On ISO8583 Generic 3.02

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK8.0.2 Technical Information Bulletin

28. Standard development platforms

This SDK release is compatible with the following products.

28.1. Wireless
Telium2:

iWL220B, iWL220G,

iWL250B, iWL250G ,

iWL280.
Telium1:

EFT930 color,

EFT930 black and white.

28.2. Countertop terminals

Telium2:

iCT220, iCT250,

E532 (for development only)
Telium1:

EFT SMART Plus,

EFT SMART,

EFT30

28.3. Signature capture terminals

Telium2:

iSC250,

iSC350.

28.4. Pinpads
Telium 2:

iPP320, iPP350,

iPP320 used as a smart card reader (Pinpad emulation mode).
Telium 1:

ML30, ML30 color, ML30 color contactless.
‘Booster only’ pinpads:

iPP280, iPP250, iPP220, PPC30, PPR30, P30, P30 Contactless, PP30, PP30S.

28.5. Unattended
See UCM add-on package for the exhaustive list.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

28.6. Satellite terminals

Telium2:

iST150.
Telium1:

TeliumPass Plus.

28.7. Mobile payment

Telium2:

iMP3xx (only hardware V4 are supported from this release),

SPM (iPA280).

28.8. French health care

TWINs.

29. What’s new?

Issues solved are detailed in paragraph 4.
Here are main evolutions coming with this Telium SDK release compared to the release 8.0.1

29.1. TIB warning

TIB warning (low battery) declared with SDK 8.0.1 is now closed.

29.2. Terminals compatibility

In Telium SDK 8.0:

iWL 220 and iWL250 were delivered for production: applications developed with this SDK can
be deployed in the field;

Other products were delivered for development only: applications must not be deployed in
the field. These products were not full validated.
Telium SDK 8.0.1 and SDK8.0.2 are on the same base and provides software for production for the
terminals listed above.

29.3. Add-On compatibility

This package needs to be associated with add-on Cless 3.10.1, simultaneously delivered, to guarantee
cohabitation between Touch Screen and Contact Less.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

30. Highlighted points

30.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response;

Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC is not limited to banking cards. Direct communication to
other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection)

An evolution of the certification of the device proposes an alternative solution, which consists in using
the End-to-End Encryption DLL. The DLL allows two additional use-cases:

Communication in clear text form of card data to the external world (including PDA) for cards
whose BIN is within a range specified as a white list. The idea is to free the usage of private and
loyalty cards

Communication of encrypted cardholder data for banking cards.

The E2EE DLL usable for iPA280 is provided within SDK (versions 7.6 and above).

One must keep in mind that direct (i.e. using APDU commands) communication with the smart card
from the PDA remains unauthorized. The only E2EE method covered by the certification is the one that
has been certified and bespoke encryption solutions are not allowed.

30.2. Incendo Online smart browser

30.2.1. Presentation
Incendo Online is a hosted service offer that bridges customer touch points
with value-added service providers.

Incendo Online provides:

A flexible development framework based on internet-like technology for a quick and easy
service development, deployment, follow-up;

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Back-office tools for customer to monitor service success, administrate service portfolio, and to
promote services to customers;

A partnership program for partner support and go to market definition (tools, business
model…).

You can find complete presentation under the directory /Application/Incendo in the directory you
installed the Telium SDK.
All technical documentation is provided with Ingedev.

30.2.2. Components of the Incendo solutions

The Incendo Online smart browser, which is now part of the Telium SDK, is the software embedded in
the Telium terminals that interpret TML type files developed for services.
The Incendo SDK (simulator, gateway…) will be provided in the next version of Ingedev (v7.8.0).

30.2.3.Reservations on this version

If you want to deploy Incendo Online solution, please contact the Incendo support.
You can deploy this version but Ingenico can oblige you to migrate to a newer version.

30.2.4. Memory
Before deploying this solution, please check the memory usage of your terminals.

30.2.5.Migration to this version

Incendo Online smart browser was previously delivered as an independent package. It was designed to
be signed with region security keys.
The version in this Telium SDK is signed with manufacturer key. So the application type is different
between these two versions. If you have already deployed the browser, to migrate to the version
included in this SDK, you must manage the change of application type. For further details, please
contact the Incendo support.

30.2.6. Compatibility

30.2.6.1. Terminals managed

Minimal hardware prerequisites are:

Terminal is Ethernet or GPRS;

Terminals is Ingetrust ready;

Minimum of 16 MB of Flash is mandatory;

16 MB of RAM are recommended but not mandatory. 8 MB is possible if terminal is Incendo
Online only (no other applications).

This release of Incendo Online browser is compatible with the following terminals:

EFT930 Color (Booster 2 type),

iCT220, iCT250,

iWL220, iWL250
You must not use it on other terminals.

30.2.6.2. EMV packages compatibility

Incendo smart Browser is compatible with the following EMV packages:

Version 18

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Version 19

30.3. Best practices for Contactless

30.3.1. Field on/off

The contactless field is to be activated only when a contactless card is waited by the terminal. It must be
stopped when the management of the contactless card is finished.
If the contactless field is opened all the time:

On wireless terminals, product battery autonomy is reduced a lot;

The contactless module and antenna are highly stressed and reliability could decrease quickly
with time;
Applications have to manage the opening and the closing of the field according their business logic.

30.3.2.Implicit selection
Following terminals having the contactless feature inside are concerned: iWL2xx, iCT250, iSC2xx, iSC3xx,
EFT930 GCC, EFT930 BCC, iPP3XX, iPA280 (SPM), ML30C and P30C.

Implicit selection is not recommended and must be managed with caution.

Due to physical reason, implicit selection can lead to unexpected issues, for example, at the beginning
of the swipe, the card would possibly enter the antenna field and contactless chip would be handled
instead of magnetic track.

30.3.3.Use of PSTN modem with contactless activated

The electro-magnetic field created when the contactless is activated, on an integrated terminal,
prevents the usage of the PSTN modem with contactless activated.
This is not a software issue, and no software solution exists. The contactless field shall not be activated
at the same time as the modem.

Currently, the issue exists only on the iCT250, which is the only Ingenico integrated terminal with
contactless and PSTN modem.
(For instance, on EFT930BCC or EFT930GCC with modem, it works, because the modem is on the cradle,
and the distance between the modem and the contactless field is sufficient).

30.4. Pinpad system

To avoid problems when a non mock-up pinpad is linked to a mock-up terminal, the terminal mock-up
catalogues don’t include pinpad systems. So, you have to load the pinpad system (located in the
directory “Component\OS”) according to the pinpad you are using.

30.5. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

30.6. Reserved numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.
Tag numbers used by applications must be taken in the range 9FA000-9FAFFF.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

30.7. EFT930 embedding 8Mo of flash

It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

31. Issues solved in this release by component

31.1. Telium System (New version: 10.50)
Following main points are delivered in this release.

31.1.1. System Thunder

Following points are delivered in this release.

Internal
SUPTEL Description
tracker
10173 SDK 8.0.2 : No more SDK 8.0 warning for EFT930 (low battery)
10224 Fix for missing draw of single touch dot

31.2. Telium Manager (New version: 62.04)

Following points are delivered in this release.

9946 Improvement for swap between WGUI screen and standard screen
10039 SUPTEL-2555 iPP280 display : Use POLICE8x12 to display AID selection menu on IPP280
IWL280: PaintFilm( ) – BmpToScreen function works with BMP files of 1,8
10134 SUPTEL-2666
and 24 bits resolution
10148 SUPTEL-2253 USQ_EthernetConfig return the last “REAL” address negociated
10177 Documentation only
10182 Base Status : Bad information no more indicated

31.3. Security

31.3.1. DLL Security (Version: 03.20)

No evolution.

31.3.2. Security Extend library (Version: 02.04)

No evolution.

31.3.3. DLL E2EE (Version: 01.01)

No evolution.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

31.3.4. TLV Schemes (Version: 02.04)

No evolution.

31.3.5. Non-TLV Schemes (Version: 03.06)

No evolution.

31.4. Communication

31.4.1. Link Layer (Version: 03.20)

No evolution.

31.4.2. Pack IP (Version: 03.08)

No evolution.

31.4.3. FTP (Version: 01.20)

No evolution.

31.4.4. SNMP (Version: 01.01)

No evolution.

31.4.5. SSL (Version: 01.61)

No evolution.

31.5. Display

31.5.1. DLL Image (Version: 01.01)

No evolution.

31.5.2. Fonts (Version: 01.10)

No evolution.

31.5.3. CGUI (Version : 01.17) / CGUI tools (Version 01.10)

No evolution.

31.5.4. Plug-in Signature Capture (Version: 01.09)

Following point is delivered in this release.

10224 Fix for missing draw of single touch dot

31.5.5. Plug-in Multimedia (Version: 01.09)

No evolution.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

31.6. Applications

31.6.1. Incendo Online browser (Version 3.0.4)

No evolution.

31.6.2. Image Loader (01.06)

No evolution.

31.7. AVL (Version: 01.16)

Documentation only.

31.8. SDK features

Following points are delivered in this release.

10201 Cgui documentation re-established in SDK’s CHM

10220 Compilation warning messages deleted

32. Add-ons to Telium SDK

The following table presents the versions of recommended add-ons to use with this SDK.

Recommended
Add on
version to use with this SDK
Easy Path To EMV 20.1
Add On Cless (New
3.10.1(New version)
architecture)
Easy Path To CLESS 3.06

Add On PCL for iPA280 1.15

Add On PCL for iWP 1.15

PCL for iMP3xx 1.00 (New version)

Add On Morpho 1.06

Add On Telicapt 2.14

Add On UCM 2.06

Add On SPDH 1.01

Add On APACS 40 Generic 1.08

Add On ISO8583 Generic 3.02

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK8.0.1 Technical Information Bulletin

1. Standard development platforms

This SDK release is compatible with the following products.

1.1. Wireless
Telium2:

iWL220B, iWL220G,

iWL250B, iWL250G ,

iWL280.
Telium1:

EFT930 color,

EFT930 black and white.

1.2. Countertop terminals

Telium2:

iCT220, iCT250,

E532 (for development only)
Telium1:

EFT SMART Plus,

EFT SMART,

EFT30

1.3. Signature capture terminals

Telium2:

iSC250,

iSC350.

1.4. Pinpads
Telium 2:

iPP320, iPP350,

iPP320 used as a smart card reader (Pinpad emulation mode).
Telium 1:

ML30, ML30 color, ML30 color contactless.
‘Booster only’ pinpads:

iPP280, iPP250, iPP220, PPC30, PPR30, P30, P30 Contactless, PP30, PP30S.

1.5. Unattended
See UCM add-on package for the exhaustive list.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

1.6. Satellite terminals

Telium2:

iST150.
Telium1:

TeliumPass Plus.

1.7. Mobile payment

Telium2:

iMP3xx (only hardware V4 are supported from this release),

SPM (iPA280).

1.8. French health care

TWINs.

2. What’s new?
Issues solved are detailed in paragraph 4.
Here are main evolutions coming with this Telium SDK release compared to the release 8.0.

2.1. Terminals compatibility

In Telium SDK 8.0:

iWL 220 and iWL250 were delivered for production: applications developed with this SDK can
be deployed in the field;

Other products were delivered for development only: applications must not be deployed in
the field. These products were not full validated.
Telium SDK 8.0.1 is on the same base and provides software for production for the terminals listed
above.

2.2. Applications
 The application Incendo Online Browser is now provided in the Telium SDK. See dedicated
chapter.

2.3. General points

 “How To” documentations updated.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

3. Highlighted points
3.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response;

Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC is not limited to banking cards. Direct communication to
other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection)

An evolution of the certification of the device proposes an alternative solution, which consists in using
the End-to-End Encryption DLL. The DLL allows two additional use-cases:

Communication in clear text form of card data to the external world (including PDA) for cards
whose BIN is within a range specified as a white list. The idea is to free the usage of private and
loyalty cards

Communication of encrypted cardholder data for banking cards.

The E2EE DLL usable for iPA280 is provided within SDK (versions 7.6 and above).

One must keep in mind that direct (i.e. using APDU commands) communication with the smart card
from the PDA remains unauthorized. The only E2EE method covered by the certification is the one that
has been certified and bespoke encryption solutions are not allowed.

3.2. Incendo Online smart browser

3.2.1. Presentation
Incendo Online is a hosted service offer that bridges customer touch points
with value-added service providers.

Incendo Online provides:

A flexible development framework based on internet-like technology for a quick and easy
service development, deployment, follow-up;

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Back-office tools for customer to monitor service success, administrate service portfolio, and to
promote services to customers;

A partnership program for partner support and go to market definition (tools, business
model…).

You can find complete presentation under the directory /Application/Incendo in the directory you
installed the Telium SDK.
All technical documentation is provided with Ingedev.

3.2.2. Components of the Incendo solutions

The Incendo Online smart browser, which is now part of the Telium SDK, is the software embedded in
the Telium terminals that interpret TML type files developed for services.
The Incendo SDK (simulator, gateway…) will be provided in the next version of Ingedev (v7.8.0).

3.2.3. Reservations on this version

If you want to deploy Incendo Online solution, please contact the Incendo support.
You can deploy this version but Ingenico can oblige you to migrate to a newer version.

3.2.4. Memory
Before deploying this solution, please check the memory usage of your terminals.

3.2.5. Migration to this version

Incendo Online smart browser was previously delivered as an independent package. It was designed to
be signed with region security keys.
The version in this Telium SDK is signed with manufacturer key. So the application type is different
between these two versions. If you have already deployed the browser, to migrate to the version
included in this SDK, you must manage the change of application type. For further details, please
contact the Incendo support.

3.2.6. Compatibility

3.2.6.1. Terminals managed

Minimal hardware prerequisites are:

Terminal is Ethernet or GPRS;

Terminals is Ingetrust ready;

Minimum of 16 MB of Flash is mandatory;

16 MB of RAM are recommended but not mandatory. 8 MB is possible if terminal is Incendo
Online only (no other applications).

Incendo Online is compatible with the following terminals:

EFT930 Color (Booster 2 type),

iCT220, iCT250,

iWL220, iWL250
You must not use it on other terminals.

3.2.6.2. EMV packages compatibility

Incendo smart Browser is compatible with the following EMV packages:

Version 18

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Version 19

3.3. Best practices for Contactless

3.3.1. Field on/off

The contactless field is to be activated only when a contactless card is waited by the terminal. It must be
stopped when the management of the contactless card is finished.
If the contactless field is opened all the time:

On wireless terminals, product battery autonomy is reduced a lot;

The contactless module and antenna are highly stressed and reliability could decrease quickly
with time;
Applications have to manage the opening and the closing of the field according their business logic.

3.3.2. Implicit selection

Following terminals having the contactless feature inside are concerned: iWL2xx, iCT250, iSC2xx, iSC3xx,
EFT930 GCC, EFT930 BCC, iPP3XX, iPA280 (SPM), ML30C and P30C.

Implicit selection is not recommended and must be managed with caution.

Due to physical reason, implicit selection can lead to unexpected issues, for example, at the beginning
of the swipe, the card would possibly enter the antenna field and contactless chip would be handled
instead of magnetic track.

3.3.3. Use of PSTN modem with contactless activated

The electro-magnetic field created when the contactless is activated, on an integrated terminal,
prevents the usage of the PSTN modem with contactless activated.
This is not a software issue, and no software solution exists. The contactless field shall not be activated
at the same time as the modem.

Currently, the issue exists only on the iCT250, which is the only Ingenico integrated terminal with
contactless and PSTN modem.
(For instance, on EFT930BCC or EFT930GCC with modem, it works, because the modem is on the cradle,
and the distance between the modem and the contactless field is sufficient).

3.4. Pinpad system

To avoid problems when a non mock-up pinpad is linked to a mock-up terminal, the terminal mock-up
catalogues don’t include pinpad systems. So, you have to load the pinpad system (located in the
directory “Component\OS”) according to the pinpad you are using.

3.5. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

3.6. Reserved numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.
Tag numbers used by applications must be taken in the range 9FA000-9FAFFF.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

3.7. EFT930 embedding 8Mo of flash

It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

4. Issues solved in this release by component

4.1. Telium System (New version: 10.46)
Following main points are delivered in this release.

4.1.1. System Thunder

Internal
SUPTEL Description
tracker
Pinpad auto-detection at start-up: complement for this issue.

The pinpad must be off before the auto-detection. Put "pinpad_unknown"

in 020132 parameter of MANAGER.PAR. Here is a sample for
9539 SUPTEL-2290
MANAGER.PAR:
020101=1;
020131=1;
020132=255;

4.2. Telium Manager (New version: 62.03)

Following points are delivered in this release.

7809 French health care : CARD_INSIDE entry point is now available on CAM1
9437 SUPTEL-2249 Polling mode for SELECT_AID_EXTENDED added
Function PSQ_update_ClessReader() added to configure the contactless
9555 SUPTEL-2312
reader
9582 Documentation update
9606 SUPTEL-2330 “Pinpad Out Of Order” message can be customized by application
9856 On IPP3XX in emulation mode, contactless target display size fixed
9977 iST150 download report ticket now correctly printed
10037 SUPTEL-2610 Wrong return of HWCNF_SetStandbyDelay() fixed on iWL220 and iWL250
10038 SUPTEL-2610 On iST150, message 'PRESENTER MOBILE' was truncated
10039 SUPTEL-2555 Improvement of IPP280 display
10049 Bad return fixed on ipdu_etab_ligne()
10073 SUPTEL-2614 Improvement on stand by delay on iWL220/250
Improvement of help for functions PushCGUIContext() and
10113 SUPTEL-2570
PopCGUIContext()
10124 SUPTEL-2660 _clrscr does not work in SDK 8.0

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

4.3. Security

4.3.1. DLL Security (Version: 03.20)

No evolution.

4.3.2. Security Extend library (Version: 02.04)

No evolution.

4.3.3. DLL E2EE (Version: 01.01)

No evolution.

4.3.4. TLV Schemes (Version: 02.04)

No evolution.

4.3.5. Non-TLV Schemes (Version: 03.06)

No evolution.

4.4. Communication

4.4.1. Link Layer (Version: 03.20)

No evolution.

4.4.2. Pack IP (Version: 03.08)

No evolution.

4.4.3. FTP (Version: 01.20)

No evolution.

4.4.4. SNMP (Version: 01.01)

No evolution.

4.4.5. SSL (Version: 01.61)

No evolution.

4.5. Display

4.5.1. DLL Image (Version: 01.01)

No evolution.

4.5.2. Fonts (Version: 01.10)

No evolution.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

4.5.3. CGUI (Version: 01.17) / CGUI tools (Version 01.10)

No evolution.

4.5.4. Plug-in Signature Capture (Version: 01.08)

Following points are delivered in this release.

9998 Compatibility with CGUI for version upper or equal to SDK 8.0

4.5.5. Plug-in Multimedia (Version: 01.09)

Following points are delivered in this release.

10030 Compatibility with CGUI for version upper or equal to SDK 8.0

4.6. Applications

4.6.1. Incendo Online browser (Version 3.0.4)

This is a new component of the Telium SDK.

4.6.2. Image Loader (01.06)

No evolution.

4.7. AVL (Version: 01.15)

No evolution.

4.8. SDK features

Following points are delivered in this release.

10029 SUPTEL-2562 Update of buzzer section in "How To Develop on iPP3xx"

Update of the "How To " documents
Double definition of TAG_EMV_INT_TRANSACTION_TYPE removed. Define
10036 in EMV is renamed by TAG_INT_TRANSACTION_TYPE.
Use Easy Path EMV 20.01

5. Add-ons to Telium SDK

The following table presents the versions of recommended add-ons to use with this SDK.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Recommended
Add on
version to use with this SDK
Easy Path To EMV 20.1 (New version)
Add On Cless (New
3.10
architecture)
Easy Path To CLESS 3.06

Add On PCL for iPA280 1.15

Add On PCL for iWP 1.15

PCL for iMP3xx Available beginning of June

Add On Morpho 1.06

Add On Telicapt 2.14

Add On UCM 2.06

Add On SPDH 1.01

Add On APACS 40 Generic 1.08

Add On ISO8583 Generic 3.02

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK8.0 Technical Information Bulletin

Only iWL220 and iWL250 are supported for production purpose (without CGUI), other terminals are
for development only.

1. Standard development platforms

1.1. Supported terminals for production
The following terminals are managed in this SDK for production:

iWL220 and iWL250 GPRS;

iWL220 and iWL250 Bluetooth.
You can deploy applications based on this SDK for these terminals only.
Nota: CGUI applications are not yet guaranteed.

1.2. Supported terminals for development only

The other terminals are provided for application development only. The qualification of this Telium SDK
on these terminals is currently in progress:

Telium1: EFT30, EFT SMART, TWIN, ML30, SMART2, EFT930 (wireless terminal), EFT930 BL2
(wireless terminal).

Telium2: iCT220, iCT250 , ,SPM (iPA280) , iPP320, iPP350, iSC250, iSC350, iMP350, E532, iWL280
GPRS;

Pinpad: P30, P30 Contactless, PP30S, PPC30, PPR30, iPP220, iPP250, iPP280, iPP320 used as a
smart card reader (Pinpad emulation mode), iST150, TeliumPass Plus.
You are not allowed to deploy in the field, applications based on this SDK for these terminals.

You will be informed about the delivery of the “full terminals compatible” version of this SDK.

2. What’s new?
Issues solved are detailed in paragraph 4.
Here are the main evolutions coming with this Telium SDK release.

2.1. New terminals

 IWL220 and iWL250 Bluetooth : they are provided for production;
 Smart bases BEM (Bluetooth Ethernet Modem) for iWL220 and iWL250 are now managed.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

2.2. Features
 Energy save mode for ICT220 and iCT250.

2.3. Security
 This SDK is software PCI V3 ready;
 New TLV scheme pack version 2.04 is provided.

2.4. Applications
 The application Image Loader is now provided in the Telium SDK.

2.5. General points

 Many documentation improvements
 “Frequently Asked Questions” section in the CHM help file now informs you of important
points to know about Telium SDK.

3. Highlighted points
3.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response;

Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC does is not limited to banking cards. Direct
communication to other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection)

An evolution of the certification of the device proposes an alternative solution, which consists in using
the End-to-End Encryption DLL. The DLL allows two additional use-cases:

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Communication in clear text form of card data to the external world (including PDA) for cards
whose BIN is within a range specified as a white list. The idea is to free the usage of private and
loyalty cards

Communication of encrypted cardholder data for banking cards.

The E2EE DLL usable for iPA280 is provided within SDK (versions 7.6 and above).

One must keep in mind that direct (i.e. using APDU commands) communication with the smart card
from the PDA remains unauthorized. The only E2EE method covered by the certification is the one that
has been certified and bespoke encryption solutions are not allowed.

3.2. Image Loader

Image Loader is a terminal application managing idle screen, dedicated to Telium colour terminals.
Thanks to an easy handling menu, it manages fixed images display and slide shows (animations).
BMP, JPG and PNG Images and animations can be loaded from USB key, SD card or via TMS.

The installation of this application is optional: you are asked at the end of Telium SDK installation if you
want to install it.
All documentation is in the directory where Image Loader is installed.

Image Loader is compatible with the following terminals:

EFT930 Color Contactless

ML30 Color Contactless

iCT250

iWL250,

iSC250,

iSC350

iPP350.

Image Loader is particularly suitable with images generated with Image Optimizer (PC editor).

3.3. Security components

3.3.1. Schemes Pack

The Schemes Pack version 2.04 is integrated in this version of Telium SDK. It is compatible with PCI V3
requirements.

3.3.2. Security Extend library

The Security Extend library (SEC_extend.lib) is an extension of the DLL security (high level functions).

In the CHM help file in the security DLL page, you can find the list of schemes functions managed by the
Security Extend library.

If you need to use the schemes functions managed by the Security Extend library, you have to:

Include the file SEC_extend.h in your source code (SEC_extend.h includes itself the file
SEC_interface.h);

Link with SEC_extend.lib (if you use Ingedev, this library is automatically used for the link).

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

The Security Extend library version will change independently of the Security DLL version. Its version is
linked to the Schemes Pack version.

3.4. Libraries compatible with GCC4

From SDK 7.6, libraries are provided in the GNU4 format (compiled with GNU ARM 4.3.4). Main benefits
to migrate to this compiler are:

The use of a buffer overflow protection mechanism called canary;

The best support for C++.

These libraries are provided in the directory SDK\lib_gnu_434.

On the Ingedev side, this feature is available since the version 7.6.0.6.

You can read more information about this subject in the IngeDev User Guide, in the chapter Telium
Development > Stack Buffer Overflow.

3.5. Telium fonts

Fonts were previously named ISO1.xGN, ISO2.xGN…. To allow the downloading from the TMS, their
names now follows the same rule than other files. They are named 844nnnAABB.xGN where 844nnn is
the Ingenico software number, AA is the major version of the file and BB is the minor version).
The link between the names ISO and 844nnn is given in the file readme.txt in the directory
($YourInstallPath)\component\Fonts.
This change is compatible with the existing applications: for example you can continue to use
LoadFont(/SYSTEM/ISO1.SGN). You can also use: LoadFont(/SYSTEM/8442160101.SGN).

In the directory “Standard” (previously in directory “New”), are provided fonts managing fixed width
(excepted font ISO6 which is not available for fixed width due to large characters included in this
alphabet). They must be used for new development.
Fonts provided in the directory “Deprecated” (previously “Old”) embeds some characters which don’t
respect the fixed width. They are kept for compatibility with some old applications. In existing
applications, you can use the standard fonts if you don’t need the fixed width characters.

3.6. Best practices for Contactless

3.6.1. Field on/off

The contactless field is to be activated only when a contactless card is waited by the terminal. It must be
stopped when the management of the contactless card is finished.
If the contactless field is opened all the time:

On wireless terminals, product battery autonomy is reduced a lot;

The contactless module and antenna are highly stressed and reliability could decrease quickly
with time;
Applications have to manage the opening and the closing of the field according their business logic.

3.6.2. Implicit selection

Following terminals having the contactless feature inside are concerned: iWL2xx, iCT250, iSC2xx, iSC3xx,
EFT930 GCC, EFT930 BCC, iPP3XX, iPA280 (SPM), ML30C and P30C.

Implicit selection is not recommended and must be managed with caution.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Due to physical reason, implicit selection can lead to unexpected issues, for example, at the beginning
of the swipe, the card would possibly enter the antenna field and contactless chip would be handled
instead of magnetic track.

3.6.3. Use of PSTN modem with contactless activated

The electro-magnetic field created when the contactless is activated, on an integrated terminal,
prevents the usage of the PSTN modem with contactless activated.
This is not a software issue, and no software solution exists. The contactless field shall not be activated
at the same time as the modem.

Currently, the issue exists only on the iCT250, which is the only Ingenico integrated terminal with
contactless and PSTN modem.
(For instance, on EFT930BCC or EFT930GCC with modem, it works, because the modem is on the cradle,
and the distance between the modem and the contactless field is sufficient).

3.7. Pinpad system

To avoid problems when a non mock-up pinpad is linked to a mock-up terminal, the terminal mock-up
catalogues don’t include pinpad systems. So, you have to load the pinpad system (located in the
directory “Component\OS”) according to the pinpad you are using.

3.8. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

3.9. Reserved numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.
Tag numbers used by applications must be taken in the range 9FA000-9FAFFF.

3.10. EFT930 embedding 8Mo of flash

It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

4. Issues solved in this release by component

4.1. Telium System (New version: 10.35)
Following main points are delivered in this release.

4.1.1. System Thunder

9468 SUPTEL 2236 IPP3xx was unable to detect Ethernet on a 10Mbit hub
9002 SUPTEL-2038 CHM improvement on RegisterPowerFailure() function

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Improvement for HID USB, when

9353 SUPTEL-2184
used in combination with the Link Layer.
9367 SUPTEL-2333 Now, backlight display / keyboard / pinpad is managed independently
9845 SUPTEL-2383 A lot of traces in CDC driver had been removed to avoid trace_tool freeze
Evolutions for PKI V3
9427 Mock-up for MA500 et MA2G products
9457 Energy save mode for ICT220 and iCT250
9589 Improvement of Telium System documentation
9837 Contactless LED Asia managed on iST1xx
9843 PatchDriver optimisation

4.1.2. System Thunder III

Multimedia: allow secured application to disable certificate check (aka
9298 SUPTEL-2165
.MGN files)

4.1.3. Remote debugger

When using the remote debugger with Ingedev, the limit
9155 SUPTEL-1284 of 16 simultaneous breakpoints has been increased to be
50.

4.1.4. Signature
On Telium II, when a component is updated with LLT or
TMS, now, if is signed with only one signature, the
8649 TFU 5518
download is aborted with message :
"Signature 1 not found:<filename>"

4.1.5. Swipe generic

Improvement of swipe card detection when terminal exit
9243 SUPTEL-2128
from idle state (swipe already opened)

4.2. Telium Manager (New version: 62.00)

Following points are delivered in this release.

8954 SUPTEL-2006 "How to configure hardware" documentation added

Added IS_NAME_EXTENDED entry point managing 38 applications
9257 SUPTEL-2077
(IS_NAME manages 15 applications)
9144 SUPTEL-2118 Function SetFooterBmp() added to setup the bitmap displayed in the footer
Now, Telium Manager displays message "WELCOME" on PP30S when it
9381 SUPTEL-2166
waits for card after amount entry
9539 SUPTEL-2290 Pinpad auto-detection at start-up
Improvement when re-reading a magnetic stripe card (when the terminal is
9911 SUPTEL-2516
not parameterized as ISO2 only and if service call mechanism 100 is used)

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Added information to know if IP address has been obtained with manager

Header.

On Black and White terminals:

- Not connected = nothing written on top of handset
- Connected with no IP = “Eth” written on top of handset
9440 SUPTEL-2253
- Connected with IP = “ETH” written on top of handset

On Colour terminals:
- Not connected = Gray bitmap representing “Ethernet”
- Connected with no IP = Red bitmap representing “Ethernet”
- Connected with IP = Green bitmap representing “Ethernet”
When header is activated/deactivated from KEYBOARD_EVENT entry
9855 SUPTEL-2327
point, the screen is now instantly refreshed
The maximum value of IAM task is now the maximum number of mailboxes
9674 SUPTEL-2377
allowed by the system
9760 SUPTEL-2430 French domain only: In protocol CONCERT, CUP_BPOP application managed
9822 SUPTEL-2449 Use of English messages by default in the hardware configuration menus
New management for WakeUp of POS to be sure that the POS wake up at
9487
good hour.
Removed controls on Bluetooth hardware configuration in the analysis
8570
of MANAGER.PAR file
9582 Improvement of Telium Manager documentation
9675 Display of header is now correctly managed during network fallback
Added new function to display the contactless logo on B&W terminals:
9680
extern int DisplayTargetCless(int periph)
Add new function to get pinpad serial number for IPP3XX used in pinpad
9730
emulation mode: PPS_GetSoftwareConfig()
9762 Large size data supported on DLL PSC
Management of Telium fonts new names (including version and
9806
amendment)
Contactless target correctly displayed on IPP3XX used in pinpad emulation
9856
mode
Function PPS_GetConnectedPinpad() added to know the type of pinpad
9375
connected
Improvement for swap between CGUI screen and standard (non CGUI)
9946
screen
9539 SUPTEL-2290 Added pin pad auto-detect via MANAGER.PAR
Add three new functions to manage display with CGUI
CGUI_Display ();
9578
CGUI_DisplayMSG();
CGUI_DisplayMSGnum();
9902 It is now possible to enter an empty string with CGUI interface.
9930 Added ITP for ISC250 and ISC350

4.3. DLL Hardware (Version: 02.50)

Evolutions are reported with the Telium Manager evolutions in the paragraph 4.2.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

4.4. Security

4.4.1. DLL Security (Version: 03.20)

Following points are delivered in this release.

9832 Update to be compliant with Scheme Pack 2.04

9842 Update to be compliant with Scheme Pack 2.04
9608 TlvFirstKey managed in mock-up

4.4.2. Security Extend library (Version: 02.04)

This is a new component.

4.4.3. DLL E2EE (Version: 01.01)

No evolution.

4.4.4. TLV Schemes (Version: 02.04)

This is a new version of TLV schemes.

4.4.5. Non-TLV Schemes (Version: 03.06)

No evolution.

4.5. Communication

4.5.1. Link Layer (Version: 03.20)

Following points are delivered in this release.

Improvement of 300ms in certain conditions when testing the availability of

9485 SUPTEL-1951
the driver (both MODEM and MODEM_V34 loaded)..
9475 SUPTEL-2212 Add of the configuration tag LL_PPP_T_TERMINATION_DELAY for PPP layer
Added 2 specific statuses LL_STATUS_PERIPHERAL_OUT_OF_BASE for USB,
9545 SUPTEL-2282
and LL_STATUS_ETHERNET_OUT_OF_BASE for Ethernet.

4.5.2. Pack IP (Version: 03.08)

No evolution.

4.5.3. FTP (Version: 01.20)

No evolution.

4.5.4. SNMP (Version: 01.01)

No evolution.

4.5.5. SSL (Version: 01.61)

Following points are delivered in this release.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Compatibility with PKI V3

9521 DLL SSL error codes improvement

4.6. Display

4.6.1. DLL Image (Version: 01.01)

No evolution.

4.6.2. Fonts (Version: 01.10)

Following points are delivered in this release.

To allow update with TMS, new name has been given to

Telium font files, including version and amendment:
844216=FONT ISO1 STANDARD
844217=FONT ISO2 STANDARD
844218=FONT ISO3 STANDARD
844219=FONT ISO5 STANDARD
844220=FONT ISO7 STANDARD
844221=FONT ISO15 STANDARD
9594
844209=FONT ISO1 DEPRECATED
844210=FONT ISO2 DEPRECATED
844211=FONT ISO3 DEPRECATED
844212=FONT ISO5 DEPRECATED
844213=FONT ISO6 DEPRECATED
844214=FONT ISO7 DEPRECATED
844215=FONT ISO15 DEPRECATED

The fonts are now double signed for Telium2

4.6.3. CGUI (Version: 01.17) / CGUI tools (Version 01.10)

Following points are delivered in this release.

8911 SUPTEL-1958 Documentation updated for fonts CGUICURSIVE et CGUIFANTASY

Before any loadurl we ensure that there are no remaining events in
9138 SUPTEL-2110
the browser
WGUI_DISPLAY_BLACK_WHITE and WGUI_DISPLAY_COLORS are now
9273 SUPTEL-2145 deprecated WGUI_DISPLAY_HARDWARE is used to create the display in
terminal native mode
9645 SUPTEL-2354 Improvement when image is enlarged
Some explicit not needed refreshes of the browser were identified
9729 SUPTEL-2410
and removed
Now, loading url of type javascript:"some javascript" execute
5593 "some javascript" in the browser. Previously it wrote "some javascript"
on the page
Now, touchscreen samples are groupped together before being sent to
8778
plugin
9442 The file is now correctly closed when a resource is missing in a tar cabinet

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Changing src of an iframe with javascript is now correctly handled using

9790
iframe parent document as current url
Some explicit not needed refresh of the browser were identified and
9729 SUPTEL-2410
removed

4.6.4. NanoX (Version 01.23)

This is a new version of NanoX.

4.6.5. Plug-in Signature Capture (Version: 01.07)

No evolution.

4.6.6. Plug-in Multimedia (Version: 01.08)

This is a new version of this component.

4.7. Applications

4.7.1. Incendo Online browser

This component will be delivered in the next version of the Telium SDK (version with all terminals
supported).

4.7.2. Image Loader (01.06)

This is a new component of the Telium SDK.

4.8. AVL (Version: 01.15)

Following points are delivered in this release.

9688 SUPTEL-2227 Function TlvTree_RemoveChild() is now deprecated.

4.9. SDK features

Following points are delivered in this release.

9702 Add a "FAQ" section in the SDK CHM help file

5. Deprecated APIs
Due to evolution of product ranges or software, some functions become sometimes obsolete.
The deprecated functions are now grouped in the file deprecated.h. They will be removed from the SDK
in the future.
We deeply advise you to clean your code by applying the new way described in the help file as soon as
functions become obsoletes.
Nevertheless, if you want to continue to use these functions, it is possible by adding deprecated.h and,
according the information in the help file, add a compilation option. If you don’t do that, there will be a
warning during the compilation.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

5.1. Changes between SDK7.5 and SDK7.6

The variable UNKNOWN, defined in param.h in the SDK7.5.x, is replaced by UNKNOWN_PPAD
because UNKNOWN is a name too common and could be used elsewhere in client applications.

The function ColorScreenSaver() changes of prototype.

5.2. Changes between SDK7.4.1 and SDK7.5

Following functions become deprecated:

gprslib_open()

colorlib_open()

umslib_open()

5.3. Changes between SDK7.2 and SDK7.4.1

No external function or structure becomes obsolete.

5.4. Changes before SDK7.2

Here is the list of functions which have been declared obsolete before this SDK and added to
deprecated.h:

InitModeGraphic();
Telium Manager functions of type void XXXlib_open (void); Check the CHM help file to have the
exhaustive list (functions of type XXXlib_open, not belonging to the Telium Manager can be not
concerned).
int InitSysPpad (int);
int InitDLLSaisiePpad (void);
int is_loaded(NO_SEGMENT i);
void ET_Idf_seq (T_VERSION version,NO_SEGMENT *noseg,CHECKSUM *nochecksum);
void ET_Identifier_seq (int noappli);
void USQ_Aff_montant (unsigned long * montant ,S_MONEY * devise);
int PPS_SendClearKeyCommand (unsigned char *Domain);
unsigned char PSQ_Double90_cle ( void );

6. Add-ons to Telium SDK

The following table presents the versions of recommended add-ons to use with this SDK.

Recommended
Add on
version to use with this SDK
Easy Path To EMV 20 (New version)
Add On Cless (New
3.10 (New version)
architecture)
Easy Path To CLESS 3.06

Add On PCL for iPA280 1.15 (New version)

Add On PCL for iWP 1.15 (New version)

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

PCL for iMP3xx New package to come

Add On Morpho 1.06

Add On Telicapt 2.14 (New version)

Add On UCM 2.06

Add On SPDH 1.01

Add On APACS 40 Generic 1.08

Add On ISO8583 Generic 3.02

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK7.6.1 Technical Information Bulletin

1. Standard development platforms

1.1. Telium 1
This SDK release is compatible with the following terminals:

EFT30

EFT SMART

TWIN

ML30

SMART2

EFT930 (wireless terminal)

EFT930 BL2 (wireless terminal)

1.2. Telium 2
This SDK release is compatible with the following terminals:

iCT220, iCT250

SPM (iPA280)

iPP320, iPP350

iSC250

iSC350

iWL220G, iWL250G (wireless terminals). Smart bases are not currently managed.

iWL280 (wireless terminal, for development only)

iMP3xx

E532+ (for development only)

1.3. Pinpads
This SDK release is compatible with the following products:

P30, P30 Contactless

PP30S

PPC30

PPR30

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

iPP220, iPP250, iPP280

iPP320 used as a smart card reader (Pinpad emulation mode)

1.4. Contactless readers

This SDK release is compatible with the following products:

iST150

TeliumPass Plus

2. Main evolutions
Issues solved are detailed in paragraph 4.
Here are the main evolutions coming with this release.

2.1. New terminals

Terminal TWIN31 (TWIN30 without RS232) is now supported in the SDK.

2.2. Telium Manager

For PCI+ applications: download at startup bug fix

CAD30UCR in power off mode, card insertion is detected again

Correction for migration of an ipp3xx in terminal mode to a Telium SDK7.6 or higher version

2.3. General points

Many documentation improvements

3. Highlighted points
3.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response;

Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC does is not limited to banking cards. Direct
communication to other types of cards (e.g. loyalty) is not allowed.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection).

3.2. Migration of an iPP3xx to SDK7.6

In case of an iPP320 or an iPP350 configured as terminal and loaded with a SDK lower than version 7.6,
the migration to SDK7.6 must be run with, at the same time, the update of the parameter “020504” in
Manager.PAR file. If you don’t do that, the VID/PID of the iPP3xx could change.
As a reminder, values of this parameter are the following:

Before SDK .6 From SDK 7.6

iPP3 is terminal mode 020504=0; 020504=2;
iPP3 in pinpad emulation mode 020504=1; 020504=1;
Mode reserved for future use This mode didn’t exist 020504=0;

3.3. Libraries compatible with GCC4

From SDK 7.6, libraries are provided in the GNU4 format (compiled with GNU ARM 4.3.4). Main benefits
to migrate to this compiler are:

The use of a buffer overflow protection mechanism called canary;

The best support for C++.

These libraries are provided in the directory SDK\lib_gnu_434.

On the Ingedev side, this feature is available since the version 7.6.0.6.

You can read more information about this subject in the IngeDev User Guide, in the chapter Telium
Development > Stack Buffer Overflow

3.4. Contactless

3.4.1. Field on/off

The contactless field is to be activated only when a contactless card is waited by the terminal. It must be
stopped when the management of the contactless card is finished.
If the contactless field is opened all the time:

On wireless terminals, product battery autonomy is reduced a lot;

The contactless module and antenna are highly stressed and reliability could decrease quickly
with time;
Applications have to manage the opening and the closing of the field according their business logic.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

3.4.2. Implicit selection

Following terminals having the contactless feature inside are concerned: iWL2xx, iCT250, iSC2xx, iSC3xx,
EFT930 GCC, EFT930 BCC, iPP3XX, iPA280 (SPM), ML30C and P30C.

Implicit selection is not recommended and must be managed with caution.

Due to physical reason, implicit selection can lead to unexpected issues, for example, at the beginning
of the swipe, the card would possibly enter the antenna field and contactless chip would be handled
instead of magnetic track.

3.4.3. Use of PSTN modem with contactless activated

The electro-magnetic field created when the contactless is activated, on an integrated terminal,
prevents the usage of the PSTN modem with contactless activated.
This is not a software issue, and no software solution exists. The contactless field shall not be activated
at the same time as the modem.

Currently, the issue exists only on the iCT250, which is the only Ingenico integrated terminal with
contactless and PSTN modem.
(For instance, on EFT930BCC or EFT930GCC with modem, it works, because the modem is on the cradle,
and the distance between the modem and the contactless field is sufficient).

3.5. ISC250 and iSC350 terminals downgrades

As a general rule, it is forbidden to mix Telium Manager and Telium System from different SDKs.
Nevertheless, if it happens during the development phase, be aware that on iSC250 and iSC350, due to
NanoX driver incompatibility,

If you mix a Telium system included in a SDK greater or equal to SDK7.6, with a Telium Manager
included in a SDK lower than SDK7.6 the loading will be refused by the system;

If you mix a Telium System included in a SDK lower than SDK7.6, with a Telium Manager
included in a SDK greater or equal to SDK7.6, the terminal will not be able to restart;

3.6. Pinpad system

To avoid problems when a non mock-up pinpad is linked to a mock-up terminal, the terminal mock-up
catalogues don’t include pinpad systems. So, you have to load the pinpad system (located in the
directory “Component\OS”) according to the pinpad you are using.

3.7. Functions XXX_libopen()

Due to some XXX_libopen() functions which are now deprecated, on Ingedev version lower or equal to
7.4.0.7, there are warnings when this SDK if used with a project created by a “New Telium Project”. You
have to add the compilation option _DEPRECATED_SDK71_ to remove the warnings.

3.8. Binaries having a size multiple of 1024 bytes (Telium 1 terminals)

With the SDKs 6.4.X, 6.5.x and 6.6, it was not possible to download binaries having a size multiple of
1024 bytes before signature. Message is "Bad signature". To avoid loading problem on these SDK, you
have to check that the size of your generated application, without signature, is not a multiple of 1024
bytes. (Size of application – 676) must not be a multiple of 1024.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

3.9. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

3.10. Reserved numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.
Tag numbers used by applications must be taken in the range 9FA000-9FAFFF.

3.11. EFT930 embedding 8Mo of flash

It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

4. Issues solved in this release by component

4.1. Telium Manager (New version: 61.01)
Following points are delivered in this release.

FT SUPTEL Description
Card entry service : New point of customization
See Telium Manager User Guide "How to use the Card Entry service"
6934 and sample in SDK
7857 CAD30UCR in power off mode, card insertion is detected again.
iPP 3xx in pinpad mode : compatibility
8118 from SDK7.5 to SDK7.6.1 is now managed
8378 Manage QVGA screen and specific keyboard of IWL280 (like ISC250)
8954 SUPTEL-2006 "How to configure hardware": documentation updated
"remote_download”, “remote_downloading” and
SUPTEL-2034 “remote_downloading_from_manager” functions :
8956 (See also 2171) documentation updated
8985 SUPTEL-2026 HWCNF_SetStandbyDelay function : documentation updated
Manager User Guide.doc (020103,020105,020111 et 020112
parameters) :
9059 SUPTEL-2067 documentation updated.
9228 SUPTEL-2138 Fallback management by Manager: documentation updated.
9256 SUPTEL-2145 PushCGUIContext : documentation updated
New POS TWIN31 = TWIN30 with no RS232
9428 OS_GetIdLecteur updated for Twin31
PSQ_Get_Cless_Capabilities returns right value if
9486 SUPTEL-2264 Pin Pad not supporting CLESS is connected
9519 Cless Target is now at right position for ICT2XX
9525 GetManagerLanguage returns correct value for customized language
Consultation of list of software "F / Manager / Consulting /
State /" and Applications with no loaded applications displays
9531 "NO SEGMENTS"
9532 Unexpected blank screen has been removed

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

9533 Backlight management on ISC350 now possible

9537 On iSC350, available flash menu displays the right value
9538 CGUI page, disappeared references removed(French domain only)
9540 cash flow register on COM1 (IWL2XX for example) is now managed
9575 “EventHeader” function correctly implemented for color displays
9622 for PCI+ applications: download at startup bug fix

4.2. DLL Hardware (Version: 02.46)

Evolutions are reported with the Telium Manager evolutions in the paragraph 4.2

4.3. CGUI (Version: 01.15) / CGUI tools (Version 01.10)

No evolution.

4.4. NanoX (Version 01.19 for Thunder 3 terminals, 01.17 for others)
No evolution.

4.5. Plug-in Multimedia (Version: 01.07)

No evolution.

4.6. Plug-in Signature Capture (Version: 01.07)

No evolution.

4.7. DLL Security (Version: 03.19)

No evolution.

4.8. DLL E2EE (Version: 01.01)

No evolution.

4.9. Schemes (Version: 03.06)

No evolution.

4.10. TLV Schemes (Version: 01.16)

No evolution.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

4.11. Pack IP (Version: 03.08)

No evolution.

4.12. Link Layer (Version: 03.19)

No evolution.

4.13. FTP (Version: 01.20)

No evolution.

4.14. SSL (Version: 01.57)

No evolution.

4.15. DLL Image (Version: 01.01)

No evolution.

4.16. AVL (Version: 01.14)

No evolution.

4.17. SDK features

Following points are delivered in this release.

9596 Sample CardEntry bug fix

4.18. Fonts (Version: 01.09)

No evolution.

5. Deprecated APIs
Due to evolution of product ranges or software, some functions become sometimes obsolete.
The deprecated functions are now grouped in the file deprecated.h. They will be removed from the SDK
in the future.
We deeply advise you to clean your code by applying the new way described in the help file as soon as
functions become obsoletes.
Nevertheless, if you want to continue to use these functions, it is possible by adding deprecated.h and,
according the information in the help file, add a compilation option. If you don’t do that, there will be a
warning during the compilation.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

5.1. Changes between SDK7.5 and SDK7.6

The variable UNKNOWN, defined in param.h in the SDK7.5.x, is replaced by UNKNOWN_PPAD
because UNKNOWN is a name too common and could be used elsewhere in client applications.

The function ColorScreenSaver() changes of prototype.

5.2. Changes between SDK7.4.1 and SDK7.5

Following functions become deprecated:

gprslib_open()

colorlib_open()

umslib_open()

5.3. Changes between SDK7.2 and SDK7.4.1

No external function or structure becomes obsolete.

5.4. Changes before SDK7.2

Here is the list of functions which have been declared obsolete before this SDK and added to
deprecated.h:

InitModeGraphic();
Telium Manager functions of type void XXXlib_open (void); Check the CHM help file to have the
exhaustive list (functions of type XXXlib_open, not belonging to the Telium Manager can be not
concerned).
int InitSysPpad (int);
int InitDLLSaisiePpad (void);
int is_loaded(NO_SEGMENT i);
void ET_Idf_seq (T_VERSION version,NO_SEGMENT *noseg,CHECKSUM *nochecksum);
void ET_Identifier_seq (int noappli);
void USQ_Aff_montant (unsigned long * montant ,S_MONEY * devise);
int PPS_SendClearKeyCommand (unsigned char *Domain);
unsigned char PSQ_Double90_cle ( void );

6. Add-ons to Telium SDK

The following table presents the versions of recommended add-ons to use with this SDK.

Recommended
Add on
version to use with this SDK
Easy Path To EMV 19.1
3.09 is required to use the
AddOn Cless (New
iST150 in smart mode.
architecture) Otherwise, you can use 3.07.
3.06 is required to use the
Easy Path To CLESS iST150 in smart mode.
Otherwise, you can use 3.04.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

AddOn PCL for iPA280 1.11

AddOn PCL for iWP 1.05

PCL for iMP3xx New package to come

AddOn Morpho 1.06

AddOn Telicapt 2.12

AddOn UCM 2.06

AddOn SPDH 1.01

AddOn APACS 40 Generic 1.08

AddOn ISO8583 Generic 3.02

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK7.6 Technical Information Bulletin

1. Standard development platforms

1.1. Telium 1
This SDK release is compatible with the following terminals:

EFT30

EFT SMART

TWIN

ML30

SMART2

EFT930 (wireless terminal)

EFT930 BL2 (wireless terminal)

1.2. Telium 2
This SDK release is compatible with the following terminals:

iCT220, iCT250

SPM (iPA280)

iPP320, iPP350

iSC250

iSC350

iWL220G, iWL250G (wireless terminals). Smart bases are not currently managed.

iWL280 (wireless terminal, for development only)

iMP3xx

E532+ (for development only)

1.3. Pinpads
This SDK release is compatible with the following products:

P30, P30 Contactless

PP30S

PPC30

PPR30

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

iPP220, iPP250, iPP280

iPP320 used as a smart card reader (P30 emulation mode)

1.4. Contactless readers

This SDK release is compatible with the following products:

iST150

TeliumPass Plus

2. Main evolutions
Issues solved are detailed in paragraph 4.
Here are the main evolutions coming with this release.

2.1. New terminals

Following terminals are now supported in the SDK.

iWL280 iMP350
(for development only)

New terminal for production: iMP350;

New terminals for development only: iWL280, E532+.

2.2. Telium Manager

Improvements of Telium Manager menus;

Management of specific transactions via MESSAGE_RECEIVED.

2.3. Telium System

Fixed problem of CGUI EFT930 BL2 when the terminal is associated with a smart cradle;

Increased maximum number of applications on a terminal.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

2.4. General points

Telium simulator is no more supported and is not provided anymore;

Libraries are compatible with compiler GNU 4.3.4;

2.5. Documentation

Many improvements of documentation in Telium System and Telium Manager;

“How To Develop on color terminals” provided.

3. Highlighted points
3.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response;

Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC does is not limited to banking cards. Direct
communication to other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection).

3.2. Libraries compatible with GCC4

3.2.1. Overview
In this release the libraries are provided in the GNU4 format (compiled with GNU ARM 4.3.4). Main
benefits to migrate to this compiler are:

The use of a buffer overflow protection mechanism called canary;

The best support for C++.

These libraries are provided in the directory SDK\lib_gnu_434.

On the Ingedev side, this feature is available since the version 7.6.0.6.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

3.2.2. Canaries
Stack buffer overflow is a well known cause of bugs in programs. It is also a way for security attacks.
The canary protection provided with GNU 4.3.4 is a mechanism detecting these buffer overflows. You
can read more information about this subject in the IngeDev User Guide, in the chapter Telium
Development > Stack Buffer Overflow
When a buffer overflow is detected, the application stops on OEM_Exit (9E). Additional information is
available on the diagnostic ticket.

Stack protector option is activated in the library provided in the SDK.

If you don’t use Ingedev, you have to add the compilation option: -fstack-protector-all to enable
canaries. If you use Ingedev, canaries are activated by default when you choose the tool chain GNU
ARM 4.3.4.

3.3. Contactless

3.3.1. Field on/off

The contactless field is to be activated only when a contactless card is waited by the terminal. It must be
stopped when the management of the contactless card is finished.
If the contactless field is opened all the time:

On wireless terminals, product battery autonomy is reduced a lot;

The contactless module and antenna are highly stressed and reliability could decrease quickly
with time;
Applications have to manage the opening and the closing of the field according their business logic.

3.3.2. Implicit selection

Following terminals having the contactless feature inside are concerned: iWL2xx, iCT250, iSC2xx, iSC3xx,
EFT930 GCC, EFT930 BCC, iPP3XX, iPA280 (SPM), ML30C and P30C.

Implicit selection is not recommended and must be managed with caution.

Due to physical reason, implicit selection can lead to unexpected issues, for example, at the beginning
of the swipe, the card would possibly enter the antenna field and contactless chip would be handled
instead of magnetic track.

3.3.3. Use of PSTN modem with contactless activated

The electro-magnetic field created when the contactless is activated, on an integrated terminal,
prevents the usage of the PSTN modem with contactless activated.
This is not a software issue, and no software solution exists. The contactless field shall not be activated
at the same time as the modem.

Currently, the issue exists only on the iCT250, which is the only Ingenico integrated terminal with
contactless and PSTN modem.
(For instance, on EFT930BCC or EFT930GCC with modem, it works, because the modem is on the cradle,
and the distance between the modem and the contactless field is sufficient).

3.4. ISC250 and iSC350 terminals downgrades

As a general rule, it is forbidden to mix Telium Manager and Telium System from different SDKs.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Nevertheless, if it happens during the development phase, be aware that on iSC250 and iSC350, due to
NanoX driver incompatibility,

If you mix a Telium system included in a SDK greater or equal to SDK7.6, with a Telium Manager
included in a SDK lower than SDK7.6the loading will be refused by the system;

If you mix a Telium System included in a SDK lower than SDK7.6, with a Telium Manager
included in a SDK greater or equal to SDK7.6, the terminal will not be able to restart;

3.5. Pinpad system

To avoid problems when a non mock-up pinpad is linked to a mock-up terminal, the terminal mock-up
catalogues don’t include pinpad systems. So, you have to load the pinpad system (located in the
directory “Component\OS”) according to the pinpad you are using.

3.6. Functions XXX_libopen()

Due to some XXX_libopen() functions which are now deprecated, on Ingedev version lower or equal to
7.4.0.7, there are warnings when this SDK if used with a project created by a “New Telium Project”. You
have to add the compilation option _DEPRECATED_SDK71_ to remove the warnings.

3.7. Binaries having a size multiple of 1024 bytes (Telium 1 terminals)

With the SDKs 6.4.X, 6.5.x and 6.6, it was not possible to download binaries having a size multiple of
1024 bytes before signature. Message is "Bad signature". To avoid loading problem on these SDK, you
have to check that the size of your generated application, without signature, is not a multiple of 1024
bytes. (Size of application – 676) must not be a multiple of 1024.

3.8. Function Beep()

From SDK 6.4 to 6.4.3, prototype of the function Beep() was: int Beep(int note, int octave, unsigned
short duration).
Since SDK 6.5, it is: int Beep(int note, int octave, unsigned short duration, int Action);
So if you have generated your application with SDK6.4.x you have to re-compile it while upgrading to a
SDK 6.5 or newer.

3.9. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

3.10. Reserved numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.
Tag numbers used by applications must be taken in the range 9FA000-9FAFFF.

3.11. EFT930 embedding 8Mo of flash

It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

4. Issues solved in this release by component

4.1. Telium System (New version: 10.04)
Following points are delivered in this release.

4.1.1. System Thunder

7199 TFU 4444
Documentation of function status() has been updated for CAM peripherals
New limitations in the number of applications:
- Now, maximum of applications with different VAR Ids is 14 (previously maximum
8643 was 14 different applications)
- The sum of number of VAR applications and number of constructor applications is
increased to 38 (previously it was 38)
When message "bad key number" is displayed by LLT, the key number had no
8887
meaning.
Documentation of CAM function error code has been updated: error code 1 is
SUPTEL-2020
8904 returned only with power_down() function. Otherwise, error code 7 is used if the
/ TFU 5772 card is not inserted.
8944 Update of "Telium System Reference Manual"

4.1.2. Driver Bluetooth

CGUI versions didn't work on EFT930 BL2 when the terminal is associated with a smart
9187
cradle

4.1.3. Driver GPRS

8531 TFU5510 Fix buffer overflow in GPRS driver with the DGPRS_FIOCTL_GET_IMSI fioctl.

4.1.4. Driver Modem

Now it is possible to choose fast connect (75ms) or fast connect (500ms) using
8691 TFU5548
v22fc_Philippines=ON;

4.1.5. System Thunder III

8991 SUPTEL-2040 Fixed problem with simultaneous functioning of the touch screen and the contactless.

4.2. Telium Manager (New version: 61.00)

Following points are delivered in this release.

9130 French health care only: Third CAM is now logged into the Hardware Configuration ticket
A section was added in each header of exported functions of EFT30.LIB to specify if the
4047
function exits when it don't exist into DLL
On software loading via USB or card, now, Telium Manager proposes only the catalogues
5935
corresponding to the terminal

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

8110 Treatment of SCREEN.INI for PINPAD IDLE bug fixed

8204 TFU 5336 CHM improvment : rename TPass with Contactless into documentation
8621 Added function to get the 2 letters of serial number
8893 TFU 5689 API added to start Telium Manager menu: extern int PSQ_Telium Manager_menu (void);
8901 For French health Care: Access to MODEM for authorisation in configuration "SANTE"
8923 For French health Care: buffer USB/serial increased
For French health Care: function OS_ClkGetMilliseconds added to return the number of
8924
milliseconds since the start up of the terminal
8931 SUPTEL-2030 Documentation of Service Call 100
8954 SUPTEL-2006 "How to configure hardware" documentation improvement
SUPTEL-2034 Updated documentation about returned values of “remote_download”,
8956
SUPTEL-2171 “remote_downloading” and “remote_downloading_from_Telium Manager” functions
It is now possible to dynamically load an element in the header: API added: void
8957 SUPTEL-1996
SetHeaderAreaBmp(int HeaderArea,char *PtBmp);
Field "display" added into S_TRANSIN structure
--> 0 means that Telium Manager display default screen (default value)
8971 --> 1 means that Telium Manager does not display screen
Must be activated with GET_AMOUNT_STATE_PARAMETER entry point and
ACTIV_SPECIFIC_DISPLAY mask
8985 SUPTEL-2026 Improvement of help for HWCNF_SetStandbyDelay()
8997 Translation of function names
9041 PSQ_Write_money() didn't work (disk HOST was not mounted)
Some functions added:
Pinpad_List_Entry
9053 Pinpad_Confirm_AID
Terminal_Confirm_AID
Terminal_List_Entry
9059 SUPTEL-2067 Error into documentation about 020103,020105,020111 et 020112 parameters fixed
9090 Timeout to enter APN was too short
9110 Put footer key (F1, F2, F3, F4) on screen in accordance with real keyboard mapping
9114 SUPTEL-2095 French domain only: DLL CB2A: mount of the GPRS link at first connection
Added:
Call START_OF_TRANSACTION entry point before credit, cancel and pre-
9115 SUPTEL-2107 auto transaction.
Call END_OF_TRANSACTION entry point after credit, cancel and pre-auto
transaction.
9134 It is now possible for Service Call 100 to be for only one application
9141 Management of specific transaction via MESSAGE_RECEIVED
9144 SUPTEL-2118 Possibility to customize footer on non-colour device with SetFooterBmp()
9153 Chip card was not processed when inserted during Receive_message service call.
9228 SUPTEL-2138 Improvement of documentation
UNKNOWN define is already use in kernel EMV.
9251
Replaced UNKNOWN by UNKNOWN_PPAD in param.h.
9256 SUPTEL-2145 PushCGUIContext problem of returning 0 as error code on iPP320 fixed
9291 Optimized disconnection process in GPRS/GSM communication
9304 Regression fixed in Telium Manager/INITIALISATION/HEADER menu
9313 Regression fixed into Telium Manager/LICENSE/ADD menu
9314 Regression fixed into Telium Manager menu.
9325 SUPTEL-2176 Function returning model equipment added
9350 For French domain: feature added to disable contactless
9362 Disable shortcut "37" and "38" if internal Cless
9378 Added new function to get BOOSTER type: int BoosterType(void);

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

9379 Improvement of IDLE_MESSAGE sample in Telium Manager Documentation

8743 TFU5669 Updated documentation about BMP format
8777 Added function to return terminal number as an integer
8486 SUPTEL-1760 Type of the parameter file containing the message is 5962
Add supported BMP format into CHM for IDLE_SCREEN field into SCREEN.INI
9403
configuration file.
9096 Fixed error on software configuration ticket
4605 SUPTEL-2147 New functions added to calculate the Ram free size and the flash free size
8766 Optimized default parameters for backlight.
8895 TFU 5613 Updated description of HWCNF_SetBacklightDuration() function
9036 SUPTEL-2070 Improved documentation
9262 SUPTEL-2149 Improvement of ColorScreen sample
9398 SUPTEL-2182 API added to change the date format
Function sms_get_info() returned SMS sender instead of date in timestamp field
9477 SUPTEL-2267
of SMS_INFO.
PSQ_Get_Cless_Capabilities() didn't return right value if connected Pin Pad does
9486 SUPTEL-2264
not support CLESS
9276 Fixed problem to use PP30 on SDK7.5

4.3. DLL Hardware (Version: 02.45)

Evolutions are reported with the Telium Manager evolutions in the paragraph 4.2.

4.4. CGUI (Version: 01.15) / CGUI tools (Version 01.10)

Following documentation point is delivered in this release.

SUPTEL-
8911 Update of CGUI documentation
1958

4.5. NanoX (Version 01.19 for Thunder 3 terminals, 01.17 for others)
This new version only includes internal improvements.

4.6. Plug-ins Multimedia (Version: 01.07)

This new version only includes internal improvements.

4.7. Plug-ins Signature Capture (Version: 01.07)

No evolution.

4.8. DLL Security (Version: 03.19)

Following points are delivered in this release.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

TFU3678 Adding treatments for SEC_ComputeMAC_AC() and SEC_VerifyMAC_AC() when

6306
SUPTEL-679 uiInputDataLength is not multiple of 8

4.9. DLL E2EE (Version: 01.01)

E2EE stands for End To End Encryption.

This is a new feature. It is available only for iPA280 and must not be used on other terminals.
The scheme IngeCrypt is provided in version 1.05.

4.10. Schemes (Version: 03.06)

No evolution.

4.11. TLV Schemes (Version: 01.16)

No evolution.

4.12. Pack IP (Version: 03.08)

No evolution.

4.13. Link Layer (New version: 03.18)

Following points are delivered in this release.

9241 SUPTEL-1961 Internal improvement

9285 SUPTEL-2109 LL_GPRS_Connect() management on timeout
9296 LL_ERROR_NOT_READY becomes LL_ERROR_NETWORK_NOT_READY
9401 Application can open the driver itself

4.14. FTP (Version: 01.20)

Following points are delivered in this release.

Allows LLTonEFT application to upload files directly in the /HOST disk of the remote
9071
terminal (instead of using TRANSFER.INI mechanism).

4.15. SSL (Version: 01.57)

Following points are delivered in this release.

9167 Library SSL provided in GCC4 format (canaries activated)

4.16. DLL Image (Version: 01.01)

Following documentation point is delivered in this release.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

9262 SUPTEL-2149 Function ImageReadFile() has been added into ColorScreen sample

4.17. AVL (Version: 01.14)

AVL stands for Added Value Libraries.

Following points are delivered in this release.

TFU4783
8708 Library AVL can now be used in a C++ project
TFU5634
9159 Library AVL provided in GCC4 format (canaries activated)

4.18. SDK features

Following points are delivered in this release.

9178 Telium simulator is no more supported and is removed from SDK

9270 Sample are now provided by default in Telium 2 compatibility
7048 "how to develop on Colour terminal" documentation added to the SDK
7682 Provided libraries generated with compiler GNU 4.3.4
8918 Added documentation to know the first SDK of availability for trap functions
Update information about Contactless in "How To Use iPP320 as a Pinpad"
9306 document
9066 CHM improvement: EAN barcodes
9070 CHM improvement : barcode 39

4.19. Fonts (Version: 01.09)

No evolution.

5. Deprecated APIs
Due to evolution of product ranges or software, some functions become sometimes obsolete.
The deprecated functions are now grouped in the file deprecated.h. They will be removed from the SDK
in the future.
We deeply advise you to clean your code by applying the new way described in the help file as soon as
functions become obsoletes.
Nevertheless, if you want to continue to use these functions, it is possible by adding deprecated.h and,
according the information in the help file, add a compilation option. If you don’t do that, there will be a
warning during the compilation.

5.1. Changes between SDK7.5 and SDK7.6

The variable UNKNOWN, defined in param.h in the SDK7.5.x, is replaced by UNKNOWN_PPAD
because UNKNOWN is a name too common and could be used elsewhere in client applications.

The function ColorScreenSaver() changes of prototype.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

5.2. Changes between SDK7.4.1 and SDK7.5

Following functions become deprecated:

gprslib_open()

colorlib_open()

umslib_open()

5.3. Changes between SDK7.2 and SDK7.4.1

No external function or structure becomes obsolete.

5.4. Changes before SDK7.2

Here is the list of functions which have been declared obsolete before this SDK and added to
deprecated.h:

InitModeGraphic();
Telium Manager functions of type void XXXlib_open (void); Check the CHM help file to have the
exhaustive list (functions of type XXXlib_open, not belonging to the Telium Manager can be not
concerned).
int InitSysPpad (int);
int InitDLLSaisiePpad (void);
int is_loaded(NO_SEGMENT i);
void ET_Idf_seq (T_VERSION version,NO_SEGMENT *noseg,CHECKSUM *nochecksum);
void ET_Identifier_seq (int noappli);
void USQ_Aff_montant (unsigned long * montant ,S_MONEY * devise);
int PPS_SendClearKeyCommand (unsigned char *Domain);
unsigned char PSQ_Double90_cle ( void );

6. Add-ons to Telium SDK

The following table presents the versions of recommended add-ons to use with this SDK.

Recommended
Add on
version to use with this SDK
Easy Path To EMV 19.1
3.09 is required to use the
AddOn Cless (New
iST150 in smart mode.
architecture) Otherwise, you can use 3.07.
3.06 is required to use the
Easy Path To CLESS iST150 in smart mode.
Otherwise, you can use 3.04.
AddOn PCL for iPA280 1.11

AddOn PCL for iWP 1.05

PCL for iMP3xx New package to come

AddOn Morpho 1.06

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

AddOn Telicapt 2.12

AddOn UCM 2.06

AddOn SPDH 1.01

AddOn APACS 40 Generic 1.08

AddOn ISO8583 Generic 3.02

7. Version of components in the previous SDKs

The following table compiles the versions of modules packaged in the previous versions of the SDK.
In this table, grey cells correspond to evolution of the component.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

DLL Hardware

TLV Schemes
DLL Security

Multimedia
CGUI tools
Link layer

Simulator
Signature
Schemes

capture
Pack IP

Telium
SNMP

Image

Pinlib
CGUI

IAPP
Font
AVL
SSL
FTP
SDK System Manager

1.05
6.5 08.33 54.01 2.31 3.09 3.06 1.12 3.10 3.05 1.17 1.47 1.05 1.01 2.05 1.10 1.08
(1)
7.0 Pre for 08.52 55.99 3.09 3.10 3.05 1.01 1.99 1.01
ISC350
6.5.1 08.34 54.02 2.32 3.10 3.06 1.12 3.10 3.05 1.17 1.48 1.07 1.01 1.09 1.6.1 2.05 1.10 1.08
6.5.2 08.34 54.03 2.32 3.10 3.06 1.12 3.10 3.05 1.17 1.48 1.07 1.01 1.09 1.6.1 2.05 1.10 1.08
7.0 Pre 2 for 08.54 55.98 3.09 3.10 3.05 1.01 1.99 1.02 1.02
ISC350
6.5.3 08.35 54.03 2.32 3.10 3.06 1.12 3.10 3.05 1.17 1.48 1.07 1.01 1.09 1.6.1 2.05 1.10 1.08
6.6 08.44 55.00 2.32 3.10 3.06 1.12 3.10 3.05 1.17 1.48 1.07 1.01 1.09 1.07 1.01 2.06 1.10 1.08
7.1 09.00 56.00 2.35 3.11 3.06 1.16 3.10 3.05 1.17 1.48 1.08 1.01 1.09 1.11 1.10 1.03 1.04 2.07 1.10 1.08
3.11
7.2 09.16 57.01 2.37 3.06 1.16 3.13 3.06 1.17 1.48 1.09 1.01 1.09 1.12 1.10 1.05 1.05 2.07 1.10 1.08
(2)
7.2.1 09.20 57.02 2.38 3.12 3.06 1.16 3.13 3.06 1.17 1.48 1.09 1.01 1.09 1.12 1.10 1.05 1.05 2.07 1.10 1.08
7.3 09.30 58.00 2.38 3.12 3.06 1.16 3.14 3.06 1.17 1.01 1.48 1.09 1.01 1.09 1.12 1.10 1.05 1.05 2.07 1.10 1.08
7.3.1 09.31 58.01 2.38 3.12 3.06 1.16 3.14 3.06 1.17 1.01 1.48 1.09 1.01 1.09 1.12 1.10 1.05 1.05 2.07 1.10 1.08
7.3.2 09.31 58.04 2.38 3.12 3.06 1.16 3.14 3.06 1.17 1.01 1.48 1.09 1.01 1.09 1.12 1.10 1.05 1.05 2.07 1.10 1.08
7.4 09.51 59.03 2.38 3.15 3.06 1.16 3.16 3.07 1.19 1.01 1.53 1.09 1.01 1.09 1.14 1.10 1.07 1.06 2.07 1.10 1.08
7.4.1 09.51 59.04 2.38 3.15 3.06 1.16 3.16 3.07 1.19 1.01 1.53 1.09 1.01 1.09 1.14 1.10 1.07 1.06 2.07 1.10 1.08
7.5 09.76 60.00 2.43 3.17 3.06 1.16 3.17 3.08 1.19 1.01 1.56 1.10 1.01 1.09 1.15 1.10 1.07 1.06 2.07 1.10 1.08
7.5.1 09.78 60.01 2.43 3.17 3.06 1.16 3.17 3.08 1.19 1.01 1.56 1.10 1.01 1.09 1.15 1.10 1.07 1.06 2.07 1.10 1.08
7.5.2 for
09.80 60.02 2.43 3.17 3.06 1.16 3.17 3.08 1.19 1.01 1.56 1.10 1.01 1.09 1.15 1.10 1.07 1.06 2.07 1.10 1.08
iSC350
7.6 10.04 61.00 2.45 3.19 3.06 1.16 3.19 3.08 1.20 1.01 1.57 1.14 1.01 1.09 1.15 1.10 1.07 1.07 NA 1.10 1.10

(2): 3.12 pour CTAP

(1): 1.06 pour ISO1

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK7.5.2 Technical Information Bulletin

8. Standard development platforms

8.1. Telium 2
This SDK release is compatible only with iSC350.

9. Highlighted points
9.1. Contactless

9.1.1. Field on/off

The contactless field is to be activated only when a contactless card is waited by the terminal. It must be
stopped when the management of the contactless card is finished.
If the contactless field is opened all the time:

On wireless terminals, product battery autonomy is reduced a lot;

The contactless module and antenna are highly stressed and reliability could low quickly with
time;
Applications have to manage the opening and the closing of the field according their business logic.

9.1.2. Implicit selection

Implicit selection is not recommended and must be managed with caution.
Due to physical reason, implicit selection can lead to unexpected issues, for example, at the beginning
of the swipe, the card would possibly enter the antenna field and contactless chip would be handled
instead of magnetic track.

9.2. Functions XXX_libopen()

Due to some XXX_libopen() functions which are now deprecated, on Ingedev version lower or equal to
7.4.0.7, there are warnings when this SDK if used with a project created by a “New Telium Project”. You
have to add the compilation option _DEPRECATED_SDK71_ to remove the warnings.

9.3. Service numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

10. Issues solved in this release by component

10.1. Telium System (New version: 9.80_iSC350)

10.1.1. System Booster 3 (0219)

Internal improvements.

10.1.2. System Thunder 3 (0019)

Internal improvements.

10.2. Telium Manager (New version: 60.02)

Internal improvements.

10.3. CGUI (Version: 01.15) / CGUI tools (Version 01.10)

No evolution.

10.4. NanoX (Version 01.19)

Evolutions are included with the Telium Manager evolutions in the paragraph 4.2.

10.5. Plug-ins Multimedia (Version: 01.06)

No evolution.

10.6. Plug-ins Signature Capture (Version: 01.07)

No evolution.

10.7. DLL Security (Version: 03.17)

No evolution.

10.8. DLL Hardware (Version: 02.43)

No evolution.

10.9. Schemes (Version: 03.06)

No evolution.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

10.10. TLV Schemes (Version: 01.16)

No evolution.

10.11. Pack IP (Version: 03.08)

No evolution.

10.12. Link Layer (New version: 03.17)

No evolution.

10.13. FTP (Version: 01.19)

No evolution.

10.14. SSL (Version: 01.56)

No evolution.

10.15. AVL (Version: 01.10)

AVL stands for Added Value Libraries.

No evolution.

10.16. SDK functionalities

No evolution.

10.17. Fonts (Version: 01.09)

No evolution.

11. Deprecated APIs

Due to evolution of product ranges or software, some functions become sometimes obsolete.
The deprecated functions are now grouped in the file deprecated.h. They will be removed from the SDK
in the future.
We deeply advise you to clean your code by applying the new way described in the help file as soon as
functions become obsoletes.
Nevertheless, if you want to continue to use these functions, it is possible by adding deprecated.h and,
according the information in the help file, add a compilation option. If you don’t follow that, there will
be a warning during the compilation.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

11.1. Changes since SDK 7.5

No evolution.

11.2. Changes between SDK7.4.1 and SDK7.5

Following functions become deprecated:

gprslib_open

colorlib_open

umslib_open

11.3. Changes between SDK7.2 and SDK7.4.1

No external function or structure becomes obsolete.

11.4. Changes before SDK7.2

Here is the list of functions which have been declared obsolete before this SDK and added to
deprecated.h:

InitModeGraphic();
Telium Manager functions of type void XXXlib_open (void); Check the CHM help file to have the
exhaustive list (functions of type XXXlib_open, not belonging to the Telium Manager can be not
concerned).
int InitSysPpad (int);
int InitDLLSaisiePpad (void);
int is_loaded(NO_SEGMENT i);
void ET_Idf_seq (T_VERSION version,NO_SEGMENT *noseg,CHECKSUM *nochecksum);
void ET_Identifier_seq (int noappli);
void USQ_Aff_montant (unsigned long * montant ,S_MONEY * devise);
int PPS_SendClearKeyCommand (unsigned char *Domain);
unsigned char PSQ_Double90_cle ( void );

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK7.5.1 Technical Information Bulletin

1. Standard development platforms

1.1. Telium 1
This SDK release is compatible with the following terminals:

EFT30

EFT SMART

TWIN

ML30

SMART2

EFT930 (wireless terminal)

EFT930 BL2 (wireless terminal)

1.2. Telium 2
This SDK release is compatible with the following terminals:

iCT220, iCT250

SPM (iPA280)

iPP320, iPP350

iSC250

iSC350

iWL220, iWL250

1.3. Pinpads
This SDK release is compatible with the following products:

P30, P30 Contactless

PP30S

PPC30

PPR30

iPP220, iPP250, iPP280

iPP320 in emulation mode

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

1.4. Contactless readers

This SDK release is compatible with iST150.

2. Highlighted points
2.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response
Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC does is not limited to banking cards. Direct
communication to other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection).

2.2. Contactless

2.2.1. iPPx
IPP2XX and IPP3XX are supported since the version 3.4 of the add-on contactless for new architecture.
These terminals are not supported by old architecture (add-on 2.x).

2.2.2. Field on/off

The contactless field is to be activated only when a contactless card is waited by the terminal. It must be
stopped when the management of the contactless card is finished.
If the contactless field is opened all the time:

On wireless terminals, product battery autonomy is reduced a lot;

The contactless module and antenna are highly stressed and reliability could low quickly with
time;
Applications have to manage the opening and the closing of the field according their business logic.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

2.2.3. Implicit selection

Following terminals having the contactless feature inside are concerned: iWL2xx, iCT250, iSC2xx, iSC3xx,
EFT930 GCC, EFT930 BCC, iPP3XX, iPA280 (SPM), ML30C and P30C.

Implicit selection is not recommended and must be managed with caution.

Due to physical reason, implicit selection can lead to unexpected issues, for example, at the beginning
of the swipe, the card would possibly enter the antenna field and contactless chip would be handled
instead of magnetic track.

2.3. Pinpad system

To avoid problems when a non mock-up pinpad is linked to a mock-up terminal, the terminal mock-up
catalogues don’t include pinpad systems. So, you have to load the pinpad system (located in the
directory “Component\OS”) according to the pinpad you are using.

2.4. Functions XXX_libopen()

Due to some XXX_libopen() functions which are now deprecated, on Ingedev version lower or equal to
7.4.0.7, there are warnings when this SDK if used with a project created by a “New Telium Project”. You
have to add the compilation option _DEPRECATED_SDK71_ to remove the warnings.

2.5. Binaries having a size multiple of 1024 bytes (Telium 1 terminals)

With the SDKs 6.4.X, 6.5.x and 6.6, it was not possible to download binaries having a size multiple of
1024 bytes before signature. Message is "Bad signature". To avoid loading problem on these SDK, you
have to check that the size of your generated application, without signature, is not a multiple of 1024
bytes. (Size of application – 676) must not be a multiple of 1024.

2.6. Function Beep()

From SDK 6.4 to 6.4.3, prototype of the function Beep() was: int Beep(int note, int octave, unsigned
short duration).
Since SDK 6.5, it is: int Beep(int note, int octave, unsigned short duration, int Action);
So if you have generated your application with SDK6.4.x you have to re-compile it while upgrading to a
SDK 6.5 or newer.

2.7. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

2.8. Service numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

2.9. EFT930 embedding 8Mo of flash

It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

3. Issues solved in this release by component

3.1. Telium System (New version: 9.78)
Following points are delivered in this release.

3.1.1. System Thunder 1 & 2

9001 Fixed the problem when an iWL is put on the base when it is in sleep mode

3.2. Telium Manager (New version: 60.01)

Following points are delivered in this release.
8878 Software configuration ticket taken into account for iPP320 in emulation mode

3.3. CGUI (Version: 01.15) / CGUI tools (Version 01.10)

No evolution.

3.4. NanoX (Version 01.17)

No evolution.

3.5. Plug-ins Multimedia (Version: 01.06)

No evolution.

3.6. Plug-ins Signature Capture (Version: 01.07)

No evolution.

3.7. DLL Security (Version: 03.17)

No evolution.

3.8. DLL Hardware (Version: 02.43)

Evolutions are included with the Telium Manager evolutions in the paragraph 4.2.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

3.9. Schemes (Version: 03.06)

No evolution.

3.10. TLV Schemes (Version: 01.16)

No evolution.

3.11. Pack IP (Version: 03.08)

No evolution.

3.12. Link Layer (New version: 03.17)

No evolution.

3.13. FTP (Version: 01.19)

No evolution.

3.14. SSL (Version: 01.56)

No evolution.

3.15. AVL (Version: 01.10)

AVL stands for Added Value Libraries.

No evolution.

3.16. SDK functionalities

No evolution.

3.17. Fonts (Version: 01.09)

No evolution.

4. Deprecated APIs
Due to evolution of product ranges or software, some functions become sometimes obsolete.
The deprecated functions are now grouped in the file deprecated.h. They will be removed from the SDK
in the future.
We deeply advise you to clean your code by applying the new way described in the help file as soon as
functions become obsoletes.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Nevertheless, if you want to continue to use these functions, it is possible by adding deprecated.h and,
according the information in the help file, add a compilation option. If you don’t follow that, there will
be a warning during the compilation.

4.1. Changes between SDK7.4.1 and SDK7.5

Following functions become deprecated:

gprslib_open

colorlib_open

umslib_open

4.2. Changes between SDK7.2 and SDK7.4.1

No external function or structure becomes obsolete.

4.3. Changes before SDK7.2

Here is the list of functions which have been declared obsolete before this SDK and added to
deprecated.h:

InitModeGraphic();
Telium Manager functions of type void XXXlib_open (void); Check the CHM help file to have the
exhaustive list (functions of type XXXlib_open, not belonging to the Telium Manager can be not
concerned).
int InitSysPpad (int);
int InitDLLSaisiePpad (void);
int is_loaded(NO_SEGMENT i);
void ET_Idf_seq (T_VERSION version,NO_SEGMENT *noseg,CHECKSUM *nochecksum);
void ET_Identifier_seq (int noappli);
void USQ_Aff_montant (unsigned long * montant ,S_MONEY * devise);
int PPS_SendClearKeyCommand (unsigned char *Domain);
unsigned char PSQ_Double90_cle ( void );

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK7.5 Technical Information Bulletin

1. Standard development platforms

1.1. Telium 1
This SDK release is compatible with the following terminals:

EFT30

EFT SMART

TWIN

ML30

SMART2

EFT930 (wireless terminal)

EFT930 BL2 (wireless terminal)

1.2. Telium 2
This SDK release is compatible with the following terminals:

iCT220, iCT250

SPM (iPA280)

iPP320, iPP350

iSC250

iSC350

iWL220, iWL250

1.3. Pinpads
This SDK release is compatible with the following products:

P30, P30 Contactless

PP30S

PPC30

PPR30

iPP220, iPP250, iPP280

iPP320 in emulation mode

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

1.4. Contactless
This SDK release is compatible with iST150.

2. New terminals
Following terminals are now supported in the SDK.

iWL250 iWL220

iST150 iSC250 iPP280

It is also now possible to use iPP320 in pinpad emulation mode.

3. Highlighted points
3.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response
Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC does is not limited to banking cards. Direct
communication to other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection).

3.2. Contactless

3.2.1. iPPx
IPP2XX and IPP3XX are supported since the version 3.4 of the add-on contactless for new architecture.
These terminals are not supported by old architecture (add-on 2.x).

3.2.2. Field on/off

The contactless field is to be activated only when a contactless card is waited by the terminal. It must be
stopped when the management of the contactless card is finished.
If the contactless field is opened all the time:

On wireless terminals, product battery autonomy is reduced a lot;

The contactless module and antenna are highly stressed and reliability could low quickly with
time;
Applications have to manage the opening and the closing of the field according their business logic.

3.2.3. Implicit selection

Following terminals having the contactless feature inside are concerned: iWL2xx, iCT250, iSC2xx, iSC3xx,
EFT930 GCC, EFT930 BCC, iPP3XX, iPA280 (SPM), ML30C and P30C.

Implicit selection is not recommended and must be managed with caution.

Due to physical reason, implicit selection can lead to unexpected issues, for example, at the beginning
of the swipe, the card would possibly enter the antenna field and contactless chip would be handled
instead of magnetic track.

3.3. QR Barcode
AVL library included in this release manages QR Barcode. To use this functionality, the DLL 844096xxx
must be loaded in the terminal.
This DLL is provided in the SDK in the directory component\AVL\Barcode\QR.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

3.4. Functions XXX_libopen()

Due to some XXX_libopen() functions which are now deprecated, on Ingedev version lower or equal to
7.4.0.7, there are warnings when this SDK if used with a project created by a “New Telium Project”. You
have to add the compilation option _DEPRECATED_SDK71_ to remove the warnings.

3.5. Binaries having a size multiple of 1024 bytes (Telium 1 terminals)

With the SDKs 6.4.X, 6.5.x and 6.6, it was not possible to download binaries having a size multiple of
1024 bytes before signature. Message is "Bad signature". To avoid loading problem on these SDK, you
have to check that the size of your generated application, without signature, is not a multiple of 1024
bytes. (Size of application – 676) must not be a multiple of 1024.

3.6. Function Beep()

From SDK 6.4 to 6.4.3, prototype of the function Beep() was: int Beep(int note, int octave, unsigned
short duration).
Since SDK 6.5, it is: int Beep(int note, int octave, unsigned short duration, int Action);
So if you have generated your application with SDK6.4.x you have to re-compile it while upgrading to a
SDK 6.5 or newer.

3.7. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

3.8. Service numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.

3.9. EFT930 embedding 8Mo of flash

It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

4. Issues solved in this release by component

4.1. Telium System (New version: 9.76)
Following points are delivered in this release.

4.1.1. System Thunder 1 & 2

4513 Improved CDC device compatibility (COM5)
Send DCD event to application task when device is removed. USB_PRESENT is
7192
sent.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

7711 TFU 4821 Improvement of documentation for is_iso1() and is_iso3() functions
8031 The number of semaphore is increased from 70 to 150.
8534 Added definition for COMH event number and event mask, E_COMH and COMH
New values returned by SystemFioctl(SYS_FIOCTL_GET_DISPLAY_TYPE). Old
8607
ones are still supported
Added SystemFioctl SYS_FIOCTL_GET_VIDEO_CAPABILITY to know if video is
8611
supported by the terminal
8648 TFU 4993 Add definition for COMH event number and event mask, E_COMH and COMH
Const added before const string parameters of the following functions :
FS_dskkill(), FS_dskdelete(), FS_mount(), FS_unmount(), FS_format(),
8669 TFU 5597 FS_readmode(), FS_chgmode (), FS_dsksize (), FS_dskfree (), FS_opendir (),
FS_rename(), FS_unlink (), FS_exist (), FS_open(), FS_write (),FS_mkdir(),
FS_rmdir()
Documentation had been updated concerning ttestall(): only bits 15 and 31 are
7867 TFU 4811
reserved for application.
Add a comment to the description of the StartRetroEclairage and
StopRetroEclairage functions. StartRetroEclairage and StopRetroEclairage are
8720 TFU 5613
for system usage. The application must use HWCNF_SetBacklightIntensity and
HWCNF_SetBacklightDuration functions for backlight management

4.1.2. Driver USB CDC

Send DCD event to application task when device is removed. USB_PRESENT is
7192
sent.
Added driver serial signals for COM_SL : DCD, RTS, DTR, CTS. Hardware flow
7810
control can be activated using format()

4.1.3. Booster III ISC

8256 TFU 5017 Touch screen: Alternative combined mode

4.2. Telium Manager (New version: 60.00)

Following points are delivered in this release.

4605 New function used to calculate the free size Ram and the free size flash
4894 Backlight has now a minimum value on color display.
USB or flash loading via the Telium Manager is now possible by selecting the
5935
catalogue
the terminal type is not checked if the tag 020501 or the tag 020502 is present in
6211
the file manager.par
New parameter in MANAGER.PAR.
TAG 020629
6920
0 = Display Provider Name if known into header (default)
1 = Force Display Network Name into header
The terminal can perform an auto detection of pinpad in the menu
6928 pinpad type or when the terminal is started if the parameter pinpad
is set to yes.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

7008 TFU 4264 Come back of InitVar() prototype in services.h

TFU 4482,
7743 Documentation improvement for Telium manager menus
5659
8147 France only: message 'INTRODUIRE CARTE' is replaced by 'INSEREZ CARTE'
8204 TFU 5336 Updated documentation about contactless in manager.PAR
8271 Cleaned Telium manager menus about deep discharge
8353 GPRS information added in the Telium Manager ticket
Timeout added when the terminal is waiting for the Telium Manager password
8359
in CGUI mode
Detailed list of libraries is increased to 99 in CGUI mode (like it was in non CGUI
8360
mode)
8402 Backlight on portables now remains activated when an application is running
8409 TFU 5435 Added documentation for Priority management of Manager Entry Points
8433 It is now possible to enter IP address on 7 digits (previously minimum was 8)
8455 GPRS automatic start-up problem fixed
8467 Memory optimization when displaying the header
Telium Manager messages names with version and amendment are now
8486 TFU 5438
supported. Type of the parameter file containing the message is AC36
8491 TFU 5449 France only: taken into account of the field Auto in cash register protocol
8637 TFU 5555 Improvement of documentation on Telium Manager General Parameter
Fonction PSQ_Is_Pinpad_Contactless() added to know if a pinpad is contacless
8675
or not
6913 CDMA managed by Telium Manager
8520 Display improvement when display is done by booster and then by Thunder
Telium manager now refreshes the screen after keyboard_event() returning 0 (=
8785
no key pressed)
8818 Opening of DLL Crypto() added for CADTOOL
8856 TFU 5716 SQ_Treat_Message() removed from include file because it is a private function
8861 Improved font DAX

4.3. CGUI (Version: 01.15) / CGUI tools (Version 01.10)

The Mock-up manager catalogue has to be loaded only to use the Ingedev CGUI Preview tool.

Following points are delivered in this release.

The monospace font has been regenerated and all characters have the same
7060 5641 width. Overlapping characters are not supported by font drawing engine, all
characters must be verified by hand to have the same width

4.4. NanoX (Version 01.17)

Following points are delivered in this release.

8275 TFU 5363 Signature Capture file has last 8 bytes repeated twice

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

4.5. Plug-ins Multimedia (Version: 01.06)

No evolution.

4.6. Plug-ins Signature Capture (Version: 01.07)

No evolution.

4.7. DLL Security (Version: 03.17)

Following points are delivered in this release.

8586 Management of DLL Security when loaded on product without Booster

4.8. DLL Hardware (Version: 02.43)

Evolutions are included with the Telium Manager evolutions in the paragraph 4.2.

4.9. Schemes (Version: 03.06)

No evolution.

4.10. TLV Schemes (Version: 01.16)

No evolution.

4.11. Pack IP (Version: 03.08)

Following points are delivered in this release.

Added protocoles to reach proxy servers: SOCKS4a, SOCKS5 et HTTP-CONNECT

7059
tunnel
2229/8732 Default parameters for Wi-Fi interface
8817 TFU5728 Added functions to manage IP routing table
8654 TFU 5586 Improved documentation SSL for update information about PKCS files

4.12. Link Layer (New version: 03.17)

Following points are delivered in this release.

5510 In audit mode, ATZ sent after receiving No Carrier

8258 Add scripting capability to the Link Layer

4.13. FTP (Version: 01.19)

No evolution.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

4.14. SSL (Version: 01.56)

Following points are delivered in this release.

8142 TFU 5660 Fixed problem with SSL_New() with invalid files as parameter
8725 Improved return codes of SSL_Connect()
Some functions don't reset anymore if DLL is not present.
List of function is: SSL_New(), SSL_NewProfile(), SSL_LoadProfile(),
7936 TFU 5045 SSL_DeleteProfile(), (), SSL_GetProfile(), SSL_GetProfileCount(), X509_Load(),
PKCS12_GetPrivateKey(), PKCS12_GetCertificate(), PKCS12_GetCA(),
SSL_Server_Open()

4.15. AVL (Version: 01.10)

AVL stands for Added Value Libraries.

Following points are delivered in this release.

8601 TFU 5530 Management of barcodes QR

8914 Printing of AVL ASM module is now optional
8598 TFU 5492 CRC of ASM component was equal to 0

4.16. SDK functionalities

Following points are delivered in this release.

Last directory where the Telium SDK is installed becomes the default installation
8346
directory
Following functions become deprecated:
gprslib_open()
8580
colorlib_open()
umslib_open()
8744 TFU 5665 CHM improvement

4.17. Fonts (Version: 01.09)

No evolution.

5. Deprecated APIs
Due to evolution of product ranges or software, some functions become sometimes obsolete.
The deprecated functions are now grouped in the file deprecated.h. They will be removed from the SDK
in the future.
We deeply advise you to clean your code by applying the new way described in the help file as soon as
functions become obsoletes.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Nevertheless, if you want to continue to use these functions, it is possible by adding deprecated.h and,
according the information in the help file, add a compilation option. If you don’t follow that, there will
be a warning during the compilation.

5.1. Changes between SDK7.4.1 and SDK7.5

Following functions become deprecated:

gprslib_open

colorlib_open

umslib_open

5.2. Changes between SDK7.2 and SDK7.4.1

No external function or structure becomes obsolete.

5.3. Changes before SDK7.2

Here is the list of functions which have been declared obsolete before this SDK and added to
deprecated.h:

InitModeGraphic();
Telium Manager functions of type void XXXlib_open (void); Check the CHM help file to have the
exhaustive list (functions of type XXXlib_open, not belonging to the Telium Manager can be not
concerned).
int InitSysPpad (int);
int InitDLLSaisiePpad (void);
int is_loaded(NO_SEGMENT i);
void ET_Idf_seq (T_VERSION version,NO_SEGMENT *noseg,CHECKSUM *nochecksum);
void ET_Identifier_seq (int noappli);
void USQ_Aff_montant (unsigned long * montant ,S_MONEY * devise);
int PPS_SendClearKeyCommand (unsigned char *Domain);
unsigned char PSQ_Double90_cle ( void );

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK7.4.2 Technical Information Bulletin

6. Standard development platforms

6.1. Telium 1
This SDK release is compatible with the following terminals:

EFT30

EFT SMART

TWIN

ML30

SMART2

EFT930 (wireless terminal)

EFT930 BL2 (wireless terminal)

6.2. Telium 2
This SDK release is compatible with the following terminals:

iCT220, iCT250

SPM (iPA280)

iPP320, iPP350

iSC350
ISC250 is provided in this release for development only.
Applications written with this SDK are compatible with the wireless terminals iWL220 and iWL250
(development purpose only).

6.3. Pinpads
This SDK release is compatible with the following products:

P30, P30 Contactless

PP30S

PPC30

PPR30

iPP220, iPP250

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

7. Highlighted points
7.1. Fix for iPP3XX
Ethernet communication now works when using magic box with IPP3xx.

7.2. Restriction for iPA280 and PCI PED 2.x compliance

During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response
Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC does is not limited to banking cards. Direct
communication to other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection).

7.3. Contactless
For the contactless functionality, you must use at least the Add-on “Contactless” version 3.2 (new
architecture) and 2.12 (old architecture).
For IPP2XX and IPP3XX, use version equal or upper to 3.4 for new architecture. These terminals are not
supported by old architecture (add-on 2.x).

7.4. IWL
Applications written with this SDK are compatible with the wireless terminals iWL220 and iWL250
(development purpose only).

7.5. Functions XXX_libopen()

Due to the XXX_libopen() functions which are now deprecated, on Ingedev version lower or equal to
7.4.0.7, there are warnings when this SDK if used with a project created by a “New Telium Project”. You
have to add the compilation option _DEPRECATED_SDK71_ to remove the warnings.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

7.6. Binaries having a size multiple of 1024 bytes (Telium 1 terminals)

With the SDKs 6.4.X, 6.5.x and 6.6, it was not possible to download binaries having a size multiple of
1024 bytes before signature. Message is "Bad signature". To avoid loading problem on these SDK, you
have to check that the size of your generated application, without signature, is not a multiple of 1024
bytes. (Size of application – 676) must not be a multiple of 1024.

7.7. Function Beep()

From SDK 6.4 to 6.4.3, prototype of the function Beep() was: int Beep(int note, int octave, unsigned
short duration).
Since SDK 6.5, it is: int Beep(int note, int octave, unsigned short duration, int Action);
So if you have generated your application with SDK6.4.x you have to re-compile it while upgrading to a
SDK 6.5 or newer.

7.8. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

7.9. Service numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.

7.10. EFT930 embedding 8Mo of flash

It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

8. Issues solved in this release by component

8.1. Telium System (New version: 9.57 for iPP3XX only, remains 9.51
for other terminals)
Following point is delivered in this release.

SUPTEL Ethernet detection timeout value increased from 3sec to 30sec to be able to
10420/9468
2844 detect 10Mbit ethernet connection (For IPP3XX only)

8.2. Telium Manager (Version: 59.04)

No evolution.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

8.3. CGUI (Version: 01.14) / CGUI tools (Version 01.10)

No evolution.

8.4. Plug-ins Multimedia (Version: 01.06)

No evolution.

8.5. Plug-ins Signature Capture (Version: 01.07)

No evolution.

8.6. DLL Security (Version: 03.15)

No evolution.

8.7. DLL Hardware (Version: 02.38)

No evolution.

8.8. Schemes
No evolution of schemes: version is 03.06.
No evolution of TLV schemes: version is 01.16.

8.9. Pack IP (Version: 03.07)

No evolution.

8.10. Link Layer (New version: 03.16)

No evolution.

8.11. FTP (Version: 01.19)

No evolution.

8.12. SSL (Version: 01.53)

Following points are delivered in this release.

8.13. AVL (Version: 01.09)

AVL stands for Added Value Libraries.
No evolution.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

8.14. SDK functionalities

No evolution.

8.15. Fonts (Version: 01.09)

No evolution.

9. Deprecated APIs
Due to evolution of product ranges or software, some functions become sometimes obsolete.
The deprecated functions are now grouped in the file deprecated.h. They will be removed from the SDK
in the future.
We deeply advise you to clean your code by applying the new way described in the help file as soon as
functions become obsoletes.
Nevertheless, if you want to continue to use these functions, it is possible by adding deprecated.h and,
according the information in the help file, add a compilation option. If you don’t follow that, there will
be a warning during the compilation.

9.1. Changes between SDK7.2 and SDK7.4

No external function or structure becomes obsolete.

9.2. Changes before SDK7.2

Here is the list of functions which have been declared obsolete before this SDK and added to
deprecated.h:

InitModeGraphic();
All Telium Manager functions of type void XXXlib_open (void);
int InitSysPpad (int);
int InitDLLSaisiePpad (void);
int is_loaded(NO_SEGMENT i);
void ET_Idf_seq (T_VERSION version,NO_SEGMENT *noseg,CHECKSUM *nochecksum);
void ET_Identifier_seq (int noappli);
void USQ_Aff_montant (unsigned long * montant ,S_MONEY * devise);
int PPS_SendClearKeyCommand (unsigned char *Domain);
unsigned char PSQ_Double90_cle ( void );

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK7.4.1 Technical Information Bulletin

1. Standard development platforms

1.1. Telium 1
This SDK release is compatible with the following terminals:

EFT30

EFT SMART

TWIN

ML30

SMART2

EFT930 (wireless terminal)

EFT930 BL2 (wireless terminal)

1.2. Telium 2
This SDK release is compatible with the following terminals:

iCT220, iCT250

SPM (iPA280)

iPP320, iPP350

iSC350
ISC250 is provided in this release for development only.
Applications written with this SDK are compatible with the wireless terminals iWL220 and iWL250
(development purpose only).

1.3. Pinpads
This SDK release is compatible with the following products:

P30, P30 Contactless

PP30S

PPC30

PPR30

iPP220, iPP250

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

2. Highlighted points
2.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response
Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC does is not limited to banking cards. Direct
communication to other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection).

2.2. Contactless
For the contactless functionality, you must use at least the Add-on “Contactless” version 3.2 (new
architecture) and 2.12 (old architecture).
For IPP2XX and IPP3XX, use version equal or upper to 3.4 for new architecture. These terminals are not
supported by old architecture (add-on 2.x).

2.3. IWL
Applications written with this SDK are compatible with the wireless terminals iWL220 and iWL250
(development purpose only).

2.4. Functions XXX_libopen()

Due to the XXX_libopen() functions which are now deprecated, on Ingedev version lower or equal to
7.4.0.7, there are warnings when this SDK if used with a project created by a “New Telium Project”. You
have to add the compilation option _DEPRECATED_SDK71_ to remove the warnings.

2.5. Binaries having a size multiple of 1024 bytes (Telium 1 terminals)

With the SDKs 6.4.X, 6.5.x and 6.6, it was not possible to download binaries having a size multiple of
1024 bytes before signature. Message is "Bad signature". To avoid loading problem on these SDK, you

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

have to check that the size of your generated application, without signature, is not a multiple of 1024
bytes. (Size of application – 676) must not be a multiple of 1024.

2.6. Function Beep()

From SDK 6.4 to 6.4.3, prototype of the function Beep() was: int Beep(int note, int octave, unsigned
short duration).
Since SDK 6.5, it is: int Beep(int note, int octave, unsigned short duration, int Action);
So if you have generated your application with SDK6.4.x you have to re-compile it while upgrading to a
SDK 6.5 or newer.

2.7. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

2.8. Service numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.

2.9. EFT930 embedding 8Mo of flash

It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

3. Issues solved in this release by component

3.1. Telium System (New version: 9.51)
No evolution.

3.2. Telium Manager (New version: 59.04)

Following points are delivered in this release.

8647 For French application: SPM come back to base managed in Telium Manager
8740 Fixed French health care CAM1 problem

3.3. CGUI (Version: 01.14) / CGUI tools (Version 01.10)

No evolution.

3.4. Plug-ins Multimedia (Version: 01.06)

No evolution.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

3.5. Plug-ins Signature Capture (Version: 01.07)

No evolution.

3.6. DLL Security (Version: 03.15)

No evolution.

3.7. DLL Hardware (Version: 02.38)

No evolution.

3.8. Schemes
No evolution of schemes: version is 03.06.
No evolution of TLV schemes: version is 01.16.

3.9. Pack IP (Version: 03.07)

No evolution.

3.10. Link Layer (New version: 03.16)

No evolution.

3.11. FTP (Version: 01.19)

No evolution.

3.12. SSL (Version: 01.53)

Following points are delivered in this release.

3.13. AVL (Version: 01.09)

AVL stands for Added Value Libraries.
No evolution.

3.14. SDK functionalities

No evolution.

3.15. Fonts (Version: 01.09)

No evolution.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

4. Deprecated APIs
Due to evolution of product ranges or software, some functions become sometimes obsolete.
The deprecated functions are now grouped in the file deprecated.h. They will be removed from the SDK
in the future.
We deeply advise you to clean your code by applying the new way described in the help file as soon as
functions become obsoletes.
Nevertheless, if you want to continue to use these functions, it is possible by adding deprecated.h and,
according the information in the help file, add a compilation option. If you don’t follow that, there will
be a warning during the compilation.

4.1. Changes between SDK7.2 and SDK7.4

No external function or structure becomes obsolete.

4.2. Changes before SDK7.2

Here is the list of functions which have been declared obsolete before this SDK and added to
deprecated.h:

InitModeGraphic();
All Telium Manager functions of type void XXXlib_open (void);
int InitSysPpad (int);
int InitDLLSaisiePpad (void);
int is_loaded(NO_SEGMENT i);
void ET_Idf_seq (T_VERSION version,NO_SEGMENT *noseg,CHECKSUM *nochecksum);
void ET_Identifier_seq (int noappli);
void USQ_Aff_montant (unsigned long * montant ,S_MONEY * devise);
int PPS_SendClearKeyCommand (unsigned char *Domain);
unsigned char PSQ_Double90_cle ( void );

5. Version of components in the previous SDKs

The following table compiles the versions of modules packaged in the previous versions of the SDK.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK7.4 Technical Information Bulletin

1. Standard development platforms

1.1. Telium 1
This SDK release is compatible with the following terminals:

EFT30

EFT SMART

ML30

SMART2

EFT930 (wireless terminal)

EFT930 BL2 (wireless terminal)

1.2. Telium 2
This SDK release is compatible with the following terminals:

iCT220, iCT250

SPM (iPA280)

iPP320, iPP350

iSC350
ISC250 is provided in this release for development only.
Applications written with this SDK are compatible with the wireless terminals iWL220 and iWL250
(development purpose only).

1.3. Pinpads
This SDK release is compatible with the following products:

P30, P30 Contactless

PP30S

PPC30

PPR30

iPP220, iPP250

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

2. Highlighted points
2.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response
Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC does is not limited to banking cards. Direct
communication to other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection).

2.2. Contactless
For the contactless functionality, you must use at least the Add-on “Contactless” version 3.2 (new
architecture) and 2.12 (old architecture).
For IPP2XX and IPP3XX, use version equal or upper to 3.4 for new architecture. These terminals are not
supported by old architecture (add-on 2.x).

2.3. UCM
You have to use at least add-on UCM version 2.5.

2.4. IWL
Applications written with this SDK are compatible with the wireless terminals iWL220 and iWL250
(development purpose only).

2.5. TWIN
This SDK is not compatible with TWIN range of terminals.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

2.6. Functions XXX_libopen()

Due to the XXX_libopen() functions which are now deprecated, on Ingedev version lower or equal to
7.4.0.7, there are warnings when this SDK if used with a project created by a “New Telium Project”. You
have to add the compilation option _DEPRECATED_SDK71_ to remove the warnings.

2.7. Binaries having a size multiple of 1024 bytes (Telium 1 terminals)

With the SDKs 6.4.X, 6.5.x and 6.6, it was not possible to download binaries having a size multiple of
1024 bytes before signature. Message is "Bad signature". To avoid loading problem on these SDK, you
have to check that the size of your generated application, without signature, is not a multiple of 1024
bytes. (Size of application – 676) must not be a multiple of 1024.

2.8. Function Beep()

From SDK 6.4 to 6.4.3, prototype of the function Beep() was: int Beep(int note, int octave, unsigned
short duration).
Since SDK 6.5, it is: int Beep(int note, int octave, unsigned short duration, int Action);
So if you have generated your application with SDK6.4.x you have to re-compile it while upgrading to a
SDK 6.5 or newer.

2.9. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

2.10. Service numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.

2.11. EFT930 embedding 8Mo of flash

It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.

3. Issues solved in this release by component

3.1. Telium System (New version: 9.51)
Following points are delivered in this release.

3.1.1. System Thunder

EthernetSetOption() now allow to change Ethernet interface parameters
3920
(ETH_IFO_GATEWAY, ETH_IFO_DNS1 et ETH_IFO_DNS2)

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

TFU3783
6252 and Unplugging of Ethernet wire was not detected during a download by TMS
TFU4810
7617 Application types range added for Manufacturer applications: 44000-44999
7654 Inter UC evolution
7753 Rewriting in a disk in RAM improved
7764 TFU4917 Change backlight frequency for IPP320/IPP350
7793 USB traces transfer improved
7819 Battery management improved when temperature rises up
8031 Number of semaphores managed is now 150 (70 before)
Function SYS_FIOCTL_GET_PINPAD_INFORMATIONS() returned wrong number
8115
on iPP3XX
8162 Inter UC evolution

3.1.2. System Thunder (IPP3XX)

Update of the issue
Limit energy consumed by buzzer on IPP3xx.
To be able to play different frequencies on buzzer we define two mode:
TFU4841
1) power full mode (100dcb), you need to use the parameters:
6738 and
div:0x00 dutycycle=0x2300 and period= 0x2800 (dutycycle from 0x2300 to
TFU4955
0x2800)
2) standard mode, you are able to play all frequencies but for energy reason,
the operating system limits the duty cycle from 95% to 100% of the period.

3.1.3. System Thunder III (ISC)

7637 On iSC350, there was a transfer problem with LLT (blank screen)
7733 TFU 4833 Correction of ISC350 crashes while running video
7826 Driver Printer SPM now managed on ISC
7839 Modification of audio initialisation on iSC250
1. If the replaced panel type is different, then the driver will delete current
calibration matrix file.
2. The same problem can occur if we replace panel even with the same type. For
7881 this purpose the new IOCTL function is implemented:
SystemFioctl(SYS_FIOCTL_CALIBRATION_MATRIX_ERASE, NULL);
NOTE: This function can be called only when the touch screen peripheral is
closed.
7896 Now, reset is not necessary after the initialisation and activation of an iSC250
7897 Sometimes iSC250 didn't reboot at reset
7898 There was sometimes a problem to save data in flash in PowerDown mode
8154 TFU5273 LLT didn't work once USB was switched to HID

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

3.1.4. System Thunder (930GCC)

Update of the issue
Colour screen saver on EFT930 now fully functional:
In SCREEN.INI:
6383 TFU3619 [ID_SCREEN]
COLOR_SAVER=/HOST/IMAGE.BMP”
Manager manages BMP, JPG and PNG extension
For PNG and JPG extension, you need to load Images DLL into the terminal.

3.1.5. System IPP2XX

7582 TFU4933 Contactless LEDs are now switched off at start-up
Now, on pinpad not displaying smiley at start up, the messages mock-up,
7707
unauthorised or alert irruption are displayed as soon as the pinpad is starting

3.1.6. System P30

Application can change the number of retransmission of ISO driver, and can
6992
accept card response that are received before minimum delay.
7184 Modification to support EZlink cards
7582 TFU4933 Contactless LEDs are now switched off at startup

3.1.7. System Booster 2 (ML30 / SMART2)

8322 Correction for ETEC8 card on ML30 colour

3.1.8. System Booster 3 (ICT2XX, IPP3XX, iPA2XX)

Application can change the number of retransmission of ISO driver, and can
6992
accept card response that is received before minimum delay.
7184 Modification to support EZlink cards
7582 TFU4933 Contactless LEDs are now switched off at start-up
7582 TFU4933 Contactless LEDs are now switched off at start-up
7724 Now Swipe can read 240bpi cards
7750 TFU4898 Correction for simultaneous activation of LED CAM and SWIPE
8016 TFU5241 The ICT220 had a high failure rate when the card was swiped slow

3.1.9. system Booster 3 (ISC)

If the touch screen driver was opened in "catch press only" mode then the first
7949
sample can be lost for the second and following "opens".

3.1.10. Driver USB CDC

Now DCD event is sent to application task when USB device is removed.
7192
Today, USB_PRESENT is already sent.
7656 Inter UC evolution
Added drives serial signals for COM_SL : DCD, RTS, DTR, CTS.
7810
Hardware flow control can be activated using format()

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

3.1.11. Driver VFS

7515 Management of file systems without partition table

3.1.12. 930B Driver Bluetooth BC02

There was an erratic behaviour of Ethernet connectivity with multiple handsets
7729
on one base (old BC02 model).
Since SDK7.2, it was impossible to download with an intelligent Ethernet
7923
modem.

3.1.13. 930B Driver Bluetooth BC06

7730 There were connection failures in mixed BC02 / BC06 handset configurations.
Since SDK7.2, it was impossible to download with an intelligent Ethernet
7923
modem.

3.1.14. GPRS
7752 Speed-up non-responding GPRS modem detection.
7766 USSD works again as expected.

3.1.15. TS2 LDBG

6594 During remote debugging when there is OEM_exit, now the terminal reboots

3.2. Telium Manager (New version: 59.03)

Following points are delivered in this release.

Information added to know if a terminal was ingetrusted or not (information in

5701
the hardware configuration ticket and padlock displayed by the terminal)
7090 French health domain only : ""Fréquence coupleur externe"" menu added
Information displayed on screen for non printer terminals are now the same
7443
than in the configuration ticket
7559 Adaptation for ISC250
7805 Change of screen saver without reset
7809 Entry point CARD_INSIDE is supported on CAM1 as it is for CAM0
7857 Management of peripherals if there is a KEYBOARD_EVENT and a card is present
7908 TFU4953 Optimization of function Read_Message()
7917 Printing of shortcuts defined by applications
8036 Booster type printed in the hardware configuration ticket
8056 PPP configuration for CDMA was wrong
8080 TFU 5207 _DrawWindow() now supports ISO8859 fonts
8110 Pinpad idle screen was not taken account after adding a pinpad to a terminal
On non contactless terminals in the terminal configuration ticket, the field for
8323
contactless hardware LEDS was "yes"
8409 TFU 5435 Improved documentation for Priority management of Manager Entry Points
8455 Fix automatic start of GPRS problems

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

3.3. CGUI (Version: 01.14) / CGUI tools (Version 01.10)

The Mock-up manager catalogue has to be loaded only to use the Ingedev CGUI Preview tool.

Following points are delivered in this release.

6810 TFU 4168 "Select" tag now displays scrollbar when too much options are present
A new option has been set on the browser :
7044 TFU 4336 WGUI_BROWSER_TEXT_CURSOR_WIDTH : a cursor of 1, 2 or 3px width can
be chosen
The monospace font has been regenerated and all characters have the same
7060 TFU 4346
width
7117 The colour name "grey" has been added. It is the same as the "gray" color.
The monospace font has been regenerated and all characters have the same
7174
width
7309 ARM SDT now supported (previously link problem)
7343 UTF-8 BOM are now correctly handled when present at the beginning of the file

A new action on binding has been added : WGUI_KEY_IGNORE. When a key is

7600
bind with this action no more characters or action are done by the browser
7601 The insertion mode in a text is now correctly handled
Now the object tag is an inline element as the image, was block before, and %
7739
can be used on it
JavaScript documents included in buffer sent via writehtml are now loaded. The
8004 TFU 4672 problem was about charset, with writehtml the expected charset is Unicode and
if no known charset is in the file it assumes a unicode charset too.

Stream was not destroyed in this case and the maximum number of stream is
8018 TFU 5149
10. Now XHR stream are destroyed even when using writehtml
8248 Affecting background colour of a row element with JavaScript now works
5964,
JavaScript alert is not supported
7245
8103 TFU5146 cGUI support for applications for monochrome devices

3.4. Plug-ins Multimedia (Version: 01.06)

Following points are delivered in this release.

7717 MMPlayer: add support for USB CAM

3.5. Plug-ins Signature Capture (Version: 01.07)

Following points are delivered in this release.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

The signature data file can not be accessed until the terminal is rebooted in a
7557
particular scenario.
7846 Correction to avoid the memory overlaps with DLL AXIS for RPO1.

3.6. DLL Security (Version: 03.15)

Following points are delivered in this release.

7445 Added SEC_LoadKey for TLV_TYPE_KTDES_24

7446 Added KCV TDES Key 24 bytes
7972 Added TDES Dukpt light in the scheme TLV TDES DUKPT standard

3.7. DLL Hardware (Version: 02.38)

No evolution.

3.8. Schemes
No evolution of schemes: version is 03.06.
No evolution of TLV schemes: version is 01.16.

3.9. Pack IP (Version: 03.07)

Following points are delivered in this release.

7503 TFU4732 SSL documentation

7540 TFU4737 SSL documentation
7202 TFU4510 Added standard socket defines

3.10. Link Layer (New version: 03.16)

Following points are delivered in this release.

Printing of the version on the ticket is now optional (see FT7475 = TFU3970 and
7817
TFU4729)
Fix problem of temporary state (400ms) while connecting using an unknown
6433 TFU3349
APN
4237 BT Terminal on non-BT base: association to use the modem through IR
8181 Management of CDMA
8383 TFU5428 Added documentation for IP and GPRS error code of the link layer

3.11. FTP (Version: 01.19)

Following points are delivered in this release.

Increasing the timeout at the signature verification stage (120 seconds instead
8213
of 30 seconds).

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

8366 Management of connexion with COM_EXT

3.12. SSL (Version: 01.53)

Following points are delivered in this release.

6655 It is now possible to manage a SSL communication via a memory area

7936 TFU5045 Added management when calls to DLL functions if DLL is not loaded
8005 TFU5132 OID managed by DLL SLL instead of NID
8142 TFU5246 SSL_New() now returns SSL_ENOENT when file names are invalid

3.13. AVL (Version: 01.09)

AVL stands for Added Value Libraries.
No evolution.

3.14. SDK functionalities

Following points are delivered in this release.

8296 SDK_TELIUM.chm compatibility with IngeDev

Link to elements in the .CHM file are now to the function (previously at the
8148
beginning of the page)

3.15. Fonts (Version: 01.09)

No evolution.

4. Deprecated APIs
Due to evolution of product ranges or software, some functions become sometimes obsolete.
The deprecated functions are now grouped in the file deprecated.h. They will be removed from the SDK
in the future.
We deeply advise you to clean your code by applying the new way described in the help file as soon as
functions become obsoletes.
Nevertheless, if you want to continue to use these functions, it is possible by adding deprecated.h and,
according the information in the help file, add a compilation option. If you don’t follow that, there will
be a warning during the compilation.

4.1. Changes between SDK7.2 and SDK7.4

No external function or structure becomes obsolete.

4.2. Changes before SDK7.2

Here is the list of functions which have been declared obsolete before this SDK and added to
deprecated.h:

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

InitModeGraphic();
All Telium Manager functions of type void XXXlib_open (void);
int InitSysPpad (int);
int InitDLLSaisiePpad (void);
int is_loaded(NO_SEGMENT i);
void ET_Idf_seq (T_VERSION version,NO_SEGMENT *noseg,CHECKSUM *nochecksum);
void ET_Identifier_seq (int noappli);
void USQ_Aff_montant (unsigned long * montant ,S_MONEY * devise);
int PPS_SendClearKeyCommand (unsigned char *Domain);
unsigned char PSQ_Double90_cle ( void );

5. Version of components in the previous SDKs

The following table compiles the versions of modules packaged in the previous versions of the SDK.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Plug-in Multimedia
Plug-in Signature
Telium Manager

Telium System

DLL Hardware

TLV Schemes
DLL Security

cGUI tools

Simulator
Link layer
Schemes

DLL FTP

Capture
DLL SSL
Pack IP

cGUI
Font
AVL
SDK

6.5 54.01 08.33 3.09 2.31 3.06 1.12 3.10 3.05 1.17 1.47 1.05 1.05 (2) 2.05

6.5.1 54.02 08.34 3.10 2.32 3.06 1.12 3.10 3.05 1.17 1.48 1.07 1.09 1.6.1 2.05
6.5.2 54.03 08.34 3.10 2.32 3.06 1.12 3.10 3.05 1.17 1.48 1.07 1.09 1.6.1 2.05
6.5.3 54.03 08.35 3.10 2.32 3.06 1.12 3.10 3.05 1.17 1.48 1.07 1.09 1.6.1 2.05
6.6 55.00 08.44 3.10 2.32 3.06 1.12 3.10 3.05 1.17 1.48 1.07 1.09 1.07 1.01 2.06
7.1 56.00 09.00 3.11 2.35 3.06 1.16 3.10 3.05 1.17 1.48 1.08 1.09 1.11 1.10 1.03 1.04 2.07

7.2 57.01 09.16 3.11 (1) 2.37 3.06 1.16 3.13 3.06 1.17 1.48 1.09 1.09 1.12 1.10 1.05 1.05 2.07

7.2.1 57.02 09.20 3.12 2.38 3.06 1.16 3.13 3.06 1.17 1.48 1.09 1.09 1.12 1.10 1.05 1.05 2.07
7.3 58.00 09.30 3.12 2.38 3.06 1.16 3.14 3.06 1.17 1.48 1.09 1.09 1.12 1.10 1.05 1.05 2.07
7.3.1 58.01 09.31 3.12 2.38 3.06 1.16 3.14 3.06 1.17 1.48 1.09 1.09 1.12 1.10 1.05 1.05 2.07
7.3.2 58.04 09.31 3.12 2.38 3.06 1.16 3.14 3.06 1.17 1.48 1.09 1.09 1.12 1.10 1.05 1.05 2.07

(1): Version 3.12 for CTAP configuration

(2): Version 1.06 for ISO1 fonts

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

SDK7.3.2 TECHNICAL INFORMATION BULLETIN

1. Standard development platforms

1.1. Telium 1
The following terminals are compatible with this SDK release:

EFT30

EFT SMART

TWIN

ML30

SMART2

EFT930 (wireless terminal)

EFT930 BL2 (wireless terminal)

1.2. Telium 2
The following terminals are compatible with this SDK release:

iCT220, iCT250

SPM (iPA280)

iPP320, iPP350

iSC350
iSC250 is provided in this release for development only.

1.3. Pinpads
This SDK is compatible with these products:

P30, P30 Contactless

PP30S

PPC30

PPR30

iPP220, iPP250
iPP3XX as emulation of a P30 is provided in this release for development purpose only (function
download is not available).

2. Main evolutions from SDK 7.3.1 Version

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

All issues solved are in paragraph 2.11 : EFT930 embedding 8Mo of flash
It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is provided:
EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please contact your R&D
Regional Interface for more information.
Issues solved in this release.

2.1. Telium Manager

Now, CAM0 is opened at startup of manager only:
1) on UCM (UCM_Behaviour),
2) On Health POS (SECUR application present).

New function: clrscr() to clear display and force refresh on Color Screen.
Screen will be updated after call of PaintGraphics() function.

Reset of the pinpad solved.

3. Highlighted points
3.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level of
communication of sensitive data from the Secure Payment Module (SPM) to the external world. The PDA
part of the product has to be considered as the external world. The reason of this restriction is that the
scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the iPA280
product as a whole.

The restriction forbids communicating:

Any APDU command response
Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the smartcard.
The restriction imposed by PCI SSC does is not limited to banking cards. Direct communication to other types
of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces. It is
for sure possible to address communication by using lower level functionalities. This must not be used to
circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and PDA
parts of the device. The PDA can be used for merchant application only (i.e. advertising, product selection).

3.2. Contactless
For the contactless functionality, you must use at least the Add-on “Contactless” version 3.2 (new
architecture) and 2.12 (old architecture).
For IPP2XX and IPP3XX, use version equal or upper to 3.4 for new architecture. These terminals are not
supported by old architecture (add-on 2.x).

3.3. UCM
You have to use at least add-on UCM version 2.5.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

3.4. Functions XXX_libopen()

Due to the XXX_libopen() functions which are now deprecated, on Ingedev version lower or equal to 7.4.0.7,
there are warnings when this SDK if used with a project created by a “New Telium Project”. You have to add
the compilation option _DEPRECATED_SDK71_ to remove the warnings.

3.5. Binaries having a size multiple of 1024 bytes (Telium 1 terminals)

With the SDKs 6.4.X, 6.5.x and 6.6, it was not possible to download binaries having a size multiple of
1024 bytes before signature. Message is "Bad signature". To avoid loading problem on these SDK, you
have to check that the size of your generated application, without signature, is not a multiple of 1024
bytes. (Size of application – 676) must not be a multiple of 1024.

3.6. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a system
which not manages directories (catalogue XXX.mYY).

3.7. Service numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.

3.8. EFT930 embedding 8Mo of flash

It is possible to use this SDK on EFT930 which has only 8 Mo of flash but you may need some adjustments.
Please contact your R&D Regional Interface for more information.

4. Issues solved in this release by component

4.1. Telium System (New version: 9.31)
No evolution.

4.2. Pack Manager (New version: 58.04)

Following points are delivered in this release.

Now, CAM0 is opened at startup of manager only:

7855 TFU4996 1) on UCM (UCM_Behaviour)
2) On Health POS (SECUR application present)

New function: clrscr() to clear display and force refresh on Color Screen.
7937
Screen will be updated after call of PaintGraphics() function

Reset during the association of an Ingetrusted pinpad with an Ingetrusted terminal

8007 solved
Reset when calling to function TransferToBooster() with empty Pin zone solved

8032 TFU5145 There was a reset after a call to InitContexteGraphique ()

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

4.3. CGUI (Version: 01.12) / CGUI tools (Version 01.10)

No evolution.
The Mock-up manager catalogue has to be loaded only to use the Ingedev CGUI Preview tool.

4.4. Plug-ins Multimedia (Version: 01.05)

No evolution.

4.5. Plug-ins Signature Capture (Version: 01.05)

No evolution.

4.6. DLL Security (Version: 03.12)

No evolution.

4.7. DLL Hardware (Version: 02.38)

No evolution.

4.8. DLL Pinpad (New version: 05.00)

No evolution.

4.9. Schemes
No evolution of schemes: version is 03.06.
No evolution of TLV schemes: version is 01.16.

4.10. Pack IP (Version: 03.06)

No evolution.

4.11. Link Layer (New version: 03.14)

No evolution.

4.12. FTP (Version: 01.17)

No evolution.

4.13. SSL (Version: 01.48)

No evolution.

4.14. AVL (Version: 01.09)

AVL stands for Added Value Libraries.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

No evolution.

4.15. SDK functionalities

No evolution.

4.16. Fonts (Version: 01.09)

No evolution.

4.17. Simulator (Version: 02.07)

No evolution.

5. Deprecated APIs
Due to evolution of product ranges or software, some functions become sometimes obsolete.
The deprecated functions are now grouped in the file deprecated.h. They will be removed from the SDK in
the future.
We deeply advise you to clean your code by applying the new way described in the help file as soon as
functions become obsoletes.
Nevertheless, if you want to continue to use these functions, it is possible by adding deprecated.h and,
according the information in the help file, add a compilation option. If you don’t follow that, there will be a
warning during the compilation.

5.1. Changes between SDK7.2 and SDK7.3.2

No external function or structure becomes obsolete.

5.2. Changes before SDK7.2

Here is the list of functions which have been declared obsolete before this SDK and added to deprecated.h:

InitModeGraphic();
All Telium Manager functions of type void XXXlib_open (void);
int InitSysPpad (int);
int InitDLLSaisiePpad (void);
int is_loaded(NO_SEGMENT i);
void ET_Idf_seq (T_VERSION version,NO_SEGMENT *noseg,CHECKSUM *nochecksum);
void ET_Identifier_seq (int noappli);
void USQ_Aff_montant (unsigned long * montant ,S_MONEY * devise);
int PPS_SendClearKeyCommand (unsigned char *Domain);
unsigned char PSQ_Double90_cle ( void );

6. Version of modules in the previous SDK

This table compiles the versions of modules packaged in the previous versions of the SDK.

For additional information, please contact your R&D Regional Interface

 Technical Information Bulletin

Plug-in Multimedia
Plug-in Signature
DLL Hardware

TLV Schemes
DLL Security

cGUI tools

Simulator
Link layer
Manager

Schemes

DLL FTP

Capture
DLL SSL
System

Pack IP

cGUI
Font
AVL
SDK

6.5 54.01 08.33 3.09 2.31 3.06 1.12 3.10 3.05 1.17 1.47 1.05 1.05 (2) 2.05

6.5.1 54.02 08.34 3.10 2.32 3.06 1.12 3.10 3.05 1.17 1.48 1.07 1.09 1.6.1 2.05
6.5.2 54.03 08.34 3.10 2.32 3.06 1.12 3.10 3.05 1.17 1.48 1.07 1.09 1.6.1 2.05
6.5.3 54.03 08.35 3.10 2.32 3.06 1.12 3.10 3.05 1.17 1.48 1.07 1.09 1.6.1 2.05
6.6 55.00 08.44 3.10 2.32 3.06 1.12 3.10 3.05 1.17 1.48 1.07 1.09 1.07 1.01 2.06
7.1 56.00 09.00 3.11 2.35 3.06 1.16 3.10 3.05 1.17 1.48 1.08 1.09 1.11 1.10 1.03 1.04 2.07

7.2 57.01 09.16 3.11 (1) 2.37 3.06 1.16 3.13 3.06 1.17 1.48 1.09 1.09 1.12 1.10 1.05 1.05 2.07

7.2.1 57.02 09.20 3.12 2.38 3.06 1.16 3.13 3.06 1.17 1.48 1.09 1.09 1.12 1.10 1.05 1.05 2.07
7.3 58.00 09.30 3.12 2.38 3.06 1.16 3.14 3.06 1.17 1.48 1.09 1.09 1.12 1.10 1.05 1.05 2.07
7.3.1 58.01 09.31 3.12 2.38 3.06 1.16 3.14 3.06 1.17 1.48 1.09 1.09 1.12 1.10 1.05 1.05 2.07
7.3.2 58.04 09.31 3.12 2.38 3.06 1.16 3.14 3.06 1.17 1.48 1.09 1.09 1.12 1.10 1.05 1.05 2.07

(1) : Version 3.12 for CTAP configuration

(2) : Version 1.06 for ISO1 fonts

For additional information, please contact your R&D Regional Interface

SDK7.3.1 TECHNICAL INFORMATION BULLETIN

1. Standard development platforms

1.1. Telium 1
The following terminals are compatible with this SDK release:

EFT30

EFT SMART

TWIN

ML30

SMART2

EFT930 (wireless terminal)

EFT930 BL2 (wireless terminal)

1.2. Telium 2
The following terminals are compatible with this SDK release:

iCT220, iCT250

SPM (iPA280)

iPP320, iPP350

iSC350
iSC250 is provided in this release for development only.

1.3. Pinpads
This SDK is compatible with these products:

P30, P30 Contactless

PP30S

PPC30

PPR30

iPP220, iPP250

iPP3XX as a pinpad (emulation of a P30). Function download is not available.

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 153 / 167
Please check document validity before using
2. Main evolutions from SDK 7.3 Version

All issues solved are in paragraph 2.11 : EFT930 embedding 8Mo of flash
It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.
Issues solved in this release.

2.1. Telium System

PP30 back in the release: it was not working on SDK 7.3

2.2. Telium Manager

In some conditions (see below): in case of a wrong track reading, the contactless field is cut for
the second try. A parameter allows to not cut the field,

For French domain only : ITP is now correct for IPP3XX,

PSQ_Get_Cless_Capabilities() returns 0 if function doesn’t exist.

3. Highlighted points
3.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

The restriction forbids communicating:

Any APDU command response
Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC does is not limited to banking cards. Direct
communication to other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection).

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 154 /
167
Please check document validity before using
 3.2. Contactless
For the contactless functionality, you must use at least the Add-on “Contactless” version 3.2 (new
architecture) and 2.12 (old architecture).
For IPP2XX and IPP3XX, use version equal or upper to 3.4 for new architecture. These terminals are not
supported by old architecture (add-on 2.x).

3.3. UCM
You have to use at least add-on UCM version 2.5.

3.4. Functions XXX_libopen()

Due to the XXX_libopen() functions which are now deprecated, on Ingedev version lower or equal to
7.4.0.7, there are warnings when this SDK if used with a project created by a “New Telium Project”. You
have to add the compilation option _DEPRECATED_SDK71_ to remove the warnings.

3.5. Binaries having a size multiple of 1024 bytes (Telium 1 terminals)

With the SDKs 6.4.X, 6.5.x and 6.6, it was not possible to download binaries having a size multiple
of 1024 bytes before signature. Message is "Bad signature". To avoid loading problem on these
SDK, you have to check that the size of your generated application, without signature, is not a
multiple of 1024 bytes. (Size of application – 676) must not be a multiple of 1024.

3.6. DIR system version downgrade

It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

3.7. Service numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.

3.8. EFT930 embedding 8Mo of flash

It is possible to use this SDK on EFT930 which has only 8 Mo of flash but you may need some
adjustments. Please contact your R&D Regional Interface for more information.

4. Issues solved in this release by component

4.1. Telium System (New version: 9.31)
Following points are delivered in this release.

7448 PP30 was not working on SDK 7.3

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 155 / 167
Please check document validity before using
 4.2. Pack Manager (New version: 58.01)
Following points are delivered in this release.

French domain only:

6819
PSQ_Get_Cless_Capabilities() returns 0 if function doesn’t exist to avoid reset

Now, in the following conditions :

- Implicit selection
- Proceed entry before presentation of card
7678
- Contactless is an internal module of the terminal
(TFU4916)
Then:
- By default, in case of a wrong track reading, the contactless field is cut for the second try
- A parameter allows to not cut the field

7889 ISDN was not in English in the Telium Manager menu

7934 For French domain only : ITP was not correct on IPP3XX
7891 PSQ_Donner_format_date( ) documentation improvement
(TFU5021)
6598, 7918 Miscellaneous documentation improvements

4.3. CGUI (Version: 01.12) / CGUI tools (Version 01.10)

No evolution.
The Mock-up manager catalogue has to be loaded only to use the Ingedev CGUI Preview tool.

4.4. Plug-ins Multimedia (Version: 01.05)

No evolution.

4.5. Plug-ins Signature Capture (Version: 01.05)

No evolution.

4.6. DLL Security (Version: 03.12)

No evolution.

4.7. DLL Hardware (Version: 02.38)

No evolution.

4.8. DLL Pinpad (New version: 05.00)

No evolution.

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 156 /
167
Please check document validity before using
 4.9. Schemes
No evolution of schemes: version is 03.06.
No evolution of TLV schemes: version is 01.16.

4.10. Pack IP (Version: 03.06)

No evolution.

4.11. Link Layer (New version: 03.14)

No evolution.

4.12. FTP (Version: 01.17)

No evolution.

4.13. SSL (Version: 01.48)

No evolution.

4.14. AVL (Version: 01.09)

AVL stands for Added Value Libraries.
No evolution.

4.15. SDK
No evolution.

4.16. Fonts (Version: 01.09)

No evolution.

4.17. Simulator (Version: 02.07)

No evolution.

5. Deprecated APIs
Due to evolution of product ranges or software, some functions become sometimes obsolete.
The deprecated functions are now grouped in the file deprecated.h. They will be removed from the SDK
in the future.
We deeply advise you to clean your code by applying the new way described in the help file as soon as
functions become obsoletes.

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 157 / 167
Please check document validity before using
Nevertheless, if you want to continue to use these functions, it is possible by adding deprecated.h and,
according the information in the help file, add a compilation option. If you don’t follow that, there will
be a warning during the compilation.

5.1. Changes between SDK7.2 and SDK7.3.1

No external function or structure becomes obsolete.

5.2. Changes before SDK7.2

Here is the list of functions which have been declared obsolete before this SDK and added to
deprecated.h:

InitModeGraphic();
All Telium Manager functions of type void XXXlib_open (void);
int InitSysPpad (int);
int InitDLLSaisiePpad (void);
int is_loaded(NO_SEGMENT i);
void ET_Idf_seq (T_VERSION version,NO_SEGMENT *noseg,CHECKSUM *nochecksum);
void ET_Identifier_seq (int noappli);
void USQ_Aff_montant (unsigned long * montant ,S_MONEY * devise);
int PPS_SendClearKeyCommand (unsigned char *Domain);
unsigned char PSQ_Double90_cle ( void );

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 158 /
167
Please check document validity before using
SDK7.3 TECHNICAL INFORMATION BULLETIN

1. Standard development platforms

1.1. Telium 1
The following terminals are compatible with this SDK release:

EFT30

EFT SMART

TWIN

ML30

SMART2

EFT930 (wireless terminal)

EFT930 BL2 (wireless terminal)

1.2. Telium 2
The following terminals are compatible with this SDK release:

iCT220, iCT250

SPM (iPA280)

iPP320, iPP350

iSC350
iSC250 is provided in this release for development only.

1.3. Pinpads
This SDK is compatible with these products:

P30, P30 Contactless

PP30S

PPC30

PPR30

iPP220, iPP250

iPP3XX as a pinpad (emulation of a P30). Function download is not available.
PP30 is not managed by this release.

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 159 /
167
Please check document validity before using
2. Main evolutions from SDK 7.2.1 Version

All issues solved are in paragraph 2.11 : EFT930 embedding 8Mo of flash
It is possible to use this SDK on EFT930 which has only 8 Mo of flash (special system catalogue is
provided: EFT930_8MO_PROD.m31). If you use Ingestate you may need some adjustments: please
contact your R&D Regional Interface for more information.
Issues solved in this release.

2.1. New terminals

iSC250 is provided in this package for development purpose only;

iPP3XX can be used as a pinpad (emulation of a P30). However, function download is not
available in this package.

2.2. Telium System

Add HID protocol for USB Device;

Energy saving features for iPP3XX;

The information on type of contactless configuration works for all terminals;

HISR modem reset solved;

Stack overflow fixed in archiver_diagnostic();

Reading of serial number over USB for French Health Care applications;

Improvement for iSC350.

2.3. Telium Manager

New parameter in MANAGER.PAR for real and virtual operator name;

When ISO1 or ISO3 track was not valid, Telium Manager didn't return the error to the
application;

During the opening of an Ingestate session, it is now possible to enter the TMS ID in BCD.

2.4. Link layer

Link layer not defined as a banking application.

3. Highlighted points
3.1. Restriction for iPA280 and PCI PED 2.x compliance
During the PCI PED 2.x certification of the iPA280 devices, some constraints have been put at the level
of communication of sensitive data from the Secure Payment Module (SPM) to the external world. The
PDA part of the product has to be considered as the external world. The reason of this restriction is that
the scope of the PCI PED evaluation was the SPM, which has a secure Telium architecture, and not the
iPA280 product as a whole.

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 160 /
167
Please check document validity before using
The restriction forbids communicating:
Any APDU command response
Any cardholder data (i.e. ISO tracks 1 & 2 and their EMV counterpart).
It is also forbidden to receive APDU command queries from the external and to relay them to the
smartcard. The restriction imposed by PCI SSC does is not limited to banking cards. Direct
communication to other types of cards (e.g. loyalty) is not allowed.

The communication APIs to establish communication between SPM and PDA propose some interfaces.
It is for sure possible to address communication by using lower level functionalities. This must not be
used to circumvent the protocol restrictions for communication.

Since cardholder data must remain within the SPM, the implication of this restriction is that payment
applications have to be executed in the SPM and can not be based on a split design between SPM and
PDA parts of the device. The PDA can be used for merchant application only (i.e. advertising, product
selection).

3.2. Contactless
For the contactless functionality, you must use at least the Add-on “Contactless” version 3.2 (new
architecture) and 2.12 (old architecture).
For IPP2XX and IPP3XX, use version equal or upper to 3.4 for new architecture. These terminals are not
supported by old architecture (add-on 2.x).

3.3. PP30
PP30 is not managed by this release.

3.4. UCM
You have to use at least add-on UCM version 2.5.

3.5. Functions XXX_libopen()

Due to the XXX_libopen() functions which are now deprecated, on Ingedev version lower or equal to
7.4.0.7, there are warnings when this SDK if used with a project created by a “New Telium Project”. You
have to add the compilation option _DEPRECATED_SDK71_ to remove the warnings.

3.6. Binaries having a size multiple of 1024 bytes (Telium 1 terminals)

With the SDKs 6.4.X, 6.5.x and 6.6, it was not possible to download binaries having a size multiple
of 1024 bytes before signature. Message is "Bad signature". To avoid loading problem on these
SDK, you have to check that the size of your generated application, without signature, is not a
multiple of 1024 bytes. (Size of application – 676) must not be a multiple of 1024.

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 161 / 167
Please check document validity before using
 3.7. DIR system version downgrade
It is not possible to downgrade from a system managing directories (catalogue XXX_DIR.mYY) to a
system which not manages directories (catalogue XXX.mYY).

3.8. Service numbers

Service numbers from 1 to 100 and from 7680 à 8191 are reserved for Ingenico internal use.

3.9. EFT930 embedding 8Mo of flash

It is not possible to use this SDK on EFT930 which has only 8 Mo of flash.

4. Issues solved in this release by component

4.1. Telium System (New version: 9.30)
Following points are delivered in this release.

Thunder 1 and 2
5244 Twin 30 didn't work with LLT 4.2.3

6833 Serial number read on USB for French Health Care applications
Added information "configuration Cless present or not" (modification for IPP3XX on which Cless is
6969
an pluggable module)
7024 It is now possible to replace a file in the disk Host with LLT in command mode

7168 dllmalloc improved for big buffers

7246 HISR modem reset solved

7250 Stack overflow fixed in archiver_diagnostic

7271 Add HID protocol for USB Device

7425
COM2 management of flow control added
(TFU4658)
7448
COM ttestall or status didn't work correctly at 19200
(TFU4634)
7542 Optimization of IAPP transfer delay

System P30
6778 There were reset of CAD30 Tool or CAD30 UPP when connected with a pinpad on USB

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 162 /
167
Please check document validity before using
 7079 Booster only terminal are now supported on Linux

System PP30S
6573 To save memory system fonts (displayng Mock-up, unauthorized, ...) are now only in ROM

6778 There were reset of CAD30 Tool or CAD30 UPP when connected with a pinpad on USB

7079 Booster only terminal are now supported on Linux

System IPP2XX
6778 There were reset of CAD30 Tool or CAD30 UPP when connected with a pinpad on USB

7079 Booster only terminal are now supported on Linux

7114 Optimisations of Mifare driver

7116 Optimisations of Calypso driver

7128 Signature Check From Scheme and Shared Area Managed in the Booster

7308 Optimisations of Calypso driver

At startup, press key F1 to display an IHM that allows setting IUC link (USB or RS232).
7333
USB IUC link is selected by default.
7341 Menu added to erase trace files on 2 lines display pinpads

7550 IPP2XX backlight color bug fixed

Booster 2 930 BL2

6525 LLT connexion impossible fixed

7114 Optimisations of Mifare driver

930 Wireless: Driver BT BC06 Portable and base

5304 Support of OPEN_BT

SMART2 / ML30
6272
Possibility added to do an automatic IFS request in ISO7816 mode
(TFU3596)

Booster III ICT2XX /iPP3XX/ IPA280

6272
Possibility added to do an automatic IFS request in ISO7816 mode
(TFU3596)
7128 Signature Check From Scheme and Shared Area Managed in the Booster

7341 Menu added to erase trace files on 2 lines display pinpads

Driver Modem 930

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 163 /
167
Please check document validity before using
 7298 V22FC connexion delay improved
7082 / 7376 /
Authorization call failure on RTC lines fixed
4977

French healthcare
6833 Reading of serial number over USB for French Health Care applications

IPP3XX
6565 Backlights of keyboard and displayed are now independent on IPP3XX for energy savings purpose

6738 Limit energy used by buzzer on IPP3xx

P30 emulation of IPP3XX

7337 / 7338 / 7339 /
Added inter-UC link : it will allows to connect a "Thunder" pinpad with a Telium product
7340 / 7353 / 7364

CAD30 CBS and CAD30 CBS VM

6784 Reset in a very specific context, fixed

CAD30-UCR (MR40)
7767 Driver Cless B' added in MR40 system

6578 Improve robustness of CLESS driver by checking RC531 state if there is no interruption.

6778 Pinpad resets on USB pinpad connected to UCM or UCR fixed

iSC350 / iSC250 Booster 3

7685 Touch Screen Driver: implementation for RP01

7736 New command for Touch Screen: set sensitivity

iSC350 / iSC250 Thunder 3

7270 Add HID protocol for USB Device

7434 Stereo reading improvement

7546 Change configuration backlight from 25% to 100% by default

7661 USB Host: add WIFI & improve CAM.

7686 Touch Screen Driver: implementation for RP01

7717 MMPlayer: add support for usb CAM

7735 Touch Screen: New IOCTL commands: Sensitivity Adjustment

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 164 /
167
Please check document validity before using
 4.2. Pack Manager (New version: 58.00)
Following points are delivered in this release.

5942
Download time gauge removed
(TFU3573)
New parameter in MANAGER.PAR for real and virtual operator name.
TAG 020629
6920
0 = Display Provider Name if known into header (default)
1 = Force Display Network Name into header
Health domain only:
7091
Update of the names of products returned by OS_GetIdLecteur()
7530 In hardware configuration menu name of twin32 was wrong

7549 During the opening of an Ingestate session, it is now possible to enter the TMS ID in BCD
Adaptation for ISC250 product regarding:
- Colour compatible mode
7559 - Header
- Foot
- CGUI
7560
PSQ_lire_param() et PSQ_ecrire_param() evolutions
(TFU4660)
7577 It was not possible to remove software which have a 9 digits name
7618
When ISO1 or ISO3 track was not valid, Telium Manager didn't return the error to the application.
(TFU4394)
7633 Menu Pinpad removed from ISC350

7635 Key '-' is now managed in the maintenance menu of the iSC350

7559 ISC250 evolutions in Telium Manager

7665
Add Yellow Func Key (Corr Key) support in PPS_Fct_Entry()
(TFU4884)
6383 Colour screen saver on EFT930 (Telium manager part of the correction only, fully functional in the next
(TFU3619) SDK)
6940
wG_List_Entry title was displayed incorrectly in extended graphical display
(TFU4210)
7666
Stop_Entry didn’t stop wG_List_Entry on ML30CC
(TFU4812)
7673 On a configuration "ICT220 + P30 Cless", the message inviting to insert the card was not displayed
7678 When contactless is activated, if the magnetic card reading is wrong, the contactless module is cut for the
(TFU4916) second try
7757 Priority levels added in screen.ini

4.3. CGUI (Version: 01.12) / CGUI tools (Version 01.10)

No evolution.

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 165 /
167
Please check document validity before using
The Mock-up manager catalogue has to be loaded only to use the Ingedev CGUI Preview tool.

4.4. Plug-ins Multimedia (Version: 01.05)

No evolution.

4.5. Plug-ins Signature Capture (Version: 01.05)

No evolution.

4.6. DLL Security (Version: 03.12)

No evolution.

4.7. DLL Hardware (Version: 02.38)

No evolution.

4.8. DLL Pinpad (New version: 05.00)

7334 DLL pinpad can now manage IPP3XX as a pinpad (P30 emulation)

4.9. Schemes
No evolution of schemes: version is 03.06.
No evolution of TLV schemes: version is 01.16.

4.10. Pack IP (Version: 03.06)

No evolution.

4.11. Link Layer (New version: 03.14)

7372 Link layer not defined as a banking application (use of entry point
(TFU4667) GIVE_YOUR_SPECIFIC_CONTEXT)

4.12. FTP (Version: 01.17)

No evolution.

4.13. SSL (Version: 01.48)

7419 It was not possible to include "SSL_.h" in a C++ source file

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 166 /
167
Please check document validity before using
 4.14. AVL (Version: 01.09)
AVL stands for Added Value Libraries.
No evolution.

4.15. SDK
7517 Warning is now popping up at the beginning of the setup if the package is already installed. User
can stop or continue the installation.

7811 List of USB peripherals managed on Telium, added in the documentation

4.16. Fonts (Version: 01.09)

No evolution.

4.17. Simulator (Version: 02.07)

No evolution.

5. Deprecated APIs
Due to evolution of product ranges or software, some functions become sometimes obsolete.
The deprecated functions are now grouped in the file deprecated.h. They will be removed from the SDK
in the future.
We deeply advise you to clean your code by applying the new way described in the help file as soon as
functions become obsoletes.
Nevertheless, if you want to continue to use these functions, it is possible by adding deprecated.h and,
according the information in the help file, add a compilation option. If you don’t follow that, there will
be a warning during the compilation.

5.1. Changes between SDK7.2 and SDK7.3

No external function or structure becomes obsolete.

5.2. Changes before this SDK

Here is the list of functions which have been declared obsolete before this SDK and added to
deprecated.h:

InitModeGraphic();
All Telium Manager functions of type void XXXlib_open (void);
int InitSysPpad (int);
int InitDLLSaisiePpad (void);
int is_loaded(NO_SEGMENT i);
void ET_Idf_seq (T_VERSION version,NO_SEGMENT *noseg,CHECKSUM *nochecksum);

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 167 /
167
Please check document validity before using
void ET_Identifier_seq (int noappli);
void USQ_Aff_montant (unsigned long * montant ,S_MONEY * devise);
int PPS_SendClearKeyCommand (unsigned char *Domain);
unsigned char PSQ_Double90_cle ( void );

Ingenico document - Reproduction or disclosure prohibited without written authorization Page 168 /
167
Please check document validity before using