Electronic settlement agent system and program

Abstract

To provide an electronic settlement proxy system as a self-system for performing the electronic settlement of a charge to be charged to a user as the value of the use of a first service by the user of the other system for providing the first service to the user.SOLUTION: The other system 10 includes a plurality of rental targets 20 each of which is a movable property or a real estate, and when the user accesses the electronic payment agent system 10 via the communication terminal 90 at the end of use of any one of the rental targets 20 in the other system 10, the electronic payment agent system 110 performs, based on rental target identification information for identifying any one of the rental targets 20 received from the communication terminal 90 at the end of use and fee information indicating an amount of a fee in association with any one of the rental targets 20 at the end of use, To enable electronic settlement of a charge.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a technology that allows users to make electronic payments using communication devices, and in particular to a technology that acts as an agent for electronic payments in other systems, and / or a technology that enables payment systems that do not support electronic payments to support electronic payments. [Background technology]

[0002] Systems that provide certain goods or services, or movable or immovable property, to users are already in widespread use. An example of a system that provides certain goods to users is a vending machine. Throughout this application, the term "provide" refers to acts such as transferring, leasing, etc., whether free of charge or for a fee.

[0003] Another example of a certain type of service is a service that rents real estate or movable property to users. Specifically, an example of a real estate rental object is a rental space such as a seat or parking lot, and an example of a movable property rental object is a means of transportation such as a rental bicycle or rental car.

[0004] More specifically, rental real estate includes, for example, accommodation facilities where users can stay for a short period of time (e.g., rooms in a hotel, rooms in a private home or apartment building that is temporarily rented to others), rooms in accommodation facilities where users can stay for a long period of time (e.g., individual homes, apartment buildings, etc.), coin lockers, parking lots (e.g., parking lots with one or more parking spaces), individual parking spaces (e.g., each of multiple parking spaces in a parking lot), etc.

[0005] Examples of movable property that can be rented include land, water, or air vehicles (e.g., rental cars, rental bicycles, etc.), rental furniture, rental clothing, rental electrical appliances (including the audio guide devices described below), rental accessories that can be detachably attached to electrical appliances (e.g., batteries or chargers), and rental recording media (e.g., CDs) on which audiovisual content is recorded that can be played by the user.

[0006] Here, taking the parking lot business as an example, some conventional examples of systems that provide certain goods or services to users will be described, focusing particularly on payment methods.

[0007] Patent document 1 discloses a parking lot management system that can accept electronic payments (also known as "smartphone payments," which includes, for example, credit card payments), but cannot accept cash payments or prepaid IC card payments (also simply referred to as "card payments").

[0008] This system includes a server installed outside the parking lot that can communicate with the user's mobile terminal, and an exit restriction device installed inside the parking lot that communicates with and is controlled by the server or the user's mobile terminal. Throughout this specification, the "exit restriction device" is also referred to as an exit permission device, which physically restricts a vehicle that has entered the parking lot from leaving the parking lot until the user has completed payment, and physically permits the vehicle to leave once the user has completed payment.

[0009] Patent Document 2 discloses a parking lot management system that can only handle cash or card payments, that is, that can handle non-electronic payments.

[0010] The system includes a payment machine installed in the parking lot (a device that allows users to make non-electronic payments), an exit restriction device installed in the parking lot that is controlled by the payment machine, and a server installed outside the parking lot that is capable of communicating with the payment machine but not with the user's mobile terminal.

[0011] Patent Document 3 discloses a parking lot management system that can handle both non-electronic and electronic payments. This system includes a ticket issuing machine installed in the parking lot that enables non-electronic payments, and a management server installed outside the parking lot that communicates with users' mobile terminals and enables users to make electronic payments. In this case, the management server is managed by the same company that manages the parking lot, and therefore, in this system, the ticket issuing machine and the management server are under the management of the same company.

[0012] Meanwhile, an electronic payment system has already been proposed in which a user can make electronic payments using a communication device. Patent Document 4 discloses an electronic money payment device that allows electronic payments using multiple types of electronic money. [Prior art documents] [Patent documents]

[0013] [Patent Document 1] Patent No. 6401849 [Patent Document 2] Japanese Patent Application Laid-Open No. 2016-045916 [Patent Document 3] Japanese Patent Application Publication No. 2018-173965 [Patent Document 4] Japanese Patent Application Laid-Open No. 2014-119807 Summary of the Invention [Problem to be solved by the invention]

[0014] While electronic payments are becoming increasingly common as a method of payment for goods or services or movable or immovable property provided to users, there are still users who prefer to make payments non-electronically.

[0015] It is possible to build a system that is designed to handle non-electronic payments, and then at least partially modify the hardware configuration of the system to accommodate electronic payments in order to meet the demand for electronic payments. However, this can increase the burden of modifying the system.

[0016] Furthermore, even if a certain system can handle electronic payments, if the types of electronic payments that the system can handle do not match the types of electronic payments that a user can use, the user will not be able to use the system simply because of the mismatch in the types of electronic payments, which limits the range of systems that a user can use.

[0017] Furthermore, the technology disclosed in Patent Document 4 expands the range of electronic payment options available to users. However, the conventional technology disclosed in this document requires businesses to create and operate a new dedicated management system to handle multiple types of electronic payments.

[0018] Therefore, with this type of conventional technology, if an attempt is made to improve user convenience by expanding the range of electronic payment methods available to users in order to promote the realization of a cashless distribution society, the fixed costs and operating expenses that businesses must bear will increase, which is an obstacle.

[0019] Furthermore, when the price for a single event, service, or product provided to a single user includes multiple types of fees corresponding to multiple payees, conventional technology forces the user's communication device to access a dedicated management server for each payee to make electronic payments.

[0020] Therefore, in conventional technology, the user experience of making such payments is such that a large burden is imposed on the user when operating a communication device to make an electronic payment, and therefore there is room for improvement in user convenience.

[0021] Therefore, in technology that allows users to make electronic payments using communication devices, there is a problem of expanding the range of electronic payment types available to users and / or enabling users to make comprehensive electronic payments for composite fees consisting of multiple types of individual fees while reducing the economic burden on businesses; a problem of improving technology that provides users with certain goods or services or movable or immovable property so that users can pay for the provision of those goods or services by electronic payment; and a problem of modifying a payment system that cannot support a certain payment method so that it can support that payment method by using another payment system that can support that payment method while minimizing additional burdens.

[0022] Against this background, the present invention has been made with the objective of providing a technology that allows a user to make electronic payments using a communication device, a technology that acts as an agent for electronic payments on other systems, and / or a technology that enables a payment system that does not support electronic payments to support electronic payments by using another payment system that does support electronic payments. [Means for solving the problem]

[0023] In order to solve this problem, be According to Aspect, An electronic payment agency system as a system that acts as an agent for electronically paying a fee charged to a user of another system that provides a first service to the user as consideration for the user's use of the first service, The other system includes a plurality of rental objects, each of which is movable or immovable property; The electronic payment agency system allows the user to make an electronic payment for the fee based on rental object identification information for identifying the rental object received from the communication terminal at the end of the use and fee information indicating the amount of the fee associated with the rental object at the end of the use, if the user accesses the electronic payment agency system via a communication terminal at the start of the use of any rental object or at the end of the use of any rental object in the other system. A system is provided.

[0024] According to another aspect of the present invention, there is provided a multi-electronic payment system, comprising: A plurality of payment servers, whether or not the types of electronic payments that each server can handle are completely identical to each other; A plurality of management servers that manage the respective payment servers, each of which is operated by a different business operator, and which may or may not completely match the types of electronic payments that can be handled by each of the management servers, but which have the same types of electronic payments that can be handled by the corresponding payment servers, and each management server is used for a system that provides users with certain goods or services, or movable or immovable property, A payment route selection server is a server separate from the management servers and commonly connected to the management servers, and is capable of communicating with a communication device of a user who wishes to make an electronic payment to a selected business. When the server receives an electronic payment request and electronic payment information from the user's communication device, the server identifies the business that is the payment destination for the user from the received electronic payment information, selects one of the management servers operated by the identified business, and transmits an electronic payment request to the selected management server. Including, When the selected management server receives the electronic payment request from the payment route selection server, the selected management server communicates with the payment server assigned to the management server to execute the electronic payment desired by the user; A multi-electronic payment system is provided in which the plurality of management servers are commonly connected to the payment route selection server, thereby constructing a multi-electronic payment communication network that can be used by users.

[0025] According to a first aspect of the present invention, there is provided a multi-electronic payment system, comprising: A plurality of payment servers, in which the types of electronic payments that can be handled by the payment servers do not completely match each other; A plurality of management servers used for a system that provides certain goods or services or movable or immovable property to users; Including, These management servers are a plurality of deemed management servers that manage the plurality of payment servers, respectively, in which the types of electronic payments that can be handled by the deemed management servers do not completely match each other, but the types of electronic payments that can be handled by the corresponding payment servers are common to each other; A payment route selection server is a real management server commonly connected to the deemed management servers and capable of communicating with a communication device of a user who desires any type of electronic payment, and upon receiving an electronic payment request and electronic payment information from the communication device, identifies the type of electronic payment that the user desires to use from the received electronic payment information, selects from the plurality of deemed management servers one that can handle the electronic payment that matches the identified electronic payment, and transmits the electronic payment request to one of the selected one or more deemed management servers. Including, When one of the selected one or more deemed management servers receives the electronic payment request from the payment route selection server, it communicates with a payment server assigned to that deemed management server to execute the electronic payment desired by the user; A multi-electronic payment system is provided in which the plurality of deemed management servers are commonly connected to the payment route selection server, thereby constructing a multi-electronic payment communication network that can be used by users.

[0026] According to a second aspect of the present invention, there is provided a multi-electronic payment system, comprising: A plurality of management servers, the types of electronic payments that they can handle may or may not be completely identical to each other, and each of which is operated by a different business operator; a plurality of payment servers that are assigned to the management servers respectively and that can communicate with the management servers, and that can handle the same types of electronic payment as the management servers assigned to each payment server; A payment route selection server capable of communicating with a communication device of a user who desires to make an electronic payment to a given business, which, upon receiving an electronic payment request and electronic payment information from the communication device, identifies the business that is the user's payment recipient from the received electronic payment information, selects one of the plurality of management servers operated by the identified business, and transmits the electronic payment request to the selected one or more management servers. Including, Upon receiving the electronic payment request from the payment route selection server, the selected one or more management servers communicate with a payment server assigned to the management server to execute the electronic payment desired by the user; A multi-electronic payment system is provided in which the plurality of management servers are commonly connected to the payment route selection server, thereby constructing a multi-electronic payment communication network that can be used by users.

[0027] According to a third aspect of the present invention, there is provided a system for providing certain goods or services or movable or immovable property to a user, the system comprising: the system allows a first type of payment by the user but does not support a second type of payment by itself, and executes a substitute payment mode in cooperation with a second system that provides the user with the same or different type of goods or services or movable or immovable property and that supports said second type of payment; A multi-electronic payment compatible service providing system is provided in which, in the substitute payment mode, a user's communication device accesses the second system, either via or without a communication device other than the communication device, thereby making the second type of payment, and then the second system communicates with the system, either via or without a communication device other than the second system, thereby causing the system to receive a payment completion signal from the second system.

[0028] In one example, the first type of payment includes at least non-electronic payments and the second type of payment includes at least electronic payments.

[0029] In another example, the first type of payment includes at least electronic payments and the second type of payment also includes at least electronic payments.

[0030] According to a first aspect of the present invention, there is provided a system for providing a certain type of product or service, or movable or immovable property to a user, the system comprising: The system allows non-electronic payments by the user, such as cash or card payments, but does not support electronic payments by itself, but performs a pseudo-electronic payment mode in cooperation with a second system that provides the user with the same or different goods or services or movable or immovable property and that supports electronic payments; In the pseudo-electronic payment mode, an electronic payment-enabled service provision system is provided in which a user's communication terminal accesses the second system, either via or without a communication device other than the communication terminal, thereby making an electronic payment, and then the second system communicates with the system, either via or without a communication device other than the second system, thereby causing the system to receive a payment completion signal from the second system.

[0031] According to this system, by using another payment system that can support electronic payments, it becomes easy to convert a payment system that cannot support electronic payments into a payment system that can support electronic payments while minimizing additional burden.

[0032] According to a second aspect of the present invention, there is provided a system for providing a certain type of product or service or movable or immovable property to a user, the system comprising: The system allows users to make non-electronic payments, such as cash payments or card payments, and the system itself operates in a non-electronic payment mode that does not support electronic payments. In the non-electronic payment mode, the user makes non-electronic payments; the system operates in a pseudo-electronic payment mode in cooperation with a second system that provides users with goods or services or movable or immovable property of the same or different type as the system and that is capable of accepting electronic payments; The second system independently executes an electronic payment mode corresponding to the electronic payment, provided that the user is a member of the second system, and in the electronic payment mode, the user's communication terminal communicates with the second system to thereby perform the electronic payment, and then the second system transmits a payment completion signal to the communication terminal; In the pseudo-electronic payment mode, an electronic payment-enabled service provision system is provided in which a user's communication terminal accesses the second system, either via a communication device other than the communication terminal, while the user is either pretending to be a member of the second system or actually becoming a member of the second system, thereby making an electronic payment, and then the second system communicates with the second system, either via a communication device other than the second system, or without going through that communication device, thereby causing the system to receive a payment completion signal from the second system.

