Information processing device, fare adjustment program, and fare adjustment method

Abstract

To provide an information processing apparatus which can collect the fare while preventing congestion of alighting users, a fare adjustment program, and a fare adjustment method.SOLUTION: In a fare payment system configured by connecting a settlement apparatus, a fare adjustment apparatus, and a user terminal to communicate with each other over a network, a fare adjustment apparatus 12 includes: an acquisition unit 40 which notifies a company which settles a payment of a user, about the fare, and acquires an answer as to whether the fare can be settled or not from the company; a providing unit 41 which provides an image to be used when alighting from transportation to the user when the acquisition unit 40 acquires an answer that the fare can be settled; and a transmission unit 42 which transmits the fare to the company when receiving a notification that the image has been read.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present disclosure relates to an information processing device, a fare adjustment program, and a fare adjustment method. [Background technology]

[0002] When using public transport such as trains and buses, fares are paid when passengers get off the train. To systematize such fare payments, high processing speed is required. For this reason, fare payment systems using IC (integrated circuit) cards are known. For example, Patent Document 1 discloses a system in which charged (deposited) amount information is stored in an IC card, and the fare is paid by deducting the fare from the amount information stored in the IC card by touching the IC card to a reader in an automatic ticket gate. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2004-310683 A Summary of the Invention [Problem to be solved by the invention]

[0004] Conventional fare payment systems using IC cards require users to carry an IC card, which makes their introduction difficult. There is also a risk of the IC card being lost.

[0005] Therefore, it is conceivable that the user's fare information could be managed in a server device, and when getting off the train, the user could access the server device from a user terminal such as a smartphone carried by the user, deduct the fare from the fare information, and pay the fare.

[0006] However, when a user gets off the train, the server device is accessed from the user terminal to carry out a process of deducting the fare from the amount information, which lengthens the processing time and causes the user to remain stuck after getting off the train.

[0007] The present disclosure aims to provide an information processing device, a fare settlement program, and a fare settlement method that can collect fares while preventing users from staying behind when getting off the train. [Means for solving the problem]

[0008] An information processing device according to an aspect of the present disclosure includes an acquisition unit, a provision unit, and a transmission unit. The acquisition unit notifies a business that performs payment for a user of a fare and acquires a response from the business as to whether or not the fare can be paid. If the acquisition unit receives a response that the fare can be paid, the provision unit provides the user with an image to be used when getting off the means of transportation. When notified that the image has been read, the transmission unit transmits the fare to the business. Effect of the Invention

[0009] According to one embodiment of the present disclosure, it is possible to collect fares while preventing users from staying behind when getting off the train. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing an example of a schematic configuration of a fare payment system according to the first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating a schematic functional configuration of the fare adjustment device according to the first embodiment. [Diagram 3] FIG. 3 is a diagram illustrating a flow of registering a user terminal in the payment device in the fare payment system according to the first embodiment. [Figure 4] FIG. 4 is a flowchart illustrating an example of a procedure of the payment process according to the first embodiment. [Diagram 5] FIG. 5 is a diagram illustrating the flow of payment of transportation fares in the fare payment system according to the first embodiment. [Figure 6] FIG. 6 is a diagram illustrating a schematic functional configuration of the fare adjustment device according to the second embodiment. [Figure 7]FIG. 7 is a flowchart illustrating an example of a procedure of a payment process according to the second embodiment. [Figure 8] FIG. 8 is a diagram illustrating a schematic functional configuration of the fare adjustment device according to the third embodiment. [Figure 9] FIG. 9 is a flowchart illustrating an example of a procedure of the payment process according to the third embodiment. [Figure 10] FIG. 10 is a block diagram showing an example of the hardware configuration of the fare adjustment device according to the first to third embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, the present embodiment will be described in detail with reference to the drawings. In this specification and the drawings, the same reference numerals are used to denote substantially the same components, and redundant description will be omitted.

[0012] The explanation will be given in the following order. 1. First embodiment 1.1. System configuration example 1.2. Example of functional configuration 1.3.Functional Flow 2. Second embodiment 2.1. Example of functional configuration 2.2. Functional Flow 3. Third embodiment 3.1. Example of functional configuration 3.2. Functional Flow 4. Hardware configuration example 5. Summary 6.Effects

[0013] <1. First embodiment> <<1.1. System configuration example>> First, a fare payment system including an information processing device of the present disclosure will be described. A fare payment system 10 according to a first embodiment is a system used for paying fares for transportation such as trains and buses. FIG. 1 is a diagram showing an example of a schematic configuration of the fare payment system 10 according to the first embodiment. The fare payment system 10 has a settlement device 11, a fare adjustment device 12, and a user terminal 13. In this embodiment, the fare adjustment device 12 corresponds to the information processing device of the present disclosure.

[0014] The payment device 11, the fare adjustment device 12, and the user terminal 13 are communicatively connected to a network N. As an embodiment of the network N, any type of communication network, whether wired or wireless, such as a mobile communication network such as a mobile phone, the Internet, a LAN (Local Area Network), or a VPN (Virtual Private Network) can be adopted. In the example of FIG. 1, the network N is provided with a base station N1 of a mobile communication network. The user terminal 13 is communicatively connected to the network N by mobile communication via the base station N1. Note that, although the example of FIG. 1 illustrates a case where one user terminal 13 is provided, this is not limiting, and any number of user terminals 13 can be used.

[0015] The payment device 11 is a device that executes a payment for a user. The payment device 11 is, for example, a computer such as a server computer. The payment device 11 may be implemented as one computer, or may be implemented by multiple computers. In this embodiment, the payment device 11 will be described as an example of one computer.

[0016] The payment device 11 is operated by a payment business operator. Examples of the payment business operator include a bank, a credit company, and a wallet business operator. For example, a user opens an account with a payment business operator and deposits money into the account. The payment device 11 performs payment from the user's account.

[0017] The fare adjustment device 12 is a device that provides a function for paying fares for transportation such as trains and buses. The fare adjustment device 12 is, for example, a computer such as a server computer. The fare adjustment device 12 may be implemented as a single computer, or may be implemented by multiple computers. In this embodiment, the fare adjustment device 12 will be described as an example of a single computer.

[0018] The user terminal 13 is a communication terminal device carried by a user. For example, the user terminal 13 is an information processing device such as a smartphone or a mobile terminal carried by a user. A user who uses a transportation facility accesses the fare settlement device 12 using the user terminal 13 and pays the fare for the transportation facility.

