Page Comparison

...

Predictably, most of the methods in each SDK have similar names, allowing integrators to find a common thread to trace when navigating each SDK’s reference guide. The call to start an EMV transaction is an obvious starting point:

Each of the calls above is copied as it appears in the three reference guides, and, although each SDK has its respective syntax, the main call—emv_startTransaction()—is the same across all three implementations. Integrators will find similar continuity for most methods across ID TECH SDKs.

Other information may be similar across two SDKs but have a different name in the third SDK. For example, the iOS and Android SDKs use unencryptedTags as a parameter field for unencrypted EMV Tag data, but the Windows SDK simplifies this parameter to tlv, whether the EMV Tag data is unencrypted, encrypted, or masked. While the names for the fields don’t map perfectly, or return exactly the same granularity of response, the reference guides provide enough of a common thread to give an integrator a sense of what to look for when the SDKs have differences.

...

ID TECH encourages integrators to refer to each reference guide’s Core Implementation sections:

In addition to the basic required libraries, platform-specific protocols, and initializations, each guide provides a sample project for its SDK demonstrating how basic calls and callbacks function. Using each reference guide to determine areas of similarity, plus sample projects demonstrating basic implementations, should give integrators the jump-start they need to integrate ID TECH SDKs into an application on multiple platforms.