[0033] According to this system, by using another payment system that can support electronic payments, it becomes easy to convert a payment system that cannot support electronic payments into a payment system that can support electronic payments while minimizing additional burden.

[0034] According to a third aspect of the present invention, there is provided a system for providing a certain type of product or service or movable or immovable property to a user, the system comprising: the system allows users to make a first type of electronic payment but does not by itself support a second type of electronic payment, and executes a substitute electronic payment mode in cooperation with a second system that provides users with the same or different types of goods or services or movable or immovable property and that allows users to make said second type of electronic payment; An electronic payment-enabled service providing system is provided in which, in the substitute electronic payment mode, the user's communication terminal accesses the second system, either via or without another communication device, thereby making the second type of electronic payment, and then the second system communicates with the system, either via or without another communication device, thereby causing the system to receive a payment completion signal from the second system.

[0035] According to this system, even if the types of electronic payments available to a user do not match the types of electronic payments that the system can handle without relying on the second system, cooperation with the second system allows the types of electronic payments available to a user to match the types of electronic payments that the system can handle in a pseudo manner, thereby enabling the user to use the system. Thus, according to this system, the types of electronic payments that the system can handle will ultimately increase.

[0036] In other words, this system makes it easy to modify a payment system that cannot support a certain payment method into a payment system that can support that payment method while minimizing additional burden by using another payment system that can support that payment method.

[0037] According to a fourth aspect of the present invention, there is provided a system for providing a certain type of product or service, or movable or immovable property to a user, the system comprising: the system is independently capable of accommodating non-electronic payments but not electronic payments, or is independently capable of accommodating at least limited types of electronic payments; a user's communication terminal; In normal payment mode, the system acts as a settlement or payment machine for users to make payments using a payment method that can be handled by the system alone. Including, the system operates in conjunction with a plurality of second systems, each of which provides users with goods or services or personal or real property of the same or different type as the system in connection with the payment process; Each of the second systems is capable of supporting at least one type of electronic payment, and the types of electronic payments that can be supported by the second systems do not completely match each other; The system is a determination unit that, when the communication terminal receives an electronic payment request from a user, determines the type of electronic payment specified by the electronic payment request; a selection unit that, when the type of electronic payment designated by the user does not match any of the types of electronic payment that the system can support, selects, as a substitute system, one of the second systems that covers the type of electronic payment designated by the user; When the substitute system is selected, the communication terminal accesses the substitute system in a substitute electronic payment mode, either via another communication device or without, and the substitute system thereby performs the user-specified electronic payment on behalf of the system. Including, An electronic payment-compatible service providing system is provided in which the substitute system communicates with the settlement machine or payment machine of the system with or without going through another communication device, whereby the settlement machine or payment machine of the system receives a payment completion signal from the substitute system.

[0038] According to this system, if the type of electronic payment available to the user does not match the type of electronic payment that the system can handle, one of multiple second systems that covers the type of electronic payment available to the user is automatically selected, and the selected second system functions as the payment means for the system, thereby making the system pseudo-capable of handling the types of electronic payment that the user can handle.

[0039] This allows the system to virtually accommodate any type of electronic payment available to the user, improving the convenience of the user in the payment process.

[0040] In other words, this system does not allow for just one type of electronic payment, but rather allows for multiple types of pseudo-electronic payments to be realized within the same system, a so-called multi-payment system.

[0041] The present invention provides the following aspects. Each aspect is divided into paragraphs, each numbered, and described by citing the numbers of other paragraphs as necessary. This is to facilitate understanding of some of the technical features and combinations thereof that may be employed by the present invention, and should not be construed as limiting the technical features and combinations thereof that may be employed by the present invention to the following aspects. In other words, it should be understood that technical features that are not described in the following aspects but are described in this specification may be appropriately extracted and employed as technical features of the present invention.

[0042] Furthermore, describing each paragraph in a format that refers to the number of other paragraphs does not necessarily mean that the technical features described in each paragraph cannot be separated and made independent from the technical features described in other paragraphs, and it should be interpreted that the technical features described in each paragraph can be made independent as appropriate depending on their nature.

[0043] (1) A system that provides certain goods or services or personal or real property to users, a cashier that allows a user to make non-electronic payments, such as cash or card payments; an optionally present management server capable of communicating with the settlement machine; Including, The system does not support electronic payments by itself, but operates in a pseudo-electronic payment mode in cooperation with a second system that provides users with the same or different goods or services or movable or immovable property as the system and that supports electronic payments; The second system comprises: a second management server capable of communicating with the user's communication terminal; A payment server that enables users to make electronic payments and is capable of communicating with the second management server. Including, The system is an electronic payment-compatible service providing system in which, in the pseudo-electronic payment mode, the user's communication terminal accesses the second management server, either via or without another communication device (for example, if the system has the management server, then the management server), while the user pretends to be a member of the second system, thereby making electronic payments using the payment server.

[0044] (2) A system that provides certain goods or services or personal or real property to users, a cashier that allows a user to make non-electronic payments, such as cash or card payments; an optionally present management server capable of communicating with the settlement machine; Including, The system operates in a non-electronic payment mode that does not support electronic payments by itself, and in the non-electronic payment mode, a user makes a non-electronic payment using the settlement machine; The system operates in a pseudo-electronic payment mode in cooperation with a second system that provides users with goods or services or movable or immovable property of the same or different kind as the system; The second system comprises: a second management server capable of communicating with the user's communication terminal; A payment server that enables users to make electronic payments and is capable of communicating with the second management server. Including, The second system independently executes an electronic payment mode corresponding to electronic payment, provided that the user is a member of the second system, and in the electronic payment mode, the user's communication terminal communicates with the second management server, thereby performing electronic payment using the payment server, and then the second management server transmits a payment completion signal to the communication terminal; In the pseudo-electronic payment mode, the system is an electronic payment-enabled service providing system in which the user's communication terminal accesses the second management server, either via or without going through another communication device (for example, if the system has the management server, then the management server), while the user is pretending to be a member of the second system, thereby making an electronic payment using the payment server, and then the second management server communicates with the settlement machine, either via or without going through another communication device, thereby causing the settlement machine to receive a payment completion signal.

[0045] (3) The electronic payment-enabled service providing system described in (1) or (2) includes a service of renting a space to a user for parking a vehicle, including a bicycle, an automobile, or a motorcycle, and / or a service of renting a vehicle, including a bicycle, an automobile, or a motorcycle, to a user.

[0046] (4) The service includes a service of renting a space in a parking lot to a user for parking a vehicle, including a bicycle, an automobile, or a motorcycle; The system further comprises: a parking permitting device that physically restricts a vehicle that has entered the parking lot from leaving the parking lot until payment by the user is completed, and physically permits the vehicle to leave the parking lot once payment by the user is completed, the parking permitting device being controlled by the payment machine; The electronic payment compatible service providing system according to (3), wherein the settlement machine transmits a withdrawal permission signal to the withdrawal permission device when the settlement machine receives the payment completion signal.

[0047] (5) The service includes a service of renting to a user a parking space selected by the user from among a plurality of parking spaces for the user to park a vehicle, including a bicycle, an automobile, or a motorcycle, in a parking lot; The system further comprises: An electronic payment-compatible service providing system described in any of (1) to (4), which includes a spoofing access means for, when the pseudo-electronic payment mode is selected by the user at the entry stage when the vehicle enters the selected vehicle space or at the exit stage when the vehicle leaves the vehicle space, the user's communication terminal acquires a combination of information for identifying the parking lot and information for identifying the selected vehicle space, assigns to the combination an impersonation member ID for accessing the second system as a member of the second system, and uses the impersonation member ID to access the second system with or without going through the management server.

[0048] (6) Furthermore, An electronic payment-compatible service providing system described in any of (1) to (4), which includes a spoofing access means for, when the pseudo-electronic payment mode is selected by the user, the user's communication terminal obtains the user ID of the user or information uniquely corresponding to the user, assigns an impersonation member ID to the user ID or information for accessing the second system of the second system as a member of the second system, and uses the impersonation member ID to access the second system with or without going through another communication device.

[0049] (7) A program for causing a computer to function as a communication terminal in the electronic payment compatible service providing system described in any one of (1) to (6).

[0050] Throughout this specification, the term "program" may be interpreted to mean, for example, but not limited to, a combination of instructions that are executed by a computer to perform its functions, and may also be interpreted to include not only the combination of instructions, but also the files and data that are processed in accordance with each instruction.

[0051] Furthermore, this program may be executed by a computer alone to achieve its intended purpose, or may be executed by a computer together with other programs to achieve its intended purpose, but is not limited to these. In the latter case, the program according to this paragraph may be, but is not limited to, one that mainly consists of data.

[0052] (8) A program for causing a computer to function as a management server in the electronic payment compatible service providing system described in any one of (1) to (6).

[0053] (9) A program for causing a computer to function as a settlement machine in the electronic payment compatible service providing system described in any one of (1) to (6).

[0054] (10) A recording medium on which the program according to any one of (7) to (9) is recorded in a computer-readable manner.

[0055] Throughout this specification, the term "recording medium" may be interpreted to mean various types of recording medium, including, but not limited to, magnetic recording media such as floppy disks, optical recording media such as CDs and CD-ROMs, magneto-optical recording media such as MOs, and non-removable storage media such as ROMs.

[0056] (11) A system that provides certain goods or services or personal or real property to users, The system allows a user to make a first type of payment (here, when simply referring to "payment," it does not matter what type it is, such as cash payment, card payment, electronic payment, etc.), but does not support a second type of payment by itself, and executes a substitute payment mode in cooperation with a second system that provides the user with goods or services or movable or immovable property of the same or different type as the system and that supports the second type of payment; In the substitute payment mode, an electronic payment-enabled service providing system is provided in which the user's communication terminal accesses the second system, either via or without a communication device other than the communication terminal, thereby making the second type of payment, and then the second system communicates with the system, either via or without a communication device other than the second system, thereby causing the system to receive a payment completion signal from the second system.

[0057] Examples of combinations of "first type of payment" and "second type of payment" include a combination of non-electronic payment and electronic payment, and a combination of first type of electronic payment and second type of electronic payment. [Brief explanation of the drawings]

[0058] [Figure 1] FIG. 1 is a perspective view conceptually illustrating a parking management system according to an exemplary embodiment of the present invention that is not capable of supporting electronic payments on its own, along with a second parking management system that is capable of supporting electronic payments on its own. [Figure 2] FIG. 2 is a flowchart conceptually showing the operations of the transmitter, the user's mobile terminal, and the management server in the second parking lot management system shown in FIG. 1, which are carried out in the parking entry stage. [Figure 3] FIG. 2 is a flowchart conceptually showing the operations of the transmitter, the user's mobile terminal, and the management server in the second parking lot management system shown in FIG. 1, which are carried out in the leaving stage. [Figure 4] FIG. 4 is a block diagram showing three examples of communication procedures for enabling the parking lot management system shown in FIG. 1 to partially utilize the second parking lot management system shown in the same figure to support electronic payments. [Figure 5]Figure 5 is a flowchart conceptually illustrating the operations of the payment machine, the user's mobile terminal, and the management server in the parking lot management system shown in Figure 1, and the management server and payment server in the second parking lot management system, which are carried out to execute the pseudo-electronic payment mode at the exit stage. [Figure 6] Figure 6 is a block diagram showing an example of a communication procedure for enabling the parking lot management system shown in Figure 1 to support electronic payments by partially utilizing the second parking lot management system shown in the same figure, which is a partial modification of the second communication procedure shown in Figure 4 as a fourth communication procedure. [Figure 7] FIG. 7 is a flowchart conceptually showing an example of a program executed by the parking lot management system shown in FIG. 1 in accordance with the fourth communication procedure shown in FIG. [Figure 8] FIG. 8 is a flowchart conceptually illustrating a program executed by the parking lot management system shown in FIG. 1 to simulate code reading payment with the help of the second parking lot management system shown in FIG. 1. [Figure 9] FIG. 9 is a flowchart conceptually showing another example of a program executed by the parking lot management system shown in FIG. 1 in accordance with the fourth communication procedure shown in FIG. [Figure 10] FIG. 10 is a functional block diagram conceptually illustrating a multi-electronic payment system according to another exemplary embodiment of the present invention. [Figure 11] FIG. 11 is a flowchart conceptually showing the operation of the multi-electronic payment system shown in FIG. [Figure 12] FIG. 12 conceptually illustrates an example of electronic payment request related information for the multi-electronic payment system shown in FIG. [Figure 13] FIG. 13 is a flowchart conceptually showing a modified example of the operation of the multi-electronic payment system shown in FIG. [Figure 14] FIG. 14 conceptually shows an example of electronic payment request related information for the multi-electronic payment system shown in FIG. DETAILED DESCRIPTION OF THE INVENTION

[0059] Some of the more specific exemplary embodiments of the present invention will be described in detail below with reference to the drawings.

[0060] <Overall structure>