[0019] In the first embodiment, a payment service provider provides an application that can be used on a user terminal 13. The application is provided with a button linked to the fare settlement device 12. A user who uses a means of transport installs the application provided by the payment service provider into the user terminal 13. The user then uses the application on the user terminal 13 to access the fare settlement device 12 and pays the fare for the means of transport.

[0020] <<1.2. Example of functional configuration>> Next, an example of the functional configuration of the fare adjustment device 12 will be described. Fig. 2 is a diagram showing an outline of the functional configuration of the fare adjustment device 12 according to the first embodiment. The fare adjustment device 12 has a communication unit 20, a storage unit 21, and a control unit 22.

[0021] (Communication Department 20) The communication unit 20 is a communication interface that communicates with the network N. The communication unit 20 transmits and receives various data to and from the payment apparatus 11 and the user terminal 13 via the network N.

[0022] (Storage unit 21) The storage unit 21 is a storage device such as a hard disk, a solid state drive (SSD), or an optical disk. The storage unit 21 may be a semiconductor memory in which data can be rewritten, such as a random access memory (RAM), a flash memory, or a non-volatile static random access memory (NVSRAM). The storage unit 21 stores an operating system (OS) executed by the control unit 22 and various programs for executing various processes. Furthermore, the storage unit 21 stores various types of information. For example, the storage unit 21 stores user information 30. The user information 30 is data in which various types of information related to a user are stored for each user. The storage unit 21 may store other types of information.

[0023] (Control unit 22) The control unit 22 is a device that controls the entire fare settlement device 12. The control unit 22 is, for example, a processor. The control unit 22 has an internal memory for storing programs that define various processing procedures and control data, and executes various processes using these. The control unit 22 functions as various processing units by the operation of various programs. For example, the control unit 22 has an acquisition unit 40, a provision unit 41, and a transmission unit 42.

[0024] (Acquisition part 40) The acquisition unit 40 notifies the fare to the business that carries out the payment for the user, and acquires a response from the business as to whether the fare can be paid or not. For example, the fare for a transportation facility is transmitted from the user terminal 13 to the fare settlement device 12. The acquisition unit 40 notifies the received fare to the payment device 11 of the payment business, and acquires a response from the payment device 11 as to whether the fare can be paid or not. The payment device 11 responds as to whether the fare can be paid or not depending on the user's account balance, the user's past usage record, the user's income, and other factors that determine the user's creditworthiness for payment. For example, the payment device 11 responds that the fare can be paid if the balance in the user's account is equal to or greater than the fare.

[0025] (Provider 41) When the acquisition unit 40 responds that the fare can be paid, the provision unit 41 provides the user with an image to be used when getting off the transportation facility. For example, when the provision unit 41 receives a response that the fare can be paid, it transmits a code image to the user terminal 13 that transmitted the fare as an image to be used when getting off the transportation facility. The code image may be a two-dimensional code image such as a QR (Quick Response) code, or a one-dimensional code image such as a barcode. The code image may include various types of information, such as the validity period of the code image, the fare, the transportation facility ID, the user ID, and a unique identification number, in a coded form.

[0026] The user terminal 13 displays the provided code image to prove that the fare has been paid. The transportation facility provides a reader to read the code image, and notifies the fare adjustment device 12 of the information on the code image read by the reader.

[0027] (Transmitter 42) When notified that the image has been read, the transmission unit 42 transmits the fare to the payment device 11 of the payment business operator. For example, when notified that the code image has been read by a reader installed in the transportation facility, the transmission unit 42 transmits the fare to the payment device 11 of the payment business operator. For example, when notified of the information of the code image, the transmission unit 42 stores the fare included in the code image in the memory unit 21. Then, the transmission unit 42 transmits the fare stored in the memory unit 21 to the payment device 11 of the payment business operator at a periodic transmission timing. The periodic transmission timing may be at a fixed time (for example, every minute) or at a predetermined time.

[0028] The settlement device 11 performs settlement by deducting the received fare from the amount information of the user's account. The settlement device 11 does not need to perform settlement at the timing of receiving the fare, and may perform settlement as a batch process at regular intervals.

[0029] An example of the functional configuration of the fare adjustment device 12 according to this embodiment has been described above. Note that the above functional configuration described using FIG. 2 is merely an example. The functional configuration of the fare adjustment device 12 according to this embodiment is not limited to the above functional configuration. For example, the fare adjustment device 12 does not necessarily have all of the configuration shown in FIG. 2, and some of the configuration may be provided in a computer different from the fare adjustment device 12. In addition, the fare adjustment device 12 may have multiple configurations as a single configuration. The functional configuration of the fare adjustment device 12 according to this embodiment can be flexibly modified according to specifications and operation.

[0030] The functions of each component may be performed by a computing device such as a CPU (Central Processing Unit) reading a control program from a storage medium such as a ROM (Read Only Memory) or a RAM (Random Access Memory) that stores a control program describing the processing procedures for realizing these functions, and interpreting and executing the program. Therefore, the configuration to be used can be changed as appropriate depending on the technical level at the time of implementing this embodiment. An example of the hardware configuration of the fare settlement device 12 will be described later.

[0031] <<1.3.Functional flow>> Next, the flow of various processes executed by the fare settlement device 12 according to the first embodiment will be described. First, the flow of registering the user terminal 13 in the payment device 11 will be described. FIG. 3 is a diagram explaining the flow of registering the user terminal 13 in the payment device 11 in the fare payment system 10 according to the first embodiment. When making a payment using a payment business, the user opens an account with the payment business and deposits money into the account. The payment business sets authentication information for user authentication such as a user ID and password, and notifies the user. The authentication information may be registerable by the user to the payment business.

[0032] A user installs an application provided by a payment service provider on the user terminal 13 owned by the user. The application accepts input of authentication information. The user operates the user terminal 13 and inputs the authentication information into the application. When the application accepts the authentication information, it performs user authentication, and becomes available for use once authenticated. Once authenticated, the application may store the authentication information and not require user authentication for a certain period of time. In addition, the application may perform user authentication when using a payment-related function such as paying fares.

[0033] The application has a menu with a new registration button linked to the fare adjustment device 12. The application also has a browser function, and can display linked pages within the application.

[0034] A user who uses a means of transport operates the user terminal 13 in advance, and accesses the fare settlement device 12 by selecting a new registration button in the menu of the application. The fare settlement device 12 displays a new registration screen on the user terminal 13 to enable payment of the fare from an account. The new registration screen is provided with an input area for inputting a name, a telephone number, attributes, and the like. The user operates the user terminal 13 and inputs a name, a telephone number, attributes, and the like in the input area. The application transmits to the fare settlement device 12 the name, telephone number, attributes, and authentication information such as a user ID and a password input in the input area. The authentication information such as a user ID and a password may be input on the new registration screen. The fare settlement device 12 may also check whether the telephone number corresponds to the user of the user terminal 13 by sending a message by SMS (short message service) to the telephone number input on the new registration screen and inputting information included in the message from the user terminal 13.

