Unboxing the iOS SDK
Payment Gateway Account
Register for a gateway account with your partner:
- Once logged in, click on Settings – Security Keys and follow the on-screen instructions.
- Your API Key will need to have
APIsource permissions only.
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 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.
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. |
From iOS 4.1.1 the SDK ships in two variants. The full variant (
SDK/full/) includes the Cloud Commerce SDK required for Tap to Pay (minimum iOS 18.5). The lite variant (SDK/lite/) does not support Tap to Pay (minimum iOS 17.4). Use the full variant for Tap to Pay on iPhone integrations.
Updated about 8 hours ago