PAYMENT PROCESSING DEVICE, PAYMENT PROCESSING METHOD, AND PAYMENT PROCESSING PROGRAM

Abstract

To provide a payment processing device, method, and program for supporting payment by a plurality of users for enabling a user to select remittance after knowing an amount to be paid to other user when the payment is made by the plurality of users.SOLUTION: In a communication system, an electronic settlement server 1 for executing price settlement processing using an electronic settlement application executes processing to: receive settlement request information indicating a request for settlement using a user terminal 2-1 used by any first user belonging to a group of users; acquire an amount of burden charge charged to a second user belonging to the group from payment to be settled according to the settlement request information; transmit burden charge amount information indicating the amount of burden charge to a terminal 2-2 used by the second user; in response to that the terminal device 2-2 having received the burden charge amount information accepts operation to transfer money, receive remittance request information indicating a request for money transfer from the terminal device 2-2; and upon receipt of the money transfer request information, execute processing for transmitting the burden charge from the second user to the first user.SELECTED DRAWING: Figure 12

Description

[Technical field]

[0001] The present invention relates to a method for facilitating multi-user payment. [Background technology]

[0002] When a group uses a facility or purchases something, the group may split the cost, etc. Conventionally, there have been known techniques for supporting such payments.

[0003] For example, Patent Document 1 discloses a technique for splitting and settling multiple payments made by multiple people on mobile terminals. In this technique, user A sets up a group including user A and user B in advance. When user A makes a payment, user A's terminal transmits payment information to the server, and the server calculates the expenditure and allocation for the payment within the group. When user B makes a payment, user B's terminal also transmits payment information to the server, and the server similarly calculates the expenditure and allocation. In response to a request for split calculation from user A, the server calculates the total expenditure and total allocation for each user, and transmits a notice to user B's terminal that the split payment will be made. User B's terminal displays a screen indicating that the split payment will be made. When user B approves the split payment, the server calculates the offset amount for each user, and transfers money between the users in the group based on the offset amount. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2020-166365 Summary of the Invention [Problem to be solved by the invention]

[0005] However, a user who is going to send money to another user in the group cannot know whether the other user will send money or not until the transfer is actually performed. A user may want to select a transfer after knowing the amount to be paid to the other user.

[0006] The present invention has been made in consideration of the above points, and one example of its objective is to provide a payment processing device, a payment processing method, and a payment processing program that, when multiple users are paying for something, enable a user to select a transfer after knowing the amount to be paid to other users. [Means for solving the problem]

[0007] In order to solve the above problem, the invention described in claim 1 provides a payment method using a first terminal device used by a first user belonging to a user group, the payment method including: a payment request information receiving means for receiving payment request information indicating a request for payment of a price to be paid by the first user; and a payment request information receiving means for receiving the payment request information indicating a request for payment of the price to be paid by the first user. Chi, The system is characterized in that it comprises: a burden amount acquisition means for acquiring the amount of a burden to be charged to a second user belonging to the group and different from the first user; a burden amount information transmission means for transmitting burden amount information indicating the acquired amount of the burden to a second terminal device used by the second user; a remittance request information receiving means for receiving remittance request information indicating a remittance request from the second terminal device in response to the second terminal device receiving the transmitted burden amount information accepting a remittance operation; a remittance means for executing a process of remitting the burden from the second user to the first user in response to the remittance request information being received by the remittance request information receiving means; and an granting means for executing a process of granting a benefit to the first user on the condition that the remittance means has executed the process of remitting the burden from the second user to the first user.

[0008] According to this invention, the payment is settled using a first terminal device of a first user belonging to a group. As a result, the first user pays the payment once. After that, payment amount information indicating the amount of the payment to be paid by a second user belonging to the group is transmitted to a second terminal device used by the second user. Therefore, the second user can know the payment amount. Then, the second user operates the second terminal device, whereby the payment amount is transferred from the second user to the first user. Therefore, when multiple users pay the payment, the users can select the transfer after knowing the amounts to be paid to the other users.

[0009] The invention described in claim 2 is characterized in that the amount paid in accordance with the received payment request information is an amount paid to any facility, and further comprises a location relationship information acquisition means for acquiring location relationship information indicating a location relationship between the first terminal device and at least one terminal device different from the first terminal device, the location relationship information including first location information indicating the location of the first terminal device, and an identification means for identifying, as the second user belonging to the group, a user using a terminal device among the at least one terminal device, whose location relationship when the first terminal device is located at the facility is indicated to be a predetermined location relationship by the acquired location relationship information.

[0010] According to this invention, positional relationship information indicating a positional relationship between a first terminal device and another terminal device is acquired. The positional relationship between the terminal devices may be a positional relationship between users who use those terminal devices. Then, a user who has a predetermined positional relationship with the first user when the first user is in a facility to which the payment is to be made is identified as a second user who belongs to the same group as the first user. Since the first user and the second user who have a predetermined positional relationship may use the facility together, it may be appropriate for the second user to bear at least a part of the fee paid by the first user. Therefore, even if the user does not perform the task of setting up a group, it is possible to identify users who belong to a group who used the facility.

[0011] The invention described in claim 3 is characterized in that the identification means identifies the second user on condition that the first location information indicates that the first terminal device has been located in the facility for a predetermined period of time or more.

[0012] According to this invention, when a first user stays in a facility for a predetermined time or more, a second user who belongs to the same group as the first user is identified. In order for a user to use a facility, the user may need to stay in the facility for a certain amount of time. Therefore, it is possible to identify a situation in which the first user is likely to be using the facility, and to identify a second user who is likely to be using the facility together with the first user.

[0013] The invention described in claim 4 is characterized in that the identification means identifies the second user from among users who use a terminal device among the at least one terminal device, the positional relationship between which and the first terminal device is a predetermined positional relationship when the first terminal device is located outside the facility.

[0014] According to this invention, even if the positional relationship between the first user and the user is a predetermined positional relationship when the first user is inside the facility, the user who is not in the predetermined positional relationship when the first user is outside the facility may not be identified as a second user belonging to the same group as the first user. Therefore, a user who happens to be present with the first user at the facility but does not act together with the first user outside the facility can be excluded from the second users belonging to the same group as the first user.

[0015] The invention described in claim 5 is characterized in that the acquired location relationship information further includes communication status information indicating the status of wireless communication between the first terminal device and each of the at least one terminal device, and the identification means identifies the location relationship between the first terminal device and each of the at least one terminal device based on the communication status information.

[0016] According to the present invention, the positional relationship between terminal devices is identified based on the state of wireless communication between the terminal devices. For example, the state of reception by another terminal device of a signal wirelessly transmitted from one terminal device may be affected by the positional relationship between the terminal devices. Therefore, the positional relationship between users can be appropriately identified.

[0017] The invention described in claim 6 is characterized in that each of the at least one terminal device transmits a specified signal wirelessly, the communication status information indicates the terminal device that transmitted the specified signal that reached the first terminal device, and the identification means identifies the second user from among users who use the terminal device that transmitted the specified signal that reached the first terminal device.

[0018] According to this invention, each terminal device transmits a predetermined signal wirelessly. Among the users using the terminal device that has received the transmitted predetermined signal, a second user who belongs to the same group as the first user is identified. The positional relationship between users within the range reached by the predetermined signal is likely to be such that the users can easily act as a group. Therefore, the second user who uses the facility together with the first user can be appropriately identified.

[0019] The invention described in claim 7 further comprises a remittance history information acquisition means for acquiring remittance history information indicating a remittance history capable of identifying each user, the remittance source and the remittance destination, in which the first user is either the remittance source or the remittance destination, and the identification means is characterized in that it identifies the second user based on the acquired location relationship information and the acquired remittance history information.

[0020] According to this invention, a second user who belongs to the same group as the first user is identified by further using remittance history information showing the history of remittances between users. A user who has remitted money to a first user is likely to be a user who acts together with the first user. Therefore, a second user who uses a facility together with the first user can be appropriately identified.

[0021] The invention described in claim 8 is a payment device described in claim 7, characterized in that the specified positional relationship includes a specified first positional relationship and a specified second positional relationship different from the first positional relationship, the identification means identifies a user using a terminal device whose positional relationship with the first terminal device is both the first positional relationship and the second positional relationship as the second user belonging to the group, and the identification means identifies a user using a terminal device whose positional relationship with the first terminal device is only one of the first positional relationship and the second positional relationship as the second user belonging to the group when there is an actual fact of remittance between the first user and the user.

[0022] According to this invention, a user who satisfies at least two of the location relationship conditions is identified as a second user who belongs to the same group as the first user. On the other hand, a user who satisfies only one of the conditions may also be a second user who belongs to the same group as the first user. Therefore, when a remittance is being made between such a user and the first user, the user is identified as a second user. Therefore, a second user who uses a facility together with the first user can be appropriately identified.

[0023] The invention described in claim 9 further includes a billing information sending means for sending billing information indicating the identified second user to the first terminal device, and an edited billing information acquisition means for acquiring edited billing information indicating the second user after editing in response to the first terminal device accepting an operation to edit the second user indicated by the transmitted billing information, wherein the charge amount acquisition means acquires the amount of the charge for the second user indicated by the acquired edited billing information, and the charge amount information sending means transmits the charge amount information to the second terminal device used by the second user indicated by the acquired edited billing information.

[0024] According to the invention, a first user may edit users identified by the payment device as second users who belong to the same group as the first user, e.g., may be able to add or remove second users.

[0025] The invention described in claim 10 is characterized in that the specified positional relationship is a positional relationship seen when the first user and the second user are using a facility as a group, and is a positional relationship between the first terminal device and the second terminal device.

[0026] The invention described in claim 11 is The granting means further The present invention is characterized in that a process of granting a privilege to the user is executed.

[0027] According to this invention, when the charge is transferred from the second user to the first user, the first user and the second user fart Therefore, the user can be encouraged to send money to split the bill.

[0028] The invention described in claim 12 is characterized in that the granting means grants the benefit, the value of which corresponds to the amount of the charge, to the second user.

[0029] According to this invention, the higher the amount of money the second user has to pay, the more the second user can be encouraged to remit money.

[0030] The invention described in claim 13 is a method for providing a first facility using a first facility, the first facility being a fee paid by the first user to the first facility when the first user uses the first facility, and the providing means providing a privilege that can be used at a second facility that is different from the first facility and is located within a predetermined range from the first facility, The first user or The second user is then given the information.

[0031] According to this invention, a benefit is given that can be used at a second facility located within a predetermined range from a first facility used by a group. Since the group was at the first facility, it is in a location that makes it easy to travel to the second facility. Therefore, it is possible to encourage the use of the second facility.

[0032] The invention described in claim 14 is a method for providing a service in which the first user pays a fee to a facility when the first user uses the facility, and the providing unit provides a privilege available at the facility, The first user or The second user is then given the information.

[0033] According to the present invention, it is possible to promote reuse of facilities.

[0034] The invention described in claim 15 is characterized in that the granting means grants the first user the benefit of a value corresponding to the amount of the fee minus the amount of the acquired charge.

[0035] According to this invention, the higher the amount borne by the first user, the more the first user can be encouraged to make a payment that allows remittance to split the bill.

[0036] The invention described in claim 16 is characterized in that the remittance means executes the process of remitting the charge in a specified electronic money, and the granting means grants the benefit to the first user if the remittance by the remittance means is the second user's first use of the specified electronic money.

[0037] According to this invention, when a second user who has never used a predetermined electronic money uses the predetermined electronic money for the first time to transfer money from the second user to the first user, a benefit is given to the first user. Therefore, by encouraging the first user to make a payment that allows for a transfer to split the bill, it is possible to promote the use of the predetermined electronic money.

[0038] The invention described in claim 17 is characterized in that the granting means grants a bonus to the first user when a payment process is executed in which the first user pays the fee and a process is executed by the remittance means to remit the charge from the second user to the first user, and does not grant a bonus to the first user when the payment process is executed but the process is not executed by the remittance means to remit the charge from the second user to the first user. Claim 18The invention described in is characterized in that the burden amount acquisition means determines the amount of the first user's burden and the amount of the second user's burden to amounts corresponding to the age of the first user and the age of the second user, respectively, and the burden amount information transmission means transmits the burden amount information indicating the amount of the burden determined for the second user by the burden amount acquisition means. Claim 19 The invention described in further comprises a second burden amount information transmitting means for transmitting second burden amount information indicating the acquired amount of the burden to the first terminal device, and a changed burden amount information acquiring means for acquiring changed burden amount information indicating the changed amount of the burden in response to the first terminal device accepting an operation to change the amount of the burden indicated by the transmitted second burden amount information, and is characterized in that the burden amount information transmitting means transmits the acquired changed burden amount information as the burden amount information.

[0039] According to this invention, the older the user is, the higher the fee that each user must pay. Therefore, each user can be required to pay an amount according to his / her age.

[0040] The invention described in claim 18 further comprises a second burden amount information transmitting means for transmitting second burden amount information indicating the acquired amount of the burden to the first terminal device, and a changed burden amount information acquiring means for acquiring changed burden amount information indicating the changed amount of the burden in response to the first terminal device accepting an operation to change the amount of the burden indicated by the transmitted second burden amount information, wherein the burden amount information transmitting means transmits the acquired changed burden amount information as the burden amount information.

[0041] According to this invention, the payment amount acquired by the payment device can be changed at the discretion of the first user.

[0042] Claim 20The invention described in further comprises a reservation information acquisition means for acquiring reservation information indicating a reservation made by the first user for services available during the trip, and a judgment means for respectively judging whether the payment request information has been received by the payment request information receiving means during the trip by the first user and whether the trip has ended based on the acquired reservation information, wherein the burden amount acquisition means, when there is a plurality of pieces of payment request information judged by the judgment means to have been received during the trip, acquires the amount of the burden corresponding to the sum of the multiple amounts of the fees to be paid in accordance with the multiple pieces of payment request information, and the burden amount information transmission means transmits the burden amount information indicating the sum of the amount of the burden acquired by the burden amount acquisition means in accordance with the sum of the amounts of the fees after it is judged by the judgment means that the trip has ended.

[0043] According to this invention, it is determined whether or not a payment using the first terminal is made during the first user's trip and whether or not the first user's trip has ended, based on reservation information for a service for the trip. If a payment is made during the first user's trip, processing for remittance based on splitting is not performed at that point. After the trip ends, processing for remittance based on splitting is performed by collecting multiple payments made during the trip. Therefore, the group to which the first user belongs can split the amount paid by the first user during the trip all at once after the trip.

[0044] Claim 21The invention described in the above is a payment method executed by a computer, the payment using a first terminal device used by any first user belonging to a user group, the payment method including a payment request information receiving step of receiving payment request information indicating a request for payment of a price to be paid by the first user, a burden amount acquisition step of acquiring an amount of a burden to be charged to a second user belonging to the group, the second user being different from the first user, from the price to be paid in accordance with the received payment request information, a burden amount information sending step of sending burden amount information indicating the acquired amount of the burden to a second terminal device used by the second user, a remittance request information receiving step of receiving remittance request information indicating a remittance request from the second terminal device in response to the second terminal device receiving the transmitted burden amount information and accepting a remittance operation, and a remittance step of executing a process of remittance of the burden from the second user to the first user in response to the remittance request information being received by the remittance request information receiving step. a granting step of executing a process of granting a privilege to the first user on condition that a process of transferring the charge from the second user to the first user has been executed in the remittance step; The present invention is characterized by comprising:

