• About
  • Connected Vehicle
  • Architecture
  • Approach
  • Viewpoints
  • Security
• Applications
• Views
  • Enterprise
  • Functional
  • Physical
  • Communications
• Standards
  • CV Standards
  • CV Standards Plan
• Resources
  • Databases
  • Diagrams
  • Documents
  • Presentations
  • Tools
  • Training
• Glossary
  • Acronyms
• Contact Us

7.3.5: Provide Transit Vehicle Payment Device Interface

This process shall be responsible for providing the interface through which the payment information can be read from a traveler card. The process shall support the reading of this data from travelers embarking on-board transit vehicles, for use in paying the current transit fare, and if required, advanced payments. The process shall support advanced payments for tolls, and/or parking lot charges, and/or transit fares. It shall be possible for the process to collect either the credit identity or the stored credit value data from the traveler card, and to update the stored credit value as a result of the fare and (possibly) advanced charges having been paid.

This process is associated with the Transit Vehicle OBE physical object.

This process is associated with the following application objects:

• Transit Vehicle On-Board Fare Management

This process is associated with the following data flows:

• fpd-confirm_fare_payment_on_transit_vehicle - In
• fpd-transit_vehicle_tag_data - In
• fpd-traveler_passenger_personal_information - In
• tpd-debited_payment_on_transit_vehicle - Out
• tpd-request_fare_payment_on_transit_vehicle - Out
• tpd-traveler_passenger_information_update - Out
• transit_vehicle_fare_payment_confirmation - Out
• transit_vehicle_fare_payment_debited - In
• transit_vehicle_fare_payment_request - In
• traveler_vehicle_tag_data - Out