Traveler Support Equipment --> Payment Device:
request for payment
Definitions
request for payment (Information Flow): Request to deduct cost of service from user's payment account.
Traveler Support Equipment (Source Physical Object): 'Traveler Support Equipment' provides access to traveler information at transit stations, transit stops, other fixed sites along travel routes (e.g., rest stops, merchant locations), and major trip generation locations such as special event centers, hotels, office complexes, amusement parks, and theaters. Traveler information access points include kiosks and informational displays supporting varied levels of interaction and information access. At transit stops this might be simple displays providing schedule information and imminent arrival signals. This may be extended to include multi-modal information including traffic conditions and transit schedules to support mode and route selection at major trip generation sites. Personalized route planning and route guidance information can also be provided based on criteria supplied by the traveler. It also supports service enrollment and electronic payment of transit fares. In addition to the traveler information provision, it also enhances security in public areas by supporting traveler activated silent alarms.
Payment Device (Destination Physical Object): The 'Payment Device' enables the electronic transfer of funds from the user of a service (I.e. a traveler) to the provider of the service. Potential implementations include smart cards that support payment for products and services, including transportation services and general purpose devices like smart phones that support a broad array of services, including electronic payment. In addition to user account information, the payment device may also hold and update associated user information such as personal profiles, preferences, and trip histories.
Included In
This Triple is in the following Service Packages:
- PT04: Transit Fare Collection Management
- TI06: Shared Use Mobility and Dynamic Ridesharing
- TI09: Travel Services Information and Reservation
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
- tpd-debited_fare_payment_at_roadside
- tpd-debited_traveler_payment_at_roadside
- tpd-debited_traveler_payment_at_roadside_for_transit
- tpd-request_fare_payment_at_roadside
This Triple has the following triple relationships:
Relationship | Source | Destination | Flow |
---|---|---|---|
Interactive | Payment Device | Traveler Support Equipment | actuate secure payment |
Communication Solutions
No communications solutions identified.Characteristics
Characteristic | Value |
---|---|
Time Context | Now |
Spatial Context | Adjacent |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | True |
Interoperability | Description |
---|---|
National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Moderate | Moderate | High | |
Basis | Contains charges and possibly balance or personal information. Charge information may or may not be public, and balance and personal information is not, though it may be displayed visually. Could be LOW if no personal or balance information and no identifier is not included in the flow. | Payment related information needs to be correct or the user may be inconvenienced or defrauded. | Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |