Payment processing device, payment processing method, and payment processing program
The system addresses the uncertainty in group payments by using positional and communication data to identify group members and confirm amounts owed, enhancing transparency and decision-making in payment splitting.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- RAKUTEN GROUP INC
- Filing Date
- 2024-12-25
- Publication Date
- 2026-07-23
AI Technical Summary
Users in a group cannot determine the exact amount they owe to other users until the money transfer is completed, leading to uncertainty in making payment decisions.
A system that acquires positional relationship information between users' terminal devices, identifies group members based on proximity and communication status, and allows users to confirm the amount owed before deciding to split the payment, with options for remittance and reward mechanisms.
Enables users to make informed payment decisions by knowing the amount owed to others, facilitating group payments with transparency and reducing uncertainty.
Smart Images

Figure 0007894433000001 
Figure 0007894433000002 
Figure 0007894433000003
Abstract
Description
Technical Field
[0001] The present invention relates to a method for assisting a plurality of users in making payments.
Background Art
[0002] When a group uses a facility or purchases something, the group may pay the cost by sharing it among members. Conventionally, techniques for assisting such payments are known.
[0003] For example, Patent Document 1 discloses a technique for performing a sharing settlement of a plurality of settlements made by a plurality of people using mobile terminals. In this technique, User A presets a group including User A and User B. By a settlement operation by User A, the terminal of User A transmits settlement information to the server, and the server calculates the expenditure amount and the allocated amount regarding the settlement within the group. Also, by a settlement operation by User B, the terminal of User B also transmits settlement information to the server, and the server calculates the expenditure amount and the allocated amount in the same manner. In response to a request for sharing calculation by User A, the server calculates the total expenditure and the total allocation of each user, and transmits a notification indicating that sharing payment is to be made to the terminal of User B. The terminal of User B displays a screen indicating that sharing payment is to be made. When User B approves the sharing payment, the server calculates the offset amount of each user, and transfers money among the users in the group based on the offset amount.
Prior Art Documents
Patent Documents
[0004]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0005] However, a user who is sending money to another user in a group cannot know whether or not that user will actually send the money until the transfer is completed. Users may want to know the amount they owe to the other user before deciding to send money.
[0006] The present invention has been made in view of the above points, and one example of the problem it addresses is to provide a payment processing device, a payment processing method, and a payment processing program that allow a user to choose to send money after knowing the amount to be paid to other users when multiple users are paying a fee. [Means for solving the problem]
[0007] To solve the above problems, the invention described in claim 1 is: Position relationship information acquisition means for acquiring position relationship information that indicates the positional relationship between a first terminal device of a first user that settles a payment and at least one terminal device different from the first terminal device, the position relationship information including first position information indicating the position of the first terminal device; identification means for identifying a user who uses a terminal device whose positional relationship is indicated to be a predetermined positional relationship based on the acquired positional relationship information as a second user belonging to the same group as the group to which the first user belongs; Once payment is completed, The aforementioned A screen display control means that automatically displays on the first terminal device a screen that allows the user to select whether or not to split the payment, and after the user selects to split the payment on the screen displayed on the first terminal device, The identified The system comprises: a burden amount information transmission means that transmits burden amount information indicating the amount of the burden to be charged to the second user to the second user's second terminal device; a remittance request information receiving means that receives remittance request information indicating a request for remittance from the second terminal device that received the transmitted burden amount information; and a remittance means that, in response to the receipt of the remittance request information by the remittance request information receiving means, executes a process to remit the burden from the second user to the first user. The identifying means identifies the user of a terminal device whose positional relationship to the first terminal device when the first terminal device is located in any facility is the predetermined positional relationship, and whose positional relationship to the first terminal device when the first terminal device is located outside the facility is the predetermined positional relationship, as the second user, but does not identify the user of a terminal device whose positional relationship to the first terminal device when the first terminal device is located outside the facility is not the predetermined positional relationship, even if the positional relationship to the first terminal device when the first terminal device is located in the facility is the predetermined positional relationship, as the second user. It is characterized by the following:
[0008] The invention described in claim 2 is, The system further includes a specific user screen display control means that, when the option to split the bill is selected on the screen displayed on the first terminal device, causes the first terminal device to display a specific user screen indicating the identified second user. It is characterized by the following:
[0009] The invention described in claim 3 is, The system further includes a means for determining the amount of the burden, which automatically determines the amount of the burden based on the amount of the payment that has been settled, and the means for transmitting the amount of the burden information transmits the amount of the burden information indicating the determined amount. It is characterized by the following:
[0010] The invention described in claim 4 further comprises a burden amount screen display control means that causes the first terminal device to display a burden amount screen that shows the determined amount of the burden, after it is selected to split the cost on the screen displayed on the first terminal device, and the burden amount information transmission means transmits the burden amount information showing the amount of the burden after it has been changed on the burden amount screen displayed by the first terminal device. The invention described in claim 5 is characterized in that, after the option to split the cost is selected on the screen displayed on the first terminal device, the amount of the cost is as follows 1 The system further includes a designated burden amount information receiving means for receiving designated burden amount information indicating an amount specified by the user, The means for transmitting the amount of burden information is characterized by transmitting the amount of burden information indicating the amount shown by the received designated amount of burden information. The invention described in claim 6 is further characterized by comprising granting means that performs a process of granting a benefit to the first user, on the condition that the remittance means has performed a remittance process from the second user to the first user. The invention described in claim 7 is, After the specific user screen is displayed on the first terminal device, the system further includes billing information receiving means that receives billing information from the first terminal device indicating the second user designated by the first user among the second users shown on the specific user screen, and the burden amount information transmitting means transmits the burden amount information to the second terminal device of the second user indicated by the received billing information. Characterized by 。
[0011] Claim 8 The invention described herein is characterized in that the identifying 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 time or longer.
[0012] According to this invention, if a first user is in a facility for a predetermined amount of time or longer, a second user belonging to the same group as the first user is identified. In order for a user to use a facility, they may need to be in that facility for a considerable amount of time. Therefore, by identifying situations in which the first user is likely to be using the facility, it is possible to identify a second user who is likely to be using the facility together with the first user.
[0015] Claim9 The invention described herein is characterized in that the acquired positional 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 identifying means identifies the positional relationship between the first terminal device and each of the at least one terminal device based on the communication status information.
[0016] According to this invention, the relative positions of terminal devices are determined based on the status of wireless communication between those terminal devices. For example, the reception status of a signal transmitted wirelessly from one terminal device by another terminal device may be influenced by the relative positions of those terminal devices. Therefore, the relative positions of users can be appropriately determined.
[0017] Claim 10 The invention described herein is characterized in that each of the at least one terminal device transmits a predetermined signal wirelessly, the communication status information indicates the terminal device that transmitted the predetermined signal and reached the first terminal device, and the identification means identifies the second user from among the users using the terminal device that transmitted the predetermined signal and reached the first terminal device.
[0018] According to this invention, each terminal device transmits a predetermined signal wirelessly. From among the users of the terminal devices whose transmitted predetermined signal reaches the first terminal device, a second user belonging to the same group as the first user is identified. The positional relationships between users within the range of the predetermined signal are likely to be positions that facilitate group activities. Therefore, a second user who uses the facility together with the first user can be appropriately identified.
[0019] Claim 11The invention described in is a remittance history capable of identifying users of each of the remitter and the remittance destination, and further includes remittance history information acquisition means for acquiring remittance history information indicating a remittance history in which the first user is either the remitter or the remittance destination, and the specifying means specifies the second user based on the acquired positional relationship information and the acquired remittance history information.
[0020] According to this invention, by further using remittance history information indicating the remittance history between users, a second user belonging to the same group as the first user is specified. A user who has made a remittance to the first user is likely to be a user who acts together with the first user. Therefore, the second user who uses the facility together with the first user can be appropriately specified.
[0044] Claim 12 The invention described in is a payment method executed by a computer, A positional relationship information acquisition step, which acquires positional relationship information indicating the positional relationship between a first terminal device of a first user that settles a payment and at least one terminal device different from the first terminal device, and which includes first position information indicating the position of the first terminal device; an identification step, which identifies a user who uses a terminal device whose positional relationship is indicated to be a predetermined positional relationship based on the acquired positional relationship information, as a second user belonging to the same group as the group to which the first user belongs; and When the settlement of the payment is completed, The aforementioned a screen display control step of automatically displaying, on the first terminal device, a screen enabling an operation of selecting whether to split the settled payment among the first terminal device, and after it is selected on the screen displayed on the first terminal device to split the payment, The identified a burden amount information transmission step of transmitting, to the second terminal device of the second user, burden amount information indicating the amount of the burden to be claimed from the second user, a remittance request information reception step of receiving, from the second terminal device that has received the transmitted burden amount information, remittance request information indicating a remittance request, and a remittance step of executing a process of remitting the burden amount from the second user to the first user in response to the remittance request information being received in the remittance request information reception step, and includes The identification step identifies the user of a terminal device whose positional relationship to the first terminal device when the first terminal device is located in any facility is the predetermined positional relationship, and whose positional relationship to the first terminal device when the first terminal device is located outside the facility is the predetermined positional relationship, as the second user, and does not identify the user of a terminal device whose positional relationship to the first terminal device when the first terminal device is located in the facility is the predetermined positional relationship, but whose positional relationship to the first terminal device when the first terminal device is located outside the facility is not the predetermined positional relationship, as the second user. characterized by this.
[0045] Claim 13 The invention described in is a computer, Position relationship information acquisition means for acquiring position relationship information that indicates the positional relationship between a first terminal device of a first user that settles a payment and at least one terminal device different from the first terminal device, the position relationship information including first position information indicating the position of the first terminal device; identification means for identifying a user who uses a terminal device whose positional relationship is indicated to be a predetermined positional relationship based on the acquired positional relationship information as a second user belonging to the same group as the group to which the first user belongs; When the settlement of the payment is completed, The aforementionedA screen display control means that automatically displays on the first terminal device a screen that allows the user to select whether or not to split the payment, and after the user selects to split the payment on the screen displayed on the first terminal device, The identified The system functions as follows: a burden amount information transmission means that transmits burden amount information indicating the amount of the burden to be charged to the second user to the second terminal device of the second user; a remittance request information receiving means that receives remittance request information indicating a request for remittance from the second terminal device that received the transmitted burden amount information; and a remittance means that, in response to the receipt of the remittance request information by the remittance request information receiving means, executes a process to remit the burden from the second user to the first user. The identifying means identifies the user of a terminal device whose positional relationship to the first terminal device when the first terminal device is located in any facility is the predetermined positional relationship, and whose positional relationship to the first terminal device when the first terminal device is located outside the facility is the predetermined positional relationship, as the second user, but does not identify the user of a terminal device whose positional relationship to the first terminal device when the first terminal device is located outside the facility is not the predetermined positional relationship, even if the positional relationship to the first terminal device when the first terminal device is located in the facility is the predetermined positional relationship, as the second user. It is characterized by the following: [Effects of the Invention]
[0046] According to the present invention, when multiple users pay a fee, users can choose to send money after knowing the amount they will pay to other users. [Brief explanation of the drawing]
[0047] [Figure 1] This figure shows an example of the general configuration of a communication system S according to one embodiment. [Figure 2] This block diagram shows an example of the outline configuration of an electronic payment server 1 according to one embodiment. [Figure 3] This figure shows an example of information stored in the database of electronic payment server 1. [Figure 4] This diagram shows an example of a functional block in the system control unit 11 of the electronic payment server 1. [Figure 5] This diagram shows an example of information sent from user terminal 2 to electronic payment server 1. [Figure 6] This figure shows an example of a specific group. [Figure 7] This figure shows an example of a specific group. [Figure 8] This figure shows an example of the payment completion screen 210. [Figure 9]This figure shows an example of the billing address editing screen 220. [Figure 10] This figure shows an example of the burden amount editing screen 230. [Figure 11] This figure shows an example of the billing screen 310. [Figure 12] This flowchart shows an example of processing in a communication system S in one embodiment. [Figure 13] This diagram shows an example of a functional block in the system control unit 11 of the electronic payment server 1. [Figure 14] (a) is a diagram showing an example of group identification. (b) is a diagram showing an example of a settlement log. [Figure 15] This figure shows an example of the general configuration of a communication system S according to one embodiment. [Figure 16] This figure shows an example of the information stored in the database of the travel reservation server 3. [Figure 17] This block diagram shows an example of the outline configuration of an electronic payment server 1 according to one embodiment. [Figure 18] An example of the information stored in the split-bill pending settlement DB14i is shown below. [Figure 19] This diagram shows an example of a functional block in the system control unit 11 of the electronic payment server 1. [Figure 20] (a) is a diagram showing an example of accommodation reservation information stored in the accommodation reservation DB3a. (b) is a diagram showing an example of transportation reservation information stored in the transportation ticket reservation DB3b. (c) is a diagram showing an example of the group's activities during the trip. [Figure 21] This figure shows an example of the payment editing screen 240. [Figure 22] This figure shows an example of the billing screen 310. [Modes for carrying out the invention]
[0048] Embodiments of the present invention will be described in detail below with reference to the drawings.
[0049] [1. First Embodiment] [1-1. Communication System Configuration] First, the configuration and functional overview of the communication system S according to the first embodiment will be described with reference to Figure 1. Figure 1 is a diagram showing an example of the overview configuration of the communication system S according to this embodiment. As shown in Figure 1, the communication system S is composed of 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 by, for example, 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 performs various processes related to the settlement of payments using a predetermined electronic payment application. The electronic payment application may be an application that can be executed by each user terminal 2, and may be an application that enables electronic payment of payments 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 usable for electronic payments include designated electronic money and credit cards. The service for using the designated electronic money may be provided by a company that provides electronic payment services using an electronic payment app, or by an affiliated company. For convenience, this designated electronic money will be referred to as R electronic money.
[0052] Furthermore, the electronic payment server 1 may perform transfers between users. For example, it may be possible to transfer money using R electronic money via an electronic payment application.
[0053] The electronic payment server 1 may identify groups consisting of multiple users, each possessing a user terminal 2. The identified groups may be, for example, groups of users who are presumed to be acting together.
[0054] If the user who paid using the electronic payment app is a member of the aforementioned group, the electronic payment server 1 may execute a process for each of the other members to pay a portion of the payment in a split payment arrangement. In this embodiment, "split payment" may include both all members paying equally and each member paying an amount set individually rather than being divided equally. When multiple users act together, some payment is incurred. Therefore, it is assumed that this payment will be shared among those users. Here, we assume that the member of the group who paid using the electronic payment app is the representative. The electronic payment server 1 may, for example, calculate the amount of each member's share based on the paid amount. The electronic payment server 1 may send 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 amount information. The user confirms the amount of the share and performs an operation to send the share to the representative. In response to this operation, the electronic payment server 1 may execute a transfer process using R electronic money from the other members to the representative.
[0055] The electronic payment management server 1 may, when a group member performs a remittance, execute a process to grant a reward to at least one of the representative and the member who made the remittance. Examples of rewards include R electronic money (cashback), coupons, and points usable in a points program. Coupons may be discount vouchers, preferential treatment vouchers, or free vouchers. These coupons may be usable at any facility or on any website. In addition to remittances using R electronic money, each member can pay the representative a contribution in other ways, such as cash. Granting rewards in response to remittances can encourage the use of R electronic money.
[0056] Each user terminal 2 may be a portable terminal device owned by a user who is eligible to use the electronic payment service described above. Examples of user terminals 2 include smartphones, tablet computers and other portable information terminals, mobile phones, PDAs (Personal Digital Assistants), and wearable computers. An electronic payment application may be installed on each user terminal 2. An example of payment using the electronic payment application is to display code information on the screen of the user terminal 2 that encodes information identifying the user making the payment. Examples of code information include one-dimensional barcodes and two-dimensional codes (e.g., QR code®). An employee of the facility to which the payment is to be made may, for example, have the code information displayed on the screen read by a POS register. The POS register may then send the payment request to the electronic payment server 1 via the POS system. Another example of payment using the electronic payment application is to have the user terminal 2 read code information that encodes information about the transaction item provided by the facility as consideration for the payment. Information about the transaction item may include, for example, information identifying the facility, information identifying the transaction item, and the amount of the payment. This code information may be displayed on a display within the facility or printed on paper. The user terminal 2, having read the code information, may send a payment request to the electronic payment server 1 based on the user's actions.
[0057] Each user terminal 2 may have a function to acquire its own location information. For example, user terminal 2 may use a satellite positioning system such as GPS (Global Positioning System) to calculate its latitude and longitude as location information. Alternatively, for example, a mobile communications carrier may provide user terminal 2 with location information using a base station. Furthermore, each user terminal 2 may be capable of wireless communication with other user terminals 2 using short-range wireless communication. Examples of standards for this short-range wireless communication include Bluetooth® and ZigBee®. Examples of upper limits on the distance at which communication is possible using this short-range wireless communication include several meters, tens of meters, and tens of meters. Each user terminal 2 may periodically or continuously transmit a presence notification signal using short-range wireless communication. The presence notification signal may indicate that the user terminal 2 that transmitted the presence notification signal is nearby or that a user using that user terminal 2 is nearby. The presence notification signal may include, for example, information that identifies the user.
[0058] [1-2. Configuration of the Electronic Payment Server] Next, the configuration of the electronic payment server 1 will be described with reference to Figures 2 and 3. Figure 2 is a block diagram showing an example of the schematic configuration of the electronic payment server 1 according to this embodiment. As shown in Figure 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 is composed of a CPU (Central Processing Unit) 11a, a ROM (Read Only Memory) 11b, a RAM (Random Access Memory) 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, for example, 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 on a device different from the electronic payment server 1. The electronic payment server 1 may be able to access the database through that device.
[0062] Figure 3 shows an example of information stored in the database of the electronic payment server 1. User DB 14a may store user information for each user who can use the electronic payment service. For example, the electronic payment server 1 may store user information such as user ID, name, gender, date of birth, address, telephone number, and email address, all associated with each other. The user ID is identification information that identifies the user.
[0063] Facility DB14b may store facility information for each facility where users can pay using an electronic payment app. Each facility offers a transaction item, which may be at least one of goods or services. Users can purchase goods or services offered at a facility by visiting it. Facility DB14b may store facility information such as facility ID, category information, facility name, address, and facility location information, all of which are associated with each other. The facility ID is identification information that identifies the facility. The category information indicates the category to which the facility belongs. Examples of facility categories include restaurants, cafes, fast food restaurants, other eateries, drive-ins, roadside stations, service areas, amusement parks, aquariums, museums, souvenir shops, concert venues, baseball stadiums, gas stations, car rental agencies, convenience stores, supermarkets, department stores, other shops, accommodations, train stations, airports, and ticket offices for other transportation. Facility location information may indicate the coordinates of the location where the facility is located. For example, facility location information may indicate the position of each vertex that constitutes the outer edge of the facility's site, using longitude and latitude.
[0064] The electronic money balance DB14c may store the balance of each user's R electronic money. For example, the electronic money balance DB14c may store the user ID and balance for each user, associated with each other.
[0065] The payment history DB14d may store a history of payments made using an electronic payment application. For example, each time a payment is made, the payment history DB14d may store the transaction number, payment date and time, user ID, payment method information, payee information, and payment amount as a payment log, all associated with each other. The transaction number is identification information that identifies the payment. The payment date and time indicates the date and time the payment was made. The user ID indicates the user who made the payment. The payment method information indicates the payment method used for the payment. The facility ID indicates the payee. If a user pays to a facility, the payee information may be the facility ID of that facility. The payment amount indicates the amount of the payment made.
[0066] The remittance history DB14e may store a history of remittances between users using R electronic money. For example, each time a remittance is made, the remittance history DB14e may store the remittance log, including the remittance number, the remitting user ID, the receiving user ID, and the remittance amount, in association with each other. The transaction number is identification information that identifies the settlement. The remittance number is identification information that identifies the remittance. The remitting user ID is the user ID of the user who made the remittance. The receiving user ID is the user ID of the user who received the remittance. The remittance amount indicates the amount that was remitted.
[0067] Location information DB14f may store location information indicating the location of each user terminal 2. Each user terminal 2 may periodically acquire location information and send it to the electronic payment server 1, for example, according to an electronic payment application. The electronic payment management server 1 may store the location information received from the user terminals 2 in location information DB14f. Location information DB14f may store location information such as user ID, recording date and time, and coordinate information in association with each other. The user ID indicates the user using the user terminal 2 that sent 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 in latitude and longitude at the time of the recording date and time.
[0068] The Inter-Terminal Communication Status DB 14g may store inter-terminal communication status information indicating the communication status between each user terminal 2 and other user terminals 2 using short-range wireless communication. Each user terminal 2 may periodically acquire inter-terminal communication status information and send it to the electronic payment server 1, for example, according to an electronic payment application. For example, each user's user terminal 2 may send 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 terminals 2 in the inter-terminal communication status DB 14g. The inter-terminal communication status DB 14g may store inter-terminal communication status information such as user ID, recording date and time, and signal source list, associated with each other. The user ID indicates the user using the user terminal 2 that sent 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 source list may be a list of user IDs of users using the user terminal 2 that sent the presence notification signal received by the user terminal 2 at the recording date and time. Furthermore, the signal source list may include the intensity of the presence notification signal received by the user terminal 2 at the recorded date and time, associated with each user ID. As mentioned above, the presence notification signal includes identification information that identifies the user using the user terminal 2 that sent the presence notification signal. The user terminal 2 may generate a signal source list containing the identification information contained in each received presence notification signal and send the inter-terminal communication status information to the electronic payment server 1. The identification information contained 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 piece of identification information contained in the signal source list of the inter-terminal communication status information received from the user terminal 2 into a user ID.
[0069] The Issued Coupon DB14h may store issued coupon information for each coupon granted to a user. By using a coupon, a user can receive a discount when purchasing the item(s) in the transaction. For example, the Issued Coupon DB14h may store issued coupon information such as the issue number, user ID, facility ID, applicable transaction information, and discount information, all of which are associated with each other. The issue number is identification information that identifies the granted coupon. The user ID indicates the user who acquired the coupon. The facility ID indicates the facility where the user can use the coupon. Applicable transaction information is set when the items to which the discount by the coupon applies are limited. Applicable transaction information is information that identifies the items to which the coupon applies. 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 payments, money transfers, and electronic payment applications. The server program may be acquired from other devices via a network NW, or it may be recorded on a recording medium such as magnetic tape, optical disc, or memory card and read via a drive device.
[0071] The communication unit 15 is composed of, for example, a network interface card. The communication unit 15 connects to a user terminal 2, etc., via a network NW and controls the communication status with the connected device.
[0072] [1-3. Overview of Functions] Next, with reference to Figures 4 to 12, an overview of the functions of the system control unit 11 in the electronic payment server 1 will be described. Figure 4 is a diagram showing an example of the functional blocks of the system control unit 11 in the electronic payment server 1. The system control unit 11 may function as a position relationship information acquisition unit 1101, a group identification unit 1102, a payment request reception unit 1103, a payment unit 1104, a billing destination information transmission unit 1105, an edited billing destination 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, and a benefit granting unit 1113, etc., as shown in Figure 4, by the CPU 11a reading and executing various program codes included in the server program.
[0073] [1-3-1. Identifying the Group] The position relationship information acquisition unit 1101 may acquire position relationship information indicating the positional relationship between multiple user terminals 2. For example, the position relationship information acquisition unit 1101 may acquire position relationship information indicating the positional relationship between any user terminal 2-1 among the user terminals 2 on which the electronic payment application is installed, and at least one other user terminal 2 different from user terminal 2-1. The user using user terminal 2-1 is referred to as the first user. The position relationship information may include at least the position information of user terminal 2-1. The position relationship information may also include the position information of each of the multiple user terminals 2. Based on the position information, the distance between user terminals 2 can be identified as a positional relationship. The distance between user terminals 2 can be calculated from the position information of each user terminal 2. The position relationship information may also include terminal-to-terminal communication status information received from each user terminal 2. The user ID included in the signal source list of terminal-to-terminal communication status information received from user terminal 2 indicates a user using a user terminal 2 located within range of the existence notification signal that reaches that user terminal 2. Whether a user terminal 2 is located within range of a presence notification signal transmitted by another user terminal 2 corresponds to the relative positions of those user terminals 2. The signal source list may include the strength of the presence notification signal in addition to the user ID. Whether a user terminal 2 is located within range of a presence notification signal transmitted by another user terminal 2 with that signal strength also corresponds to the relative positions of those user terminals 2.
[0074] The designation of any user terminal 2 as user terminal 2-1 is arbitrary. For example, the location relationship information acquisition unit 1101 may identify each user terminal 2 as user terminal 2-1 and acquire location relationship information indicating the location relationship based on that user terminal 2-1. Alternatively, the location relationship information acquisition unit 1101 may identify any user terminal 2 that has moved into any of the facilities as user terminal 2-1. Alternatively, the location relationship information acquisition unit 1101 may identify any user terminal 2 that has received an operation to settle a payment to a facility as user terminal 2-1.
[0075] Figure 5 shows an example of information transmitted from user terminal 2 to electronic payment server 1. In Figure 5, user terminals 2-1 and 2-2 are shown as user terminals 2. User terminal 2-1 transmits an existence notification signal R1 containing the identification information of user terminal 2-1. User terminal 2-2 transmits an existence notification signal R2 containing the identification information of user terminal 2-2. User terminal 2-1 receives the existence notification signal R2. User terminal 2 then transmits, for example, the location information of user terminal 2-1 along with the inter-terminal communication status information containing the identification information of user terminal 2-2 to the electronic payment server 1. User terminal 2-2 receives the existence notification signal R1. User terminal 2 also transmits the location information of user terminal 2-2 along with the inter-terminal communication status information containing the identification information of user terminal 2-1 to the electronic payment server 1. In this way, the location relationship information acquisition unit 1101 acquires location information and inter-terminal communication status information from each user terminal 2. Alternatively, the location relationship information acquisition unit 1101 may acquire location information and inter-terminal communication status information received from the user terminal 2 and stored in the location information DB 14f and inter-terminal communication status DB 14g, respectively, from those 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 the facility together. For example, the group identification unit 1102 may allow users to set up groups, as disclosed in Patent Document 1. For example, a user may set up a group by entering information that identifies each member of the group (e.g., name and address, telephone number, or email address). However, users do not necessarily use the facility with the same members every time. Therefore, users need to set up a group each time they engage in group activities or use the facility. It may be desirable to identify a group of users who use the facility together while reducing the workload on the user.
[0077] Therefore, the group identification unit 1102 may identify a second user belonging to the same group as the first user based on the location relationship information acquired by the location relationship information acquisition unit 1101. The user terminal 2 used by the second user is called user terminal 2-2. The group identification unit 1102 may, for example, identify as the second user a user who uses a user terminal 2 that is different from user terminal 2-1, and whose location relationship when user terminal 2-1 is located in any facility is indicated by the location relationship information as a predetermined location relationship. One second user may be identified, or multiple second users may be identified.
[0078] The predetermined spatial relationship may be, for example, the spatial relationship between user terminals 2 held by user 1 and user 2 when they are acting as a group, when they are acting together, or when they are using a facility together. For example, if the users are in places where they can hear each other's voices or see each other, they may be acting as a group. The following are specific examples of the predetermined spatial relationship.
[0079] Positional relationship a: The distance between user terminals 2 is less than a predetermined distance. Location relationship b: The signal strength of the presence notification signal transmitted by one of the user terminals 2, at the location of the other user terminal 2, 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, one specific positional relationship among positional relationships a, b, and c. Alternatively, the predetermined positional relationship may be any combination of positional relationships a, b, or c, or a combination of two specific positional relationships among those positions.
[0081] Positional relationship 'a' indicates that the users are in close proximity to each other. Users in a group tend to act in close proximity to one another. Also, when users in a group speak directly to each other, they need to be in a certain degree of proximity.
[0082] The signal strength in positional relationship b is the reception strength of the presence notification signal transmitted by one user terminal 2 to the other user terminal 2. Positional relationship b may also indicate that the users are in close proximity to each other. Furthermore, positional relationship b may indicate that there is a high probability that there are no obstacles between the users. Users in a group tend to act in the same area (e.g., facility, room, etc.). If there is an obstacle, such as a wall, between users, the presence notification signal transmitted from user terminal 2 may not reach the other user terminal 2, or the reception strength may be low. In positional relationship b, where the threshold is set to zero, the user terminals 2 are located in such a position that the presence notification signal transmitted by one user terminal 2 reaches the other user terminal 2. Whether or not the presence notification signal was received can be determined by whether or not the user ID is included in the signal source list. Let's assume there are two user terminals 2, a first user terminal 2 and a second user terminal 2. The signal strength at the time the second user terminal 2 receives the presence notification signal transmitted by the first user terminal 2 may differ from the signal strength at the time the first user terminal 2 receives the presence notification signal transmitted by the second user terminal 2. In this case, the group identification unit 1102 may determine, for example, whether the average value of the signal strengths is higher than a threshold. Alternatively, the group identification unit 1102 may determine whether either of the signal strengths is higher than a threshold. Alternatively, the group identification unit 1102 may determine whether both signal strengths are higher than a threshold.
[0083] Location relationship c indicates that those users may be using the same facility. For example, based on the location information of user terminal 2 and the facility location information stored in facility DB 14b, it is possible to determine whether user terminal 2 is located within a facility and which facility it is located within.
[0084] If the predetermined positional relationship includes at least one of positional relationships a and b, the group identification unit 1102 may identify users who use user terminals 2 that are within a predetermined distance or whose signal strength is greater than a threshold, based on the user terminal 2 of a specific user as the first user, as users belonging to the same group as the first user. For example, the specific user may be a user who pays using an electronic payment application. Alternatively, the group identification unit 1102 may identify the positional relationship between each user terminal 2 as the first user, and then identify users belonging to the same group by comprehensively considering these positional relationships. Alternatively, the group identification unit 1102 may use clustering to identify groups of users that are close to each other or groups of users with high reception strength of presence notification signals.
[0085] Figure 6 shows an example of group identification. For example, each user of user terminal 2 located in position a and position b belongs to the same group. Figure 6 shows users U1 to U5. Each user possesses a user terminal 2. Let's assume that user U1 is the first user among users U1 to U5. User U1 is currently inside restaurant 110. Users U2 to U5 are users located less than a predetermined distance from user U1. Therefore, user U1 and users U2 to U5 are in position a. Users U2 and U3 are inside restaurant 110. The presence notification signals R2 and R3 transmitted by user terminal 2 possessed by user U2 and user terminal 2 possessed by user U3 have reached user terminal 2 possessed by user U1. Therefore, user U1 and users U2 and U3 are in position b. For this reason, the group identification unit 1102 may determine that users U1 to U3 belong to the same group. User U4 is outside restaurant 110. The presence notification signal R4 transmitted by user terminal 2, which user U4 possesses, is blocked by the outer wall of restaurant 110 and does not reach user U1. User U5 is inside restaurant 110. However, the presence notification signal R5 transmitted by user terminal 2, which user U5 possesses, is blocked by the inner wall 111 of 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 user U1.
[0086] The group identification unit 1102 may identify a second user belonging to the same group as the first user, provided that the location information of user terminal 2-1 indicates that user terminal 2-1 has been located at the facility for a predetermined amount of time or longer. In order for a user to use a facility, that user may need to stay at the facility for a certain amount of time or longer. The group identification unit 1102 may determine whether the first user is using the facility based on the time. If it is presumed that the first user is using the facility, and the positional relationship between user terminal 2-1 and user terminal 2-2 is such that it is presumed that the first user and the second user are acting together, then it is presumed that those users are using the facility together. The time required to use a facility may be the same for all facilities, or it may be set for each category of facility. For example, it may be set that a time of 30 minutes or more is required to use a restaurant, while a time of 5 minutes or more is required to use a supermarket. For categories of facilities that can be used in a considerably short time, such time restrictions may not be imposed.
[0087] Since each user can move at any time, the relative positions of user terminals 2 can also change over time. Therefore, even among users belonging to the same group, there may be times when the relative positions of their user terminals 2 are not in a predetermined position. Conversely, even among users who do not belong to the same group, there may be times when the relative positions of their user terminals 2 are in a predetermined position. In this case, the positional relationship information acquisition unit 1101 may determine that users whose relative positions of user terminals 2 are in a predetermined position for a predetermined proportion of time or more within a unit of time 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 is different from user terminal 2-1 and whose positional relationship with user terminal 2-1 when user terminal 2-1 is located outside the facility is a predetermined positional relationship. In this case, the predetermined positional relationship may be, for example, the positional relationship between user terminals 2 owned by the first user and the second user as observed when they are acting as a group or when they are acting together. Positional relationship c may be excluded from the predetermined positional relationship in this case. When the group to which the first user belongs is using the facility, there may also be users who do not belong to that group and are using the facility. In this case, even among users who do not belong to that group, there may be users whose positional relationship with the first user is a predetermined positional relationship. When outside the facility, users spend relatively more time moving than when inside the facility. Therefore, when outside the facility, the positional relationship between a user belonging to a certain group and a user who does not belong to that group may not be a predetermined positional relationship, or the time during which it is not a predetermined positional relationship may be longer. By determining the positional relationships outside the facility, users who are unlikely to belong to the group can be excluded. The positional relationship information acquisition unit 1101 may use the positional relationships of the first user before they moved into the facility. In this case, it may be predetermined how many hours before the first user moves into the facility the positional relationships should be identified. Alternatively, the positional relationship information acquisition unit 1101 may use the positional relationships of the first user after they have moved outside the facility. In this case, it may be predetermined how many hours after the first user moves outside the facility the positional relationships should be identified. Alternatively, the positional relationships may be identified both before and after the first user moves into the facility. Even when users are outside the facility, the positional relationship information acquisition unit 1101 may identify users who belong to the same group from among those users whose positional relationships with user terminals 2 are predetermined for a predetermined proportion of time or longer within a unit of time.
[0089] Figure 7 shows an example of group identification. Each user of user terminal 2 located in position a and position b belongs to the same group. Figure 7 shows users U1 to U4. Each user possesses a user terminal 2. For example, let's assume user U1 is the first user. As shown in Figure 7(a), users U1 to U4 are outdoors. Users U1 and U2 are moving in close proximity to each other. The presence notification signal R2 transmitted by user terminal 2 possessed by user U2 reaches user terminal 2 possessed by user U1. Users U3 and U4 are moving at a considerable distance from user U1. Furthermore, the presence notification signals R3 and R4 transmitted by user terminal 2 possessed by user U3 and user terminal 2 possessed by user U4, respectively, do not reach user terminal 2 possessed by user U1.
[0090] Subsequently, as shown in Figure 7(b), users U1 to U4 visited restaurant 120 at the same time. The distance between user U1 and each of users U2 to U4 is less than a predetermined distance. Also, the presence notification signals R2, R3, and R4 transmitted by the user terminals 2 of users U2, U3, and U4 respectively reached the user terminal 2 held by user U1. If the determination is made only based on the positional relationship within restaurant 120, users U1 to U4 are determined to belong to the same group. However, outdoors, the positional relationship between user U1 and user U2 is a predetermined positional relationship, while the positional relationship between user U1 and users U3 and U4 is not a predetermined positional relationship. Therefore, the group identification unit 1102 may determine that users U1 and U2 belong to the same group, while users U3 and U4 do not belong to the same group as user U1.
[0091] As described later, when a first user belonging to a group performs an operation on user terminal 2 to settle a payment for the facility, the electronic payment server 1 executes a process for other members of the group to send money to the first user. The group identification unit 1102 may identify the group before the payment is made, or it may identify the group at the time the payment is made.
[0092] [1-3-2. Payment] The payment request receiving unit 1103 may receive a payment request indicating a payment request using user terminal 2-1 used by any first user belonging to a user group. This payment may be for an amount payable by the first user. The user group may be a group already identified by the group identification unit 1102 or a group to be identified in the future.
[0093] The payment request may include, for example, the user ID of the first user making the payment, the facility ID of the facility to which the payment is made, payment method information, and payment amount. The payment request receiving unit 1103 may receive payment requests from, for example, the user terminal 2-1, or from a system such as a POS system.
[0094] The settlement unit 1104 settles the payment in response to the settlement request being received by the settlement request receiving unit 1103. For example, if the payment method is R electronic money, the settlement unit 1104 may perform a process to subtract the payment amount from the balance of the first user stored in the electronic money balance DB 14c, based on the user ID and payment amount included in the payment request. Alternatively, the settlement unit 1104 may perform a process to add the payment amount to the amount of sales made using R electronic money at the facility to which the payment is made. If the payment method is a credit card, the settlement unit 1104 may obtain the card information of the first user. The card information may include, for example, the card number, expiration date, and the name of the cardholder. For example, the storage unit 14 may store information of the card registered in the electronic payment application for each user. The settlement unit 1104 may perform a process to settle the payment using the card information. The payment method may be a known payment method using a credit card.
[0095] Once the payment is complete, the payment unit 1104 may store the 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 newly generated transaction number and the user ID, payment method information, facility ID, and payment amount included in the payment request.
[0096] [1-3-3. Money transfer for splitting the bill] Once the payment is complete, the payment unit 1104 may display a payment completion screen on the user terminal 2-1 indicating that the payment has been completed. The payment completion screen may, for example, be a screen that allows the user to choose whether or not to have other members pay a portion of the payment. The payment unit 1104 may also send a web page equivalent to the payment completion screen to the user terminal 2-1.
[0097] Figure 8 shows an example of a payment completion screen 210. As shown in Figure 8, the payment completion screen 210 may include, for example, a split-the-bill message 211, an approval button 212, and a rejection button 213. The completion message 211 is a message that asks whether or not to split the bill. The approval button 212 is a button that can be operated to approve the split-the-bill. The rejection button 213 is a button that can be operated to reject the split-the-bill.
[0098] The billing information transmission unit 1105 may transmit provisional billing information indicating the second user identified by the group identification unit 1102 to the user terminal 2-1. The provisional billing information may indicate the second user as the user to be billed for the charges. For example, the provisional billing information may include the second user's user ID and name. The billing information transmission unit 1105 may transmit the provisional billing information only when, for example, the approval button 212 is pressed by the first user on the payment completion screen 210.
[0099] The billing information transmission unit 1105 may display a billing recipient editing screen on the user terminal 2-1 for the first user to confirm and edit the users to whom the charges are billed, as indicated by the provisional billing recipient information. Editing the billing recipient users may include at least one of adding or deleting billing recipient users. The billing information transmission unit 1105 may also transmit, for example, a web page corresponding to the billing recipient editing screen to the user terminal 2-1. This web page may include the provisional billing recipient information.
[0100] Figure 9 shows an example of the billing recipient editing screen 220. As shown in Figure 9, the billing recipient editing screen 220 may include one or more billing recipient information entries 221, an add button 222, and a next button 223. Each billing recipient information entry 221 displays the name of a second user identified by the group identification unit 1102. Each billing recipient information entry 221 may include a delete button 224. The delete button 224 is a button that can be operated to remove the second user indicated by the billing recipient information entry 221 from the list of billing recipient users. When the delete button 224 is operated, the billing recipient information entry 221 including this delete button 224 is removed from the billing recipient editing screen. The add button 222 is a button that can be operated to add a billing recipient user. When the add button 222 is operated, the user terminal 2-1 may display, for example, a billing recipient addition screen. The billing recipient addition screen may include, for example, input fields for a telephone number or email address. When the first user enters a phone number or email address, the billing information transmission unit 1105 may search the user terminal DB 14a for user information, including the entered phone number or email address. The billing information transmission unit 1105 may also send the user ID and name included in the retrieved user information to the user terminal 2-1. The user terminal 2-1 may display the name sent from the electronic payment server 1 on the billing address addition screen. When the first user performs an operation to add the user indicated by the displayed name as a billing address, the user terminal 2-1 may clear the billing address addition screen, redisplay the billing address editing screen 220, and add the billing address information 221 corresponding to the added user to the billing address editing screen 220. The next button 223 is a button that can be operated to provisionally confirm the user indicated by the billing address information 221 currently displayed on the billing address editing screen 220 as a billing address user.
[0101] The Edited Billing Information Acquisition Unit 1106 may acquire edited billing information indicating the user of the billing destination after editing, in response to user terminal 2-1 receiving an operation to edit the user of the billing destination for the charges indicated by the provisional billing destination information transmitted by billing destination information transmission unit 1105. For example, when the first user operates the next button 223 on the billing destination editing screen 220, user terminal 2-1 may transmit edited billing information, including the user ID of the user indicated by each billing destination information 221 displayed on the billing destination editing screen 220, to the electronic payment server 1.
[0102] The burden amount acquisition unit 1107 may acquire the amount of the burden to be billed to the second user, who belongs to the same group as the first user, as the user to whom the burden is billed, from the amount of the payment to be settled in response to the settlement request received by the settlement 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 settlement by the settlement unit 1104 has been completed.
[0103] When the editing request information acquisition unit 1106 receives editing request information from the user terminal 2-1, the cost acquisition unit 1107 may acquire the cost after receiving the editing request information. In this case, the cost acquisition unit 1107 may acquire the cost for each user of the edited request indicated by the editing request information.
[0104] The cost acquisition unit 1107 may automatically determine the cost based on the amount of the payment that has been settled. The cost acquisition unit 1107 may also determine the cost for each member so that the sum of the costs for all members in the group, including the first user, matches the amount of the payment. For example, the cost acquisition unit 1107 may calculate the cost per person by dividing the amount of the payment by the number of members in the group.
[0105] The provisional burden amount information transmission unit 1108 may transmit provisional burden amount information, which indicates the burden amount obtained by the burden amount acquisition unit 1107, to the user terminal 2-1. The provisional burden amount information may include the user ID, name, and burden amount for each user identified by the group identification unit or indicated by the editing request destination information.
[0106] The provisional burden amount information transmission unit 1108 may display a burden amount editing screen on the user terminal 2-1 for the first user to confirm and change each user's burden amount. The provisional burden amount information transmission unit 1108 may also transmit, for example, a web page equivalent to the burden amount editing screen to the user terminal 2-1. This web page may include provisional burden amount information.
[0107] Figure 10 shows an example of the burden amount editing screen 230. As shown in Figure 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 about the user who will bear at least a portion of the settled amount. The burden amount editing screen 230 displays burden user information 231 corresponding to each second user, and may also include burden user information 231 corresponding to the first user. Each burden user information 231 may include the user's name. 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 obtained 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 used to reduce the amount displayed in the amount input field 232 by a predetermined amount. The back button 235 is a button used to redisplay the billing recipient editing screen 220. The confirmation button 236 is a button used to provisionally confirm the amount currently displayed in each amount input field 232 as the final amount. The confirmation button 236 may only be enabled if the total amount of all users' burdens matches the amount of the payment that has been settled. When the confirmation button 236 is operated, the user terminal 2-1 may display the billing confirmation screen. The billing confirmation screen may display the name and burden amount of each user. On the billing confirmation screen, the first user can perform operations to confirm the billing recipients and the burden amounts of each user.
[0108] The Changed Burden Amount Information Acquisition Unit 1109 may acquire Changed Burden Amount Information indicating the changed burden amount when the user terminal 2-1 accepts 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 the changed amount of the first user, as well as the user ID and the changed burden amount of each user to whom the burden payment is billed.
[0109] The burden amount information transmission unit 1110 may transmit the burden amount information, which indicates the burden amount obtained by the burden amount acquisition unit 1107, to the user terminal 2-2 used by the second user. If the changed burden amount information is obtained by the changed burden amount information acquisition unit 1109, the burden amount information transmission unit 1110 may transmit the changed burden amount information as burden amount information. In addition, if the edited billing destination information is obtained by the edited billing destination information acquisition unit 1106, the burden amount information transmission unit 1110 may transmit the burden amount information to the user terminal 2-2 used by the user to whom the payment indicated by the edited billing destination information is billed.
[0110] The burden amount information transmission unit 1110 may transmit burden amount information and have the user terminal 2-2 display this burden amount information. For example, the burden amount information transmission unit 1110 may display a request screen on the user terminal 2-2 for the second user to send the burden amount to the first user. The burden amount information transmission unit 1110 may also transmit a web page corresponding to the request screen to the user terminal 2-1. This web page may include the burden amount. This web page may also include the user ID of the second user as the sender user ID and the user ID of the first user as the recipient user ID.
[0111] Figure 11 shows an example of a billing screen 310. As shown in Figure 11, the billing screen 310 may include payment information 311, payment amount information 312, a remittance button 313, a charge button 314, and a non-remittance button 315. The payment information 311 may include the payment date, the name of the facility to which the payment was made, the payment amount, etc. The payment amount information 312 indicates the amount to be borne by the user using the user terminal 2-2 that displays the billing screen. The remittance button 313 is a button for sending the payment amount using R electronic money. When the remittance button 313 is operated, the user terminal 2-2 may, for example, display a remittance confirmation screen. The remittance confirmation screen may include the name of the second user as the sender, the name of the first user as the recipient, and the payment amount as the amount to be sent. The second user can perform operations to execute the remittance based on the information shown on the remittance confirmation screen. The charge button 314 is a button that can be operated to charge R electronic money. When the charge button 314 is operated, the user terminal 2-2 may display, for example, a charge screen. The second user can charge R electronic money according to the charge screen. Once the charge is complete, the user terminal 2-2 may redisplay the billing screen 310. The non-transfer button 315 is a button that can be operated to display a predetermined home screen of the electronic payment application without performing a transfer.
[0112] The remittance request receiving unit 1111 may receive a remittance request from user terminal 2-2 indicating a request for remittance from the second user to the first user, in response to user terminal 2-2 accepting a remittance operation after receiving burden amount information transmitted by burden amount information transmission unit 1110. For example, when the operation to execute a remittance is performed on the remittance confirmation screen, user terminal 2-2 may send a remittance request to the electronic payment server 1. The remittance request may include the second user's user ID as the remitter user ID, the first user's user ID as the recipient user ID, and the burden amount as the remittance amount.
[0113] The remittance unit 1112 may, upon receiving a remittance request from the remittance request receiving unit 1111, execute a process to remit the payment from the second user to the first user. For example, the remittance unit 1112 may subtract the amount to be remitted included in the remittance request from the balance associated with the same user ID as the remitter user ID included in the remittance request in the electronic money balance DB 14c. Alternatively, the remittance unit 1112 may add the amount to be remitted included in the remittance request to the balance associated with the same user ID as the recipient user ID included in the remittance request in the electronic money balance DB 14c. In this way, the remittance unit 1112 may update the balances of both the first and second users.
[0114] Once the transfer is complete, the transfer unit 1112 may store the transfer log in the transfer history DB 14e. At this time, the transfer unit 1112 may generate a new transfer number. The transfer unit 1112 may generate a transfer log based on the generated transfer number and the sender user ID, recipient user ID, and transfer amount included in the transfer request.
[0115] The system control unit 11 may execute the process of transferring money from the second user to the first user in a split payment manner only when a payment request for payment to a facility is transmitted to the facility while the user terminal 2-1 is located at that facility. Alternatively, the system control unit 11 may execute the process of transferring money from the second user to the first user in a split payment manner only when a payment request for payment to a facility is transmitted to the facility while the user terminal 2-1 is located within a predetermined distance from that facility. Alternatively, the system control unit 11 may execute the process of transferring money from the second user to the first user in a split payment manner even if the first user moves after a payment request for payment to a facility has been transmitted.
[0116] [1-3-4. Granting of Benefits] The reward granting unit 1113 may, in response to the remittance processing being executed by the remittance unit 1112, perform a process to grant the reward to at least one of the first user and the second user. The reward granting unit 1113 may grant the reward to only one of the first user and the second user who made the remittance, or it may grant the reward to both.
[0117] The reward granting unit 1113 may grant a reward to a second user that can be used at a facility different from the facility to which payment was made using the electronic payment app, but located within a predetermined range from the facility to which payment was made. 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 located within a predetermined range from the facility to which payment was made include facilities within a predetermined distance in a straight line from the facility to which payment was made, facilities within a predetermined distance traveled along a route from the facility to which payment was made, facilities within a predetermined time travel from the facility to which payment was made, and facilities in the same area as the facility to which payment was made. Examples of areas include cities, towns, districts, and city blocks. The group is at or near the facility to which payment was made. By granting a reward, the user or group to which the reward was granted can be encouraged to use another facility near where the group is located.
[0118] The reward granting unit 1113 may grant a reward to the second user that can be used at the same 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 is granted to reuse the facility.
[0119] The reward distribution unit 1113 may provide coupons that are only usable at predetermined facilities. Alternatively, the reward distribution unit 1113 may provide coupons that are only usable for the purchase of predetermined goods or transactions.
[0120] When granting a reward to a second user, the reward granting unit 1113 may grant a reward of value corresponding to the burden amount obtained by the burden amount acquisition unit 1107 or the burden amount obtained by the changed burden amount information acquisition unit 1109. The reward granting unit 1113 may increase the value of the reward as the burden amount increases. This provides the second user with an incentive to pay the burden amount to the first user via remittance, the higher the burden amount presented to the second user. The value of the reward may be, for example, a predetermined percentage of the burden amount. When granting R electronic money, the reward granting unit 1113 may increase the amount granted as the burden amount increases. When granting a coupon, the reward granting unit 1113 may increase the discount amount or discount rate of the coupon granted as the burden amount increases. Alternatively, the value of the reward may be fixed.
[0121] The reward granting unit 1113 may randomly decide whether or not to grant the reward to the second user after the transfer is completed. For example, the reward granting unit 1113 may display a video of a lottery on the user terminal 2-2 and grant the reward if the second user wins the lottery.
[0122] The reward granting unit 1113 may grant the reward to the first user each time any second user in the group sends a contribution. Alternatively, the reward granting unit 1113 may grant the reward to the first user only once when any second user in the group sends a contribution. Alternatively, the reward granting unit 1113 may grant the reward to the first user only when all second users in the group have sent contributions.
[0123] When granting a benefit to the first user, the benefit granting unit 1113 may grant a benefit of value corresponding to the amount of the payment minus the amount borne by the second user. That is, the benefit granting unit 1113 may grant a benefit of value corresponding to the amount borne by the first user out of the amount of the payment settled. The value of the benefit may be, for example, a predetermined percentage of the amount borne by the first user, an amount calculated by dividing the amount borne by the first user by the number of second users in the group, or an amount equivalent to the amount borne by the first user. When granting R electronic money, the benefit granting unit 1113 may grant a higher amount the higher the amount borne. When granting a coupon, the benefit granting unit 1113 may grant a higher discount amount or discount rate for the coupon the higher the amount borne. Alternatively, the value of the benefit may be fixed.
[0124] [1-4. Operation of the communication system] Next, the operation of the communication system S will be described with reference to Figure 12. Figure 12 is a flowchart showing an example of processing of the communication system S in this embodiment. The example shown in Figure 12 is an example of processing when a group is identified before payment is made. The example shown in Figure 12 is an example of processing when R electronic money is given as a reward to the first user and a coupon is given as a reward to the second user.
[0125] As shown in Figure 12, user terminal 2-1 periodically acquires location information and inter-terminal communication status information and transmits it to the electronic payment management server 1 (step S101). User terminal 2-2 also periodically acquires location information and inter-terminal communication status information and transmits it to the electronic payment management server 1 (step S102). The location relationship information acquisition unit 1101 of the electronic payment management server 1 stores the location information and inter-terminal communication status information transmitted from each user terminal 2 in the location information DB 14f and the inter-terminal communication status DB 14g, respectively.
[0126] The group identification unit 1102 of the electronic payment management server 1 monitors, for example, 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 longer. Here, the group identification unit 1102 determines that user terminal 2-1 is located in the facility for a predetermined time or longer (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 user terminal 2-1 belongs (step S104). Here, the group identification unit 1102 may, for example, identify users of user terminal 2 that are located outside the facility and whose location relationship with user terminal 2-1 is a predetermined location relationship as a candidate for group member. For example, the group identification unit 1102 may identify users of user terminal 2 whose location relationship with user terminal 2-1 is a specific location relationship among location relationships a and b, or both, for a predetermined proportion of the time during the predetermined period before user terminal 2-1 moves to that facility. The group identification unit 1102 may search the location information DB 14f for the user ID of a user using a user terminal 2 located within a predetermined distance from the location of user terminal 2-1, as location relationship a. The group identification unit 1102 may also search for a user whose presence notification signal strength is higher than a threshold from the inter-terminal communication status information transmitted from user terminal 2-1, as location relationship b. Once member candidates are identified, the group identification unit 1102 may identify as a member of the group users of user terminal 2 whose location relationship with user terminal 2-1 within the facility is a predetermined location relationship. For example, the group identification unit 1102 may identify users of user terminal 2 whose location relationship with user terminal 2-1 is a specific location relationship among location relationships a, b, and c, a combination of two specific location relationships among those location relationships, or a combination of all of those location relationships for a predetermined percentage or more of the time user terminal 2-1 is located in the facility.
[0127] Meanwhile, user U1, using user terminal 2-1, performs an operation to settle the payment to the facility (step S105). In response to this operation, for example, user terminal 2-1 sends a payment request to electronic payment server 1 (step S106). The payment unit 1104 of electronic payment management server 1 executes the payment processing for that amount based on the payment request (step S107). The payment unit 1104 also stores the payment log in the payment history DB 14d.
[0128] Next, the settlement unit 1104 sends the payment completion screen 210 webpage to the user terminal 2-1 (step S108). At this time, if the settlement unit 1104 confirms that the payee information included in the payment request is the facility ID of the facility where the user terminal 2-1 is located, it adds a split payment message 211, an approval button 212, and a rejection button 213 to the payment completion screen 210. The user terminal 2-1 displays the payment completion screen 210, and user U1 operates the approval button 212. In response to this operation, the user terminal 2-1 sends an approval response to the electronic payment management server 1 (step S109). The approval response indicates that user U1 has approved the split payment.
[0129] Upon receiving the approval response, the billing information transmission unit 1105 of the electronic payment management server 1 sends the billing information editing screen 220 webpage 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 webpage. The user terminal 2-1 displays the billing information editing screen 220, and user U1 adds or deletes members of the billing recipients for the charges as needed (step S111). When user U1 operates the next button 223, the user terminal 2-1 sends 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, which has received the editing request destination information, calculates the burden amount for each member of the request destination (step S113). For example, the burden amount acquisition unit 1107 may count the number of user IDs included in the editing request destination information as the number of members of the group. The burden amount acquisition unit 1107 may also 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 burden amount editing screen 230 webpage to the user terminal 2-1 (step S114). At this time, the provisional burden amount information transmission unit 1108 includes the user ID and name of each user included in the edited billing information, as well as the burden amount calculated for each user, on this webpage. The user terminal 2 displays the burden amount editing screen 230, and user U1 changes the burden amount as necessary (step S115). When user U1 confirms 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] Upon receiving the change burden amount information, the burden amount information transmission unit 1110 of the electronic payment management server 1 transmits the invoice screen webpage to each user terminal 2 used by users other than user U1, who are indicated by the user ID included in the change burden amount information (step S117). User U2, who uses user terminal 2-2, is among the recipients of the webpage. The burden amount information transmission unit 1110 includes the burden amount for user U2, indicated by the change burden amount information, and the user ID of user U1 in this webpage. User terminal 2-2 displays the invoice screen 310, and user U2 operates the remittance button 313. Then, when user U2 performs the operation to execute the remittance on the remittance confirmation screen (step S118), user terminal 2-2 transmits the remittance request to the electronic payment management server 1 (step S119).
[0133] Upon receiving a remittance request, the remittance unit 1112 of the electronic payment management server 1 executes the remittance process from user U2 to 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 the reward granting process (step S121). For example, the reward granting unit 1113 may calculate a predetermined percentage of the amount borne by user U2 as the discount amount of the coupon to be granted to 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 payment is made. The reward granting unit 1113 may determine one of the searched facilities as a facility where the coupon to be granted to user U2 can be used. The reward granting unit 1113 may generate coupon information including the user ID of 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. Alternatively, the reward granting unit 1113 may calculate a predetermined percentage of the amount borne by user U1 as the amount of electronic money to be granted to user U2. The reward granting unit 1113 may add the calculated amount to the balance stored in the electronic money balance DB 14c associated with user U1.
[0135] Once the reward granting process is complete, the reward granting unit 1113 sends a webpage for the remittance completion notification and reward granting notification screen to user terminal 2-2 (step S122). The remittance completion notification and reward granting notification screen displays a message indicating that the remittance has been completed. The remittance completion notification and reward granting notification screen also displays a message indicating that a coupon has been granted to user U2, along with the name of the facility where the coupon can be used and the discount amount. The reward granting unit 1113 then sends a webpage for the deposit notification and reward granting notification screen to user terminal 2-1 (step S123). The deposit notification and reward granting notification screen displays a message indicating that a deposit has been made to user U1. The deposit notification and reward granting notification screen also displays a message indicating that a cashback has been made to user U1 in R electronic money, along with the amount of the cashback.
[0136] As described above, according to this embodiment, the electronic payment server 1 may receive a payment request using 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 total amount to be settled in response to the payment request. The electronic payment server 1 may also transmit contribution amount information indicating the amount of the contribution to user terminal 2-2. The electronic payment server 1 may also receive a remittance request from user terminal 2-2 in response to user terminal 2-2 accepting a remittance operation after receiving the contribution amount information. The electronic payment server 1 may also execute a process to send the contribution from the second user to the first user in response to receiving a remittance request. In this case, the payment is settled using user terminal 2-1. As a result, the first user initially pays the payment on behalf of the group. Subsequently, contribution amount information indicating the amount to be borne by the second user belonging to the group from the total amount to be settled is transmitted to user terminal 2-2 used by the second user. Therefore, the second user can find out the amount to be borne. Then, the second user performs an operation on user terminal 2-2, and the payment is transferred from the second user to the first user. Therefore, when multiple users are paying a fee, each user can choose to transfer money knowing the amount they will pay to the other users.
[0137] Here, the electronic payment server 1 may acquire positional relationship information indicating the positional relationship between user terminal 2-1 and at least one other user terminal 2 that is different from user terminal 2-1. Alternatively, the electronic payment server 1 may identify a user who uses a user terminal 2 whose positional relationship with user terminal 2-1 when it is located in the facility is indicated by the positional relationship information as a predetermined positional relationship, as a second user belonging to the group. In this case, positional relationship information indicating the positional relationship between user terminal 2-1 and other user terminals 2 is acquired. The positional relationship between user terminals 2 can be the positional relationship between the users who use those user terminals 2. Furthermore, a user whose positional relationship with the first user when the first user is at the facility where the payment is to be settled is determined to be a predetermined positional relationship is identified as a second user belonging to the same group as the first user. Since the first and second users whose positional relationship is a predetermined positional relationship may be using the facility together, it may be reasonable for the second user to bear at least a portion of the amount 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 belonging to a group that used the facility.
[0138] Here, the electronic payment server 1 may identify the second user on the condition that location information indicates that user terminal 2-1 has been in the facility for a predetermined time or longer. In this case, if the first user has been in the facility for a predetermined time or longer, the second user belonging to the same group as the first user will be identified. In order for a user to use a facility, they may need to be in that facility for a considerable amount of time. Therefore, by identifying situations in which the first user is likely to be using the facility, it is possible to identify the second user who is likely to be using the facility together with the first user.
[0139] Furthermore, the electronic payment server 1 may identify a second user from among users who use user terminal 2, the location of which is a predetermined location when user terminal 2-1 is located outside the facility. In this case, even if a user's location is the predetermined location when the first user is inside the facility, a user whose location is not the predetermined location 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 happened to be in the same facility as the first user but did not act together with the first user outside the facility can be excluded from being a second user belonging to the same group as the first user.
[0140] Furthermore, the electronic payment server 1 may determine the positional relationship between user terminal 2-1 and at least one other user terminal 2 based on the inter-terminal communication status information. In this case, the positional relationship between the user terminals 2 is determined based on the status of wireless communication between the user terminals 2. For example, the reception status of a presence notification signal transmitted wirelessly from one user terminal 2 by another user terminal 2 may be influenced by the positional relationship between those user terminals 2. Therefore, the positional relationship between users can be appropriately determined.
[0141] Here, the electronic payment server 1 may identify the second user from among the users using user terminal 2 that transmitted the presence notification signal that reached user terminal 2-1. In this case, each user terminal 2 transmits a presence notification signal wirelessly. From among those user terminals 2, the second user belonging to the same group as the first user is identified from among the users using user terminal 2 whose transmitted presence notification signal reached user terminal 2-1. The spatial relationships between users within the range of the presence notification signal are likely to be in positions that make it easy for those users to act as a group. Therefore, the second user who uses the facility together with the first user can be appropriately identified.
[0142] Furthermore, the electronic payment server 1 may send billing information indicating the identified second user to the user terminal 2-1. Alternatively, the electronic payment server 1 may obtain edited billing information indicating the edited second user when the user terminal 2-1 accepts 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 belonging to the same group as the first user.
[0143] Furthermore, the predetermined positional relationship may also be the positional relationship between user terminal 2-1 and user terminal 2-2 as seen when the first user and the second user are using the facility as a group.
[0144] Furthermore, the electronic payment server 1 may grant a reward 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 payment to the first user, the reward is granted to at least one of the first user and the second user. Thus, users can be encouraged to make remittances for splitting the bill.
[0145] Here, the electronic payment server 1 may grant the second user a benefit of value commensurate with the amount of the payment. In this case, the higher the amount of the second user's payment, the more the server can encourage the second user to make a payment.
[0146] Furthermore, the electronic payment server 1 may grant the second user a benefit that can be used at a second facility located within a predetermined range from the first facility, which is a different facility from the first facility to which the payment was made. In this case, the group will be granted a benefit that can be used at the second facility located within a predetermined range from the first facility they used. Since the group was at the second facility, they are in a location that makes it easy for them to move to the second facility. Therefore, it is possible to encourage them to use the second facility.
[0147] Furthermore, the electronic payment server 1 may grant the second user benefits that can be used at the facility to which the payment was made. In this case, the group can be encouraged to reuse the facilities they have used.
[0148] Furthermore, the electronic payment server 1 may grant the first user a benefit of value corresponding to the amount remaining after deducting the second user's contribution. In this case, the higher the first user's contribution, the more likely it is to encourage the first user to use a payment method that allows for splitting the bill.
[0149] Furthermore, the electronic payment server 1 may send provisional payment amount information indicating the amount to be paid to the user terminal 2-1. Also, when the user terminal 2-1 accepts an operation to change the payment amount indicated by the provisional payment amount information, the electronic payment server 1 may acquire changed payment amount information indicating the changed payment amount. Furthermore, the electronic payment server 1 may send the changed payment amount information as payment amount information to the user terminal 2-2. In this case, the payment amount acquired 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, the remittance history is used to identify the group. The second embodiment may be identical to the first embodiment, except for the points described below.
[0151] Figure 13 shows an example of a functional block of the system control unit 11 in the electronic payment server 1. In Figure 13, elements identical to those in Figure 4 are denoted by the same reference numerals. The difference between Figure 13 and Figure 4 is that Figure 13 includes an additional remittance history acquisition unit 1114.
[0152] The remittance history acquisition unit 1114 may acquire remittance history from the remittance history DB 14e. The remittance history acquisition unit 1114 may acquire remittance history where the user using the user terminal 2, from which at least some of the location relationship information (e.g., location information) has been acquired by the location relationship information acquisition unit 1101, is either the sender or the recipient. For example, the remittance history acquisition unit 1114 may acquire remittance history where the first user is either the sender or the recipient. The sender and recipient are identified by the sender user ID and recipient 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 location relationship information. In this embodiment, for example, a predetermined location relationship includes a combination of at least two location relationships from location relationships a to c. For convenience, each of the at least two location relationships is referred to as the first location relationship and the second location relationship. The group identification unit 1102 may identify a user who uses a user terminal 2 whose location relationship with user terminal 2-1 is both the first location relationship and the second location relationship as a second user belonging to the same group as the first user. This point is basically the same as in the first embodiment. On the other hand, suppose there is a user who uses a user terminal 2 whose location relationship with user terminal 2-1 is only one of the first location relationship and the second location relationship. In this case, the group identification unit 1102 may determine, based on the remittance history, whether or not there has been a remittance between that user and the first user. If a transfer has been made, that user may be identified as a second user belonging to the same group as the first user.
[0154] In some cases, it may not be possible to obtain information that should be included in the location relationship information from some user terminals 2. For example, a typical user terminal 2 may have a setting to enable or disable the location information acquisition function, or a setting to enable or disable the short-range wireless communication function. If the location information acquisition function is disabled, the electronic payment server 1 cannot obtain location information from that user terminal 2. Therefore, the electronic payment server 1 cannot determine that the location relationship of that user terminal 2 with other user terminals 2 is location relationship a or c. Also, if the short-range wireless communication function is disabled, that user terminal 2 will neither transmit an existence notification signal nor detect an existence notification signal transmitted from other user terminals 2. Therefore, the electronic payment server 1 cannot obtain terminal-to-terminal communication status information from that user terminal 2. Consequently, the electronic payment server 1 cannot determine that the location relationship of that user terminal 2 with other user terminals 2 is location relationship b. Since at least one of the two location relationship conditions for determining that a user is a second user will always be unmet, the user will never be determined to belong to any group. However, the user satisfies the other party's location relationship conditions. Therefore, the possibility remains that the user belongs to the group. Users who have sent money to or received money from the first user are likely to be acquaintances of the first user. If the acquaintance is near the first user, in the same facility as the first user, or within range of the presence notification signal, then the acquaintance is likely to be acting together with the first user. Therefore, the group identification unit 1102 may use the remittance history as an alternative to location information or inter-terminal communication status information to identify the group.
[0155] Figure 14(a) is a diagram illustrating an example of group identification. For example, users whose user terminal 2 is located in positions a, b, and c are considered to belong to the same group. Figure 14(a) shows users U1 to U4. For example, let's assume user U1 is the first user. Users U1 to U4 are currently inside Hotel 113. Users U2 to U4 are located less than a predetermined distance from user U1. Therefore, user U1 and users U2 to U4 are in position a. Users U2 and U3 have enabled the short-range wireless communication function of their user terminal 2. Therefore, user terminals 2 for users U2 and U3 respectively transmit presence notification signals R2 and R3. Presence notification signals R2 and R3 reach 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, user U4 has disabled the short-range wireless communication function of user terminal 2. Therefore, user terminal 2 either does not send inter-terminal communication status information to the electronic payment server 1, or sends inter-terminal communication status information to the electronic payment server 1 that does not include the identification information of any user. For this reason, the group identification unit 1102, which has identified user U4, who is located in the same facility as user U1 and is within a predetermined distance from user U1, and whose presence notification signal strength is not higher than a threshold, may search for a remittance log that includes the user ID of either user U1 or U4 as the sender user ID and the user ID of the other user as the recipient user ID. Figure 14(b) is a diagram showing an example of a payment log. As shown in Figure 14(b), the remittance history DB 14e stores a remittance log that includes user U4's user ID as the sender user ID and user U1's user ID as the recipient user ID. Therefore, the group identification unit 1102 may determine that users U1 to U4 are members of the same group.
[0157] As explained above, according to this embodiment, a second user belonging to the same group as the first user is identified based on the remittance history between users. Users with whom remittances have been made are likely to be users who act together with the first user. Therefore, a second user who uses the facility together with the first user can be appropriately identified.
[0158] [3. Third Embodiment] Next, a third embodiment will be described. In the third embodiment, the amount each member pays is determined based on the age of the group members. Except as described below, the second embodiment may be identical to at least one of the first and second embodiments.
[0159] In this embodiment, the burden amount acquisition unit 1107 determines the burden amount for each of the first user and the second user identified by the group identification unit 1102, according to the age of the first user and the age of the second user, respectively. Therefore, the older the age, the higher the burden amount. For example, the burden amount may be proportional to age. In this case, the burden amount acquisition unit 1107 may calculate the burden amount per year by dividing the amount of the settlement by the sum of the ages 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 for the burden amount may be predetermined for each age. In this case, the older 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 settlement by the sum of the allocation 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 allocation points of each member. Furthermore, each user's age can be determined from their date of birth stored in user DB14a.
[0160] The burden amount information transmission unit 1110 may transmit the burden amount information, which indicates the burden amount determined for the second user by the burden amount acquisition unit 1107, to the user terminal 2-2. If the first user is allowed to change the burden amount, the changed burden amount information acquisition unit 1109 may transmit provisional burden amount information, which indicates the burden amount determined for the second user by the burden amount acquisition unit 1107, to the user terminal 2-1.
[0161] As explained above, according to this embodiment, the older each user is, the higher the fee they will have to pay. Therefore, each user can be required to pay an amount corresponding to their age.
[0162] [4. Fourth Embodiment] Next, a fourth embodiment will be described. In the fourth embodiment, whether or not the first user is granted a benefit depends on whether or not the second user has experience using R electronic money. Except for the points described below, the second embodiment may be identical to 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 if the transfer of the payment from the second user to the first user is due to the second user's first use of R electronic money. This encourages the first user to use electronic payment apps for payments or to split bills. Furthermore, it is expected that the second user, who has used R electronic money for the first time, will continue to use R electronic money in the future.
[0164] The reward granting unit 1113 may determine whether the second user is using R electronic money for the first time based on the settlement history DB 14d and the remittance history DB 14e. For example, if the settlement log containing the second user's user ID is not stored in the settlement history DB 14d, and, excluding the remittance log for the current remittance from the second user to the first user, no remittance logs containing the second user's user ID as the remitter user ID are stored in the remittance history DB 14e, the reward granting unit 1113 may determine that the second user is using R electronic money for the first time.
[0165] As explained above, according to this embodiment, if a second user who has never used R electronic money before uses R electronic money for the first time when sending money from the second user to the first user, the first user will be granted a benefit. Therefore, by encouraging the first user to use a payment method that allows for splitting bills, the use of R electronic money can be promoted.
[0166] [5. Fifth Embodiment] Next, a fifth embodiment will be described with reference to Figures 15 to 22. In the previous embodiments, the second user was billed for their share of the cost each time the first user made a payment. In this embodiment, the payments made by the first user during the group trip are combined, and the second user is billed for their share after the trip. The purpose of the trip is not particularly limited. Except for the points described below, the fifth embodiment may be identical to at least one of the first to fourth embodiments.
[0167] Figure 15 is a diagram showing an example of the schematic configuration of the communication system S according to this embodiment. In Figure 15, the same reference numerals are used for elements that are the same as those in Figure 1. As shown in Figure 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 booking server 3 may be a server device that performs various processes related to the travel booking site. The travel booking site may be a website that allows users to book services available during their 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 booking server 3 may perform processing to book services for the trip in response to a request from the user terminal 2.
[0169] The travel booking server 3 may include databases such as accommodation booking DB3a and airline ticket booking DB3b. The electronic payment server 1 may be able to access the databases provided by the travel booking server 3 via a network NW. Alternatively, the storage unit 14 of the electronic payment server 1 may store a copy of the databases provided by the travel booking server 3. The electronic payment server 1 may, for example, periodically update the contents of the databases to the latest information.
[0170] Figure 16 shows an example of information stored in the database of the travel reservation server 3. As shown in Figure 16, the accommodation reservation DB 3a may store accommodation reservation information each time a reservation is made. For example, the accommodation reservation DB 3a may store accommodation reservation information such as reservation number, user ID, facility ID, start date of stay, end date of stay, scheduled check-in time, check-out deadline, number of guests, price, and payment method, all of which are associated with each other. The reservation number is a number that identifies the reservation. The user ID indicates the user who made the accommodation reservation. The facility ID indicates the reserved facility. The start date of stay indicates the date on which check-in will take place at the accommodation. The end date of stay indicates the date on which check-out will take place at the accommodation. The scheduled check-in time indicates the time on which check-in will take place. The check-out deadline indicates the time by which check-out must be completed. The number of guests indicates the number of users who are scheduled to stay at the accommodation. The price indicates the accommodation fee that will be charged to the reservation holder for using the accommodation. The payment method indicates how the fee will be paid. Payment methods may include on-site payment and online payment. On-site payment indicates that the reservation holder pays the fee at the booked accommodation. Online payment indicates that the fee is automatically charged based on the credit card information that the reservation holder has registered in advance on the travel booking website.
[0171] Transportation reservation DB3b may store transportation reservation information related to the reservation of transportation tickets each time a reservation is made. Examples of tickets include airline tickets, express train tickets and regular tickets, highway bus tickets, and ship boarding passes. Accommodation reservation DB3a may store accommodation reservation information such as reservation number, user ID, transportation type, departure point ID, arrival point ID, scheduled departure date and time, scheduled arrival date and time, number of seats, and price, all of which may be associated with each other. The reservation number is a number that identifies the reservation. The user ID indicates the user who made the transportation ticket reservation. The transportation type indicates the type of transportation for which the ticket was reserved. The departure point ID is the facility ID of the facility that is the departure point of the transportation for which the ticket was reserved. The arrival point ID is the facility ID of the facility that is the arrival point of that transportation. Examples of facilities that serve as departure and arrival points include airports, train 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 date and time indicates the expected arrival date and time of the transportation. The number of seats indicates the number of reserved seats. The fare indicates the price of the reserved ticket.
[0172] Figure 17 is a block diagram showing an example of the schematic configuration of the electronic payment server 1 according to this embodiment. In Figure 17, elements similar to those in Figure 2 are denoted by the same reference numerals. The difference between Figure 17 and Figure 2 is that in Figure 17, the split payment pending settlement DB 14i is added to the database stored in the storage unit 14.
[0173] Figure 18 shows an example of information stored in the split-bill pending settlement DB14i. As shown in Figure 18, the split-bill pending settlement DB14i may store pending settlement information for settlements for which splitting the bill has been put on hold during the user's trip, each time such a settlement is made. For example, the split-bill pending settlement DB14i may store pending settlement information such as a transaction number and a user ID, associated with each other. The transaction number indicates the settlement for which splitting the bill has been put on hold. The user ID indicates the user who paid for that settlement.
[0174] Figure 19 shows an example of a functional block of the system control unit 11 in the electronic payment server 1. In Figure 19, elements identical to those in Figure 4 are denoted by the same reference numerals. The difference between Figure 19 and Figure 4 is that Figure 19 includes the addition of a reservation information acquisition unit 1115, a travel determination unit 1116, and a payment information transmission unit 1117.
[0175] The reservation information acquisition unit 1115 acquires reservation information indicating a reservation made by the first user for services available during the trip. The acquired reservation information may be at least one of accommodation reservation information and transportation reservation information. The user ID included in the reservation information makes it possible to identify whether or not the reservation was made by the first user.
[0176] The travel determination unit 1116 may determine, based on the reservation information acquired by the reservation information acquisition unit 1115, whether or not a payment request was received by the payment request receiving unit 1103 during the trip by the first user. That is, the travel determination unit 1116 may determine whether or not the first user paid for the trip during the trip. The travel determination unit 1116 may also determine, based on the reservation information, whether or not the first user's trip has ended.
[0177] For example, when using accommodation reservation information, the travel determination unit 1116 may determine that the first user is traveling for at least the period from the scheduled check-in time on the start date of the stay to the final check-in time on the end date of the stay. The travel determination unit 1116 may further use the 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 more than a predetermined distance away from the first user's address on the start date of the stay. Alternatively, 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 first user's address on or after the end date of the stay.
[0178] When using transportation reservation information, the travel determination unit 1116 may determine, for example, whether the reserved transportation ticket is for the outbound or return journey. For example, the travel determination unit 1116 may compare the distance from the first user's address to the departure point of the transportation with the distance from that address to the arrival point of the transportation. The location of the facility as the departure or arrival point is indicated by the facility location information stored in the facility DB 14b. The travel determination unit 1116 may determine that the ticket is for the outbound journey if the distance to the departure point is shorter, and that the ticket is for the return journey if the distance to the arrival point is shorter. The travel determination unit 1116 may determine that the first user's journey begins from the scheduled departure date and time in the outbound transportation reservation information. The travel determination unit 1116 may also determine that the first user's journey ends at the scheduled arrival date and time in the return transportation reservation information. The travel determination unit 1116 may further use the 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 user terminal 2-1 reaches the departure point on the scheduled departure date. Alternatively, the travel determination unit 1116 may determine that the first user's trip has started when the user terminal 2-1 is a predetermined distance or more away from the first user's address on the scheduled departure date. Furthermore, the travel determination unit 1116 may determine that the first user's trip has ended when the user terminal 2-1 reaches the destination on the scheduled arrival date. Alternatively, the travel determination unit 1116 may determine that the first user's trip has ended when the user terminal 2-1 is within a predetermined distance of the first user's address on the scheduled arrival date.
[0179] The travel determination unit 1116 may make a determination using both accommodation reservation information and 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 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 first user's address. The travel determination unit 1116 may also determine that the first user is traveling from the point when the location of the user terminal 2-1 is more than a second predetermined distance (e.g., 5 km) away from the first user's address until it approaches within the second predetermined distance of that address. The second predetermined distance is shorter than the first predetermined distance.
[0181] The travel 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 travel determination unit 1116 may determine whether the first user is traveling or not each time a payment request is received by the payment request receiving unit 1103, based on the location history of the user terminal 2-1 and reservation information.
[0182] The travel determination unit 1116 may store the transaction number of each payment request received during the first user's trip and the user ID of the first user who made the payment in the split payment pending payment DB 14i.
[0183] Figure 20(a) shows an example of accommodation reservation information stored in the accommodation reservation DB3a. Figure 20(b) shows an example of transportation reservation information stored in the transportation ticket reservation DB3b. For example, suppose user U1 lives in Tokyo. User U1 plans to travel to Okinawa with users U2 and U3. Therefore, user U1 made a reservation for Hotel F in Okinawa through a travel reservation website. As a result, as shown in Figure 20(a), the accommodation reservation DB3a stores the accommodation reservation including user U1's user ID. The start date of the stay is March 2nd, and the end date of the stay is March 4th. In addition, user U1 made round-trip air tickets for three people between Haneda Airport and Naha Airport. Therefore, as shown in Figure 20(b), the transportation ticket reservation DB3b stores the outbound and return transportation reservation information including user U1's user ID. The planned departure date for the outbound trip is March 2nd. The planned arrival date for the return trip is March 4th.
[0184] Figure 20(c) shows an example of a group's activities during a trip. On March 2nd, users U1 to U3 arrived at Haneda Airport (step S201). The travel determination unit 1116 may determine that user U1 has started their trip from this point. User U1's group had breakfast at a restaurant in the airport, and user U1 paid for it using an electronic payment app (S202). Afterwards, the group traveled to Naha Airport by passenger plane (step S203). Then, the group checked into Hotel F (step S204). On March 3rd, the group rented a car from a rental shop (step S205). The group drank coffee at a coffee shop along the way (step S206). That evening, the group ate and drank at an izakaya (Japanese pub) (S207). User U1 paid for each of the expenses for that day using an electronic payment app. On March 4th, the group checked out of Hotel F, and user U1 paid for the accommodation using an electronic payment app (step S208). The group arrived at Naha Airport and purchased souvenirs at a shop inside the airport. Again, user U1 paid for the purchases using an electronic payment app. Then, the group traveled to Naha Airport by passenger plane (step S210). The travel determination unit 1116 may determine that the trip has ended when the first user arrives at Haneda Airport. The travel determination unit 1116 may also determine that the payments in steps S202 and S205-S209 were made during the trip.
[0185] The group identification unit 1102 may identify second users belonging to the group by considering reservation information acquired by the reservation information acquisition unit 1115 in addition to location information. Accommodation reservation information includes the number of guests, and transportation reservation information includes the number of seats. The number of guests and the number of seats may correspond to the number of members in the group. Therefore, the group identification unit 1102 may identify second users equal to the number of guests or seats in the group.
[0186] The payment unit 1104 does not have to include the split-the-bill message 211, the approval button 212, and the rejection button 213 on the payment completion screen 210 displayed on the user terminal 2-1 when it has processed a payment request in response to a payment request that the travel determination unit 1116 has determined to have been received during the first user's trip. Therefore, the split-the-bill does not occur at the time the payment is settled. On the other hand, the payment unit 1104 may include the split-the-bill message 211, the approval button 212, and the rejection button 213 on the payment completion screen 210 for payment requests that have not been determined to have been received during the first user's trip.
[0187] If the travel determination unit 1116 determines that there are multiple payment requests received during the first user's trip, the payment information transmission unit 1117 may, after the travel determination unit 1116 determines that the trip has ended, transmit multiple payment information items, each indicating a payment corresponding to one of those payment requests, to the user terminal 2-1. Each payment information item may include, for example, a transaction number, a payment date, the name of the facility to which the payment is made, and the payment amount. The payment information transmission unit 1117 may also search the split payment 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 travel determination unit 1116. The payment information transmission unit 1117 may also search the payment history DB 14d for a payment log containing the same transaction number as the transaction number included in the pending payment information. The payment information transmission unit 1117 may then 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 for splitting the bill. The payment information transmission unit 1117 may also transmit, for example, a web page equivalent to the payment editing screen to the user terminal 2-1. This web page may contain payment information.
[0189] Figure 21 shows an example of the payment editing screen 240. As shown in Figure 21, the payment editing screen 240 may include multiple payment information items 241, an approval button 243, and a rejection button 244. Each payment information item 241 is information about a payment made at the request of the first user. Each payment information item 241 may include, for example, the payment date, the name of the payee, the payment amount, etc. Furthermore, the payment information item 241 may include a delete button 242. The delete button 242 is a button that can be operated to remove the amount paid in the payment indicated by the payment information item 241 from the split payment. When the delete button 242 is operated, the payment information item 241 including this delete button 242 is removed from the payment editing screen 240. The approval button 243 is a button that can be operated to approve the inclusion of the amount paid in the payment indicated by the payment information item 241 currently displayed on the payment editing screen 240 in the split payment. When the approval button 243 is operated, the user terminal 2-1 may display the billing address editing screen 220. Subsequently, the screens may sequentially transition to the burden amount editing screen 230 and the billing confirmation screen according to the user's operation.
[0190] If accommodation fees are paid online, they are not included in the cost-sharing scheme under the methods described above. Similarly, if accommodation fees are paid in cash at the accommodation facility, they are not included in the cost-sharing scheme. Furthermore, assuming that online payment is the only method available for paying for transportation tickets, the purchase price is also not included in the cost-sharing scheme. However, the payment information transmission unit 1117 can obtain the fees from the reservation information. Therefore, the payment information transmission unit 1117 may include the cost of services used during the trip, regardless of whether the payment for the reserved service was made using an electronic payment app, and regardless of whether the payment was made during the trip. For example, in the example shown in Figure 21, the cost of round-trip air tickets may also be included in the cost-sharing scheme.
[0191] The cost acquisition unit 1107 may acquire the cost amount corresponding to the sum of the amounts of payments made according to the payment request information, if there are multiple payment requests that the travel determination unit 1116 has determined to have been received during the first user's trip. For example, the cost acquisition unit 1107 may acquire the payment amount from each payment log retrieved by the payment information transmission unit 1117. The cost acquisition unit 1107 may calculate the cost amount per person by dividing the sum of the multiple payment amounts by the number of members in the group identified by the group identification unit 1102. Alternatively, the cost acquisition unit 1107 may calculate the cost amount for each member based on the total amount of payments and the age of each member of the group. If any payment is removed from the split payment target on the cost amount editing screen 230, the cost acquisition unit 1107 may calculate the total payment amount excluding the removed payment. The cost acquisition unit 1107 may, as described above, include the cost of services booked for travel in the cost to be split, regardless of whether or not the payment was made using an electronic payment app.
[0192] After the travel determination unit 1116 determines that the first user's trip has ended, the cost amount information transmission unit 1110 may transmit cost amount information, which indicates the cost amount obtained by the cost amount acquisition unit 1107 according to the total cost, to the user terminal 2-2. After transmitting the cost amount information, the cost amount information transmission unit 1110 may delete the pending settlement information, including the user ID of the first user whose trip has been determined to have ended, from the split payment pending settlement DB 14i.
[0193] Figure 22 shows an example of a billing screen 310. In Figure 22, elements similar to those in Figure 11 are denoted by the same reference numerals. As shown in Figure 22, the billing screen 310 may include multiple 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 represents the sum of the multiple payment amounts indicated by the multiple payment information 311.
[0194] As explained above, according to this embodiment, based on the reservation information for the travel service, it is determined whether or not 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. If payment is made during the first user's trip, no processing for remittance based on splitting the bill is performed at that time. After the trip ends, processing for remittance based on splitting the bill is performed for all 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 after the trip.
[0195] [6. Other Embodiments] In the embodiments described so far, the group identification by the group identification unit 1102 based on location information was performed for the purpose of transferring money between members within the group for splitting bills. However, group identification may be used for purposes other than splitting bills or transferring money between members. For example, group identification may be used for sharing information among group members, distributing information according to common or similar attributes among members within the group, or distributing information about the facility where the group is located.
[0196] (Appendix 1-1) A payment processing device that uses a first terminal device used by any first user belonging to a group of users, comprising: payment request information receiving means for receiving payment request information indicating a request for payment of an amount to be paid by the first user; burden amount acquisition means for acquiring the amount of the burden to be charged to a second user, who belongs to the group but is different from the first user, from the amount to be settled according to the received payment request information; burden amount information transmission means for transmitting the burden amount information indicating the acquired burden amount to a second terminal device used by the second user; 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 accepting a remittance operation after receiving the transmitted burden amount information; and remittance means for executing a process to remit 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 according to Appendix 1-1, further comprising: position relationship information acquisition means for acquiring position relationship information that indicates the positional relationship between the first terminal device and at least one terminal device different from the first terminal device, and which includes first position information indicating the position of the first terminal device; and identification means for identifying a user who uses one of the at least one terminal devices, whose positional relationship when the first terminal device is located at the facility is shown to be a predetermined positional relationship based on the acquired positional relationship information, as the second user belonging to the group.
[0198] (Appendix 1-3) The payment processing device according to Appendix 1-2, characterized in that the identifying 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 time or longer.
[0199] (Appendix 1-4) The payment processing device according to Appendix 1-2 or 1-3, wherein the identifying means identifies the second user from among users who use a terminal device among the at least one terminal device such that the positional relationship between the first terminal device and the first terminal device when the first terminal device is located outside the facility is a predetermined positional relationship.
[0200] (Appendix 1-5) The positional relationship information obtained 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 identifying means identifies the positional relationship between the first terminal device and each of the at least one terminal device based on the communication status information, as described in any one of Appendix 1-2 to 1-4.
[0201] (Appendix 1-6) The payment processing device according to Appendix 1-5, wherein each of the at least one terminal devices transmits a predetermined signal wirelessly, the communication status information indicates the terminal device that transmitted the predetermined signal and reached the first terminal device, and the identification means identifies the second user from among the users using the terminal device that transmitted the predetermined signal and reached the first terminal device.
[0202] (Appendix 1-7) A payment processing device according to any one of Appendix 1-2 to 1-6, further comprising a means for acquiring remittance history information that acquires remittance history information indicating that the first user is either the remittance source or the recipient, 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 according to Appendix 1-7, wherein the predetermined positional relationship includes a predetermined first positional relationship and a predetermined second positional relationship different from the first positional relationship, the identifying means identifies a user who uses a terminal device whose positional relationship with the first terminal device is both the first and second positional relationship as the second user belonging to the group, and the identifying means identifies a user who uses a terminal device whose positional relationship with the first terminal device is only one of the first and second positional relationships as the second user belonging to the group when there is a fact of remittance between the user and the first user.
[0204] (Appendix 1-9) A payment processing device according to any one of Appendix 1-2 to 1-8, further comprising: billing information transmission means for transmitting billing information indicating the identified second user to the first terminal device; and edited billing information acquisition means for acquiring edited billing information indicating the second user after editing, in response to the first terminal device receiving an operation to edit the second user indicated by the transmitted billing information, wherein the amount of the charge acquisition means acquires the amount of the charge for the second user indicated by the acquired edited billing information, and the amount of the charge information transmission means transmits the amount of the charge information to the second terminal device used by the second user indicated by the acquired edited billing information.
[0205] (Appendix 1-10) The payment processing device according to any one of Appendix 1-2 to 1-9, characterized in that the predetermined positional relationship is the positional relationship observed when the first user and the second user are using the facility as a group, and is the positional relationship between the first terminal device and the second terminal device.
[0206] (Appendix 1-11) The payment processing device according to any one of Appendix 1-1 to 1-10, further comprising granting means for performing a process of granting a benefit to at least one of the first user and the second user in response to the execution of the remittance process by the remittance means.
[0207] (Appendix 1-12) The payment processing device according to Appendix 1-11, characterized in that the granting means grants the benefits to the second user in a value corresponding to the amount of the contribution.
[0208] (Appendix 1-13) The payment processing device according to Appendix 1-11 or 1-12, wherein the payment to be settled is the payment that the first user pays to the first facility when the first user uses any of the first facilities, and the granting means grants the second user a benefit that can be used at a second facility which is different from the first facility but is located within a predetermined range from the first facility.
[0209] (Appendix 1-14) The payment processing device according to any one of Appendix 1-11 to 1-13, wherein the payment to be settled is the payment that the first user pays to a facility when the first user uses any of the facilities, and the granting means grants the second user a benefit that can be used at the facility.
[0210] (Appendix 1-15) The payment processing device according to any one of Appendix 1-11 to 1-14, characterized in that the granting means grants the first user the benefit in a value corresponding to the amount of the price after deducting the amount of the acquired contribution.
[0211] (Appendix 1-16) The payment processing device according to any one of Appendix 1-11 to 1-15, wherein the remittance means performs the process of remitting the payment in predetermined electronic money, and the granting means grants the benefit to the first user if the remittance by the remittance means is the first use of the predetermined electronic money by the second user.
[0212] (Appendix 1-17) The payment processing device according to any one of Appendix 1-1 to 1-16, characterized in that the means for obtaining the amount of the burden is determined to be an amount corresponding to the age of the first user and the age of the second user, respectively, and the means for transmitting the amount of the burden is transmitted to show the amount of the burden determined for the second user by the means for obtaining the amount of the burden.
[0213] (Appendix 1-18) A payment processing device according to any one of Appendix 1-1 to 1-17, further comprising: a second burden amount information transmission means for transmitting second burden amount information indicating the amount of the acquired burden to the first terminal device; and a changed burden amount information acquisition means for acquiring changed burden amount information indicating the changed burden amount in response to the first terminal device receiving an operation to change the amount of the burden indicated by the transmitted second burden amount information, wherein the burden amount information transmission means transmits the acquired changed burden amount information as the burden amount information.
[0214] (Appendix 1-19) A payment processing device according to any one of Appendix 1-1 to 1-18, further comprising: reservation information acquisition means for acquiring reservation information indicating a reservation made by the first user for services available during the trip for the purpose of the trip; determination means for determining, based on the acquired reservation information, whether the first user received the payment request information by the payment request information receiving means during the trip, and whether the trip has ended, the payment amount acquisition means acquires the amount of the payment amount corresponding to the sum of the amounts of the multiple payments to be settled according to the multiple payment request information if the determination means determines that there are multiple payments request information that have been received during the trip; and the payment amount information transmission means transmits the payment amount information indicating the sum of the payment amounts acquired by the payment amount acquisition means according to the sum of the amounts of the payments after the determination means has determined that the trip has ended.
[0215] (Appendix 1-20) A payment method performed by a computer, wherein the payment is made using a first terminal device used by any first user belonging to a group of users, and is characterized by comprising: a payment request information receiving step of receiving payment request information indicating a request for payment of an amount to be paid by the first user; a burden amount acquisition step of obtaining the amount of the burden to be charged to a second user, who belongs to the group but is different from the first user, from the amount to be paid according to the received payment request information; a burden amount information transmission step of transmitting the burden amount information indicating the acquired burden amount to a second terminal device used by the second user; a remittance request information receiving step of receiving remittance request information from the second terminal device indicating a request for remittance in response to the second terminal device accepting a remittance operation after receiving the transmitted burden amount information; and a remittance step of executing a process to remit 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 in that a computer functions as a payment processing device used by any first user belonging to a group of users, comprising: 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; burden amount acquisition means for acquiring the amount of the burden to be charged to a second user, who belongs to the group but is different from the first user, from the amount to be paid according to the received payment request information; burden amount information transmission means for transmitting the burden amount information indicating the acquired burden amount to a second terminal device used by the second user; 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 accepting a remittance operation after receiving the transmitted burden amount information; and remittance means for executing a process to remit 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] (Appendix 2-1) A group identification device characterized by comprising: position relationship information acquisition means for acquiring position relationship information indicating the positional relationship between a first terminal device used by any first user belonging to a group of users and at least one terminal device different from the first terminal device, the position relationship including first position information indicating the position of the first terminal device; and identification means for identifying a user who uses one of the at least one terminal devices, whose positional relationship when the first terminal device is located in any facility is shown to be a predetermined positional relationship based on the acquired position relationship information, as a second user belonging to the group.
[0218] (Appendix 2-2) The group identification device according to 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 time or longer.
[0219] (Appendix 2-3) The group identification device according to Appendix 2-1 or 2-2, characterized in that the identification means identifies the second user from among users of 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.
[0220] (Appendix 2-4) The group identification device according to any one of Appendix 2-1 to 2-3, wherein the acquired positional 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 positional 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 according to Appendix 2-4, characterized in that each of the at least one terminal devices transmits a predetermined signal wirelessly, the communication status information indicates the terminal device that transmitted the predetermined signal that reached the first terminal device, and the identification means identifies the second user from among the users using the terminal device that transmitted the predetermined signal that reached the first terminal device.
[0222] (Appendix 2-6) A group identification device according to any one of Appendix 2-1 to 2-5, further comprising a means for acquiring remittance history information that acquires remittance history information indicating that the first user is either the remittance source or the recipient, and the identification means identifies the second user based on the acquired location relationship information and the acquired remittance history information.
[0223] (Claim 2-7) The group identification device according to Appendix 6, wherein the predetermined positional relationship includes a predetermined first positional relationship and a predetermined second positional relationship different from the first positional relationship, the identifying means identifies a user who uses 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 identifying means identifies a user who uses 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 a fact of remittance between the user and the first user.
[0224] (Appendix 2-8) The group identification device according to any one of Appendix 2-1 to 2-7, characterized in that the predetermined positional relationship is the positional relationship observed when the first user and the second user are using the facility as a group, and is the positional relationship between the first terminal device and the second terminal device used by the second user.
[0225] (Appendix 2-9) A group identification device according to any one of Appendix 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 payable by the first user; a burden amount acquisition means for acquiring the amount of the burden to be charged to the second user from the amount to be paid according to the received payment request information; and a burden amount information transmitting means for transmitting burden amount information indicating the acquired burden amount to a second terminal device used by the second user.
[0226] (Appendix 2-10) The group identification device according to Appendix 2-9, further comprising: a remittance request information receiving means for receiving remittance request information from the second terminal device in response to the second terminal device accepting a remittance operation after receiving the transmitted burden amount information; and a remittance means for executing a process of remitting the burden amount 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) The group identification device according to Appendix 2-9 or 2-10, further comprising: billing information transmission means for transmitting billing information indicating the identified second user to the first terminal device; and edited billing information acquisition means for acquiring edited billing information indicating the second user after editing, in response to the first terminal device receiving 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 transmission 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 performed by a computer, comprising: a position relationship information acquisition step of acquiring position relationship information that indicates the positional relationship between a first terminal device used by any first user belonging to a group of users and at least one terminal device different from the first terminal device, the position relationship of which includes first position information indicating the position of the first terminal device; and an identification step of identifying a user who uses one of the at least one terminal devices, whose positional relationship when the first terminal device is located in any facility is indicated by the acquired position relationship information to be a predetermined positional relationship, as a second user belonging to the group.
[0229] (Appendix 2-13) A group identification program characterized in that it causes a computer to function as a positional relationship information acquisition means for acquiring positional relationship information that indicates the positional relationship between a first terminal device used by any first user belonging to a group of users and at least one terminal device different from the first terminal device, the acquisition means for acquiring positional relationship information that includes first positional information indicating the position of the first terminal device, and a user of one of the at least one terminal device whose positional relationship when the first terminal device is located in any facility is indicated by the acquired positional relationship information to be a predetermined positional relationship, and which is identified as a second user belonging to the group. [Explanation of symbols]
[0230] 1. Electronic payment server 2 User terminals 3. Travel booking server 11 System Control Unit 12 System Bus 13 Input / Output Interfaces 14 Storage section 14a UserDB 14b Facility Database 14c Electronic Money Balance Database 14d Payment History DB 14e Remittance History Database 14f Location information DB 14g Inter-terminal communication status database 14h Issued Coupon Database 14i Split Payment Hold Settlement DB 15 Communications Department 3a Accommodation Reservation Database 3b Transportation ticket reservation database 1101 Positional relationship information acquisition unit 1102 Group Specialized Department 1103 Payment Request Receiving Unit 1104 Payment Department 1105 Billing Information Transmission Department 1106 Editorial Request Information Acquisition Department 1107 Department for obtaining the amount of the burden 1108 Provisional burden amount information transmission section 1109 Change Burden Amount Information Acquisition Unit 1110 Unit for transmitting information on the amount of the burden 1111 Remittance Request Receiving Unit 1112 Remittance Department 1113 Special Offer 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. Position relationship information acquisition means for acquiring position relationship information that indicates the positional relationship between a first terminal device of a first user that settles a payment and at least one terminal device different from the first terminal device, the position relationship information including first position information indicating the position of the first terminal device. Based on the acquired positional relationship information, a means for identifying a user using a terminal device whose positional relationship is indicated to be a predetermined positional relationship as a second user belonging to the same group as the first user, When the payment of the aforementioned amount is completed, the first terminal device is provided with a screen display control means that automatically displays a screen on the first terminal device that allows the user to select whether or not to split the payment of the aforementioned amount. After the option to split the cost is selected on the screen displayed on the first terminal device, a means for transmitting burden amount information indicating the amount of the burden to be charged to the identified second user is transmitted to the second terminal device of the second user. A remittance request information receiving means that receives remittance request information indicating a request for remittance from the second terminal device that received the transmitted burden amount information, A remittance means that, upon receiving the remittance request information by the remittance request information receiving means, executes a process to remit the payment from the second user to the first user, Equipped with, The identifying means identifies the user of a terminal device whose positional relationship with the first terminal device when the first terminal device is located in any facility is the predetermined positional relationship, and whose positional relationship with the first terminal device when the first terminal device is located outside the facility is the predetermined positional relationship, as the second user, and does not identify the user of a terminal device whose positional relationship with the first terminal device when the first terminal device is located in the facility is the predetermined positional relationship, but whose positional relationship with the first terminal device when the first terminal device is located outside the facility is not the predetermined positional relationship, as the second user.
2. The payment processing device according to claim 1, further comprising a specific user screen display control means for causing the first terminal device to display a specific user screen indicating the identified second user when the option to split the payment is selected on the screen displayed on the first terminal device.
3. The system further includes a means for determining the amount of the burden, which automatically determines the amount of the burden based on the amount of the payment that has been settled. The payment processing device according to claim 1 or 2, characterized in that the means for transmitting the amount of the amount of the burden transmits the amount of the burden indicating the determined amount.
4. After selecting to split the cost on the screen displayed on the first terminal device, the system further includes a burden amount screen display control means that causes the first terminal device to display a burden amount screen showing the determined amount of the burden, which allows the user to change the amount of the burden. The payment processing device according to claim 3, wherein the burden amount information transmission means transmits the burden amount information indicating the amount of the burden after it has been changed on the burden amount screen displayed by the first terminal device.
5. The system further includes designated burden amount information receiving means for receiving designated burden amount information indicating the amount specified by the first user as the amount of the burden after the option to split the cost is selected on the screen displayed on the first terminal device, The payment processing device according to claim 1 or 2, wherein the means for transmitting the amount of
6. The payment processing device according to claim 1 or 2, further comprising granting means for performing a process of granting benefits to the first user, on the condition that the remittance means has performed a remittance process from the second user to the first user.
7. After the specific user screen is displayed by the first terminal device, the system further comprises a billing information receiving means that receives from the first terminal device billing information indicating the second user designated by the first user among the second users shown on the specific user screen, The payment processing device according to claim 2, characterized in that the means for transmitting the amount of burden information transmits the amount of burden information to the second terminal device of the second user indicated by the received billing information.
8. The payment processing device according to claim 1 or 2, wherein the identifying 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 time or longer.
9. The acquired positional 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 devices, The payment processing device according to claim 1 or 2, characterized in that the identifying means identifies the positional relationship between the first terminal device and each of the at least one terminal devices based on the communication status information.
10. Each of the at least one terminal device transmits a predetermined signal wirelessly, The aforementioned communication status information indicates the terminal device that transmitted the predetermined signal that reached the first terminal device, The payment processing device according to claim 9, characterized in that the identifying means identifies the second user from among the users using the terminal device who have transmitted the predetermined signal that has reached the first terminal device.
11. A remittance history that can identify the users of the remittance source and the remittance recipient, further comprising remittance history information acquisition means for acquiring remittance history information indicating that the first user is either the remittance source or the remittance recipient, The payment processing device according to claim 1 or 2, characterized in that the identifying means identifies the second user based on the acquired location relationship information and the acquired remittance history information.
12. A payment method performed by a computer, A positional relationship information acquisition step involves acquiring positional relationship information that indicates the positional relationship between a first terminal device of a first user that settles a payment 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. Based on the acquired positional relationship information, the user using the terminal device whose positional relationship is indicated to be a predetermined positional relationship is identified as a second user belonging to the same group as the first user; When the payment of the aforementioned amount is completed, a screen display control step is performed to automatically display a screen on the first terminal device that allows the user to select whether or not to split the payment of the aforementioned amount. After selecting to split the cost on the screen displayed on the first terminal device, a burden amount information transmission step is performed, in which burden amount information indicating the amount of the burden to be charged to the identified second user is transmitted to the second terminal device of the second user. A remittance request information receiving step, receiving remittance request information indicating a request for remittance from the second terminal device that received the transmitted burden amount information, A remittance step is performed in response to the receipt of the remittance request information in the remittance request information receiving step, which involves performing a process to remit the payment from the second user to the first user. Includes, The payment processing method is characterized in that the identification step identifies the user of a terminal device whose positional relationship with the first terminal device when the first terminal device is located in any facility is the predetermined positional relationship, and whose positional relationship with the first terminal device when the first terminal device is located outside the facility is the predetermined positional relationship, as the second user, and does not identify the user of a terminal device whose positional relationship with the first terminal device when the first terminal device is located in the facility is the predetermined positional relationship, but whose positional relationship with the first terminal device when the first terminal device is located outside the facility is not the predetermined positional relationship, as the second user.
13. A computer, Position relationship information acquisition means for acquiring position relationship information that indicates the positional relationship between a first terminal device of a first user that settles the payment and at least one terminal device different from the first terminal device, the position relationship information including first position information indicating the position of the first terminal device, Based on the acquired positional relationship information, a means for identifying a user using a terminal device whose positional relationship is indicated to be a predetermined positional relationship as a second user belonging to the same group as the first user, When the payment of the aforementioned amount is completed, the first terminal device is provided with a screen display control means that automatically displays a screen on the first terminal device that allows the user to select whether or not to split the payment of the aforementioned amount. After the option to split the cost is selected on the screen displayed on the first terminal device, a means for transmitting burden amount information indicating the amount of the burden to be charged to the identified second user is transmitted to the second terminal device of the second user. A remittance request information receiving means that receives remittance request information indicating a request for remittance from the second terminal device that received the transmitted burden amount information, A remittance means that, upon receiving the remittance request information by the remittance request information receiving means, executes the process of sending the payment from the second user to the first user. To make it function as, The identifying means is characterized in that, among terminal devices whose positional relationship with the first terminal device when the first terminal device is located in any facility is the predetermined positional relationship, the user of a terminal device whose positional relationship with the first terminal device when the first terminal device is located outside the facility is the predetermined positional relationship is identified as the second user, and the user of a terminal device whose positional relationship with the first terminal device when the first terminal device is located in the facility is the predetermined positional relationship, but whose positional relationship with the first terminal device when the first terminal device is located outside the facility is not the predetermined positional relationship is identified as the second user.