Card SDK requirements and interoperability

This article includes updates for Nexus Card SDK 6.3.

This article contains requirements and interoperability data for Nexus Card SDK.

Requirements

Supported Windows platforms for client PC:

Windows 10 (32 and 64 bit)
Windows 11

It is recommended to fully update Windows before installing Card SDK.

Outdated Windows platforms

As soon as Microsoft announces End of Support for a certain Windows platform, Nexus will no longer support this specific Windows version. Therefore that Windows version will be removed from the officially supported platforms.

Nevertheless, Nexus typically does not remove any functionalities in the software (for example drivers) as long as there is no technical need to do this. So, customers can still use Nexus Card SDK on outdated environments at their own responsibility and risk. The software will still work in most of the cases, but Nexus will no longer do tests and bug fixing related to outdated Windows platforms and will also no longer support these setups.

64-bit operating system

Both the applications of Nexus Card SDK and the ActiveX components run as 32-bit applications, even if the environment is a 64-bit operating system (which is automatically recognized by the Windows operating system).

Therefore, all the drivers required for the connection and operation of external devices (for example, encoders, scanners, printers, etc.) have to support 32-bit mode, that is, they must be accessible from a 32-bit application.
Note: The drivers included in the program package (for example, the dongle driver) support 32/64 bit mode by default.

Disk space

Disk space required:

Approximately 150 MB

PKI clients

To manage certificates on cards, for example on admin client, card production client and end user client, the following requirement applies:

Java 11 must be installed

The platform architecture of middleware must match the Java platform architecture, that is, if 32-bit middleware is used, a 32-bit Java is required, for 64-bit middleware clients, the 64-bit Java is necessary.

Interoperability

Supported cameras in Card SDK

This section describes which cameras are supported by Nexus Card SDK.

For Windows 11 there are no supported drivers available yet.

For information about outdated Windows platforms, see "Requirements" in Card SDK requirements and interoperability.

The Card SDK Capture dialog supports the following cameras:

Canon EOS digital cameras

Other EOS models than the ones in the table are not supported or do not have a ‘LiveView’ function.

Camera type and name

Connection type

Live View

Software
controlled

Windows

S-Video

USB

FireWire

7
32+64 Bit

8
32+64 Bit

10
32+64 Bit

11
32+64 Bit

EOS 2000D,
EOS 4000D,
EOS 1300D,
EOS 1200D/Rebel T5,
EOS 1100D/Rebel T3,
EOS 1000D/Rebel XS,
EOS 750D/Rebel T6i,
EOS 760D/Rebel T6s,
EOS 700D/Rebel T5i,
EOS 670D,
EOS 650D/Rebel T4i,
EOS 600D/Rebel T3i,
EOS 550D/Rebel T2i,
EOS 500D/Rebel T1i,
EOS 100D/Rebel SL1,
EOS 70D, EOS 60D, EOS 60Da,
EOS 50D, EOS 40D, EOS 7D,
EOS 5D Mark III, EOS-1D Mark IV,
EOS-1D X, EOS-1D Mark III,
EOS-1Ds Mark III

-

EOS 450D/Rebel XSi

-

(32 Bit)

-

Cameras with TWAIN-Treiber

Camera type and name	Connection type			Live View	Software controlled	Windows
Camera type and name	S-Video	USB	FireWire	Live View	Software controlled	7 32+64 Bit	8 32+64 Bit	10 32+64 Bit	11 32+64 Bit
All with TWAIN-Treiber	-		-	^{(Depending on the model} ^{and the TWAIN/VIA/WDM} ^{driver involved)}	-

Webcams via WDM

Camera type and name	Connection type			Live View	Software controlled	Windows
Camera type and name	S-Video	USB	FireWire	Live View	Software controlled	7 32+64 Bit	8 32+64 Bit	10 32+64 Bit	11 32+64 Bit
All webcams (integrated or USB)

Supported card printers in Card SDK

This section includes updates for Nexus Card SDK 6.2.

This section describes which card printers with integrated encoding are supported by Nexus Card SDK.

