'PAC Payment Administration' provides administration and management of payments associated with electronic toll collection, parking payments, and other e–payments. It provides the back office functions that support enrollment, pricing, reduced fare eligibility, payment reconciliation with financial institutions, and violation notification to enforcement agencies. It also supports dynamic pricing to support demand management, allow/block–list management and token validation.
| ID | Requirement | User Defined |
|---|
| 1 | The center shall manage toll transactions, including maintaining a log of all transactions and toll pricing structure information. | False |
|---|
| 2 | The center shall dynamically price tolls based on current traffic condition information. | False |
|---|
| 3 | The center shall provide secure user account management, providing user access to rules and policies, current billing status, invoices, payments, and mechanisms for review and challenge of the collected data. | False |
|---|
| 4 | The center shall register vehicles for road or parking use payment, establishing accounts that identify owner billing information and preferences. | False |
|---|
| 5 | For electronic toll payments requiring financial payment, the center shall process the financial information from ITS roadway payment equipment and manage an interface to a Financial Institution. | False |
|---|
| 6 | The center shall manage a local billing database for toll customers. | False |
|---|
| 7 | The center shall manage the details of toll payment violations based on vehicle information from the ITS roadway payment equipment, registration information from the Department of Motor Vehicles, invalid payment information from a Financial Institution, and previous violation information stored locally, and report such violations to appropriate law enforcement agencies. | False |
|---|
| 8 | The center shall calculate traffic flow based on timestamped toll transactions for vehicle travel between successive toll plazas and send to other agencies. | False |
|---|
| 9 | The center shall respond to changes in toll prices from the Payment Administrator. | False |
|---|
| 10 | The center shall exchange data with other payment administration agencies to coordinate toll transactions and pricing. | False |
|---|
| 11 | The center shall report payment violations including vehicle information and vehicle image to the designated Enforcement Agency. | False |
|---|
| 12 | The center shall register users for an electronic payment system, establishing accounts that identify owner billing information and preferences. | False |
|---|
| 13 | The center shall provide secure user account management for the electronic payment system, providing user access to rules and policies, current billing status, invoices, payments, and mechanisms for review and challenge of the collected data. | False |
|---|
| 14 | This center shall maintain and publish the prices for the electronic payment system. | False |
|---|
| 15 | The center shall provide the HOT pricing information, including variable pricing based on calendar, time of day, vehicle type and passenger occupancy. | False |
|---|
| 16 | The center shall receive traveler payment information and compute the cost of using the portion of the transportation system. | False |
|---|
| 17 | The center shall process and clear payments from travelers and vehicle owners. | False |
|---|
| 18 | The center shall coordinate with payment administration centers that serve as a clearing house for a regional payment system in order to perform payment reconciliation. | False |
|---|
| 19 | The center shall exchange data with other payment administration centers in order to coordinate electronic payments systems use and pricing. | False |
|---|
| 20 | The center shall report enforcement agency of detected HOV or HOT lane entry violations including vehicle information and documents the lane parameter that was violated. | False |
|---|
| 21 | The center shall provide toll pricing information to other transportation centers. | False |
|---|
| 22 | The center shall exchange data with emergency centers to coordinate the modification of tolls in specific circumstances. | False |
|---|
| 23 | The center shall collect customer usage and billing information from the electric utility. | False |
|---|
| 24 | The center shall calculate the cost of a complete trip according to a trip plan, accommodating multiple modes if the trip plan uses more than one mode. | False |
|---|
| 25 | The center shall be able to authenticate and charge transactions with financial institutions. | False |
|---|
| 26 | The center shall be able to charge trips to managed accounts. | False |
|---|
| 27 | The center shall provide a bank card / fare pair to a financial processor for conditional approval of fare payment. | False |
|---|
| 28 | The center shall approve charges based on a pre–existing white/black list. | False |
|---|
| 29 | The Payment Processor needs to collect and aggregate charges over a time period. | False |
|---|
| 30 | The Payment Processor needs to provide process charges with financial institutions as a batch process. | False |
|---|
| 31 | The Payment Processor needs to learn when a card has been lost. | False |
|---|
| 32 | The Payment Processor needs to learn when a card has been used fraudulently. | False |
|---|
| 33 | The center shall access service metrics for all modes of transport for which they bill. Relevant metrics may include service cost, availability, allowed payments, fare caps and discounts. | False |
|---|
| 34 | The center shall provide fare payment to the transport provider when payment for travel on the transport provider vehicles is made with a regional payment system. | False |
|---|
| 35 | The center shall discount a traveler's rate for different segments of a multimodal trip based on the eligibility of the traveler. | False |
|---|