[0045] Claim 22 The invention described in the above relates to a payment system for a computer using a first terminal device used by a first user belonging to a user group, the system comprising: a payment request information receiving means for receiving payment request information indicating a request for payment of a price to be paid by the first user; a burden amount acquiring means for acquiring an amount of a burden to be charged to a second user belonging to the group and different from the first user, from the price to be paid in accordance with the received payment request information; a burden amount information transmitting means for transmitting the burden amount information indicating the acquired amount of the burden to a second terminal device used by the second user; a remittance request information receiving means for receiving remittance request information indicating a remittance request from the second terminal device in response to the second terminal device receiving the transmitted burden amount information accepting a remittance operation; and a remittance means for executing a process of remittance of the burden from the second user to the first user in response to the remittance request information being received by the remittance request information receiving means. and , a granting means for executing a process of granting a privilege to the first user on condition that the process of transferring the charge from the second user to the first user has been executed by the remittance means; The present invention is characterized in that it functions as a Effect of the Invention

[0046] According to the present invention, when a payment is made among a plurality of users, each user can select to transfer money after knowing the amount to be paid to the other users. [Brief description of the drawings]

[0047] [Figure 1] 1 is a diagram illustrating an example of a schematic configuration of a communication system S according to an embodiment. [Diagram 2] FIG. 1 is a block diagram showing an example of a schematic configuration of an electronic payment server 1 according to an embodiment. [Diagram 3] FIG. 2 is a diagram showing an example of information stored in a database of the electronic payment server 1. [Figure 4] 2 is a diagram showing an example of functional blocks of a system control unit 11 in the electronic payment server 1. FIG. [Diagram 5] 4 is a diagram showing an example of information transmitted from the user terminal 2 to the electronic payment server 1. FIG. [Figure 6] FIG. 13 is a diagram illustrating an example of specifying a group. [Figure 7] FIG. 13 is a diagram illustrating an example of specifying a group. [Figure 8] FIG. 2 shows an example of a payment completion screen 210. [Figure 9] FIG. 2 shows an example of a billing destination edit screen 220. [Figure 10] FIG. 2 shows an example of an amount-of-payment edit screen 230. [Figure 11] FIG. 3 shows an example of a billing screen 310. [Figure 12] 1 is a flowchart showing an example of processing in a communication system S according to an embodiment. [Figure 13] 2 is a diagram showing an example of functional blocks of a system control unit 11 in the electronic payment server 1. FIG. [Figure 14] 13A is a diagram showing an example of specifying a group, and FIG. 13B is a diagram showing an example of a payment log. [Figure 15] 1 is a diagram illustrating an example of a schematic configuration of a communication system S according to an embodiment. [Figure 16] FIG. 4 is a diagram showing an example of information stored in a database provided in the travel reservation server 3. [Figure 17] FIG. 1 is a block diagram showing an example of a schematic configuration of an electronic payment server 1 according to an embodiment. [Figure 18] 13 shows an example of information stored in the split payment reservation DB 14i. [Figure 19] 2 is a diagram showing an example of functional blocks of a system control unit 11 in the electronic payment server 1. FIG. [Figure 20] 1A is a diagram showing an example of accommodation reservation information stored in the accommodation reservation DB 3a, FIG. 1B is a diagram showing an example of transportation means reservation information stored in the transportation means ticket reservation DB 3b, and FIG. 1C is a diagram showing an example of a group's behavior during a trip. [Figure 21] FIG. 2 shows an example of a payment editing screen 240. [Figure 22] FIG. 3 shows an example of a billing screen 310. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0048] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

[0049] [1. First embodiment] [1-1. Communication system configuration] First, the configuration and functional overview of a communication system S according to the first embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of a schematic configuration of a communication system S according to this embodiment. As shown in Fig. 1, the communication system S includes an electronic payment server 1 and a plurality of user terminals 2. The electronic payment server 1 and each user terminal 2 are connected to a network NW. The network NW is constructed, for example, by the Internet, a dedicated communication line (for example, a CATV (Community Antenna Television) line), a mobile communication network (including base stations, etc.), and a gateway, etc.

[0050] The electronic payment server 1 may be a server device that executes various processes related to payment using a predetermined electronic payment application. The electronic payment application may be an application executable by each user terminal 2, and enables electronic payment of the price using the user terminal 2. In response to a payment operation using the user terminal 2, the electronic payment server 1 may receive a payment request from the user terminal 2, a POS (Point of Sales) system, or another system. The electronic payment server 1 may process the electronic payment in response to this payment request.

[0051] Examples of payment methods that can be used for electronic payments include predetermined electronic money, credit cards, etc. The service for using the predetermined electronic money may be a service provided by a company that provides electronic payment services using an electronic payment app, or an associated company of the company. For convenience, this predetermined electronic money will be referred to as R-electronic money.

[0052] The electronic payment server 1 may also execute remittance between users. For example, remittance in R electronic money may be possible using an electronic payment app.

[0053] The electronic payment server 1 may identify a group made up of a plurality of users each possessing a user terminal 2. The identified group may be, for example, a group of users who are presumed to be acting together.

[0054] When a user who has paid the bill using the electronic payment app is a member of the group described above, the electronic payment server 1 may execute a process for each of the other members to split the bill. In this embodiment, splitting the bill may mean both all members paying equally and each member paying an individual share instead of an equal share. As a result of multiple users acting together, some payment of a bill occurs. Therefore, it is assumed that the bill is shared and paid by these users. Here, it is assumed that the member of the group who has paid the bill using the electronic payment app is the representative. The electronic payment server 1 may calculate the amount of each member's share based on the paid price, for example. The electronic payment server 1 may transmit share information indicating the amount of the share to the user terminal 2 of each member other than the representative. The user terminal 2 may display this share information. The user confirms the amount of the share and performs an operation to transfer the share to the representative. In response to this operation, the electronic payment server 1 may execute a transfer process in R electronic money from the other members to the representative.

[0055] When a remittance process is performed by a member of a group, the electronic payment management server 1 may execute a process of granting a privilege to at least one of the representative and the member who made the remittance. Examples of the privilege include R electronic money (cash back), coupons, and points that can be used in a point program. The coupon may be a discount coupon, a complimentary coupon, or a free coupon. This coupon may be usable, for example, at any facility or on any website. In addition to remittances in R electronic money, each member may pay a contribution to the representative in, for example, cash. Granting a privilege in response to remittances can promote the use of R electronic money.

[0056] Each user terminal 2 may be a portable terminal device owned by a user who can use the electronic payment service described above. Examples of the user terminal 2 include a mobile information terminal such as a smartphone or a tablet computer, a mobile phone, a PDA (Personal Digital Assistant), a wearable computer, and the like. An electronic payment app may be installed in each user terminal 2. An example of payment using the electronic payment app is to display code information that encodes information identifying the user who will pay the price on the screen of the user terminal 2. Examples of code information include a one-dimensional barcode and a two-dimensional code (e.g., QR code (registered trademark)). An employee of the facility to which the price is to be paid reads the code information displayed on the screen into a POS register, for example. The POS register may transmit a payment request to the electronic payment server 1 via a POS system. Another example of payment using the electronic payment app is to read code information that encodes information about a transaction object provided by the facility as a consideration for the price into the user terminal 2. The information about the transaction object may include, for example, information identifying the facility, information identifying the transaction object, the amount of the price, and the like. This code information may be displayed on a display in the facility or printed on paper or the like. The user terminal 2 that has read the code information may transmit a payment request to the electronic payment server 1 based on an operation by the user.

[0057] Each user terminal 2 may have a function of acquiring location information of the user terminal 2. For example, the user terminal 2 may calculate longitude and latitude as location information by using a satellite positioning system such as a GPS (Global Positioning System). For example, a mobile communication carrier may provide the user terminal 2 with location information using a base station. Each user terminal 2 may be capable of wireless communication with other user terminals 2 using short-range wireless communication. Examples of standards for short-range wireless communication include Bluetooth (registered trademark) and ZigBee (registered trademark). Examples of the upper limit of the distance that can be communicated using short-range wireless communication include several meters, several tens of meters, and several tens of meters. Each user terminal 2 may periodically or constantly transmit a presence notification signal using short-range wireless communication. The presence notification signal may be a signal indicating that the user terminal 2 that transmitted the presence notification signal is nearby or that a user using the user terminal 2 is nearby. The presence notification signal may include, for example, information that identifies the user.

[0058] [1-2. Electronic payment server configuration] Next, the configuration of the electronic payment server 1 will be described with reference to Fig. 2 and Fig. 3. Fig. 2 is a block diagram showing an example of a schematic configuration of the electronic payment server 1 according to this embodiment. As shown in Fig. 2, the electronic payment server 1 includes a system control unit 11, a system bus 12, an input / output interface 13, a storage unit 14, and a communication unit 15. The system control unit 11 and the input / output interface 13 are connected via the system bus 12.

[0059] The system control unit 11 includes a central processing unit (CPU) 11a, a read only memory (ROM) 11b, a random access memory (RAM) 11c, and the like.

[0060] The input / output interface 13 performs interface processing between the storage unit 14 and the communication unit 15 and the system control unit 11 .

[0061] The storage unit 14 is composed of, for example, a hard disk drive. This storage unit 14 may store databases such as a user DB 14a, a facility DB 14b, an electronic money balance DB 14c, a payment history DB 14d, a remittance history DB 14e, a location information DB 14f, an inter-terminal communication status DB 14g, and an issued coupon DB 14h. "DB" is an abbreviation for database. At least one database may be stored in a device different from the electronic payment server 1. The electronic payment server 1 may be able to access the database via that device.

[0062] 3 is a diagram showing an example of information stored in the database of the electronic payment server 1. The user DB 14a may store user information on each user who can use the electronic payment service. For example, the electronic payment server 1 may store, as user information, a user ID, name, sex, date of birth, address, telephone number, and email address, etc., in association with one another. The user ID is identification information that identifies a user.

[0063] Facility DB14b may store facility information on each facility where a user can pay using an electronic payment app. Each facility provides a transaction object. The transaction object may be at least one of a product and a service. By visiting a facility, a user can purchase a product or service provided at the facility. Facility DB14b may store, as facility information, for example, a facility ID, category information, a facility name, an address, and facility location information in association with each other. The facility ID is identification information for identifying a facility. The category information is information indicating a category to which the facility belongs. Examples of facility categories include restaurants, coffee shops, fast food restaurants, other eating and drinking establishments, drive-ins, roadside stations, service areas, amusement parks, aquariums, museums, souvenir shops, concert venues, baseball stadiums, gas stations, rental car rental shops, convenience stores, supermarkets, department stores, other shops, accommodation facilities, train stations, airports, ticket sales offices for other transportation facilities, and the like. The facility location information may be information indicating the coordinates of a location where the facility is located. For example, facility location information may indicate the positions of each vertex constituting the outer edge of the site of the facility using longitude and latitude.

[0064] The electronic money balance DB 14c may store the balance of R electronic money of each user. For example, the electronic money balance DB 14c may store a user ID and a balance for each user in association with each other.

[0065] The payment history DB14d may store a history of payments made using an electronic payment app. For example, the payment history DB14d may store, each time a payment is made, a transaction number, a payment date and time, a user ID, payment method information, payee information, and a payment amount, etc., associated with one another as a payment log. The transaction number is identification information that identifies the payment. The payment date and time indicates the date and time when the payment was made. The user ID indicates the user who paid the payment. The payment method information is information that indicates the payment method used for the payment. The facility ID is information that indicates the payee of the payment. When the user paid the payment to a facility, the payee information may be the facility ID of the facility. The payment amount indicates the amount of the payment made.

[0066] The remittance history DB14e may store the history of remittances between users in R electronic money. For example, the remittance history DB14e may store the remittance number, remittance source user ID, remittance destination user ID, remittance amount, etc., associated with each other as a remittance log each time a remittance is made. The transaction number is identification information that identifies the settlement. The remittance number is identification information that identifies the remittance. The remittance source user ID is the user ID of the user who made the remittance. The remittance destination user ID is the user ID of the user who received the remittance. The remittance amount indicates the amount remitted.

[0067] The location information DB 14f may store location information indicating the location of each user terminal 2. Each user terminal 2 may periodically acquire location information and transmit it to the electronic payment server 1, for example, according to an electronic payment app. The electronic payment management server 1 may store the location information received from the user terminal 2 in the location information DB 14f. The location information DB 14f may store, as location information, for example, a user ID, a recording date and time, and coordinate information, etc., in association with each other. The user ID indicates the user who uses the user terminal 2 that transmitted the location information. The recording date and time indicates the date and time when the user terminal 2 recorded the location information. The coordinate information may indicate the location of the user terminal 2 at the time of the recording date and time in latitude and longitude.

[0068] The inter-terminal communication status DB 14g may store inter-terminal communication status information indicating the status of communication between each user terminal 2 and another user terminal 2 using short-distance wireless communication. Each user terminal 2 may periodically acquire inter-terminal communication status information and transmit it to the electronic payment server 1 according to, for example, an electronic payment application. For example, the user terminal 2 of each user may transmit location information and inter-terminal communication status information simultaneously. The electronic payment management server 1 may store the inter-terminal communication status information received from the user terminal 2 in the inter-terminal communication status DB 14g. The inter-terminal communication status DB 14g may store, as the inter-terminal communication status information, for example, a user ID, a recording date and time, and a signal reception source list, etc., in association with each other. The user ID indicates the user who uses the user terminal 2 that has transmitted the inter-terminal communication status information. The recording date and time indicates the date and time when the user terminal 2 recorded the inter-terminal communication status information. The signal reception source list may be a list of user IDs of users who use the user terminal 2 that has transmitted the presence notification signal that the user terminal 2 received at the recording date and time. The signal reception source list may also include the strength of the presence notification signal received by the user terminal 2 at the recorded date and time in association with each user ID. As described above, the presence notification signal includes identification information that identifies the user who uses the user terminal 2 that transmitted the presence notification signal. The user terminal 2 may generate a signal reception source list including the identification information included in each received presence notification signal and transmit the inter-terminal communication status information to the electronic payment server 1. The identification information included in the presence notification signal may be a user ID. Alternatively, this identification information may be, for example, a hash value of the user ID or other information that can identify the user. The electronic payment server 1 may convert each identification information included in the signal reception source list of the inter-terminal communication status information received from the user terminal 2 into a user ID.

[0069] The issued coupon DB 14h may store issued coupon information regarding each coupon granted to a user. By using a coupon, a user can receive a discount when purchasing a transaction object. For example, the issued coupon DB 14h may store, as issued coupon information, an issue number, a user ID, a facility ID, applicable transaction object information, discount information, and the like, in association with one another. The issue number is identification information for identifying an granted coupon. The user ID indicates the user who has acquired the coupon. The facility ID indicates the facility at which the user can use the coupon. The applicable transaction object information is set when the transaction object to which the discount by the coupon is applied is limited. The applicable transaction object information is information for identifying the transaction object to which the coupon is applied. The discount information indicates the discount amount or discount rate.

[0070] The storage unit 14 further stores various programs such as an operating system, a DBMS (Database Management System), and a server program. The server program may be a program that causes the system control unit 11 to execute processes related to electronic payment, remittance, electronic payment applications, and the like. The server program may be obtained from another device via the network NW, or may be recorded on a recording medium such as a magnetic tape, an optical disk, or a memory card and read via a drive device.

[0071] The communication unit 15 is configured by, for example, a network interface card, etc. The communication unit 15 connects to the user terminal 2 etc. via the network NW, and controls the communication state with the connected device.

[0072] [1-3. Functionality Overview] Next, a functional overview of the system control unit 11 in the electronic payment server 1 will be described with reference to Fig. 4 to Fig. 12. Fig. 4 is a diagram showing an example of a functional block of the system control unit 11 in the electronic payment server 1. As shown in Fig. 4, the system control unit 11 may function as a positional relationship information acquisition unit 1101, a group identification unit 1102, a payment request reception unit 1103, a payment unit 1104, a billing information transmission unit 1105, an edited billing information acquisition unit 1106, a burden amount acquisition unit 1107, a provisional burden amount information transmission unit 1108, a changed burden amount information acquisition unit 1109, a burden amount information transmission unit 1110, a remittance request reception unit 1111, a remittance unit 1112, a privilege granting unit 1113, and the like, by the CPU 11a reading and executing various program codes included in the server program.