[0061] FIG. 1 shows a pseudo-electronic payment-enabled parking lot management system 10 (hereinafter simply referred to as "system 10") according to an exemplary embodiment of the present invention, together with a second electronic payment-enabled parking lot management system 110 (hereinafter simply referred to as "system 110"). System 10 is an example of an electronic payment-enabled service providing system according to an embodiment of the present invention. System 10 also implements a parking lot management method according to an embodiment of the present invention, and the parking lot management method is an example of a pseudo-electronic payment-enabled service providing method according to an embodiment of the present invention.

[0062] System 10 operates in a non-electronic payment mode that does not support electronic payments by itself. In this non-electronic payment mode, a user makes a non-electronic payment using a settlement machine 30 in system 10. One example of a non-electronic payment is cash payment, and another example is prepaid IC card payment (also simply referred to as "card payment").

[0063] Furthermore, the system 10 operates in a pseudo-electronic payment mode in cooperation with a second system 110 that provides users with the same type of service as the system 10. In the pseudo-electronic payment mode, a user uses his or her own mobile terminal 90 (an example of the communication terminal) to make an electronic payment using the management server 140 and the payment server 160 in the second system 110.

[0064] Throughout this application, electronic payment is also referred to as "smartphone payment" (abbreviated as "smartphone payment") and refers to any type of payment made by a user using a mobile terminal 90.

[0065] Examples of such electronic payments include credit card payments, prepaid or postpaid electronic money payments, and code reading payments (also referred to as "QR code (registered trademark) payments" or "code payments") in which a user reads a payment code such as a two-dimensional barcode or one-dimensional barcode like a QR code (registered trademark) with the camera of the mobile terminal 90 and pays the fee using the user's credit card linked to the user or the mobile terminal 90 or electronic money that the user has previously charged.

[0066] In this embodiment, when "code reading payment" is adopted as electronic payment, the "code reading payment" may be executed on a prepaid basis or a postpaid basis.

[0067] Based on the above definition, the criterion used to distinguish between electronic and non-electronic payments is, for example, that a payment made by a user operating the mobile terminal 90 is an electronic payment, and a payment made by a user without operating the mobile terminal 90 is a non-electronic payment. When this criterion is used, it does not matter whether the monetary value (monetary value) of the user consumed for electronic payment is represented by cash in the user's bank account, or by electronic money charged by the user to an individual virtual account in a prepaid or postpaid manner.

[0068] This system 10 is a postpaid system that allows a user to exit parking lot 20 on the condition that the user pays a postpaid parking fee that corresponds to the length of time the user actually parks. However, instead of this, this system 10 can also adopt a prepaid system that allows a user to use parking lot 20 on the condition that the user pays a prepaid parking fee that corresponds to the length of time the user wants to park (e.g., planned parking time) prior to starting to use parking lot 20.

[0069] <System 10 Configuration>

[0070] Referring to FIG. 1, the system 10 is a system for managing a parking lot 20. The parking lot 20 has a plurality of parking spaces 22. One vehicle is parked in each parking space 22. An exit permission device 24 is installed for each parking space 22.

[0071] Regarding the definition of the term "vehicle," the term "vehicle" should be interpreted as including not only automobiles but also all kinds of moving objects such as bicycles and motorcycles.

[0072] An example of an exit permission device 24 has a vehicle presence sensor (for example, a loop coil buried in the ground, a photosensor installed so as to be exposed on the support surface of the parking lot 20, etc.) that detects the presence of a vehicle in the corresponding vehicle compartment 22 (such as a vehicle entering the corresponding vehicle compartment 22), and a mechanism unit having a baffle plate (a flap, lifting device, car stopper, wheel stopper, etc.) as a movable member that switches between an exit prevention state that prevents the vehicle in the vehicle compartment 22 from leaving (exiting) the vehicle compartment 22, and an exit permission state that permits the vehicle to leave.

[0073] When the vehicle presence sensor detects the presence of a vehicle, the mechanism unit causes the baffle plate to transition to an exit-preventing state by, for example, raising or tilting it, and when the user pays the deferred parking fee, causes the baffle plate to transition to an exit-permitting state by, for example, lowering or leveling it.

[0074] In this embodiment, an adjustment machine 30 is installed in common to multiple vehicle compartments 22. The adjustment machine 30 communicates with the vehicle presence sensor in each vehicle compartment 22 and monitors the presence or absence of a vehicle in each vehicle compartment 22 based on signals from the vehicle presence sensor. Furthermore, an adjustment machine 30 is installed in common to multiple exit permission devices 24. The adjustment machine 30 communicates with the mechanism unit in each vehicle compartment 22 and switches the mechanism unit between an exit permission state and an exit prevention state as appropriate. The adjustment machine 30 may be configured mainly from a sequencer or a computer.

[0075] In another example, the exit permission device 24 is installed in common to a plurality of vehicle compartments 22. The exit permission device 24 has, for example, a mechanism for opening and closing a gate at the entrance and exit of the parking lot 20.

[0076] In addition, it is not essential to install an exit permission device 24 in the parking lot 20 in order to implement the present invention, and the present invention can be applied to a parking lot 20 that is a post-payment type but does not have an exit permission device 24.

[0077] The system 10 further includes a management server 40. The management server 40 is operated, for example, by a parking lot management company that manages the parking lot 20 on behalf of the owner of the parking lot 20.

[0078] In non-electronic payment mode, this management server 40 communicates (e.g., wirelessly) only with the settlement machine 30, thereby realizing multiple functions, including the function of remotely monitoring the operating status of the parking lot 20 in real time.

[0079] In contrast, in the pseudo-electronic payment mode, the management server 40 communicates (e.g., wirelessly) with each of the user's mobile terminal 90 and the management server 140 of the second system 110 (an example of the second management server), thereby enabling the user to legally impersonate a member of the second system 110 and legally access the second system 110, thereby realizing multiple functions including an impersonation access function that enables electronic payment, although the system 10 alone cannot handle electronic payments.

[0080] <Configuration of the mobile terminal 90>

[0081] The user's mobile terminal 90 is, for example, a device that is carried by the user and has a wireless communication function, such as a mobile phone, a smartphone, a laptop computer, a tablet computer, a PDA, etc. The mobile terminal 90 is an example of a user's communication terminal, and the communication terminal may be one that is not carried by the user, such as an in-vehicle communication terminal.

[0082] The mobile terminal 90 is mainly configured as a computer having a processor and a memory that stores a plurality of applications executed by the processor.

[0083] The mobile terminal 90 further has a display unit (e.g., a liquid crystal display) that displays information on a screen, a receiving unit that receives signals from an external communication device, and a transmitting unit that generates signals and transmits the signals to the external communication device.

[0084] The mobile terminal 90 further includes an input unit for inputting data and commands from the user. The input unit includes, for example, an operation unit that can be operated by the user to input desired information (for example, commands, data, etc.) into the mobile terminal 90.

[0085] The control unit may include, but is not limited to, a touch screen (means for allowing manual input of data) that displays several icons (e.g., virtual buttons) that can be operated by a user, a physical control unit (means for allowing manual input of data, such as a keyboard, keypad, buttons, etc.) that can be operated by a user, and a microphone that detects voice (means for allowing voice input of data).

[0086] This mobile terminal 90 further has, as another type of input unit, a camera (more precisely, a digital camera, but it may also be understood as a type of image sensor) that captures an image and converts the captured image into an electrical signal. By using this camera, mobile terminal 90 can capture not only landscapes, people, and other objects, but also codes such as QR Code (registered trademark) and barcodes, and numeric symbol strings, whether encrypted or not, as image data.

[0087] The mobile terminal 90 further includes a GPS (Global Positioning System) receiver. As is well known, the GPS receiver receives multiple GPS signals from multiple GPS satellites and determines the position (latitude, longitude, and altitude) of the GPS receiver on the Earth by triangulation based on the GPS signals.

[0088] <Configuration of the second system 110>

[0089] 1, the second system 110 is configured to manage a post-payment parking lot 120, similar to the system 10. The parking lot 120 also has a plurality of parking spaces 122.

[0090] In the parking lot 120, one transmitter 130 is installed in common for multiple compartments 122. In another example, not shown, a number of transmitters 130, the number of which is smaller than the number of compartments 122, are installed in association with each of multiple compartment groups. In yet another example, not shown, the same number of transmitters 130 as the number of compartments 122 are installed for each compartment 122.

[0091] 1, one transmitter 130 is associated with one parking lot 120, and further with all of the parking spaces 122. Therefore, if the transmitter 130 is identified by the user's mobile terminal 190, the location of the associated parking lot 120, that is, the parking space code (or parking space ID) and location (place name, geographical position, etc.) of the parking space 120 selected by the user, are known, but the location of the one parking space 122 selected by the user is unknown.

[0092] The mobile terminal 190 has a common configuration with the above-described mobile terminal 90. Therefore, a duplicated description of the mobile terminal 190 will be omitted.

[0093] In this second system 110, the user can only select the electronic payment mode, and cannot select the non-electronic payment mode. In this embodiment, electronic payment is typically defined as the term meaning the above-mentioned credit card payment.

[0094] <Configuration of the transmitter 130>

[0095] First, conceptually, the transmitter 130 is a contactless or contact (proximity) communication device that emits an identification signal that can identify a unique transmitter code (or transmitter ID).

[0096] The user's mobile terminal 190 exclusively receives the identification signal from the transmitter 130 in one direction via short-range wireless communication. The distance at which the mobile terminal 190 can receive the signal from the transmitter 130, i.e., the reception radius (for example, 0 m to approximately 50 m), is variably set by software on the mobile terminal 190. The area surrounded by a circle having that reception radius is called the receivable area or reception zone.

[0097] The transmitter 130 is usually installed immovably in a fixed location in the corresponding parking lot 120, but it can also be installed movably so that it can be moved as needed. Also, it is sufficient for the transmitter 130 to have at least a transmission function, but it may also be configured to have a receiving function as well, if necessary.

[0098] Next, the operation method will be explained. The transmitter 130 actively transmits a unique identification signal locally without requiring an external trigger signal, and continuously as long as there is no shortage of power supply.

[0099] The transmitter 130 is generally a device known as a beacon device, a radio beacon, or the like that transmits a beacon signal as an identification signal. In one example, the transmitter 130 modulates an original signal to generate an identification signal representing a corresponding transmitter code, and locally transmits the generated identification signal as an IR signal, a Bluetooth (registered trademark) signal, an NFC (near field communication) signal, or the like.

[0100] Next, the hardware configuration will be explained without referring to the drawings. The transmitter 130 is mainly configured as a computer having a processor and a memory for storing a plurality of applications executed by the processor.

[0101] <Configuration of management server 140>

[0102] The second system 110 further includes a management server 140. This management server 140 communicates with the user's mobile terminal 190 in a two-way manner using long-distance wireless communication.

[0103] To explain the hardware configuration without referring to the drawings, the management server 140 is mainly configured as a computer having a processor and a memory for storing a plurality of applications executed by the processor.

[0104] Specifically, this management server 140 has a receiving unit that receives signals from mobile terminal 190, a transmitting unit that generates signals and transmits them to mobile terminal 190, and a clock that measures the current time. This management server 140 does not receive signals from transmitter 130 directly, but in fact receives signals via mobile terminal 190.

[0105] <Operation of the second system 110>

[0106] The operation of the second system 110 will now be described with reference to FIGS.

[0107] <Stage of receiving goods>

[0108] First, referring to Figure 2, the operation of the second system 110 in the entry stage when a vehicle enters one of the vehicle compartments 122 will be explained. When a user starts the parking lot usage program on the mobile terminal 190, the mobile terminal 190 first sends a login request to the management server 140 to log in to the management server 140, together with a member ID indicating that the user is a member eligible to use the second system 110.

[0109] In response, in step S231, the management server 140 receives the login request along with the member ID, and then in step S232, by referring to the member database in the memory of the management server 140, determines whether the current user is a legitimate member.

[0110] If the current user is a legitimate member, the determination in step S232 is YES, and in step S233, a login completion signal indicating completion of login is returned to the current user's mobile terminal 190. If the current user is a legitimate member, the credit card number or bank account number linked to the user is stored in advance in association with the user in the memory of management server 140. On the other hand, if the current user is not a legitimate member, the determination in step S232 is NO, and the process returns to step S231, where input of a legitimate member ID is awaited.

[0111] Thereafter, in step S211, the mobile terminal 190 receives the login completion signal, and at this timing executes step S212, thereby receiving a signal from the transmitter 130 installed in the parking lot 120 where the user is currently located.

[0112] Next, in step S213, the mobile terminal 190 extracts the transmitter code corresponding to the current transmitter 130 from the signal received from that transmitter 130. Thereafter, in step S214, the mobile terminal 190 converts the extracted transmitter code into the corresponding parking lot code in accordance with a predetermined relationship between the transmitter code and the parking lot code that is stored in the memory of the mobile terminal 190. This identifies the parking lot 120 into which the current user has parked.

[0113] Next, in step S215, the mobile terminal 190 displays a "Check In" button on its screen to confirm the user's intention to check in. When the user touches the "Check In" button, it is determined that the user intends to check in, and in step S216, a check-in request by the user to check in, the parking lot code, and the member ID are associated with each other and transmitted to the management server 140. Then, in step S217, the mobile terminal 190 stores the current parking lot code in the memory of the mobile terminal 190 as a check-in parking lot code for later reference.

