JP7626635B2 - Payment operation system, vehicle-mounted device for payment operation system, and payment operation program - Google Patents

Description

The present invention relates to a payment operation system applied to payments for taxis, etc., an in-vehicle device for the payment operation system, and a payment operation program.

Various technologies have been proposed for taxi meters (on-board devices) connected to a network that can be applied to payment operations in taxis (Patent Document 1).
For example, there are cases where payment is carried out using a plurality of payment devices linked to a taxi meter.

In addition, there has been an increase in the number of people making online payments using tablet-type information terminals (such as dispatch tablets) equipped with a dispatch application (dispatch app) that allows them to request a taxi dispatch via a communication line.

For example, one type of payment operation system calculates the fare from the distance and time traveled using a taxi meter. The fare is then displayed on the meter display, and the fare information is sent to a connected payment device (e.g., a dispatch tablet, a dedicated payment machine, etc.) to share the fare information.

Regarding payment methods, general taxi meters allow "cash payment" and "taxi ticket payment." Also, "dispatch tablets" often allow "online payment" via a network. Furthermore, dedicated payment machines may allow "card payment,""electronic money payment," etc.
Based on the amount information received by the payment system, the payment of the taxi fare, etc. is carried out by operating each payment device.

Special table 2016-501407 publication

However, when payment processing is performed on multiple payment devices, there is a problem in that a duplicate payment is mistakenly made on one payment device even though the other payment device has already processed the same transaction.

That is, for example, a case may occur where a reservation for online payment has been made in advance using the dispatch tablet, but payment is mistakenly made by card using the payment device.

In such cases, there are inconveniences such as problems arising between passengers and the fare-paying passenger due to incorrect payment, or the crew having to cancel or redo the payment operation.

The present invention was made in consideration of the above problems, and aims to provide a payment operation system, an on-board device for the payment operation system, and a payment operation program that can prevent problems and erroneous operations when paying for taxi fares.

The payment operation system according to the present invention includes a dispatch terminal that requests dispatch of a taxi via a communication line, a fare management server that manages fare information for the taxi, an on-board device that is mounted on the taxi and transmits fare information to the fare management server, a fare payment condition input unit that is provided on the dispatch terminal and the on-board device and that inputs the fare payment conditions for the taxi in operation, a fare payment condition determination unit that determines whether each of the fare payment conditions matches a preset specified condition, an invalidation unit that invalidates the fare payment condition that is determined by the fare payment condition determination unit not to match the specified condition, and a payment device that settles the fare for the taxi based on the fare payment condition that is determined to match the specified condition.

The dispatch terminal is preferably configured as a tablet-type information terminal and is equipped with a dispatch application that processes taxi dispatch requests, inputs the fare payment terms for the taxi, transmits the information, and processes the online payment of the fare.

It is preferable that the vehicle-mounted device is configured as a taximeter equipped with a communication unit that communicates with the dispatch terminal and the fare management server, and the payment device.

It is preferable that the fare payment condition determination unit is provided in the fare management server, and the vehicle dispatch terminal or the payment device performs payment processing for the fare based on payment information based on the determination result of the fare payment condition determination unit.

When the fee payment condition determination unit determines that the fee payment conditions do not match the specified conditions, it is preferable that the invalidation unit controls so as not to transmit the payment information to the vehicle dispatch terminal or the payment device into which the fee payment conditions were input.

It is preferable that the invalidation unit controls so that payment operations using cash and taxi tickets cannot be performed when the fee payment condition determination unit determines that the fee payment conditions do not match the predetermined conditions.

An in-vehicle device for a payment operation system according to another aspect of the present invention includes a dispatch terminal that requests dispatch of a taxi via a communication line, a communication unit with a fare management server that manages fare information for the taxi, and a fare payment terms input unit that inputs the fare payment terms for the taxi.

It is preferable to have a fare payment condition determination unit that determines whether the fare payment conditions match predetermined conditions, an invalidation unit that invalidates the fare payment conditions when the fare payment conditions are determined not to match the predetermined conditions, and a payment device that settles the fare for the taxi based on the fare payment conditions when the fare payment conditions are determined to match the predetermined conditions.

