Skip to main content

Upgrading and Uninstalling Payment Device SDK Applications

Updated

Table of Contents

Overview

When upgrading and uninstalling a Payment Device SDK application, please be aware of the following:

  • When you are uninstalling the application, this will remove the Payment Device SDK database from your device's local application data.
  • The local application data will contain any offline transactions that may have been performed. So please be aware to make sure all offline transactions have successfully been submitted online before uninstalling the application.
  • Once the application has been uninstalled, all offline transactions that are stored on the mobile device will be removed as part of the database being removed.
  • This will also delete any settings that are set up on the application such as the application password, PIN pad name, terminal ID(s), etc.

Updating the Payment Device SDK for iOS

Two Payment Device SDK variants are now supplied in the iOS release:

  1. ChipDnaMobile/Library which contains static libraries and header files, supporting Architectures: x86_84 for Simulator, as well as arm64 for iOS Devices.
  2. ChipDnaMobile/Framework which contains the XCFrameworks for Apple Silicon, supporting x86_64 and arm64 simulators, as well as arm64 iOS devices.

Important: Do not include both variants in the same project. Choose the one that best fits your integration approach:

To update your Payment Device SDK version, you will need to replace old frameworks or libraries in your application with the newer ones included in the latest download of the SDK. Ensure to update the Tap to Pay and PIN pad-specific dependencies, if these are being used in your integration. Once updated, you will need to rebuild then deploy your application. Further details are available in the SDK's Integration Guide documentation.

Updating the Payment Device SDK for Android

The Android SDK includes library files in the libs folder. To update your Payment Device SDK version, you will need to replace old library JAR files in your application with the newer ones included in the latest download of the SDK. Ensure to update the Tap to Pay AAR files and PIN pad-specific dependencies, if these are being used in your integration. Once updated, you will need to rebuild then deploy your application. Further details are available in the SDK's Integration Guide documentation.