API Overview

Card Present Connect | Mass Transit Developer Guide
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Mass Transit Transaction Workflows
- American Express Pay As You Go Workflow
- Mastercard Pay As You Go Workflow
- Visa Mobility and Transport Transaction Workflow
- Additional Workflows
  - Near Real-Time Workflow
  - Fare Calculation and Submission Workflow
  - Debt Recovery Workflows

Mass Transit Payment Services Using EMV and Card Data
- Transaction Types
- Required Fields for Authorizations with EMV Data
- American Express Authorization with EMV Data
  - Example: American Express Account Status Check Authorization with EMV Data
  - Example: American Express Delayed Online Authorization with EMV Data
- Mastercard Authorization with EMV Data
  - Example: Mastercard Authorization with EMV Data
- Visa Account Verification Request (AVR) with EMV Data
  - Example: Visa AVR Authorization with EMV Data
- Required Fields for Sales with EMV Data
- Visa Deferred Sale with EMV Data
  - Example: Visa Deferred Sale with EMV Data
- Required Fields for Authorization for Debt Recovery
- Tap-Initiated Authorization for Debt Recovery with EMV Data
  - Example: Tap-Initiated Authorization for Debt Recovery with EMV Data
- Merchant-Initiated Authorizations for Debt Recovery with Stored Card Data
  - Example: Merchant-Initiated Authorization for Debt Recovery with Stored Card Data
- Required Fields for Sales for Debt Recovery
- Tap-Initiated Sales for Debt Recovery with EMV Data
  - Example: Mastercard Tap-Initiated Sale for Debt Recovery with EMV Data Using the REST API
  - Example: Tap-Initiated Sale for Debt Recovery with EMV Data Using the REST API
- Merchant-Initiated Sales for Debt Recovery with Stored Card Data
  - Example: Merchant-Initiated Sale for Debt Recovery with Stored Card Data
- Required Fields for Stand-Alone Credits with Card Data
- Stand-Alone Credits with Card Data
  - Example: Stand-Alone Credit with Card Data

Mass Transit Payment Services Using TMS Tokens
- Mass Transit Mastercard Authorization with a Token
  - Required Fields for a Mastercard Authorization with a Token Using the REST API
  - Example: Performing a Mastercard Authorization with a Token Using the REST API
- Mass Transit Visa Account Verification Request (AVR) with a Token
  - Required Fields for a Visa AVR Authorization with a Transient Token Using the REST API
  - Example: Performing a Visa AVR Authorization with a Transient Token Using the REST API
- Mass Transit Visa Deferred Sale with a Token
  - Required Fields for a Visa Deferred Sale with a Token Using the REST API
  - Example: Performing a Visa Deferred Sale with a Token Using the REST API
- Mass Transit Authorizations for a Tap-Initiated Debt Recovery with a Token
  - Required Fields for a Tap-Initiated Authorization for Debt Recovery with a Token Using the REST API
  - Example: Performing a Tap-Initiated Authorization for Debt Recovery with a Token Using the REST API
- Mass Transit Merchant-Initiated Authorizations for Debt Recovery with a Token
  - Required Fields for a Merchant-Initiated Authorization for Debt Recovery with a Token Using the REST API
  - Example: Performing a Merchant-Initiated Authorization for Debt Recovery with a Token Using the REST API
- Mass Transit Tap-Initiated Sale for Debt Recovery with a Token
  - Required Fields for a Tap-Initiated Sale for Debt Recovery with a Token Using the REST API
  - Example: Performing a Tap-Initiated Sale for Debt Recovery with a Token Using the REST API
- Mass Transit Merchant-Initiated Sale for Debt Recovery with a Token
  - Required Fields for a Merchant-Initiated Sale for Debt Recovery with a Token Using the REST API
  - Example: Performing a Merchant-Initiated Sale for Debt Recovery with a Token Using the REST API
- Mass Transit Stand-Alone Credit with a Token
  - Required Fields for a Stand-Alone Credit with a Token Using the REST API
  - Example: Performing a Stand-Alone Credit with a Token Using the REST API

Mass Transit Follow-On Payment Services
- Required Fields for Mass Transit Captures
- Capture an Authorization
  - Example: Capture an Authorization
- Required Fields for Mass Transit Reversals
- Authorization Reversals
  - Example: Reversing a Mass Transit Authorization
- Timeout Reversal
  - Example: Timeout Reversal
- Required Field for Timeout Voids
- Timeout Void
  - Example: Timeout Void

Mass Transit Token Management Services
- Creating a Token
  - Required Fields for Creating a Token Using the REST API
  - Example: Create a Token Using the REST API
- Retrieving Transient Token Details
  - Example: Retrieve Transient Token Details Using the REST API
- Retrieving an Instrument Identifier Details
  - Example: Retrieving Instrument Identifier Details Using the REST API
- Retrieving Card Hash Details
  - Example: Retrieving Card Hash Details Using the REST API
- Retrieving Payment Instrument Details
  - Example: Retrieving Payment Instrument Details Using the REST API
- Deleting an Instrument Identifier
  - Example: Deleting an Instrument Identifier Using the REST API
- Deleting a Card Hash
  - Example: Deleting a Card Hash Using the REST API

Transit Test Cases

Fare Calculation and Submission Workflow

The fare calculation workflow begins at the end of the travel period.

Flow diagram illustrating the process of calculating and submitting transit
fares — Visa Fare Calculation and Submission Flow

The back office calculates the fare of all rides taken during the travel period.

You request a sale transaction for the accumulated fare. See Visa Deferred Sale with EMV Data.

When the sale is successful, the process is complete.

When the sale is declined, the card hash is added to the deny list.

When the declined sale amount is above the chargeback threshold, the transaction is moved to debt recovery. See Debt Recovery Workflows.

When the declined sale amount is for a first ride and below the chargeback threshold, you can request the payment using the first ride risk chargeback rules as defined by each card scheme.

Back to top