A payment operation program according to another aspect of the present invention is executed in a payment operation system, and includes a payment condition input process for inputting the fare payment conditions of the taxis in commercial operation for the dispatch terminal and the on-board device, respectively, a payment condition determination process for determining whether each of the fare payment conditions matches a predetermined condition that has been set in advance, an invalidation process for invalidating the fare payment conditions when it is determined that the fare payment conditions do not match the predetermined condition, and a payment execution process for settling the fare for the taxi based on the fare payment conditions when it is determined that the predetermined condition is met.

The invalidation process preferably controls so that, if it is determined in the fare payment condition determination process that the fare payment conditions do not match the predetermined conditions, payment information is not sent to the vehicle dispatch terminal or payment device into which the fare payment conditions were entered.

It is preferable that the invalidation process controls so that payment operations using cash and taxi tickets cannot be performed if the payment condition determination process determines that the payment conditions do not match the predetermined conditions.

The present invention provides a payment operation system that can prevent problems and erroneous operations when paying for taxi fares, as well as an in-vehicle device and a payment operation program for the payment operation system.

1 is a block diagram showing a schematic configuration of a payment operation system according to an embodiment. 1 is a functional block diagram showing the functional configuration of a payment operation system according to an embodiment. FIG. 1 is a block diagram showing an example of the configuration of a taxi meter applied to the payment operation system according to an embodiment. FIG. 1 is an explanatory diagram showing an example of fare display in the payment operation system of the embodiment. FIG. 13 is a flowchart showing an example of a processing procedure for taxi fare payment processing executed in the payment operation system according to the embodiment. 13 is a flowchart showing an example of a processing procedure for a meter pre-determination cancellation/change process executed in the payment operation system according to the embodiment. 10 is a flowchart showing an example of a processing procedure for a meter payment process executed in the payment operation system according to the embodiment.

With reference to Figures 1 to 7, the payment operation system S1 according to an embodiment of the present invention will be described.

(Functional configuration of the payment operation system)
The functional configuration of payment operation system S1 according to the present embodiment will be described with reference to FIGS.
As shown in Figures 1 and 2, the payment operation system S1 includes a dispatch terminal (dispatch tablet, etc.) TB1 consisting of a tablet-type information terminal or the like that requests the dispatch of a taxi V via a communication line N2.
The communication line N2 may be either a wired line or a wireless line.

This dispatch terminal TB1 is owned by a user (customer) of a taxi V, etc., and is equipped with a dispatch application (dispatch app) consisting of software that processes requests for dispatching a taxi, inputs payment terms for the taxi V, transmits information, and processes online payments for fares. Note that a smartphone or the like with a dispatch app installed can also be used as the dispatch terminal TB1.

The dispatch terminal TB1 also includes a communication unit 501 that communicates information with a taxi meter (on-board device) TM1, a fare payment conditions input unit 502 that inputs fare payment conditions for a taxi V in commercial operation, and an online payment unit 503 that settles fares.
The payment operation system S1 also includes a fare management server SA1 as an external device that manages fare information for taxis V.
The fare management server SA1 includes a communication unit 402 that receives fare information, etc. from multiple taxis V.
The system also includes a storage unit 400, which is configured with a hard disk device or the like, for storing each piece of received fare information.
The electronic device 400 also includes a processing unit 401 that is configured with a CPU and executes various processes.

The processing unit 401 also constitutes a fee payment condition determination unit 410 that determines whether the information on each fee payment condition received by the communication unit 402 via the communication line N1 matches a predetermined condition that has been set in advance.

The payment operation system S1 also includes an on-board device TM1 that is installed in each taxi V and is composed of a taxi meter or the like having a communication unit 17 that transmits fare information to the fare management server SA1.
The vehicle-mounted device TM1 is equipped with a fare payment conditions input unit 11, which is composed of a numeric keypad input unit on a taxi meter screen, a keyboard, etc., for inputting fare payment conditions for a taxi V in commercial operation.
The vehicle-mounted device TM1 may also be equipped with a vehicle dispatch application similar to that of the vehicle dispatch terminal TB1.

