Acceptance Devices | Tap to Pay on Android Solution Integration Guide
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Introduction to Acceptance Devices | Tap to Pay on Android Solution

Compatibility Requirements for Android Phones

Transaction Workflow for the Tap to Pay on Android Solution

Getting Started with the Tap to Pay on Android Solution
- Configuring the Tap to Pay on 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
- Generating a Secret Key for an Existing Merchant ID
  - Generating a Secret Key for an Existing Merchant ID in the Business Center
  - Generating a Secret Key for an Existing Merchant ID Using a REST API Request
    - Required Fields for Generating a Secret Key for an Existing Merchant ID Using a REST API Request
    - REST Example: Generating a Secret Key for an Existing Merchant ID Using a REST API Request
- Creating an mposUI Instance
  - Creating an mposUI Instance
  - Configuring an mposUI Instance
    - Creating a UiConfiguration Instance
- Customizing the Default User Interface
  - Customizing Default User Interface Style Elements
  - Enabling Dark Mode in the Default User Interface
- Enabling Device Enrollment
  - Enrolling a Device
  - Enrolling a Previously Enrolled Device
  - Viewing the Device Enrollment Result

Tap to Pay on Android Payment Services
- Processing a Sale
- Processing a Refund
- Processing a Stand-Alone Credit
- Requesting a Check Transaction Status
- Processing a Sale with On-Reader Tipping
- Processing a Pre-Authorization
- Processing an Incremental Authorization
- Processing a Capture
- Processing a Sale with Installment Details
- Processing a Sale with Payment Facilitator Details
- Processing a Sale with Tax Details
- Emailing a Customer Receipt

Release Notes for Tap to Pay on Android Solution
- SDK Version 2.101.1 Release Notes
  - New Features
  - Improvements
  - Fixed Issues
- SDK Version 2.100.0 Release Notes
  - Improvements
  - Fixed Issues
- SDK Version 2.99.0 Release Notes
  - New Features
  - Improvements
- SDK Version 2.98.0 Release Notes
  - Updated Requirements
  - New Features
  - Improvements
  - Fixed Issues
- Archive of Release Notes
  - SDK Version 2.97.0 Release Notes
    - Improvements
  - SDK Version 2.96.0 Release Notes
    - Fixed Issues
  - SDK Version 2.95.0 Release Notes
    - Improvements
    - Fixed Issues
  - SDK Version 2.94.0 Release Notes
    - Fixed Issues
    - New Features
  - SDK Version 2.93.0 Release Notes
    - Improvements
    - Updated Requirements
    - Fixed Issues
  - SDK Version 2.92.0 Release Notes
    - Improvements
  - SDK Version 2.91.0 Release Notes
    - New Features
    - Improvements
    - Fixed Issues
  - SDK Version 2.90.0 Release Notes
    - New Features
    - Improvements
    - Updated Requirements
    - Fixed Issues
    - General Information
  - SDK Version 2.89.0 Release Notes
    - Fixed Issues
    - Improvements
  - SDK Version 2.88.0 Release Notes
    - New Features
    - Improvements
  - SDK Version 2.87.0 Release Notes
    - General Information
    - Updated Requirements
    - Fixed Issues
  - SDK Version 2.86.0 Release Notes
    - Improvements
  - SDK Version 2.85.0 Release Notes
    - Improvements
    - Fixed Issues
  - SDK Version 2.84.0 Release Notes
    - Improvements
  - SDK Version 2.83.0 Release Notes
    - New Features
    - Improvements
    - Fixed Issues
  - SDK Version 2.82.0 Release Notes
    - New Features
    - Fixed Issues

On This Page

REST API

Improvements

Improved the error message that can appear when a magnetic-stripe card is not read correctly by the device.

Tap To Phone: Improved the error messages that can appear during enrollment of previously enrolled device.

Back to top