[0073] [1-3-1. Identifying groups] The positional relationship information acquisition unit 1101 may acquire positional relationship information indicating a positional relationship between a plurality of user terminals 2. For example, the positional relationship information acquisition unit 1101 may acquire positional relationship information indicating a positional relationship between any one of the user terminals 2-1 and at least one user terminal 2 different from the user terminal 2-1 among the user terminals 2 in which the electronic payment application is installed. A user who uses the user terminal 2-1 is referred to as a first user. The positional relationship information may include at least the positional information of the user terminal 2-1. The positional relationship information may also include the positional information of each of the plurality of user terminals 2. Based on the positional information, the distance between the user terminals 2 can be specified as the positional relationship. The distance between the user terminals 2 can be calculated from the positional information of each user terminal 2. The positional relationship information may also include inter-terminal communication status information received from each user terminal 2. A user ID included in a signal receiving source list of the inter-terminal communication status information received from the user terminal 2 indicates a user who uses a user terminal 2 located within a range in which a presence notification signal reaches the user terminal 2. Whether or not a certain user terminal 2 is located within a range where a presence notification signal transmitted by another user terminal 2 can reach corresponds to the positional relationship between those user terminals 2. The signal reception source list may include the strength of the presence notification signal in addition to the user ID. The position of a certain user terminal 2 within a range where a presence notification signal transmitted by another user terminal 2 can reach with that signal strength also corresponds to the positional relationship between those user terminals 2.

[0074] Any user terminal 2 may be determined as the user terminal 2-1. For example, the positional relationship information acquisition unit 1101 may identify each user terminal 2 as the user terminal 2-1 and acquire positional relationship information indicating a positional relationship based on the user terminal 2-1. Alternatively, the positional relationship information acquisition unit 1101 may identify a user terminal 2 that has moved into any facility as the user terminal 2-1. Alternatively, the positional relationship information acquisition unit 1101 may identify a user terminal 2 that has accepted an operation for settling a fee to be paid to a facility as the user terminal 2-1.

[0075] FIG. 5 is a diagram showing an example of information transmitted from the user terminal 2 to the electronic settlement server 1. In FIG. 5, user terminals 2-1 and 2-2 are shown as the user terminals 2. The user terminal 2-1 transmits a presence notification signal R1 including the identification information of the user terminal 2-1. The user terminal 2-2 transmits a presence notification signal R2 including the identification information of the user terminal 2-2. The user terminal 2-1 receives the presence notification signal R2. Then, the user terminal 2 transmits, for example, the position information of the user terminal 2-1 and the terminal-to-terminal communication status information including the identification information of the user terminal 2-2 to the electronic settlement server 1. The user terminal 2-2 receives the presence notification signal R1. Then, the user terminal 2 also transmits, to the electronic settlement server 1, the terminal-to-terminal communication status information including the identification information of the user terminal 2-1 together with the position information of the user terminal 2-2. In this way, the positional relationship information acquisition unit 1101 acquires the positional information and the terminal-to-terminal communication status information from each user terminal 2. Alternatively, the positional relationship information acquiring unit 1101 may acquire the positional information and the inter-terminal communication status information received from the user terminal 2 and stored in the positional information DB 14f and the inter-terminal communication status DB 14g, respectively, from these databases.

[0076] The group identification unit 1102 may identify a group of users. The identified group may be a group of users who act together or a group of users who use a facility together. For example, the group identification unit 1102 may enable a user to set a group, as disclosed in Patent Document 1. For example, a user may set a group by inputting information identifying each member of the group (e.g., name and address, telephone number, or email address). However, a user does not necessarily use a facility with the same members every time. Therefore, the user needs to set a group every time a group activity or every time a facility is used. It may be desirable to identify a group of users who use a facility together while reducing the user's workload.

[0077] Therefore, the group identification unit 1102 may identify a second user who belongs to the same group as the first user, based on the positional relationship information acquired by the positional relationship information acquisition unit 1101. The user terminal 2 used by the second user is referred to as a user terminal 2-2. The group identification unit 1102 may identify, as the second user, a user who uses a user terminal 2 whose positional relationship when the user terminal 2-1 is located in a facility is indicated by the positional relationship information as a predetermined positional relationship, among at least one user terminal 2 other than the user terminal 2-1, for example. One second user or multiple second users may be identified.

[0078] The predetermined positional relationship may be, for example, a positional relationship between the user terminals 2 held by a first user and a second user observed when the first user and the second user are acting as a group, when the users are acting together, or when the users are using a facility together. For example, if the users are in locations where they can hear each other's voices or where they can see each other, there is a possibility that the users are acting as a group. The following are specific examples of the predetermined positional relationship.

[0079] Positional relationship a: The distance between the user terminals 2 is less than a predetermined distance. Positional relationship b: The signal strength of the presence notification signal transmitted by one of the user terminals 2 at the location where the other of the user terminals 2 is located is higher than a predetermined threshold. Location relationship c: The user terminals 2 are located within the same facility.

[0080] The predetermined positional relationship may be, for example, a specific one of the positional relationships a, b, and c. Alternatively, the predetermined positional relationship may be a combination of all of the positional relationships a, b, and c, or a combination of two specific positional relationships among these positional relationships.

[0081] The positional relationship a indicates that the users are close to each other. Users in a group tend to act in close proximity to each other. Also, when users in a group talk to each other directly, they need to be close to each other to some extent.

[0082] The signal strength in the positional relationship b is the reception strength of the presence notification signal transmitted by one of the user terminals 2 by the other user terminal 2. The positional relationship b may also indicate that the users are close to each other. The positional relationship b may also indicate that there is a high possibility that there is no obstacle between the users. Users in a group tend to behave in the same area (e.g., a facility, a room, etc.). If there is an obstacle such as a wall between the users, the presence notification signal transmitted from the user terminal 2 may not reach the other user terminal 2, or the reception strength may be low. Here, in the positional relationship b when the threshold is set to zero, the user terminals 2 are located in such a place that the presence notification signal transmitted by the user terminal 2 reaches the other user terminal 2. Whether or not the presence notification signal has been received can be determined by whether or not the user ID is included in the signal receiving source list. Assume that there are a first user terminal 2 and a second user terminal 2 as the user terminals 2. There may be cases where the signal strength when the second user terminal 2 receives the presence notification signal transmitted by the first user terminal 2 differs from the signal strength when the first user terminal 2 receives the presence notification signal transmitted by the second user terminal 2. In this case, the group identifying unit 1102 may determine, for example, whether or not the average value of the signal strengths is higher than a threshold value. Alternatively, the group identifying unit 1102 may determine whether or not one of the signal strengths is higher than a threshold value. Alternatively, the group identifying unit 1102 may determine whether or not both signal strengths are higher than a threshold value.

[0083] The positional relationship c indicates that the users may be using the same facility. For example, based on the positional information of the user terminal 2 and the facility positional information stored in the facility DB 14b, it is possible to determine whether the user terminal 2 is located within a facility and in which facility the user terminal 2 is located.

[0084] When the predetermined positional relationship includes at least one of the positional relationships a and b, the group identification unit 1102 may identify users who use user terminals 2 within a predetermined distance or whose signal strength is greater than a threshold value, as users who belong to the same group as the first user, with the user terminal 2 of a specific user as a reference. For example, the specific user may be a user who pays for a purchase using an electronic payment app. Alternatively, the group identification unit 1102 may identify the positional relationships between the user terminals 2 of each user as the first user, and identify users who belong to the same group by comprehensively considering these positional relationships. Alternatively, the group identification unit 1102 may use clustering to identify a group of users who are close to each other or a group of users whose reception strength of the presence notification signal is high.

[0085] FIG. 6 is a diagram showing an example of group identification. For example, it is assumed that the users of the user terminals 2 in the positional relationship a and the positional relationship b belong to the same group. In FIG. 6, users U1 to U5 are shown. Each user has a user terminal 2. Of the users U1 to U5, for example, it is assumed that the user U1 is the first user. The user U1 is currently in the restaurant 110. The users U2 to U5 are users located at a distance from the user U1 that is less than a predetermined distance. Therefore, the user U1 and each of the users U2 to U5 are in the positional relationship a. The users U2 and U3 are in the restaurant 110. The presence notification signals R2 and R3 transmitted by the user terminal 2 owned by the user U2 and the user terminal 2 owned by the user U3, respectively, have arrived at the user terminal 2 owned by the user U1. Therefore, the user U1 and each of the users U2 and U3 are in the positional relationship b. Therefore, the group identification unit 1102 may determine that the users U1 to U3 belong to the same group. User U4 is outside the restaurant 110. A presence notification signal R4 transmitted from a user terminal 2 carried by user U4 is blocked by the outer wall of the restaurant 110 and does not reach user U1. User U5 is inside the restaurant 110. However, a presence notification signal R5 transmitted from a user terminal 2 carried by user U5 is blocked by an inner wall 111 of the restaurant 110 and does not reach user U1. Therefore, the group identification unit 1102 may determine that neither user U4 nor U5 belongs to the same group as the group to which user U1 belongs.

[0086] The group identification unit 1102 may identify a second user belonging to the same group as the first user, on the condition that the location information of the user terminal 2-1 indicates that the user terminal 2-1 has been located at the facility for a predetermined time or more. In order for a user to use a facility, the user may need to stay at the facility for a certain amount of time or more. The group identification unit 1102 may determine whether the first user is using the facility based on time. When it is estimated that the first user is using the facility, and the location relationship between the user terminal 2-1 and the user terminal 2-2 is such that the first user and the second user are estimated to be acting together, it is estimated that the users are using the facility together. The time required to use the facility may be common to all facilities, or may be determined for each category of facility. For example, it may be determined that 30 minutes or more is required to use a restaurant, while 5 minutes or more is required to use a supermarket. For a category of facilities that can be used in a fairly short time, such a time limit may not be set.

[0087] Since each user may move at any time, the positional relationship of the user terminals 2 may also change over time. Therefore, even between users who belong to the same group, there may be a time when the positional relationship of their user terminals 2 is not a predetermined positional relationship. Conversely, even between users who do not belong to the same group, there may be a time when the positional relationship of their user terminals 2 is a predetermined positional relationship. Therefore, the positional relationship information acquisition unit 1101 may determine that those users whose user terminals 2 have a predetermined positional relationship for a time period equal to or greater than a predetermined percentage of a unit time are users who belong to the same group.

[0088] The group identification unit 1102 may identify a second user belonging to the same group as the first user from among users who use a user terminal 2 that has a predetermined positional relationship with the user terminal 2-1 when the user terminal 2-1 is located outside the facility, among at least one user terminal 2 different from the user terminal 2-1. The predetermined positional relationship in this case may be, for example, a positional relationship between the user terminals 2 owned by the first user and the second user observed when the first user and the second user are acting as a group or when the users are acting together. The predetermined positional relationship in this case may exclude the positional relationship c. When the group to which the first user belongs uses a facility, a user not belonging to the group may also use the facility. In this case, even if the user does not belong to the group, there may be a user whose positional relationship with the first user is a predetermined positional relationship. When outside the facility, the user moves for a relatively long time compared to when inside the facility. Therefore, when outside the facility, the positional relationship between a user belonging to a certain group and a user not belonging to the group does not become a predetermined positional relationship, or the time during which the positional relationship does not become a predetermined positional relationship is long. By determining the positional relationship outside the facility, it is possible to exclude users who are unlikely to belong to the group. The positional relationship information acquisition unit 1101 may use the positional relationship before the first user moves into the facility. In this case, it may be predetermined how many hours before the first user moves into the facility to specify the positional relationship. Alternatively, the positional relationship information acquisition unit 1101 may use the positional relationship after the first user moves outside the facility. In this case, it may be predetermined how many hours after the first user moves outside the facility to specify the positional relationship. Alternatively, it may specify the positional relationship before and after the first user moves into the facility. The positional relationship information acquisition unit 1101 may specify users who belong to the same group from among those users whose user terminals 2 have a predetermined positional relationship for a predetermined percentage of the unit time or more even when the users are outside the facility.

[0089] FIG. 7 is a diagram showing an example of group identification. It is assumed that users of user terminals 2 in positional relationship a and positional relationship b belong to the same group. In FIG. 7, users U1 to U4 are shown. Each user has a user terminal 2. For example, assume that user U1 is the first user. As shown in FIG. 7(a), users U1 to U4 are outdoors. Users U1 and U2 are moving close to each other. The presence notification signal R2 transmitted by the user terminal 2 possessed by user U2 reaches the user terminal 2 possessed by user U1. Users U3 and U4 are moving at a location considerably distant from user U1. In addition, the presence notification signals R3 and R4 transmitted by the user terminal 2 possessed by user U3 and the user terminal 2 possessed by user U4, respectively, do not reach the user terminal 2 possessed by user U1.

[0090] After that, as shown in FIG. 7(b), the users U1 to U4 visit the restaurant 120 at the same time. The distance between the user U1 and each of the users U2 to U4 is less than a predetermined distance. In addition, the presence notification signals R2, R3, and R4 transmitted by the user terminals 2 of the users U2, U3, and U4, respectively, arrive at the user terminal 2 carried by the user U1. When determining based only on the positional relationship within the restaurant 120, the users U1 to U4 are determined to belong to the same group. However, outdoors, the positional relationship between the user U1 and the user U2 is a predetermined positional relationship, whereas the positional relationship between the user U1 and each of the users U3 and U4 is not a predetermined positional relationship. Therefore, the group identification unit 1102 may determine that the users U1 and U2 belong to the same group, and determine that the users U3 and U4 do not belong to the same group as the user U1.

[0091] As described later, when a payment process is performed in response to a first user belonging to a group performing an operation on the user terminal 2 to settle the fee to be paid to a facility, the electronic payment server 1 executes a process for other members of the group to transfer money to the first user. The group identification unit 1102 may identify the group before the payment is made, or may identify the group at the timing of the payment.

[0092] [1-3-2. Payment] The payment request receiving unit 1103 may receive a payment request indicating a request for payment using the user terminal 2-1 used by any first user belonging to the user group. This payment may be a payment for a price to be paid by the first user. The user group may be a group already identified by the group identifying unit 1102 or a group to be identified.

[0093] The payment request may include, for example, the user ID of the first user paying the price, the facility ID of the facility to which the payment is made, payment method information, the payment amount, etc. The payment request receiving unit 1103 may receive the payment request from, for example, the user terminal 2-1, or may receive the payment request from a system such as a POS system.

[0094] The settlement unit 1104 settles the price in response to the receipt of the settlement request by the settlement request receiving unit 1103. For example, when the payment method is R electronic money, the settlement unit 1104 may execute a process of subtracting the payment amount from the balance of the first user stored in the electronic money balance DB 14c based on the user ID and the payment amount included in the settlement request. The settlement unit 1104 may also execute a process of adding the payment amount to the amount of sales in R electronic money at the facility of the payment destination. When the payment method is a credit card, the settlement unit 1104 may acquire card information of the first user. The card information may include, for example, a card number, an expiration date, and a cardholder's name. For example, the memory unit 14 may store information on cards registered in an electronic payment app for each user. The settlement unit 1104 may execute a process of settling the price using the card information. The payment method may be a known payment method using a credit card.

[0095] When the payment is completed, the payment unit 1104 may store a payment log in the payment history DB 14d. At this time, the payment unit 1104 may generate a new transaction number. The payment unit 1104 may generate a payment log based on the generated new transaction number and the user ID, payment method information, facility ID, and payment amount included in the payment request.

[0096] [1-3-3. Transferring money to split the bill] When the payment is completed, the payment unit 1104 may display a payment completion screen on the user terminal 2-1 to indicate that the payment is completed. The payment completion screen may be a screen on which, for example, a user can select whether or not to split a portion of the payment with other members. The payment unit 1104 may transmit a web page corresponding to the payment completion screen to the user terminal 2-1.