The fare management server SA1 also includes an invalidation unit 160, which is configured with a CPU 151 and the like, that invalidates the fee payment condition that is determined not to meet the specified conditions by the fee payment condition determination unit 410 provided in the fare management server SA1.

The system also includes a payment device 14, which is composed of a card reader or the like, that settles the fare for the taxi V based on the payment conditions that are determined by the payment conditions determination unit 410 to match the specified conditions.

Then, the vehicle dispatch terminal TB1 or the settlement device 14 receives settlement information based on the result of the judgment by the fee payment condition judgment unit 410, and performs settlement processing for the fare based on the settlement information.
2, the payment device 14 is shown as a part of the taxi meter (on-board device) TM1, but is not limited to this. That is, for example, the payment device 14 may be provided externally to the taxi meter (on-board device) TM1 and may be configured to operate in conjunction with the taxi meter (on-board device) TM1.

In addition, for example, if the fee payment condition determination unit 410 determines that the fee payment conditions do not match the specified conditions, the invalidation unit 160 controls so as not to send payment information to the vehicle dispatch terminal TB1 or payment device 14 that entered the fee information.

The invalidation unit 160 may also perform control so that payment operations using cash or a taxi ticket cannot be performed, for example, when the fee payment condition determination unit 410 determines that the fee payment conditions do not match predetermined conditions.

Here, for example, assume that the specified condition is set to prioritize the fare payment conditions entered at the vehicle dispatch terminal TB1. Under this condition, if the fare payment conditions for online payment are reserved at the vehicle dispatch terminal TB1, the fare payment conditions entered at the vehicle-mounted device TM1 are invalidated as they do not match the specified condition.

Therefore, even though the fare is paid by online settlement at the vehicle dispatch terminal TB1, it is possible to effectively avoid a situation where a card settlement is mistakenly made at the settlement device 14 on the vehicle-mounted device TM1 side, or a payment operation is made with cash or a taxi ticket.
In this way, the payment operation system S1 can prevent payment-related problems between taxi users and drivers. It also prevents the driver from having to cancel or redo a payment operation, improving convenience.

(Example of vehicle-mounted device configuration)
Referring to FIG. 3, a configuration example of an in-vehicle device (taxi meter) TM1 applied to the payment operation system S1 according to the present embodiment will be described.
The taxi meter TM1 is mounted in a taxi (vehicle) V and has, for example, a car navigation unit (so-called car navigation) function, a taxi meter function, and the like.
The car navigation function includes, for example, a function for detecting the current position of the vehicle and a function for outputting map information including the current position.

In the configuration example shown in FIG. 3, the taxi meter TM1 includes a microcomputer (CPU) 151 that constitutes the invalidation unit 160, etc., and a memory unit (RAM) 52 that constitutes the working area for calculation processing, etc.

It also has a fixed information memory unit (ROM) 53 for storing software such as calculation programs and various data such as freight data, and a touch panel type display unit (LCD) 16.
The device also includes input interfaces 56, 57, 59, and 60, and a clock IC (RTC) 58 that generates a clock signal for determining the timing of calculations and the like.
Furthermore, the device is provided with a GPS (Global Positioning System) receiver 10 which constitutes a location information acquisition unit.

The system also includes a card R/W interface 54 into which a memory card 64 onto which various data can be written can be inserted, and operation units 40a to 40c for operating vacant vehicles, rental vehicles, totals, pick-up vehicles, etc.
The vehicle also includes a communication unit 17 for transmitting and receiving destination information, route information, pre-determined fares, changed fares, in-vehicle information, and the like to and from the fare management server SA1.
Also provided are a speaker constituting the notification unit 18, a thermal printer 65 constituting a printing unit for printing fares and the like, and the like.
The memory card 64 stores, for example, data necessary for driver authentication, business data such as the taxi vehicle's driving history and fare history, and time-series data.

The microcomputer (CPU) 151 also receives a running pulse P1 output from the vehicle and calculates a meter value corresponding to the actual running fare. The microcomputer (CPU) 151 also receives tariff information.
Furthermore, a drive recorder and the like are connected to the input interface 56 .