[0035] In addition, when the payment business operator stores the telephone number of the user terminal 13 in association with each user, the application may transmit the telephone number of the user terminal 13 to the payment business operator, identify the user from the telephone number, and perform user authentication. For example, when the payment device 11 stores the telephone number of the user terminal 13 in association with each user, the application may transmit the telephone number of the user terminal 13 to the payment device 11, identify the user from the telephone number, and perform user authentication.

[0036] The fare settlement device 12 accesses the payment device 11 and inquires whether the user is available for payment. For example, the fare settlement device 12 accesses the payment device 11, notifies the authentication information and the telephone number, and inquires whether the user is available for payment. The payment device 11 identifies the user based on the notified authentication information and the telephone number. If the identified user is a user who allows payment of the fare, the payment device 11 responds to the fare settlement device 12 that the user is available for payment. For example, if the identified user is a user who has an account, the payment device 11 responds to the fare settlement device 12 that the user is available for payment. If the fare settlement device 12 receives a response that the user is available for payment, it stores the user's name, telephone number, and attributes in the user information 30 for each user ID. The fare settlement device 12 displays the completion of registration on the user terminal 13.

[0037] In addition, if the application authenticates the user as a user who can make payments with the payment service provider, the fare settlement device 12 may store the user's name, telephone number, and attributes entered on the new registration screen in user information 30 without inquiring of the payment device 11.

[0038] Next, a flow of a payment process for paying a transportation fare using the fare payment system 10 according to the first embodiment will be described. Fig. 4 is a flowchart showing an example of the procedure of the payment process according to the first embodiment. Fig. 5 is a diagram explaining the flow of payment of a transportation fare in the fare payment system 10 according to the first embodiment.

[0039] The application has a settlement button in the menu for paying the fare linked to the fare settlement device 12. A user who has boarded the transportation facility operates the user terminal 13 to select the settlement button from the application menu and access the fare settlement device 12 in order to pay the fare before getting off. The fare settlement device 12 displays a menu screen related to the payment of the transportation facility fare on the user terminal 13. The menu screen has direct payment, ticket purchase, and ticket display. Direct payment is an item that specifies the payment of the fare from the user's account. Ticket purchase is an item that specifies the purchase of tickets that can be used on the transportation facility. Ticket display is an item that specifies the display of purchased tickets.

[0040] When paying the fare from an account, the user selects direct payment. When direct payment is selected, the fare settlement device 12 displays on the user terminal 13 that direct payment is selected, and determines whether the fare can be paid.

[0041] For example, if the user selects direct payment, the application on the user terminal 13 transmits the transportation fare along with authentication information and a phone number.

[0042] As shown in Fig. 4, the acquisition unit 40 of the fare settlement device 12 notifies the business that carries out the payment for the user of the fare and acquires a response from the business as to whether the fare can be paid or not. For example, the acquisition unit 40 transmits the received fare, authentication information, and telephone number to the payment device 11 of the payment business (step S10). The acquisition unit 40 determines whether a response as to whether the fare can be paid or not has been received from the payment device 11 (step S11). If the acquisition unit 40 has not received a response (step S11: No), it waits to receive a response.

[0043] The payment device 11 identifies the user from the received authentication information and telephone number, and responds whether the fare can be paid or not depending on the creditworthiness of the identified user for payment. For example, the payment device 11 responds that the fare can be paid if the balance of the user's account is equal to or greater than the fare. If the transportation facility has a flat fare for one ride, the fare is a fixed amount. If the fare varies depending on the distance traveled, etc., the fare may be calculated from the boarding point and the disembarking point using an existing fare calculation system, etc.

[0044] When receiving a response from the payment device 11 as to whether the fare can be paid (step S11: Yes), the providing unit 41 judges whether the response is that the fare can be paid (step S12). When the response is that the fare cannot be paid (step S12: No), the providing unit 41 transmits to the user terminal 13 a message indicating that the fare cannot be paid, and displays the message on the user terminal 13 (step S13). On the other hand, when the response is that the fare can be paid (step S12: Yes), the providing unit 41 provides the user with an image to be used when getting off the transportation facility. For example, when the providing unit 41 receives a response indicating that the fare can be paid, the providing unit 41 transmits a code image as an image to be used when getting off the transportation facility to the user terminal 13 that transmitted the fare (step S14).

[0045] When the user terminal 13 receives information indicating that the fare cannot be paid, it displays that the fare cannot be paid. The user pays the fare by another method, such as by cash. On the other hand, when the user terminal 13 receives a code image, it displays the received code image.

[0046] When a user gets off the transportation facility, the user has the reader 50 installed in the transportation facility read the code image displayed on the user terminal 13. In the transportation facility, the reader 50 reads the code image. The reader 50 judges whether the read code image is valid. For example, the reader 50 judges whether the code image is valid based on whether the current date and time is within the validity period included in the code image, whether the ID of the transportation facility included in the code image matches the ID of the transportation facility where the reader 50 is installed, whether the unique identification number included in the code image has already been read, etc. The providing unit 42 may generate and provide a code image including a token that cannot be replicated in the code, and the reader 50 may check the token of the code included in the code image to judge whether the code image is valid. In the transportation facility, if the read code image is valid, information on the code image is transmitted to the fare settlement device 12 via the reader 50 or a server device capable of communicating with the reader 50.

[0047] When the transmission unit 42 is notified that the image has been read, it transmits the fare to the payment device 11 of the payment business operator. For example, the transmission unit 42 determines whether or not it has received information on the code image (step S15). If the transmission unit 42 has not received information on the code image (step S15: No), it waits to receive information on the code image. On the other hand, if it has received information on the code image (step S15: Yes), the transmission unit 42 transmits the fare to the payment device 11 (step S16). For example, the transmission unit 42 stores the fare in the memory unit 21. Then, when the transmission unit 42 is notified that the code image has been read, it transmits the fare stored in the memory unit 21 to the payment device 11 of the payment business operator at a periodic transmission timing, and ends the process.

[0048] When the payment device 11 is notified of the fare, the payment device 11 deducts the notified fare from the amount information of the user's account and settles the payment. For example, when the payment device 11 receives the fare, the payment device 11 deducts the notified fare from the amount information of the user's account and settles the payment.