For more information, see Card SDK requirements and interoperability.

Supported ID card printer models are listed below, marked with a (subject to the availability of the drivers for the respective Windows versions).

HID Fargo

Printer name / Manufacturer	Proximity encodings						Contact chip		Print			Supported OS
	Proximity encodings						Contact chip		DPI			Supported OS
	LEGIC	MIFARE	HITAG, EM	Proxif	my-d	UHF	Memory	Smart card	300	600	UV	Windows 10 32- and 64-bit	Windows 11	Info
DTC4250e				-	-	-	-			-	-
DTC4500e				-	-	-	-			-	-
HDP5000				-	-	-	-			-
HDP5600				-	-	-	-				-		-	EOL
HDP6600				-	-	-	-				-
HDP8500				-	-	-	-			-	-		Driver available (untested)	EOL

Matica Group

Printer name / Manufacturer	Magnet	Proximity encodings						Contact chip		DPI		Supported OS
Printer name / Manufacturer	Magnet	LEGIC	MIFARE	HITAG, EM	Proxif	my-d	UHF	Memory	Smart card	300	600	Windows 10 32- and 64-bit	Windows 11	Info
XID 8300 (*2)					-	-	-				-
XID 8600 (*2)
XID 93xx (*2)										-	-	-	-	EOL
XID 5xxie										-	-	-	-	EOL
DCP 360i							-			-	-	-	-	EOL

Magicard

Printer name / Manufacturer	Magnet	Proximity encodings						Contact chip		DPI		Supported OS
Printer name / Manufacturer	Magnet	LEGIC	MIFARE	HITAG, EM	Proxif	my-d	UHF	Memory	Smart card	300	600	Windows 10 32- and 64-bit	Windows 11	Info
Magicard 600	-				-	-	-	-					Driver available (untested)
Magicard RIO Tango 2e							-	-	-	-	-	-	-	EOL
Magicard Rio Pro						-	-			-	-		-	EOL
Magicard Rio Pro 360	-				-	-	-	-		-	-		-	EOL
Magicard Prima 4 (*3)						-	-				-		-	EOL
Magicard Prima 8 (*3)						-	-				⁽⁾		-
Magicard Pronto	-	-	-	-	-	-	-	-	-		-		-

Evolis

Printer name / Manufacturer	Magnet	Proximity encodings						Contact chip		DPI		Supported OS
Printer name / Manufacturer	Magnet	LEGIC	MIFARE	HITAG, EM	Proxif	my-d	UHF	Memory	Smart card	300	600	Windows 10 32- and 64-bit	Windows 11	Info
Evolis Tattoo RW 2	-	-	-	-	-	-	-	-	-		-	Driver available (untested)
Evolis Primacy	-	-	-	-	-	-	-	-	-		-		Driver available (untested)	EOL
Evolis Quantum 2 (*1)	-	-		-	-	-	-	-			-		-
Evolis Primacy 2	-	-		-	-	-	-	-			-

Other

Printer name / Manufacturer	Magnet	Proximity encodings						Contact chip		DPI		Supported OS
Printer name / Manufacturer	Magnet	LEGIC	MIFARE	HITAG, EM	Proxif	my-d	UHF	Memory	Smart card	300	600	Windows 10 32- and 64-bit	Windows 11	Info
Datacard SP55, SP75			-	-	-	-	-	-	-	-	-	-	-	EOL
Datacard SR200, SR300		-	-	-	-	-	-	-	-	-	-	-	-	EOL
Datacard SD-, CD-, SE- Series		-	-	-	-	-	-	-		-	-		Driver available (untested)	will be replaced with DSx Series

(*1) Evolis Quantum 2

Evolis Quantum 2 is only supported with Nexus Card SDK 6.1 and later.

(*2) Driver support

Printers marked with a (*2) use a JVC driver (based on the DNP CX-D80 OEM/H printer) that is no longer valid in terms of signing. The driver might still work, but the signature of the driver is deprecated. This will block the enabling of the WIN11 Memory Integration Feature.

