API Overview

Card Present Connect | Mass Transit Developer Guide
- Recent Revisions to This Document

Introduction to Card Present Connect | Mass Transit
- Transit Rider Benefits
- Transit System Benefits
- Supported Card Types
- Mass Transit Terminology
- Mass Transit Prerequisites
- Mass Transit Validation and Certification
- First Ride Risk
- Transit Test Cases

Mass Transit Models and Workflows
- American Express Mass Transit Model
- Discover Pay As You Go Model
- Mastercard Pay As You Go Model
- Visa Mass Transit Model
- Common Mass Transit Transaction Workflows and Features

Mass Transit Payment Services Using EMV and Card Data
- Mass Transit Transaction Types
- Required Fields for Authorizations with EMV Data
- American Express Account Status Check Authorization with EMV Data
- American Express Delayed Online Authorization with EMV Data
- Discover Authorization with EMV Data
- Mastercard Authorization with EMV Data
- Visa Account Verification Request with EMV Data
- Required Fields for a Sale with EMV Data
- Discover Sale with EMV Data
- Visa Deferred Sale with EMV Data
- Required Fields for Authorizations for Debt Recovery
- Tap-Initiated Authorization for Debt Recovery with EMV Data
- 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
- Tap-Initiated Sale for Visa Debt Recovery with EMV Data
- Merchant-Initiated Sale for Discover Debt Recovery with Card Data
- Merchant-Initiated Sale for Mastercard Debt Recovery with Card Data
- Merchant-Initiated Sale for Visa Debt Recovery with Stored Card Data

Mass Transit Payment Services Using TMS Tokens
- Mastercard Authorization with a Token
- Visa Account Verification Request with a Token
- Visa Deferred Sale with a Token
- Tap-Initiated Authorization for Debt Recovery with a Token
- Merchant-Initiated Authorization for Debt Recovery with a Token
- Tap-Initiated Sale for Debt Recovery with a Token
- Merchant-Initiated Sale for Debt Recovery with a Token

Mass Transit Follow-On Payment Services
- Required Fields for Mass Transit Captures
- Capture
- Required Fields for Mass Transit Reversals
- Authorization Reversal
- Time-Out Authorization Reversal
- Stand-Alone Credit with a Token
- Required Field for Timeout Voids
- Time-Out Void

Mass Transit Token Management Services
- Creating a Token
- Retrieving Transient Token Details
- Retrieving an Instrument Identifier Details
- Retrieving Card Hash Details
- Retrieving Payment Instrument Details
- Deleting an Instrument Identifier
- Deleting a Card Hash

On This Page

Mass Transit Validation and Certification

You must complete validation and certification activities before your system can go live. Work with your payment technology provider (PTP) to complete message-level validation (MLV) and EMV Level 3 certification of your transit fare processing system. You must pass MLV before beginning EMV Level 3 certification.

Message-Level Validation

Message-level validation (MLV) is a script-based, field-level validation against Visa Acceptance Solutions specifications.

Your PTP uses amount-based test triggers to send transactions into a test environment and the Visa Certification Management System for decryption. The test results are XML or RESTful output, Business Center test transactions, and log prints.

Visa Acceptance Solutions uses these activities to validate the results:

Cross edit checks

Data element validation

Interchange compliance

Data mapping validation

EMV Level 3 Certification

This section describes the Level 3 certification process used by Visa Acceptance Solutions and Visa Platform Connect. The certification processes and support for Global Card Present Connect projects and for direct merchant and acquirer projects differ from what is described here, but the timelines are basically the same.

Certification
is a formal process used to validate that the device and application are compliance with card scheme acceptance regulations. The certification team uses a brand test tool and simulator during the certification process, which includes these elements:

A payment card simulation tool such as UL, ICC, or Fime.

Failed case analysis and resolution.

For Mastercard certification, your PTP submits results to Mastercard and pays the costs for approved partners that Mastercard uses.

For Visa certification, Visa Acceptance Solutions submits results to Visa.

Waivers from the card schemes for exceptions.

Card schemes responses or Letter of Approval (LOA) to signify acceptance and Level 3 certification.

For information about how to design an EMV Level 3 certified payment application, see EMV Book 3 Application Specification
.

Back to top