[0049] In this way, even when the fare is paid from an account, if the fare settlement device 12 receives a response from the payment device 11 as to whether the fare can be paid or not, it provides a code image to the user terminal 13 before making the payment. When the user gets off the vehicle, the user can get off by having the code image displayed on the user terminal 13 read by the reader 50 of the transportation facility, which can reduce the user's time staying at the vehicle after getting off. In addition, after the user gets off the vehicle, the fare settlement device 12 can collect the fare by sending the fare to the payment device 11 and paying the fare from the account.

[0050] The fare settlement device 12 also notifies the payment provider of the fare. The payment provider responds whether or not the fare can be paid, depending on the degree of credit for payment. If the fare settlement device 12 receives a response that the fare can be paid, it provides a code image to the user terminal 13. As a result, the fare settlement device 12 can reliably collect the fare even after the user gets off the train, because the fare settlement device 12 has received a response from the payment provider that the fare can be paid.

[0051] <2. Second embodiment> Next, a second embodiment will be described. In the second embodiment, a case where the fare payment system is used to pay fares for fixed-fare transportation facilities, in which the fare is a fixed amount, and variable-fare transportation facilities, in which the fare varies according to the distance traveled, will be described. The configuration of the fare payment system 10 according to the second embodiment is similar to that of the fare payment system 10 according to the first embodiment shown in FIG. 1, and therefore a description thereof will be omitted.

[0052] <<2.1. Example of functional configuration>> Fig. 6 is a diagram showing a schematic functional configuration of the fare adjustment device 12 according to the second embodiment. The fare adjustment device 12 according to the second embodiment has a configuration partially similar to that of the fare adjustment device 12 according to the first embodiment shown in Fig. 2, so similar components are denoted by similar reference numerals and explanations are omitted, and mainly different parts are explained.

[0053] (Storage unit 21) The storage unit 21 further stores blacklist information 31. The blacklist information 31 is data that registers users who are denied boarding public transport. For example, in the blacklist information 31, a user who has a problem, such as non-collection of fares, is registered as a user who is denied boarding public transport. When the problem is resolved, the user is deleted from the blacklist information 31. For example, in the blacklist information 31, it is possible to register and delete a user from the management screen of the fare settlement device 12. Note that, when there are multiple payment service providers, the blacklist information 31 may be stored on a payment service provider basis, or may be stored on a multiple payment service provider basis.

[0054] (Control unit 22) The control unit 22 further includes a determination unit 43 , a specification unit 44 , and a derivation unit 45 .

[0055] (Judgment unit 43) The determination unit 43 determines whether a user who boards a transportation facility is a user registered in the blacklist information 31. For example, when a user boards a transportation facility, information about the boarding user is transmitted from the user terminal 13 to the fare settlement device 12. The determination unit 43 identifies the user from the received information about the user, and determines whether the identified user is a user registered in the blacklist information 31. The determination unit 43 also determines from the received information whether the user has boarded the transportation facility and whether the fare has been settled. Note that, when there are multiple payment service providers, the determination unit 41 determines whether the identified user is a user registered in the blacklist information 31 of the payment service provider requesting payment of the fare.

[0056] (Provider 41) When a user who boards a transportation facility is a user registered in the blacklist information 31, the providing unit 41 notifies the user that boarding is denied. For example, when the determining unit 43 determines that the user is a user registered in the blacklist information 31, the providing unit 41 notifies the user terminal 13 that boarding is denied.

[0057] (Specific part 44) The identification unit 44 identifies whether the fare of the transportation to be boarded is a fixed fare type or a variable fare type that varies depending on the travel distance. For example, the fare settlement device 12 is notified of information for determining whether the fare of the transportation to be boarded by the user is a fixed fare type or a variable fare type from the user terminal 13. The notified information may be fare type information indicating whether the fare is a fixed fare type or a variable fare type, or may be boarding transportation information indicating the transportation to be boarded. When the notified information is fare type information, the identification unit 44 identifies whether the fare is a fixed fare type or a variable fare type from the notified fare type information. On the other hand, when the notified information is boarding transportation information, the fare settlement device 12 stores in the storage unit 21, as master data of the transportation, whether the fare of the transportation is a fixed fare type or a variable fare type for each transportation. The identification unit 44 identifies whether the fare of the transportation of the notified boarding transportation information is a fixed fare type or a variable fare type from the master data stored in the storage unit 21.

[0058] (Derivation part 45) When the identification unit 44 identifies the fare as being of the variable fare type, the derivation unit 45 derives the fare from the boarding section of the transportation to be boarded. For example, when the fare is of the variable fare type, the fare settlement device 12 is notified of information on the boarding point and the alighting point as the boarding section of the transportation to be boarded from the user terminal 13. The derivation unit 45 derives the fare from the boarding section from the notified information on the boarding section. For example, the derivation unit 45 inputs the boarding point and the alighting point to an existing fare calculation system and derives the fare using the fare calculation system. Note that the fare settlement device 12 may store fare information in which fares are registered for each combination of the boarding point and the alighting point of the transportation in the storage unit 21, and the derivation unit 45 may derive the fare by calculating the fare corresponding to the notified boarding point and the alighting point from the fare information.

[0059] <<2.2. Functional flow>> Next, a description will be given of the flow of a payment process for paying a transportation fare using the fare payment system 10 according to the second embodiment. Fig. 7 is a flowchart showing an example of the procedure of the payment process according to the second embodiment.

[0060] The transportation facility has a communication device installed at the boarding gate where the user boards, capable of communicating with the user terminal 13. The communication device is set to determine whether the fare for the transportation facility is a fixed fare type or a variable fare type. When the user terminal 13 touches the communication device, the communication device notifies the user terminal 13 of fare type information indicating whether the fare is a fixed fare type or a variable fare type, for example, via short-range wireless communication such as Bluetooth (registered trademark). Furthermore, when the fare is a variable fare type, the communication device notifies the user terminal 13 of boarding point information indicating the boarding point via short-range wireless communication. Note that the communication device may be set with boarding transportation facility information indicating the transportation facility, and notify the user terminal 13 of the set boarding transportation facility information via short-range wireless communication.

[0061] When boarding a transportation facility, the user touches the user terminal 13 to the communication device at the boarding gate. The user terminal 13 transmits information notified by the communication device via short-range wireless communication to the fare adjustment device 12 together with authentication information and a telephone number. For example, the user terminal 13 receives fare type information, boarding transportation facility information, and boarding location information from the communication device via short-range wireless communication. The user terminal 13 transmits the received fare type information, boarding transportation facility information, and boarding location information to the fare adjustment device 12 together with authentication information and a telephone number. The fare type information or boarding transportation facility information may be transmitted from a wireless device such as a beacon installed inside the transportation facility. The fare type, the transportation facility the user will board, and the boarding location may be input by the user to the user terminal 13.