[0114] In response, in step S234, management server 140 receives the entry request, parking lot code, and member ID in association with each other, and then in step S235, measures the current time using the clock. Thereafter, in step S236, management server 140 treats the measured current time as the entry time, and then in step S237, associates the entry time with the member ID and stores it in the memory of management server 140. As a result, the member ID, parking lot 20 ID, and entry time are stored in association with each other in the memory of management server 140.

[0115] <Shipping stage>

[0116] 3, the operation of the second system 110 in the exit stage when the vehicle leaves one of the compartments 122 will be described. First, in step S311, the user's mobile terminal 190 receives a signal from a transmitter 130 installed in the parking lot 120 where the user is currently located. Next, in step S312, the mobile terminal 190 extracts a transmitter code corresponding to the transmitter 130 from the signal received from the transmitter 130.

[0117] Thereafter, in step S313, the mobile terminal 190 converts the extracted transmitter code into a corresponding parking lot code in accordance with a predetermined relationship between the transmitter code and the parking lot code that is stored in the memory of the mobile terminal 190. This identifies the parking lot 120 where the user is currently located, i.e., the exit parking lot 120 from which the user wants to exit.

[0118] Next, in step S314, the mobile terminal 190 reads the already-saved entrance parking lot code from the memory of the mobile terminal 190 and determines whether it matches the converted parking lot code, i.e., the exit parking lot code. If they match, the determination in step S314 is YES and the process proceeds to step S315, but if they do not match, the determination is NO and the process returns to step S311 to wait for the acquisition of the correct exit parking lot code.

[0119] Next, in step S315, the mobile terminal 190 displays a "Exit" button on its screen to confirm the user's intention to exit. When the user touches the "Exit" button, it determines that the user intends to exit, and in step S316, it transmits a "Exit" request, the "Exit parking lot code," and the "Member ID" to the management server 140 in association with each other.

[0120] In response, in step S331, the management server 140 receives the exit request, the exit parking lot code, and the member ID in association with each other, and then in step S332, determines whether the same combination of exit parking lot code and member ID as the received combination exists in the memory of the management server 140, thereby determining whether to authenticate the current user and the current parking lot 120 as legitimate.

[0121] If the authentication is successful, management server 140 measures the current time using the clock in step S333. Then, in step S334, management server 140 treats the measured current time as the departure time, and then in step S335, reads from the memory the entry time stored in management server 140 in association with the current member ID, and calculates the parking time by subtracting the entry time from the departure time.

[0122] Then, in step S336, management server 140 calculates a parking fee that corresponds to the calculated length of parking time in accordance with a predetermined relationship between the length of parking time and the amount of parking fee that is stored in the memory of management server 140. Management server 140 then transmits the calculated parking fee amount to the user's mobile terminal 190.

[0123] In response, the mobile terminal 190 receives the amount of the parking fee in step S317, and then displays the amount of the parking fee on the screen in step S318.

[0124] Meanwhile, after executing step S336, in step S337, the management server 140 sends a payment request to make electronic payment for the parking fee to the payment server 160, along with information necessary for electronic payment (e.g., the aforementioned credit card number or bank account number linked to the user).

[0125] In response, the payment server 160 receives the payment request in step S351, and then performs the electronic payment according to the specified details in step S352. Next, in step S353, the payment server 160 transmits a payment completion signal indicating that the electronic payment has been completed to the management server 140.

[0126] In response to this, the management server 140 receives the settlement completion signal in step S338, and then transmits a withdrawal permission signal (or a settlement completion signal) to the mobile terminal 190 in step S339.

[0127] In response, the mobile terminal 190 receives the exit permission signal (or payment completion signal) in step S319, thereby letting the user know that the parking fee has been paid electronically and that the user has therefore obtained the authority to legitimately exit the current parking lot 120.

[0128] <System 10 Operation>

[0129] <Stage of receiving goods>

[0130] To explain the operation of this system 10, when a vehicle enters one of the compartments 22 at the entry stage, a corresponding vehicle presence sensor detects the vehicle and sends a signal indicating this to the payment machine 30. The payment machine 30 measures the time as the entry time and records which compartment 22 the vehicle entered at that entry time (in association with the compartment number). This establishes a link between the entry time and the compartment 22 number (or compartment ID).

[0131] The payment machine 30 further associates the entry time with the parking space 22 number (or parking space ID) and transmits them to the management server 40, which then stores the data in association with each other. This enables the management server 40 to monitor the operating status of the parking lot 20 in real time. The management server 40 is configured to centrally manage multiple parking lots 20 so as to monitor the operating status of other parking lots 20 as well.

[0132] <Shipping stage>

[0133] <Non-electronic payment mode>

[0134] In contrast, in the exit stage when the vehicle leaves one of the compartments 22, the user first selects either a non-electronic payment mode or a pseudo-electronic payment mode (which appears to the user as an electronic payment mode realized by this system 10).

[0135] When the non-electronic payment mode is selected, the user inputs the number of his / her parking space 22 into the payment machine 30, which then measures that time as the exit time, calculates the elapsed time from the recorded entry time to the exit time as the parking time, and calculates a deferred parking fee corresponding to that length.

[0136] When the user pays the parking fee to the payment machine 30 using cash or a prepaid card, the payment machine 30 switches the exit permission device 24 corresponding to the current parking space 22 from an exit prevention state to an exit permission state, thereby enabling the user to exit the vehicle from the current parking space 22. In this way, in the exit stage, the parking fee amount is determined using the parking space 22 number entered by the user into the payment machine 30 as a key.

[0137] <Pseudo-electronic payment mode>

[0138] On the other hand, when the pseudo-electronic payment mode is selected, the user starts up a pseudo-electronic payment program that is pre-installed on the mobile terminal 90 .

[0139] <Variations in communication procedures between systems>

[0140] The pseudo-electronic payment program will be described in detail later with reference to Figure 5, but generally, in the pseudo-electronic payment mode, as shown in the top column of Figure 4, the calculation of the postpaid parking fee is performed by the management server 40 on behalf of the payment machine 30 (first communication procedure), but there is also the possibility that the fee calculation is instead performed by the management server 140 of the second system 110 on behalf of the payment machine 30 (second communication procedure), as shown in the middle column of Figure 4, or that the payment machine 30 still performs the calculation (third communication procedure), as shown in the bottom column of Figure 4.

[0141] Here, we will explain the three communication procedures shown in Figure 4. In all of the communication procedures, the combination of management server 40, management server 140, and payment server 160 (the three elements or servers present within the area surrounded by dashed lines in the figure) exists between the mobile terminal 90 and the settlement machine 30 to function as a system 10 that cannot handle electronic payments on its own, by partially utilizing the second system 110 to enable it to handle electronic payments; in this sense, the combination is also referred to as an electronic payment realization means.

[0142] In this electronic payment realization means, the management server 40 is also called the "real management server" in the sense that it is a management server that actually exists in the system 10. In contrast, the management server 140 is also called the "impersonation management server" in the sense that it actually exists not in the system 10 but in the second system 110 and is seen by the user as if it were a management server that actually exists in the system 10.

[0143] Next, these communication procedures will be explained individually.

[0144] <First communication procedure>

[0145] First, in the first communication procedure, as shown in the top column of Figure 4, the mobile terminal 90 communicates wirelessly with the actual management server 40 (e.g., via a telephone line network), thereby causing the actual management server 40 to calculate the parking fee (also called "fee calculation").

[0146] When the fee calculation is complete, the real management server 40 connects to the settlement server 160 via the impersonation management server 140, thereby causing the settlement server 160 to carry out the electronic settlement. When the electronic settlement is complete, the real management server 40 transmits a withdrawal permission signal to the withdrawal permission device 24 via the settlement machine 30, thereby permitting the user to withdraw.

[0147] At this time, the actual management server 40 further transmits the calculated amount of the parking fee to the payment machine 30, and the payment machine 30 displays the received amount of the parking fee on its screen (e.g., LCD, touch panel) either without encrypting the numeric string representing the amount, or it may encrypt and display it as the aforementioned QR code (registered trademark), barcode, or a numeric symbol string selected using a random number table.

[0148] The encrypted information is captured as image data representing the code using the camera of the mobile terminal 90. The captured code is decrypted using a decryption application (an application that converts between original data and encrypted data) of the mobile terminal 90, thereby restoring the original data representing the parking fee. As a result, the user and the mobile terminal 90 can recognize the amount of the parking fee.

[0149] The technology described above, in which the payment machine 30 displays the amount of the parking fee to the user or transmits it to the mobile terminal 90 by printing or radio waves (for example, by transmitting it using the Bluetooth (registered trademark) communication method), can also be used in other communication procedures described below.

[0150] Regarding the communication between the management server 40, the settlement machine 30, and the release permission device 24, in the example shown in Figure 4, the actual management server 40 transmits a release permission signal to the settlement machine 30, and in response, the settlement machine 30 transmits a release permission signal to the release permission device 24.

[0151] Alternatively, the actual management server 40 may receive a payment completion signal from the payment server 60 and transmit a payment completion signal to the settlement machine 30 indicating that the user's electronic payment has been completed, and in response, the settlement machine 30 may transmit an exit permission signal to the exit permission device 24.

[0152] In any case, the "payment completion signal" and the "withdrawal permission signal" are both signals that indicate that the user is permitted to withdraw goods when the user's electronic payment is completed, in an environment where the user is permitted to withdraw goods once the user's electronic payment is completed. Therefore, although the names are different, the substantive meanings are the same. Therefore, there is no problem in reading the "withdrawal permission signal" in the example shown in Figure 4 as the "payment completion signal."

[0153] <Second communication procedure>

[0154] Next, in the second communication procedure, as shown in the center column of Figure 4, the mobile terminal 90 communicates wirelessly with the impersonation management server 140 (e.g., via a telephone line network), thereby causing the impersonation management server 140 to calculate the parking fee (also called "fee calculation").

[0155] When the fee calculation is complete, the impersonation management server 140 connects to the settlement server 160, thereby enabling the user to make an electronic payment. When the electronic payment is complete, the impersonation management server 140 notifies the real management server 40 of the completion of the electronic payment, and in response, the real management server 40 transmits a withdrawal permission signal to the withdrawal permission device 24 via the settlement machine 30, thereby permitting the user to withdraw.

[0156] <Third communication procedure>

[0157] Furthermore, in the third communication procedure, as shown in the bottom column of Figure 4, the mobile terminal 90 communicates wirelessly (e.g., using Bluetooth (registered trademark) communication method) with the payment machine 30, thereby causing the mobile terminal 90 to cause the payment machine 30 to calculate the parking time and the parking fee, and further to return the calculated parking fee to the mobile terminal 90.

[0158] Thereafter, the mobile terminal 90 communicates wirelessly (e.g., via a telephone network) with the impersonation management server 140, which then connects to the settlement server 160, thereby enabling the user to make an electronic payment. When the electronic payment is completed, the impersonation management server 140 notifies the real management server 40 of the completion of the electronic payment, and in response, the real management server 40 transmits a withdrawal permission signal to the withdrawal permission device 24 via the settlement machine 30, thereby permitting the user to withdraw.

[0159] <One example of pseudo-electronic payment mode>

[0160] Next, referring to Figure 5, we will explain the operation of the settlement machine 30, mobile terminal 90 and management server 40 of system 10 and the management server 140 and settlement server 160 of second system 110 when the pseudo-electronic payment mode is executed in accordance with the first communication procedure described above at the delivery stage.

[0161] Of the multiple steps shown in Figure 5, the time series of those executed on mobile terminal 90 corresponds to the pseudo electronic payment program mentioned above, the time series of those executed on management server 40 corresponds to the pseudo electronic payment program for the real management server, the time series of those executed on management server 140 corresponds to the pseudo electronic payment management program for the impersonation management server, and the time series of those executed on payment server 160 corresponds to the electronic payment program.

[0162] When the user starts the pseudo-electronic payment program on the mobile terminal 90, first, in step S511, a withdrawal button is displayed on the user's screen to confirm the user's intention to withdraw (within pseudo-electronic payment mode, not in non-electronic payment mode). Next, in step S512, it is determined whether the user has operated (e.g., touched) the withdrawal button. If the withdrawal button is operated, the determination is YES, and it is determined that the user intends to withdraw.

[0163] Next, in step S513, the mobile terminal 90 prompts the user to input parking lot identification information, for example, a parking lot code, for identifying the parking lot 20 in which the user is currently located, in order to identify the parking lot 20. In response, the user inputs the corresponding parking lot code into the mobile terminal 90 manually (for example, by the manual input or the voice input) or semi-automatically or fully automatically (in a manner in which the input is assisted by the mobile terminal 90).

[0164] In a first example of a method for assisting in inputting a parking lot code, the mobile terminal 90 measures the current location at the location of the current parking lot 20 using the GPS function, and, in accordance with a predetermined relationship between a plurality of parking lots 20 and a plurality of map locations that is stored in the memory of the mobile terminal 90, presents to the user at least one parking lot 20 that corresponds to one of the plurality of map locations that is located near the measured current location as a candidate for the current parking lot 20.

[0165] In this first example, when the user selects one of the parking lots 20 on the mobile terminal 90, the parking lot code corresponding to that parking lot 20 is input into the mobile terminal 90.