[0097] Fig. 8 is a diagram showing an example of a payment completion screen 210. As shown in Fig. 8, the payment completion screen 210 may include, for example, a split-the-bill message 211, an approval button 212, and a denial button 213. The completion message 211 is a message inquiring whether or not to split the bill. The approval button 212 is a button that can be operated to approve splitting the bill. The denial button 213 is a button that can be operated to deny splitting the bill.

[0098] The billing information transmitting unit 1105 may transmit provisional billing information indicating the second user identified by the group identifying unit 1102 to the user terminal 2-1. The provisional billing information may indicate the second user as a user to whom the charge is to be billed. For example, the provisional billing information may include the user ID and name of the second user. The billing information transmitting unit 1105 may transmit the provisional billing information only when, for example, the approval button 212 on the payment completion screen 210 is operated by the first user.

[0099] The billing information transmission unit 1105 may cause the user terminal 2-1 to display a billing edit screen for the first user to confirm and edit the users to whom the charges indicated by the provisional billing information are to be billed. Editing the billing users may include at least one of adding and deleting the billing users. The billing information transmission unit 1105 may transmit, for example, a web page equivalent to the billing edit screen to the user terminal 2-1. This web page may include the provisional billing information.

[0100] FIG. 9 is a diagram showing an example of the billing destination editing screen 220. As shown in FIG. 9, the billing destination editing screen 220 may include one or more billing destination information 221, an add button 222, and a next button 223. In each billing destination information 221, the name of the second user identified by the group identification unit 1102 is displayed. Each billing destination information 221 may include a delete button 224. The delete button 224 is a button that can be operated to delete the second user indicated by the billing destination information 221 from the billing destination users. When the delete button 224 is operated, the billing destination information 221 including the delete button 224 is deleted from the billing destination editing screen. The add button 222 is a button that can be operated to add a billing destination user. When the add button 222 is operated, the user terminal 2-1 may display, for example, a billing destination addition screen. The billing destination addition screen may include, for example, an input field for a phone number or an email. When the first user inputs a telephone number or an e-mail, the billing information transmission unit 1105 may search for user information including the input telephone number or e-mail from the user terminal DB14a. The billing information transmission unit 1105 may transmit the user ID and name included in the searched user information to the user terminal 2-1. The user terminal 2-1 may display the name transmitted from the electronic settlement server 1 on the billing addition screen. When the first user performs an operation to add the user indicated by the displayed name as a billing destination, the user terminal 2-1 may erase the billing addition screen and redisplay the billing edit screen 220, and add the billing information 221 corresponding to the added user to the billing edit screen 220. The next button 223 is a button that can be operated to provisionally confirm the user indicated by the billing information 221 currently displayed on the billing edit screen 220 as the billing destination user.

[0101] The edited billing information acquisition unit 1106 may acquire edited billing information indicating the edited billing user in response to the user terminal 2-1 accepting an operation to edit the user to which the charge is to be billed, which is indicated by the provisional billing information transmitted by the billing information transmission unit 1105. For example, when the first user operates the next button 223 on the billing edit screen 220, the user terminal 2-1 may transmit the edited billing information including the user ID of the user indicated by each billing information 221 displayed on the billing edit screen 220 to the electronic settlement server 1.

[0102] The burden amount acquisition unit 1107 may acquire the amount of the burden to be charged to a second user belonging to the same group as the first user as the user to whom the burden is to be charged, from the amount of the price to be paid in response to the payment request received by the payment request receiving unit 1103. The burden amount acquisition unit 1107 may acquire the burden amount for each second user identified by the group identification unit 1102. The burden amount acquisition unit 1107 may acquire the burden amount, for example, after the payment by the payment unit 1104 is completed.

[0103] When the edited billing destination information acquisition unit 1106 receives the edited billing destination information from the user terminal 2-1, the charge amount acquisition unit 1107 may acquire the charge amount after receiving the edited billing destination information. In this case, the charge amount acquisition unit 1107 may acquire the charge amount for each user of the billing destination after editing indicated by the edited billing destination information.

[0104] The burden amount acquisition unit 1107 may automatically determine the burden amount based on the amount of the settled fee. The burden amount acquisition unit 1107 may determine the burden amount of each member such that the total of the burden amounts of all members included in the group, including the first user, matches the amount of the fee. For example, the burden amount acquisition unit 1107 may calculate the burden amount per person by dividing the amount of the fee by the number of members in the group.

[0105] The provisional burden amount information sending unit 1108 may send provisional burden amount information indicating the burden amount acquired by the burden amount acquiring unit 1107 to the user terminal 2-1. The provisional burden amount information may include the user ID, name, and burden amount of each user identified by the group identifying unit or indicated by the edited billing destination information.

[0106] The provisional sharing amount information transmission unit 1108 may display a sharing amount editing screen on the user terminal 2-1 for the first user to confirm and change the sharing amount of each user. The provisional sharing amount information transmission unit 1108 may transmit, for example, a web page equivalent to the sharing amount editing screen to the user terminal 2-1. This web page may include provisional sharing amount information.

[0107] FIG. 10 is a diagram showing an example of the burden amount editing screen 230. As shown in FIG. 10, the burden amount editing screen 230 may include one or more burden user information 231, a back button 235, and a confirmation button 236. The burden user information 231 is information on a user who bears at least a part of the settled price. The burden amount editing screen 230 may display the burden user information 231 corresponding to each second user and may include the burden user information 231 corresponding to the first user. Each burden user information 231 may include the name of the user. In addition, each burden user information 231 may include an amount input field 232, an increase button 233, and a decrease button 234. The amount input field 232 displays the burden amount acquired by the burden amount acquisition unit 1107. The first user may be able to change the burden amount by operating the burden amount acquisition unit 1107. The increase button 233 is a button for increasing the burden amount displayed in the amount input field 232 by a predetermined amount. The reduction button 234 is a button for reducing the amount of payment displayed in the amount input field 232 by a predetermined amount. The back button 235 is a button for redisplaying the billing destination editing screen 220. The confirmation button 236 is a button for provisionally confirming the amount of payment currently displayed in each amount input field 232 as the final amount of payment. The confirmation button 236 may be enabled only when the total amount of payment of all users matches the amount of the settled price. When the confirmation button 236 is operated, the user terminal 2-1 may display a billing confirmation screen. The name and amount of payment of each user may be displayed on the billing confirmation screen. On the billing confirmation screen, the first user can perform an operation to confirm the billing destination user and the amount of payment of each user.

[0108] The changed burden amount information acquisition unit 1109 may acquire changed burden amount information indicating the changed burden amount in response to the user terminal 2-1 accepting an operation to change the burden amount indicated by the provisional burden amount information transmitted by the provisional burden amount information transmission unit 1108. For example, when a confirmation operation is performed on the billing confirmation screen, the user terminal 2-1 may transmit the changed burden amount information to the electronic payment server 1. The changed burden amount information may include, for example, the user ID and changed user ID of the first user, and the user ID and changed burden amount of each user to whom the burden amount is to be billed.

[0109] The burden amount information transmitting unit 1110 may transmit the burden amount information indicating the burden amount acquired by the burden amount acquiring unit 1107 to the user terminal 2-2 used by the second user. When the changed burden amount information is acquired by the changed burden amount information acquiring unit 1109, the burden amount information transmitting unit 1110 may transmit the changed burden amount information as the burden amount information. Also, when the edited billing destination information acquiring unit 1106 acquires edited billing destination information, the burden amount information transmitting unit 1110 may transmit the burden amount information to the user terminal 2-2 used by the user to whom the fee indicated by the edited billing destination information is billed.

[0110] The burden amount information transmitting unit 1110 may transmit the burden amount information and cause the user terminal 2-2 to present the burden amount information. For example, the burden amount information transmitting unit 1110 may cause the user terminal 2-2 to display a billing screen for transferring the burden from the second user to the first user. The burden amount information transmitting unit 1110 may transmit a web page corresponding to the billing screen to the user terminal 2-1. This web page may include the burden amount. In addition, this web page may include the user ID of the second user as the remittance source user ID and the user ID of the first user as the remittance destination user ID.

[0111] FIG. 11 is a diagram showing an example of a billing screen 310. As shown in FIG. 11, the billing screen 310 may include payment information 311, burden amount information 312, a remittance button 313, a charge button 314, and a non-remittance button 315. The payment information 311 may include the date of payment, the name of the facility to which the settled price is to be paid, the payment amount, and the like. The burden amount information 312 indicates the amount to be borne by the user using the user terminal 2-2 displaying the billing screen. The remittance button 313 is a button for remitting the burden amount with R electronic money. When the remittance button 313 is operated, the user terminal 2-2 may display, for example, a remittance confirmation screen. The remittance confirmation screen may include the name of the second user as the remittance source user, the name of the first user as the remittance destination user, and the burden amount as the remittance amount. The second user can perform an operation to execute remittance according to the contents shown on the remittance confirmation screen. The charge button 314 is a button that can be operated to charge R electronic money. When the recharge button 314 is operated, the user terminal 2-2 may display, for example, a recharge screen. The second user can recharge R electronic money in accordance with the recharge screen. When recharging is completed, the user terminal 2-2 may redisplay the billing screen 310. The non-remittance button 315 is a button that can be operated to display a predetermined home screen of the electronic payment app without executing remittance.

[0112] The remittance request receiving unit 1111 may receive a remittance request indicating a request for remittance from the second user to the first user from the user terminal 2-2 in response to the user terminal 2-2 receiving the remittance amount information transmitted by the remittance amount information transmitting unit 1110 accepting a remittance operation. For example, when an operation to execute remittance is performed on the remittance confirmation screen, the user terminal 2-2 may transmit a remittance request to the electronic settlement server 1. The remittance request may include the second user's user ID as the remittance source user ID, the first user's user ID as the remittance destination user ID, and the remittance amount as the remittance amount.

[0113] In response to the remittance request being received by the remittance request receiving unit 1111, the remittance unit 1112 may execute a process of remitting the contribution from the second user to the first user. For example, the remittance unit 1112 may subtract the remittance amount included in the remittance request from the balance associated with the same user ID as the remittance source user ID included in the remittance request in the electronic money balance DB14c. The remittance unit 1112 may also add the remittance amount included in the remittance request to the balance associated with the same user ID as the remittance destination user ID included in the remittance request in the electronic money balance DB14c. In this way, the remittance unit 1112 may update the balances of the first user and the second user.

[0114] When the remittance is completed, the remittance unit 1112 may store the remittance log in the remittance history DB 14e. At this time, the remittance unit 1112 may generate a new remittance number. The remittance unit 1112 may generate a remittance log based on the generated remittance number, the remittance source user ID, the remittance destination user ID, and the remittance amount included in the remittance request.

[0115] The system control unit 11 may execute the process for transferring money from the second user to the first user on an even split basis only when a payment request for paying a price to a facility is transmitted when the user terminal 2-1 is located at the facility. Alternatively, the system control unit 11 may execute the process for transferring money from the second user to the first user on an even split basis only when a payment request for paying a price to a facility is transmitted when the user terminal 2-1 is located within a predetermined distance from the facility. Alternatively, the system control unit 11 may execute the process for transferring money from the second user to the first user on an even split basis even if the first user moves after a payment request for paying a price to a facility is transmitted.

[0116] [1-3-4. Granting of Benefits] The reward giving unit 1113 may execute a process of giving a reward to at least one of the first user and the second user in response to the remittance process being executed by the remittance unit 1112. The reward giving unit 1113 may give a reward to only one of the first user and the second user who remitted the reward, or may give a reward to both of them.

[0117] The reward granting unit 1113 may grant to the second user a reward that can be used at a facility that is different from the facility of the payment destination using the electronic payment app and is located within a predetermined range from the payment destination facility. Alternatively, the reward granting unit 1113 may grant this reward to the first user. An example of a reward that can be used at a facility is a coupon. Examples of facilities that are located within a predetermined range from the payment destination facility include a facility that is within a predetermined straight line distance from the payment destination facility, a facility that is within a predetermined travel distance along a route from the payment destination facility, a facility that is within a predetermined travel time from the payment destination facility, and a facility that is in the same area as the payment destination facility. Examples of areas include a city, ward, town, town, block, and city block. The group is at or near the payment destination facility. By granting a reward, it is possible to encourage the user or group to whom the reward is granted to use another facility near the location of the group.

[0118] The reward granting unit 1113 may grant a reward to the second user that can be used at the same facility as the facility to which the payment was made using the electronic payment app. Alternatively, the reward granting unit 1113 may grant this reward to the first user. This can encourage the user or group to which the reward was granted to reuse the facility.

[0119] The bonus granting unit 1113 may grant a coupon that can be used only at a predetermined facility. The bonus granting unit 1113 may also grant a coupon that can be used only for the purchase of a predetermined product or transaction object.

[0120] When granting a privilege to the second user, the privilege granting unit 1113 may grant a privilege of a value according to the burden amount acquired by the burden amount acquisition unit 1107 or the burden amount acquired by the changed burden amount information acquisition unit 1109. The privilege granting unit 1113 may increase the value of the privilege as the burden amount increases. In this way, the second user can be motivated to pay the burden amount to the first user by remittance as the burden amount presented to the second user increases. The value of the privilege may be, for example, a predetermined percentage of the burden amount. When granting R electronic money, the privilege granting unit 1113 may increase the amount to be granted as the burden amount increases. When granting a coupon, the privilege granting unit 1113 may increase the discount amount or discount rate of the granted coupon as the burden amount increases. Alternatively, the value of the privilege may be fixed.

[0121] The reward giving unit 1113 may randomly determine whether to give a reward to the second user after the remittance is completed. For example, the reward giving unit 1113 may display a video of a lottery on the user terminal 2-2, and may give a reward if the second user wins the lottery.

[0122] The privilege granting unit 1113 may grant a privilege to the first user each time any second user included in the group remits the contribution. Alternatively, the privilege granting unit 1113 may grant a privilege to the first user only once any second user included in the group remits the contribution. Alternatively, the privilege granting unit 1113 may grant a privilege to the first user only when all second users included in the group remit the contribution.

[0123] When granting a privilege to the first user, the privilege granting unit 1113 may grant a privilege of a value corresponding to the amount of the price minus the amount borne by the second user. That is, the privilege granting unit 1113 may grant a privilege of a value corresponding to the amount borne by the first user out of the amount of the settled price. The value of the privilege may be, for example, a predetermined percentage of the amount borne by the first user, may correspond to an amount calculated by dividing the amount borne by the first user by the number of second users in the group, or may correspond to the amount borne by the first user. When granting R electronic money, the privilege granting unit 1113 may increase the amount to be granted as the amount borne by the first user increases. When granting a coupon, the privilege granting unit 1113 may increase the discount amount or discount rate of the granted coupon as the amount borne by the first user increases. Alternatively, the value of the privilege may be fixed.

[0124] [1-4. Operation of communication system] Next, the operation of the communication system S will be described with reference to Fig. 12. Fig. 12 is a flowchart showing a processing example of the communication system S in this embodiment. The example shown in Fig. 12 is a processing example in which a group is identified before a payment is made. Also, the example shown in Fig. 12 is a processing example in which R electronic money is given as a privilege to a first user, and a coupon is given as a privilege to a second user.

[0125] 12, the user terminal 2-1 periodically acquires location information and terminal-to-terminal communication status information and transmits them to the electronic payment management server 1 (step S101). The user terminal 2-2 also periodically acquires location information and terminal-to-terminal communication status information and transmits them to the electronic payment management server 1 (step S102). The location relation information acquisition unit 1101 of the electronic payment management server 1 stores the location information and terminal-to-terminal communication status information transmitted from each user terminal 2 in the location information DB 14f and the terminal-to-terminal communication status DB 14g, respectively.