[0062] The determination unit 43 of the fare adjustment device 12 determines whether or not the user has boarded the vehicle based on the received information (step S50). For example, when the determination unit 43 receives fare type information or boarding transportation facility information, the determination unit 43 determines that the user has boarded the vehicle.

[0063] When it is determined that the user has boarded the vehicle upon receiving the fare type information or the boarding transportation information (step S50: Yes), the determination unit 43 identifies the user based on the authentication information and the phone number received together with the fare type information or the boarding transportation information (step S51). The determination unit 43 determines whether the identified user is a user registered in the blacklist information 31 (step S52). If the identified user is a user registered in the blacklist information 31 (step S52: Yes), the provision unit 41 presents the user with a message that boarding is denied (step S53). For example, the provision unit 41 transmits screen information indicating that boarding is denied to the user terminal 13, and ends the process.

[0064] When the user terminal 13 receives the screen information indicating that boarding is denied, the user terminal 13 displays a message indicating that boarding is denied. This makes it possible to prevent users registered in the blacklist information 31 from boarding the vehicle.

[0065] On the other hand, if the user is not registered in the blacklist information 31 (step S52: No), the identification unit 44 identifies whether the fare is a fixed fare type or a variable fare type from the received fare type information or boarded transportation information (step S54). For example, when the identification unit 44 receives fare type information, it identifies whether the fare is a fixed fare type or a variable fare type from the fare type information. When the identification unit 44 receives boarded transportation information, it identifies whether the fare of the transportation in the boarded transportation information is a fixed fare type or a variable fare type from the master data stored in the memory unit 21.

[0066] The determination unit 43 determines whether the specified fare is a fixed fare type (step S55). If the fare is a variable fare type and not a fixed fare type (step S55: No), the process ends. If the fare is a variable fare type, the fare will be settled later.

[0067] On the other hand, if the fare is a flat-rate fare (step S55: Yes), the acquisition unit 40 notifies the fare to the business that executes the payment for the user, and acquires a response from the business as to whether the fare can be paid or not. For example, the acquisition unit 40 transmits the fare, authentication information, and telephone number to the payment device 11 of the payment business (step S56). The acquisition unit 40 judges whether a response as to whether the fare can be paid or not has been received from the payment device 11 (step S57). If the acquisition unit 40 has not received a response (step S57: No), it waits for the reception of a response. For a flat-rate fare type transportation facility, the fare may be stored in the master data, or may be received from the user terminal 13 as in the first embodiment.

[0068] The settlement device 11 identifies the user from the received authentication information and telephone number, and responds as to whether or not the fare can be settled depending on the degree of creditworthiness of the identified user for payment.

[0069] When receiving a response from the payment device 11 as to whether the fare can be paid (step S57: Yes), the providing unit 41 judges whether the response indicates that the fare can be paid (step S58). When the response indicates that the fare cannot be paid (step S58: No), the providing unit 41 transmits a message to the user terminal 13 indicating that the fare cannot be paid (step S59), and ends the process.

[0070] On the other hand, if the answer is that the fare can be paid (step S58: Yes), the providing unit 41 provides the user with an image to be used when getting off the transportation facility. For example, if the answer is that the fare can be paid, the providing unit 41 transmits a code image as an image to be used when getting off the transportation facility to the user terminal 13 that transmitted the fare (step S60), and ends the process.

[0071] When the user terminal 13 receives information indicating that the fare cannot be paid, it displays that the fare cannot be paid. The user pays the fare by another method, such as by cash. On the other hand, when the user terminal 13 receives a code image, it displays the received code image.

[0072] On the other hand, if the fare is a variable fare type, when the user gets off the transportation facility, the user inputs the alighting point into the user terminal 13. The user terminal 13 transmits boarding point information and alighting point information indicating the alighting point to the fare settlement device 12. Note that if the boarding point information has already been transmitted at the time of boarding, transmission may be omitted.

[0073] If the received information is boarding point information or disembarking point information, the determination unit 43 of the fare adjustment device 12 determines that the information is not a user's boarding information because it is not fare type information or boarding transportation information (step S50: No).

[0074] The determination unit 43 determines whether or not the fare is to be paid based on the received information (Step S61). For example, when the determination unit 43 receives the alighting point information, the determination unit 43 determines that the fare is to be paid (Step S61: Yes).

[0075] The derivation unit 45 derives the fare from the boarding section of the transportation means to be boarded (step S62). For example, the derivation unit 45 derives the fare from the boarding point in the boarding point information to the alighting point in the alighting point information. For example, the derivation unit 45 inputs the boarding point and the alighting point to an existing fare calculation system, and derives the fare using the fare calculation system. Note that, when fare information in which fares are registered for each combination of the boarding point and the alighting point is stored in the storage unit 21, the derivation unit 45 may derive the fare by finding the fare corresponding to the boarding point and the alighting point from the fare information.

[0076] The acquisition unit 40 notifies the business operator who will carry out the payment for the user of the fare and acquires a response from the business operator as to whether the fare can be paid. For example, the acquisition unit 40 transmits the fare derived by the derivation unit 45, the authentication information, and the phone number to the payment device 11 of the payment business operator (step S63). The acquisition unit 40 determines whether a response as to whether the fare can be paid or not has been received from the payment device 11 (step S64). If the acquisition unit 40 has not received a response (step S64: No), it waits to receive a response.

[0077] The settlement device 11 identifies the user from the received authentication information and telephone number, and responds as to whether or not the fare can be paid, depending on the degree of creditworthiness of the identified user for payment.

[0078] When receiving a response from the payment device 11 as to whether the fare can be paid (step S64: Yes), the providing unit 41 judges whether the response is that the fare can be paid (step S65). When the response is that the fare cannot be paid (step S65: No), the providing unit 41 transmits a message to the user terminal 13 indicating that the fare cannot be paid (step S66), and ends the process.

[0079] On the other hand, if the answer is that the fare can be paid (step S65: Yes), the providing unit 41 provides the user with an image to be used when getting off the transportation facility. For example, if the answer is that the fare can be paid, the providing unit 41 transmits a code image as an image to be used when getting off the transportation facility to the user terminal 13 that transmitted the fare (step S67), and ends the process.

