Payment Administration (Subsystem*)

The Payment Administration Subsystem (PAS) provides general payment administration capabilities and supports the electronic transfer of authenticated funds from the customer to the transportation system operator or other service provider. Charges can be recorded for tolls, vehicle-mileage charging, congestion charging, or other goods and services. This subsystem supports traveler enrollment and collection of both pre-payment and post-payment transportation fees in coordination with the existing, and evolving financial infrastructure supporting electronic payment transactions. The system may establish and administer escrow accounts depending on the clearinghouse scheme and the type of payments involved. This subsystem posts a transaction to the customer account and generates a bill (for post-payment accounts), debits an escrow account, or interfaces to the financial infrastructure to debit a customer designated account. It supports communications with the Roadway Payment Subsystem to support fee collection operations. As an alternative, a wide-area wireless interface can be used to communicate directly with vehicle equipment. The subsystem also sets and administers the pricing structures and includes the capability to implement road pricing policies in coordination with the Traffic Management Subsystem. The electronic financial transactions in which this subsystem is an intermediary between the customer and the financial infrastructure shall be cryptographically protected and authenticated to preserve privacy and ensure authenticity and auditability.

Functionality
Inputs/Outputs
Security
Subsystem Interfaces Diagram
Terminator Interfaces Diagram

Subsystem Interfaces Diagram

This is a context diagram for the entity Payment Administration Subsystem that shows the interfaces to subsystems and every architecture flow that this entity sends or receives, as defined in the National ITS Architecture. A complete list of all architecture flows shown on this diagram, is available under the Inputs/Outputs section on this page.

Get the Source Graphic, a Enhanced Windows Metafile (EMF), in ZIP format.

Terminator Interfaces Diagram

Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.

Security Considerations:

The primary security consideration for the Payment Administration Subsystem is related to the financial information collected from the field and exchanged between other agencies using common electronic payment media that needs to have a relatively high degree of confidentiality in order to safeguard the information. Additional security sensitivity is for the personal information associated with electronic accounts. In addition, it is important that the information is available to the Payment Administration Subsystem in order to ensure that payments are properly accounted for. The integrity of the information is also important to consider in order to prevent disruption of fee collection operations.

Functionality: Equipment Packages* and PSpecs*

Center VMT Payment Administration (Equipment Package*)
PSpecs:
- 7.6.1.2-Calculate Vehicle VMT Charges
- 7.6.1.4-Manage VMT Price Data
- 7.6.1.5-Manage VMT Processing
- 7.6.5-Exchange VMT Data with Other Payment Administration
- 7.6.6.1-Provide VMT Services User Interface
- 7.6.8-Provide VMT Enforcement Interface
Toll Administration (Equipment Package*)
PSpecs:
- 5.4.2-Process Violations for Tolls
- 7.1.1.3-Manage Bad Toll Payment Data
- 7.1.1.6-Collect Probe Data From Toll Transactions
- 7.1.1.7-Update Toll Price Data
- 7.1.1.8-Register for Advanced Toll Payment
- 7.1.1.9-Manage Toll Processing
- 7.1.8-Exchange Data with Other Payment Administration
Toll Data Collection (Equipment Package*)
PSpecs:
- 7.1.1.11-Manage Toll Archive Data
Toll Operator Alert (Equipment Package*)
PSpecs:
- 7.1.1.9-Manage Toll Processing

Inputs/Outputs: Architecture Flows* and Data Flows*

Archived Data Management Payment Administration

archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*:
- toll_archive_request
archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
- toll_archive_status

DMV Payment Administration

registration (Architecture Flow*) - Registered owner of vehicle and associated vehicle information.
Data Flows*:

Emergency Management Payment Administration

alert notification (Architecture Flow*) - Notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The flow identifies the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This flow may also identify specific information that should not be released to the public.
Data Flows*:
- wide_area_alert_notification_for_tolls
toll service change request (Architecture Flow*) - Request to change pricing, modify restrictions, or modify operations of a toll road facility
Data Flows*:
- evacuation_toll_change_request

