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

Publishing Your Application in Google Play Store

You must have a Google Play Store account in order to complete this required procedure.

This section describes how to navigate and publish your application (app) package in the Google Play Store. For more information, see the Google Play Store documentation.

To ensure maximum security, device enrollment and payment transactions are allowed only in the Tap to Phone Android SDK production environment when the app using the SDK is installed from a trusted source such as Google Play Store. Installing the app from another source causes the device enrollment feature not to function.

For the purposes of integrating the Tap to Phone Android SDK with your app, the minimum requirement is to publish your production app package in the lowest track in Google Play Store. The lowest track is the internal testing track. For more information about Google Play Store internal testing, see Google Play Store Internal Testing documentation.

Follow these steps to upload and publish your production app package in Google Play Store.

In your Google Play Store account, navigate to Google Play Console.

On your Google Play Console, upload your production app package. You can control whether the uploaded app is available publicly or internally. For internal testing, you can use the Google Play Developer Publishing API to automatically deploy builds as they become available. For more information, see the Google Play Developer Publishing API documentation.

Enable the Google Play Integrity API by selecting your app. For more information, see the Google Play Integrity API documentation.

In the Release section, click

Setup > App integrity

.

On the Integrity API page, click

Link project

.

Choose

Create new project

.

Click

Link project

.

Back to top