[0080] When the user terminal 13 receives information indicating that the fare cannot be paid, it displays that the fare cannot be paid. The user pays the fare by another method, such as by cash. On the other hand, when the user terminal 13 receives a code image, it displays the received code image.

[0081] When the user gets off the transportation facility, the user has the reader 50 installed in the transportation facility read the code image displayed on the user terminal 13. In the transportation facility, the reader 50 reads the code image. If the read code image is valid, the transportation facility transmits information about the code image to the fare adjustment device 12 via the reader 50 or a server device capable of communicating with the reader 50.

[0082] If the received information is code image information, the determination unit 43 of the fare adjustment device 12 determines that the passenger has disembarked (step S68) because the received information is not fare type information, boarding transportation information, or disembarking point information (step S50: No and step S61: No). Note that the determination unit 43 may determine that the passenger has disembarked depending on whether the received information is code image information.

[0083] When the transmission unit 42 is notified that the image has been read, it transmits the fare to the payment device 11 of the payment business operator. For example, when the transmission unit 42 receives information about a code image, it transmits the fare included in the code image to the payment device 11 (step S69), and ends the process.

[0084] In this way, the fare adjustment device 12 according to the present embodiment can collect fares while preventing users from staying at the transportation facility after getting off, regardless of whether the transportation facility fare is a fixed fare type or a variable fare type. In addition, the fare adjustment device 12 can prevent users registered in the blacklist information 31 from boarding the transportation facility.

[0085] <3. Third embodiment> Next, a third embodiment will be described. In the third embodiment, a case where a plurality of pieces of blacklist information are included will be described. The configuration of the fare payment system 10 according to the third embodiment is similar to that of the fare payment system 10 according to the first embodiment shown in FIG. 1, and therefore the description thereof will be omitted.

[0086] <<3.1. Example of functional configuration>> Fig. 8 is a diagram showing a schematic functional configuration of the fare adjustment device 12 according to the third embodiment. The fare adjustment device 12 according to the third embodiment has a configuration partially similar to that of the fare adjustment device 12 according to the first and second embodiments shown in Fig. 2 and Fig. 6, so similar components are denoted by similar reference numerals and descriptions thereof are omitted, and mainly different parts are described.

[0087] (Storage unit 21) The storage unit 21 further stores first blacklist information 32 and second blacklist information 33 instead of the blacklist information 31. The first blacklist information 32 is data that registers users who are refused boarding fixed-fare and variable-fare transportation. For example, the first blacklist information 32 registers users who should be highly cautious, such as users who cannot make payments at a payment service provider and users who are refused use of transportation. The second blacklist information 33 is data that registers users who should be highly cautious, such as users who cannot make payments at a payment service provider and users who are refused use of transportation. The second blacklist information 33 registers users who should be highly cautious, such as users who cannot make payments at a payment service provider and users who are refused use of transportation. The second blacklist information 33 registers users who should be highly cautious, although they have unpaid fares. When the trouble is resolved, the user is deleted from the first blacklist information 32 and the second blacklist information 33. For example, the first blacklist information 32 and the second blacklist information 33 allow users to be registered and deleted from the management screen of the fare settlement device 12. When there are multiple payment service providers, the first blacklist information 32 and the second blacklist information 33 may be stored for each payment service provider, or for multiple payment service providers. When there are multiple payment service providers, the determination unit 41 determines whether the identified user is a user registered in the first blacklist information 32 and the second blacklist information 33 of the payment service provider requesting payment of the fare.

[0088] (Provider 41) When a user who boards a transportation facility is a user registered in the first blacklist information 32, the providing unit 41 notifies the user that boarding is denied. In addition, when a user who boards a transportation facility is a user registered in the second blacklist information, the providing unit 41 notifies the user that boarding of the transportation facility with a variable fare is denied.

[0089] <<3.2. Functional flow>> Next, the flow of payment processing for paying transportation fares using the fare payment system 10 according to the third embodiment will be described. Fig. 9 is a flow chart showing an example of the procedure of the payment processing according to the third embodiment. The procedure of the payment processing according to the third embodiment is partially similar to the procedure of the payment processing according to the second embodiment shown in Fig. 7, so similar processing parts are denoted by similar reference numerals and their explanations are omitted, and mainly different processing parts will be described.

[0090] When the user is identified in step S51, the determination unit 43 determines whether the identified user is a user registered in the first blacklist information 32 (step S70). If the identified user is a user registered in the first blacklist information 32 (step S70: Yes), the provision unit 41 presents the user with a message that boarding is denied (step S71). For example, the provision unit 41 transmits screen information indicating that boarding is denied to the user terminal 13, and ends the process. On the other hand, if the identified user is not a user registered in the first blacklist information 32 (step S70: No), the process proceeds to step S54.

[0091] Furthermore, if the fare is a flat-rate fare (step S55: Yes), the judgment unit 43 judges whether the identified user is a user registered in the second blacklist information 33 (step S72). If the identified user is a user registered in the second blacklist information 33 (step S72: Yes), the provision unit 41 presents the user with a notice that boarding is denied (step S73). For example, the provision unit 41 transmits screen information indicating that boarding is denied to the user terminal 13, and ends the process. On the other hand, if the identified user is not a user registered in the second blacklist information 33 (step S72: No), the process proceeds to step S56.

[0092] In this way, the fare adjustment device 12 according to this embodiment can permit or deny a user who should be wary from boarding fixed-fare and variable-fare public transportation services depending on the degree to which the user should be wary.

[0093] <4. Hardware configuration example> Next, a hardware configuration example of the fare adjustment device 12 according to the first to third embodiments will be described. FIG. 10 is a block diagram showing a hardware configuration example of the fare adjustment device 12 according to the first to third embodiments. Referring to FIG. 10, the fare adjustment device 12 has, for example, a processor 801, a ROM 802, a RAM 803, a host bus 804, a bridge 805, an external bus 806, an interface 807, an input device 808, an output device 809, a storage 810, a drive 811, a connection port 812, and a communication device 813. Note that the hardware configuration shown here is an example, and some of the components may be omitted. In addition, components other than those shown here may be further included.

[0094] (Processor 801) The processor 801 functions, for example, as an arithmetic processing device or control device, and controls all or part of the operation of each component based on various programs recorded in the ROM 802, the RAM 803, the storage 810, or the removable recording medium 901.

[0095] (ROM802, RAM803) The ROM 802 is a means for storing the programs to be read into the processor 801, data to be used for calculations, etc. The RAM 803 temporarily or permanently stores, for example, the programs to be read into the processor 801, various parameters that change appropriately when the programs are executed, etc.

