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 Account Status Check Authorization with EMV Data
  - Required Fields for a American Express Account Status Check AVR Authorization with EMV Data Using the REST API
  - Example: American Express Account Status Check Authorization with EMV Data
- American Express Delayed Online Authorization with EMV Data
  - Required Fields for a American Express Delayed Online Authorization with EMV Data Using the REST API
  - Example: American Express Delayed Online Authorization with EMV Data
- Mastercard Authorization with EMV Data
  - Required Fields for a Mastercard Authorization with EMV Data Using the REST API
  - Example: Mastercard Authorization with EMV Data
- Visa Account Verification Request (AVR) with EMV Data
  - Required Fields for a Visa AVR Authorization with EMV Data Using the REST API
  - Example: Visa AVR Authorization with EMV Data
- Required Fields for Sales with EMV Data
- Visa Deferred Sale with EMV Data
  - Required Fields for a Visa Deferred Sale with EMV Data Using the REST API
  - Example: Visa Deferred Sale with EMV Data
- Required Fields for an Authorization for Debt Recovery
- Tap-Initiated Authorization for Debt Recovery with EMV Data
  - Required Fields for a Tap-Initiated Authorization for Debt Recovery with EMV Data Using the REST API
  - Example: Tap-Initiated Authorization for Debt Recovery with EMV Data
- Merchant-Initiated Authorizations for Debt Recovery with Stored Card Data
  - Required Fields for a Merchant-Initiated Authorization for Debt Recovery with Stored Card Data Using the REST API
  - Example: Merchant-Initiated Authorization for Debt Recovery with Stored Card Data
- Required Fields for a Sale for Debt Recovery
- Tap-Initiated Sale for Mastercard Debt Recovery with EMV Data
  - Required Fields for a Tap-Initiated Sale for Mastercard Debt Recovery with EMV Data Using the REST API
  - Example: Tap-Initiated Sale for Mastercard Debt Recovery with EMV Data Using the REST API
- Tap-Initiated Sale for Visa Debt Recovery with EMV Data
  - Required Fields for a Tap-Initiated Sale for Visa Debt Recovery with EMV Data Using the REST API
  - Example: Tap-Initiated Sale for Visa Debt Recovery with EMV Data Using the REST API
- Merchant-Initiated Sale for Debt Recovery with Stored Card Data
  - Required Fields for a Merchant-Initiated Sale for Debt Recovery with Stored Card Data Using the REST API
  - Example: Merchant-Initiated Sale for Debt Recovery with Stored 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
  - Required Fields for a Mass Transit Capture
  - Example: Capture an Authorization
- Required Fields for Mass Transit Reversals
- Authorization Reversal
  - Required Fields for a Mass Transit Authorization Reversal
  - Example: Reversing a Mass Transit Authorization
- Timeout Reversal
  - Required Fields for a Timeout Reversal
  - Example: Timeout Reversal
- Required Field for Timeout Voids
- Timeout Void
  - Required Field for a 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

Journey History Service

Card schemes might require transit operators to provide cardholders with a journey history service that enables the cardholder to view their journey history and receipt information. Refer to card scheme documentation for more information about each card scheme's requirements for journey history.

Payment Account Reference

Cybersource supports the use of the payment account reference (PAR) by providing the PAR value in authorization responses when a PAR is available from the card issuer. The PAR response field is

processorInformation.paymentAccountReferenceNumber

. Using the PAR enables you to track card accounts when digital devices, such as smart phones and smart watches, have a network token or device PAN (DPAN) that the card issuer provided to the device. You can use the PAR to provide journey history to cardholders and to match the card account funding PAN (FPAN) and device PAN (DPAN) values.

Merchant Descriptor

You can use the merchant descriptor feature to produce a transaction-specific reference that cardholders can see on their card account statement. To use the merchant descriptor feature, include the

merchantInformation.merchantDescriptor.name

field in your authorization, credit, and capture requests. The value for the field must consist solely of English characters.

Before implementing transit journey history functionality, confirm with your acquirer and card schemes that the PAR and merchant descriptor features are supported.

For documentation regarding Cybersource card-not-present services that you can use to support a transit system journey history service, see the

Payments Developer Guide

.

Back to top