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 Software

The SDK software is packaged and supplied as .zip archives for Android. The contents are described in Table 1.

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 including Cloud Commerce SDK for Tap to Pay functionality.

Cloud Commerce SDK Components

The Android SDK includes specific components for Tap to Pay functionality:

Test vs Production AARs

We include two AARs in our release package due to MPoC security requirements:

Test AAR (cloud-commerce-sdk-mtf): Built as debuggable and preconfigured to use only sandbox endpoints. You get verbose logs and can't accidentally hit a live endpoint.
Production AAR (cloud-commerce-sdk): Non-debuggable with minimal logging and locked to live endpoints under full PCI-compliant security controls.

In the Android release these can be found at:

Test SDK libs/cloud-commerce-sdk-mtf-<version>.aar
Production SDK libs/cloud-commerce-sdk-<version>.aar

To switch between the Production and Test SDKs, it is required to uninstall and reinstall the app - or clear its storage, since each environment requires its own storage.