This is a well know issue and needs to be handled by the driver provider/printer manufacturer. Nexus cannot fix this issue. Those printers will still be listed as supported, since the driver was and is still working. But those drivers are not suitable for high security environments.

(*3) Integrated Encoder

Some printers have integrated encoding units from the manufacturer. For specific encoding options with those integrated readers, refer to the manufacturer site.

If possible, Nexus can exchange the encoder in the printer to fulfill a different need for encoding. This needs to be handled separately.

The table above only provides an indication regarding which integration that is possible, this is not necessarily the case with printers directly ordered from the manufacturer.

Supported document or image scanners in Card SDK

Generally, most devices with a 32-bit TWAIN driver for the respective client operating system can be connected as document/image scanners.

Supported encoders in Card SDK

This section is updated for Card SDK 6.2 and describes which encoders that are supported by Nexus Card SDK.

The following encoders are supported:

LEGIC (13.56 MHz)

Encoding methods

Supported encoders

Credentials / Chips, Remarks

Device

Installation module or Component

Connection type

U: USB
S: Serial

LEGIC prime

MIMIU-S
various

MSM 100-S V3.x

MSM 100-S V4.0

SC-2560

SM-4500

S

MIM256, MIM1024 (segmented and unsegmented)

SM-4500, SC-2560 can not support unsegmented media

LEGIC advant LEGIC CTC

various

SC-2560

SM-4500 (for CTC-Chip, LEGIC OS-2000 V7.1 or higher is required)

TWN4 MultiTech 2 LEGIC 45 M-PI (*)

S

MIM256, MIM1024

ATC128-MV210, ATC256-MV210

ATC1024-MV110, ATC512-MP110

ATC2048-MP110,ATC4096-MP310

ATC4096-MP311

AFS4096-JP10

CTC4096-MP410 (only segmented media)

Remark: TWN4 MultiTech 2 LEGIC 45 M-PI

(* ) : The reader contains a SM-4500 Reader-Chip. To support the Legic encoding, the reader must be flashed with the Elatec "transparent Legic Firmware".

MIFARE (13,56 MHz)

Encoding methods	Supported encoders			Credentials / Chips, Remarks
Encoding methods	Device	Installation module or Component	Connection type U: USB S: Serial	Credentials / Chips, Remarks
MIFARE Classic (1K, 4K)	Philips MF RD560/ADA		S	only 1K media
	Elatec TWN4 MIFARE NFC-PI	Elatec TWN4 MIFARE NFC-PI	U	Must be flashed with a PC/SC compatible firmware
	Gemplus GCR680		S	only 1K media
	Gemalto GemEasy332		S
	Gemalto GemEasy-Access332 (new name: GemProx-P2)		S
		Gemalto GemEasyLink332 (new name: GemProx-C2)	S	identical to GemEasyAccess332, but without the housing
	OMNIKEY CardMan 5121	OMNIKEY CardMan 5121 Board	U	Is a dual interface reader: RFID & Smartcard
	OMNIKEY CardMan 5321/5421	OMNIKEY CardMan 5321/5421 Board	U	Is a dual interface reader: RFID & Smartcard
	OMNIKEY CardMan 5x22	OMNIKEY CardMan 5x22	U	RFID
MIFARE DESFire EV1/EV2	OMNIKEY CardMan 5121	OMNIKEY CardMan 5121 Board	U	Is a dual interface reader: RFID & Smartcard
	OMNIKEY CardMan 5321/5421	OMNIKEY CardMan 5321/5421 Board	U	Is a dual interface reader: RFID & Smartcard
	OMNIKEY CardMan 5x22	OMNIKEY CardMan 5x22	U	RFID
	OMNIKEY 5127CK-Mini	OMNIKEY 5127CK-Mini	U	RFID
	Elatec TWN4 MIFARE NFC-PI	Elatec TWN4 MIFARE NFC-PI	U	Must be flashed with a PC/SC compatible firmware
	MFP72, MFP80	MFP72/80	U	Only for non-standard
	REINER SCT cyberJack^® RFID basis		U	Only available as a desktop reader

