Acceptance Devices | PAX Semi-Integration Solution Integration Guide
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners

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
  - Customizable Semi-Integrated Mode Parameters
  - Customizable Standalone Mode Parameters
  - 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

Processing Payment Transactions in Semi-Integrated Mode
- Communication Protocol Used in Semi-Integrated Mode
- Retrieving the Root CA Certificate
  - Retrieving the Root CA Certificate in the Business Center
  - 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
  - Generating a POS Connection Code for the Point-of-Sale System
  - 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
- Processing a Sale
  - Required Fields for Processing a Sale
  - REST Example: Processing a Sale
- Processing a Linked Refund
  - Required Fields for Processing a Linked Refund
  - Optional Fields for Processing a Linked Refund
  - REST Example: Processing a Linked Refund
- Processing a Stand-Alone Credit
  - Required Fields for Processing a Stand-Alone Credit
  - REST Example: Processing a Stand-Alone Credit
- Requesting a Check Transaction Status
  - Required Fields for Requesting a Check Transaction Status
  - REST Example: Requesting a Check Transaction Status
- Processing a Cancel Transaction
  - Required Fields for Processing a Cancel Transaction
  - REST Example: Processing a Cancel Transaction
- Processing a Sale with On-Reader Tipping
  - Required Fields for Processing a Sale with On-Reader Tipping
  - REST Example: Processing a Sale with On-Reader Tipping
- Processing a Sale with On-Receipt Tipping
  - Required Fields for Processing a Sale with On-Receipt Tipping
  - REST Example: Processing a Sale with On-Receipt Tipping
  - Processing a Tip Adjust
    - Required Fields for Processing a Tip Adjust
    - REST Example: Processing a Tip Adjust
- Processing a Token Refund
  - Required Fields for Processing a Token Refund
  - REST Example: Processing a Token Refund
- Processing a Pre-Authorization
  - Required Fields for Processing a Pre-Authorization
  - REST Example: Processing a Pre-Authorization
- Processing an Incremental Authorization
  - Required Fields for Processing an Incremental Authorization
  - REST Example: Processing an Incremental Authorization
- Processing a Capture
  - Required Fields for Processing a Capture
  - Optional Fields for Processing a Capture
  - REST Example: Processing a Capture
- Processing a Mail Order or Telephone Order Sale
  - Required Fields for Processing a Mail Order or Telephone Order Sale
  - REST Example: Processing a Mail Order or Telephone Order Sale
- Processing a Mail Order or Telephone Order Pre-Authorization
  - Required Fields for Processing a Mail Order or Telephone Order Pre-Authorization
  - REST Example: Processing a Mail Order or Telephone Order Pre-Authorization
- Processing a Mail Order or Telephone Order Account Verification
  - Required Fields for Processing a Mail Order or Telephone Order Account Verification
  - REST Example: Processing a Mail Order or Telephone Order Account Verification
- Processing an Account Verification
  - Required Fields for Processing an Account Verification
  - REST Example: Processing an Account Verification
- Processing an Offline Transaction
  - Enabling Offline Mode for Offline Sale or Refund Transactions
  - Submitting an Offline Transactions Batch for Authorization
  - Disabling Offline Mode for Offline Sale or Refund Transactions
- Processing a Cashback
  - Required Fields for Processing a Cashback
  - REST Example: Processing a Cashback
- Processing a Sale with Installment Details
  - Required Fields for Processing a Sale with Installment Details
  - Optional Fields for Processing a Sale with Installment Details
  - REST Example: Processing a Sale with Installment Details
- Processing a Sale with Payment Facilitator Details
  - Required Fields for Processing a Sale with Payment Facilitator Details
  - Optional Fields for Processing a Sale with Payment Facilitator Details
  - REST Example: Processing a Sale with Payment Facilitator Details
- Processing a Sale with Tax Details
  - Required Fields for Processing a Sale with Tax Details
  - Optional Fields for Processing a Sale with Tax Details
  - REST Example: Processing a Sale with Tax Details
- Generating a Customer or Merchant Receipt

Processing Payment Transactions in Standalone Mode
- Enabling Standalone Mode in the Acceptance Devices App

Processing Payment Transactions in Cloud Mode
- Communication Protocol Used in Cloud Mode
- 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
  - 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