[0166] In a second example of the parking lot code input assistance method, the mobile terminal 90 communicates wirelessly (for example, via Bluetooth (registered trademark) communication) with the payment machine 30, and at this time, the payment machine 30 returns to the mobile terminal 90 a signal indicating the parking lot code corresponding to the parking lot 20 in which the payment machine 30 is installed. This allows the user to input into the mobile terminal 90 the parking lot code for the parking lot 20 in which the user is currently located.

[0167] In a third example of the parking lot code input assistance method, the camera of the mobile terminal 90 reads an identification mark, for example, a computer-readable pattern or image (for example, a one-dimensional code such as a barcode, or a two-dimensional code such as a QR code (registered trademark)), attached to each payment machine 30 or vehicle compartment 22, and converts the read result into the parking lot code corresponding to the current parking lot 20. This allows the user to input the parking lot code of the parking lot 20 in which they are currently located into the mobile terminal 90.

[0168] Next, in step S514, the mobile terminal 90 prompts the user to input compartment identification information, for example, a compartment number, that identifies the compartment 22 in which the user's vehicle is currently parked, in order to identify the compartment 22 in the parking lot 20 in which the user is currently located. In response, the user inputs the corresponding compartment number into the mobile terminal 90 manually (for example, by the manual input or voice input) or semi-automatically or fully automatically (in a manner in which input is assisted by the mobile terminal 90).

[0169] In one example of a method for assisting in inputting a vehicle compartment number, the camera of the mobile terminal 90 reads an identification mark attached to each vehicle compartment 22, for example, a computer-readable pattern (for example, a barcode, a two-dimensional code such as a QR code (registered trademark), etc.), and converts the read result into the vehicle compartment number corresponding to the current vehicle compartment 22. This allows the user to input into the mobile terminal 90 the vehicle compartment number of the vehicle compartment 22 in which their vehicle is currently parked.

[0170] Here, the "identification mark" may be configured as a multipurpose identification mark that includes both the identification mark for the vehicle compartment 22 and the identification mark for the parking lot 20. In this case, the camera of the mobile terminal 90 reads the multipurpose identification mark attached to each vehicle compartment 22, and converts the read result into a combination of the parking lot code corresponding to the current parking lot 20 and the vehicle compartment number corresponding to the current vehicle compartment 22.

[0171] According to this exemplary input assistance method, the user can input into the mobile terminal 90 the parking lot code of the parking lot 20 where the user is currently located and the compartment number of the compartment 22 where the user's vehicle is currently parked, all at once.

[0172] Thereafter, in step S515, the mobile terminal 90 assigns one impersonation member ID to the current user (more precisely, the combination of the current parking lot code and the current parking space number) so that the current user can legitimately access the second system 110 to use the electronic payment means of the second system 110. The impersonation member ID is set to be different for each user.

[0173] However, a user who wishes to use the second system 110 for its intended purpose of parking a vehicle is required to be pre-registered as a member of the second system 110. However, a user of the system 10 is not required to be a member of the second system 110 in order to use the system 10.

[0174] Therefore, in this embodiment, the user temporarily poses as a member of the second system 110 through data processing of the mobile terminal 90, regardless of the intention of the user of the system 10 and without the user's knowledge. This qualification as a posing member automatically expires when the user finishes using the system 10 (when the parking fee is paid by pseudo-electronic payment).

[0175] To accomplish this spoofing process, the memory of the mobile terminal 90 stores multiple virtual member IDs, i.e., IDs that are not assigned to any user of the second system 110, but that allow the mobile terminal 90 to access the second system 110 solely for the purpose of electronic payments. These same virtual member IDs are also stored in the memory of the second system 110, allowing the second system 110 to perform member authentication of users of the system 10.

[0176] Each time the mobile terminal 90 receives a user's request for withdrawal in pseudo-electronic payment mode, it selects one of these virtual member IDs so that it does not overlap with any IDs already used on the same mobile terminal 90 or any other mobile terminal 90, and assigns it to the current user. This links the current parking lot code, current parking space number, and current impersonation member ID to one another. When each mobile terminal 90 selects a certain impersonation member ID, it transmits the result to the management server 40, and the management server 40 provides information to other mobile terminals 90 to prevent them from selecting the same impersonation member ID.

[0177] Then, in step S516, the mobile terminal 90 transmits to the management server 40 a request for the user to leave the parking lot (leaving the parking lot in pseudo-electronic payment mode, not in non-electronic payment mode) in association with the parking lot code and the vehicle space number.

[0178] Since the current user is not a real member of the second system 110, nor is he a member who was forcibly registered this time, the management server 140 does not know the credit card number linked to the current user. Therefore, in this embodiment, the mobile terminal 90 further transmits the credit card number linked to the current user to the management server 40 as electronic payment information required for electronic payment.

[0179] In response, in step S531, the management server 40 receives the request for leaving the parking lot, the parking lot code, the parking space number, and the electronic payment information in association with each other.

[0180] Next, in step S532, management server 40 measures the current time using the clock. Thereafter, management server 40 treats the measured current time as the departure time, and then reads from the memory of management server 40 the entry time associated with the current parking space number and stored in the memory, and calculates the parking time by subtracting the entry time from the departure time.

[0181] Thereafter, in step S533, management server 40 calculates a parking fee that corresponds to the calculated length of parking time in accordance with a predetermined relationship between the length of parking time and the amount of parking fee, which is stored in the memory of management server 40. Next, in step S534, management server 40 transmits the calculated amount of parking fee to the user's mobile terminal 90.

[0182] In response, the mobile terminal 90 receives the amount of the parking fee in step S517, and then displays the amount of the parking fee on the screen.

[0183] Thereafter, in step S518, the mobile terminal 90 transmits the amount of the parking fee, an electronic payment request for making an electronic payment for the parking fee, and the current impersonated member ID, along with information necessary for the electronic payment (including the electronic payment information), to the management server 140 of the second system 110. Alternatively, the payment request may be transmitted to the management server 140 by the management server 40 instead of the mobile terminal 90.

[0184] In response, in step S551, management server 140 receives the parking fee amount, the payment request, the impersonated member ID, and information necessary for electronic payment.

[0185] Next, in step S552, the management server 140 refers to its own memory to determine whether a virtual member ID that matches the received impersonated member ID exists, and if so, permits the current user to access the second system 110 for the sole purpose of electronic payment. This is how member authentication is performed.

[0186] Thereafter, in step S553, the management server 140 transmits a payment request for electronic payment of the parking fee to the payment server 160 together with information necessary for electronic payment.

[0187] In response, the payment server 160 receives the payment request in step S571, and then performs the electronic payment according to the specified details in step S572. Next, in step S573, the payment server 160 transmits a payment completion signal indicating that the electronic payment has been completed to the management server 40.

[0188] In response, the management server 40 receives the payment completion signal in step S535, and subsequently determines in step S536 that the payment of the parking fee has been completed by electronic payment. Thereafter, in step S537, the management server 40 transmits a withdrawal permission signal (or a payment completion signal) to the payment machine 30.

[0189] In response to this, the settlement machine 30 receives the exit permission signal (or payment completion signal) in step S501, and subsequently, in step S502, transmits an exit permission signal to the exit permission device 24 to allow the user's vehicle to leave the current vehicle compartment 22. In response to the exit permission signal, the exit permission device 24 retracts (stores) the baffle plate from the operating position to the non-operating position, thereby allowing the vehicle to exit from the exit permission device 24.

[0190] <Fourth communication procedure>

[0191] Several variations of the second communication procedure shown in the center column of FIG. 4 are proposed, which differ in that the fee calculation is performed on the real management server 40 instead of the masquerading management server 140.

[0192] <First Modification of the Fourth Communication Procedure>

[0193] In a first variant of the fourth communication procedure, as illustrated in a block diagram in Figure 6 as the fourth communication procedure and conceptually represented in a flowchart in Figure 7, first, in step S701, when the user operates the aforementioned exit button, the mobile terminal 90 accesses the impersonation management server 140, thereby transmitting a combination of the parking lot identification information and the vehicle compartment identification information to the impersonation management server 140.

[0194] Here, the "combination of parking lot identification information and vehicle compartment identification information" is information that identifies the parking lot 20 used by the current user and the vehicle compartment 22 within that parking lot 20, i.e., vehicle compartment identification information, and is also information that individually identifies the current user, i.e., information that uniquely corresponds to the current user, i.e., information specific to the current user.

[0195] Next, in step S702, the mobile terminal 90 further transmits the credit card number (or bank account number) linked to the user to the impersonation management server 140 as information required for electronic payment (e.g., electronic payment information required for the payment server 160 to perform credit card payment).

[0196] Next, in step S733, the impersonated management server 140 accesses the real management server 40 and thereby transmits the vehicle compartment identification information received from the mobile terminal 90 to the real management server 40. In step S752, the real management server 40 temporarily stores the received vehicle compartment identification information in its own memory.

[0197] Next, in step S753, the real management server 40 identifies the parking lot 20 and the vehicle compartment 22 (hereinafter referred to as "individual vehicle compartment position") represented by the received vehicle compartment identification information.

[0198] Thereafter, in step S754, the real management server 40 calculates the actual parking time by the user this time (the usage time of the compartment 22 by the user) for the identified individual compartment position.

[0199] Specifically, as described above, the real management server 40 reads from the memory of the real management server 40 the entry time that is associated with the current vehicle space 22 and transmitted from the payment machine 30 to the real management server 40 and recorded in association with the vehicle space 22, and calculates the length of the parking time as the difference between the read entry time and the exit time (for example, the time when the user operates the exit button on the screen of the mobile terminal 90, the time when the mobile terminal 90 accesses the impersonation management server 140, the current time, etc.).

[0200] Thereafter, in step S755, the real management server 40 calculates the parking fee corresponding to the calculated length of parking time by referring to a predetermined fee table (not shown).

[0201] Next, in step S756, the real management server 40 transmits the calculated parking fee amount to the impersonation management server 140, associating it with the corresponding individual vehicle space location (e.g., a combination of parking space 20 and vehicle space 22) or user ID.

[0202] In this way, the spoofing management server 140 receives the amount of the current parking fee individually for each user.

[0203] Then, in step S735, the spoofing management server 140 sends an electronic payment request to the payment server 160. Furthermore, in step S736, the spoofing management server 140 sends the electronic payment information to the payment server 160. Furthermore, in step S737, the spoofing management server 140 determines the amount represented by the received parking fee data as the payment amount, and sends payment amount data representing the payment amount to the payment server 160.

[0204] In response to this, in step S774, the payment server 160 performs electronic payment (credit card payment) based on the received electronic payment information and payment amount data. Then, in step S775, a completion signal indicating that the electronic payment has been completed is sent to the impersonation management server 140 and the real management server 40. This allows the impersonation management server 140 and the real management server 40 to know that the payment of the parking fee has been completed in the form of electronic payment.

[0205] In response to this, in step S739, the impersonation management server 140 transmits a payment completion signal indicating that the electronic payment has been completed to the mobile terminal 90. This notifies the user that the electronic payment has been completed.

[0206] In response to this, in step S758, the physical management server 40 transmits a payment completion signal to the communication device of the payment adjustment machine 30. This notifies the payment adjustment machine 30 that the payment of the parking fee has been completed in the form of electronic payment.

[0207] <Second Modification of the Fourth Communication Procedure>

[0208] A second variation of the fourth communication procedure is illustrated in the block diagram of Fig. 6 as the fourth communication procedure, and is conceptually represented in the flowchart of Fig. 9. The flowchart will be explained below, but redundant explanations of elements common to the flowchart of Fig. 7 will be omitted.

[0209] In the flowchart of Figure 9, first, in step S901, when the user operates the aforementioned exit button, the mobile terminal 90 accesses the impersonation management server 140, thereby transmitting the vehicle compartment identification information (information identifying the parking lot 20 being used by the current user and the vehicle compartment 22 within that parking lot 20) to the impersonation management server 140.

[0210] In response, in step S931, the spoofing management server 140 receives the vehicle compartment identification information from the mobile terminal 90. The received vehicle compartment identification information is stored in the memory of the spoofing management server 140. Next, in step S932, the spoofing management server 140 sends a fee information request to the real management server 40 to obtain parking fee information regarding the parking fee to be charged to the current user.

[0211] In response, in step S951, the real management server 40 receives the fee information request from the masquerade management server 140. Next, in step S952, the real management server 40 calculates the parking fee amount as in the above-described steps S754 and S755 and the above-described step S852. Thereafter, in step S953, the real management server 40 transmits fee information indicating the parking fee amount to the masquerade management server 140.

[0212] In response to this, in step S933, spoofing management server 140 receives the fee information from real management server 40. The received fee information is stored in the memory of spoofing management server 140. Next, in step S934, spoofing management server 140 transmits the received fee information to mobile terminal 90.

[0213] In response to this, in step S902, mobile terminal 90 receives the fee information from impersonation management server 140. Next, in step S903, mobile terminal 90 transmits the electronic payment information stored in its own memory to impersonation management server 140.

[0214] In response, in step S935, the spoofing management server 140 receives the electronic payment information from the mobile terminal 90. The received electronic payment information is stored in the memory of the spoofing management server 140. Next, in step S936, the spoofing management server 140 transmits the electronic payment request to the payment server 160 together with the electronic payment information (e.g., credit card number) and the fee information (e.g., parking fee amount).

