API Overview

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

Introduction to Acceptance Devices | Tap to Pay on Android Acceptance Devices App

Compatibility Requirements for Android Devices

Payment Devices Supported by the Tap to Pay on Android Acceptance Devices App

Transaction Workflow for the Tap to Pay on Android Acceptance Devices App

PCI MPoC Standard Compliance
- Transaction Workflow for the PCI-Certified MPoC Solution

Getting Started with the Acceptance Devices App
- Install the Tap to Pay Ready App
- Set Up an Android Device
- Activating an Android Device in the Acceptance Devices App
  - Generate an Android Device Activation Code in the Business Center
  - Generate an Android Device Activation Code Using a REST API Request
    - Required Fields for Generating an Android Device Activation Code
    - REST Example: Generating an Android Device Activation Code
    - Enter an Activation Code in the Acceptance Devices App
- Starting the Acceptance Devices App Server
  - Start the Acceptance Devices App Server
- Customizing the Acceptance Devices App
  - Customizable User Interface Parameters
  - Customizable Common Parameters
  - Customizable Local Mode Parameters
  - Customizable Standalone Mode Parameters
  - Customize Parameters in the Business Center
  - Retrieve Parameters Using a REST API Request
    - Required Fields to Retrieve Parameters Using a REST API Request
    - REST Example: Retrieve Parameters Using a REST API Request
  - Customize Parameters Using a REST API Request
    - Required Fields to Customize Parameters Using a REST API Request
    - REST Example: Customize Parameters Using a REST API Request

Local Mode Payment Services
- Communication Protocol Used in Local Mode
- Retrieving the Root CA Certificate
  - Retrieve the Root CA Certificate in the Business Center
  - Retrieve the Root CA Certificate Using a REST API Request
    - Required Fields to Retrieve the Root CA Certificate Using a REST API Request
    - REST Example: Retrieve the Root CA Certificate Using a REST API Request
- Activating a Secure mTLS Connection
  - Generate a POS Connection Code for the Point-of-Sale System
  - Request Certificates for the Point-of-Sale System
    - Required Fields to Request Certificates for the Point-of-Sale System
    - REST Example: Request Certificates for the Point-of-Sale System
- Implement Hostname Validation in Local Mode
- Sale
  - Required Fields for a Sale
  - REST Example: Sale
- Refund
  - Required Fields for a Refund
  - Optional Fields for a Refund
  - REST Example: Refund
- Stand-Alone Credit
  - Required Fields for a Stand-Alone Credit
  - REST Example: Stand-Alone Credit
- Check Transaction Status
  - Required Fields to Request a Check Transaction Status
  - REST Example: Request a Check Transaction Status
- Cancel Transaction
  - Required Fields to Cancel Transaction
  - REST Example: Cancel Transaction
- Sale with On-Reader Tipping
  - Required Fields for a Sale with On-Reader Tipping
  - REST Example: Sale with On-Reader Tipping
- Pre-Authorization
  - Required Fields for a Pre-Authorization
  - REST Example: Pre-Authorization
- Incremental Authorization
  - Required Fields for an Incremental Authorization
  - REST Example: Incremental Authorization
- Capture
  - Required Fields for a Capture
  - Optional Fields for a Capture
  - REST Example: Capture
- Sale with Installment Details
  - Required Fields for a Sale with Installment Details
  - Optional Fields for a Sale with Installment Details
  - REST Example: Sale with Installment Details
- Sale with Payment Facilitator Details
  - Required Fields for a Sale with Payment Facilitator Details
  - Optional Fields for a Sale with Payment Facilitator Details
  - REST Example: Sale with Payment Facilitator Details
- Sale with Tax Details
  - Required Fields for a Sale with Tax Details
  - Optional Fields for a Sale with Tax Details
  - REST Example: Sale with Tax Details

Cloud Mode Payment Services
- Communication Protocol Used in Cloud Mode
- Generating a Bearer Token for Authentication
  - Generate a Bearer Token for Authentication
- Sale
  - Required Fields for a Sale
  - REST Example: Sale
- Refund
  - Required Fields for a Refund
  - Optional Fields for a Refund
  - REST Example: Refund
- Stand-Alone Credit
  - Required Fields for a Stand-Alone Credit
  - REST Example: Stand-Alone Credit