Financial Institution Payment Administration

transaction status (Architecture Flow*) - Response to transaction request. Normally dealing with a request for payment.
Data Flows*:

Fleet and Freight Management Payment Administration

toll data request (Architecture Flow*) - Request made to obtain toll schedule information or pay a toll in advance. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
Data Flows*:
- cvo_advanced_toll_request
- cvo_toll_price_request

Information Service Provider Payment Administration

toll data request (Architecture Flow*) - Request made to obtain toll schedule information or pay a toll in advance. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
Data Flows*:

Other Payment Administration Payment Administration

toll coordination (Architecture Flow*) - This flow supports reciprocity between toll agencies/service centers by exchanging information that supports reconciliation of toll charges by customers that are enrolled with other toll service centers. In addition to toll charge reconciliation, exchanged information may include toll schedule information, customer information and other toll service information that is coordinated between toll agencies or centers.
Data Flows*:
- fopa-toll_charges_reconciliation_data
- fopa-toll_pricing_data
VMT payment coordination (Architecture Flow*) - Coordinate apportionment of VMT data or charges between jurisdictions (e.g. federal government, states, various jurisdictions that might be public or private within a state). Apportionment reconciliation includes either sharing information about VMT data in other jurisdictions (so that the Other Payment Administration subsystems can make appropriate charges), or sharing revenue collected. When sharing revenue, this flow also includes VMT charging rate policies
Data Flows*:
- fopa-vmt_coordination_data

Payment Administration Archived Data Management

toll archive data (Architecture Flow*) - Data indicating toll facility usage and pricing schedules. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
- toll_archive_data

Payment Administration DMV

license request (Architecture Flow*) - Request supporting registration data based on license plate read during violation.
Data Flows*:

Payment Administration Emergency Management

alert status (Architecture Flow*) - Information indicating the current status of the emergency alert including identification of the traveler and driver information systems that are being used to provide the alert.
Data Flows*:
- alert_notification_status_from_tolls
toll service change response (Architecture Flow*) - Response to toll service change requests indicating level of compliance with request.
Data Flows*:
- evacuation_toll_change_response

Payment Administration Enforcement Agency

payment violation notification (Architecture Flow*) - Notification to enforcement agency of a toll, parking, or transit fare payment violation.
Data Flows*:
- tea-toll_violation_data
- tea-vmt_equipment_failure

Payment Administration Financial Institution

payment request (Architecture Flow*) - Request for payment from financial institution.
Data Flows*:

Payment Administration Fleet and Freight Management

toll data (Architecture Flow*) - Current toll schedules for different types of vehicles as well as advanced toll payment information.
Data Flows*:
- cvo_advanced_toll_confirmation
- cvo_toll_price

Payment Administration Information Service Provider

toll data (Architecture Flow*) - Current toll schedules for different types of vehicles as well as advanced toll payment information.
Data Flows*:
toll probe data (Architecture Flow*) - Aggregate probe data derived from electronic toll collection operations. Data collected could include vehicle speeds and travel times for a given link or collection of links.
Data Flows*:
- toll_probe_data_for_isp
VMT data for ISP (Architecture Flow*) - Road use charge rate policies for distribution to travelers.
Data Flows*:
- vmt_price_data

Payment Administration Other Payment Administration

toll coordination (Architecture Flow*) - This flow supports reciprocity between toll agencies/service centers by exchanging information that supports reconciliation of toll charges by customers that are enrolled with other toll service centers. In addition to toll charge reconciliation, exchanged information may include toll schedule information, customer information and other toll service information that is coordinated between toll agencies or centers.
Data Flows*:
- topa-toll_charges_reconciliation_data
- topa-toll_pricing_data
VMT payment coordination (Architecture Flow*) - Coordinate apportionment of VMT data or charges between jurisdictions (e.g. federal government, states, various jurisdictions that might be public or private within a state). Apportionment reconciliation includes either sharing information about VMT data in other jurisdictions (so that the Other Payment Administration subsystems can make appropriate charges), or sharing revenue collected. When sharing revenue, this flow also includes VMT charging rate policies
Data Flows*:
- topa-vmt_coordination_data