[0126] The group identification unit 1102 of the electronic payment management server 1, for example, monitors the facility location information stored in the facility information and the location information stored in the location information DB 14f to determine whether any user terminal 2 is located in any facility for a predetermined time or more. Here, the group identification unit 1102 determines that the user terminal 2-1 is located in the facility for a predetermined time or more (step S103). In response to this determination, the group identification unit 1102 identifies other second users belonging to the group to which the user of the user terminal 2-1 belongs (step S104). Here, the group identification unit 1102 may identify, for example, a user who uses a user terminal 2 that has a predetermined location relationship with the user terminal 2-1 outside the facility as a candidate member of the group. For example, the group identification unit 1102 may identify a user of a user terminal 2 whose location relationship with the user terminal 2-1 is a specific location relationship among location relationships a and b, or both, for a predetermined percentage or more of a predetermined period before the user terminal 2-1 moves to the facility. The group identification unit 1102 may search for the user ID of a user who uses a user terminal 2 located within a predetermined distance from the position of the user terminal 2-1 from the position information DB 14f as the positional relationship a. The group identification unit 1102 may search for a user whose signal strength of a presence notification signal is higher than a threshold from the terminal-to-terminal communication status information transmitted from the user terminal 2-1 as the positional relationship b. When the member candidates are identified, the group identification unit 1102 may identify, as a member of the group, a user who uses a user terminal 2 whose positional relationship with the user terminal 2-1 in the facility is a predetermined positional relationship among the member candidates. For example, the group identification unit 1102 may identify a user of a user terminal 2 whose positional relationship with the user terminal 2-1 is a specific positional relationship among the positional relationships a, b, and c, a combination of two specific positional relationships among the positional relationships, or a combination of all of the positional relationships, for a predetermined percentage or more of the period during which the user terminal 2-1 is located in the facility.

[0127] Meanwhile, the user U1 using the user terminal 2-1 performs an operation to settle the amount to be paid to the facility (step S105). In response to this operation, for example, the user terminal 2-1 transmits a settlement request to the electronic settlement server 1 (step S106). The settlement unit 1104 of the electronic settlement management server 1 executes settlement processing of the amount based on the settlement request (step S107). The settlement unit 1104 also stores a settlement log in the settlement history DB 14d.

[0128] Next, the settlement unit 1104 transmits the web page of the settlement completion screen 210 to the user terminal 2-1 (step S108). At this time, when the settlement unit 1104 confirms that the payee information included in the settlement request is the facility ID of the facility where the user terminal 2-1 is located, it includes a split-the-bill message 211, an Approve button 212, and a Deny button 213 in the settlement completion screen 210. It is assumed that the user terminal 2-1 displays the settlement completion screen 210, and the user U1 operates the Approve button 212. In response to this operation, the user terminal 2-1 transmits an approval response to the electronic settlement management server 1 (step S109). The approval response indicates that the user U1 has approved the split.

[0129] The billing information transmission unit 1105 of the electronic payment management server 1 that has received the approval response transmits the web page of the billing edit screen 220 to the user terminal 2-1 (step S110). At this time, the billing information transmission unit 1105 includes the user ID and billing information 221 of each second user identified in step S104 in this web page. The user terminal 2-1 displays the billing edit screen 220, and the user U1 adds or deletes members to be billed for the contribution as necessary (step S111). When the user U1 operates the next button 223, the user terminal 2-1 transmits the edited billing information to the electronic payment management server 1 (step S112).

[0130] The burden amount acquisition unit 1107 of the electronic payment management server 1 that has received the edited billing information calculates the burden amount of each billing member (step S113). For example, the burden amount acquisition unit 1107 may count the number of user IDs included in the edited billing information as the number of members of the group. The burden amount acquisition unit 1107 may calculate the burden amount per person by dividing the payment amount included in the payment request by the number of members.

[0131] Next, the provisional burden amount information transmission unit 1108 transmits the web page of the burden amount editing screen 230 to the user terminal 2-1 (step S114). At this time, the provisional burden amount information transmission unit 1108 includes in this web page the user ID and name of each user included in the edited billing destination information, and the burden amount calculated for each user. The user terminal 2 displays the burden amount editing screen 230, and the user U1 changes the burden amount as necessary (step S115). When the user U1 performs an operation to confirm the billing details on the billing confirmation screen, the user terminal 2-1 transmits the changed burden amount information to the electronic payment management server 1 (step S116).

[0132] The burden amount information transmission unit 1110 of the electronic payment management server 1 that has received the changed burden amount information transmits a web page of a billing screen to the user terminals 2 used by each user other than the user U1 among the users indicated by the user IDs included in the changed burden amount information (step S117). The destinations of the web page include the user U2 who uses the user terminal 2-2. The burden amount information transmission unit 1110 includes the burden amount of the user U2 indicated by the changed burden amount information and the user ID of the user U1 in this web page. The user terminal 2-2 displays the billing screen 310, and the user U2 operates the remittance button 313. Then, when the user U2 performs an operation to execute the remittance on the remittance confirmation screen (step S118), the user terminal 2-2 transmits a remittance request to the electronic payment management server 1 (step S119).

[0133] The remittance unit 1112 of the electronic settlement management server 1 that has received the remittance request executes a remittance process from the user U2 to the user U1 based on the remittance request (step S120). The remittance unit 1112 also stores the remittance log in the remittance history DB 14e.

[0134] Next, the reward granting unit 1113 executes a reward granting process (step S121). For example, the reward granting unit 1113 may calculate a predetermined percentage of the amount paid by the user U2 as the discount amount of the coupon to be granted to the user U2. The reward granting unit 1113 may search the facility DB 14b for facilities located within a predetermined range from the facility to which the fee is paid. The reward granting unit 1113 may determine one of the searched facilities as a facility at which the coupon to be granted to the user U2 can be used. The reward granting unit 1113 may generate coupon information including the user ID of the user U2, the facility ID of the determined facility, and discount information indicating the calculated discount amount. The reward granting unit 1113 may store this coupon information in the issued coupon DB 14h. In addition, the reward granting unit 1113 may calculate the predetermined percentage of the amount paid by the user U1 as the discount amount of the coupon to be granted to the user U2. 1 The bonus giving unit 1113 may calculate the bonus amount as the amount of electronic money to be given to the user U1. The bonus giving unit 1113 may add the calculated amount to the balance stored in the electronic money balance DB14c in association with the user U1.

[0135] When the reward granting process is completed, the reward granting unit 1113 transmits a web page of a remittance completion notification and reward grant notification screen to the user terminal 2-2 (step S122). The remittance completion notification and reward grant notification screen displays a message indicating that the remittance has been completed. The remittance completion notification and reward grant notification screen also displays a message indicating that a coupon has been granted to the user U2, and the name of the facility where the coupon can be used and the discount amount. The reward granting unit 1113 also transmits a web page of a deposit notification and reward grant notification screen to the user terminal 2-1 (step S123). The deposit notification and reward grant notification screen displays a message indicating that a deposit has been made to the user U1. The deposit notification and reward grant notification screen also displays a message indicating that a cashback has been made to the user U1 in the form of R electronic money, and the amount of the cashback.

[0136] As described above, according to this embodiment, the electronic payment server 1 may receive a payment request using the user terminal 2-1. The electronic payment server 1 may also obtain the amount of the contribution to be charged to the second user belonging to the group from the amount to be paid in response to the payment request. The electronic payment server 1 may also transmit the contribution amount information indicating the amount of the contribution to the user terminal 2-2. The electronic payment server 1 may also receive a remittance request from the user terminal 2-2 in response to the user terminal 2-2 receiving the contribution amount information accepting a remittance operation. The electronic payment server 1 may also execute a process of remittance of the contribution from the second user to the first user in response to receiving the remittance request. In this case, the payment is settled using the user terminal 2-1. As a result, the first user pays the payment on behalf of the first user. After that, the contribution amount information indicating the amount of the amount to be paid by the second user belonging to the group is transmitted to the user terminal 2-2 used by the second user. Therefore, the second user can know the contribution amount. Then, the second user operates the user terminal 2-2, whereby the charge is transferred from the second user to the first user. Therefore, when multiple users are paying for something, the users can select to transfer money after knowing the amount to be paid to the other users.

[0137] Here, the electronic payment server 1 may obtain positional relationship information indicating a positional relationship between the user terminal 2-1 and at least one user terminal 2 different from the user terminal 2-1. The electronic payment server 1 may also identify a user who uses a user terminal 2 whose positional relationship when the user terminal 2-1 is located at a facility is indicated to be a predetermined positional relationship by the positional relationship information as a second user belonging to the group. In this case, positional relationship information indicating a positional relationship between the user terminal 2-1 and the other user terminal 2 is obtained. The positional relationship between the user terminals 2 may be a positional relationship between the users who use those user terminals 2. Then, a user who has a predetermined positional relationship with the first user when the first user is in the facility to which the payment is to be made is identified as a second user who belongs to the same group as the first user. Since the first user and the second user who have a predetermined positional relationship may use the facility together, it may be appropriate for the second user to bear at least a part of the fee paid by the first user. Therefore, even if the user does not perform the work of setting up a group, it is possible to identify a user who belongs to a group who has used the facility.

[0138] Here, the electronic payment server 1 may identify the second user on the condition that the location information indicates that the user terminal 2-1 has been located at the facility for a predetermined time or more. In this case, if the first user has been at the facility for a predetermined time or more, the second user who belongs to the same group as the first user is identified. In order for a user to use a facility, the user may need to be at the facility for a certain amount of time. Therefore, it is possible to identify a situation in which the first user is likely to be using the facility, and to identify a second user who is likely to be using the facility together with the first user.

[0139] The electronic payment server 1 may also identify the second user from among users who use a user terminal 2 that has a predetermined positional relationship with the user terminal 2-1 when the user terminal 2-1 is located outside the facility. In this case, even if the first user has a predetermined positional relationship when inside the facility, a user who does not have a predetermined positional relationship when the first user is outside the facility may not be identified as a second user belonging to the same group as the first user. Therefore, a user who happens to be present with the first user at the facility but does not act together with the first user outside the facility can be excluded from the second users belonging to the same group as the first user.

[0140] Furthermore, the electronic payment server 1 may specify the positional relationship between the user terminal 2-1 and at least one of the user terminals 2 based on the inter-terminal communication status information. In this case, the positional relationship between the user terminals 2 is specified based on the status of wireless communication between those user terminals 2. For example, the status of reception by the other user terminal 2 of a presence notification signal wirelessly transmitted from any one of the user terminals 2 may be affected by the positional relationship between those user terminals 2. Therefore, the positional relationship between the users can be appropriately specified.

[0141] Here, the electronic payment server 1 may identify the second user from among the users using the user terminal 2 that transmitted the presence notification signal that reached the user terminal 2-1. In this case, each user terminal 2 transmits a presence notification signal wirelessly. Among those user terminals 2, the second user who belongs to the same group as the first user is identified from among the users using the user terminal 2 whose transmitted presence notification signal reached the user terminal 2-1. The positional relationship between the users within the range reached by the presence notification signal is likely to be such that those users can easily act as a group. Therefore, the second user who uses the facility together with the first user can be appropriately identified.

[0142] The electronic payment server 1 may also transmit billing information indicating the identified second user to the user terminal 2-1. The electronic payment server 1 may also acquire edited billing information indicating the edited second user in response to the user terminal 2-1 accepting an operation to edit the second user indicated by the billing information. In this case, the first user can edit the user identified as the second user who belongs to the same group as the first user.

[0143] The predetermined positional relationship may be the positional relationship between the user terminal 2-1 and the user terminal 2-2 that can be seen when a first user and a second user are using a facility as a group.

[0144] Furthermore, the electronic payment server 1 may grant a privilege to at least one of the first user and the second user in response to the execution of the remittance process. In this case, when the second user remits the charge to the first user, the privilege is granted to at least one of the first user and the second user. This makes it possible to encourage the users to remit money to split the bill.

[0145] Here, the electronic payment server 1 may provide the second user with a reward of a value according to the amount borne by the second user. In this case, the higher the amount borne by the second user, the more the second user is encouraged to remit money.

[0146] The electronic payment server 1 may also grant the second user a benefit that can be used at a second facility that is different from the first facility to which the payment is made and that is located within a predetermined range from the first facility. In this case, a benefit that can be used at the second facility that is located within a predetermined range from the first facility used by the group is granted. Since the group was at the second facility, it is in a location that makes it easy to travel to the second facility. This can encourage the use of the second facility.

[0147] In addition, the electronic payment server 1 may provide the second user with a benefit that can be used at the facility to which the payment is made. In this case, it is possible to encourage the group to reuse the facility that they used.

[0148] The electronic payment server 1 may also provide the first user with a benefit whose value corresponds to the amount of the payment minus the amount of the second user's contribution. In this case, the higher the amount of the first user's contribution, the more the first user can be encouraged to make a payment that allows remittance for splitting the bill.

[0149] The electronic payment server 1 may also transmit provisional burden amount information indicating the burden amount to the user terminal 2-1. The electronic payment server 1 may also obtain changed burden amount information indicating the changed burden amount in response to the user terminal 2-1 accepting an operation to change the burden amount indicated by the provisional burden amount information. The electronic payment server 1 may also transmit the changed burden amount information to the user terminal 2-2 as burden amount information. In this case, the burden amount obtained by the payment device can be changed at the discretion of the first user.

[0150] [2. Second embodiment] Next, a second embodiment will be described with reference to Figures 13 and 14. In the second embodiment, a remittance history is used to identify a group. Except for the points described below, the second embodiment may be the same as the first embodiment.

[0151] Figure 13 is a diagram showing an example of functional blocks of the system control unit 11 in the electronic payment server 1. In Figure 13, the same elements as in Figure 4 are given the same reference numerals. Figure 13 differs from Figure 4 in that a remittance history acquisition unit 1114 is added in Figure 13.

[0152] The remittance history acquisition unit 1114 may acquire a remittance history from the remittance history DB 14e. The remittance history acquisition unit 1114 may acquire a remittance history in which a user using a user terminal 2 from which at least a part of the location relationship information (e.g., location information) has been acquired by the location relationship information acquisition unit 1101 is either a remittance source or a remittance destination. For example, the remittance history acquisition unit 1114 may acquire a remittance history in which a first user is either a remittance source or a remittance destination. The remittance source and the remittance destination are identified by the remittance source user ID and the remittance destination user ID included in each remittance log.

[0153] The group identification unit 1102 may identify a second user belonging to the same group as the first user based on the remittance history acquired by the remittance history acquisition unit 1114 in addition to the positional relationship information. In this embodiment, for example, the predetermined positional relationship includes a combination of at least two positional relationships among the positional relationships a to c. For convenience, each of the at least two positional relationships is referred to as a first positional relationship and a second positional relationship. The group identification unit 1102 may identify a user who uses a user terminal 2 whose positional relationship with the user terminal 2-1 is both the first positional relationship and the second positional relationship as a second user who belongs to the same group as the first user. This point is basically the same as in the first embodiment. On the other hand, it is assumed that there is a user who uses a user terminal 2 whose positional relationship with the user terminal 2-1 is only one of the first positional relationship and the second positional relationship. In this case, the group identification unit 1102 may determine whether or not there is a fact of remittance between the user and the first user based on the remittance history. If a remittance has been made, the user may be identified as a second user who belongs to the same group as the first user.

