Recent Revisions to This Document

About This Guide

Introduction to Mass Transit
- Rider Benefits
- Transit System Benefits
- Mass Transit Terminology
- Mass Transit Prerequisites
- Mass Transit Validation and Certification
  - Message-Level Validation
  - EMV L3 Certification
- Mass Transit Transactions
  - Card Types and Transaction Models
  - Mastercard Mass Transit Models
    - Pay As You Go (PAYG)
  - Visa Mass Transit Model
    - Visa Mobility and Transport Transaction

Mass Transit Transaction Workflows
- Mastercard Pay As You Go (PAYG) 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
- Mass Transit Mastercard Authorization with EMV Data
  - Required Fields for a Mastercard Authorization with EMV Data Using the REST API
  - Required Fields for a Mastercard Authorization with EMV Data in Europe Using the REST API
  - Performing a Mastercard Authorization with EMV Data Using the REST API
- Mass Transit Visa Account Verification Request (AVR) with EMV Data
  - Required Fields for a Visa AVR Authorization with EMV Data Using the REST API
  - Performing a Visa AVR Authorization with EMV Data Using the REST API
- Mass Transit Visa Deferred Sale with EMV Data
  - Required Fields for a Visa Deferred Sale with EMV Data Using the REST API
  - Performing a Visa Deferred Sale with EMV Data Using the REST API
- Mass Transit Authorizations for a Tap-Initiated Debt Recovery with EMV Data
  - Required Fields for a Tap-Initiated Authorization for Debt Recovery with EMV Data Using the REST API
  - Required Fields for a Tap-Initiated Authorization for Debt Recovery with EMV Data for Mastercard in Europe Using the REST API
  - Performing a Tap-Initiated Authorization for Debt Recovery with EMV Data Using the REST API
- Mass Transit Merchant-Initiated Authorizations for Debt Recovery with EMV Data
  - Required Fields for a Merchant-Initiated Authorization for Debt Recovery with EMV Data Using the REST API
  - Required Fields for a Merchant-Initiated Authorization for Debt Recovery with EMV Data for Mastercard in Europe Using the REST API
  - Performing a Merchant-Initiated Authorization for Debt Recovery with EMV Data Using the REST API
- Mass Transit Tap-Initiated Sales for Debt Recovery with EMV Data
  - Required Fields for a Tap-Initiated Sale for Debt Recovery with EMV Data Using the REST API
  - Required Fields for a Tap-Initiated Sale for Debt Recovery with EMV Data for Mastercard in Europe Using the REST API
  - Performing a Tap-Initiated Sale for Debt Recovery with EMV Data Using the REST API
- Mass Transit Merchant-Initiated Sales for Debt Recovery with EMV Data
  - Required Fields for a Merchant-Initiated Sale for Debt Recovery with EMV Data Using the REST API
  - Required Fields for a Merchant-Initiated Sale for Debt Recovery with EMV Data in Europe Using the REST API
  - Performing a Merchant-Initiated Sale for Debt Recovery with EMV Data Using the REST API
- Mass Transit Stand-Alone Credits with Card Data
  - Required Fields for a Stand-Alone Credit with Card Data Using the REST API
  - Performing a Stand-Alone Credit with Card Data Using the REST API

Mass Transit Follow-On Payment Services
- Mass Transit Captures
  - Required Fields for a Mass Transit Capture Using the REST API
  - Capturing a Mass Transit Authorization Using the REST API
- Mass Transit Authorization Reversals
  - Required Fields for a Mass Transit Authorization Reversal Using the REST API
  - Reversing a Mass Transit Authorization Using the REST API
- Mass Transit Timeout Reversal
  - Required Fields for a Timeout Reversal Using the REST API
  - Performing a Timeout Reversal Using the REST API
- Mass Transit Timeout Voids
  - Required Field for a Timeout Void Using the REST API
  - Performing a Timeout Void Using the REST API

BIN Lookup Service

Transit Test Cases

REST API Fields
- clientReferenceInformation.code (Request)
- clientReferenceInformation.partner.solutionId
- clientReferenceInformation.partner.thirdPartyCertificationNumber
- clientReferenceInformation.transactionId
- consumerAuthenticationInformation.strongAuthentication. riskAnalysisExemptionIndicator
- orderInformation.amountDetails.currency (Request)
- orderInformation.amountDetails.totalAmount
- paymentInformation.card.expirationMonth
- paymentInformation.card.expirationYear
- paymentInformation.card.number
- paymentInformation.card.cardType
- paymentInformation.card.type
- paymentInformation.fluidData.descriptor
- paymentInformation.fluidData.encoding
- paymentInformation.initiationChannel
- pointOfSaleInformation.catLevel
- pointOfSaleInformation.deviceId
- pointOfSaleInformation.emv.cardSequenceNumber
- pointOfSaleInformation.emv.tags (request)
- pointOfSaleInformation.entryMode
- pointOfSaleInformation.serviceCode
- pointOfSaleInformation.terminalCapability
- pointOfSaleInformation.terminalID (request)
- pointOfSaleInformation.terminalPinCapability
- pointOfSaleInformation.trackData
- processingInformation.authorizationOptions. aggregatedAuthIndicator
- processingInformation.authorizationOptions.authIndicator
- processingInformation.authorizationOptions. debtRecoveryIndicator
- processingInformation.authorizationOptions. deferredAuthIndicator
- processingInformation.authorizationOptions.ignoreAvsResult
- processingInformation.authorizationOptions.ignoreCvResult
- processingInformation.authorizationOptions.initiator. credentialStoredOnFile
- processingInformation.authorizationOptions.initiator. merchantInitiatedTransaction.previousTransactionID
- processingInformation.authorizationOptions.initiator. merchantInitiatedTransaction.reason
- processingInformation.authorizationOptions.initiator. storedCredentialUsed
- processingInformation.authorizationOptions.initiator.type
- processingInformation.authorizationOptions.transportationMode
- processingInformation.capture
- processingInformation.captureOptions.dateToCapture
- processingInformation.commerceIndicator
- processingInformation.industryDataType
- reversalInformation.amountDetails.currency
- reversalInformation.amountDetails.totalAmount
- reversalInformation.reason

On This Page

SCMP API | Visa Platform Connect

Message-Level Validation

Message-level validation (MLV) is a script-based field-level validation against Cybersource 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.

Cybersource validates the results by:

Cross edit checks.

Data element validation.

Interchange compliance.

Data mapping validation.

Back to top