# Transit
source: https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/trans-enrich-data/cardholder-present-data/transit/index.md

## Overview {#overview}

The Transit implementation refers to the customer Card Present Mastercard Gateway implementation.

Each scheme has specific requirements for transit and covers the API requests required to ensure that transactions are performed in accordance with those scheme requirements.

### Card acceptor business code (Merchant Category Codes) for transit merchants {#card-acceptor-business-code-merchant-category-codes-for-transit-merchants}

* 4111 Transportation - Suburban and Local Commuter Passenger, including Ferries
* 4112 Passenger Railways
* 4131 Bus Lines
* 4784 Bridge and Road Fees, Tolls
* 7523 Automobile Parking Lots and Garages

The acquirer advises which card acceptor business code is most appropriate for the merchant's transit implementation.

## Supported schemes {#supported-schemes}

* Mastercard
* Visa
* American Express

## Transit deployment models {#transit-deployment-models}

Mastercard Gateway supports two transit deployment models:

* Known Fare This is the simplest of the deployment model:

<!-- -->

* Mastercard - Retail-Like Acceptance
* Visa - Known Fare Transaction
* American Express - Pay in Advance

<!-- -->

* Aggregation The aggregation model is designed for situations where the final fare is not known at the time of travel. Instead, the fare is calculated at the end of a predefined travel period, typically 24 hours, based on the journeys made during that period.

<!-- -->

* Mastercard - Pay As You Go
* Visa - Mobility and Transport Transaction model (MTT)
* American Express - Pay As You Go