[0154] There are cases where information that should be included in the positional relationship information cannot be obtained from some user terminals 2. For example, a general user terminal 2 can be set to enable or disable a function for acquiring positional information, or to enable or disable a function for short-distance wireless communication. When the function for acquiring positional information is disabled, the electronic payment server 1 cannot acquire positional information from the user terminal 2. Therefore, the electronic payment server 1 cannot determine that the positional relationship between the user terminal 2 and another user terminal 2 is positional relationship a or c. Also, when the function for short-distance wireless communication is disabled, the user terminal 2 does not transmit a presence notification signal, nor detect a presence notification signal transmitted from another user terminal 2. Therefore, the electronic payment server 1 cannot acquire inter-terminal communication status information from the user terminal 2. Therefore, the electronic payment server 1 cannot determine that the positional relationship between the user terminal 2 and another user terminal 2 is positional relationship b. Since one of at least two positional relationship conditions for determining that a user is a second user is always not satisfied, the user is not determined to belong to any group. However, the user satisfies the other's positional relationship condition. Therefore, the possibility remains that the user belongs to the group. A user who has sent money to the first user or who has received money from the first user is likely to be an acquaintance of the first user. If an acquaintance is close to the first user, in the same facility as the first user, or within a range where a presence notification signal can be received, the acquaintance is likely to be acting together with the first user. Therefore, the group identification unit 1102 may identify a group using a remittance history as a substitute for positional information or terminal-to-terminal communication status information.

[0155] FIG. 14(a) is a diagram showing an example of group identification. For example, users whose user terminals 2 are in the positional relationships a, b, and c belong to the same group. FIG. 14(a) shows users U1 to U4. For example, assume that user U1 is a first user. Users U1 to U4 are currently in a hotel 113. Users U2 to U4 are users who are located less than a predetermined distance away from user U1. Therefore, user U1 and each of users U2 to U4 are in the positional relationship a. Users U2 and U3 have enabled the short-distance wireless communication function of their user terminals 2. Therefore, the user terminals 2 of users U2 and U3 transmit presence notification signals R2 and R3. The presence notification signals R2 and R3 reach the user terminal 2 of user U1. Therefore, the group identification unit 1102 may determine that users U1 to U3 belong to the same group regardless of the presence or absence of a remittance log.

[0156] On the other hand, the user U4 disables the short-distance wireless communication function of the user terminal 2. Therefore, the user terminal 2 does not transmit terminal-to-terminal communication status information to the electronic settlement server 1, or transmits terminal-to-terminal communication status information that does not include identification information of either user to the electronic settlement server 1. Therefore, the group identification unit 1102 that identifies the user U4 who is located in the same facility as the user U1 and whose distance to the user U1 is within a predetermined distance, but whose signal strength of the presence notification signal is not higher than a threshold, may search for a remittance log that includes the user ID of either one of the users U1 and U4 as a remittance source user ID and the user ID of the other as a remittance destination user ID. FIG. 14(b) is a diagram showing an example of a settlement log. As shown in FIG. 14(b), the remittance history DB14e stores a remittance log that includes the user ID of the user U4 as a remittance source user ID and the user ID of the user U1 as a remittance destination user ID. Therefore, the group identification unit 1102 may determine that the users U1 to U4 are members of the same group.

[0157] As described above, according to this embodiment, a second user who belongs to the same group as a first user is identified based on the remittance history between users. A user who has remitted money to a first user is likely to be a user who acts together with the first user. Therefore, a second user who uses a facility together with the first user can be appropriately identified.

[0158] [3. Third embodiment] Next, the third embodiment will be described. In the third embodiment, the amount of each member's contribution is determined based on the age of the group members. Except for the points described below, the second embodiment may be the same as at least one of the first and second embodiments.

[0159] In this embodiment, the burden amount acquisition unit 1107 determines the burden amount of each of the first user and the second user identified by the group identification unit 1102 to be an amount according to the age of the first user and the age of the second user, respectively. Therefore, the higher the age, the higher the burden amount. For example, the burden amount may be proportional to the age. In this case, the burden amount acquisition unit 1107 may calculate the burden amount per year by dividing the amount of the paid price by the total age of all members of the group. Then, the burden amount acquisition unit 1107 may calculate the burden amount by multiplying the burden amount per year by the age of each member. Alternatively, the allocation points of the burden may be predetermined for each age. In this case, the higher the age, the higher the points. The burden amount acquisition unit 1107 may calculate the burden amount per point by dividing the amount of the paid price by the total allocated points of all members of the group. Then, the burden amount acquisition unit 1107 may calculate the burden amount by multiplying the burden amount per point by the allocated points of each member. The age of each user can be identified from the date of birth stored in the user DB 14a.

[0160] The burden amount information transmitting unit 1110 may transmit the burden amount information indicating the burden amount determined for the second user by the burden amount acquiring unit 1107 to the user terminal 2-2. When the burden amount can be changed by the first user, the changed burden amount information acquiring unit 1109 may transmit provisional burden amount information indicating the burden amount determined for the second user by the burden amount acquiring unit 1107 to the user terminal 2-1.

[0161] As described above, according to this embodiment, the older the user is, the higher the fee that the user must pay. Therefore, each user can be required to pay an amount according to his / her age.

[0162] [4. Fourth embodiment] Next, a fourth embodiment will be described. In the fourth embodiment, whether or not a benefit is given to a first user depends on whether or not a second user has experience using R electronic money. Except for the points described below, the second embodiment may be the same as at least one of the first to third embodiments.

[0163] In this embodiment, the reward granting unit 1113 may grant a reward to the first user only when the remittance of the charge from the second user to the first user is the first use of R electronic money by the second user. This can encourage the first user to make payments using an electronic payment app or split the bill. In addition, the second user who uses R electronic money for the first time is expected to continue using R electronic money in the future.

[0164] The reward granting unit 1113 may determine whether the second user has used R electronic money for the first time based on the payment history DB 14d and the remittance history DB 14e. For example, the reward granting unit 1113 may determine that the second user has used R electronic money for the first time when a payment log including the user ID of the second user is not stored in the payment history DB 14d and a remittance log including the user ID of the second user as the remitter user ID is not stored in the remittance history DB 14e, except for the remittance log of the current remittance from the second user to the first user.

[0165] As described above, according to this embodiment, when a second user who has never used R electronic money uses R electronic money for the first time to transfer money from the second user to the first user, a benefit is given to the first user. Therefore, by encouraging the first user to make a payment that allows transfer for splitting the bill, it is possible to promote the use of R electronic money.

[0166] [5. Fifth Embodiment] Next, a fifth embodiment will be described with reference to Figs. 15 to 22. In the above embodiments, the second user was charged an equal share of the cost each time the first user paid the fee. In this embodiment, the fees paid by the first user during a group trip are combined, and the second user is charged the share after the trip. The purpose of the trip is not particularly limited. Except for the points described below, the fifth embodiment may be the same as at least one of the first to fourth embodiments.

[0167] Fig. 15 is a diagram showing an example of a schematic configuration of a communication system S according to this embodiment. In Fig. 15, the same elements as those in Fig. 1 are denoted by the same reference numerals. As shown in Fig. 15, the communication system S includes an electronic payment server 1, a plurality of user terminals 2, and a travel reservation server 3.

[0168] The travel reservation server 3 may be a server device that executes each process related to the travel reservation site. The travel reservation site may be a website that allows reservations of services that can be used during a trip. Examples of such services include the provision of accommodation and transportation of people. Examples of accommodation include hotels, inns, and guesthouses. Examples of transportation for transporting people include airplanes, trains, ships, and express buses. The travel reservation server 3 may execute a process for reserving services for a trip in response to a request from the user terminal 2.

[0169] The travel reservation server 3 may include databases such as an accommodation reservation DB3a and an airline ticket reservation DB3b. The electronic payment server 1 may be able to access the databases included in the travel reservation server 3 via the network NW. Alternatively, a copy of the databases included in the travel reservation server 3 may be stored in the memory unit 14 of the electronic payment server 1. The electronic payment server 1 may then periodically update the contents of the databases to the latest contents, for example.

[0170] FIG. 16 is a diagram showing an example of information stored in a database provided in the travel reservation server 3. As shown in FIG. 16, accommodation reservation information related to reservations at accommodations may be stored in the accommodation reservation DB 3a each time a reservation is made. For example, the accommodation reservation DB 3a may store the following accommodation reservation information in association with each other: reservation number, user ID, facility ID, accommodation start date, accommodation end date, scheduled check-in time, check-out deadline, number of guests, fee, and payment method. The reservation number is a number that identifies the reservation. The user ID indicates the user who has reserved the accommodation. The facility ID indicates the reserved facility. The accommodation start date indicates the date on which check-in will take place at the accommodation. The accommodation end date indicates the date on which check-out will take place at the accommodation. The scheduled check-in time indicates the time when check-in will take place. The final check-out time indicates the time by which check-out should be performed. The number of guests indicates the number of users who plan to stay at the accommodation. The fee indicates the accommodation fee charged to the person who made the reservation for using the accommodation. The payment method indicates how the fee is to be paid. The payment method may include on-site payment and online payment. On-site payment means that the person who made the reservation pays the fee at the accommodation that they have booked. Online payment means that the fee is automatically paid based on the credit card information that the person who made the reservation has registered in advance on the travel reservation site.

[0171] The transportation reservation DB3b may store transportation reservation information related to the reservation of a transportation ticket each time a reservation is made. Examples of tickets include airline tickets, limited express train tickets and passenger tickets, express bus tickets, and ship boarding passes. The accommodation reservation DB3a may store, as accommodation reservation information, for example, a reservation number, a user ID, a transportation type, a departure point ID, an arrival point ID, a scheduled departure date and time, a scheduled arrival date and time, the number of seats, and a fare, in association with each other. The reservation number is a number that identifies a reservation. The user ID indicates a user who has reserved a transportation ticket. The transportation type indicates the type of transportation for which the ticket is reserved. The departure point ID is a facility ID of a facility that is the departure point of the transportation for which the ticket is reserved. The arrival point ID is a facility ID of a facility that is the arrival point of the transportation. Examples of facilities as departure points and arrival points include airports, stations, and ports. The scheduled departure date and time indicates the date and time when the transportation is scheduled to depart from the departure point. The estimated arrival time indicates the date and time when the transportation is scheduled to arrive at the destination. The number of seats indicates the number of reserved seats. The fare indicates the price of the reserved ticket.

[0172] Fig. 17 is a block diagram showing an example of a schematic configuration of the electronic settlement server 1 according to this embodiment. In Fig. 17, the same elements as those in Fig. 2 are given the same reference numerals. Fig. 17 differs from Fig. 2 in that a split payment reserved settlement DB 14i is added to the database stored in the storage unit 14 in Fig. 17.

[0173] Fig. 18 shows an example of information stored in the split-bill reserved payment DB 14i. As shown in Fig. 18, the split-bill reserved payment DB 14i may store reserved payment information regarding a payment that has been put on hold to split during a user's trip each time the relevant payment is made. For example, the split-bill reserved payment DB 14i may store a transaction number, a user ID, and the like, in association with each other as the reserved payment information. The transaction number indicates the payment for which splitting has been put on hold. The user ID indicates the user who paid for that payment.

[0174] Fig. 19 is a diagram showing an example of functional blocks of the system control unit 11 in the electronic payment server 1. In Fig. 19, the same elements as those in Fig. 4 are given the same reference numerals. Fig. 19 differs from Fig. 4 in that a reservation information acquisition unit 1115, a trip determination unit 1116, and a payment information transmission unit 1117 are added in Fig. 19.

[0175] The reservation information acquisition unit 1115 acquires reservation information indicating a reservation made by the first user for a service available during the trip. The acquired reservation information may be at least one of accommodation reservation information and transportation reservation information. It is possible to identify whether the reservation was made by the first user based on the user ID included in the reservation information.

[0176] The trip determination unit 1116 may determine whether or not a payment request is received by the payment request receiving unit 1103 while the first user is traveling, based on the reservation information acquired by the reservation information acquisition unit 1115. That is, the trip determination unit 1116 may determine whether or not the first user has paid for the trip during the trip. The trip determination unit 1116 may also determine whether or not the first user's trip has ended, based on the reservation information.

[0177] For example, when accommodation reservation information is used, the travel determination unit 1116 may determine that the first user is traveling at least during the period from the scheduled check-in time on the stay start date to the final check-in time on the stay end date. The travel determination unit 1116 may further use location information of the user terminal 2-1. For example, the travel determination unit 1116 may determine that the first user's trip has started when the location of the user terminal 2-1 is a predetermined distance or more away from the address of the first user on the stay start date. Furthermore, the travel determination unit 1116 may determine that the first user's trip has ended when the location of the user terminal 2-1 approaches within a predetermined distance of the address of the first user on the stay end date or after that date.

[0178] When using the transportation reservation information, the trip determination unit 1116 may determine whether the transportation for which the ticket is reserved is used for the outward journey or the return journey. For example, the trip determination unit 1116 may compare the distance from the address of the first user to the departure point of the transportation with the distance from the address to the arrival point of the transportation. The location of the facility as the departure point or the arrival point is indicated by the facility location information stored in the facility DB 14b. If the distance to the departure point is shorter, the trip determination unit 1116 may determine that the ticket is an outward ticket, and if the distance to the arrival point is shorter, the ticket may determine that the ticket is a return ticket. The trip determination unit 1116 may determine that the first user's trip starts from the scheduled departure date and time in the outward transportation reservation information. In addition, the trip determination unit 1116 may determine that the first user's trip ends at the scheduled arrival date and time in the return transportation reservation information. The trip determination unit 1116 may further use the location information of the user terminal 2-1. For example, the trip determination unit 1116 may determine that the first user's trip has started when the location of the user terminal 2-1 reaches the departure point on the scheduled departure date. Alternatively, the trip determination unit 1116 may determine that the first user's trip has started when the location of the user terminal 2-1 is a predetermined distance or more away from the address of the first user on the scheduled departure date. Furthermore, the trip determination unit 1116 may determine that the first user's trip has ended when the location of the user terminal 2-1 reaches the arrival point on the scheduled arrival date. Alternatively, the trip determination unit 1116 may determine that the first user's trip has ended when the location of the user terminal 2-1 approaches within a predetermined distance of the address of the first user on the scheduled arrival date.

[0179] The travel determination unit 1116 may make the determination using both the accommodation reservation information and the transportation reservation information.

[0180] The travel determination unit 1116 may determine whether the first user is traveling based on the location information of the user terminal 2-1 without using the reservation information. For example, the travel determination unit 1116 may determine that the first user is traveling when the location of the user terminal 2-1 is a first predetermined distance (e.g., 50 km) away from the address of the first user. The travel determination unit 1116 may then determine that the first user is traveling from the time when the location of the user terminal 2-1 is a second predetermined distance (e.g., 5 km) or more away from the address of the first user to the time when the user terminal 2-1 approaches within the second predetermined distance from the address. The second predetermined distance is shorter than the first predetermined distance.

[0181] The trip determination unit 1116 may, for example, monitor the location of the user terminal 2-1 and determine the start and end of the trip in real time or periodically. Alternatively, the trip determination unit 1116 may determine whether the first user is traveling or not based on the location history and reservation information of the user terminal 2-1 every time a payment request is received by the payment request receiving unit 1103.

[0182] The trip determination unit 1116 may store, for each payment request received during the first user's trip, the transaction number of the payment and the user ID of the first user who made the payment in the split payment reserved payment DB 14i.

[0183] FIG. 20(a) is a diagram showing an example of accommodation reservation information stored in the accommodation reservation DB3a. FIG. 20(b) is a diagram showing an example of transportation reservation information stored in the transportation ticket reservation DB3b. For example, assume that a user U1 lives in Tokyo. The user U1 plans to travel to Okinawa with users U2 and U3. Therefore, the user U1 reserves a hotel F in Okinawa on a travel reservation site. Therefore, as shown in FIG. 20(a), the accommodation reservation DB3a stores an accommodation reservation including the user ID of the user U1. The stay start date is March 2nd, and the stay end date is March 4th. In addition, the user U1 has reserved round-trip air tickets between Haneda Airport and Naha Airport for three people. Therefore, as shown in FIG. 20(b), the transportation ticket reservation DB3b stores transportation reservation information for the outbound trip and transportation reservation information for the return trip, including the user ID of the user U1. The scheduled departure date of the outbound trip is March 2nd. The scheduled arrival date of the return trip is March 4th.

