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

Submitting Your Application Package Names for Validation

As part of a standard integrity check, the application (app) package names that you use for testing and production must be validated.

Submit all of the app package names that you intend to use with the Tap to Phone Android SDK to your implementation manager for validation.

If you use multiple variations of the app package name, submit all of the name variants to your implementation manager. For example, if you use one app package name for testing and debugging and use a different name for production, you would submit both of these name variants for validation. For more information about build variants, see Configure build variants in Android Studio.

After your implementation manager validates your app package names, they will be added to the Tap to Phone Android SDK backend as allowed apps.

Back to top