- Processing a Sale
  - Required Fields for Processing a Sale
  - REST Example: Processing a Sale
- Processing a Linked Refund
  - Required Fields for Processing a Linked Refund
  - Optional Fields for Processing a Linked Refund
  - REST Example: Processing a Linked Refund
- Processing a Stand-Alone Credit
  - Required Fields for Processing a Stand-Alone Credit
  - REST Example: Processing a Stand-Alone Credit
- Requesting a Check Transaction Status
  - Required Fields for Requesting a Check Transaction Status
  - REST Example: Requesting a Check Transaction Status
- Processing a Cancel Transaction
  - Required Fields for Processing a Cancel Transaction
  - REST Example: Processing a Cancel Transaction
- Processing a Sale with On-Reader Tipping
  - Required Fields for Processing a Sale with On-Reader Tipping
  - REST Example: Processing a Sale with On-Reader Tipping
- Processing a Sale with On-Receipt Tipping
  - Required Fields for Processing a Sale with On-Receipt Tipping
  - REST Example: Processing a Sale with On-Receipt Tipping
  - Processing a Tip Adjust
    - Required Fields for Processing a Tip Adjust
    - REST Example: Processing a Tip Adjust
- Processing a Token Refund
  - Required Fields for Processing a Token Refund
  - REST Example: Processing a Token Refund
- Processing a Pre-Authorization
  - Required Fields for Processing a Pre-Authorization
  - REST Example: Processing a Pre-Authorization
- Processing an Incremental Authorization
  - Required Fields for Processing an Incremental Authorization
  - REST Example: Processing an Incremental Authorization
- Processing a Capture
  - Required Fields for Processing a Capture
  - Optional Fields for Processing a Capture
  - REST Example: Processing a Capture
- Processing a Mail Order or Telephone Order Sale
  - Required Fields for Processing a Mail Order or Telephone Order Sale
  - REST Example: Processing a Mail Order or Telephone Order Sale
- Processing a Mail Order or Telephone Order Pre-Authorization
  - Required Fields for Processing a Mail Order or Telephone Order Pre-Authorization
  - REST Example: Processing a Mail Order or Telephone Order Pre-Authorization
- Processing a Mail Order or Telephone Order Account Verification
  - Required Fields for Processing a Mail Order or Telephone Order Account Verification
  - REST Example: Processing a Mail Order or Telephone Order Account Verification
- Processing an Account Verification
  - Required Fields for Processing an Account Verification
  - REST Example: Processing an Account Verification
- Processing a Cashback
  - Required Fields for Processing a Cashback
  - REST Example: Processing a Cashback
- Processing a Sale with Installment Details
  - Required Fields for Processing a Sale with Installment Details
  - Optional Fields for Processing a Sale with Installment Details
  - REST Example: Processing a Sale with Installment Details
- Processing a Sale with Payment Facilitator Details
  - Required Fields for Processing a Sale with Payment Facilitator Details
  - Optional Fields for Processing a Sale with Payment Facilitator Details
  - REST Example: Processing a Sale with Payment Facilitator Details
- Processing a Sale with Tax Details
  - Required Fields for Processing a Sale with Tax Details
  - Optional Fields for Processing a Sale with Tax Details
  - REST Example: Processing a Sale with Tax Details
- Generating a Customer or Merchant Receipt
- Receiving Transaction Responses Asynchronously
  - Receiving Transaction Responses Asynchronously
  - REST Example: Processing a Sale Asynchronously
  - Processing a Check Transaction Events
    - Required Fields for Processing a Check Transaction Events
    - REST Example: Processing a Check Transaction Events

On This Page

REST API

Processing a Tip Adjust

This section describes how to process the follow-on tip adjust that is required for a sale with on-receipt tipping when the app is in Semi-Integrated mode.

A follow-on tip adjust request must be sent within 24 hours in order to capture the transaction. After the original transaction is pre-authorized, the customer writes the tip or total amount on the printed receipt. A follow-on tip adjust request is then sent to capture the additional tip amount. This transaction is also referred to as an overcapture
.

Endpoints

The endpoint is the same for the test and production environments.

Test:

wss://{terminal IP address:port number}/

Production:

wss://{terminal IP address:port number}/

Back to top