(Regarding fare information, etc.)
Referring to FIG. 4, an example of a fare presentation by payment operation system S1 according to the present embodiment will be described.
As shown in FIG. 4, when the taxi V arrives at the destination, the taxi meter TM1 displays the confirmed fare calculated based on the traveled distance, etc.
Here, it is assumed that, for example, a predetermined condition is set such that priority is given to the fare payment conditions inputted at the vehicle dispatch terminal TB1 with respect to the payment of the fare.
If the vehicle dispatch terminal TB1 has reserved the fare payment conditions for online settlement under these predetermined conditions, the fare payment conditions inputted on the vehicle-mounted device TM1 side are invalidated as they do not match the predetermined conditions. Then, the confirmed fare is paid by online settlement on the vehicle dispatch terminal TB1 side.

On the other hand, it is also conceivable that, for example, a predetermined condition may be set to prioritize the fare payment conditions input (or operated) on the taxi meter TM1 when paying the fare.

Under these conditions, the payment conditions (e.g., online reservation) entered on the dispatch terminal TB1 are invalid because they do not meet the predetermined conditions. The confirmed fare is then paid by the payment device (e.g., card payment device) on the taxi meter TM1.
In this case, payment may be made by cash or a taxi ticket, etc., depending on the taxi user's preference.

In this way, the payment operation system S1 can effectively prevent situations in which, even though the fare is paid online at the dispatch terminal TB1, payment is mistakenly made by card at the payment device 14 on the in-vehicle device TM1, or payment is made by cash or a taxi ticket.

Therefore, the payment operation system S1 can prevent payment-related problems between taxi users and drivers. It can also prevent the driver from having to cancel or redo a payment operation, improving convenience.

(Regarding taxi fare payment processing)
Next, an example of a processing procedure of the taxi fare payment processing (main processing) executed in the payment operation system S1 will be described with reference to the flowchart of FIG.
This process is executed by, for example, the CPU 151 of the vehicle-mounted device (taxi meter) TM1, and can be realized by cooperation between an OS (operating system) included in the vehicle-mounted device (taxi meter) and a predetermined application program (such as a vehicle dispatching application). However, some or all of the various functions of the vehicle dispatching application may be realized by hardware.

In addition, here, it is assumed that, for example, a predetermined condition is set for the payment of the fare such that the fare payment conditions input in the vehicle dispatch application on the in-vehicle device (taxi meter) TM1 side are given priority.
When this process is started, an event occurs in step S10, such as the taxi V picking up the passenger at the destination and the fare being confirmed, and the process proceeds to step S11.

In step S11, the fare payment condition determination unit 410 of the fare management server SA1 performs a determination process to give priority to the fare payment conditions input in the dispatch application on the in-vehicle device (taxi meter) TM1 side, and then proceeds to step S12.
In step S12, the confirmed fare is paid using a payment device (such as a card payment device) on the taxi meter TM1, and the process proceeds to step S13.
In step S13, the tariff of taxi V is changed to vacant, and the process ends.

When a predetermined condition is set for fare payment, for example, that the fare payment conditions entered in the dispatch application 500 of the dispatch terminal TB1 be given priority, the fare payment condition determination unit 410 of the fare management server SA1 performs a determination process to give priority to the fare payment conditions entered in the dispatch application 500 of the dispatch terminal TB1, instead of step S11. Then, instead of step S12, the dispatch terminal TB1 executes a payment process for the confirmed fare by online payment or the like.

(Regarding cancellation and change of pre-determined meters)
Next, an example of a procedure for a meter pre-determination cancellation/change process executed in the payment operation system S1 will be described with reference to the flowchart of FIG.
In this process, the fare (provisional fare) previously agreed upon via the dispatch application of the dispatch terminal TB1 or the in-vehicle device (taxi meter) TM1 is referred to as the "pre-determined fare."
This process is executed by, for example, the CPU 151 of the vehicle-mounted device (taxi meter) TM1, and can be realized by cooperation between an OS (operating system) included in the vehicle-mounted device (taxi meter) and a predetermined application program (such as a vehicle dispatching application). However, some or all of the various functions of the vehicle dispatching application may be realized by hardware.
When this process starts, in step S20, it is determined whether or not a pre-determined fare has been incurred.