HITAG (125 kHz)

Encoding methods	Supported encoders			Credentials / Chips, Remarks
Encoding methods	Device	Installation module or Component	Connection type U: USB S: Serial	Credentials / Chips, Remarks
HITAG 1,2	Philips/Mikron HT RM440		S
		Feig OBID ID RW01	S	This reader is only used to encode / read the ID number defined by Feig
	Feig OBID ID RW02		S	This reader is only used to encode / read the ID number defined by Feig
HITAG 1,2,S	Frosch HT RM401		S

Proxif (125 kHz)

Encoding methods

Supported encoders

Credentials / Chips, Remarks

Device

Installation module or Component

Connection type

U: USB
S: Serial

Proxif (HITAG 1)

Philips/Mikron HAT RM440

S

Interflex Proxif Encoder

Interflex Proxif Board

S

HID

Encoding methods	Supported encoders			Credentials / Chips, Remarks
Encoding methods	Device	Installation module or Component	Connection type U: USB S: Serial	Credentials / Chips, Remarks
Prox (125 kHz)	ProxPro 5352A		S	Only for reading HID Prox cards
	RFIDeas pcProx Reader		U	For reading HID Prox cards and Indala Prox
	Elatec TWN4 MIFARE NFC-PI	Elatec TWN4 MIFARE NFC-PI	U	Only for reading HID Prox cards. Must be flashed with a PC/SC compatible firmware.
	Elatec TWN4 MULTITECH 2 LF-P	Elatec TWN4 MULTITECH 2 LF-P	U	Only for reading HID Prox cards. Must be flashed with a PC/SC compatible firmware.

EM (125 kHz)

Encoding methods

Supported encoders

Credentials / Chips, Remarks

Device

Installation module or Component

Connection type

U: USB
S: Serial

EM4001, EM4002,

EM4022, EM4102,

EM4200, Unique,

Q5,e5555

FEIG OBID ID RW 40.30-U

FEIG OBID ID RW 40.30-U (Board)

USB (Virtual COM Port)

Reading the serial number of the transponder chip

EM4102

Elatec TWN4 MIFARE NFC-PI

U

Reading the serial number of the transponder chip. Must be flashed with a PC/SC compatible firmware.

UHF (860-960 MHz)

Encoding methods

Supported encoders

Credentials / Chips

Remarks

Device

Installation module or Component

Connection type

U: USB
S: Serial

UHF EPC Gen2

ThingMagic M5e

ThingMagic M5e-C

U

16/32/48/64/80/96 bits Only Class-1 tags (passive tags)

End of life. This is no longer supported.

Memory chip cards

Encoding methods

Supported encoders

Credentials / Chips, Remarks

Device

Installation module or Component

Connection type

U: USB
S: Serial

Cards with an asynchronous protocol (T=0, T=1);
with a synchronous protocol (2-wire protocol / 3-wire protocol, I²C-Bus);

OMNIKEY B1 CardMan 9010

S

ST14 C 02 (256 bytes)

GFM 2K (256 bytes)

SLE 4418

SLE 4428

Magnetic stripe encoding

Encoding methods

Supported encoders

Credentials / Chips, Remarks

Device

Installation module or Component

Connection type

U: USB
S: Serial

External Devices

Jarltech 1210R
Scanteam 6980
MKL-03/2
Rinas MSL 1233
MKW 01
Universal Magstripe Encoder

S
S
S
S
S
S

Magnetic stripe encoders (LoCo, HiCo)
built into printers

Almost all card printers that conform to ISO 7810 standards

No separate device connection; control through printer interface

Supported encoding methods in Card SDK

This section is valid for Nexus Card SDK 6.0 and later.

This section describes which encoding methods are supported by Nexus Card SDK.

The following ID card encoding methods are supported:

RFID:

