Recent Revisions to This Document

About This Guide

Introduction to Acceptance Devices | Tap to Phone Android Solution

Compatibility Requirements for an Android Phone

Transaction Workflow for the Tap to Phone Android Solution

Getting Started with the Tap to Phone Android Solution
- Preparing Your Application for Testing and Production
  - Submitting Your Application Package Names for Validation
  - Publishing Your Application in Google Play Store
- Configuring the Tap to Phone Android SDK
  - Configuring the Project settings.gradle File
  - Configuring the Project build.gradle File
  - Configuring the Module build.gradle File
  - Updating the AndroidManifest.xml File
  - Configuring ProGuard Rules to Enable Obfuscation
- Adding Dependencies
  - Adding the aar Files to Your Project
  - Obtaining Kernel in the Cloud Files
    - Adding Kernel in the Cloud Dependencies
  - Obtaining Visa Sensory Branding Files
    - Adding Visa Sensory Branding Dependencies
  - Obtaining Mastercard Sonic Branding Files
    - Adding Mastercard Sonic Branding Dependencies
- Obtaining a Merchant ID and Secret Key
  - Obtaining a Merchant ID and Secret Key from the Business Center
  - Obtaining a Merchant ID and Secret Key Using a REST API Request
    - Required Field for Obtaining a Merchant ID and Secret Key Using a REST API Request
    - REST Example: Obtaining a Merchant ID and Secret Key Using a REST API Request
- Creating an mposUI Instance
  - Creating an mposUI Instance Using the create Function
  - Configuring an mposUI Instance
    - Creating a UiConfiguration Instance
- Enabling Device Enrollment
  - Enabling Device Enrollment Using the enrollDevice Activity
  - Enabling Device Enrollment Using the getEnrollDeviceIntent Method
  - Viewing the Device Enrollment Result

Performing Payment Transactions in the Tap to Phone Android Solution
- Performing a Sale
- Performing a Linked Refund
- Performing a Standalone Credit
- Performing a Check Transaction Status
- Performing a Sale with On-Reader Tipping
- Performing a Pre-Authorization
- Performing an Incremental Authorization
- Performing a Capture
- Emailing a Customer Receipt

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

On This Page

REST API

Configuring the Module build.gradle
File

Follow these steps to configure your module build.gradle
file.

In the Android section, add these exclusion rules to your module's build.gradle
file.

android {
    ...
    packaging {
        resources {
            excludes.add("META-INF/*")
            excludes.add("LICENSE.txt")
            excludes.add("asm-license.txt")
        }
    }
}

In order for the app to support Java 11 features, you must set the compatibility levels.

android {
    ...
    compileOptions {
        sourceCompatibility = JavaVersion.VERSION_11
        targetCompatibility = JavaVersion.VERSION_11
    }
    kotlinOptions {
        jvmTarget = "11"
    }
}

The Tap to Phone Android Solution library publishes a release build type only. The debug build type is not available, so set the

matchingFallbacks

field value to

release

.

android {
    ...
    buildTypes {
        ...
        debug {
            matchingFallbacks.apply {
                clear()
                add("release")
            }
        }
    }
}

IMPORTANT

The repository contains the six latest SDK versions, which are updated continually. You cannot build a new version of your application using an outdated SDK version after it is removed from the repository. To ensure that you benefit from the latest features and enhancements, regularly update to the latest version of the SDK.

Add the required Default UI and Tap to Phone libraries to the Dependencies section of your module's build.gradle
file.

dependencies {
    ...
    // This is the Default UI dependency
    implementation("io.payworks:paybutton-android:2.88.0")
  
    // This is the Tap to Phone dependency
    implementation("io.payworks:mpos.android.taptophone:2.88.0")   
}

Back to top