If the result of the determination is "Yes", the process proceeds to step S22. In step S22, the vehicle dispatch application priority flag is set to ON, and the process ends. As a result, the pre-determined fare contracted in the vehicle dispatch application is given priority at the time of payment.
If the determination in step S20 is "No", the process proceeds to step S21.
In step S21, it is determined whether the pick-up button (see FIG. 4) of the vehicle-mounted device (taxi meter) TM1 has been pressed.
If the determination result is "Yes", the process proceeds to step S22, and if the determination result is "No", the process ends.

(Meter payment processing)
Next, an example of a procedure for meter payment processing executed in the payment operation system S1 will be described with reference to the flowchart of FIG.
This process is executed by, for example, the CPU 151 on the vehicle-mounted device (taxi meter) TM1 side, and can be realized by cooperation between an OS (operating system) included in the vehicle-mounted device (taxi meter) and a predetermined application program (such as a vehicle dispatching application). However, some or all of the various functions of the vehicle dispatching application may be realized by hardware.
When this process is started, in step S30, the payment (total) button (see FIG. 4) of the vehicle-mounted device (taxi meter) TM1 is pressed, and the process proceeds to step S31.
In step S31, it is determined whether or not the ride-dispatch application priority flag is ON.

If the determination result is "Yes", the process proceeds to step S32, in which the process of transmitting the fare information set in the ride-hailing application to the payment device 14 is started, and the process proceeds to step S33.
In step S33, a message indicating that payment by cash and taxi ticket (ticket) is invalid is displayed on the display unit 16, and the process proceeds to step S34.
In step S34, a display is made to indicate that the send button (see FIG. 4) is enabled, and the process proceeds to step S37.
On the other hand, if the determination in step S31 is "No", the process proceeds to step S35.
In step S35, a process of transmitting fare information to payment device 14 in the case where the ride-dispatch application priority flag is OFF is started, and the process proceeds to step S36.
In step S36, the process of transmitting fee information for payment (payment information) to the payment device 14 is started, and the process proceeds to step S37.
In step S37, it is determined whether or not the transmission button (see FIG. 4) of the vehicle-mounted device (taxi meter) TM1 has been pressed.
If the determination result is "No", the process proceeds to step S38, and if the determination result is "Yes", the process proceeds to step S39.

In step S39, a process is executed to transmit fare information (payment information) for payment to the payment device 14 of the vehicle-mounted device (taxi meter) TM1, and the process proceeds to step S40.
In step S40, a message indicating that payment by cash and taxi ticket (ticket) is valid is displayed on the display unit 16, and the process proceeds to step S41.
In step S41, information indicating that the send button has been pressed is sent to the fare management server SA1, and the process proceeds to step S38.

In step S38, it is determined whether the taxi V is vacant. If the determination result is "No", the process returns to step S37, and if the determination result is "Yes", the process ends.

The above describes the payment operation system S1 of the present invention based on the illustrated embodiment, but the present invention is not limited to this, and the configuration of each part can be replaced with any configuration having similar functions.
For example, in a commercial operation in which a metered pick-up occurs and in which a pre-determined fare occurs, fare information may be transmitted only to the vehicle dispatch terminal TB1.

In addition, if payment information is received from the payment device 14 of the vehicle dispatch terminal TB1 or the vehicle-mounted device (taxi meter) TM1 while payment processing is already in progress, the vehicle-mounted device (taxi meter) TM1 may display an alarm or issue an audio warning.

In addition, information on pressing the transmission button on the vehicle-mounted device (taxi meter) TM1 and payment information may be transmitted in real time to the fare management server SA1, and fares may be managed at a management office, etc.

S1 Payment operation system SA1 Fare management server V Taxi TB1 Dispatch terminal (dispatch tablet)
TM1 In-vehicle device (taxi meter)
11, 502 Fee payment condition input unit 14 Payment device 160 Invalidation unit 410 Fee payment condition determination unit 500 Vehicle dispatch application

Claims (9)

