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

Recent Revisions to This Document

24.03

Applied updates:: Added SDK Version 2.88.0 Release Notes and updated release version in code examples.; Made general editorial changes.

24.02

Applied updates:: Updated code example in Configuring ProGuard Rules to Enable Obfuscation.; Added SDK Version 2.87.0 Release Notes and updated release version in code examples.

24.01

Added new section:: Release Notes for Tap to Phone Android Solution
Applied updates:: Added SDK Version 2.86.0 Release Notes and updated release version in code examples.; Updated code examples in Configuring the Tap to Phone Android SDK.; Updated Adding Dependencies to include Adding the aar Files to Your Project. This update replaced "Adding the Library Folder to Your Project."

23.03

Applied updates:: Updated SDK release version to Tap to Phone 2.85.0.; Updated code examples in Configuring the Tap to Phone Android SDK.
Reorganized sections:: Adding Dependencies; Obtaining a Merchant ID and Secret Key; Creating an mposUI Instance

23.02

Added new section:: VISA Platform Connect: Specifications and Conditions for Resellers/Partners
Applied updates:: Updated SDK release version to Tap to Phone 2.83.0.; Updated code examples in Creating a UiConfiguration Instance and Performing a Check Transaction Status.
Added payment transaction types:: Performing a Sale with On-Reader Tipping; Performing a Pre-Authorization; Performing an Incremental Authorization; Performing a Capture; Emailing a Customer Receipt

23.01

Initial beta release: Includes release versions:
Tap to Phone 2.82.0
Kernel in the Cloud 23.04.00

Back to top