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

Updating the AndroidManifest.xml
File

Update your AndroidManifest.xml
file to enable a large heap size, disable support for right to left (RTL) layouts, and enable the needed permissions for the Default UI. Enabling a large heap size is required in order to accommodate situations in which an update of your terminals is required, and for which larger chunks of data are requested and transferred.

WARNING

Do not enable automatic backup in your app's AndroidManifest
file. The Tap to Phone Android SDK uses the Android Keystore to install and store cryptographic keys in your app. Using automatic backup restores the default encryption preferences and causes a functionality error in the Tap to Phone Android SDK.

Follow these steps to update your AndroidManifest.xml
file.

Set the

android:allowBackup

attribute to

false

, the

android:largeHeap

attribute to

true

, and the

android:supportsRtl

attribute to

false

.

<application
    ...
    android:allowBackup="false"
    android:largeHeap="true"
    android:supportsRtl="false"
    >
    ...
</application>

Enable the needed permissions for the Default UI.

<!-- Needed for Default UI !-->
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission android:name="android.permission.READ_PHONE_STATE"/>

Back to top