Back to productDownload detailed guide
Pars HadishDetailed product introduction · 1

Product concept

University transport payment concept

Product introduction

The Pars Hadish university transport payment concept provides a way to collect and track university shuttle fares by route and work shift.

Under this concept, each payment request is linked to its route and shift, and its result is displayed as approved, declined, or unresolved. This distinction helps drivers and support staff identify the payment status and review cases that require follow-up.

University transport payment conceptPage 1 / 7
Pars HadishDetailed product introduction · 2

Product concept

University transport payment concept

Product introduction (continued)

For example, if no conclusive response is received during fare payment, the transaction remains unresolved, and the next request is blocked until its result is established. An uncertain payment result is therefore treated separately from a declined payment.

University transport payment conceptPage 2 / 7
Pars HadishDetailed product introduction · 3

University transport payment concept

Product features and capabilities

Payment association with route and shift
Identify the route and shift associated with each request.
Fare payment request
Start the fare collection process during the active shift.
Payment status display
Distinguish approved, declined, and unresolved results.
Subsequent request control
Block a new request until the outcome of the unresolved payment has been established.
Unresolved payment tracking
Check the result through the connected inquiry service.
University transport payment conceptPage 3 / 7
Pars HadishDetailed product introduction · 4

University transport payment concept

Users and applications

University transport managers
Oversee shuttle fare collection
Shuttle drivers
Start shifts and view payment request results
Support staff
Review and follow up on unresolved payments
University transport payment conceptPage 4 / 7
Pars HadishDetailed product introduction · 5

University transport payment concept

Product images

Campus payment report preview

Original product interfaceCampus payment report preview
Original university pilot report in the application’s own acceptance preview mode. Amounts and states come from its built-in test fixture. This is a backoffice view, not execution of a card payment.

The data shown in this image is synthetic test data.

University transport payment conceptPage 5 / 7
Pars HadishDetailed product introduction · 6

University transport payment concept

Product images

Synthetic transaction report

Original product interfaceSynthetic transaction report
Original university backoffice transaction report with three fictional confirmed, declined and unknown results. Every API response is mocked locally. This is a backoffice view; no card payment or real inquiry was performed.

The data shown in this image is synthetic test data.

University transport payment conceptPage 6 / 7
Pars HadishDetailed product introduction · 7

University transport payment concept

Product images

Backoffice rate card management

Original product interfaceBackoffice rate card management
Original pilot backoffice rate card page with two fictional management cards. These select a line and fare; they are not ticket payment cards. The image shows backoffice administration only, with no card operation performed.

The data shown in this image is synthetic test data.