LEGIC (prime, advant)
LEGIC Hybrid + CTC (prime+advant)
MIFARE Classic (1K, 4K)
MIFARE DESFire EV1 (optionally with SAM AV1/AV2)
MIFARE DESFire EV2 (optionally with SAM AV3)
MIFARE DESFire EV3 (optionally with SAM AV3)
MIFARE DESFire EV3C (optionally with SAM AV3)
HITAG 1/2/S
Proxif
HID Prox (read only)
EM (read only)
UHF EPC Gen2
iCode SLI

Others:

Magnetic Stripes (all ISO tracks)
NFC Mobile phone with a suitable RFID applet

Integrated encoding of contact chips, LEGIC, MIFARE, and magnetic stripes is possible for a variety of ID card printers. For more information, see Card SDK requirements and interoperability .

Generally, a maximum of 1 RFID encoding position is available inside the card printer. Exception: The FARGO HDP5000 has (with the “Duplex” option) 2 RFID encoding positions. At each position, one of the following encoding devices can be used (if enough space for mounting the device or antenna is available):

RFID combinations with FARGO HDP5000 Duplex:

FARGO HDP5000 Duplex	Device at RFID Pos. 1	Device at RFID Pos. 2	Some of the possible encodings within the same production step and with one card body:
Variant 1	LEGIC encoder	OMNIKEY 5x21	MIFARE classic + LEGIC prime/advant/CTC MIFARE DESFire EV1 (Standard) + LEGIC prime/advant/CTC MIFARE DESFire EV1 (Standard) + LEGIC prime/advant/CTC + Smartcard
Variant 2	MFP80	OMNIKEY 5x21	MIFARE DESFire EV1 (Standard) + MIFARE DESFire EV1 (Non-Standard) MIFARE DESFire EV1 (Standard) + MIFARE DESFire EV1 (Non-Standard) + Smartcard
Variant 3	OMNIKEY 5x21	FEIG OBID	MIFARE DESFire EV1 (Standard) + Reading EM 4105/4200 MIFARE DESFire EV1 (Standard) + Reading EM 4105/4200 + Smartcard
Variant 4	LEGIC encoder	FEIG OBID	LEGIC prime/advant/CTC + Reading EM 4105/4200 LEGIC prime/advant/CTC + Reading EM 4105/4200 + Smartcard
Variant 5	LEGIC encoder	OMNIKEY 5x21 + FEIG OBID	MIFARE classic + LEGIC prime/advant/CTC + Reading EM 4105/4200 MIFARE DESFire (Standard) + LEGIC prime/advant/CTC + Reading EM 4105/4200 MIFARE DESFire (Standard) + LEGIC prime/advant/CTC + Reading EM 4105/4200 + Smartcard

Supported fingerprint scanners in Card SDK

This section describes which fingerprint scanners are supported by Nexus Card SDK.

Preferred device:

Crossmatch "Verifier 300 USB"

Other devices can also be connected if they have a 32-bit TWAIN driver for the respective client operating system.

Supported ID scanners in Card SDK

This section describes which ID scanners are supported by Nexus Card SDK.

Standard device for scanning of bar codes and QR codes:

Datalogic Magellan 1100i

Standard device for scanning the MRZ code of national ID cards and passports:

3M Passport Reader AT9000 MK2

The 3M Passport Reader is EOS/EOL . We will no longer provide support or assitance for this ID scanner.

Supported signature pads in Card SDK

This section describes which signature pads are supported by Nexus Card SDK.

For the capture of signatures, devices from the following manufacturers (amongst others) are supported:

SignoTec Sigma (via TWAIN driver)
SignoTec Omega (via TWAIN driver)
StepOver duraSign Pad Brilliance

Devices from other manufacturers and specific device designations on request.

Supported smartcards in Card SDK

This section describes which smart cards are supported by Nexus Card SDK.

Smartcards are only supported from Nexus Card SDK in conjunction with Smart ID Identity Manager. For more information, see Identity Manager requirements and interoperability.

For more information, see the appropriate Technical Specifications of the above mentioned applications and program packages.

Languages

The following languages are supported:

Arabic
Chinese
English
French
German
Italian
Polish
Portuguese
Russian
Spanish
Swedish