[0096] (host bus 804, bridge 805, external bus 806, interface 807) The processor 801, ROM 802, and RAM 803 are connected to each other via, for example, a host bus 804 capable of high-speed data transmission. On the other hand, the host bus 804 is connected to an external bus 806 having a relatively low data transmission speed via, for example, a bridge 805. In addition, the external bus 806 is connected to various components via an interface 807.

[0097] (Input device 808) Examples of the input device 808 include a mouse, a keyboard, a touch panel, a button, a switch, and a lever. Furthermore, a remote controller capable of transmitting control signals using infrared rays or other radio waves may be used as the input device 808. The input device 808 also includes an audio input device such as a microphone.

[0098] (Output Device 809) The output device 809 is a device capable of visually or audibly notifying the user of acquired information, such as a display device such as a CRT (Cathode Ray Tube), LCD, or organic EL, an audio output device such as a speaker or a headphone, a printer, a mobile phone, a facsimile, etc. The output device 809 according to this embodiment also includes various vibration devices capable of outputting tactile stimuli.

[0099] (Storage 810) The storage 810 is a device for storing various types of data. For example, a magnetic storage device such as a hard disk drive (HDD), a semiconductor storage device, an optical storage device, or a magneto-optical storage device may be used as the storage 810.

[0100] (Drive 811) The drive 811 is a device that reads information recorded on a removable recording medium 901 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, and writes information to the removable recording medium 901.

[0101] (Connection port 812) The connection port 812 is a port for connecting an external device 902, such as a Universal Serial Bus (USB) port, an IEEE1394 port, a Small Computer System Interface (SCSI), an RS-232C port, or an optical audio terminal.

[0102] (Communication device 813) The communication device 813 is a communication device for connecting to a network, such as a communication card for wired or wireless LAN, Bluetooth (registered trademark), or WUSB (Wireless USB), a router for optical communications, a router for ADSL (Asymmetric Digital Subscriber Line), or a modem for various types of communications.

[0103] (Removable recording media 901) The removable recording medium 901 is, for example, a DVD medium, a Blu-ray (registered trademark) medium, an HD DVD medium, various semiconductor storage media, etc. Of course, the removable recording medium 901 may be, for example, an IC card equipped with a non-contact type IC chip, or an electronic device.

[0104] (External connection device 902) The external connection device 902 is, for example, a printer, a portable music player, a digital camera, a digital video camera, or an IC recorder.

[0105] The storage unit 21 according to the present embodiment is realized by the ROM 802, the RAM 803, and the storage 810. The control unit 22 according to the present embodiment, which is realized by the processor 801, reads out and executes each control program that realizes the acquisition unit 40, the provision unit 41, the transmission unit 42, the determination unit 43, the identification unit 44, and the derivation unit 45 from the ROM 802, the RAM 803, etc. The communication unit 110 according to the present embodiment reads out data from the ROM 802, the RAM 803, etc., and transmits the data to the communication device 813 via the host bus 804, the bridge 805, the external bus 806, and the interface 807, thereby transmitting the data to the external device. The communication unit 110 writes the data received by the communication device 813 to the ROM 802 or the RAM 803 via the interface 807, the external bus 806, the bridge 805, and the host bus 804, and receives data from the external device.

[0106] <5. Summary> As described above, the fare settlement device 12 has an acquisition unit 40, a provision unit 41, and a transmission unit 42. The acquisition unit 40 notifies the business operator who carries out the payment for the user of the fare, and obtains a response from the business operator as to whether the fare can be paid. If the acquisition unit 40 obtains a response that the fare can be paid, the provision unit 41 provides the user with an image to be used when getting off the means of transportation. When the transmission unit 42 is notified that the image has been read, it transmits the fare to the business operator.

[0107] This allows the fare adjustment device 12 to collect fares while preventing users from staying behind after getting off the train.

[0108] Although the preferred embodiment of the present disclosure has been described in detail above with reference to the attached drawings, the technical scope of the present disclosure is not limited to such examples. It is clear that a person having ordinary knowledge in the technical field of the present disclosure can conceive of various modified or amended examples within the scope of the technical ideas described in the claims, and it is understood that these also naturally belong to the technical scope of the present disclosure.

[0109] For example, in the above embodiment, the fare settlement device 12 displays an image in an application provided by the settlement service provider. However, the present invention is not limited to this. The fare settlement device 12 may provide each of the functions of the acquisition unit 40, the provision unit 41, the determination unit 43, the transmission unit 42, the identification unit 44, and the derivation unit 45 as an API (Application Programming Interface) that can be called from an external device. The application may also be such that the settlement service provider creates a screen related to the payment of the fare, and the application may call the API of the fare settlement device 12 in response to an operation on the screen related to the payment of the fare to execute each of the functions of the acquisition unit 40, the provision unit 41, the transmission unit 42, the determination unit 43, the identification unit 44, and the derivation unit 45.

[0110] In the above embodiment, the fare adjustment device 12 is described as an information processing device of the present disclosure. However, this is not limited to this. The user terminal 13 may be the information processing device of the present disclosure. For example, an application having the functions of the acquisition unit 40, the provision unit 41, the transmission unit 42, the determination unit 43, the identification unit 44, and the derivation unit 45 and performing fare adjustment may be installed in the user terminal 13, and the user terminal 13 may execute the functions of the acquisition unit 40, the provision unit 41, the transmission unit 42, the determination unit 43, the identification unit 44, and the derivation unit 45.

[0111] <6. Effects> As described above, the information processing device (fare adjustment device 12, user terminal 13) may have the following configuration and provide various effects. However, the effects described in this specification are merely descriptive or exemplary and are not limiting. In other words, the technology disclosed herein may provide other effects that are apparent to a person skilled in the art from the description of this specification, in addition to or in place of the above effects.

[0112] (1) an acquisition unit 40 that notifies a fare to a business that executes payment for a user and acquires a response from the business as to whether or not the fare can be paid; a provision unit 41 that provides the user with an image to be used when getting off the transportation facility when the acquisition unit 40 has responded that the fare can be paid; a transmission unit 42 that transmits the fare to the business operator when the image has been read; An information processing device having the above configuration.

[0113] This enables the information processing device to collect fares while preventing users from staying behind when getting off the train.

[0114] (2) the providing unit 41 provides a code image as the image, When the transmitting unit 42 is notified that the code image has been read by the reader 50 installed in the transportation facility, the transmitting unit 42 transmits the fare to the business operator. An information processing device as described in (1).

[0115] This enables the information processing device to prevent the erroneous collection of fares for purposes other than the use of public transportation.