Payment Administration Roadway Payment

toll advisories (Architecture Flow*) - Alerts and advisories provided to toll plazas to keep toll operators informed of identified threats that may impact toll operations or public safety on a toll facility.
Data Flows*:
- alert_notification_for_toll_operator
toll instructions (Architecture Flow*) - Information provided to configure and support toll plaza operations including toll pricing information.
Data Flows*:
vehicle payment request (Architecture Flow*) - Request for information supporting toll and parking payments.
Data Flows*:
- vmt_payment_request_to_field
- vmt_vehicle_payment_data_clear_to_field

Payment Administration Traffic Management

toll probe data (Architecture Flow*) - Aggregate probe data derived from electronic toll collection operations. Data collected could include vehicle speeds and travel times for a given link or collection of links.
Data Flows*:
- toll_probe_data_for_traffic
toll service change response (Architecture Flow*) - Response to toll service change requests indicating level of compliance with request.
Data Flows*:
- toll_price_changes_response
- toll_price_direct_details

Payment Administration Vehicle

vehicle payment request (Architecture Flow*) - Request for information supporting toll and parking payments.
Data Flows*:
- vmt_payment_request_from_admin
- vmt_vehicle_payment_data_clear_from_admin
VMT cost data (Architecture Flow*) - VMT charges per link.
Data Flows*:
- vmt_cost_data

Payment Administrator Payment Administration

payment administration requests (Architecture Flow*) - Personnel inputs that control system operations, including requests to change toll fees, confirmation that alerts should be provided to toll operators, management of VMT charge policies and management of VMT account processing, etc.
Data Flows*:

Personal Information Access Payment Administration

traveler payment information (Architecture Flow*) - Payment information for road use charges.
Data Flows*:
- traveler_personal_vmt_payment_info
user VMT account setup (Architecture Flow*) - Billing information, vehicle information (or registration information), and requests for reports.
Data Flows*:
- traveler_personal_vmt_account_setup_info

Remote Traveler Support Payment Administration

traveler payment information (Architecture Flow*) - Payment information for road use charges.
Data Flows*:
- traveler_vmt_payment_info
user VMT account setup (Architecture Flow*) - Billing information, vehicle information (or registration information), and requests for reports.
Data Flows*:
- traveler_vmt_account_setup_info

Roadway Payment Payment Administration

toll transactions (Architecture Flow*) - Detailed list of transactions from a toll station.
Data Flows*:
vehicle payment information (Architecture Flow*) - Information provided for payment of tolls and parking fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested.
Data Flows*:
- vmt_payment_collected_from_field
- vmt_payment_confirmation_from_field
VMT data (Architecture Flow*) - A vehicle’s road use history that records where the vehicle has traveled over time. Optionally includes vehicle speeds as well as distance traveled for some applications. Information is accurate enough to distinguish between adjacent roads, adjacent lanes, and identify direction of travel on the roads.
Data Flows*:
- vehicle_identity_for_vmt_from_roadway
- vehicle_location_for_vmt_from_roadway
VMT equipment fault (Architecture Flow*) - Provides fault status of the VMT data collection equipment in a vehicle and vehicle image and other characteristics to allow independent identification of the vehicle and its owner.
Data Flows*:

Traffic Management Payment Administration

toll service change request (Architecture Flow*) - Request to change pricing, modify restrictions, or modify operations of a toll road facility
Data Flows*:
- toll_price_changes_request
- toll_price_direct_request

Vehicle Payment Administration

vehicle payment information (Architecture Flow*) - Information provided for payment of tolls and parking fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested.
Data Flows*:
- vmt_payment_collected_for_admin
- vmt_payment_confirmation_for_admin
VMT data (Architecture Flow*) - A vehicle’s road use history that records where the vehicle has traveled over time. Optionally includes vehicle speeds as well as distance traveled for some applications. Information is accurate enough to distinguish between adjacent roads, adjacent lanes, and identify direction of travel on the roads.
Data Flows*: