TWI891272B - Payment processing system, payment processing method, and payment processing program - Google Patents

Abstract

[Topic] When multiple users pay for a fee, users can first be informed of the amount to be paid to other users before making a payment. [Solution] A payment processing device receives payment request information indicating a payment request from a first terminal device used by a first user belonging to a user group. The payment processing device obtains the amount of the share to be charged to a second user belonging to the group for the fee paid in response to the payment request information. The payment processing device then transmits payment amount information indicating the amount of the share to a second terminal device used by the second user. In response to the second terminal device, which has received the payment amount information, accepting the payment request, the payment processing device receives remittance request information indicating a remittance request from the second terminal device. In response to receiving the remittance request information, the payment processing device executes a remittance process to transfer the payment amount from the second user to the first user.

Description

Payment processing device, payment processing method, and payment processing program

The present invention relates to a method for providing support for payment by multiple users.

When a group uses a facility or purchases something, the group sometimes pays for the cost through a split payment or other means. Technologies for supporting such payments are already known.

For example, Patent Document 1 discloses a technology for distributing payments across multiple checkouts performed by multiple users using portable terminals. In this technology, user A pre-configures a group consisting of user A and user B. When user A performs a checkout, user A's terminal sends checkout information to a server, which calculates the payout and share for the group. Similarly, when user B performs a checkout, user B's terminal also sends checkout information to the server, which similarly calculates the payout and share. In response to a request from User A for a split payment, the server calculates each user's total expenditure and the split total, and sends a notification to User B's terminal indicating the split payment is about to be made. User B's terminal displays a screen indicating the split payment is about to be made. Once User B approves the split payment, the server calculates the offset amount for each user and transfers funds between the group users based on the offset amount.

[Prior Art Literature] [Patent Literature]

[Patent Document 1] Japanese Patent Application Laid-Open No. 2020-166365

However, if a user wishes to transfer funds to another user within the group, there's no way to know whether the transfer will actually proceed until the transfer is actually executed. As a user, there are situations where you might want to know the amount you owe to another user before you make the transfer.

The present invention was developed in light of the above considerations. One example of its subject matter is to provide a payment processing device, payment processing method, and payment processing program that, when multiple users are paying for a fee, allows each user to first know the amount to be paid to other users and then choose to transfer the funds.

In order to solve the above-mentioned problem, the invention described in claim 1 is characterized by comprising: a billing request information receiving means for receiving billing request information, which indicates a billing request for a charge to be paid by the first user using a first terminal device used by any first user belonging to a user group; and a share amount obtaining means for obtaining: an amount of share to be charged to a second user belonging to the first user and being different from the first user, of the previous charge settled in response to the previously received billing request information; and a share amount obtaining means. The amount information transmitting means is used to transmit the amount information indicating the amount of the previously acquired liability to the second terminal device used by the previously mentioned second user; the remittance request information receiving means is used to receive remittance request information indicating a remittance request from the previously mentioned second terminal device in response to the previously mentioned second terminal device accepting the remittance operation after receiving the previously transmitted amount information; and the remittance means is used to execute a remittance process of the previously mentioned liability from the previously mentioned second user to the previously mentioned first user in response to the previously mentioned remittance request information being received by the previously mentioned remittance request information receiving means.

According to this invention, charges are settled using the first terminal device of a first user belonging to a group. This means that the first user pays the charges first. Subsequently, the amount of the charge that a second user belonging to the group must pay is sent to the second terminal device used by the second user. This allows the second user to know the amount of the charge. The second user then operates the second terminal device, and the amount of the charge is transferred from the second user to the first user. Therefore, when multiple users pay for a charge, each user can first know the amount to be paid to the other users and then choose to transfer the funds.

The invention described in claim 2 is characterized in that the previously recorded fee settled in response to the previously received billing request information is a fee paid for a certain facility; and further comprises: a position relationship information acquisition means for acquiring position relationship information, which is used to obtain position relationship information representing the position relationship between the previously recorded first terminal device and at least one terminal device different from the previously recorded first terminal device, and the previously recorded position relationship information The information includes first location information indicating the location of the aforementioned first terminal device; and identifying means for identifying, among at least one of the aforementioned terminal devices, a user of the terminal device whose aforementioned location relationship, based on the previously acquired location relationship information, is indicated as exhibiting the predetermined location relationship when the aforementioned first terminal device is located within the aforementioned facility, as a previously mentioned second user belonging to the aforementioned group.

According to this invention, location relationship information indicating the location relationship between a first terminal device and other terminal devices is acquired. The location relationship between the terminal devices may be the location relationship between the users utilizing those terminal devices. A user whose location relationship with the first user exhibits the specified location relationship while the first user is at the facility for which the charges are to be paid is then identified as a second user belonging to the same group as the first user. Since the first and second users exhibiting the specified location relationship may be utilizing the facility together, it may be appropriate for the second user to bear at least a portion of the charges paid by the first user. Therefore, even if the user has not set a group, users belonging to the group utilizing the facility can be identified.

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

According to this invention, if a first user is present in a facility for a predetermined period of time or longer, a second user belonging to the same group as the first user can be identified. Sometimes, in order to use a facility, a user must be present for a certain period of time. Therefore, situations where the first user is likely to be using the facility can be identified, and second users who are likely to be using the facility together with the first user can be identified.

The invention recited in claim 4 is characterized in that the aforementioned identifying means identifies the aforementioned second user from among users of the terminal devices whose aforementioned positional relationship with the aforementioned first terminal device when the aforementioned first terminal device is located outside the aforementioned facility.

According to this invention, even if the first user's locational relationship with the user exhibits a predetermined locational relationship while inside the facility, the first user's locational relationship with the user outside the facility is not such that the second user is identified as belonging to the same group as the first user. Therefore, a user who happens to be with the first user inside the facility but does not travel with the first user outside the facility can be excluded from the second user belonging to the same group as the first user.

The invention recited in claim 5 is characterized in that the acquired location relationship information further includes communication status information indicating the status of wireless communication between the first terminal device and each of the at least one terminal devices; and the identifying means identifies the location relationship between the first terminal device and each of the at least one terminal devices based on the communication status information.

According to this invention, the locational relationships between terminal devices can be identified based on the status of wireless communication between these terminal devices. For example, the reception of a signal wirelessly transmitted from one terminal device by other terminal devices may be affected by the locational relationships between these terminal devices. Therefore, the locational relationships between users can be accurately identified.

The invention recited in claim 6 is characterized in that each of the aforementioned at least one terminal device transmits a predetermined signal wirelessly; the aforementioned communication status information indicates the terminal device from which the predetermined signal was transmitted before reaching the aforementioned first terminal device; and the aforementioned identifying means identifies the aforementioned second user from among users of the aforementioned terminal device from which the predetermined signal was transmitted before reaching the aforementioned first terminal device.

According to this invention, each terminal device wirelessly transmits a predetermined signal. Among the users of these terminal devices whose transmitted predetermined signal has reached the first terminal device, a second user belonging to the same group as the first user is identified. The location relationship between users within the reach of the predetermined signal is highly likely to indicate that these users tend to move around as a group. Therefore, the second user who utilizes the facility with the first user can be accurately identified.

The invention recited in claim 7 is characterized by further comprising: remittance history information acquisition means for acquiring remittance history information representing remittance history that can identify each user of a remittance source and a remittance destination, wherein the aforementioned first user is the remittance history of either the aforementioned remittance source or the aforementioned remittance destination; and aforementioned identifying means for identifying the aforementioned second user based on the aforementioned location relationship information and the aforementioned remittance history information.

According to this invention, remittance history information indicating the history of remittances between users can be used to identify a second user who belongs to the same group as the first user. The user who remitted money to the first user is likely to have been traveling with the first user. Therefore, the second user who used the facility with the first user can be accurately identified.

The invention described in claim 8 is a payment device described in claim 7, characterized in that the positional relationship described in the preceding paragraph includes: a predetermined first positional relationship, and a predetermined second positional relationship different from the predetermined first positional relationship; and the predetermined specific means described in the preceding paragraph is to cause a user of a terminal device whose positional relationship with the predetermined first terminal device is such that the terminal device presents the predetermined first positional relationship and also presents the predetermined second positional relationship. , specifically identified as the aforementioned second user belonging to the aforementioned group; the aforementioned identifying means is to identify the user as the aforementioned second user belonging to the aforementioned group only if the location relationship between the user and the aforementioned first terminal device is such that there is a fact of money transfer between the user who uses the terminal device of either the aforementioned first location relationship or the aforementioned second location relationship and the aforementioned first user.

According to this invention, a user who meets at least two location-related conditions is identified as a second user belonging to the same group as the first user. On the other hand, a user who meets only one of these conditions may still be a second user belonging to the same group as the first user. Therefore, if such a user transfers money with the first user, that user is identified as the second user. This allows for the precise identification of a second user who utilizes a facility with the first user.

The invention described in claim 9 is characterized in that it further comprises: a means for sending payment object information, which is used to send the payment object information indicating the second user specified in the previous record to the first terminal device of the previous record; and a means for obtaining the payment object information after editing, which is used to edit the payment object information sent by the previous record and indicated by the second user of the previous record in response to the first terminal device of the previous record accepting the operation of the second user of the previous record. The previously recorded payment target information of the second user is obtained; the previously recorded liability amount obtaining means obtains the previously recorded liability amount for the previously recorded second user indicated by the previously recorded payment target information; and the previously recorded liability amount information transmitting means transmits the previously recorded liability amount information to the previously recorded second terminal device used by the previously recorded second user indicated by the previously recorded payment target information.

According to this invention, a user identified by a payment device as a second user belonging to the same group as the first user can be edited by the first user. For example, the second user may be added or deleted.

The invention recited in claim 10 is characterized in that the aforementioned positional relationship is a positional relationship that is visible only when the aforementioned first user and the aforementioned second user utilize the facility as a group, and is a positional relationship between the aforementioned first terminal device and the aforementioned second terminal device.

The invention described in claim 11 is characterized by further comprising: a granting means for granting a gift to at least one of the first user and the second user in response to the aforementioned remittance processing having been performed by the aforementioned remittance means.

According to this invention, once the burden is transferred from the second user to the first user, a gift is given to at least one of the first and second users. This can encourage users to transfer the funds required for the shared payment.

The invention described in claim 12 is characterized in that the means for granting the pre-credit is to grant the pre-credit gift of a value corresponding to the amount of the pre-credit contribution to the second user.

According to this invention, the higher the amount of money the second user bears, the more likely it is that the second user will be encouraged to make a remittance.

The invention set forth in claim 13 is characterized in that the charges charged are charges paid by the first user for the first facility when the first user utilizes any of the first facilities; and the granting means grants the second user a gift of the right to use a second facility, other than the first facility, that is located within a predetermined range from the first facility.

This invention provides a gift of access to a second facility within a specified range from the first facility used by a group. Since the group is located in the first facility, it is easily accessible to the second facility. This can promote the use of the second facility.

The invention described in claim 14 is characterized in that the charges charged are fees paid by the first user for the facilities mentioned above when the first user uses any of the facilities mentioned above, and the granting means mentioned above grants the second user a gift of the right to use the facilities mentioned above.

If this invention is made, the reuse of facilities can be promoted.

The invention described in claim 15 is characterized in that the means for granting the credit is to grant the first user a credit gift corresponding to the amount of the credit after deducting the amount of the credit already acquired.

According to this invention, the higher the amount of money the first user bears, the more likely it is that the first user will be able to make the necessary remittances to split the payment.

The invention described in claim 16 is characterized in that the pre-credit remittance means performs a pre-credit processing to remit the pre-credit liability in a specified electronic currency; and the pre-credit granting means grants a pre-credit gift to the first user if the pre-credit remittance resulting from the pre-credit remittance means is the first use of the specified electronic currency by the second user.

According to this invention, if a second user who has never used a given electronic currency uses the given electronic currency for the first time in a remittance from the second user to the first user, a gift will be given to the first user. Therefore, by facilitating settlements that allow the first user to make remittances required for split payments, the use of the given electronic currency can be promoted.

The invention described in claim 17 is characterized in that the means for obtaining the amount of the previous contribution is configured to determine the amount of the contribution of the first user and the amount of the contribution of the second user as amounts corresponding to the ages of the first user and the second user, respectively; and the means for transmitting information on the amount of the previous contribution is configured to transmit information on the amount of the previous contribution, indicating the amount of the previous contribution determined for the second user by the means for obtaining the amount of the previous contribution.

According to this invention, the older the user, the higher the payment. Therefore, each user can be required to pay an amount corresponding to their age.

The invention described in claim 18 is characterized by further comprising: a second burden amount information transmission means for transmitting the second burden amount information indicating the amount of the burden obtained in the foregoing to the foregoing first terminal device; and a burden amount change information acquisition means for receiving the burden amount information change in response to the foregoing first terminal device accepting the burden amount information change. The previously transmitted second liability amount information is used to represent the previously transmitted liability amount, and the changed liability amount information representing the previously transmitted liability amount after the previous record is changed is obtained. The previously transmitted liability amount information transmitting means transmits the previously transmitted changed liability amount information as the previously transmitted liability amount information.

According to this invention, the payment amount received by the payment device can be changed based on the first user's judgment.

The invention described in claim 19 is characterized in that it further comprises: reservation information acquisition means for acquiring reservation information, which indicates the reservation made by the first user for the service that can be used in the trip; and determination means for determining, based on the reservation information acquired in the previous record, whether the first user has received the previous settlement request information during the previous trip through the previous settlement request information receiving means, and whether the previous trip has ended; and means for acquiring the amount of the previous payment after the previous determination means has received the previous settlement request information. If multiple pre-credit settlement request information has been received for a pre-credited trip, the pre-credit liability amount corresponding to the total of the multiple pre-credit charges settled in response to the multiple settlement request information is obtained. The pre-credit liability amount information transmission means transmits pre-credit liability amount information indicating the total of the pre-credit liability amounts obtained by the pre-credit liability amount acquisition means in response to the total of the pre-credit charges after the pre-credit determination means determines that the pre-credited trip has been completed.

According to this invention, based on reservation information for travel services, it is possible to determine whether a payment made using the first terminal was made during the first user's trip and whether the first user's trip has concluded. If a payment is made during the first user's trip, the remittance processing required for the split payment is not performed at that time. After the trip concludes, the multiple payments made during the trip are aggregated and the remittance processing required for the split payment is performed. Therefore, the group to which the first user belongs can aggregate the expenses paid by the first user during the trip and convert them into split payments after the trip.

The invention described in claim 20 is a payment method executed by a computer, characterized by comprising: a billing request information receiving step for receiving billing request information indicating a billing request for a charge to be paid by the first user using a first terminal device used by any first user belonging to a user group; and a share amount obtaining step for obtaining the share amount to be charged to a second user belonging to the first user, who is different from the first user, out of the previously recorded charges that were settled in response to the previously received billing request information. to obtain; and the burden amount information sending step is to send the burden amount information indicating the amount of the burden obtained in the previous record to the second terminal device used by the second user in the previous record; and the remittance request information receiving step is to receive the burden amount information sent in the previous record in response to the second terminal device in the previous record. The device accepts the remittance operation and receives remittance request information indicating a remittance request from the aforementioned second terminal device; and the remittance step, in response to the aforementioned remittance request information being received by the aforementioned remittance request information receiving step, executes a process for remitting the aforementioned balance from the aforementioned second user to the aforementioned first user.

The invention of claim 21 is characterized by causing a computer to function as: billing request information receiving means for receiving billing request information indicating a billing request for a charge to be paid by the first user using a first terminal device utilized by a first user belonging to a user group; and share amount obtaining means for obtaining the share amount to be charged to a second user belonging to the first user group, who is different from the first user, for the charge settled in response to the received billing request information; and share amount obtaining means for obtaining the share amount to be charged to a second user belonging to the first user group, who is different from the first user, for the charge settled in response to the received billing request information. The amount information transmitting means is used to transmit the amount information indicating the amount of the previously acquired liability to the second terminal device used by the previously mentioned second user; the remittance request information receiving means is used to receive remittance request information indicating a remittance request from the previously mentioned second terminal device in response to the previously mentioned second terminal device accepting the remittance operation after receiving the previously transmitted amount information; and the remittance means is used to execute a remittance process of the previously mentioned liability from the previously mentioned second user to the previously mentioned first user in response to the previously mentioned remittance request information being received by the previously mentioned remittance request information receiving means.

According to the present invention, when multiple users pay for a fee, each user can first know the amount to be paid to other users and then choose to transfer the money.

1: Electronic checkout server

2: User terminal

3: Travel Reservation Server

3a: Accommodation Reservation DB

3b: Transportation Ticket Reservation Database

11: System Control Department

11a:CPU

11b:ROM

11c: RAM

12: System bus

13: Input/Output Interface

14: Memory

14a: User DB

14b: Facilities DB

14c: Electronic Currency Balance DB

14d: Checkout History DB

14e: Remittance History DB

14f: Location Information DB

14g: Inter-terminal communication status DB

14h: Coupon DB issued

14i: Split Payment Reserve Checkout DB

15: Communications Department

110:Restaurant

111: Inner Wall

113: Hotel

120:Restaurant

210: Checkout completion screen

211: Shared payment information

212: Approval button

213: Deny button

220: Edit payment recipient screen

221: Reimbursement recipient information

222:Add button

223: Next button

224: Delete button

230: Payable amount edit screen

231: Responsible for user information

232:Amount input field

233: Increase button

234:Decrease button

235: Return button

236: Confirm button

240: Checkout edit screen

241: Checkout Information

242: Delete button

243: Approval button

244: Non-approved button

310: Payment request screen

311: Checkout Information

312: Information on the amount of money owed

313: Transfer button

314: Top-up button

315: Non-remittance button

316:Total amount

1101: Location-related information acquisition unit

1102: Group Specific Department

1103: Checkout request to the receiving department

1104: Checkout Department

1105: Information about the recipient of the payment is sent to the Information Department

1106: Editing the payment recipient information acquisition department

1107: Payment Amount Acquisition Department

1108: Provisional payment amount information sent to the Information Department

1109: Change of burden amount information acquisition department

1110: Information on the amount of payment sent to the Information Department

1111: Remittance Request Receiving Department

1112: Remittance Department

1113: Gift Giving Department

1114: Remittance History Acquisition Department

1115: Reservation Information Acquisition Department

1116: Travel Assessment Department

1117: Checkout Information Delivery Department

NW: Network

R1~R5: Notification signal exists

S: Communication system

U1~U5: Users

[Figure 1] An example of the schematic configuration of a communication system S according to one embodiment.

[Figure 2] A block diagram showing an example of the schematic configuration of the electronic checkout server 1 according to one embodiment.

[Figure 3] An example of information stored in the database of electronic checkout server 1.

[Figure 4] An example diagram of the functional blocks of the system control unit 11 in the electronic checkout server 1.

[Figure 5] An example of information sent from the user terminal 2 to the electronic checkout server 1.

[Figure 6] Illustration of a specific example of a group.

[Figure 7] Illustration of a specific example of a group.

[Figure 8] An example of a checkout completion screen 210.

[Figure 9] An example of the payment request object editing screen 220.

[Figure 10] An example of the burden amount editing screen 230.

[Figure 11] An example of a payment request screen 310.

[Figure 12] A flowchart of a processing example of the communication system S in one embodiment.

[Figure 13] An example diagram of the functional blocks of the system control unit 11 in the electronic checkout server 1.

[Figure 14] (a) is an example of a group. (b) is an example of a checkout log.

[Figure 15] A diagram showing an example of the schematic configuration of a communication system S according to one embodiment.

[Figure 16] An example of information stored in the database of the travel reservation server 3.

[Figure 17] A block diagram showing an example of the schematic configuration of the electronic checkout server 1 according to one embodiment.

[Figure 18] An example of information stored in the split payment retention checkout DB14i.

[Figure 19] An example diagram of the functional blocks of the system control unit 11 in the electronic checkout server 1.

[Figure 20] (a) is an example of accommodation facility reservation information stored in the accommodation facility reservation DB3a. (b) is an example of transportation facility reservation information stored in the transportation facility ticket reservation DB3b. (c) is an example of the actions of a traveling group.

[Figure 21] An example of a checkout edit screen 240.

[Figure 22] An example of a payment request screen 310.

The following describes the implementation of the present invention in detail with reference to the drawings.

[1. First Implementation Form]

[1-1. Communication system structure]

First, the structure and functions of the communication system S described in the first embodiment will be described with reference to Figure 1 . Figure 1 illustrates an example of the schematic structure of the communication system S described in this embodiment. As shown in Figure 1 , the communication system S comprises an electronic billing server 1 and a plurality of user terminals 2. The electronic billing server 1 and each user terminal 2 are connected to a network NW. The network NW is composed of, for example, the Internet, dedicated communication lines (such as CATV (Community Antenna Television) lines), a mobile communication network (including base stations), and gateways.

The electronic billing server 1 may also be a server device that performs various processes related to billing expenses using a predetermined electronic billing application. The electronic billing application is an application that can be executed by each user terminal 2 and may also be an application that enables electronic billing of expenses using the user terminal 2. In response to a billing operation using the user terminal 2, the electronic billing server 1 may receive a billing request from the user terminal 2, a POS (Point of Sales) system, or other system. The electronic billing server 1 may also perform electronic billing processing in response to the billing request.

Examples of payment methods that can be used in electronic payment include designated electronic currencies and credit cards. Services required to use designated electronic currencies may also be provided by, for example, a company that provides electronic payment services using an electronic payment application or its affiliated companies. For convenience, this designated electronic currency will be referred to as R electronic currency.

Furthermore, the electronic payment server 1 can also perform remittances between users. For example, remittances can be made using the electronic payment application using R electronic currency.

The electronic checkout server 1 can also identify a group consisting of a plurality of users each possessing a user terminal 2. The identified group may be, for example, a group of users presumed to be acting together.

If the user who pays for a fee using the electronic billing application is a member of the aforementioned group, the electronic billing server 1 can also perform the necessary processing to have other members pay a portion of the fee using a split payment method. Split payment in this embodiment can include both equal payment by all members and unequal payment based on individual member-specified contributions. The combined actions of multiple users result in the payment of certain fees. Therefore, it can be assumed that the fees are shared and paid by these users. Here, it is assumed that the member of the group who pays for the fee using the electronic billing application is the representative. The electronic billing server 1 can also calculate the amount of each member's contribution based on, for example, already paid expenses. The electronic billing server 1 can also send contribution amount information indicating the contribution amount to the user terminal 2 of each member other than the representative. The user terminal 2 can also display the contribution amount information. The user confirms the contribution amount and then performs the necessary operations to transfer the contribution to the representative. In response to this operation, the electronic billing server 1 can also execute a remittance process from other members to the representative using R electronic currency.

When processing remittances from group members, the electronic billing management server 1 may also process gifts to at least one of the representative and the member who made the remittance. Examples of gifts include R electronic currency (cash rewards), coupons, and points redeemable in a point program. Coupons may also be discount coupons, coupons, or free coupons. These coupons can be used, for example, at certain facilities or on certain websites. In addition to remittances using R electronic currency, each member may also pay the representative a contribution in cash. By offering gifts in conjunction with remittances, we can promote the use of R electronic currency.

Each user terminal 2 may be a portable terminal device owned by a user who can utilize the above-mentioned electronic payment service. Examples of user terminals 2 include portable information terminals such as smartphones and tablet computers, mobile phones, PDAs (Personal Digital Assistants), wearable computers, etc. Each user terminal 2 may also be installed with an electronic payment application. An example of payment using an electronic payment application is to display code information encoded with information used to identify the user paying the fee on the screen of the user terminal 2. Examples of code information include 1D barcodes, 2D codes (such as QR codes (registered trademarks)), etc. An employee of the facility to which the fee is paid, for example, displays code information displayed on a screen to a POS register. The POS register can also transmit a checkout request to the electronic checkout server 1 via the POS system. Another example of checkout using an electronic checkout application is to have a user terminal 2 read coded information encoded with information about the transaction partner provided by the facility as consideration for the fee. The information about the transaction partner can include, for example, information identifying the facility, information identifying the transaction partner, and the fee amount. The coded information can also be displayed on a display within the facility or printed on paper. After reading the code information, user terminal 2 can also send a checkout request to electronic checkout server 1 based on the user's operation.

Each user terminal 2 may also have a function for obtaining its location information. For example, the user terminal 2 may use a satellite positioning system such as the GPS (Global Positioning System) to calculate longitude and latitude as location information. Alternatively, a mobile communications operator may provide the user terminal 2 with the location information of previously used base stations. Furthermore, each user terminal 2 may also communicate wirelessly with other user terminals 2 using short-range wireless communication. Examples of standards for short-range wireless communication include Bluetooth (registered trademark) and ZigBee (registered trademark). Examples of the upper limit of the distance over which communication can be conducted using near-field wireless communication include several meters, tens of meters, or several dozen meters. Each user terminal 2 may also periodically or constantly transmit a presence notification signal using near-field wireless communication. The presence notification signal may also be a signal indicating that the user terminal 2 transmitting the presence notification signal is nearby, or that a user utilizing the user terminal 2 is nearby. The presence notification signal may also include, for example, information used to identify the user.

[1-2. Electronic checkout server configuration]

Next, the structure of the electronic checkout server 1 will be described with reference to Figures 2 and 3. Figure 2 is a block diagram showing an example of the schematic structure of the electronic checkout server 1 according to this embodiment. As shown in Figure 2, the electronic checkout server 1 includes a system control unit 11, a system bus 12, an input/output interface 13, a memory 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.

The system control unit 11 is composed of a CPU (Central Processing Unit) 11a, a ROM (Read Only Memory) 11b, and a RAM (Random Access Memory) 11c.

The input/output interface 13 performs interface processing between the memory unit 14 and the communication unit 15 and the system control unit 11.

The memory unit 14 is comprised of, for example, a hard drive. The memory unit 14 may also store databases such as a user database 14a, a facility database 14b, an electronic currency balance database 14c, a payment history database 14d, a remittance history database 14e, a location information database 14f, an inter-terminal communication status database 14g, and an issued coupon database 14h. "DB" is an abbreviation for database. Furthermore, at least one database may be stored in a device separate from the electronic payment server 1. The electronic payment server 1 may also access the database through the device.

Figure 3 illustrates an example of information stored in the database of the electronic billing server 1. User information regarding each user who can utilize the electronic billing service may also be stored in the user DB 14a. For example, in the electronic billing server 1, user ID, name, gender, date of birth, address, telephone number, and email address may be associated with each other and stored as user information. The user ID is identification information used to identify the user.

Facility DB 14b may also store facility information for each facility that allows users to pay for items using an electronic checkout application. Each facility provides a transaction object. A transaction object can be at least one of a product and a service. Users can purchase the goods or services provided by the facility by visiting the facility. Facility DB 14b may also store information such as the facility ID, category information, facility name, address, and facility location information in association with each other as facility information. The facility ID is identification information used to identify the facility. Category information indicates the category to which the facility belongs. Examples of facility types include restaurants, cafes, fast food restaurants, other food establishments, drive-ins, rest stops, service areas, amusement parks, aquariums, museums, gift shops, concert venues, stadiums, gas stations, car rental shops, convenience stores, supermarkets, department stores, other small businesses, accommodations, train stations, airports, and ticket sales locations at other transportation agencies. Facility location information may also be information indicating the coordinates of the facility's location. For example, facility location information may represent the locations of the vertices that constitute the outer edge of the facility's footprint, expressed in latitude and longitude.

The electronic currency balance DB 14c may also store each user's R electronic currency balance. For example, the electronic currency balance DB 14c may associate the user ID and balance for each user.

The payment history DB 14d may also store records of charges made using electronic payment applications. For example, the transaction number, payment date and time, user ID, payment method information, payment recipient information, and payment amount may be associated with each payment and stored as a payment log. The transaction number is identification information used to identify the payment. The payment date and time indicates the date and time of the payment. The user ID identifies the user who paid the charge. The payment method information indicates the payment method used for the payment. The facility ID indicates the payment recipient for the charge. If the user paid for a specific facility, the payment recipient information may also be the facility ID of that facility. The billing amount represents the amount of the charges being billed.

The remittance history DB14e may also store a history of remittances between users using the R electronic currency. For example, the remittance history DB14e may store, for each remittance, the remittance number, the source user ID, the destination user ID, and the remittance amount, in association with each other, as a remittance log. The transaction number is identification information used to identify the transaction. The remittance number is identification information used to identify the remittance. The source user ID is the user ID of the user who made the remittance. The destination user ID is the user ID of the user who received the remittance. The remittance amount indicates the amount of the remittance.

The location information DB 14f may also store location information indicating the location of each user terminal 2. Each user terminal 2 may periodically obtain location information, for example, in accordance with an electronic billing application, and transmit it to the electronic billing server 1. The electronic billing management server 1 may also store the location information received from the user terminal 2 in the location information DB 14f. In the location information DB 14f, for example, the user ID, recording date and time, and coordinate information may be associated and stored as location information. The user ID indicates the user of 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 also be the location of the user terminal 2 at the time of the recording date, expressed in longitude and latitude.

The inter-terminal communication status DB 14g may also store inter-terminal communication status information indicating the status of communication between each user terminal 2 and other user terminals 2 using near-field wireless communication. Each user terminal 2 may also periodically obtain inter-terminal communication status information, for example, in accordance with an electronic billing application, and transmit it to the electronic billing server 1. For example, each user terminal 2 may transmit location information along with the inter-terminal communication status information. The electronic billing management server 1 may also store the inter-terminal communication status information received from the user terminal 2 in the inter-terminal communication status DB 14g. In the inter-terminal communication status DB 14g, for example, user IDs, recording dates and times, and a list of signal reception sources can be associated with each other and stored as inter-terminal communication status information. The user ID indicates the user of user terminal 2 that sent the inter-terminal communication status information. The recording date and time indicates the date and time when the inter-terminal communication status information was recorded by user terminal 2. The list of signal reception sources can also be a list of user IDs of users of user terminal 2 that sent the presence notification signal received by user terminal 2 at the recording date and time. Furthermore, the signal reception source list may also include the strength of the presence notification signal received by the user terminal 2 at the recorded date and time, associated with each user ID. As previously mentioned, the presence notification signal includes identification information of the user terminal 2 that sent the presence notification signal. User terminal 2 may also generate a signal reception source list containing the identification information contained in each received presence notification signal and transmit inter-terminal communication status information to the electronic billing server 1. The identification information contained in the presence notification signal may also be the user ID. Alternatively, the identification information may be, for example, a hash of the user ID or other information that can be used to identify the user. The electronic checkout server 1 can also convert the identification information contained in the signal receiving source list of the inter-terminal communication status information received from the user terminal 2 into a user ID.

Issued coupon information about each coupon that has been granted to a user may also be stored in the issued coupon DB14h. By using the coupon, the user can receive a discount when purchasing the transaction object. For example, in the issued coupon DB14h, the issue number, user ID, facility ID, applicable transaction object information, and discount information may also be associated with each other and stored as issued coupon information. The issue number is identification information used to identify the issued coupon. The user ID indicates the user who has received the coupon. The facility ID indicates the facility where the user can use the coupon. The applicable transaction object information is set when the transaction object to which the discount due to the coupon is applied is limited. Applicable transaction information is used to identify the transaction party to which the coupon applies. Discount information indicates the discount amount or discount rate.