[0116] (3) The transmission unit 42 stores the fare in the memory unit 21 and transmits the fare stored in the memory unit 21 to the business operator at periodic transmission timings. An information processing device according to (1) or (2).

[0117] This means that the information processing device does not need to send the fare to the business operator in real time when it is notified that the image has been read, but only needs to perform the process of sending the fare at the transmission timing, thereby reducing the processing load.

[0118] (4) an identification unit 44 that identifies whether the fare of the transportation to be used is a fixed fare type or a variable fare type that varies depending on the travel distance; and a derivation unit 45 for deriving a fare from a boarding section of the transportation facility when the fare is determined to be the variable fare type by the determination unit, When the fare is identified as the fixed fare type by the identification unit 44, the acquisition unit 40 notifies the business operator of the fixed fare of the transportation facility, and when the fare is identified as the variable fare type by the identification unit 44, the acquisition unit 40 notifies the business operator of the fare derived by the derivation unit 45. An information processing device according to any one of (1) to (3).

[0119] This allows the information processing device to collect fares while preventing users from staying behind when getting off the train, regardless of whether the transportation fare is a fixed fare type or a variable fare type.

[0120] (5) The vehicle further includes a storage unit 21 that stores blacklist information that registers users who are denied boarding the vehicle; The providing unit 41, when a user who boards the transportation facility is a user registered in the blacklist information 31, notifies the user that boarding is to be denied. An information processing device according to any one of (1) to (4).

[0121] This allows the information processing device to restrict users registered in the blacklist information 31 from riding on public transport.

[0122] (6) The device further includes a storage unit 21 for storing first blacklist information 32 that registers users who are denied boarding of fixed-fare and variable-fare transportation means, and second blacklist information 33 that registers users who are denied boarding of variable-fare transportation means, The provision unit 41, when a user who has boarded the transportation facility is a user registered in the first blacklist information 32, presents the user with a notice that boarding will be denied, and when a user who has boarded the transportation facility is a user registered in the second blacklist information 33, presents the user with a notice that boarding of the transportation facility with a variable fare will be denied. An information processing device according to any one of (1) to (4).

[0123] This allows the information processing device to permit or deny rides on fixed-fare and variable-fare public transportation for users who should be wary, depending on the degree of caution they should be aware of. [Explanation of symbols]

[0124] 10 Fare payment system 11 Payment device 12 Fare settlement device 13 User terminal 20 Communications Department 21 Memory section 22 Control section 30 User Information 31 Blacklist Information 32 First Blacklist Information 33 Secondary Blacklist Information 40 Acquisition Department 41 Providing Department 42 Transmitter 43 Judgment section 44 Specific part 45 Derivation part 50 Reader

Claims

1. A storage unit for storing master data for each transportation facility, which stores whether the fare for the transportation facility is a fixed fare type or a variable fare type that varies depending on the travel distance; a determination unit that, when receiving from the user terminal boarding transportation means information indicating a transportation means to be boarded by a user, determines whether the fare of the transportation means in the boarding transportation means information is a fixed fare type or a variable fare type from the master data stored in the storage unit; a derivation unit that derives a fare from a travel section of the transportation facility when the fare is determined to be the variable fare type by the determination unit; an acquisition unit that notifies a business operator who executes payment for the user of the fixed fare of the transportation facility when the identification unit identifies the fare as the fixed fare type, and notifies the business operator of the fare derived by the derivation unit when the identification unit identifies the fare as the variable fare type, and acquires a response from the business operator as to whether or not the fare can be paid; a providing unit that provides the user with an image to be used when getting off the transportation facility when the acquiring unit has received a response indicating that the fare can be paid; a transmission unit that transmits the fare to the business operator when the business operator is notified that the image has been read; An information processing device having the above configuration.

2. the providing unit provides a code image as the image, The transmission unit transmits the fare to the business operator when notified that the code image has been read by a reader installed in the transportation facility. The information processing device according to claim 1 .

3. The transmission unit stores the fare in the storage unit, and transmits the fare stored in the storage unit to the business operator at periodic transmission timings.

3. The information processing device according to claim 1 or 2.

4. The storage unit stores blacklist information that registers users who are denied boarding the transportation facility, The providing unit notifies the user that boarding the transportation facility will be denied if the user is registered in the blacklist information.

4. The information processing device according to claim 1.

5. The storage unit stores first blacklist information in which users who refuse to board fixed fare and variable fare transportation modes are registered, and second blacklist information in which users who refuse to board variable fare transportation modes are registered, The provision unit, when a user who has boarded the transportation facility is a user registered in the first blacklist information, presents to the user that boarding will be denied, and when a user who has boarded the transportation facility is a user registered in the second blacklist information, presents to the user that boarding of the transportation facility with a variable fare will be denied.

4. The information processing device according to claim 1.

6. When receiving from a user terminal boarding transportation information indicating the transportation means to be boarded by a user, determining whether the fare of the transportation means in the boarding transportation information is a fixed fare type or a variable fare type from master data stored in a memory unit, the master data storing, for each transportation means, whether the fare of the transportation means is a fixed fare type or a variable fare type that varies depending on the distance traveled, If the fare is identified as being of the variable fare type, the fare is derived from the travel section of the transportation facility; If the fare is identified as the fixed fare type, notify the fixed fare of the transportation facility to the business operator that executes the payment for the user, and if the fare is identified as the variable fare type, notify the business operator of the derived fare and obtain a response from the business operator as to whether or not the fare can be paid; If a response is received indicating that the fare can be paid, an image to be used for getting off the transportation facility is provided to the user; When the image has been read, the freight is transmitted to the business. A fare adjustment program that causes a computer to execute a process.

7. When receiving from a user terminal boarding transportation information indicating the transportation means to be boarded by a user, determining whether the fare of the transportation means in the boarding transportation information is a fixed fare type or a variable fare type from master data stored in a memory unit, the master data storing, for each transportation means, whether the fare of the transportation means is a fixed fare type or a variable fare type that varies according to the distance traveled, If the fare is identified as being of the variable fare type, the fare is derived from the travel section of the transportation facility; If the fare is identified as the fixed fare type, notify the fixed fare of the transportation facility to the business operator that executes the payment for the user, and if the fare is identified as the variable fare type, notify the business operator of the derived fare and obtain a response from the business operator as to whether or not the fare can be paid; If a response is received indicating that the fare can be paid, an image to be used for getting off the transportation facility is provided to the user; When the image has been read, the freight is transmitted to the business. A fare settlement method characterized in that the processing is executed by a computer.

Images