...

For a full description of each SDK’s integration steps, see the ID TECH iOS SDK Reference Guide for VP3300, the ID TECH Android SDK Reference Guide for VP3300 AJ, and the ID TECH Windows SDK Reference Guide for Visual Studio Development, each available as part of the SDK download ZIP files on the ID TECH Knowledge Base.

iOS SDK

Our Native iOS SDK uses multiple protocols and callbacks (one per function). It also uses individual Device classes that map to the main device class. However, the main device class doesn't share the same API method as the individual device class. For example: IDT_VP3300 emv_startTrans executes IDT_Device.startTrans.

Android SDK

Our native Android Java SDK  uses a more limited set of On Receiver Listeners. The individual device classes have more device types than the iOS SDK, which just requires declaring the device is a VP3300; on Android, the application must declare the device is a VP3300_USB, a VP3300_AJ, or a VP3300_BLE.

.NET SDK

Our Visual Studio Windows SDK is our most comprehensive SDK. In this case, the SDK has a callback model, but just one callback that processes everything. Additionally, the IDT_Device class has an extended naming convention to match the individual device class names.

Similarities Between Platforms

...