- Check Transaction Status
  - Required Fields to Request a Check Transaction Status
  - REST Example: Request a Check Transaction Status
- Cancel Transaction
  - Required Fields to Cancel Transaction
  - REST Example: Cancel Transaction
- Sale with On-Reader Tipping
  - Required Fields for a Sale with On-Reader Tipping
  - REST Example: Sale with On-Reader Tipping
- Pre-Authorization
  - Required Fields for a Pre-Authorization
  - REST Example: Pre-Authorization
- Incremental Authorization
  - Required Fields for an Incremental Authorization
  - REST Example: Incremental Authorization
- Capture
  - Required Fields for a Capture
  - Optional Fields for a Capture
  - REST Example: Capture
- Sale with Installment Details
  - Required Fields for a Sale with Installment Details
  - Optional Fields for a Sale with Installment Details
  - REST Example: Sale with Installment Details
- Sale with Payment Facilitator Details
  - Required Fields for a Sale with Payment Facilitator Details
  - Optional Fields for a Sale with Payment Facilitator Details
  - REST Example: Sale with Payment Facilitator Details
- Sale with Tax Details
  - Required Fields for a Sale with Tax Details
  - Optional Fields for a Sale with Tax Details
  - REST Example: Sale with Tax Details
- Receiving Transaction Responses Asynchronously
  - Receive Transaction Responses Asynchronously
  - REST Example: Receive Transaction Responses Asynchronously
  - Check Transaction Events
    - Required Fields to Check Transaction Events
    - REST Example: Check Transaction Events

Standalone Mode Payment Services
- Enable Standalone Mode in the Acceptance Devices App
- Sale
- Refund
- Stand-Alone Credit
- Sale with On-Reader Tipping
- Pre-Authorization
- Capture
- Sale with Installment Details
- Sale with Tax Details
- Email a Customer Receipt

Release Notes for Tap to Pay on Android Acceptance Devices App
- Acceptance Devices App Version 1.18.0 Release Notes
  - New Features
  - Improvements
  - Fixed Issues
- Acceptance Devices App Version 1.17.0 Release Notes
  - New Features
  - Improvements
  - Fixed Issues
- Acceptance Devices App Version 1.16.0 Release Notes
  - Improvements
  - Fixed Issues
- Acceptance Devices App Version 1.15.0 Release Notes
  - New Features
  - Improvements
  - Fixed Issues
- Archive of Release Notes
  - Acceptance Devices App Version 1.14.0 Release Notes
    - New Features
    - Improvements
  - Acceptance Devices App Version 1.13.0 Release Notes
    - Improvements
  - Acceptance Devices App Version 1.12.0 Release Notes
    - Improvements
  - Acceptance Devices App Version 1.11.0 Release Notes
    - Improvements
    - Fixed Issues
  - Acceptance Devices App Version 1.10.0 Release Notes
    - New Features
    - Improvements
  - Acceptance Devices App Version 1.9.0 Release Notes
    - New Features
    - Improvements
  - Acceptance Devices App Version 1.8.0 Release Notes
    - Improvements
    - Fixed Issues
  - Acceptance Devices App Version 1.7.0 Release Notes
    - New Features
    - Improvements
    - Fixed Issues
  - Acceptance Devices App Version 1.6.0 Release Notes
    - Improvements
  - Acceptance Devices App Version 1.5.0 Release Notes
    - New Features
    - Improvements
    - Fixed Issues
  - Acceptance Devices App Version 1.4.0 Release Notes
    - New Features
    - Improvements
    - Fixed Issues
  - Acceptance Devices App Version 1.3.0 Release Notes
    - New Features
    - Improvements
    - Fixed Issues
  - Acceptance Devices App Version 1.2.0 Release Notes
    - Improvements
    - Fixed Issues
  - Acceptance Devices App Version 1.1.0 Release Notes
    - New Features

On This Page

REST Example: Generating an Android Device Activation Code

Request

The body of the request is empty. The POST request includes the information required to return the response.

{
}

Response to a Successful Request

The response includes the activation code (

token

field) and the amount of time (

ttl

field) that the activation code is valid. The

ttl

field value is shown in milliseconds. The activation code is valid for 24 hours.

{
    "tokens": [
        {
            "token": "%N5wU2jH",
            "ttl": 86399805
        }
    ]
}

Back to top