[0184] FIG. 20(c) is a diagram showing an example of the behavior of a group during a trip. On March 2, users U1 to U3 arrived at Haneda Airport (step S201). The trip determination unit 1116 may determine that user U1 has started the trip from this point. The group of user U1 had breakfast at a restaurant in the airport, and user U1 paid for the meal with an electronic payment app (S202). After that, the group moved to Naha Airport by passenger plane (step S203). Then, the group checked into Hotel F (step S204). On March 3, the group rented a car at a rental shop (step S205). The group had coffee at a coffee shop along the way (step S206). That night, the group ate at an izakaya (S207). User U1 paid for each meal that day with an electronic payment app. On March 4, the group checked out of Hotel F, and user U1 paid for the accommodation fee using the electronic payment app (step S208). The group arrived at Naha Airport and purchased souvenirs at a shop in the airport. User U1 paid for the purchases using the electronic payment app again. The group then traveled to Naha Airport by passenger plane (step S210). The trip determination unit 1116 may determine that the trip ended when the first user arrived at Haneda Airport. The trip determination unit 1116 may then determine that the payments in steps S202 and S205 to S209 were made during the trip.

[0185] The group identification unit 1102 may identify second users belonging to the group by considering the reservation information acquired by the reservation information acquisition unit 1115 in addition to the positional relationship information. The accommodation reservation information includes the number of guests, and the transport reservation information includes the number of seats. The number of guests and the number of seats may correspond to the number of members of the group. Thus, the group identification unit 1102 may identify second users whose number of members of the group matches the number of guests or the number of seats.

[0186] The settlement unit 1104 may not include the "split the bill" message 211, the "Approve" button 212, and the "Reject" button 213 on the settlement completion screen 210 displayed on the user terminal 2-1 when the settlement process is performed in response to a settlement request determined by the trip determination unit 1116 to have been received during the first user's trip. Therefore, splitting is not performed at the time the price is settled. On the other hand, the settlement unit 1104 may include the "split the bill" message 211, the "Approve" button 212, and the "Reject" button 213 on the settlement completion screen 210 for a settlement request that is not determined to have been received during the first user's trip.

[0187] When there are a plurality of payment requests that are determined by the trip determination unit 1116 to have been received during the first user's trip, the payment information transmission unit 1117 may transmit a plurality of pieces of payment information indicating a plurality of payments corresponding to the plurality of payment requests to the user terminal 2-1 after the trip determination unit 1116 determines that the trip has ended. Each piece of payment information may include, for example, a transaction number, a payment date, a facility name of the payment destination, a payment amount, and the like. The payment information transmission unit 1117 may search the split pending payment DB 14i for pending payment information including the user ID of the first user whose trip has been determined to have ended by the trip determination unit 1116. The payment information transmission unit 1117 may search the payment history DB 14d for a payment log including the same transaction number as the transaction number included in the pending payment information. Then, the payment information transmission unit 1117 may generate payment information based on the payment log.

[0188] The payment information transmission unit 1117 may display a payment editing screen on the user terminal 2-1 for the first user to confirm and edit the payment to be split. The payment information transmission unit 1117 may transmit, for example, a web page equivalent to the payment editing screen to the user terminal 2-1. This web page may include payment information.

[0189] FIG. 21 is a diagram showing an example of the payment editing screen 240. As shown in FIG. 21, the payment editing screen 240 may include a plurality of payment information 241, an approval button 243, and a disapproval button 244. Each payment information 241 is information about a payment executed in response to a request from the first user. Each payment information 241 may include, for example, a payment date, a name of a payee, a payment amount, and the like. The payment information 241 may further include a delete button 242. The delete button 242 is a button that can be operated to delete the amount paid in the payment indicated by the payment information 241 from the subject of splitting. When the delete button 242 is operated, the payment information 241 including the delete button 242 is deleted from the payment editing screen 240. The approve button 243 is a button that can be operated to approve the amount paid in the payment indicated by the payment information 241 currently displayed on the payment editing screen 240 as the subject of splitting. When the approve button 243 is operated, the user terminal 2-1 may display the billing destination editing screen 220. Thereafter, in accordance with a user operation, the screen may transition sequentially to the burden amount editing screen 230 and the billing confirmation screen.

[0190] When the accommodation fee for the accommodation is paid by online payment, the accommodation fee is not included in the subject of splitting in the method described above. In addition, when the accommodation fee is paid by cash at the accommodation, the accommodation fee is not included in the subject of splitting. Furthermore, if it is assumed that the method available for paying the purchase fee of a transportation ticket is limited to online payment, the purchase fee is not included in the subject of splitting. However, the payment information transmission unit 1117 can obtain the fee from the reservation information. Therefore, the payment information transmission unit 1117 may include the fee of a service used during the trip for the trip, regardless of whether the fee for the reserved service is paid using an electronic payment app or not, and regardless of whether the payment is made during the trip or not. For example, in the example shown in FIG. 21, the purchase fee of a round-trip air ticket may also be included in the subject of splitting.

[0191] When there are a plurality of payment requests determined by the trip determination unit 1116 to have been received during the first user's trip, the burden amount acquisition unit 1107 may acquire the amount of the burden according to the total amount of the plurality of fees paid in response to the plurality of payment request information. For example, the burden amount acquisition unit 1107 may acquire the payment amount from each payment log searched by the payment information transmission unit 1117. The burden amount acquisition unit 1107 may calculate the burden amount per person by dividing the total amount of the plurality of payment amounts by the number of members of the group identified by the group identification unit 1102. Alternatively, the burden amount acquisition unit 1107 may calculate the burden amount of each member based on the total amount of the fees and the age of each member of the group. When any payment is deleted from the target of splitting on the burden amount editing screen 230, the burden amount acquisition unit 1107 may calculate the total amount of payment excluding the deleted payment. As described above, the payment acquisition unit 1107 may include the cost of services booked for the trip in the split regardless of whether the cost was paid for using an electronic payment app.

[0192] After the trip determination unit 1116 determines that the first user's trip has ended, the burden amount information transmission unit 1110 may transmit burden amount information indicating the burden amount acquired by the burden amount acquisition unit 1107 according to the total price to the user terminal 2-2. After transmitting the burden amount information, the burden amount information transmission unit 1110 may delete the pending payment information including the user ID of the first user whose trip has been determined to have ended from the split pending payment DB 14i.

[0193] Fig. 22 is a diagram showing an example of a billing screen 310. In Fig. 22, the same elements as in Fig. 11 are given the same reference numerals. As shown in Fig. 22, the billing screen 310 may include a plurality of pieces of payment information 311, payment amount information 312, a remittance button 313, a charge button 314, a non-remittance button 315, a total amount 316, etc. The total amount 316 indicates the sum of a plurality of payment amounts indicated by the plurality of pieces of payment information 311.

[0194] As described above, according to this embodiment, it is determined whether or not a payment using the user terminal 2-1 is made during the first user's trip and whether or not the first user's trip has ended, based on reservation information for a service for the trip. If a payment is made during the first user's trip, no processing for remittance based on splitting is performed at that point. After the trip ends, processing for remittance based on splitting is performed by collecting multiple payments made during the trip. Therefore, the group to which the first user belongs can split the amount paid by the first user during the trip all at once after the trip.

[0195] [6. Other embodiments] In the embodiments described so far, the group is identified by the group identifying unit 1102 based on the positional relationship information for the purpose of transferring money between members in the group to split the bill. However, the group may be identified for purposes other than splitting the bill or transferring money between members. For example, the group may be identified for sharing information between members of the group, delivering information according to common or similar attributes between members of the group, delivering information about facilities where the group is located, etc.

[0196] (Supplementary Note 1-1) A payment processing device for payment using a first terminal device used by any first user belonging to a user group, comprising: a payment request information receiving means for receiving payment request information indicating a request for payment of a fee paid by the first user; a burden amount acquiring means for acquiring an amount of a burden to be charged to a second user belonging to the group, the second user being different from the first user, from the fee to be paid in accordance with the received payment request information; a burden amount information sending means for sending the acquired amount of the burden to a second terminal device used by the second user; a remittance request information receiving means for receiving remittance request information indicating a request for remittance from the second terminal device in response to the second terminal device receiving the transmitted burden amount information accepting a remittance operation; and a remittance means for executing a process of remittance of the burden from the second user to the first user in response to the remittance request information being received by the remittance request information receiving means.

[0197] (Appendix 1-2) The payment device described in Appendix 1-1, characterized in that the amount paid in accordance with the received payment request information is an amount paid to a facility, and further comprising: a location relationship information acquisition means for acquiring location relationship information indicating a location relationship between the first terminal device and at least one terminal device different from the first terminal device, the location relationship information including first location information indicating the location of the first terminal device; and an identification means for identifying, as the second user belonging to the group, a user using a terminal device among the at least one terminal device, whose location relationship when the first terminal device is located at the facility is indicated to be a predetermined location relationship by the acquired location relationship information.

[0198] (Appendix 1-3) The payment processing device described in Appendix 1-2, characterized in that the identification means identifies the second user on the condition that the first location information indicates that the first terminal device has been located at the facility for a predetermined period of time or more.

[0199] (Appendix 1-4) The payment processing device described in Appendix 1-2 or 1-3, characterized in that the identification means identifies the second user from among users who use a terminal device among the at least one terminal device, the positional relationship between which and the first terminal device is a predetermined positional relationship when the first terminal device is located outside the facility.

[0200] (Appendix 1-5) A payment processing device described in any one of Appendices 1-2 to 1-4, characterized in that the acquired location relationship information further includes communication status information indicating the status of wireless communication between the first terminal device and each of the at least one terminal device, and the identification means identifies the location relationship between the first terminal device and each of the at least one terminal device based on the communication status information.

[0201] (Appendix 1-6) A payment processing device as described in Appendix 1-5, characterized in that each of the at least one terminal device wirelessly transmits a specified signal, the communication status information indicates the terminal device that transmitted the specified signal that reached the first terminal device, and the identification means identifies the second user from among users using the terminal device that transmitted the specified signal that reached the first terminal device.

[0202] (Appendix 1-7) A payment processing device as described in any one of Appendices 1-2 to 1-6, further comprising a remittance history information acquisition means for acquiring remittance history information indicating a remittance history capable of identifying each user of the remittance source and the remittance destination, the remittance history being either the remittance source or the remittance destination, wherein the identification means identifies the second user based on the acquired location relationship information and the acquired remittance history information.

[0203] (Appendix 1-8) The payment device described in Appendix 1-7, characterized in that the specified positional relationship includes a specified first positional relationship and a specified second positional relationship different from the first positional relationship, the identification means identifies a user using a terminal device whose positional relationship with the first terminal device is both the first positional relationship and the second positional relationship as the second user belonging to the group, and the identification means identifies a user using a terminal device whose positional relationship with the first terminal device is only one of the first positional relationship and the second positional relationship as the second user belonging to the group when there is an instance of a money transfer between the first user and the first user.

[0204] (Appendix 1-9) A payment processing device as described in any one of Appendices 1-2 to 1-8, further comprising a billing information sending means for sending billing information indicating the identified second user to the first terminal device, and an edited billing information acquisition means for acquiring edited billing information indicating the second user after editing in response to the first terminal device accepting an operation to edit the second user indicated by the transmitted billing information, wherein the charge amount acquisition means acquires the amount of the charge for the second user indicated by the acquired edited billing information, and the charge amount information sending means transmits the charge amount information to the second terminal device used by the second user indicated by the acquired edited billing information.

[0205] (Appendix 1-10) A payment processing device described in any one of Appendices 1-2 to 1-9, characterized in that the specified positional relationship is a positional relationship seen when the first user and the second user are using the facility as a group, and is a positional relationship between the first terminal device and the second terminal device.

[0206] (Appendix 1-11) A payment processing device described in any one of Appendices 1-1 to 1-10, further comprising an awarding means for executing a process of awarding a benefit to at least one of the first user and the second user in response to the remittance process being executed by the remittance means.

[0207] (Supplementary Note 1-12) The payment processing device according to Supplementary Note 1-11, characterized in that the granting means grants the benefit to the second user, the value of which corresponds to the amount of the charge.

[0208] (Appendix 1-13) The payment processing device described in Appendix 1-11 or 1-12, characterized in that the amount to be settled is the amount paid by the first user to the first facility when the first user uses any of the first facilities, and the granting means grants to the second user a benefit that can be used at a second facility that is different from the first facility and is located within a predetermined range of the first facility.

[0209] (Appendix 1-14) A payment processing device described in any one of Appendices 1-11 to 1-13, characterized in that the amount to be settled is the amount paid by the first user to a facility when the first user uses the facility, and the granting means grants a benefit that can be used at the facility to the second user.

[0210] (Appendix 1-15) A payment processing device described in any one of Appendices 1-11 to 1-14, characterized in that the granting means grants the first user the benefit of a value corresponding to the amount of the price minus the amount of the acquired charge.

[0211] (Appendix 1-16) A payment processing device described in any one of Appendices 1-11 to 1-15, characterized in that the remittance means executes the process of remitting the charge in a specified electronic money, and the granting means grants the benefit to the first user if the remittance by the remittance means is the second user's first use of the specified electronic money.

[0212] (Appendix 1-17) A payment processing device described in any one of Appendices 1-1 to 1-16, characterized in that the burden amount acquisition means determines the amount of the first user's burden and the amount of the second user's burden to amounts corresponding to the age of the first user and the age of the second user, respectively, and the burden amount information transmission means transmits the burden amount information indicating the amount of the burden determined for the second user by the burden amount acquisition means.

[0213] (Appendix 1-18) A payment processing device as described in any one of Appendices 1-1 to 1-17, further comprising a second burden amount information sending means for sending second burden amount information indicating the acquired amount of the burden to the first terminal device, and a changed burden amount information acquisition means for acquiring changed burden amount information indicating the changed amount of the burden in response to the first terminal device accepting an operation to change the amount of the burden indicated by the sent second burden amount information, wherein the burden amount information sending means transmits the acquired changed burden amount information as the burden amount information.

[0214] (Appendix 1-19) A payment processing device as described in any one of Appendices 1-1 to 1-18, further comprising a reservation information acquisition means for acquiring reservation information indicating a reservation made by the first user for services available during the trip, and a judgment means for respectively judging whether the payment request information has been received by the payment request information receiving means during the trip by the first user and whether the trip has ended based on the acquired reservation information, wherein the burden amount acquisition means, when there is a plurality of pieces of payment request information judged by the judgment means to have been received during the trip, acquires the amount of the burden corresponding to the sum of the multiple amounts of the fees to be paid in accordance with the multiple pieces of payment request information, and the burden amount information transmission means transmits the burden amount information indicating the sum of the amounts of the burden acquired by the burden amount acquisition means in accordance with the sum of the amounts of the fees after it is judged by the judgment means that the trip has ended.

[0215] (Appendix 1-20) A payment method executed by a computer, comprising: a payment using a first terminal device used by any first user belonging to a user group, the payment processing method comprising: a payment request information receiving step of receiving payment request information indicating a request for payment of a price to be paid by the first user; a burden amount acquisition step of acquiring an amount of a burden to be charged to a second user belonging to the group, the second user being different from the first user, from the price to be paid in accordance with the received payment request information; a burden amount information sending step of sending burden amount information indicating the acquired amount of the burden to a second terminal device used by the second user; a remittance request information receiving step of receiving remittance request information indicating a request for remittance from the second terminal device in response to the second terminal device receiving the transmitted burden amount information accepting a remittance operation; and a remittance step of executing a process of remittance of the burden from the second user to the first user in response to the remittance request information being received by the remittance request information receiving step.