[0215] In response to this, in step S971, the payment server 160 receives the electronic payment request, the electronic payment information, and the fee information in association with each other. Next, in step S972, the payment server 160 performs electronic payment (credit card payment) based on the received various information. After that, in step S973, the payment server 160 transmits an electronic payment completion signal indicating that the electronic payment has been completed to the impersonation management server 140.

[0216] In response, in step S937, the spoofing management server 140 receives the electronic payment completion signal. This notifies the spoofing management server 140 that the parking fee payment has been completed electronically. Next, in step S938, the spoofing management server 140 transmits the electronic payment completion signal to both the mobile terminal 90 and the real management server 40.

[0217] In response to this, in step S904, the mobile terminal 90 receives the electronic payment completion signal from the impersonation management server 140. This notifies the user that the payment of the parking fee has been completed in the form of electronic payment.

[0218] Furthermore, in step S954, the real management server 40 receives the electronic payment completion signal from the masquerade management server 140. As a result, the real management server 40 becomes aware that payment of the current parking fee has been completed in the form of electronic payment. Thereafter, in step S955, the real management server 40 transmits the electronic payment completion signal to the communication device of the payment adjustment device 30. As a result, the payment adjustment device 30 becomes aware that payment of the current parking fee has been completed in the form of electronic payment.

[0219] As is clear from the above explanation, according to this embodiment, by using another payment system 110 that can support electronic payments, it is easy to modify a payment system 10 that cannot support electronic payments into a payment system 10 that can support electronic payments while minimizing additional burden on the payment system 10.

[0220] Specifically, a payment system 10 that cannot support electronic payments can make electronic payments using an electronic payment method in another payment system 110 that can support electronic payments. Therefore, in order to modify the payment system 10 to make it compatible with electronic payments (to make the payment system 10 pseudo-compatible with electronic payments), it is sufficient to make relatively simple changes to the application to be installed on the mobile terminal 90 and the software configuration of the management server 40 and the settlement machine 30, and there is no need to add a new electronic payment method to the payment system 10.

[0221] In some of the embodiments described above, when the pseudo-electronic payment mode is selected by the user, the mobile terminal 90 acquires a combination of information for identifying the current parking lot 20 (e.g., a parking lot code) and information for identifying the currently selected parking space 22 (e.g., a parking space number), assigns to the combination an impersonation member ID for accessing the second management server 140 of the second system 110 as a member of the second system 110, and is designed to include an impersonation access means for accessing the second management server 140 using the impersonation member ID.

[0222] Alternatively, the mobile terminal 90 may be designed to, when the pseudo-electronic payment mode is selected by a user, obtain the user ID of the user or information uniquely corresponding to that user (described later), assign an impersonation member ID to the user ID or unique corresponding information for accessing the second management server 140 of the second system 110 as a member of the second system 110, and include an impersonation access means for using the impersonation member ID to access the second management server 140 with or without going through the management server 40.

[0223] Here, "information that uniquely corresponds to a user (uniquely corresponding information)" includes, for example, text information (string of characters and numbers) such as the telephone number, email address, IP address, and registration number of the user's vehicle (such as the number on the license plate) of the mobile terminal 90, and image information such as an image of the user or the user's vehicle. The "vehicle registration number" may be obtained by the user manually inputting a string of characters and numbers into the mobile terminal 90, or by the user capturing an image including the vehicle's license plate with the camera of the mobile terminal 90 and extracting the number from the captured image through image recognition processing by the mobile terminal 90 or another device.

[0224] The above-described embodiments are examples of the application of the present invention to a service using a postpaid parking lot 20, but the present invention may also be applied to a service using a prepaid parking lot.

[0225] Furthermore, the several embodiments described above are examples of the application of the present invention to a parking lot service in which a space for a user to park a vehicle is rented to the user in a parking lot 20 managed by an operator (parking lot management company), but the present invention can be applied to other types of services.

[0226] Specifically, the present invention may be applied to, for example, a service in which an individual lends their parking space to others to park their vehicles (a so-called parking space sharing service), a service in which a business lends vehicles to users at their business premises (a so-called vehicle rental service), a service in which a business lends vehicles to users in an unmanned parking lot (a so-called vehicle sharing service), or a service in which an individual lends their own vehicle to others (a so-called vehicle sharing service).

[0227] Furthermore, the present invention may be applied to a service of renting real estate or personal property to users.

[0228] An example of a rental property is a coin locker. In this example, there are coin lockers that do not support electronic payment and a coin locker system that supports electronic payment (including, for example, coin lockers with communication functions, a management server, and a payment server). When the present invention is applied to this example, the payment machine of the non-electronic payment coin locker will be able to accept pseudo-electronic payments using the electronic payment coin locker system.

[0229] Furthermore, when the present invention is applied to an environment in which there exists a non-electronic payment compatible vending machine that sells items such as beverages without any staff and an electronic payment compatible vending machine system (e.g., including a vending machine with communication capabilities, a management server, and a payment server), for example, the cash register of the non-electronic payment compatible vending machine will be able to pseudo-accept electronic payments using the electronic payment compatible vending machine system.

[0230] Here, "items" may be items that have physical use value in themselves, such as beverages, food, rental balls for pachinko machines, rental coins for slot machines, or rental coins for game machines, or items that have no physical use value in themselves but prove that a user has certain authority (e.g., tickets, admission tickets, meal tickets, tokens, tokens).

[0231] The non-electronic payment-enabled vending machine system described above includes a vending machine that provides a specified item in exchange for payment by a user, and may optionally further include a management server that can communicate with the vending machine if the vending machine has a communication function.

[0232] Examples of non-electronic payment systems to which this invention can be applied include unmanned ticket vending machines for public transport that sell tickets in exchange for a user's payment, unmanned ticket vending machines installed in restaurants that sell meal tickets in exchange for a user's payment, unmanned coin laundry systems that lend out washing machines and dryers to users, payment terminals installed in commercial facilities that allow users to request and pay for items they wish to purchase, and unmanned rental machines installed in gaming facilities such as pachinko parlors and slot machine halls that lend out items necessary for gaming.

[0233] In some of the embodiments described above, a user of system 10 is granted membership in second system 110 without the user's knowledge, but the present invention may also be implemented in a manner in which the user of system 10 gains membership in second system 110 with the user's consent or instruction, and then accesses second system 110.

[0234] If a user of system 10 is required to register the credit card number associated with the user with management server 140 in order to qualify as a member of second system 110, when the current user requests an electronic payment in system 10, the credit card number associated with the user will have been previously registered with management server 140, and the user will not have to go through the trouble of sending the credit card number associated with the user to management server 140 when making an electronic payment for system 10.

[0235] Furthermore, in some of the embodiments described above, the non-electronic payment-enabled system 10 has the management server 40, but the present invention may also be implemented in a configuration that does not have the management server 40. Furthermore, regardless of whether the non-electronic payment-enabled system 10 has the management server 40 or not, the present invention may also be implemented in a configuration in which the user's mobile terminal 90 accesses the management server 140 of the second electronic payment-enabled system 110 without going through the management server 40.

[0236] Furthermore, in some of the embodiments described above, the electronic payment-enabled second system 110 conducts the same type of business as the non-electronic payment-enabled system 10, i.e., the business of providing parking spaces to users, but it may also conduct a different type of business from the non-electronic payment-enabled system 10 (for example, a business of selling goods unattended).

[0237] In addition, in some of the embodiments described above, the non-electronic payment-enabled system 10 enables users to make electronic payments using the payment means of the electronic payment-enabled second system 110, but the present invention may also be applied when the system 10 is electronic payment-enabled.

[0238] When the present invention is implemented in such an environment, for example, even if the types of electronic payments that system 10 can handle independently without relying on second system 110 do not match the types of electronic payments available to the user, cooperation with second system 110 will cause the types of electronic payments available to the user to match the types of electronic payments that system 10 can virtually handle. This will eliminate the problem of mismatched types of electronic payments, allowing the user to use system 10.

[0239] Specifically, for example, if the type of electronic payment that system 10 can accept is "VISA (registered trademark) card," while the type of electronic payment that second system 110 can accept is "MasterCard (registered trademark)," and the types of credit cards that users can use are different between systems 10 and 110, if the user does not have the authority to use a credit card that can be used with system 10, the user will not be able to use system 10 simply because electronic payments are not possible.

[0240] In contrast, according to the present invention, if a system 10 capable of accepting a first type of credit card uses the payment means of a second system 110 capable of accepting a second type of credit card, thereby enabling a user to make electronic payments using a second type of credit card, a situation in which a user is unable to use system 10 simply because there is a mismatch between the type of credit card available to the user and the type of credit card available to system 10 can be avoided, thereby improving user convenience.

[0241] <Code scanning payment>

[0242] In the several embodiments described above, the second system 110 typically employs the aforementioned "credit card payment" as the electronic payment.

[0243] Alternatively, the present invention can be implemented in a manner in which the second system 110 employs the aforementioned "code reading payment" as the electronic payment method.

[0244] In this embodiment, for example, as shown in the flowchart of Figure 8, first, in step S801, the user operates the aforementioned delivery button on the screen of the mobile terminal 90, and then, in step S802, the mobile terminal 90 requests access to the management server 140 of the second system 110.

[0245] In response to this, in step S831, the management server 140 permits access from the mobile terminal 90, and then in step S832, the management server 140 requests access to the management server 40 of the system 10.

[0246] In response to this, in step S851, if the management server 40 permits access from the management server 140, then in step S852, the amount of the parking fee is calculated as described above, and then in step S853, parking fee data representing the amount of the parking fee is sent to the management server 140.

[0247] In response, in step S833, management server 140 receives the parking fee data. Then, in step S834, it creates payment code data as image data representing a payment code (e.g., a QR code (registered trademark) or barcode) that indicates the parking fee amount represented by the received parking fee data as the payment amount. The payment code indicates the amount to be paid by the user this time and that the payment will be made by the code reading payment described above. The payment amount is encrypted and reflected in the payment code.

[0248] Then, in step S835, the management server 140 transmits the created payment code data to the communication device of the settlement machine 30.

[0249] In response to this, in step S861, the computer of the settlement machine 30 displays the corresponding settlement code on the screen of the settlement machine 30 based on the received settlement code data.

[0250] In response to this, in step S803, the user reads the displayed payment code with the camera of the mobile terminal 90. Subsequently, in step S804, the mobile terminal 90 converts the payment code into an electrical signal, thereby creating read data.

[0251] Then, in step S805, the mobile terminal 90 starts a decryption application stored in its memory to restore the payment amount from the read data. Next, in step S806, the mobile terminal 90 reads from its memory the credit card number associated with the current user as electronic payment information.

[0252] Thereafter, in step S807, the mobile terminal 90 transmits the restored payment amount and the read electronic payment information to the impersonation management server 140, associating them with the user.

[0253] In response to this, in step S837, the spoofing management server 140 determines whether or not a match is established between the received payment amount and the parking fee amount represented by the parking fee data received in the above-mentioned step S833.

[0254] A successful match means that the decryption rules used by the mobile terminal 90 were correct, and in turn means that the decryption application used by the mobile terminal 90 has been approved by the management server 140 (that is, the decryption application has been properly downloaded from the second system 110 and installed in the memory of the mobile terminal 90). The fact that the decryption application used by the mobile terminal 90 has been approved by the management server 140 means that the current user is qualified to be a member of the second system 110.

[0255] Then, in step S838, the impersonation management server 140 sends an electronic payment request to the payment server 160. Furthermore, in step S839, the impersonation management server 140 sends the electronic payment information to the payment server 160. Furthermore, in step S840, the impersonation management server 140 sends payment amount data indicating the payment amount to the payment server 160.

[0256] In response to this, in step S874, the payment server 160 performs electronic payment (credit card payment) based on the received electronic payment information and payment amount data. Then, in step S875, a completion signal indicating that the electronic payment has been completed is sent to the impersonation management server 140 and the real management server 40. This allows the impersonation management server 140 and the real management server 40 to know that the payment of the parking fee has been completed in the form of electronic payment.

[0257] In response to this, in step S842, the impersonation management server 140 transmits a payment completion signal indicating that the electronic payment has been completed to the mobile terminal 90. This notifies the user that the electronic payment has been completed.

[0258] In response to this, in step S854, the physical management server 40 transmits a payment completion signal to the communication device of the payment adjustment machine 30. As a result, the payment adjustment machine 30 is notified that the payment of the parking fee has been completed in the form of electronic payment.

[0259] According to this embodiment, the system 10, which cannot support code reading payment by itself, can use the payment means of the second system 110, which can support code reading payment, to enable the user to make code reading payment.

[0260] As can be easily understood from the above explanation, according to the present invention, a first payment system (non-electronic payment compatible) 10, which cannot support either credit card payments or code reading payments on its own, can be made to support at least credit card payments by being combined with a second payment system (electronic payment compatible) 110, which can support at least credit card payments.

[0261] Furthermore, according to the present invention, a first payment system (non-electronic payment compatible) 10, which cannot support either credit card payments or code reading payments on its own, can be made compatible with at least code reading payments by being combined with a second payment system (electronic payment compatible) 110, which can support at least code reading payments.