The memory unit 14 also stores various programs, including operating systems, DBMS (Database Management System), and server programs. Server programs can also be programs that instruct the system control unit 11 to execute processes related to electronic billing, remittances, and electronic billing applications. Server programs can be obtained from other devices via the network NW, or they can be recorded on recording media such as magnetic tapes, optical disks, or memory cards and read via a drive device.

The communication unit 15 is composed of, for example, a network interface card. The communication unit 15 connects to the user terminal 2 and the like via the network NW and controls the communication status with the connected device.

[1-3. Function overview]

Next, referring to Figures 4 to 12, the functional overview of the system control unit 11 in the electronic checkout server 1 is described. Figure 4 is a diagram showing an example of the functional blocks of the system control unit 11 in the electronic checkout server 1. The system control unit 11 can also read and execute various program codes contained in the server program through the CPU 11a, and as shown in Figure 4, it becomes a position relationship information acquisition unit 1101, a group identification unit 1102, a checkout request receiving unit 1103, a checkout unit 1104, a payment object information sending unit 1105, an encoding unit 1106, and a control unit 1107. The functions of the payment request information acquisition unit 1106, the burden amount acquisition unit 1107, the provisional burden amount information transmission unit 1108, the changed burden amount information acquisition unit 1109, the burden amount information transmission unit 1110, the remittance request reception unit 1111, the remittance unit 1112, and the gift giving unit 1113 are implemented.

[1-3-1. Identification of the Group]

The location relationship information acquisition unit 1101 may also acquire location relationship information indicating the location relationship between a plurality of user terminals 2. For example, the location relationship information acquisition unit 1101 may acquire location relationship information indicating the location relationship between any user terminal 2-1 among the user terminals 2 on which the electronic checkout application is installed and at least one user terminal 2 other than the user terminal 2-1. The user using the user terminal 2-1 is referred to as the first user. The location relationship information may also include at least the location information of the user terminal 2-1. Furthermore, the location relationship information may also include the location information of each of the plurality of user terminals 2. Based on the location information, the distance between the two user terminals can be identified as a location relationship. The distance between these user terminals 2 can be calculated based on the location information of each user terminal 2. In addition, the location relationship information may also include the inter-terminal communication status information received from each user terminal 2. The user ID included in the signal reception source list of the inter-terminal communication status information received from the user terminal 2 indicates the users of the user terminal 2 who are within the range of the presence notification signal sent to the user terminal 2. Whether a certain user terminal 2 is within the arrival range of the presence notification signal sent by other user terminals 2 is equivalent to the location relationship between these user terminals 2. The signal reception source list may also include the strength of the presence notification signal in addition to the user ID. The fact that a user terminal 2 is located within the range where presence notification signals sent by other user terminals 2 reach with a certain signal strength is equivalent to the location relationship between these user terminals 2.

The user terminal 2 designated as the user terminal 2-1 is arbitrary. For example, the location relationship information acquisition unit 1101 may identify each user terminal 2 as the user terminal 2-1 and acquire location relationship information indicating the location relationship with respect to that user terminal 2-1. Alternatively, the location relationship information acquisition unit 1101 may identify a user terminal 2 moving within any facility as the user terminal 2-1. Alternatively, the location relationship information acquisition unit 1101 may identify a user terminal 2 that has completed an operation to settle a fee paid to the facility as the user terminal 2-1.

FIG5 is a diagram illustrating an example of information transmitted from user terminal 2 to electronic checkout server 1. FIG5 illustrates user terminal 2 as user terminal 2, which includes user terminal 2. User terminal 2-1 transmits a presence notification signal R1 containing identification information of user terminal 2-1. User terminal 2-2 transmits a presence notification signal R2 containing identification information of user terminal 2-2. User terminal 2-1 receives presence notification signal R2. User terminal 2 then transmits, for example, location information of user terminal 2-1, along with inter-terminal communication status information containing identification information of user terminal 2-2, to electronic checkout server 1. User terminal 2-2 receives the presence notification signal R1. Consequently, 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 billing server 1. Thus, the location-related information acquisition unit 1101 acquires the location information and inter-terminal communication status information from each user terminal 2. Alternatively, the location-related information acquisition unit 1101 may acquire the location information and inter-terminal communication status information stored in the location information DB 14f and the inter-terminal communication status DB 14g received from each user terminal 2.

The group identification unit 1102 can also identify a group of users. The identified group can also be a group of users who act together or a group of users who use a facility together. For example, as disclosed in Patent Document 1, the group identification unit 1102 can also allow the user to set up a group. For example, the user sets up a group by entering information used to identify each member of the group (such as name and address, phone number, or email address). However, users do not necessarily use a facility with the same members every time. Therefore, users need to set up a group each time they act as a group or each time they use a facility. Therefore, there are situations where it is desirable to reduce the user's workload and be able to identify a group of users who use a facility together.

Therefore, the group identification unit 1102 can also 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. User terminal 2 used by the second user is referred to as user terminal 2-2. For example, among at least one user terminal 2 different from user terminal 2-1, the group identification unit 1102 identifies as the second user a user using user terminal 2 whose location relationship with user terminal 2-1, as indicated by the location relationship information, exhibits a predetermined location relationship when located at a certain facility. A single second user or multiple second users may be identified.

The defined location relationship may also be, for example, the location relationship between the user terminals 2 of the first and second users that can be observed when the first and second users are traveling together, when the users are traveling together, or when the users are using a facility together. For example, if the users are in a location where they can hear each other or can see each other, the users may be traveling together. The following are specific examples of defined location relationships.

Positional Relationship a: The distance between the two user terminals is less than the specified distance.

Location relationship b: The signal strength of the presence notification signal sent by any one of these user terminals 2, and the signal strength in the location where the other one of these user terminals 2 is located, is higher than a predetermined threshold.

Location relationship c: These user terminals 2 are located in the same facility.

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

Positional relationship a indicates that these users are close to each other. Group users tend to move in close proximity to each other. Furthermore, when group users speak directly to each other, they must be close to each other to a certain extent.

The signal strength in positional relationship b represents the reception strength of a presence notification signal sent by a user terminal 2 at another user terminal 2. Positional relationship b can also indicate that these users are in close proximity. Furthermore, positional relationship b can indicate a high probability that there are no obstacles between these users. Group users tend to move around in the same area (e.g., a facility, room, etc.). If there is an obstacle, such as a wall, between users, the presence notification signal sent from user terminal 2 may not reach the other user terminal 2, or the reception strength may be low. Here, when the threshold is set to zero, the positional relationship b becomes such that these user terminals 2 are located in locations where the presence notification signal sent by user terminal 2 can reach the other user terminal 2. Whether the presence notification signal has reached the other user terminal 2 can be determined by whether the user ID is included in the signal reception source list. Assume that the user terminals 2 are a first user terminal 2 and a second user terminal 2. The signal strength of the presence notification signal sent from the first user terminal 2 when received by the second user terminal 2 may differ from the signal strength of the presence notification signal sent from the second user terminal 2 when received by the first user terminal 2. In this case, the group identification unit 1102 can also determine, for example, whether the average signal strength is greater than a threshold. Alternatively, the group identification unit 1102 can determine whether the signal strength of either party is greater than a threshold. Alternatively, the group identification unit 1102 can determine whether the signal strength of both parties is greater than a threshold.

Location relationship c indicates the possibility that these users are 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.

If the specified location relationship includes at least one of location relationships a and b, the group identifying unit 1102 may use user terminal 2 of the user identified as the first user as a reference and identify users using user terminal 2 who are within the specified distance or whose signal strength is greater than a threshold as users belonging to the same group as the first user. For example, the identified users may be users who pay using an electronic checkout application. Alternatively, the group identifying unit 1102 may treat each user as the first user, identify the location relationships between user terminals 2, and then, by comprehensively considering these location relationships, identify users belonging to the same group. Alternatively, the group identification unit 1102 may use clustering to identify a group of users who are close to each other or a group of users whose notification signal reception strength is high.

FIG6 is an illustration of a specific example of a group. For example, it is assumed that each user of the user terminal 2 that presents the position relationship a and the user that presents the position relationship b belongs to the same group. FIG6 illustrates users U1 to U5. Each user holds a user terminal 2. Among users U1 to U5, for example, user U1 is assumed to be the first user. User U1 is currently located in restaurant 110. Users U2 to U5 are users whose distance from user U1 is less than a predetermined distance. Therefore, user U1 and each of users U2 to U5 present a position relationship a. Users U2 and U3 are located in restaurant 110. Presence notification signals R2 and R3, respectively, sent by user terminal 2 owned by user U2 and user terminal 2 owned by user U3, reach user terminal 2 owned by user U1. Therefore, user U1, U2, and U3 each exhibit location relationship b. Therefore, group identification unit 1102 can also determine that users U1-U3 belong to the same group. User U4 is located outside restaurant 110. Presence notification signal R4 sent by user terminal 2 owned by user U4 is blocked by the exterior wall of restaurant 110 and cannot reach user U1. User U5 is located inside restaurant 110. However, the presence notification signal R5 sent by user terminal 2 owned by user U5 is blocked by the inner wall 111 of restaurant 110 and cannot reach user U1. Therefore, the group identification unit 1102 can also determine that neither user U4 nor U5 belongs to the same group as user U1.

The group identification unit 1102 can also identify a second user who belongs to the same group as the first user, based on the condition that the location information of the user terminal 2-1 indicates that the user terminal 2-1 has been in the facility for a predetermined period of time or longer. In order to use a facility, a user may need to remain in the facility for a predetermined period of time or longer. The group identification unit 1102 can also determine whether the first user is using the facility based on time. If the first user is presumed to be using the facility, and the location relationship between the user terminal 2-1 and the user terminal 2-2 is such that the first user and the second user are presumed to be traveling together, it can be inferred that these users are using the facility together. The time required to use a facility can be common to all facilities or specified for each facility type. For example, a restaurant might require at least 30 minutes to use, while a supermarket might require at least 5 minutes. For facilities that can be used in a relatively short time, such time restrictions may not be imposed.

Because users may move at any time, the locational relationship between user terminals 2 may change over time. Therefore, even among users belonging to the same group, there may be times when the locational relationship between these user terminals 2 does not exhibit a predetermined locational relationship. Conversely, even among users not belonging to the same group, there may be times when the locational relationship between these user terminals 2 exhibits a predetermined locational relationship. Therefore, the locational relationship information acquisition unit 1101 may determine that users whose locational relationship between their terminals exhibits a predetermined locational relationship for a period exceeding a predetermined percentage within a unit of time are considered to belong to the same group.

The group identifying unit 1102 may also identify a second user belonging to the same group as the first user, from among the users of user terminals 2 that exhibit a predetermined locational relationship with user terminal 2-1, among at least one user terminal 2 other than user terminal 2-1, when user terminal 2-1 is outside the facility. The predetermined locational relationship in this case may be, for example, a locational relationship between user terminals 2 held by the first and second users that would be observed when the first and second users are traveling together or as a group. Locational relationship c may also be excluded from the predetermined locational relationship in this case. When the group to which the first user belongs is using the facility, users not belonging to the group may also be using the facility. In this case, even users who are not members of the group may still have a predetermined location relationship with the first user. When outside the facility, users take longer to move than when inside. Therefore, when outside the facility, the location relationship between a user belonging to a group and a user not belonging to the group may not show a predetermined location relationship, or the duration of the non-prescribed location relationship may be longer. By determining the location relationship outside the facility, users with a low probability of belonging to the group can be excluded. The location relationship information acquisition unit 1101 may also use the location relationship of the first user before moving inside the facility. In this case, it may be predefined to begin identifying the location relationship from a certain number of hours before the first user moves into the facility. Alternatively, the location relationship information acquisition unit 1101 may use the location relationship after the first user moves outside the facility. In this case, it may be predefined to begin identifying the location relationship from a certain number of hours after the first user moves outside the facility. Alternatively, the location relationship may be identified separately for the first user before and after their movement into the facility. The location relationship information acquisition unit 1101 may also identify users belonging to the same group from among those users whose location relationship with the two user terminals remains the same for a predetermined percentage of time or longer within a unit time period while the user is outside the facility.

Figure 7 illustrates a specific example of a group. It is assumed that the users of user terminals 2 exhibiting positional relationship a and positional relationship b belong to the same group. Figure 7 illustrates users U1 through U4. Each user possesses a user terminal 2. For example, user U1 is assumed to be the first user. As shown in Figure 7(a), users U1 through U4 are located outdoors. Users U1 and U2 are moving toward each other. The presence notification signal R2 transmitted by user terminal 2 owned by user U2 reaches user terminal 2 owned by user U1. Users U3 and U4 are moving in locations that are quite far from user U1. Furthermore, the presence notification signals R3 and R4 sent by user terminal 2 owned by user U3 and user terminal 2 owned by user U4, respectively, cannot reach user terminal 2 owned by user U1.

Subsequently, as shown in FIG7(b), users U1 to U4 visit restaurant 120 at the same time. The distance between user U1 and each of users U2 to U4 is less than the predetermined distance. Furthermore, the presence notification signals R2, R3, and R4 sent by user terminals 2 of users U2, U3, and U4 arrive at user terminal 2 owned by user U1. If the determination is made based solely on the positional relationship within restaurant 120, users U1 to U4 are determined to belong to the same group. However, outside, although the positional relationship between user U1 and user U2 shows the predetermined positional relationship, the positional relationship between user U1 and each of users U3 and U4 does not show the predetermined positional relationship. Therefore, the group identification unit 1102 may also determine that users U1 and U2 belong to the same group, while users U3 and U4 are determined not to belong to the same group as user U1.

As described later, when a first user belonging to a group performs billing processing on user terminal 2 to pay for a facility, the electronic billing server 1 executes processing to allow other members of the group to transfer funds to the first user. The group identification unit 1102 can identify the group before or during billing.

[1-3-2. Checkout]

The billing request receiving unit 1103 can also receive a billing request, which indicates a billing request from a first user belonging to a user group who has used the user terminal 2-1. This billing may also be for charges paid by the first user. The user group may be the group already identified by the group identifying unit 1102 or a group identified therefrom.

The payment request may include, for example, the user ID of the first user making the payment, the facility ID of the payment destination, payment method information, and the payment amount. The payment request receiving unit 1103 may receive the payment request from, for example, the user terminal 2-1 or a system such as a POS system.

The billing unit 1104 settles the charges in response to the billing request received by the billing request receiving unit 1103. For example, if the billing method is R electronic currency, the billing unit 1104 may subtract the billing amount from the first user's balance stored in the electronic currency balance DB 14c based on the user ID and billing amount included in the billing request. Furthermore, the billing unit 1104 may add the billing amount to the R electronic currency sales amount of the payment destination facility. If the billing method is a credit card, the billing unit 1104 may also obtain the first user's card information. Card information may also include, for example, the card number, expiration date, and the name of the cardholder. For example, the memory unit 14 may store information about cards registered to an electronic payment application for each user. The payment unit 1104 uses this card information to process the payment. The payment method may be a known payment method using a credit card.

Once checkout is complete, the checkout unit 1104 may also store the checkout log in the checkout history DB 14d. At this time, the checkout unit 1104 may also generate a new transaction number. The checkout unit 1104 may also generate a checkout log based on the generated new transaction number and the user ID, checkout method information, facility ID, and checkout amount included in the checkout request.

[1-3-3. Remittance required for split payment]

Once checkout is complete, the checkout unit 1104 may display a checkout completion screen on the user terminal 2-1 indicating that checkout is complete. For example, the checkout completion screen may include a screen that allows users to choose to share a portion of the bill with other members. The checkout unit 1104 may also send a webpage equivalent to the checkout completion screen to the user terminal 2-1.

Figure 8 illustrates an example of a checkout completion screen 210. As shown in Figure 8, the checkout completion screen 210 may also include, for example, a split payment message 211, an approval button 212, and a rejection button 213. The completion message 211 asks whether to proceed with the split payment. The approval button 212 allows the user to approve the split payment. The rejection button 213 allows the user to reject the split payment.

The payment target information transmission unit 1105 may also transmit tentative payment target information indicating the second user identified by the group identification unit 1102 to the user terminal 2-1. The tentative payment target information may also indicate the second user as the user to whom payment is to be made. For example, the tentative payment target information may include the second user's user ID or name. The payment target information transmission unit 1105 may also transmit the tentative payment target information only if the first user clicks the approval button 212 on the checkout completion screen 210.

The payment target information transmission unit 1105 can also display a payment target editing screen on the user terminal 2-1, allowing the first user to confirm and edit the payment target user whose payment is indicated based on the provisional payment target information. Editing the payment target user can also include at least one of adding and deleting payment target users. The payment target information transmission unit 1105 can also send a webpage corresponding to the payment target editing screen to the user terminal 2-1. This webpage can also include the provisional payment target information.

Figure 9 illustrates an example of a payment request object edit screen 220. As shown in Figure 9, the payment request object edit screen 220 may also include one or more payment request object information 221, an add button 222, and a next button 223. Each payment request object information 221 displays the name of the second user identified by the group identification unit 1102. Each payment request object information 221 may also include a delete button 224. The delete button 224 is used to delete the second user identified in the payment request object information 221 from the payment request object users. When the delete button 224 is pressed, the payment subject information 221 containing the delete button 224 is deleted from the payment subject edit screen. The add button 222 is used to add a user to the payment subject. When the add button 222 is pressed, the user terminal 2-1 may display, for example, a payment subject addition screen. The payment subject addition screen may also include, for example, an input field for a phone number or email address. When the first user enters a phone number or email address, the payment subject information sending unit 1105 retrieves the user information containing the entered phone number or email address from the user terminal DB 14a. The payment target information transmission unit 1105 can also transmit the user ID and name contained in the retrieved user information to the user terminal 2-1. The user terminal 2-1 can also display the name sent from the electronic billing server 1 on the payment target addition screen. Once the first user adds the user indicated by the displayed name as a payment target, the user terminal 2-1 can also clear the payment target addition screen and re-display the payment target editing screen 220, adding the payment target information 221 corresponding to the added user to the payment target editing screen 220. The Next button 223 is used to temporarily confirm the user indicated by the payment target information 221 currently displayed on the payment target edit screen 220 as the payment target user, allowing operations to be performed.

The edited payment target information acquisition unit 1106 can also acquire the edited payment target information of the user representing the edited payment target in response to user terminal 2-1 receiving an operation by the user to edit the payment target indicated by the provisional payment target information sent by the payment target information transmission unit 1105. For example, if the first user clicks the next button 223 on the payment target edit screen 220, user terminal 2-1 can also transmit the edited payment target information, including the user ID of the user indicated by each payment target information 221 displayed on the payment target edit screen 220, to the electronic billing server 1.

The share amount acquisition unit 1107 acquires the share amount to be charged to a second user belonging to the same group as the first user, from the amount of charges settled in response to the billing request received by the billing request receiving unit 1103. The share amount acquisition unit 1107 can also acquire the share amount for each second user identified by the group identification unit 1102. For example, the share amount acquisition unit 1107 can also acquire the share amount after billing by the billing unit 1104 is completed.

When the edited payment target information acquisition unit 1106 receives the edited payment target information from the user terminal 2-1, the account balance acquisition unit 1107 can also acquire the account balance after receiving the edited payment target information. In this case, the account balance acquisition unit 1107 can also acquire the account balance for each user of the edited payment target indicated by the edited payment target information.

The payment amount acquisition unit 1107 may also automatically determine the payment amount based on the amount of the billed charge. The payment amount acquisition unit 1107 may also determine each member's payment amount so that the total payment amount of all members of the group, including the first user, matches the amount of the bill. For example, the payment amount acquisition unit 1107 may divide the bill amount by the number of members in the group to calculate the payment amount per person.

The provisional liability amount information transmission unit 1108 can also transmit provisional liability amount information indicating the liability amount obtained by the liability amount acquisition unit 1107 to the user terminal 2-1. The provisional liability amount information can also include the user ID, name, and liability amount for each user identified by the group identification unit or identified by editing the payment target information.

The provisional liability amount information transmission unit 1108 may also display a liability amount editing screen on the user terminal 2-1, which is used for the first user to confirm and change each user's liability amount. The provisional liability amount information transmission unit 1108 may also send a webpage, for example, equivalent to the liability amount editing screen, to the user terminal 2-1. This webpage may also include provisional liability amount information.

Figure 10 illustrates an example of a payment amount edit screen 230. As shown in Figure 10, the payment amount edit screen 230 may also include one or more payment user information 231, a return button 235, and a confirmation button 236. The payment user information 231 is information about the user who will be responsible for at least a portion of the billed charges. The payment amount edit screen 230 may also display payment user information 231 corresponding to each second user, along with payment user information 231 corresponding to the first user. Each payment user information 231 may also include the user's name. Furthermore, each contributing user information 231 may also include an amount input field 232, an increase button 233, and a decrease button 234. The contribution amount acquired by the contribution amount acquisition unit 1107 is displayed in the amount input field 232. By operating the contribution amount acquisition unit 1107, the first user can also change the contribution amount. The increase button 233 is used to increase the contribution amount displayed in the amount input field 232 by a certain amount. Decrease button 234 is used to decrement the payment amount displayed in amount input field 232 by a predetermined amount. Return button 235 is used to redisplay the payment request object edit screen 220. Confirm button 236 is used to temporarily confirm the payment amount currently displayed in amount input field 232 as the final payment amount. Confirm button 236 may only be clickable when the total payment amount of all users matches the amount of the expense being settled. Once the confirmation button 236 is pressed, the user terminal 2-1 will display a payment request confirmation screen. The payment request confirmation screen will also display the name of each user and the amount to be paid. On the payment request confirmation screen, the first user can perform operations to confirm the users to whom the payment request is to be made and the amount to be paid by each user.

The changed liability amount information acquisition unit 1109 can also acquire changed liability amount information indicating the changed liability amount in response to the user terminal 2-1 accepting an operation to change the liability amount indicated by the provisional liability amount information sent by the provisional liability amount information transmission unit 1108. For example, once a confirmation operation is performed on the payment request confirmation screen, the user terminal 2-1 can also transmit the changed liability amount information to the electronic checkout server 1. The changed contribution amount information may also include, for example, the user ID of the first user and the changed contribution amount, as well as the user ID and the changed contribution amount of each user to whom the contribution is being charged.

The burden amount information transmission unit 1110 may also transmit burden amount information indicating the burden amount acquired by the burden amount acquisition unit 1107 to the user terminal 2-2 used by the second user. If the modified burden amount information acquisition unit 1109 acquires the changed burden amount information, the burden amount information transmission unit 1110 may also transmit the changed burden amount information as the burden amount information. Furthermore, when the edited billing target information acquisition unit 1106 acquires the edited billing target information, the payment amount information transmission unit 1110 can also transmit the payment amount information to the user terminal 2-2 used by the user who is the billing target for the expense indicated by the edited billing target information.

The payment amount information transmission unit 1110 can also transmit payment amount information, causing the payment amount information to be displayed on the user terminal 2-2. For example, the payment amount information transmission unit 1110 can also cause the user terminal 2-2 to display a payment request screen required for transferring payment from the second user to the first user. The payment amount information transmission unit 1110 can also transmit a webpage equivalent to the payment request screen to the user terminal 2-1. This webpage can also include the payment amount. Furthermore, the webpage may also include the user ID of the second user, which is the remittance source user ID, and the user ID of the first user, which is the remittance destination user ID.

Figure 11 illustrates an example of a payment request screen 310. As shown in Figure 11, the payment request screen 310 may include payment information 311, payment amount information 312, a transfer button 313, a top-up button 314, and a non-transfer button 315. The payment information 311 may include the payment date, the name of the facility to which the payment is to be made, and the payment amount. Payment amount information 312 indicates the amount that the user of the user terminal 2-2 displaying the payment request screen must pay. The transfer button 313 is used to transfer the payment amount in R electronic currency. Once the remittance button 313 is operated, the user terminal 2-2 may also display, for example, a remittance confirmation screen. The remittance confirmation screen may also include the name of the second user, the remittance source, the name of the first user, the remittance destination, and the remittance amount. The second user can perform the operations required for the remittance according to the contents displayed on the remittance confirmation screen. The top-up button 314 is a button for adding R electronic currency. Once the top-up button 314 is operated, the user terminal 2-2 may also display, for example, a top-up screen. The second user can add R electronic currency according to the top-up screen. Once the top-up is complete, the user terminal 2-2 can also display the payment request screen 310 again. The non-transfer button 315 is a button that does not execute the transfer and is used to display the designated main screen of the electronic checkout application so that operations can be performed.

In response to user terminal 2-2 accepting the remittance operation after receiving the committed amount information sent by committed amount information sending unit 1110, remittance request receiving unit 1111 can also receive a remittance request from user terminal 2-2, indicating a remittance request from the second user to the first user. For example, once a remittance execution operation is performed on the remittance confirmation screen, user terminal 2-2 can also transmit the remittance request to electronic checkout server 1. The remittance request can also include the second user's user ID as the remittance source user ID, the first user's user ID as the remittance destination user ID, and the committed amount as the remittance amount.

Remittance unit 1112 can also process a remittance from the second user to the first user in response to a remittance request received by remittance request receiving unit 1111. For example, remittance unit 1112 can deduct the remittance amount included in the remittance request from the balance in the electronic currency balance DB 14c associated with the same user ID as the source user ID included in the remittance request. Alternatively, remittance unit 1112 can add the remittance amount included in the remittance request to the balance in the electronic currency balance DB 14c associated with the same user ID as the destination user ID included in the remittance request. In this way, the remittance unit 1112 can also update the balances of the first user and the second user.

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

Furthermore, the system control unit 11 may execute the processing required to transfer funds from the second user to the first user using the split payment method only when a billing request is sent to the user terminal 2-1 for payment of a fee at a facility. Alternatively, the system control unit 11 may execute the processing required to transfer funds from the second user to the first user using the split payment method only when a billing request is sent to the user terminal 2-1 for payment of a fee at a facility while the user terminal 2-1 is within a predetermined distance from the facility. Alternatively, after a billing request is sent to pay for a facility, if the first user moves to that facility, the system control unit 11 may also execute the necessary processing to transfer funds from the second user to the first user using the split payment method.

[1-3-4. Giving Gifts]

The gift granting unit 1113 may also grant a gift to at least one of the first user and the second user, in response to the remittance processing already being executed by the remittance unit 1112. The gift granting unit 1113 may grant a gift to only one of the first user and the second user who made the remittance, or to both.

The gift giving unit 1113 may also give a gift to the second user, which is usable at a facility other than the facility for which the electronic payment application was paid, but is within a predetermined range from the facility for which the payment was made. Alternatively, the gift giving unit 1113 may also give the gift to the first user. An example of a gift usable at a facility is a coupon. Examples of facilities located within a specified range from the facility to which payment is made include facilities within a specified linear distance from the facility to which payment is made, facilities within a specified distance along a route from the facility to which payment is made, facilities within a specified travel time from the facility to which payment is made, and facilities located in the same area as the facility to which payment is made. Examples of areas include city districts, towns, cities, villages, and neighborhoods. Groups are located within or near the facility to which payment is made. By providing gifts, the user or group to whom the gift is given is encouraged to use other facilities located near the group's location.

The gift giving unit 1113 may also give the second user a gift that can be used in the same facility as the facility to which the electronic payment application fee was paid. Alternatively, the gift giving unit 1113 may also give the gift to the first user. This can encourage the user or group to whom the gift is given to use the facility again.

The gift giving unit 1113 may also grant coupons that can only be used at pre-determined facilities. Furthermore, the gift giving unit 1113 may also grant coupons that can only be used when purchasing pre-determined goods or transaction objects.

When granting a gift to the second user, the gift granting unit 1113 may grant a gift of a value corresponding to the contribution amount obtained by the contribution amount acquisition unit 1107 or the contribution amount obtained by the modified contribution amount information acquisition unit 1109. The gift granting unit 1113 may also increase the value of the gift as the contribution amount increases. This provides a stronger incentive for the second user to remit the contribution to the first user as the contribution amount increases. The value of the gift may also be, for example, a predetermined percentage of the contribution amount. When granting R electronic currency, the gift granting unit 1113 may increase the amount granted as the pledge amount increases. When granting coupons, the gift granting unit 1113 may increase the discount amount or discount rate of the coupon as the pledge amount increases. Alternatively, the value of the gift may be fixed.

After the remittance is completed, the gift granting unit 1113 can also randomly determine whether to grant a gift to the second user. For example, the gift granting unit 1113 can display a lottery video on the user terminal 2-2 and only grant the gift if the second user wins a prize in the lottery.

The gift giving unit 1113 may also give a gift to the first user each time any second user in the group remits a contribution. Alternatively, the gift giving unit 1113 may also give a gift to the first user only once, when any second user in the group remits a contribution. Alternatively, the gift giving unit 1113 may only give a gift to the first user when all second users in the group have remitted a contribution.

When awarding a gift to the first user, the gift awarding unit 1113 may award a gift of a value corresponding to the amount of the charge after deducting the second user's contribution. In other words, the gift awarding unit 1113 may award a gift of a value corresponding to the first user's contribution from the amount of the billed charge. The value of the gift may be, for example, a predetermined percentage of the first user's contribution, an amount calculated by dividing the first user's contribution by the number of second users in the group, or the first user's contribution. When granting R electronic currency, the gift granting unit 1113 may increase the amount granted as the pledge amount increases. When granting coupons, the gift granting unit 1113 may increase the discount amount or discount rate of the coupon as the pledge amount increases. Alternatively, the value of the gift may be fixed.

[1-4. Communication system operation]

Next, the operation of communication system S will be described with reference to Figure 12. Figure 12 is a flowchart illustrating an example process of communication system S in this embodiment. The example shown in Figure 12 illustrates a case where a group is identified before charges are settled. Furthermore, the example shown in Figure 12 illustrates a case where R electronic currency is given as a gift to the first user and a coupon is given as a gift to the second user.

As shown in Figure 12, user terminal 2-1 periodically obtains location information and inter-terminal communication status information and transmits it to electronic billing management server 1 (step S101). Furthermore, user terminal 2-2 also periodically obtains location information and inter-terminal communication status information and transmits it to electronic billing management server 1 (step S102). The location-related information acquisition unit 1101 of electronic billing 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.

The group identification unit 1102 of the electronic checkout 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 which user terminal 2 has been located at which facility for a predetermined period of time or longer. Here, the group identification unit 1102 determines that the user terminal 2-1 has been located at the facility for a predetermined period of time or longer (step S103). Based on this determination, the group identification unit 1102 identifies other second users belonging to the group to which the user of the user terminal 2-1 belongs (step S104). Here, the group identification unit 1102 may also identify, for example, users of user terminal 2 who are outside the facility and whose locational relationship with user terminal 2-1 exhibits a predetermined locational relationship as candidate group members. For example, the group identification unit 1102 may also identify users of user terminal 2 who, for a predetermined percentage or more of the time period before user terminal 2-1 moved to the facility, exhibited a specific locational relationship between user terminal 2-1 and locational relationship a or b, or both. The group identification unit 1102 may also retrieve from the location information DB 14f the user IDs of users of user terminal 2 who are within a predetermined distance from the location of user terminal 2-1, using locational relationship a. The group identification unit 1102 can also use the location relationship b to search for users whose notification signal strength exceeds a threshold based on the inter-terminal communication status information transmitted from the user terminal 2-1. Once candidate members are identified, the group identification unit 1102 can also identify as members of the group users of the user terminal 2 within the facility whose location relationship with the user terminal 2-1 is a predetermined location relationship. For example, the group identifying unit 1102 may also identify a user of the user terminal 2 whose location relationship with the user terminal 2-1 exhibits a specific location relationship among location relationships a, b, and c, a combination of two specific location relationships among these location relationships, or a combination of all these location relationships, for a predetermined percentage or longer period of time during which the user terminal 2-1 was located at the facility.

On the one hand, user U1 of user terminal 2-1 performs an operation to pay for a facility fee (step S105). In response to this operation, for example, user terminal 2-1 transmits a payment request to electronic billing server 1 (step S106). Billing unit 1104 of electronic billing management server 1 performs billing processing based on the payment request (step S107). Billing unit 1104 also stores the payment log in billing history DB 14d.

Next, the checkout unit 1104 sends the checkout completion screen 210 to the user terminal 2-1 (step S108). Once the checkout unit 1104 confirms that the payment destination information included in the checkout request is the facility ID of the facility at which the user terminal 2-1 is currently located, the checkout completion screen 210 includes a split payment message 211, an approval button 212, and a rejection button 213. The user terminal 2-1 displays the checkout completion screen 210. Assuming that the user U1 clicks the approval button 212, the user terminal 2-1 sends an approval response to the electronic checkout management server 1 (step S109). The approval response indicates that the user U1 has approved the split payment.

Upon receiving the approval response, the payment target information transmission unit 1105 of the electronic billing management server 1 sends the payment target edit screen 220 to the user terminal 2-1 (step S110). At this point, the payment target information transmission unit 1105 causes the payment target information 221 of each second user identified in step S104 to be included in the webpage. The user terminal 2-1 displays the payment target edit screen 220, and user U1 adds or deletes payment targets as needed (step S111). Once user U1 clicks the Next button 223, user terminal 2-1 will send the edited payment object information to the electronic billing management server 1 (step S112).

Upon receiving the edited payment request information, the account balance acquisition unit 1107 of the electronic billing management server 1 calculates the account balance for each member of the billing request (step S113). For example, the account balance acquisition unit 1107 may count the number of user IDs included in the edited payment request information as the number of group members. The account balance acquisition unit 1107 may also calculate the account balance for each person by dividing the billing amount included in the billing request by the number of members.

Next, the provisional liability information sending unit 1108 sends the liability editing screen 230 to the user terminal 2-1 (step S114). At this point, the provisional liability information sending unit 1108 causes the webpage to include the user ID and name of each user included in the edited payment request information, as well as the liability calculated for each user. User terminal 2 displays the liability editing screen 230, and user U1 changes the liability as needed (step S115). Once user U1 confirms the payment request details on the payment request confirmation screen, user terminal 2-1 sends the changed payment amount information to the electronic billing management server 1 (step S116).

Upon receiving the changed balance information, the balance information transmission unit 1110 of the electronic billing management server 1 sends a payment request screen page to the user terminals 2 used by each user other than user U1, among the users indicated by the user ID included in the changed balance information (step S117). The page is sent to user U2, who is using user terminal 2-2. The balance information transmission unit 1110 causes the balance information page to include the balance of user U2 indicated by the changed balance information and the user ID of user U1. User terminal 2-2 displays the payment request screen 310, and user U2 operates the transfer button 313. Once user U2 completes the transfer confirmation operation on the transfer confirmation screen (step S118), user terminal 2-2 sends the transfer request to the electronic billing management server 1 (step S119).

Upon receiving the remittance request, the remittance unit 1112 of the electronic billing management server 1 executes a remittance process from user U2 to user U1 based on the remittance request (step S120). Furthermore, the remittance unit 1112 stores the remittance log in the remittance history DB 14e.

Next, the gift granting unit 1113 performs gift granting processing (step S121). For example, the gift granting unit 1113 may calculate the discount amount for the coupon to be granted to user U2 by using a predetermined ratio of the amount borne by user U2. The gift granting unit 1113 may also retrieve facilities from the facility DB 14b that are within a predetermined range from the facility to which the fee is to be paid. The gift granting unit 1113 may also select any of the retrieved facilities as a facility where the coupon granted to user U2 can be used. The gift granting unit 1113 may also generate coupon information containing the user ID of user U2, the facility ID of the designated facility, and discount information indicating the calculated discount amount. The gift granting unit 1113 may also store this coupon information in the issued coupons DB 14h. Furthermore, the gift granting unit 1113 may also calculate the amount of electronic currency to be granted to user U1, using an amount calculated as a percentage of the amount contributed by user U1. The gift granting unit 1113 may also add the calculated amount to the balance associated with user U1 and stored in the electronic currency balance DB 14c.

Once the gift granting process is complete, the gift granting unit 1113 sends a webpage displaying a remittance completion notification and gift granting notification screen to user terminal 2-2 (step S122). The remittance completion notification and gift granting notification screen displays a message indicating that the remittance has been completed. Furthermore, the remittance completion notification and gift granting notification screen 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. Furthermore, the gift granting unit 1113 sends a webpage displaying a deposit notification and gift granting notification screen to user terminal 2-1 (step S123). The deposit notification and gift notification screen displays a message indicating that the deposit to user U1 has been processed. Additionally, the deposit notification and gift notification screen displays a message indicating that a cash rebate has been issued to user U1 in R electronic currency, along with the amount of the cash rebate.

As described above, according to this embodiment, the electronic billing server 1 can also receive a billing request from the user terminal 2-1. Furthermore, the electronic billing server 1 can also obtain the amount of the share to be charged to the second user belonging to the group, from among the charges billed in response to the billing request. Furthermore, the electronic billing server 1 can also transmit share amount information indicating the share amount to the user terminal 2-2. Furthermore, the electronic billing server 1 can also receive a remittance request from the user terminal 2-2 in response to the user terminal 2-2 accepting the remittance operation after receiving the share amount information. Furthermore, the electronic billing server 1 can also process a transfer of the balance from the second user to the first user in response to a remittance request. In this case, the charges are settled using the user terminal 2-1. This means that the first user first pays the charges on behalf of the first user. Subsequently, the balance information indicating the portion of the settled charges that the second user, belonging to the group, must pay is sent to the user terminal 2-2 used by the second user. The second user can then access the balance. The balance is then transferred from the second user to the first user by operating the user terminal 2-2. Therefore, when multiple users are paying for a fee, users can first know the amount to be paid to other users and then choose to transfer the funds.

Here, the electronic checkout server 1 may also obtain location relationship information indicating the location relationship between user terminal 2-1 and at least one user terminal 2 different from user terminal 2-1. Furthermore, the electronic checkout server 1 may also identify a user who is using user terminal 2 and whose location relationship, when located within the facility, is indicated as exhibiting a predetermined location relationship, as a second user belonging to the group. In this case, location relationship information indicating the location relationship between user terminal 2-1 and other user terminals 2 is obtained. The location relationship between user terminals 2 may be the location relationship between users of these user terminals 2. Then, when the first user is at the facility for which the charges are being paid, the user whose locational relationship with the first user is such that the first user exhibits the specified locational relationship will be identified as a second user belonging to the same group as the first user. Since the first and second users, who exhibit the specified locational relationship, are likely using the facility together, it may be appropriate for the second user to be responsible for at least a portion of the charges paid by the first user. Therefore, even if the user has not set up a group, users belonging to the group using the facility can still be identified.

Here, the electronic checkout server 1 can also identify a second user based on the condition that the location information indicates that the user terminal 2-1 has been at a facility for a predetermined period of time or longer. In this case, if the first user has been at the facility for a predetermined period of time or longer, the second user who belongs to the same group as the first user will be identified. Sometimes, in order to use a facility, a user must be at the facility for a predetermined period of time. Therefore, it is possible to identify situations where the first user is likely to be using the facility, and then identify a second user who is likely to be using the facility together with the first user.

Furthermore, the electronic checkout server 1 can identify the second user from among users of the user terminal 2 whose locational relationship with the user terminal 2-1 when the user terminal 2-1 is outside the facility shows a predetermined locational relationship. In this case, even if the first user's locational relationship shows a predetermined locational relationship when inside the facility, if the first user's locational relationship when outside the facility does not show a predetermined locational relationship, the second user will not be identified as belonging to the same group as the first user. Therefore, a user who happens to be with the first user inside the facility but does not travel with the first user outside the facility can be excluded from the second user belonging to the same group as the first user.

Furthermore, the electronic checkout server 1 can also identify the locational relationship between user terminal 2-1 and at least one user terminal 2 based on inter-terminal communication status information. In this case, the locational relationship between these user terminals 2 is identified based on the wireless communication status between the user terminals 2. For example, the reception status of a presence notification signal wirelessly transmitted from a certain user terminal 2 by other user terminals 2 may be affected by the locational relationship between these user terminals 2. Therefore, the locational relationship between users can be appropriately identified.

Here, the electronic billing server 1 can also identify a second user from among users of user terminals 2 that have sent a presence notification signal to user terminal 2-1. In this case, each user terminal 2 transmits a presence notification signal wirelessly. Among these user terminals 2, the second user who belongs to the same group as the first user is identified from among the users of the user terminal 2 whose presence notification signal has reached user terminal 2-1. The location relationship between users within the reach of the presence notification signal is likely to be one in which these users tend to move around as a group. Therefore, the second user who uses the facility with the first user can be accurately identified.

Furthermore, the electronic billing server 1 may transmit the payment target information indicating the identified second user to the user terminal 2-1. Furthermore, in response to the user terminal 2-1 receiving an operation to edit the second user identified by the payment target information, the electronic billing server 1 may obtain the edited payment target information indicating the second user. In this case, the first user can edit the user identified as the second user belonging to the same group as the first user.

Furthermore, the predetermined location relationship may be the location relationship between user terminal 2-1 and user terminal 2-2, which is visible only when the first user and the second user utilize the facility as a group.

Furthermore, the electronic billing server 1 may also grant a gift to at least one of the first and second users upon completion of the remittance process. In this case, once the balance is remitted from the second user to the first user, the gift is granted to at least one of the first and second users. This encourages users to make the remittances required for the split payment.

Here, the electronic checkout server 1 may also grant the second user a gift corresponding to the amount of payment. In this case, the higher the amount of payment made by the second user, the more likely the second user will be encouraged to make a remittance.

Furthermore, the electronic billing server 1 may also grant a second user a gift that allows them to use the second facility within a specified range from the first facility, a facility different from the first facility to which the bill was paid. In this case, the gift allows them to use the second facility within a specified range from the first facility used by the group. Since the group is located in the second facility, it is easily accessible to the second facility. This can encourage the use of the second facility.

Furthermore, the electronic billing server 1 can also give the second user a gift that allows them to use the facility for which the bill was paid. This can encourage the reuse of facilities previously used by the group.

Furthermore, the electronic billing server 1 may also grant the first user a gift corresponding to the amount of the fee after deducting the second user's contribution. In this case, the higher the first user's contribution, the more likely it is that the first user will be able to make the necessary remittances for the split payment.

Furthermore, the electronic billing server 1 may transmit provisional payment amount information indicating the payment amount to the user terminal 2-1. Furthermore, in response to the user terminal 2-1 accepting an operation to change the payment amount indicated by the provisional payment amount information, the electronic billing server 1 may obtain changed payment amount information indicating the changed payment amount. Furthermore, the electronic billing server 1 may transmit the changed payment amount information to the user terminal 2-2 as the payment amount information. In this case, the payment amount received by the payment device may be changed at the discretion of the first user.

[2. Second Implementation Form]

Next, referring to Figures 13 and 14 , we will explain the second embodiment. In the second embodiment, remittance history is used when a group is specified. Except for the following points, the second embodiment is similar to the first embodiment.

Figure 13 illustrates an example of the functional blocks of the system control unit 11 in the electronic checkout server 1. In Figure 13 , components identical to those in Figure 4 are denoted by the same reference numerals. Figure 13 differs from Figure 4 in that a remittance history acquisition unit 1114 is added to Figure 13 .

The remittance history acquisition unit 1114 can also acquire remittance history from the remittance history DB 14e. For example, the remittance history acquisition unit 1114 can also acquire remittance history for a user who is either a remittance source or a remittance destination, using user terminal 2, for which at least a portion of the location information (e.g., location information) has been acquired by the location information acquisition unit 1101. For example, the remittance history acquisition unit 1114 can also acquire remittance history for a user who is either a remittance source or a remittance destination. The remittance source and remittance destination can be identified by the remittance source user ID and remittance destination user ID contained in each remittance log.

The group identification unit 1102 can also 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, it is assumed that, for example, the predetermined location relationship is a combination of at least two location relationships among the 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 can also identify a user using the user terminal 2, whose location relationship with the user terminal 2-1 shows both the first location relationship and the second location relationship, as the second user belonging to the same group as the first user. This is basically the same as the first embodiment. On the other hand, suppose there is a location relationship between user terminal 2-1, and a user who uses user terminal 2 only presents either the first location relationship or the second location relationship. In this case, group identification unit 1102 can also determine whether a remittance has occurred between the user and the first user based on remittance history. If a remittance has occurred, the user can be identified as a second user belonging to the same group as the first user.

Sometimes, it is impossible to obtain the information that should be included in the location relationship information from some user terminals 2. For example, a general user terminal 2 can set the location information acquisition function to be valid or the short-range wireless communication function to be valid. When the location information acquisition function is set to invalid, the electronic checkout server 1 cannot obtain location information from the user terminal 2. Therefore, the electronic checkout server 1 cannot determine that the location relationship between the user terminal 2 and other user terminals 2 is location relationship a or c. In addition, when the short-range wireless communication function is set to invalid, the user terminal 2 will not send a presence notification signal, nor will it detect the presence notification signal sent from other user terminals 2. Therefore, the electronic billing server 1 cannot obtain inter-terminal communication status information from the user terminal 2. Therefore, the electronic billing server 1 cannot determine that the location relationship between the user terminal 2 and the other user terminal 2 is the location relationship b. Since any one of the conditions for the user to be determined to be the second user's location relationship is always not met, the user will not be determined to belong to any group. However, the user does meet the other location relationship condition. Therefore, there is still a possibility that the user belongs to the group. Users who have remitted money to the first user or users who have received remittances from the first user are highly 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 the reach of the notification signal, there is a high probability that the acquaintance is traveling with the first user. Therefore, the group identification unit 1102 can use remittance history to identify the group instead of location information or inter-terminal communication status information.

Figure 14(a) is an illustration of a specific example of a group. For example, it is assumed that the position relationship of user terminal 2 is that users presenting position relationships a, b, and c belong to the same group. Figure 14(a) illustrates users U1 to U4. For example, user U1 is assumed to be the first user. Users U1 to U4 are currently located in hotel 113. Users U2 to U4 are users whose distance from user U1 is less than a predetermined distance. Therefore, user U1 and each of users U2 to U4 presents position relationship a. Users U2 and U3 respectively set the short-range wireless communication function of user terminal 2 to be valid. Therefore, the user terminals 2 of users U2 and U3 respectively send presence notification signals R2 and R3. Notification signals R2 and R3 arrive at user terminal 2 of user U1. Therefore, group identification unit 1102 can determine that users U1-U3 belong to the same group regardless of the presence or absence of a remittance log.

On the other hand, user U4 has disabled the near-field wireless communication function of user terminal 2. Therefore, user terminal 2 does not transmit inter-terminal communication status information to electronic billing server 1, or transmits inter-terminal communication status information that does not contain any user identification information. Therefore, even if user U4 is located in the same facility as user U1 and within the specified distance, but the signal strength of the notification signal does not exceed the threshold, the group identification unit 1102 can search for remittance logs that include the user ID of either user U1 or U4 as the remittance source user ID and the user ID of the other user as the remittance destination user ID. Figure 14(b) illustrates an example of a transaction log. As shown in Figure 14(b), the remittance history DB 14e stores a remittance log containing user U4's user ID as the source user ID and user U1's user ID as the destination user ID. Therefore, the group identification unit 1102 can also determine that users U1-U4 are members of the same group.

As described above, according to this embodiment, a second user belonging to the same group as the first user can be identified based on the remittance history between users. The user who transferred money to the first user is likely to have been traveling with the first user. Therefore, the second user who used the facility together with the first user can be accurately identified.

[3. Third Implementation Form]

Next, we will explain the third implementation. In the third implementation, each group member's contribution amount is determined based on their age. Except for the points described below, the second implementation can also be similar to at least one of the first and second implementations.

In this embodiment, the contribution amount acquisition unit 1107 determines the contribution amount for each of the first user and the second user identified by the group identification unit 1102, respectively, based on the first user's age and the second user's age. Therefore, the contribution amount increases with age. For example, the contribution amount may be proportional to age. In this case, the contribution amount acquisition unit 1107 may divide the amount of the billed charges by the total age of all group members to calculate the contribution amount per year. The contribution amount acquisition unit 1107 can then calculate the contribution amount by multiplying the contribution amount per year by each member's age. Alternatively, the contribution points allocated to each age group can be pre-determined. In this case, the older the group, the higher the points. The contribution amount acquisition unit 1107 can also divide the amount of the billed expense by the total points allocated to all group members to calculate the contribution amount per point. The share amount acquisition unit 1107 can then calculate the share amount by multiplying the share amount per point by each member's allocated points. Furthermore, each user's age can be identified based on their date of birth stored in the user DB 14a.

The payment amount information transmission unit 1110 may also transmit preliminary payment amount information indicating the payment amount determined for the second user by the payment amount acquisition unit 1107 to the user terminal 2-2. If the payment amount of the first user is allowed to be changed, the payment amount change information acquisition unit 1109 may also transmit provisional payment amount information indicating the payment amount determined for the second user by the payment amount acquisition unit 1107 to the user terminal 2-1.

As described above, according to this embodiment, the older the user, the higher the contribution. Therefore, each user can be required to pay an amount corresponding to their age.

[4. Fourth Implementation Form]

Next, we will describe the fourth embodiment. In the fourth embodiment, whether or not to award a gift to the first user depends on the second user's experience with the R electronic currency. Aside from the following points, the second embodiment may be similar to at least one of the first through third embodiments.

In this embodiment, the gift granting unit 1113 may grant a gift to the first user only if the transfer of the first user's contribution from the second user is due to the second user's first use of R electronic currency. This can encourage the first user to use the electronic payment application for payment or split payment. Furthermore, the second user's first use of R electronic currency is expected to continue using R electronic currency in the future.

The gift granting unit 1113 can also determine whether the second user is using R electronic money for the first time based on the transaction history DB 14d and the remittance history DB 14e. For example, if a transaction log containing the second user's user ID is not stored in the transaction history DB 14d, and if a remittance log containing the second user's user ID as the remittance source user ID is not stored in the remittance history DB 14e, in addition to the remittance log for the current remittance from the second user to the first user, then the gift granting unit 1113 can determine that this is the second user's first time using R electronic money.

As described above, according to this embodiment, if a second user who has never used R e-money uses R e-money for the first time in a remittance from the second user to the first user, a gift will be given to the first user. Therefore, by encouraging the first user to make remittances required for split payments, the use of R e-money can be promoted.

[5. Fifth Implementation Form]

Next, the fifth embodiment will be described with reference to Figures 15 to 22. In previous embodiments, each time the first user settles an expense, the second user is charged a share of the payment. In this embodiment, in group travel, the first user first collects the settled expenses, and then charges the second user after the trip. The purpose of the trip is not particularly limited. Except for the points described below, the fifth embodiment may be the same as at least one of the first through fourth embodiments.

Figure 15 illustrates an example of the schematic configuration of a communication system S according to this embodiment. Elements identical to those in Figure 1 are denoted by the same symbols. As shown in Figure 15 , communication system S includes an electronic checkout server 1, a plurality of user terminals 2, and a travel reservation server 3.

The travel reservation server 3 may also be a server device that performs various processes related to the travel reservation website. The travel reservation website may also be a website that allows reservations for services that can be used during travel. Examples of such services include the provision of accommodation facilities and the transportation of people. Examples of accommodation facilities include hotels, inns, and guesthouses. Examples of transportation facilities required for transportation include airplanes, railways, ships, and express buses. The travel reservation server 3 may also perform the processes required to reserve travel services in response to requests from the user terminal 2.

The travel reservation server 3 may also include databases such as accommodation reservation DB 3a and flight reservation DB 3b. The electronic billing server 1 may also access the databases stored in the travel reservation server 3 via the network NW. Alternatively, the memory unit 14 of the electronic billing server 1 may store a copy of the databases stored in the travel reservation server 3. Furthermore, the electronic billing server 1 may also periodically update the databases with the latest information, for example.

FIG16 is a diagram illustrating an example of information stored in the database of the travel reservation server 3. As shown in FIG16 , in the accommodation reservation DB 3a, accommodation reservation information regarding accommodation reservations can also be stored each time a reservation is made. For example, in the accommodation reservation DB 3a, the reservation number, user ID, facility ID, accommodation start date, accommodation end date, scheduled check-in time, check-out time, number of guests, fee, and checkout method can be associated with each other and stored as accommodation reservation information. The reservation number is used to identify the reservation. The user ID indicates the user who has made a reservation for the accommodation. The facility ID indicates the reserved facility. The accommodation start date indicates the date on which check-in at the accommodation will take place. The "accommodation end date" indicates the date check-out from the accommodation will take place. The "check-in scheduled time" indicates the scheduled check-in time. The "check-out deadline" indicates the time by which check-out is permitted. The "number of guests" indicates the number of guests who have reserved accommodation at the accommodation. The "fee" indicates the accommodation fee charged to the booker for use of the accommodation. The "payment method" indicates how the payment will be made. Both in-person and online payment are acceptable payment methods. In-person payment means the booker pays the fee at the booked accommodation. Online payment means the fee is automatically paid based on the credit card information pre-registered with the travel booking website.

In the transportation facility reservation DB3b, transportation facility reservation information regarding transportation facility ticket reservations can also be stored for each reservation. Examples of tickets include airline tickets, express train tickets and boarding tickets, highway bus tickets, and ship tickets. In the accommodation facility reservation DB3a, information such as the reservation number, user ID, transportation facility type, departure point ID, arrival point ID, scheduled departure date and time, scheduled arrival date and time, number of seats, and fare can also be associated with each other and stored as accommodation facility reservation information. The reservation number is a number used to identify the reservation. The user ID indicates the user who has reserved the transportation facility ticket. The transportation facility type indicates the type of transportation facility for which the ticket has been reserved. The departure point ID is the facility ID of the transportation agency serving as the departure point for the ticket reservation. The arrival point ID is the facility ID of the transportation agency serving as the arrival point. Examples of departure and arrival points include airports, train stations, and ports. The scheduled departure date and time indicates the date and time the transportation agency plans to depart from the departure point. The scheduled arrival date and time indicates the date and time the transportation agency plans to arrive at the arrival point. The number of seats indicates the number of reserved seats. The fare indicates the fare of the reserved ticket.

Figure 17 is a block diagram showing an example of the schematic configuration of the electronic checkout server 1 described in this embodiment. Elements identical to those in Figure 2 are denoted by the same reference numerals. Figure 17 differs from Figure 2 in that a separate payment reservation checkout database 14i is added to the database stored in the memory unit 14.

Figure 18 shows an example of the information stored in the split payment hold checkout DB 14i. As shown in Figure 18, the split payment hold checkout DB 14i can store information about each time a user's travel bill is held for split payment. For example, the split payment hold checkout DB 14i can associate transaction numbers and user IDs with each other and store them as hold checkout information. The transaction number indicates the split payment that has been held, and the user ID identifies the user who paid for the bill.

Figure 19 illustrates an example of the functional blocks of the system control unit 11 in the electronic checkout server 1. Components identical to those in Figure 4 are denoted by the same reference numerals. Figure 19 differs from Figure 4 in that a reservation information acquisition unit 1115, a travel determination unit 1116, and a checkout information transmission unit 1117 are added.

The reservation information acquisition unit 1115 acquires reservation information indicating a reservation made by the first user for a service available during a trip. The acquired reservation information may be at least one of accommodation facility reservation information and transportation facility reservation information. The user ID included in the reservation information allows identification of whether the reservation has been made by the first user.

The travel determination unit 1116 can also determine, based on the reservation information obtained by the reserved information acquisition unit 1115, whether the first user has received a payment request via the payment request receiving unit 1103 during the trip. In other words, the travel determination unit 1116 can also determine whether the first user has paid for the trip. Furthermore, the travel determination unit 1116 can also determine whether the first user's trip has ended based on the reservation information.

For example, when using accommodation reservation information, the travel determination unit 1116 may determine that the first user is traveling at least from the scheduled check-in time on the accommodation start date to the final check-in time on the accommodation end date. The travel determination unit 1116 may also utilize the location information of the user terminal 2-1. For example, the travel determination unit 1116 may determine that the first user's travel has begun if the location of the user terminal 2-1 on the accommodation start date is more than a predetermined distance away from the first user's address. Furthermore, the travel determination unit 1116 may determine that the first user's travel has ended if the location of the user terminal 2-1 on or after the accommodation end date approaches the first user's address and is within a predetermined distance.

When using transportation facility reservation information, the travel determination unit 1116 can also determine, for example, whether the use of the transportation facility for which the ticket was reserved was for the outbound or return trip. For example, the travel determination unit 1116 can compare the distance from the first user's address to the transportation facility's departure point with the distance from that address to the transportation facility's arrival point. The location of the facility serving as the departure point 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 an outbound ticket if the distance to the departure point is shorter, and may determine that the ticket is a return ticket if the distance to the arrival point is shorter. The travel determination unit 1116 may also determine that the first user's travel will begin at the scheduled departure date and time in the outbound transportation agency reservation information. Furthermore, the travel determination unit 1116 may also determine that the first user's travel will end at the scheduled arrival date and time in the return transportation agency reservation information. The travel determination unit 1116 may also utilize the location information of the user terminal 2-1. For example, the travel determination unit 1116 may determine that the first user's travel has begun when the user terminal 2-1's location reaches the departure point on the scheduled departure date. Alternatively, the travel determination unit 1116 may determine that the first user's travel has begun when the user terminal 2-1's location moves beyond a predetermined distance from the first user's address on the scheduled departure date. Furthermore, the travel determination unit 1116 may determine that the first user's travel has ended when the user terminal 2-1's location reaches the arrival point on the scheduled arrival date. Alternatively, the travel determination unit 1116 may determine that the first user's travel has ended when the user terminal 2-1's location approaches the first user's address on the scheduled arrival date and is within a predetermined distance.

The travel decision unit 1116 can also use both accommodation facility reservation information and transportation agency reservation information to make a decision.

The travel determination unit 1116 may determine whether the first user is traveling based on the location information of the user terminal 2-1, rather than using reservation information. For example, the travel determination unit 1116 may determine that the first user is traveling if the location of the user terminal 2-1 is a first predetermined distance (e.g., 50 km) away from the first user's address. Furthermore, the travel determination unit 1116 may determine that the first user is traveling if the location of the user terminal 2-1 moves from the first user's address to a second predetermined distance (e.g., 5 km) or more away from the first user's address and then moves closer to the address to within the second predetermined distance. The second predetermined distance is shorter than the first predetermined distance.

The travel determination unit 1116 can, for example, monitor the location of the user terminal 2-1 and determine the start and end of a trip in real time or periodically. Alternatively, each time the payment request receiving unit 1103 receives a billing request, the travel determination unit 1116 can determine whether the first user is currently traveling based on the location history of the user terminal 2-1 or reservation information.

The travel determination unit 1116 may also store the transaction number of each payment request received during the first user's travel and the user ID of the first user who made the payment in the shared payment reservation payment DB 14i.

Figure 20(a) shows an example of accommodation reservation information stored in the accommodation reservation database 3a. Figure 20(b) shows an example of transportation reservation information stored in the transportation ticket reservation database 3b. For example, assume that user U1 lives in Tokyo. User U1 plans to travel to Okinawa with users U2 and U3. Therefore, user U1 makes a reservation for Hotel F in Okinawa on a travel reservation website. Therefore, as shown in Figure 20(a), an accommodation reservation containing user U1's user ID is stored in the accommodation reservation database 3a. The accommodation start date is March 2nd, and the accommodation end date is March 4th. Furthermore, user U1 has booked round-trip tickets for three people between Haneda Airport and Naha Airport. Therefore, as shown in Figure 20(b), the transportation ticket reservation DB3b stores both the outbound and return transportation reservation information, which contain the user ID of user U1. The scheduled departure date for the outbound trip is March 2nd. The scheduled arrival date for the return trip is March 4th.

Figure 20(c) is a diagram illustrating an example of the actions of a traveling group. On March 2, users U1 to U3 arrived at Haneda Airport (step S201). The travel determination unit 1116 can also determine that user U1 has started traveling from this point in time. User U1's group had breakfast at a restaurant located in the airport, and user U1 paid the bill using an electronic checkout application (S202). Afterwards, the group boarded a passenger plane and moved to Naha Airport (step S203). Then, the group checked into Hotel F (step S204). On March 3, the group rented a rental car at a rental car shop (step S205). The group drank coffee at a roadside cafe (step S206). That night, the group dined at an izakaya (S207). User U1 paid for each item of the day using the electronic checkout application. On March 4, the group checked out of Hotel F, and user U1 paid for the accommodation using the electronic checkout application (step S208). The group arrived at Naha Airport and purchased souvenirs at a store within the airport. At this time, user U1 also paid for the purchases using the electronic checkout application. The group then boarded a plane and traveled to Haneda Airport (step S210). The travel determination unit 1116 may also determine that the trip has ended when the first user arrives at Haneda Airport. Then, the travel determination unit 1116 may also determine that the payment in steps S202 and S205-S209 was made during the trip.

The group identification unit 1102 can also identify a second user belonging to the group by considering the reservation information acquired by the reservation information acquisition unit 1115 in addition to the location information. Accommodation facility reservation information includes the number of guests staying, and transportation facility reservation information includes the number of seats. The number of guests staying or the number of seats may be equal to the number of members in the group. Therefore, the group identification unit 1102 can also identify a second user whose group has the same number of guests staying or seats.

If the checkout unit 1104 performs checkout processing in response to a checkout request determined by the travel determination unit 1116 to be received during the first user's travel, the checkout completion screen 210 displayed on the user terminal 2-1 may not include the split payment message 211, the approval button 212, and the rejection button 213. Therefore, split payment is not performed when the charges are settled. Alternatively, if the checkout unit 1104 determines that the checkout request is received during the first user's travel, the checkout completion screen 210 may include the split payment message 211, the approval button 212, and the rejection button 213.

If the travel determination unit 1116 determines that multiple payment requests have been received during the first user's trip, the payment information transmission unit 1117 may transmit, to the user terminal 2-1, multiple payment information indicating the multiple payments corresponding to each of the multiple payment requests after the travel determination unit 1116 determines that the trip has been completed. Each payment information may include, for example, the transaction number, payment date, name of the facility to be paid, and the payment amount. The payment information transmission unit 1117 may also retrieve, from the shared payment held payment DB 14i, the reserved payment information containing the user ID of the first user whose trip has been determined by the travel determination unit 1116 to have been completed. The checkout information sending unit 1117 can also retrieve the checkout log containing the same transaction number as the transaction number contained in the retained checkout information from the checkout history DB 14d. The checkout information sending unit 1117 can then generate checkout information based on the checkout log.

The checkout information sending unit 1117 can also cause the user terminal 2-1 to display a checkout editing screen, which is required for the first user to confirm and edit the checkout settings for the stall payment. The checkout information sending unit 1117 can also send a webpage corresponding to the checkout editing screen to the user terminal 2-1. This webpage can also contain checkout information.

Figure 21 illustrates an example of a checkout edit screen 240. As shown in Figure 21, the checkout edit screen 240 may also include a plurality of checkout information 241, an approval button 243, and a disapproval button 244. Each checkout information 241 contains information regarding the checkout executed in response to the first user's request. Each checkout information 241 may also include, for example, the checkout date, the name of the payment recipient, and the checkout amount. Furthermore, the checkout information 241 may also include a delete button 242. Delete button 242 is a button used to delete the charges paid in the checkout indicated by the checkout information 241 from the payment allocation list. Once the delete button 242 is clicked, the billing information 241 containing the delete button 242 is deleted from the billing edit screen 240. The approve button 243 is used to approve the allocation of the charges paid in the billing information 241 currently displayed on the billing edit screen 240. Once the approve button 243 is clicked, the user terminal 2-1 will display the payment request edit screen 220. Subsequently, depending on the user's operation, the screen will sequentially transition to the payment request edit screen 230 and the payment request confirmation screen.

If accommodation fees at an accommodation facility are paid online, they are not included in the split payment method described so far. Furthermore, if accommodation fees at an accommodation facility are paid in cash, they are also not included in the split payment method. Furthermore, if the payment method for purchasing a transportation ticket is limited to online payment, the purchase fee is not included in the split payment method. However, the payment information sending unit 1117 can obtain the fee from the reservation information. Therefore, the billing information sending unit 1117 can also include services used during travel and reserved for travel in the items to be paid for in the split payment, regardless of whether the charges are paid using an electronic billing application and whether the billing period is during the travel period. For example, in the example shown in Figure 21, the purchase price of the round-trip air ticket can also be included in the items to be paid for in the split payment.

If the travel determination unit 1116 determines that there are multiple billing requests received during the first user's travel, the payment amount acquisition unit 1107 may acquire the payment amount corresponding to the total of the multiple charges settled in response to the multiple billing request information. For example, the payment amount acquisition unit 1107 may acquire the payment amount from each billing log retrieved by the billing information transmission unit 1117. The payment amount acquisition unit 1107 may also divide the total of the multiple billing amounts by the number of members of the group identified by the group identification unit 1102 to calculate the payment amount per person. Alternatively, the contribution amount acquisition unit 1107 may calculate each member's contribution amount based on the total amount of the charges and the age of each group member. On the contribution amount edit screen 230, if any billing item is deleted from the split payment list, the contribution amount acquisition unit 1107 may exclude the deleted billing item and calculate the total billing amount. Similarly to the above, the contribution amount acquisition unit 1107 may also include charges for services booked for travel in the split payment list, regardless of whether the charges were made using an electronic billing application.

After the travel determination unit 1116 determines that the first user's trip has been completed, the payment amount information transmission unit 1110 may transmit payment amount information indicating the payment amount obtained by the payment amount acquisition unit 1107 based on the total fare amount to the user terminal 2-2. Once the payment amount information is transmitted, the payment amount information transmission unit 1110 may delete the reserved account information containing the user ID of the first user determined to have completed the trip from the split payment reserved account DB 14i.

Figure 22 illustrates an example of a payment request screen 310. Elements identical to those in Figure 11 are denoted by the same symbols. As shown in Figure 22, payment request screen 310 may also include: multiple payment information 311, payment amount information 312, a transfer button 313, a top-up button 314, a non-transfer button 315, and a total amount 316. Total amount 316 represents the total of the multiple payment amounts indicated by the multiple payment information 311.

As described above, according to this embodiment, based on reservation information for travel services, it is possible to determine whether a payment made using user terminal 2-1 was made during the first user's trip and whether the first user's trip has already concluded. If a payment is made during the first user's trip, the processing required for remittance based on the split payment is not performed at that time. After the trip concludes, the multiple payments made during the trip are aggregated and the processing required for remittance based on the split payment is performed. Therefore, the group to which the first user belongs can aggregate the expenses paid by the first user during the trip and convert them into split payments after the trip.

[6. Other implementation forms]

In the embodiments described so far, group identification by the group identification unit 1102 based on location information is performed for the purpose of transferring funds between group members for split payments. However, group identification can also be used for purposes other than split payments or transfers. For example, group identification can be used to share information between group members, distribute information about common or similar attributes between group members, or distribute information about facilities where the group is located.

(Supplementary Note 1-1) A payment processing device characterized by comprising: billing request information receiving means for receiving billing request information indicating a billing request for a charge to be paid by a first user who has used a first terminal device utilized by a first user belonging to a user group; and share amount obtaining means for obtaining a share amount to be charged to a second user belonging to the group and being different from the first user, from the charge settled in response to the previously received billing request information; and a share amount. The information transmitting means is configured to transmit the payment amount information indicating the amount of the previously acquired payment to the second terminal device used by the previously mentioned second user; the remittance request information receiving means is configured to receive remittance request information indicating a remittance request from the previously mentioned second terminal device in response to the previously mentioned second terminal device accepting the remittance operation after receiving the previously transmitted payment amount information; and the remittance means is configured to execute a remittance process of the previously mentioned payment from the previously mentioned second user to the previously mentioned first user in response to the previously mentioned remittance request information being received by the previously mentioned remittance request information receiving means.

(Supplement 1-2) The payment processing device described in Supplement 1-1 is characterized in that the charges settled in response to the settlement request information received in the preceding paragraph are charges paid for a certain facility; and further comprises: a position relationship information acquisition means for acquiring position relationship information indicating a positional relationship between the first terminal device in the preceding paragraph and at least one terminal device other than the first terminal device in the preceding paragraph, and The aforementioned location relationship information includes first location information indicating the location of the aforementioned first terminal device; and identifying means for identifying, among at least one of the aforementioned terminal devices, a user of the terminal device that exhibits the aforementioned location relationship when the aforementioned first terminal device is located within the aforementioned facility based on the aforementioned location relationship information as a aforementioned second user belonging to the aforementioned group.

(Supplement 1-3) The payment processing device described in Supplement 1-2 is characterized in that the aforementioned identifying means identifies the aforementioned second user on the condition that the aforementioned first location information indicates that the aforementioned first terminal device has been located in the aforementioned facility for a predetermined period of time or longer.

(Supplement 1-4) The payment processing device as described in Supplement 1-2 or 1-3, characterized in that the aforementioned identifying means is to identify the aforementioned second user from among users of the aforementioned terminal devices whose aforementioned positional relationship with the aforementioned first terminal device when the aforementioned first terminal device is located outside the aforementioned facility.

(Supplementary Note 1-5) The payment processing device as set forth in any one of Supplementary Notes 1-2 to 1-4, wherein the acquired location relationship information further includes communication status information indicating the status of wireless communication between the first terminal device and each of the at least one terminal devices; and the identifying means identifies the location relationship between the first terminal device and each of the at least one terminal devices based on the communication status information.

(Appendix 1-6) The payment processing device described in Appendix 1-5 is characterized in that each of the aforementioned at least one terminal device wirelessly transmits a predetermined signal; the aforementioned communication status information indicates the terminal device that transmitted the predetermined signal before reaching the aforementioned first terminal device; and the aforementioned identifying means identifies the aforementioned second user from among users of the aforementioned terminal device that transmitted the predetermined signal before reaching the aforementioned first terminal device.

(Supplementary Note 1-7) The payment processing device as described in any of Supplementary Notes 1-2 to 1-6 is further characterized by comprising: remittance history information acquisition means for acquiring remittance history information representing remittance history that can identify each user of a remittance source and a remittance destination, wherein the aforementioned first user is the remittance history of either the aforementioned remittance source or the aforementioned remittance destination; and identifying means for identifying the aforementioned second user based on the aforementioned location relationship information and the aforementioned remittance history information.

(Note 1-8) The payment processing device described in Note 1-7 is characterized in that the position relationship specified in the preceding note includes: a predetermined first position relationship, and a predetermined second position relationship different from the predetermined first position relationship; the specific means specified in the preceding note is to use a terminal device that presents the predetermined first position relationship and the predetermined second position relationship with the predetermined first terminal device. , specifically identified as the aforementioned second user belonging to the aforementioned group; the aforementioned identifying means is to identify the user as the aforementioned second user belonging to the aforementioned group when the location relationship with the aforementioned first terminal device is such that only a user using a terminal device in either the aforementioned first location relationship or the aforementioned second location relationship has transferred money to the aforementioned first user.

(Supplementary Note 1-9) The payment processing device as described in any of Supplementary Notes 1-2 to 1-8 is characterized by further comprising: payment request information transmission means for transmitting payment request information indicating the second user identified in the preceding paragraph to the preceding first terminal device; and payment request information editing acquisition means for acquiring payment request information in response to the preceding first terminal device accepting an operation for editing the payment request information transmitted in the preceding paragraph indicating the second user identified in the preceding paragraph. The edited payment recipient information of the second user in the previous record after the previous record was edited is obtained. The means for obtaining the amount of the previous record liability is used to obtain the amount of the previous record liability for the second user in the previous record indicated by the edited payment recipient information obtained in the previous record. The means for transmitting the amount of the previous record liability information is used to transmit the amount of the previous record liability information to the second terminal device in the previous record used by the second user in the previous record indicated by the edited payment recipient information obtained in the previous record.

(Supplementary Note 1-10) The payment processing device described in any of Supplementary Notes 1-2 to 1-9 is characterized in that the location relationship specified in the preceding paragraph is a location relationship that is visible only when the first user and the second user utilize the facility as a group, and is a location relationship between the first terminal device and the second terminal device.

(Supplementary Note 1-11) The payment processing device described in any of Supplementary Notes 1-1 to 1-10 is further provided with: granting means for performing a process of granting a gift to at least one of the aforementioned first user and the aforementioned second user, in response to the aforementioned remittance process having been performed by the aforementioned remittance means.

(Note 1-12) The payment processing device described in Note 1-11 is characterized in that the means for granting the pre-credit is to grant a pre-credit gift of a value corresponding to the amount of the pre-credit contribution to the second user.

(Note 1-13) The payment processing device described in Notes 1-11 or 1-12 is characterized in that the charges charged in the preceding paragraph are charges paid by the preceding user for the preceding first facility when the preceding user uses any of the preceding first facilities; and the granting means in the preceding paragraph grants the preceding second user a gift of use at a second facility located within a predetermined range from the preceding first facility, among facilities other than the preceding first facility.

(Note 1-14) The payment processing device described in any of Notes 1-11 to 1-13 is characterized in that the charges charged are charges paid by the first user for the facility when the first user uses any facility, and the granting means grants the second user a gift for use in the facility.

(Note 1-15) The payment processing device described in any of Notes 1-11 to 1-14 is characterized in that the means for granting the pre-credit is to grant the pre-credit gift to the first user of the pre-credit, the value of which corresponds to the amount of the pre-credit expenses after deducting the amount of the pre-credit already obtained.

(Note 1-16) The payment processing device described in any of Notes 1-11 to 1-15 is characterized in that the pre-credit remittance means is a pre-credit processing means for remitting the pre-credit liability in a specified electronic currency; and the pre-credit granting means is a means for granting a pre-credit gift to the first user of the previous record if the pre-credit remittance resulting from the pre-credit remittance means is the first use of the specified electronic currency by the second user of the previous record.

(Supplementary Note 1-17) The payment processing device described in any of Supplementary Notes 1-1 to 1-16 is characterized in that the means for obtaining the pre-credited liability amount determines the amount of the pre-credited first user and the amount of the pre-credited second user as amounts corresponding to the ages of the pre-credited first user and the pre-credited second user, respectively; and the means for transmitting pre-credited liability amount information transmits pre-credited liability amount information indicating the amount of the pre-credited liability determined by the means for obtaining the pre-credited liability amount for the pre-credited second user.

(Note 1-18) The payment processing device as described in any one of Notes 1-1 to 1-17 is characterized by further comprising: a second liability amount information transmission means for transmitting the second liability amount information indicating the amount of the liability obtained in the aforementioned note to the aforementioned first terminal device; and a liability amount information change acquisition means for obtaining the change of the liability amount information in response to the aforementioned first terminal device. The device receives an operation to change the amount of the previously recorded liability indicated by the second liability amount information transmitted in the previous record, and obtains the changed liability amount information indicating the amount of the previously recorded liability after the previous record is changed. The previously recorded liability amount information transmitting means transmits the previously recorded changed liability amount information as the previously recorded liability amount information.

(Note 1-19) The payment processing device as described in any one of Notes 1-1 to 1-18 is characterized by further comprising: reservation information acquisition means for acquiring reservation information indicating the reservation made by the first user for the service that can be used during the trip; and determination means for determining, based on the reservation information acquired in the previous record, whether the first user has received the previous record settlement request information during the previous record trip through the previous record settlement request information receiving means and whether the previous record trip has ended; and the previous record borne amount acquisition means. The preceding section, if the preceding determination means has determined that multiple preceding billing request information has been received during the preceding trip, obtains the preceding liability amount corresponding to the total of the multiple preceding charges settled in response to the multiple billing request information. The preceding liability amount information transmission means, after the preceding determination means has determined that the preceding trip has been completed, transmits preceding liability amount information indicating the total of the preceding liability amounts obtained by the preceding liability amount acquisition means in response to the total of the preceding charges.

(Note 1-20) A payment processing method is a payment method executed by a computer, characterized by comprising: a settlement request information receiving step for receiving settlement request information indicating a settlement request for payment of a charge to be paid by the first user using a first terminal device utilized by any first user belonging to a user group; and a contribution amount obtaining step for collecting the contribution amount to be paid from a second user belonging to the first user, who is different from the first user, out of the charges settled in response to the settlement request information received. and a burden amount information sending step, which sends burden amount information indicating the amount of burden obtained in the previous record to the second terminal device used by the second user in the previous record; and a remittance request information receiving step, which receives the burden amount information sent in the previous record in response to the second terminal device in the previous record. The device accepts the remittance operation and receives remittance request information indicating a remittance request from the aforementioned second terminal device; and the remittance step, in response to the aforementioned remittance request information being received by the aforementioned remittance request information receiving step, executes a remittance process for remitting the aforementioned balance from the aforementioned second user to the aforementioned first user.

(Note 1-21) A payment processing program, characterized by causing a computer to function as: billing request information receiving means for receiving billing request information indicating a billing request for payment of charges to be paid by a first user who utilizes a first terminal device utilized by a first user belonging to a user group; and payment amount obtaining means for obtaining a payment amount to be charged to a second user belonging to the previous group, who is different from the first user, for the previous charges settled in response to the previously received billing request information; The burden amount information transmitting means is used to transmit burden amount information indicating the amount of the previously acquired burden to the second terminal device used by the previously mentioned second user. The remittance request information receiving means is used to receive remittance request information indicating a remittance request from the previously mentioned second terminal device in response to the previously mentioned second terminal device accepting the remittance operation after receiving the previously transmitted burden amount information. The remittance means is used to execute a remittance process of the previously mentioned burden from the previously mentioned second user to the previously mentioned first user in response to the previously mentioned remittance request information being received by the previously mentioned remittance request information receiving means.

(Supplementary Note 2-1) A group identifying device is characterized by comprising: location relationship information acquisition means for acquiring location relationship information indicating a location 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 aforementioned first terminal device, wherein the aforementioned location relationship information includes first location information indicating the location of the aforementioned first terminal device; and identifying means for identifying, among the aforementioned at least one terminal device, a user who is a user of a terminal device whose aforementioned location relationship, when indicated by the aforementioned acquired location relationship information, exhibits a predetermined location relationship when the aforementioned first terminal device is located in any facility, as a second user belonging to the aforementioned group.

(Appendix 2-2) The group identification device described in Appendix 2-1 is characterized in that the aforementioned identification means identifies the aforementioned second user under the condition that the aforementioned first location information indicates that the aforementioned first terminal device has been located in the aforementioned facility for a predetermined period of time or longer.