[0216] (Appendix 1-21) A payment processing program characterized by causing a computer to function as: a payment request information receiving means for receiving payment request information indicating a request for payment of a price paid by a first user belonging to a user group, the payment request information receiving means receiving payment request information indicating a request for payment of the price paid by the first user; a burden amount acquiring means for acquiring an amount of a burden to be charged to a second user belonging to the group, the second user being different from the first user, from the price to be settled in accordance with the received payment request information; a burden amount information sending means for sending the acquired amount of the burden to a second terminal device used by the second user; a remittance request information receiving means for receiving remittance request information indicating a request for remittance from the second terminal device in response to the second terminal device receiving the transmitted burden amount information accepting a remittance operation; and a remittance means for executing a process of remittance of the burden from the second user to the first user in response to the remittance request information being received by the remittance request information receiving means.

[0217] (Supplementary Note 2-1) A group identification device comprising: a positional relationship information acquisition means for acquiring positional relationship information indicating a positional relationship between a first terminal device used by any first user belonging to a user group and at least one terminal device different from the first terminal device, the positional relationship information including first position information indicating the position of the first terminal device; and an identification means for identifying, as a second user belonging to the group, a user using a terminal device among the at least one terminal device, the positional relationship of which is indicated to be a predetermined positional relationship when the first terminal device is located in a facility by the acquired positional relationship information.

[0218] (Appendix 2-2) The group identification device described in Appendix 2-1, characterized in that the identification means identifies the second user on the condition that the first location information indicates that the first terminal device has been located in the facility for a predetermined period of time or more.

[0219] (Appendix 2-3) The group identification device described in Appendix 2-1 or 2-2, characterized in that the identification means identifies the second user from among users who use a terminal device among the at least one terminal device, the positional relationship between which and the first terminal device is a predetermined positional relationship when the first terminal device is located outside the facility.

[0220] (Appendix 2-4) A group identification device described in any one of Appendices 2-1 to 2-3, characterized in that the acquired location relationship information further includes communication status information indicating the status of wireless communication between the first terminal device and each of the at least one terminal device, and the identification means identifies the location relationship between the first terminal device and each of the at least one terminal device based on the communication status information.

[0221] (Appendix 2-5) The group identification device described in Appendix 2-4, characterized in that each of the at least one terminal device transmits a specified signal wirelessly, the communication status information indicates the terminal device that transmitted the specified signal that reached the first terminal device, and the identification means identifies the second user from among users who use the terminal device that transmitted the specified signal that reached the first terminal device.

[0222] (Appendix 2-6) A group identification device as described in any one of Appendices 2-1 to 2-5, further comprising a remittance history information acquisition means for acquiring remittance history information indicating a remittance history capable of identifying each user, the remittance source and the remittance destination, in which the first user is either the remittance source or the remittance destination, and the identification means for identifying the second user based on the acquired location relationship information and the acquired remittance history information.

[0223] (Claim 2-7) The group identification device described in Appendix 6, characterized in that the specified positional relationship includes a specified first positional relationship and a specified second positional relationship different from the first positional relationship, and the identification means identifies a user using a terminal device whose positional relationship with the first terminal device is both the first positional relationship and the second positional relationship as the second user belonging to the group, and the identification means identifies a user using a terminal device whose positional relationship with the first terminal device is only one of the first positional relationship and the second positional relationship as the second user belonging to the group when there is an instance of a money transfer between the first user and the first user.

[0224] (Appendix 2-8) A group identification device described in any one of Appendices 2-1 to 2-7, characterized in that the specified positional relationship is a positional relationship seen when the first user and the second user are using the facility as a group, and is a positional relationship between the first terminal device and a second terminal device used by the second user.

[0225] (Appendix 2-9) A group identification device as described in any one of Appendices 2-1 to 2-8, characterized in that it further comprises a payment request information receiving means for receiving payment request information indicating a request for payment of the amount to be paid by the first user, a burden amount acquisition means for acquiring the amount of a burden to be charged to the second user from the amount to be paid in accordance with the received payment request information, and a burden amount information sending means for sending burden amount information indicating the acquired amount of the burden to a second terminal device used by the second user, for payment using the first terminal device.

[0226] (Appendix 2-10) The group identification device described in Appendix 2-9, further comprising a remittance request information receiving means for receiving remittance request information indicating a remittance request from the second terminal device in response to the second terminal device receiving the transmitted burden amount information accepting a remittance operation, and a remittance means for executing a process of remittance of the burden from the second user to the first user in response to the remittance request information being received by the remittance request information receiving means.

[0227] (Appendix 2-11) A group identification device as described in Appendix 2-9 or 2-10, further comprising a billing information sending means for sending billing information indicating the identified second user to the first terminal device, and an edited billing information acquisition means for acquiring edited billing information indicating the second user after editing in response to the first terminal device accepting an operation to edit the second user indicated by the transmitted billing information, wherein the burden amount acquisition means acquires the amount of the burden for the second user indicated by the acquired edited billing information, and the burden amount information sending means transmits the burden amount information to the second terminal device used by the second user indicated by the acquired edited billing information.

[0228] (Appendix 2-12) A group identification method executed by a computer, comprising: a positional relationship information acquisition step of acquiring positional relationship information indicating a positional relationship between a first terminal device used by any first user belonging to a user group and at least one terminal device other than the first terminal device, the positional relationship information including first position information indicating a position of the first terminal device; and an identification step of identifying, as a second user belonging to the group, a user using a terminal device among the at least one terminal device, the positional relationship of which is indicated to be a predetermined positional relationship when the first terminal device is located in a facility by the acquired positional relationship information.

[0229] (Appendix 2-13) A group identification program characterized by causing a computer to function as: a positional relationship information acquisition means for acquiring positional relationship information indicating a positional relationship between a first terminal device used by any first user belonging to a user group and at least one terminal device other than the first terminal device, the positional relationship information including first position information indicating the position of the first terminal device; and an identification means for identifying, among the at least one terminal device, a user using a terminal device whose positional relationship when the first terminal device is located in a facility is indicated to be a predetermined positional relationship by the acquired positional relationship information, as a second user belonging to the group. [Explanation of symbols]

[0230] 1. Electronic payment server 2. User terminal 3. Travel booking server 11 System control section 12 System Bus 13 Input / Output Interface 14 Storage section 14a User DB 14b Facility DB 14c Electronic Money Balance DB 14d Payment history DB 14e Remittance history DB 14f Location information DB 14g Inter-terminal communication status DB 14h Issued coupon DB 14i Split payment pending settlement DB 15 Communications Department 3a Accommodation reservation database 3b Transport ticket reservation database 1101 Location information acquisition unit 1102 Group Specific Department 1103 Payment request receiving unit 1104 Payment Department 1105 Billing Information Transmission Department 1106 Editing and Request Information Acquisition Department 1107 Cost Acquisition Department 1108 Provisional Charge Information Transmission Department 1109 Change in Charge Information Acquisition Unit 1110 Charge information transmission unit 1111 Remittance request receiving unit 1112 Remittance Department 1113 Benefits Granting Department 1114 Remittance History Acquisition Department 1115 Reservation Information Acquisition Department 1116 Travel Judgment Department 1117 Payment Information Transmission Department NW Network S Communication System

Claims

1. a payment request information receiving means for receiving payment request information indicating a request for payment of a price to be paid by a first user, the payment request information indicating a request for payment of a price to be paid by the first user, the payment request information receiving means receiving payment request information indicating a request for payment of a price to be paid by the first user, the payment request information including a payment request for a payment using a first terminal device used by a first user belonging to a user group; a charge acquisition means for acquiring an amount of a charge to be charged to a second user belonging to the group and different from the first user, out of the amount of the payment to be paid in accordance with the received payment request information; a charge information transmitting means for transmitting charge information indicating the acquired charge amount to a second terminal device used by the second user; a remittance request information receiving means for receiving remittance request information indicating a remittance request from the second terminal device in response to the second terminal device receiving the transmitted burden amount information and accepting a remittance operation; a remittance means for executing a process of remittance of the charge from the second user to the first user in response to the remittance request information being received by the remittance request information receiving means; a granting means for executing a process of granting a privilege to the first user on condition that the process of transferring the charge from the second user to the first user has been executed by the transfer means; A payment processing device comprising:

2. the payment amount to be paid in response to the received payment request information is a payment amount to be paid to any one of the facilities, a positional relationship information acquiring means for acquiring positional relationship information indicating a positional relationship between the first terminal device and at least one terminal device different from the first terminal device, the positional relationship information including first position information indicating a position of the first terminal device; an identification means for identifying a user of a terminal device, among the at least one terminal device, whose positional relationship when the first terminal device is located in the facility is indicated to be a predetermined positional relationship based on the acquired positional relationship information, as the second user belonging to the group; The payment processing device of claim 1 further comprising:

3. The payment processing device according to claim 2 , wherein the identification means identifies the second user on the condition that the first location information indicates that the first terminal device has been located at the facility for a predetermined period of time or longer.

4. The payment processing device according to claim 2 or 3, characterized in that the identification means identifies the second user from among users who use a terminal device, among the at least one terminal device, whose positional relationship with the first terminal device when the first terminal device is located outside the facility is a predetermined positional relationship.

5. the acquired positional relationship information further includes communication status information indicating a status of wireless communication between the first terminal device and each of the at least one terminal devices; The payment processing device according to claim 2 , wherein the specifying means specifies the positional relationship between the first terminal device and each of the at least one terminal device based on the communication status information.

6. Each of the at least one terminal device wirelessly transmits a predetermined signal; the communication status information indicates a terminal device that has transmitted the predetermined signal that has arrived at the first terminal device, 6. The payment processing device according to claim 5, wherein the identification means identifies the second user from among users who use the terminal device that transmitted the predetermined signal that reached the first terminal device.

7. The method further includes a remittance history information acquisition means for acquiring remittance history information indicating a remittance history in which a remittance source user and a remittance destination user can be identified, the remittance history information indicating a remittance history in which the first user is either the remittance source or the remittance destination user, The payment processing device according to claim 2 or 5, wherein the identification means identifies the second user based on the acquired location relationship information and the acquired remittance history information.

8. the predetermined positional relationship includes a predetermined first positional relationship and a predetermined second positional relationship different from the first positional relationship, the identification means identifies a user who uses a terminal device whose positional relationship with the first terminal device is the first positional relationship and also the second positional relationship as the second user belonging to the group; The payment processing device according to claim 7, characterized in that the identification means identifies a user as the second user belonging to the group when there is an instance of a money transfer between the first user and a user using a terminal device whose locational relationship with the first terminal device is either the first locational relationship or the second locational relationship.

9. a billing information transmitting means for transmitting billing information indicating the specified second user to the first terminal device; an edited billing destination information acquisition means for acquiring edited billing destination information indicating the second user after the editing in response to the first terminal device accepting an operation to edit the second user indicated by the transmitted billing destination information; Further comprising: The charge amount acquisition means acquires the amount of the charge for the second user indicated by the acquired edited billing destination information, The payment processing device according to claim 2 or 3, characterized in that the burden amount information sending means sends the burden amount information to the second terminal device used by the second user indicated by the acquired edited billing destination information.

10. The payment processing device according to claim 2 or 3, characterized in that the specified positional relationship is a positional relationship seen when the first user and the second user are using the facility as a group, and is a positional relationship between the first terminal device and the second terminal device.

11. The payment processing device according to claim 1 , wherein the granting means further executes a process of granting a benefit to the second user.

12. The payment processing device according to claim 11 , wherein the granting means grants the benefit to the second user, the benefit having a value corresponding to the amount of the charge.

13. the payment is a fee paid by the first user to the first facility when the first user uses the first facility, The payment processing device according to claim 1 or 11, characterized in that the granting means grants to the first user or the second user a benefit that can be used at a second facility that is different from the first facility and is located within a predetermined range of the first facility.

14. The fee to be settled is a fee paid by the first user to a facility when the first user uses the facility, The payment processing device according to claim 1 or 11, wherein the granting means grants a benefit that can be used at the facility to the first user or the second user.

15. The payment processing device according to claim 1 or 11, wherein the granting means grants the first user the benefit having a value corresponding to the amount of the payment minus the amount of the acquired charge.

16. The remittance means executes the process of remittance of the charge in a predetermined electronic money, 12. The payment processing device according to claim 1, wherein the granting means grants the benefit to the first user when the remittance by the remittance means is the first use of the specified electronic money by the second user.

17. The payment processing device according to claim 1 or 11, characterized in that the granting means grants a bonus to the first user when a payment process is executed in which the first user pays the fee and a process is executed by the remittance means to remit the charge from the second user to the first user, and does not grant a bonus to the first user when the payment process is executed but the process is not executed by the remittance means to remit the charge from the second user to the first user.

18. the charge acquisition means determines the amount of the charge of the first user and the amount of the charge of the second user to be amounts according to the age of the first user and the age of the second user, respectively; 3. The payment processing device according to claim 1, wherein the burden information transmitting means transmits the burden information indicating the amount of the burden determined for the second user by the burden acquisition means.

19. a second burden amount information transmitting means for transmitting second burden amount information indicating the acquired amount of the burden to the first terminal device; a modified burden amount information acquisition means for acquiring modified burden amount information indicating the amount of the burden after the change in response to the first terminal device accepting an operation to change the amount of the burden indicated by the transmitted second burden amount information; Further comprising:

3. The payment processing device according to claim 1, wherein the burden amount information transmitting means transmits the acquired changed burden amount information as the burden amount information.

20. a reservation information acquiring means for acquiring reservation information indicating a reservation made by the first user for a service available during the trip; a determination means for determining whether the payment request information has been received by the payment request information receiving means while the first user is traveling, and whether the travel has ended, based on the acquired reservation information; Further comprising: the payment amount acquisition means, when the determination means determines that a plurality of pieces of payment request information have been received during the trip, acquires the amount of the payment amount corresponding to the sum of the amounts of the plurality of fees to be paid in accordance with the plurality of pieces of payment request information; The payment processing device according to claim 1 or 2, characterized in that after the determination means determines that the trip has been completed, the burden amount information sending means transmits the burden amount information indicating the total amount of the burden acquired by the burden amount acquisition means in accordance with the total amount of the fare.

21. 1. A computer-implemented payment method comprising: a payment request information receiving step of receiving payment request information indicating a request for payment of a price to be paid by a first user, the payment request information being a payment using a first terminal device used by any first user belonging to a user group; a charge amount acquisition step of acquiring an amount of a charge to be charged to a second user belonging to the group and different from the first user, out of the amount of the payment to be paid in accordance with the received payment request information; a charge information transmission step of transmitting charge information indicating the acquired charge amount to a second terminal device used by the second user; a remittance request information receiving step of receiving remittance request information indicating a remittance request from the second terminal device in response to the second terminal device receiving the transmitted burden amount information and accepting a remittance operation; a remittance step of executing a process of remittance of the burden fee from the second user to the first user in response to the remittance request information being received by the remittance request information receiving step; a granting step of executing a process of granting a privilege to the first user on condition that the process of transferring the charge from the second user to the first user has been executed in the remittance step; 1. A method of processing a payment comprising:

22. Computer, a payment request information receiving means for receiving payment request information indicating a request for payment of a price to be paid by a first user, the payment request information indicating a request for payment of a price to be paid by the first user, the payment request information receiving means receiving payment request information indicating a request for payment of a price to be paid by the first user, the payment request information including a payment request for a payment using a first terminal device used by a first user belonging to a user group; a charge acquisition means for acquiring an amount of a charge to be charged to a second user belonging to the group and different from the first user, out of the amount of the payment to be paid in accordance with the received payment request information; a charge information transmitting means for transmitting charge information indicating the acquired charge amount to a second terminal device used by the second user; a remittance request information receiving means for receiving remittance request information indicating a remittance request from the second terminal device in response to the second terminal device receiving the transmitted burden amount information and accepting a remittance operation; a remittance means for executing a process of remittance of the charge from the second user to the first user in response to the remittance request information being received by the remittance request information receiving means; a granting means for executing a process of granting a privilege to the first user on condition that the process of transferring the charge from the second user to the first user has been executed by the remittance means; A payment processing program characterized by causing the program to function as a payment processing program.

Images