A dispatch terminal for requesting a taxi dispatch via a communication line;
A fare management server that manages fare information about the taxi;
An in-vehicle device that is installed in the taxi and transmits fare information to the fare management server;
a fare payment terms input unit provided in the dispatch terminal and the in-vehicle device for inputting fare payment terms, which are information indicating a fare payment method for the taxi in commercial operation;
a fee payment condition determination unit that determines whether the fee payment conditions inputted via the fee payment condition input unit of the vehicle dispatching terminal or the vehicle-mounted device conform to a predetermined condition that is set in advance to determine which of the fee payment conditions inputted via the fee payment condition input unit of the vehicle dispatching terminal or the vehicle-mounted device should have priority ;
an invalidation unit that invalidates the fee payment condition that is determined not to match the predetermined condition by the fee payment condition determination unit;
a payment device for making payment for the taxi fare based on the fare payment conditions of the person who is determined to meet the predetermined conditions; and
A payment operation system comprising: The vehicle-mounted device includes:
a communication unit that communicates information with the vehicle dispatch terminal and the fare management server;
The payment device;
The settlement operation system according to claim 1, comprising a taxi meter comprising: The fee payment condition determination unit is provided in the fare management server,
3. A payment operation system according to claim 1, wherein the vehicle dispatch terminal or the payment device performs payment processing for the fare based on payment information based on a result of the judgment by the fare payment condition judgment unit. The payment operation system described in claim 3, wherein the invalidation unit controls so as not to transmit the payment information to the vehicle dispatch terminal or the payment device that inputs the fare payment condition that is determined to not match the specified condition when the fare payment condition determination unit determines that the fare payment condition does not match the specified condition . The payment operation system described in claim 3, wherein the invalidation unit controls so that payment operations cannot be performed using cash or taxi tickets when the fee payment condition determination unit determines that the fee payment conditions entered into the fee payment condition input unit of the vehicle -mounted device do not match the specified conditions. An in-vehicle device for a payment operation system,
A communication unit for communicating with a dispatch terminal for requesting dispatch of a taxi via a communication line and a fare management server for managing fare information for the taxi;
a fare payment conditions input unit for inputting fare payment conditions, which are information indicating a fare payment method for the taxi;
a fare payment condition determination unit that determines whether the fare payment conditions match a predetermined condition that is set in advance to determine which of the fare payment conditions input to the vehicle dispatch terminal and the fare payment conditions input by the fare payment condition input unit should be prioritized, and when it is determined that the fare payment conditions do not match the predetermined condition, an invalidation unit that invalidates the fare payment conditions that are determined not to match the predetermined condition;
a payment device that, when it is determined that the fare payment conditions match the predetermined conditions, settles the fare for the taxi based on the fare payment conditions that are determined to match the predetermined conditions;
An in-vehicle device for a payment operation system comprising: It is executed in the payment operation system,
A fare payment condition input process for inputting, into the dispatch terminal and the on-board device, fare payment conditions which are information indicating a fare payment method for a taxi operated in business;
a fee payment condition determination process for determining whether the fee payment conditions inputted via the vehicle dispatch terminal or the vehicle-mounted device conform to a predetermined condition that is set in advance to determine whether the fee payment conditions inputted via the vehicle dispatch terminal or the vehicle-mounted device should be given priority ;
a nullifying step of nullifying the fare payment condition determined not to match the predetermined condition when the fare payment condition inputted by the vehicle dispatch terminal or the vehicle-mounted device is determined not to match the predetermined condition ;
a payment execution step of, when it is determined that the fare payment conditions inputted by the dispatch terminal or the in-vehicle device match the predetermined conditions, settling the fare for the taxi based on the fare payment conditions that are determined to match the predetermined conditions;
A payment operations program having: The payment operation program described in claim 7, wherein the invalidation process controls so as not to transmit payment information to the vehicle dispatch terminal or payment device that inputs the fare payment condition that is determined not to match the specified condition when it is determined in the fare payment condition determination process that the fare payment condition does not match the specified condition . The payment operation program described in claim 7, wherein the invalidation process controls so that payment operations cannot be performed using cash or taxi tickets when the fare payment condition determination process determines that the fare payment conditions inputted into the vehicle-mounted device do not match the specified conditions.

Images