Payment Gateway Account

Once logged in, click on Settings – Security Keys and follow the on-screen instructions.
Your API Key will need to have API source permissions only.

Keep the API Key details safe - you need this to configure the Payment Device SDK for processing transactions.

Application Identifier

The integrating application should always utilise the same value. The application identifier cannot be changed once configured on the TMS platform.

The value for this identifier should be a single word or acronym that uniquely identifies the application, for example company name or application name. It should contain only alphanumeric characters in the range A-Z and 0-9 and the same value should be used for the same integrating application across all platforms.

Payment Device SDK for iOS/Android Software

The SDK software is packaged and supplied as .zip archives, one for Android and the other for iOS. The contents are described in Tables 1 and 2.

Table 1 - Contents of Payment Device for Android .zip archive.

Folder Name	Description
ChipDnaMobileJavaDemo	An example client written in Java, including source code, demonstrating a simple integration using the ChipDNA Mobile SDK.
ChipDnaMobileKotlinDemo	An example client written in Kotlin, including source code, demonstrating a simple integration using the ChipDNA Mobile SDK.
doc	The documentation of the ChipDNA Mobile API.
libs	The ChipDNA Mobile SDK binaries.

Table 2 - Contents of Payment Device for iOS .zip archive.

Folder Name	Description
ChipDnaMobileObjectiveCDemo	An example client written in Objective-C, including source code, demonstrating a simple integration using the ChipDNA Mobile SDK.
ChipDnaMobileSwiftDemo	An example client written in Swift, including source code, demonstrating a simple integration using the ChipDNA Mobile SDK
doc	The documentation of the ChipDNA Mobile API.
ChipDnaMobile	The ChipDNA Mobile SDK binaries and header files.