(Supplement 2-3) The group identification device as described in Supplement 2-1 or 2-2 is characterized in that the aforementioned identifying means is to identify the aforementioned second user from among users of the terminal devices whose aforementioned positional relationship with the aforementioned first terminal device when the aforementioned first terminal device is located outside the aforementioned facility.

(Supplementary Note 2-4) The group identifying device according to any of Supplementary Notes 2-1 to 2-3, wherein the acquired location relationship information further includes communication status information indicating the status of wireless communication between the first terminal device and each of the at least one terminal devices; and the identifying means identifies the location relationship between the first terminal device and each of the at least one terminal devices based on the communication status information.

(Appendix 2-5) The group identification device described in Appendix 2-4 is characterized in that each of the aforementioned at least one terminal device wirelessly transmits a predetermined signal; the aforementioned communication status information indicates the terminal device from which the predetermined signal was transmitted before reaching the aforementioned first terminal device; and the aforementioned identification means identifies the aforementioned second user from among users of the aforementioned terminal device from which the predetermined signal was transmitted before reaching the aforementioned first terminal device.

(Appendix 2-6) The group identifying device according to any of Appendices 2-1 to 2-5, further comprising: remittance history information acquisition means for acquiring remittance history information representing remittance history that can identify each user of a remittance source and a remittance destination, wherein the aforementioned first user is the remittance history of either the aforementioned remittance source or the aforementioned remittance destination; and identifying means for identifying the aforementioned second user based on the aforementioned location relationship information and the aforementioned remittance history information.

(Note 2-7) The group-specific device described in Note 2-6 is characterized in that the positional relationship specified in the preceding note includes: a predetermined first positional relationship, and a predetermined second positional relationship different from the predetermined first positional relationship; the specific means specified in the preceding note is to use a terminal device whose positional relationship with the predetermined first terminal device is such that the terminal device presents both the predetermined first positional relationship and the predetermined second positional relationship. , specifically identified as the aforementioned second user belonging to the aforementioned group; the aforementioned identifying means is to identify the user as the aforementioned second user belonging to the aforementioned group when the location relationship with the aforementioned first terminal device is such that only a user using a terminal device in either the aforementioned first location relationship or the aforementioned second location relationship has transferred money to the aforementioned first user.

(Supplementary Note 2-8) For group-specific devices as described in any of Supplementary Notes 2-1 to 2-7, the positional relationship specified in the preceding paragraph is a positional relationship that is visible only when the first user and the second user utilize the facility as a group, and is a positional relationship between the first terminal device and the second terminal device utilized by the second user.

(Supplementary Note 2-9) The group identifying device according to any one of Supplementary Notes 2-1 to 2-8 is further provided with: billing request information receiving means for receiving billing request information indicating a billing request for charges to be paid by the first user using the first terminal device; share amount obtaining means for obtaining the share amount to be charged to the second user from the charges settled in response to the received billing request information; and share amount information transmitting means for transmitting share amount information indicating the share amount obtained in the first terminal device to the second user.

(Appendix 2-10) The group-specifying device described in Appendix 2-9 is characterized by further comprising: remittance request information receiving means for receiving remittance request information indicating a remittance request from the aforementioned second terminal device in response to the aforementioned second terminal device, which has received the previously transmitted payment amount information, accepting the remittance operation; and remittance means for executing a remittance process for remitting the aforementioned payment amount from the aforementioned second user to the aforementioned first user in response to the aforementioned remittance request information being received by the aforementioned remittance request information receiving means.

(Supplementary Note 2-11) The group identification device described in Supplementary Note 2-9 or 2-10 is characterized by further comprising: payment recipient information transmission means for transmitting payment recipient information indicating the second user identified in the preceding note to the first terminal device in the preceding note; and payment recipient information editing acquisition means for acquiring payment recipient information in response to the first terminal device in the preceding note accepting an operation for editing the payment recipient information transmitted in the preceding note indicating the second user identified in the preceding note. The edited payment recipient information of the second user in the previous record after the previous record was edited is obtained. The means for obtaining the amount of the previous record liability is used to obtain the amount of the previous record liability for the second user in the previous record indicated by the edited payment recipient information obtained in the previous record. The means for transmitting the amount of the previous record liability information is used to transmit the amount of the previous record liability information to the second terminal device in the previous record used by the second user in the previous record indicated by the edited payment recipient information obtained in the previous record.

(Note 2-12) A group identification method is a group identification method executed by a computer, and is characterized by comprising: a position relationship information acquisition step of acquiring position relationship information, which represents the position 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 aforementioned first terminal device, and the aforementioned position relationship information includes first position information representing the position of the aforementioned first terminal device; and a specifying step of specifying, in the aforementioned at least one terminal device, as a second user belonging to the aforementioned group, a user who uses a terminal device whose aforementioned position relationship when the aforementioned first terminal device is located in any facility is represented by the aforementioned acquired position relationship information as a second user belonging to the aforementioned group.

(Supplementary Note 2-13) A group identifying program is characterized by causing a computer to function as: position relationship information acquisition means for acquiring position relationship information indicating a positional relationship between a first terminal device used by any first user belonging to a group of users and at least one terminal device other than the first terminal device, wherein the position relationship information includes first position information indicating the position of the first terminal device; and identifying means for identifying, among the at least one terminal device, a user who is using a terminal device whose positional relationship, when indicated by the acquired position relationship information, when the first terminal device is located in any facility, is such that the first terminal device exhibits a predetermined positional relationship, as a second user belonging to the group.

1: Electronic checkout server

2: User terminal

NW: Network

S: Communication system

Claims (22)

A payment processing device characterized by comprising: Accounting request information receiving means for receiving account information indicating a request for payment of charges to be paid by the first user using a first terminal device utilized by a first user belonging to a user group; and Contribution amount obtaining means for obtaining the contribution amount to be charged to a second user belonging to the first user, who is different from the first user, of the charges settled in response to the previously received account information; and The liability amount information transmitting means is configured to transmit liability amount information indicating the amount of the liability acquired in the previous record to the second terminal device used by the second user in the previous record; and The remittance request information receiving means is configured to receive remittance request information indicating a remittance request from the second terminal device in response to the second terminal device in response to the second terminal device in response to the previously transmitted liability amount information accepting the remittance operation; and The remittance means is configured to execute a remittance process of the previous liability from the second user in the previous record to the first user in response to the previous remittance request information being received by the previous remittance request information receiving means; and The granting means is used to grant the gift to the first user in the preceding paragraph, conditioned on the fact that the remittance of the previous contribution from the second user in the preceding paragraph to the first user in the preceding paragraph has already been executed through the remittance means in the preceding paragraph. The payment processing device as recited in claim 1, wherein: the previously recorded charges settled in response to the previously received settlement request information are charges paid for a certain facility; further comprising: position relationship information acquisition means for acquiring position relationship information indicating a positional relationship between the previously recorded first terminal device and at least one terminal device other than the previously recorded first terminal device, wherein the previously recorded position relationship information includes first position information indicating the position of the previously recorded first terminal device; and The identifying means is for identifying, among at least one terminal device, a user of the terminal device whose previous location relationship, when the first terminal device is located in the facility, is indicated as exhibiting the predetermined location relationship based on the previously acquired location relationship information, as a second user belonging to the group. In the payment processing device recited in claim 2, the aforementioned identifying means identifies the aforementioned second user on the condition that the aforementioned first location information indicates that the aforementioned first terminal device is located in the aforementioned facility for a predetermined period of time or longer. A payment processing device as recited in claim 2 or 3, wherein the aforementioned specific means is to identify the aforementioned second user among the users of the terminal devices whose aforementioned positional relationship with the aforementioned first terminal device when the aforementioned first terminal device is located outside the aforementioned facility is such that the aforementioned second user exhibits a predetermined positional relationship. The payment processing device of claim 2, wherein: the acquired location relationship information further includes communication status information indicating the status of wireless communication between the first terminal device and each of the at least one terminal devices; the identifying means identifies the location relationship between the first terminal device and each of the at least one terminal devices based on the communication status information. The payment processing device of claim 5, wherein: each of the aforementioned at least one terminal device transmits a predetermined signal wirelessly; the aforementioned communication status information indicates the terminal device from which the predetermined signal was transmitted before reaching the aforementioned first terminal device; the aforementioned identifying means identifies the aforementioned second user from among users of the aforementioned terminal device from which the predetermined signal was transmitted before reaching the aforementioned first terminal device. The payment processing device according to claim 2 or 5, further comprising: remittance history information acquisition means for acquiring remittance history information representing remittance history that can identify each user of a remittance source and a remittance destination, wherein the aforementioned first user is a remittance history of either the aforementioned remittance source or the aforementioned remittance destination; and aforementioned identifying means for identifying the aforementioned second user based on the aforementioned location relationship information and the aforementioned remittance history information. The payment processing device as recited in claim 7, wherein: the aforementioned predetermined location relationship includes: a predetermined first location relationship and a predetermined second location relationship different from the aforementioned first location relationship; the aforementioned identifying means identifies a user of a terminal device whose location relationship with the aforementioned first terminal device exhibits both the aforementioned first location relationship and the aforementioned second location relationship as the aforementioned second user belonging to the aforementioned group; the aforementioned identifying means identifies a user of a terminal device whose location relationship with the aforementioned first terminal device exhibits only either the aforementioned first location relationship or the aforementioned second location relationship as the aforementioned second user belonging to the aforementioned group if there is a fact of money transfer between the user and the aforementioned first user. The payment processing device as recited in claim 2 or 3, further comprising: payment subject information transmission means for transmitting payment subject information indicating the second user identified in the previous record to the first terminal device in the previous record; and edit payment subject information acquisition means for acquiring edit payment subject information indicating the second user identified in the previous record after the previous record is edited, in response to the first terminal device in the previous record accepting an operation for editing the payment subject information transmitted in the previous record; previous record liability amount acquisition means for acquiring the previous record liability amount for the second user identified in the previous record by the edit payment subject information acquired in the previous record; The pre-recorded liability amount information transmission means transmits the pre-recorded liability amount information to the pre-recorded second terminal device used by the pre-recorded second user indicated by the edited payment target information obtained in the pre-recorded record. In the payment processing device recited in claim 2 or 3, the aforementioned location relationship is a location relationship that is visible only to the aforementioned first user and the aforementioned second user when utilizing the facility as a group, and is a location relationship between the aforementioned first terminal device and the aforementioned second terminal device. The payment processing device as recited in claim 1, wherein the aforementioned granting means further performs a process for granting a gift to the aforementioned second user. In the payment processing device recited in claim 11, the pre-credit granting means comprises granting a pre-credit gift having a value corresponding to the amount of the pre-credit contribution to the pre-credit second user. The payment processing device recited in claim 1 or 11, wherein: The charges charged are charges paid by the first user for the first facility when the first user utilizes any first facility; The granting means grants the first user or the second user a gift of use at a second facility, other than the first facility, that is within a predetermined distance from the first facility. The payment processing device recited in claim 1 or 11, wherein: The charges charged are charges paid by the first user for the facility when the first user utilizes any facility; The granting means grants the first user or the second user a gift for use in the facility. The payment processing device according to claim 1 or 11, wherein the pre-credit granting means is to grant a pre-credit gift to the first user having a value corresponding to the amount of the pre-credit expenses after deducting the amount of the pre-credit already obtained. The payment processing device according to claim 1 or 11, wherein: the pre-credit remittance means is a means for performing a pre-credit process to remit the pre-credit liability in a specified electronic currency; the pre-credit granting means is a means for granting a pre-credit gift to the first user if the pre-credit remittance resulting from the pre-credit remittance means is the first use of the specified electronic currency by the second user. In the payment processing device described in claim 1 or 11, if the pre-credit granting means is executed after the pre-credit first user has settled the pre-credit charges and the remittance of the pre-credit balance from the pre-credit second user to the pre-credit first user has been executed using the pre-credit remittance means, then the gift is granted to the pre-credit first user. If the pre-credit settlement has been executed but the remittance of the pre-credit balance from the pre-credit second user to the pre-credit first user has not been executed using the pre-credit remittance means, then the gift is not granted to the pre-credit first user. The payment processing device according to claim 1 or 2, wherein: the means for obtaining a pre-credited liability amount determines the amount of the pre-credited first user's liability and the amount of the pre-credited second user's liability as amounts corresponding to the ages of the pre-credited first user and the pre-credited second user, respectively; the means for transmitting pre-credited liability amount information indicates the amount of the pre-credited liability determined by the means for obtaining a pre-credited liability amount for the pre-credited second user. The payment processing device according to claim 1 or 2, further comprising: second liability amount information transmitting means for transmitting second liability amount information indicating the amount of the previously acquired liability to the previously acquired first terminal device; and changed liability amount information acquiring means for acquiring changed liability amount information indicating the amount of the previously acquired liability after the previously acquired liability has been changed, in response to the previously acquired first terminal device accepting an operation for changing the amount of the previously acquired liability indicated by the previously acquired second liability amount information; The means for transmitting the previously recorded liability amount information is to transmit the previously recorded modified liability amount information as the previously recorded liability amount information. The payment processing device as recited in claim 1 or 2, further comprising: reservation information acquisition means for acquiring reservation information indicating a reservation made by the first user for a service available for use during a trip; and determination means for determining, based on the previously acquired reservation information, whether the first user received the previous settlement request information during the previous trip via the previous settlement request information receiving means, and whether the previous trip has ended; The advance payment amount obtaining means, if the advance payment determination means determines that multiple advance payment settlement request information has been received during the advance payment trip, obtains the advance payment amount corresponding to the total of the multiple advance payment amounts settled in response to the multiple settlement request information. The advance payment amount information transmitting means, after the advance payment determination means determines that the advance payment trip has been completed, transmits advance payment amount information indicating the total of the advance payment amounts obtained by the advance payment amount obtaining means in response to the total of the advance payment amounts. A payment processing method, executed by a computer, is characterized by comprising: a billing request information receiving step of receiving billing request information indicating a billing request for a charge to be paid by the first user using a first terminal device utilized by a first user belonging to a user group; and a contribution amount obtaining step of obtaining the contribution amount to be charged to a second user belonging to the group, who is different from the first user, from the charges settled in response to the received billing request information; and The step of transmitting the burden amount information, which indicates the amount of the burden acquired, is transmitted to the second terminal device used by the second user mentioned above. The step of receiving the remittance request information is the step of receiving remittance request information indicating a remittance request from the second terminal device mentioned above in response to the second terminal device mentioned above accepting the remittance operation after receiving the burden amount information transmitted above. The remittance step is to execute the process of remitting the aforementioned contribution from the aforementioned second user to the aforementioned first user upon receipt of the aforementioned remittance request information by the aforementioned remittance request information receiving step; and The granting step is to execute the process of granting the gift to the aforementioned first user, conditional upon the execution of the process of remitting the aforementioned contribution from the aforementioned second user to the aforementioned first user in the aforementioned remittance step. A payment processing program, characterized by causing a computer to function as: Accounting request information receiving means for receiving account information indicating a request for payment of charges to be paid by the first user using a first terminal device utilized by a first user belonging to a user group; and Contribution amount obtaining means for obtaining the amount of a contribution to be charged to a second user belonging to the first user group, who is different from the first user, out of the charges settled in response to the previously received account information; and The liability amount information transmitting means is configured to transmit liability amount information indicating the amount of the liability acquired in the previous record to the second terminal device used by the second user in the previous record; and The remittance request information receiving means is configured to receive remittance request information indicating a remittance request from the second terminal device in response to the second terminal device in response to the second terminal device in response to the previously transmitted liability amount information accepting the remittance operation; and The remittance means is configured to execute a remittance process of the previous liability from the second user in the previous record to the first user in response to the previous remittance request information being received by the previous remittance request information receiving means; and The granting means is used to grant the gift to the first user in the preceding paragraph, conditioned on the fact that the remittance of the previous contribution from the second user in the preceding paragraph to the first user in the preceding paragraph has already been executed through the remittance means in the preceding paragraph.