[0262] Furthermore, according to the present invention, a first payment system (electronic payment compatible) 10 that can handle credit card payments on its own but cannot handle code reading payments on its own becomes capable of handling at least code reading payments by being combined with a second payment system (electronic payment compatible) 110 that can handle at least code reading payments.

[0263] <Multiple payments>

[0264] In some of the embodiments described above, the system (first system) 10 cooperates with one second system 110 in the payment procedure, thereby expanding the range of payment types that the system (first system) 10 can virtually handle from non-electronic payments to electronic payments.

[0265] However, the types of electronic payments that the second system 110 can handle are limited, and there is a possibility that the types of electronic payments that the system (first system) 10 can pseudo-handle may not match the types of electronic payments that the user can use.

[0266] In this case, the system (first system) 10 cannot support the types of electronic payments available to users even with the help of the second system 110. In other words, there is a problem in that there is a limit to the expansion of the types of electronic payments that the system (first system) 10 can support.

[0267] In order to solve this problem, the present invention can be implemented, for example, in the following manner.

[0268] This aspect is also directed to a system (first system) 10 that provides certain goods or services or personal or real property to users.

[0269] This system (first system) 10 is either capable of supporting non-electronic payments but not electronic payments on its own, or is capable of supporting at least limited types of electronic payments on its own. This system 10 includes a user's mobile terminal 90 and a settlement machine 30 or payment machine that, in a normal payment mode, allows the user to make payments using payment methods that the system 10 can support on its own.

[0270] This system (first system) 10 operates in conjunction with a number of second systems 110, each of which provides users with goods or services or personal or real property of the same or different type as system 10, in relation to payment procedures.

[0271] Each of these second systems 110 may be capable of accepting one or more types of electronic payments.

[0272] Furthermore, the second systems 110 do not completely match each other in terms of the types of electronic payments they can handle.

[0273] In particular, the second systems 110 may choose to include at least one different type of electronic payment between them, or may choose not to share any of the same electronic payment types at all.

[0274] Furthermore, the second systems 110 are not exclusive in use and can be used in combination with a plurality of other second systems that completely match each other in the types of electronic payments they can support.

[0275] This system (first system) 10 has a determination unit that, when the mobile terminal 90 receives an electronic payment request from a user (for example, by operating the aforementioned withdrawal button), determines the type of electronic payment specified by the electronic payment request.

[0276] This system (first system) 10 further has a selection unit that, when the type of user-specified electronic payment made by the mobile terminal 90 does not match any of the types of electronic payment that the system can support, selects one of the multiple second systems 110 that covers the type of user-specified electronic payment as a substitute system 110.

[0277] This system (first system) 10 further has a substitute payment unit that, when the substitute system 110 is selected, causes the mobile terminal 90 to access the substitute system 110 in a substitute electronic payment mode, either via or without another communication device (e.g., management server 40), whereby the substitute system 110 performs the user-specified electronic payment on behalf of the system 10.

[0278] The substitute system 110 communicates with the settlement machine 30 or the payment machine of the system 10, with or without going through another communication device (e.g., the management server 40), so that the settlement machine 30 or the payment machine of the system 10 receives a payment completion signal from the substitute system 110. This completes the user-specified electronic payment with the help of the substitute system 110.

[0279] According to this system 10 (first system), if the type of electronic payment available to the user does not match the type of electronic payment that system 10 can handle, one of multiple second systems 110 that covers the type of electronic payment available to the user is automatically selected, and the selected second system 110 functions as the payment means for system 10, so that system 10 becomes pseudo-capable of handling the types of electronic payment that the user can handle.

[0280] This allows the system (first system) 10 to virtually accommodate any type of electronic payment available to the user, thereby improving the convenience of the user in the payment process.

[0281] That is, this system (first system) 10 does not realize only one type of electronic payment, but realizes so-called multi-payment, which allows multiple types of electronic payments to be realized in a pseudo manner, within the same system 10. Here, the term "multi-payment" means that the types of electronic payments available to users are diversified.

[0282] It should be noted that the above-mentioned technology of displaying a payment code on the screen (e.g., LCD) of the settlement machine 30 of the system 10, thereby enabling the user to pay the current parking fee later using a code reading payment method, can be realized without relying on the second system 110; specifically, for example, by the management server 40 transmitting data for displaying the payment code to the communication device of the settlement machine 30 of the same system 10.

[0283] The concept of multi-payment has been explained above, but a specific example, a multi-electronic payment system 1000, will now be explained with reference to FIGS.

[0284] As shown in FIG. 10, this multi-electronic payment system 1000 has a first system 10 capable of supporting a single type of electronic payment (which may also be capable of supporting non-electronic payments) and multiple second systems 110 which, as mentioned above, do not completely match each other in terms of the types of electronic payments they can support.

[0285] However, it is sufficient for either system 10 or 110 to provide users with the payment service, and it is not essential to implement the present invention that the systems 10 and 110 be configured to provide services other than payment (e.g., parking lot management business), as in some of the examples described above.

[0286] Specifically, the first system 10 is a payment system to which a user's mobile terminal 90 is directly connected, regardless of the type of electronic payment (user-specified electronic payment) available to the user. The first system 10 has a management server 40 as a real management server, and is connected to a payment server 160 that can handle the corresponding type of electronic payment.

[0287] On the other hand, one of the multiple second systems 110 is a payment system selected by the first system 10 as one that matches the type of electronic payment specified by the user. The selected second system 110 is a complementary payment system to which the mobile terminal 90 is indirectly connected, without the user's knowledge, via the management server 40 (real management server) of the first system 10. The selected second system 110 has the management server 140 as a deemed management server or pseudo management server, and is connected to a payment server 160 that can handle the corresponding type of electronic payment.

[0288] The payment server 160 assigned to the first system 10 and the payment server 160 assigned to each second system 110 are generally managed by the respective businesses that operate the corresponding types of electronic payment services.

[0289] <Electronic payment request for single payment fee>

[0290] Figure 11 is a conceptual flowchart illustrating the operation of the multi-electronic payment system 1000 shown in Figure 10. For the example shown in Figure 11, the term "multi-payment" is used to mean a variety of electronic payment types available to users.

[0291] First, in step S1101, a user who wishes to make an electronic payment connects the mobile terminal 90 to the real management server 40 of the first system 10.

[0292] Specifically, the user is charged a fee in exchange for business (such as the sale of tangible goods or the provision of intangible services) provided to the user by the first system 10 or another system, and uses this multi-electronic payment system 1000 to pay the fee by electronic payment, apparently to the first system 10, but actually to the first system 10 or any of the second systems 110.

[0293] Here, "intangible services" include, for example, the provision of food and drink, the use of rental items, the use of parking lots, and the use of public transport.

[0294] In step S1101, the user transmits an electronic payment request to the real management server 40 in association with the user's electronic payment information, user identification information, and fee-related information.

[0295] Here, "electronic payment information" includes, for example, the type of electronic payment that the current user wishes to use (e.g., type of prepaid card, type of credit card, type of cryptocurrency, etc.), and information specific to the user regarding the electronic payment (e.g., prepaid card number, type of credit card, cryptocurrency number, etc.).

[0296] Furthermore, the "user identification information" includes, for example, a user ID or identification information unique to the mobile terminal 90.

[0297] Furthermore, the "fee-related information" includes, for example, the payee of the fee and one or more payment items (or purchase items) that make up the fee.

[0298] In relation to this step S1101, Figure 12 shows an example of electronic payment request related information for a single payment fee for making an individual electronic payment of a single payment fee to a single payee for one type 1 purchasing activity unit (for example, an activity of purchasing multiple items at the same store, or an activity of receiving multiple food and beverage items at the same store).

[0299] As used herein, "single payment fee" means a fee for one or more purchased items each having a separate fee, but where each separate fee is paid to a single payee, and ultimately the total fee for all such fees is paid to the same payee.

[0300] In response to the execution of step S1101, in step S1131 the real management server 40 receives an electronic payment request, electronic payment information, user identification information, and fee-related information in association with one another from the mobile terminal 90. For convenience of explanation, the collection of the electronic payment request, electronic payment information, user identification information, and fee-related information is referred to as electronic payment request-related information.

[0301] Next, in step S1132, the actual management server 40 calculates the fee to be charged to the user based on the received fee-related information and / or fee information associated with the fee-related information and received from a billing server operated by or for the corresponding payee entity (e.g., an individual store or franchise store such as a restaurant, a general commercial facility such as a department store, another parking lot management company, an entity operating each means of transportation, etc.).

[0302] Thereafter, in step S1133, the real management server 40 extracts information indicating the type of user-specified electronic payment from the received electronic payment information, and determines the type of electronic payment currently requested from the extracted results.

[0303] Electronic payment types are broadly classified into prepaid card payments, credit card payments, etc. The types of electronic payment are further classified, for example, by the type of company that handles the prepaid card, and by the type of credit card company that handles the credit card.

[0304] Next, in step S1134, the actual management server 40 determines whether the type of electronic payment determined (i.e., the type of electronic payment specified by the user this time) matches the type of electronic payment that can be supported by the first system 10 (there may be only one type or there may be multiple types).

[0305] If the electronic payment specified this time can be handled by the first system 10, the judgment in step S1134 will be YES, and then in step S1135, the actual management server 40 will send an electronic payment request together with the electronic payment information, the user identification information, and the fee calculation result (such as the execution result of step S1133) to the payment server 160 assigned to the first system 10 (the payment server 160 located on the left side in Figure 10).

[0306] In response to execution of step S1135 described above, the settlement server 160 receives the electronic settlement request, electronic settlement information, user identification information, and fee calculation result, all of which are associated with each other, from the real management server 40. Next, in step S1175, the settlement server 160 executes the electronic settlement desired by the user. After that, in step S1176, the settlement server 160 transmits a settlement completion signal, indicating that the electronic settlement has been completed, to the real management server 40, in association with the user ID.

[0307] In response, in step S1136, the actual management server 40 receives the payment completion signal from the payment server 160 in association with the user ID, references the user ID, identifies one of the mobile terminals 90 as the mobile terminal 90 of the current user, and transfers the payment completion signal to that mobile terminal 90.

[0308] In response, the mobile terminal 90 receives the transferred payment completion signal in step S1103. Thereafter, the mobile terminal 90 displays on the screen and / or outputs a message (together with the payment amount, for example) indicating that the electronic payment has been completed.

[0309] The above describes the case where the user-specified electronic payment can be handled by the first system 10. However, if the first system 10 cannot handle the user-specified electronic payment, the judgment in step S1134 will be NO, and in step S1137, the actual management server 40 will select one of the multiple second systems 110 that can handle the user-specified electronic payment.

[0310] Here, if there are multiple second systems 110 that can accommodate user-specified electronic payments, the actual management server 40 first provisionally selects each of the multiple second systems 110 that can accommodate user-specified electronic payments as multiple candidates.

[0311] Next, the actual management server 40 narrows down the provisionally selected candidates to only one second system 110 according to a predetermined priority determination rule, or narrows down the multiple candidates to a small number of candidates, presents the small number of candidates to the user via the mobile terminal 90, and allows the user to select one of the candidates.

[0312] Here, the "predetermined priority determination rule" includes, for example, a rule to preferentially select a second system 110 for which the same user has a past usage history, or a rule to preferentially select a second system 110 that, when a user uses any of the second systems 110, offers a benefit (e.g., redemption points) that is higher than a standard level and is more advantageous than other second systems 110 in terms of benefits.

[0313] Next, in step S1138, the real management server 40 associates the electronic payment request with the user ID and sends it to the deemed management server 140 (hereinafter referred to as the “current deemed management server”) 140 in the selected second system 140.

[0314] In response, in step S1151, the current deemed management server 140 associates the received electronic payment request with the user ID and forwards it to the payment server 160 assigned to the current second system 140 (the payment server on the right in Figure 10, hereinafter referred to as the "current payment server").

[0315] In response to this, the current payment server 160 receives the current electronic payment request in association with the user ID in step S1171, and then executes the electronic payment desired by the user in step S1172. After that, in step S1173, the current payment server 160 transmits a payment completion signal indicating that the current electronic payment has been completed to the current deemed management server 140 in association with the user ID.

[0316] In response to this, in step S1152, the current deemed management server 140 associates the payment completion signal with the user ID and transfers it to the real management server 40. In response, the real management server 40 refers to the user ID and transfers the payment completion signal to the mobile terminal 90 of the current user.

[0317] In response, the mobile terminal 90 receives the transferred payment completion signal in step S1102. Thereafter, the mobile terminal 90 displays on the screen and / or outputs a message (together with the payment amount, for example) indicating that the electronic payment has been completed.

[0318] Each management server 140 may be capable of supporting one or more types of electronic payments, and each payment server 160 assigned to each management server 140 may be capable of supporting one or more types of electronic payments.

[0319] 10 and 11, the first system 10 has a payment function (whether non-electronic or electronic) in addition to a fee calculation function that calculates the fee to be charged to the user and a selection function that selects one of the second systems 110 depending on the type of electronic payment designated by the user (i.e., a payment route selection function that selects a payment route), but the payment function may be omitted, and the fee calculation function may also be deleted from the first system 10 if the same function is realized elsewhere. In other words, it is sufficient for the first system 10 to have at least the selection function.

