Recent Revisions to This Document

About This Guide

Introduction to Acceptance Devices | PAX Semi-Integrated Solution

Terminals Supported by the PAX Semi-Integrated Solution

Transaction Workflow for the PAX Semi-Integrated Solution

Getting Started with the PAX Semi-Integrated Solution
- Setting Up the PAX Terminal
- Loading Printer Paper in a PAX Terminal with an Integrated Printer
- Activating a Terminal in the Acceptance Devices App
  - Generating a Terminal Activation Code in the Business Center
  - Generating a Terminal Activation Code Using a REST API Request
    - Required Fields for Generating a Terminal Activation Code
    - REST Example: Generating a Terminal Activation Code
  - Entering an Activation Code in the Acceptance Devices App
- Getting Started with the Acceptance Devices App Server
  - Starting the Acceptance Devices App Server
- Customizing the Acceptance Devices App
  - Customizable Common Parameters in the Acceptance Devices App
  - Customizable Semi-Integrated Mode Parameters in the Acceptance Devices App
  - Customizable Standalone Mode Parameters in the Acceptance Devices App
  - Customizing Parameters in the Business Center
  - Retrieving Parameters Using a REST API Request
    - Required Fields for Retrieving Parameters Using a REST API Request
    - REST Example: Retrieving Parameters Using a REST API Request
  - Customizing Parameters Using a REST API Request
    - Required Fields for Customizing Parameters Using a REST API Request
    - REST Example: Customizing Parameters Using a REST API Request

Performing Payment Transactions Using Semi-Integrated Mode
- Communication Protocol Between the Acceptance Devices App and POS System in Semi-Integrated Mode
- Retrieving the Root CA Certificate
  - Retrieving the Root CA Certificate Using a REST API Request
    - Required Fields for Retrieving the Root CA Certificate Using a REST API Request
    - REST Example: Retrieving the Root CA Certificate Using a REST API Request
- Activating a Secure mTLS Connection in the Acceptance Devices App
  - Generating a POS Connection Code for the Point-of-Sale System in the Acceptance Devices App
  - Requesting Certificates for the Point-of-Sale System
    - Required Fields for Requesting Certificates for the Point-of-Sale System
    - REST Example: Requesting Certificates for the Point-of-Sale System
- Implementing Hostname Validation
- Performing a Sale
  - Required Fields for Performing a Sale
  - REST Example: Performing a Sale
- Performing a Linked Refund
  - Required Fields for Performing a Linked Refund
  - Optional Fields for Performing a Linked Refund
  - REST Example: Performing a Linked Refund
- Performing a Standalone Credit
  - Required Fields for Performing a Standalone Credit
  - REST Example: Performing a Standalone Credit
- Performing a Check Transaction Status
  - Required Fields for Performing a Check Transaction Status
  - REST Example: Performing a Check Transaction Status
- Performing a Cancel Transaction
  - Required Fields for Performing a Cancel Transaction
  - REST Example: Performing a Cancel Transaction
- Performing a Sale with On-Reader Tipping
  - Required Fields for Performing a Sale with On-Reader Tipping
  - REST Example: Performing a Sale with On-Reader Tipping
- Performing a Sale with On-Receipt Tipping
  - Required Fields for Performing a Sale with On-Receipt Tipping
  - REST Example: Performing a Sale with On-Receipt Tipping
  - Performing a Tip Adjust
    - Required Fields for Performing a Tip Adjust
    - REST Example: Performing a Tip Adjust
- Performing a Token Refund
  - Required Fields for Performing a Token Refund
  - REST Example: Performing a Token Refund
- Performing a Pre-Authorization
  - Required Fields for Performing a Pre-Authorization
  - REST Example: Performing a Pre-Authorization
- Performing an Incremental Authorization
  - Required Fields for Performing an Incremental Authorization
  - REST Example: Performing an Incremental Authorization
- Performing a Capture
  - Required Fields for Performing a Capture
  - Optional Fields for Performing a Capture
  - REST Example: Performing a Capture
- Performing a Mail Order or Telephone Order Sale
  - Required Fields for Performing a Mail Order or Telephone Order Sale
  - REST Example: Performing a Mail Order or Telephone Order Sale
- Performing a Mail Order or Telephone Order Pre-Authorization
  - Required Fields for Performing a Mail Order or Telephone Order Pre-Authorization
  - REST Example: Performing a Mail Order or Telephone Order Pre-Authorization
- Performing a Mail Order or Telephone Order Account Verification
  - Required Fields for Performing a Mail Order or Telephone Order Account Verification
  - REST Example: Performing a Mail Order or Telephone Order Account Verification
- Performing an Account Verification
  - Required Fields for Performing an Account Verification
  - REST Example: Performing an Account Verification
- Performing Offline Transactions
  - Enabling Offline Mode to Perform an Offline Sale or Refund
  - Submitting an Offline Transactions Batch for Authorization
  - Disabling Offline Mode for Offline Sale or Refund
- Performing a Cashback
  - Required Fields for Performing a Cashback
  - REST Example: Performing a Cashback
- Printing a Customer or Merchant Receipt

Performing Payment Transactions Using Standalone Mode
- Enabling Standalone Mode in the Acceptance Devices App

Performing Payment Transactions Using Cloud Mode
- Communication Protocol Between the Acceptance Devices App and POS System in Cloud Mode
- Generating a Bearer Token for Authentication Using a REST API Request
  - 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
  - Generating a Bearer Token for Authentication Using a REST API Request
    - Required Field for Generating a Bearer Token for Authentication Using a REST API Request
    - REST Example: Generating a Bearer Token for Authentication Using a REST API Request
- Performing a Sale
  - Required Fields for Performing a Sale
  - REST Example: Performing a Sale
- Performing a Linked Refund
  - Required Fields for Performing a Linked Refund
  - Optional Fields for Performing a Linked Refund
  - REST Example: Performing a Linked Refund
- Performing a Standalone Credit
  - Required Fields for Performing a Standalone Credit
  - REST Example: Performing a Standalone Credit
- Performing a Check Transaction Status
  - Required Fields for Performing a Check Transaction Status
  - REST Example: Performing a Check Transaction Status
- Performing a Cancel Transaction
  - Required Fields for Performing a Cancel Transaction
  - REST Example: Performing a Cancel Transaction

Release Notes for PAX Semi-Integrated Solution
- 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

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

On This Page

REST API

Generating a Bearer Token for Authentication Using a REST API Request

This section describes how to generate a bearer token for authentication using an API request. A unique bearer token is required to authenticate each payment transaction request when using Cloud mode. In order to generate a bearer token, you must include a merchant ID (MID) and a secret key in the request.

Back to top