3.1 Electronic Payment Services (User Service*)

The Electronic Payment Services user service allows travelers to pay for transportation services with a common electronic payment medium for all transportation modes and functions. Electronic toll collection, transit fare payment, and parking payment would be linked through a multimodal multi-use electronic system. A common transportation service fee payment structure could be used with all modes, possibly tying into roadway pricing options.

User Service Requirements*:
3.1.0 ITS shall include an Electronic Payment capability. Electronic Payment Services allows travelers to pay for transportation services by electronic means. Four functions are provided, which are, (1) Electronic Toll Collection, (2) Electronic Fare Collection, (3) Electronic Parking Payment, and (4) Electronic Payment Services Integration.
PSpecs*: 1.4.2 , 1.4.4 , 1.4.5 , 4.5.4 , 4.6.1 , 4.6.2 , 4.6.3 , 4.6.4 , 4.6.5 , 4.6.6 , 4.6.7 , 4.7.2.1 , 4.7.2.2 , 4.7.2.3 , 4.7.2.4 , 4.7.2.5 , 4.7.2.6 , 4.7.2.7 , 5.4.2 , 5.4.3 , 5.4.4 , 5.4.5 , 5.4.6 , 5.4.7 , 6.5.8 , 7.1.1.1 , 7.1.1.10 , 7.1.1.2 , 7.1.1.3 , 7.1.1.4 , 7.1.1.5 , 7.1.1.6 , 7.1.1.7 , 7.1.1.8 , 7.1.1.9 , 7.1.2 , 7.1.3 , 7.1.4 , 7.1.5 , 7.1.6 , 7.1.7 , 7.1.8 , 7.2.1.1 , 7.2.1.10 , 7.2.1.2 , 7.2.1.3 , 7.2.1.4 , 7.2.1.5 , 7.2.1.6 , 7.2.1.7 , 7.2.1.8 , 7.2.1.9 , 7.2.2 , 7.2.3 , 7.2.4 , 7.2.5 , 7.2.6 , 7.2.7 , 7.3.1.1 , 7.3.1.2 , 7.3.1.3 , 7.3.1.4 , 7.3.1.5 , 7.3.1.6 , 7.3.1.7 , 7.3.2 , 7.3.3 , 7.3.4 , 7.3.5 , 7.4.1.1 , 7.4.1.3 , 7.4.1.5 , 7.4.1.6 , 7.4.1.7 , 7.4.2 , 7.4.3 , 7.5.1 , 7.5.2 , 7.5.3 , 7.5.4 , 7.6.1.1 , 7.6.1.2 , 7.6.1.3 , 7.6.1.4 , 7.6.1.5 , 7.6.2 , 7.6.3 , 7.6.4 , 7.6.5 , 7.6.6.1 , 7.6.6.2 , 7.6.6.3 , 7.6.7 , 7.6.8
3.1.1 Electronic Payment shall provide an Electronic Toll Collection (ETC) capability.
PSpecs*: 4.6.1 , 4.7.2.1 , 5.4.2 , 5.4.3 , 5.4.4 , 5.4.5 , 5.4.6 , 5.4.7 , 6.5.8 , 7.1.1.1 , 7.1.1.10 , 7.1.1.2 , 7.1.1.3 , 7.1.1.4 , 7.1.1.5 , 7.1.1.6 , 7.1.1.7 , 7.1.1.8 , 7.1.2 , 7.1.3 , 7.1.4 , 7.1.5 , 7.2.6 , 7.6.1.1 , 7.6.1.2 , 7.6.1.3 , 7.6.1.4 , 7.6.1.5 , 7.6.2 , 7.6.3 , 7.6.6.1 , 7.6.6.2 , 7.6.6.3 , 7.6.7 , 7.6.8
3.1.1.1 ETC shall provide the capability for vehicle operators to pay tolls without stopping their vehicles.
PSpecs*: 7.1.1.1 , 7.1.1.10 , 7.1.1.2 , 7.1.1.5 , 7.1.1.6 , 7.1.1.8 , 7.1.4 , 7.6.1.1 , 7.6.1.2 , 7.6.1.3 , 7.6.1.5 , 7.6.3 , 7.6.6.1 , 7.6.6.2 , 7.6.6.3 , 7.6.7 , 7.6.8
3.1.1.2 ETC shall provide the capability to implement pricing structures for locally determined needs.
PSpecs*: 6.5.8 , 7.1.1.2 , 7.1.1.7 , 7.6.1.2 , 7.6.1.4 , 7.6.1.5
3.1.1.3 ETC shall provide confirmation of the transaction to each customer.
PSpecs*: 7.1.2 , 7.1.4 , 7.2.6 , 7.6.3 , 7.6.6.1 , 7.6.6.2 , 7.6.6.3
3.1.1.4 ETC shall include the capability to identify those vehicles and/or operators that violate its toll collection process.
PSpecs*: 5.4.2 , 5.4.3 , 5.4.4 , 5.4.5 , 5.4.6 , 5.4.7 , 7.1.1.3 , 7.1.1.6 , 7.1.3 , 7.1.5 , 7.6.2 , 7.6.7 , 7.6.8
3.1.1.5 ETC shall accommodate single billing to commercial carriers.
PSpecs*: 7.1.1.3 , 7.1.1.4
3.1.1.6 ETC shall provide the capability to automatically access and process each commercial vehicle's required documentation.
PSpecs*: 7.1.1.1 , 7.1.1.2 , 7.1.1.6 , 7.6.1.1
3.1.1.7 ETC shall be implemented in a manner that reduces the cost of toll collection.
PSpecs*: 7.1.4 , 7.6.3 , 7.6.7 , 7.6.8
3.1.1.8 ETC shall be implemented in a manner that seeks to minimize the opportunities for fraud.
PSpecs*: 7.1.1.5 , 7.1.5 , 7.6.1.3 , 7.6.8
3.1.2 Electronic Payment shall include an Electronic Fare Collection (EFC) capability.
PSpecs*: 4.6.1 , 4.6.2 , 4.6.3 , 4.6.4 , 4.6.5 , 4.6.6 , 4.6.7 , 4.7.2.1 , 4.7.2.2 , 4.7.2.3 , 4.7.2.4 , 4.7.2.5 , 4.7.2.6 , 4.7.2.7 , 7.1.6 , 7.2.6 , 7.3.1.1 , 7.3.1.2 , 7.3.1.3 , 7.3.1.4 , 7.3.1.5 , 7.3.1.6 , 7.3.1.7 , 7.3.2 , 7.3.3 , 7.4.1.7 , 7.4.2 , 7.4.3
3.1.2.1 EFC shall be implemented in a manner that the traveler is able to use a compatible fare medium for all applicable surface transportation services.
PSpecs*: 4.6.1 , 4.7.2.4 , 7.1.6 , 7.2.6 , 7.3.1.1 , 7.3.1.2 , 7.3.1.3 , 7.3.1.4 , 7.3.1.5 , 7.3.1.6 , 7.3.2 , 7.4.1.7
3.1.2.2 EFC shall provide the capability to implement variable and flexible fare structures.
PSpecs*: 4.6.1 , 4.6.3 , 4.6.6 , 4.7.2.3 , 4.7.2.4 , 4.7.2.7 , 7.3.1.2 , 7.4.1.7
3.1.2.3 EFC shall be capable of identifying voided and/or invalid payment media.
PSpecs*: 4.6.1 , 4.6.4 , 4.6.7 , 4.7.2.4 , 4.7.2.5 , 7.3.1.3 , 7.3.1.5 , 7.3.1.6
3.1.2.4 EFC shall provide the capability for third party payment of transportation services.
PSpecs*: 4.6.1 , 4.7.2.4 , 7.2.6 , 7.3.1.1 , 7.3.1.4 , 7.4.3
3.1.2.5 For those systems requiring special eligibility, EFC shall provide the capability to verify the eligibility of riders.
PSpecs*: 4.6.1 , 4.7.2.4 , 7.3.1.3 , 7.3.1.6 , 7.3.3
3.1.2.6 EFC shall be implemented in a manner that permits expansion into other uses for the payment medium such as payment of retail, telephone, etc.
PSpecs*: 4.6.1 , 4.6.5 , 4.7.2.4 , 4.7.2.6 , 7.3.1.7 , 7.4.3
3.1.2.7 EFC shall include the capability to collect the data required to determine accurate ridership levels.
PSpecs*: 4.6.1 , 4.6.2 , 4.6.6 , 4.7.2.1 , 4.7.2.2 , 4.7.2.4 , 4.7.2.7 , 7.4.2
3.1.2.8 EFC shall provide the capability for passengers to pay fares without stopping.
PSpecs*: 4.6.1 , 4.7.2.1 , 7.3.1.1 , 7.3.1.2 , 7.3.1.4 , 7.3.1.5
3.1.3 Electronic Payment shall include an Electronic Parking Payment (EPP) capability.
PSpecs*: 4.5.4 , 7.1.6 , 7.1.7 , 7.2.1.1 , 7.2.1.10 , 7.2.1.2 , 7.2.1.3 , 7.2.1.4 , 7.2.1.5 , 7.2.1.6 , 7.2.1.7 , 7.2.1.8 , 7.2.2 , 7.2.3 , 7.2.5 , 7.2.7 , 7.3.4 , 7.3.5 , 7.4.3 , 7.5.1 , 7.5.2 , 7.5.3 , 7.5.4 , 7.6.4
3.1.3.1 EPP shall provide the capability to pay for parking without the use of cash.
PSpecs*: 7.1.6 , 7.1.7 , 7.2.1.1 , 7.2.1.2 , 7.2.1.3 , 7.2.1.4 , 7.2.1.5 , 7.2.1.6 , 7.2.1.7 , 7.2.1.8 , 7.2.2 , 7.2.5 , 7.2.7 , 7.3.4 , 7.3.5 , 7.5.1 , 7.5.2 , 7.5.3 , 7.5.4 , 7.6.4
3.1.3.2 EPP shall include the capability for transit operators to utilize a single medium to charge for both transit related charges and parking charges.
PSpecs*: 4.5.4 , 7.2.1.10 , 7.2.1.4 , 7.2.1.8 , 7.4.3
3.1.3.3 EPP shall provide the capability to provide flexible pricing parking fee structures based upon factors including, but not limited to, vehicle classification.
PSpecs*: 7.2.1.2 , 7.2.1.7 , 7.2.5
3.1.4 ITS shall include an Electronic Payment Services Integration (EPSI) feature.
PSpecs*: 4.6.1 , 4.6.2 , 4.7.2.1 , 4.7.2.2 , 7.1.1.9 , 7.1.8 , 7.2.1.10 , 7.2.1.8 , 7.2.1.9 , 7.2.4 , 7.2.6 , 7.3.1.4 , 7.3.2 , 7.4.1.1 , 7.4.1.3 , 7.4.1.5 , 7.4.1.6 , 7.4.2 , 7.4.3 , 7.6.1.5 , 7.6.5
3.1.4.1 EPSI shall provide the capability to combine electronic payments made for use of various transportation modes into a single integrated system.
PSpecs*: 7.2.1.10 , 7.2.1.8 , 7.2.4 , 7.2.6 , 7.3.2 , 7.4.1.1 , 7.4.3
3.1.4.2 EPSI shall provide the capability to integrate fare and toll pricing structures of multiple agencies.
PSpecs*: 7.1.8 , 7.3.2 , 7.4.3 , 7.6.5
3.1.4.3 EPSI shall collect and provide usage data to develop pricing strategies that favor certain transportation modes or routes.
PSpecs*: 4.6.1 , 4.6.2 , 4.7.2.1 , 4.7.2.2 , 7.1.1.9 , 7.2.1.9 , 7.4.2 , 7.6.1.5
3.1.4.4 EPSI shall be implemented in a manner that ensures that it may be deployed across multiple agency political boundaries without degrading the services it provides.
PSpecs*: 7.1.8 , 7.2.4 , 7.6.5
3.1.5 ITS shall provide a Roadway Pricing (RP) capability.
PSpecs*: 1.4.2 , 1.4.4 , 1.4.5 , 7.4.2
3.1.5.1 RP shall provide the capability to implement various road pricing policies.
PSpecs*: 1.4.2 , 1.4.4 , 1.4.5 , 7.4.2
3.1.5.1.1 Road pricing policies capable of being implemented by RP shall include variable pricing.
PSpecs*: 1.4.2 , 1.4.4 , 1.4.5 , 7.4.2
3.1.5.2 RP shall provide the capability to implement roadway pricing strategies, developed by other services, that alleviate congestion.
PSpecs*: 1.4.2 , 1.4.4 , 1.4.5 , 7.4.2
3.1.5.3 RP shall provide the capability to implement roadway pricing, developed by other services, that can be used to influence mode selection.
PSpecs*: 1.4.2 , 1.4.4 , 1.4.5 , 7.4.2