[0320] Furthermore, in the examples shown in Figures 10 and 11, for ease of explanation, it is possible to consider that the management server 40 in the first system 10 constitutes an example of the aforementioned "payment route selection server," and that the multiple management servers 140 in the multiple second systems 110 constitute an example of the aforementioned "multiple management servers."

[0321] Additionally, in the examples shown in FIGS. 10 and 11, multiple management servers 140 share one management server 40, but are independent of one another in terms of configuration, without depending on that management server 40.

[0322] Therefore, as long as the management servers 140 can establish a connection with the management server 40, it is not essential that they have compatibility in terms of the communication environment or be able to communicate with each other.

[0323] Additionally, in the examples shown in Figures 10 and 11, multiple management servers 140 are operated by different business entities and / or are installed in different locations (e.g., locations in the real space, locations in the virtual address space).

[0324] Therefore, in the examples shown in Figures 10 and 11, in order to expand the range of types of electronic payments available to a single user, multiple existing management servers 140 are selected, each capable of supporting a different type of electronic payment, and then all of these management servers 140 are simply connected to a common management server 40 without any work (such as modifications or design changes) to unify their respective communication environments and specifications, thereby creating a multi-electronic payment communication network as shown in Figure 10.

[0325] As a result, according to the examples shown in Figures 10 and 11, the types of electronic payments available to a single user can be expanded simply by connecting the existing management servers 140 to the management server 40, without any substantial modification to the setting conditions (e.g., communication conditions, etc.) of the multiple management servers 140, and without the need to change their installation locations.

[0326] As a result, according to this example, it becomes easy to improve user convenience while suppressing an increase in the economic burden (for example, facility costs) on the business operator.

[0327] The above description of the multi-electronic payment system 1000 with reference to Figures 10 and 11 is directed to a scenario in which a user pays the above-mentioned single payment fee for one of the above-mentioned first type purchase activity units to one payee (e.g., one business entity linked to the first system 10).

[0328] As a result, specifically, as shown in FIG. 11, whether electronic payment is made by the first system 10 triggered by the execution of step S1135, or whether electronic payment is made by any of the second systems 110 triggered by the execution of step S1138, the user will ultimately make electronic payment to one business entity linked to the first system 10 and pay a fee to that business entity, for example.

[0329] <Electronic payment request for multiple payment charges>

[0330] In the multi-electronic payment system 1000 shown in Figures 10 and 11, the role of the first system 10 and the management server 40 is to, when the management server 40 receives electronic payment request-related information from the user's mobile terminal 90, identify the type of electronic payment (usually one electronic payment, but it may be multiple electronic payments) that the user wishes to use from the received electronic payment request-related information, select from the management server 40 of the first system 10 and the multiple management servers 140 of the multiple second systems 110 those that can handle electronic payments that match the identified one or more electronic payments, and perform the electronic payment using the selected one or more management servers 40, 140.

[0331] Figure 13 is a conceptual flowchart showing the operation of a variant of the multi-electronic payment system 1000 shown in Figures 10 and 11. The variant shown in Figure 13 has the same hardware configuration as that shown in Figure 10.

[0332] In the variant shown in Figure 13, the role of the first system 10 and management server 40 is that when the management server 40 receives electronic payment request-related information from the user's mobile terminal 90, it identifies from the received electronic payment request-related information one or more businesses to which one or more fees imposed on the user are to be paid, selects from multiple management servers 140 of multiple second systems 110 those operated by the identified one or more businesses, and carries out electronic payment using the selected one or more management servers 140.

[0333] In this variant, the management server 40 has only the function of selecting from a plurality of second systems 140, i.e., the payment route selection function, and does not have the electronic payment function, but may be designed to have this electronic payment function as well.

[0334] In any case, from the user's perspective, it is the management server 40 to which the user's mobile terminal 90 is directly connected, but the management server 140 is not directly connected to the mobile terminal 90, so it is possible to classify the management server 40 as a real management server and the management server 140 as a deemed management server. However, if the management server 40 does not have an electronic settlement function, it may not be appropriate to call the management server 140 a deemed management server as far as the task of electronic settlement is concerned.

[0335] In terms of payment method, as mentioned above, the electronic payment system 1000 shown in Figures 10 and 11 is typically designed to allow a user to pay a single payment fee to one payee for one first type purchase activity unit.

[0336] In contrast, one variant of the multi-electronic payment system 1000 shown in Figure 13 is designed to enable a user to make comprehensive electronic payments of a composite payment fare to multiple payees (e.g., multiple transportation operator entities) for one second-type purchase activity unit (e.g., an activity in which the same user prepays transportation fares to transfer between multiple transportation facilities operated by different entities), regardless of whether the multiple second systems 110 have in common or different types of electronic payment they can support (e.g., when they have in common).

[0337] Therefore, for the example shown in Figure 13, the term "multi-payment" is used to mean compounding individual payment units (payees) that a user can electronically pay at once. In other words, "multi-payment" here means that a user can collectively pay multiple individual fees with different payees with just one electronic payment.

[0338] Below, this modified example of the multi-electronic payment system 1000 will be explained with reference to Figures 13 and 14, taking as an example a case where multiple second systems 110 have common types of electronic payment that they can handle. In Figure 13, steps that are common to the steps shown in Figure 11 are given the same step numbers, thereby avoiding redundant written explanations.

[0339] First, in step S1301, a user who wishes to make an electronic payment connects the mobile terminal 90 to the management server 40 of the first system 10 in accordance with step S1101 described above.

[0340] Specifically, a user is charged a fee in exchange for business (such as the sale of tangible goods or the provision of intangible services) provided to the user by one or more second systems 140, and uses this multi-electronic payment system 1000 to pay the fee either in its entirety to only one second system 110, or divided into multiple fee portions (fees per payee) and individually to each of the corresponding multiple second systems 110 by electronic payment.

[0341] In relation to this step S1301, Figure 14 shows an example of electronic payment request related information for a composite payment fee for comprehensive electronic payment of the composite payment fee to multiple payees for one second type purchase activity unit.

[0342] Here, the "composite payment fee" is configured as a collection of multiple individual fees that are each paid to multiple different payees, and these individual fees are paid to the corresponding payees by the first system 10. At least the total amount of the composite payment fee may be notified to the user visually or audibly via the mobile terminal 90.

[0343] For example, when a user travels from a starting point A to a destination point B by using multiple modes of transportation (e.g., rental bicycle or car, public bus, subway, train, airplane, taxi, etc.), the user is typically required to access a different management server 140 directly using the mobile terminal 90 and make an electronic payment for each mode of transportation used.

[0344] In contrast, according to this variant, even if the user transfers between multiple modes of transportation, the user only needs to access the same management server 40 (one first system 10) directly with the mobile terminal 90 once and make electronic payment only once.

[0345] As a result, this variant enables the user to comprehensively electronically pay a composite payment fee consisting of multiple individual fees (e.g., with a single electronic payment request), thereby reducing the operational burden on the user and the communication load on the mobile terminal 90.

[0346] Specifically, in this modified example, it is assumed that, before using a certain transportation facility at a departure point A, a user prepays the total fare to a destination point B by electronic payment.

[0347] In this case, the mobile terminal 90 transmits an electronic payment request and a collection of multiple sections of use for each transportation facility (corresponding to a collection of multiple payees and multiple payment items) to the management server 40. The management server 40 then sequentially selects, for each section of use, one of the multiple management servers 140 that is operated by the transportation facility that has jurisdiction over that section of use, and transmits the electronic payment request, information about the corresponding section of use (specified by both the payee and payment items), and the user's electronic payment information (e.g., credit card number) to the selected management server 140.

[0348] As a result, each relevant management server 140 electronically settles the fare appropriate for the relevant section of use using the relevant settlement server 160.

[0349] In response to the execution of step S1301, the management server 40 receives the electronic payment request related information in step S1131.

[0350] Next, in step S1302, management server 40 determines one or more payees for the fee charged to the user by referring to the received electronic payment request-related information, particularly information related to the payee. In the example shown in Figure 12, one payee is determined for one electronic payment request, and in the example shown in Figure 14, multiple payees are determined for one electronic payment request.

[0351] Next, in step S1303, based on the received electronic payment request-related information, the management server 40 selects one or more second systems 140 from the multiple second systems 140 to which the management server 40 should be connected in order to electronically settle the fee charged to the current user.

[0352] For example, when the electronic payment request-related information has only one payee, as illustrated in Fig. 12, one of the plurality of second systems 140 associated with the same payee is selected as one second system 140 for electronic payment. On the other hand, when the electronic payment request-related information has multiple payees, as illustrated in Fig. 14, one of the plurality of second systems 140 associated with the same payee is selected as multiple second systems 140 for electronic payment.

[0353] Thereafter, in step S1304, the management server 40 transmits an electronic payment request for each payee to the management server 140 of each selected second system 110 together with the electronic payment information, user identification information and fee-related information.

[0354] In response, each selected management server 140 receives the corresponding electronic payment request-related information in step S1305, and then, in step S1306, each management server 140 calculates the amount of the fee portion that the user should electronically pay to each management server 140 by referring to the received electronic payment request-related information, particularly the fee-related information.

[0355] Next, in step S1307, each management server 140 transmits electronic payment request related information, i.e., the electronic payment request, electronic payment information, user identification information, and fee calculation result (such as the execution result of step S1306), associated with each other, to the payment server 160 corresponding to each management server 140.

[0356] According to this variant, when the price for one event, service, or item provided to one user includes multiple types of fees corresponding to multiple payees, the user can complete all electronic payments for all payees by accessing management server 40 only once using mobile terminal 90, thereby improving user convenience.

[0357] It should be noted that in the example shown in Figure 13, for ease of explanation, the management server 40 in the first system 10 constitutes an example of the aforementioned "payment route selection server," and the multiple management servers 140 in the multiple second systems 110 can be considered to constitute an example of the aforementioned "multiple management servers."

[0358] Additionally, in any of the above-described embodiments, when code reading payment is adopted as the electronic payment, the payment server 160 is managed and operated by a code payment service provider. In contrast, when credit card payment is adopted as the electronic payment, the payment server 160 is managed and operated by a credit card payment service provider.

[0359] Unlike credit card payments, code reading payments have the advantage of reducing the introduction costs of the systems 10 and 110 because they do not require the installation of credit verification terminals in the systems 10 and 110. Therefore, the above-mentioned technology is beneficial to the administrators and operators of the systems 10 and 110.

[0360] Although some exemplary embodiments of the present invention have been described in detail above with reference to the drawings, these are merely examples, and the present invention can be embodied in other forms that incorporate various modifications and improvements based on the knowledge of those skilled in the art, including the embodiments described in the "Summary of the Invention" section above.

Claims

1. An electronic payment agency system as a system that acts as an agent for electronically paying a fee charged to a user of another system that provides a first service to the user as consideration for the user's use of the first service, The other system includes a plurality of rental objects, each of which is movable or immovable property; The electronic payment agency system allows the user to access the electronic payment agency system via a communication terminal at the start and end of use of any rental item in the other system, and make electronic payment for the fee based on rental item identification information for identifying any rental item received from the communication terminal at the end of use, and fee information associated with any rental item at the end of use and representing the amount of the fee.

2. The electronic payment agency system of claim 1, wherein the other system has a fee calculation function that calculates the amount of the fee for each rental item based on the length of time it is used, and the fee information is identified by the fee calculation function.

3. The other system includes a settlement machine that does not support electronic settlement and performs settlement by communication with the user's communication terminal, and a first management server that can communicate with the settlement machine; 3. The electronic settlement agent system according to claim 2, wherein the fee calculation function is realized by at least one of the settlement machine and the first management server.

4. The other system exists as a plurality of other systems, The electronic payment agency system of claim 1, wherein the electronic payment agency system is capable of identifying which of the plurality of other systems the user is currently located in by using the positioning results obtained by the positioning function of the communication terminal and / or the results obtained by the communication terminal reading a code displayed at a location where any of the other systems provides the first service to the user.

5. The electronic payment agency system includes a second management server; 2. The electronic payment agency system according to claim 1, wherein the second management server enables electronic payment of the fee based on the rental object identification information and the fee information received from the communication terminal.

6. The other system includes a settlement machine that does not support electronic settlement and performs settlement by communication with the user's communication terminal, and a first management server that can communicate with the settlement machine; 6. The electronic payment agency system of claim 5, wherein the communication terminal is capable of transitioning between a fee calculation stage for calculating the amount of the fee using the first management server or the second management server, and an electronic payment stage for providing electronic payment services to users of the other system using the second management server.

7. The plurality of rental objects are provided with a plurality of transmitters that transmit a plurality of identification codes that are unique to the corresponding rental objects or a plurality of transmitters that transmit a signal that is unique to the corresponding rental objects by a short-range wireless method, The electronic payment agency system of claim 1, which enables electronic payment for the fee based on the rental item specific information and the fee information received from the communication terminal in response to the communication terminal reading any identification code or receiving the signal from any transmitter.

8. The electronic payment agency system according to claim 7 , wherein each rental object includes a parking space in a parking lot as real property or a vehicle as personal property.

9. 7. A program for causing a computer to function as the second management server according to claim 5.

10. A computer-readable recording medium on which the program according to claim 9 is recorded.

Images