Program, Information Processing Method, Terminal

Abstract

To improve usability of a terminal which executes processing for settlement.SOLUTION: A program which causes a terminal that executes a process concerning settlement to execute the process, allows the terminal to execute transmission, by a communication unit of the terminal, of first settlement information based on a process for first settlement by a user of the terminal on the basis of input to the terminal by the user of the terminal, reception, by the communication unit, of at least information on a first amount of money among the first amount of money which the user of the terminal transfers or receives based on the first settlement information and a second amount of money which a user of a terminal different from the terminal transmits or receives, a process, by the control unit of the terminal, of first transfer money or the process of first reception based on the first amount of money, and process of second money transfer or process of second money reception by the control unit on the basis of second settlement information when the first settlement information is revised to the second settlement information.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present disclosure relates to a program, an information processing method, and a terminal.

Background Art

[0002] Recently, services that manage electronic money (e-money) of a terminal or a user of the terminal and perform settlement using e-money have been spreading by applications executable on terminals such as smartphones. For example, Patent Document 1 discloses a technique for settling the purchase amount of a product.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

[0004] According to a first aspect of the present invention, a program for causing a terminal that executes processing related to settlement to execute includes: transmitting, by a communication unit of the terminal, first settlement information based on processing related to a first settlement by a user of the terminal based on an input to the terminal by the user of the terminal; receiving, by the communication unit, information on at least a first amount that the user of the terminal remits or receives and a second amount that a user of a terminal different from the terminal remits or receives, based on the first settlement information; executing, by a control unit of the terminal, a first remittance process or a first receipt process based on the first amount; and when the first settlement information is corrected to second settlement information, executing, by the control unit, a second remittance process or a second receipt process based on the second settlement information. According to a second aspect of the present invention, an information processing method for a terminal that executes processing related to settlement includes transmitting, by a communication unit of the terminal, first settlement information based on processing related to a first settlement by a user of the terminal, based on an input to the terminal by the user of the terminal; receiving, by the communication unit, information on at least the first amount that the user of the terminal remits or receives and the second amount that the user of a terminal different from the terminal remits or receives, based on the first settlement information; executing, by a control unit of the terminal, a first remittance process or a first receipt process based on the first amount; and when the first settlement information is corrected to second settlement information, executing, by the control unit, a second remittance process or a second receipt process based on the second settlement information. According to a third aspect of the present invention, a terminal that executes processing related to settlement includes a communication unit that transmits first settlement information based on processing related to a first settlement by a user of the terminal, based on an input to the terminal by the user of the terminal, and receives information on at least the first amount that the user of the terminal remits or receives and the second amount that the user of a terminal different from the terminal remits or receives, based on the first settlement information; and a control unit that executes a first remittance process or a first receipt process based on the first amount, and when the first settlement information is corrected to second settlement information, executes a second remittance process or a second receipt process based on the second settlement information. According to a fourth aspect of the present invention, a terminal that executes processing related to settlement includes a processor that reads a program stored in a memory and executes processing based on the program, and the processor transmits, by a communication unit of the terminal, first settlement information based on processing related to a first settlement by a user of the terminal, based on an input to the terminal by the user of the terminal; receives, by the communication unit, information on at least the first amount that the user of the terminal remits or receives and the second amount that the user of a terminal different from the terminal remits or receives, based on the first settlement information; executes a first remittance process or a first receipt process based on the first amount; and when the first settlement information is corrected to second settlement information, executes a second remittance process or a second receipt process based on the second settlement information. According to a fifth aspect of the present invention, a program for causing a server that communicates with a terminal that executes processing related to settlement to execute is based on an input to the terminal by a user of the terminal, and based on processing related to a first settlement by the user of the terminal. Receiving first settlement information from the terminal by the communication unit of the server, and at least the information of the first amount that the user of the terminal remits or receives, and the user of a terminal different from the terminal, based on the first settlement information. Transmitting at least the information of the first amount to the terminal by the communication unit, and transmitting at least the information of the second amount to a different terminal by the communication unit, and a first remittance process or a first receipt process for the terminal based on the first amount. Executing a second remittance process or a second receipt process for a different terminal based on the second amount by the control unit of the server, and receiving information related to correcting from the first settlement information to the second settlement information by the communication unit. When corrected to the second settlement information, based on the second settlement information, executing a third remittance process or a third receipt process for the terminal, and a fourth remittance process or a fourth receipt process for a different terminal by the control unit is executed by the server.

Brief Description of Drawings

[0005]

Figure 1

Figure 2-1

Figure 2-2

Figure 2-3

Figure 2-4

Figure 2-5

Figure 2-6

Figure 2-7

Figure 2-8

Figure 2-9

Figure 2-10

Figure 2-11

Figure 2-12

Figure 2-13

Figure 2-14

Figure 2-15

Figure 2-16

Figure 2-17

Figure 2-18

Figure 2-19

Figure 2-20

Figure 2-21

Figure 2-22

Figure 2-23

Figure 2-24

Figure 3-1

Figure 3-2

Figure 3-3

Figure 3-4

Figure 3-5

Figure 3-6

Figure 3-7

Figure 3-8

Figure 3-9

Figure 3-10

Figure 3-11

Figure 4-1

Figure 4-2

Figure 4-3

Figure 4-4

Figure 4-5

Figure 4-6

Figure 4-7

Figure 4-8

Figure 4-9

Figure 4-10

Figure 4-11

Figure 4-12

Figure 5-1

Figure 5-2

Figure 5-3

Figure 5-4

Figure 5-5

Figure 5-6

Figure 5-7

Figure 5-8

Figure 5-9

Figure 5-10

Figure 5-11

Figure 5-12

Figure 5-13

Figure 5-14

Figure 5-15

Figure 5-16

Figure 5-17

Figure 6-1

Figure 6-2

Figure 6-3

Figure 6-4

Figure 6-5

Figure 6-6

Figure 6-7

Figure 6-8

Figure 6-9

Figure 6-10

Figure 6-11

Figure 6-12

Figure 6-13

Figure 6-14

Figure 6-15

Figure 6-16

Figure 6-17

Figure 6-18

Figure 6-19

Figure 6-20

Figure 7-1

Figure 7-2

Figure 7-3

Figure 8-1

Figure 8-2

Figure 8-3

Figure 8-4

Figure 8-5

Figure 8-6

Figure 8-7

Figure 9-1

Figure 9-2

Figure 10

Figure 11-1

Figure 11-2

Figure 12-1

Figure 12-2

Figure 12-3

Figure 12-4

Figure 13-1

Figure 13-2

Figure 14-1

Figure 14-2

Figure 14-3

Figure 14-4

Figure 14-5

Figure 14-6

Figure 14-7

Figure 14-8

Figure 14-9

Figure 14-10

Figure 15-1

Figure 15-2

Figure 15-3

Figure 15-4

Figure 15-5

Figure 15-6

Figure 16-1

Figure 16-2

Figure 16-3

Figure 16-4

Figure 16-5

Figure 16-6

Figure 17-1

Figure 17-2

Figure 17-3

Figure 17-4

Figure 17-5

Figure 17-6

Figure 17-7

Figure 17-8

Figure 17-9

Figure 17-10

Figure 17-11

Figure 17-12

Figure 17-13

Figure 17-14

Figure 17-15

Figure 17-16

Figure 18-1

Figure 18-2

Figure 19

Figure 20

Figure 21-1

Figure 21-2

Figure 21-3

Fig. 21-4

Fig. 21-5

Fig. 22-1

Fig. 22-2

Fig. 22-3

Fig. 22-4

Fig. 22-5

Mode for Carrying Out the Invention

[0006] <Compliance with Legal Matters> It should be noted that the disclosure described in this specification is premised on compliance with the legal matters of the country of implementation required for the implementation of the present disclosure, such as the secrecy of communication.

[0007] Embodiments for implementing the program, information processing method, terminal, server, etc. according to the present disclosure will be described with reference to the drawings.

[0008] <Summary> In recent years, as applications related to network services (application software), applications for making payments with electronic money (payment applications), applications for conducting settlements with electronic money (settlement applications), applications for sending / receiving money with electronic money (money transfer applications), etc., and applications that aggregate some or all of the functions of these applications have been spreading, and users of the terminal 20 have been able to receive various services related to electronic money using these applications.

[0009] "Electronic money" is electronic money distinguished from physical money, and means the electronic money managed in the above various applications or owned by the user of the terminal 20.

[0010] Note that electronic money may be expressed as "electronic cash" or "digital currency", or may not be expressed in that way. Also, as "electronic money (electronic cash)" or "digital currency", legal tender may be used, or virtual currency may be used. Also, "electronic money (electronic cash)" or "digital currency" may include cryptocurrency (crypto assets). Also, virtual currency may include physical money such as coupons.

[0011] In this specification, the expression "by the communication I / F" is used as appropriate. This indicates that the device transmits and receives various types of information and data via the communication I / F (via the communication unit) based on the control of the control unit (such as a processor), by way of example and not limitation.

[0012] Also, in this specification, "settlement" means electronic settlement (e-payment). An example of this is the e-payment using the above-mentioned electronic money. In the following embodiments, "shopping settlement" is exemplified as a type of this settlement. Shopping settlement is a settlement for making a payment as consideration for the purchase of goods, provision of services, etc., and is an example of the settlement by the user of the terminal 20 (the settlement made by the user of the terminal 20). Also, the shopping settlement history is an example of settlement information based on the processing related to the settlement by the user of the terminal 20 (the processing executed by the terminal 20 regarding the settlement by the user of the terminal 20 as described above).

[0013] "Processing related to settlement" is, by way of example and not limitation, the processing related to shopping settlement executed by the terminal 20, including the processing of obtaining code information for performing shopping settlement from a server or the like (including the processing of requesting the server or the like to generate the code information and the processing of receiving the generated code information from the server or the like), the processing of displaying the obtained code information, the processing of obtaining the settlement result (including the settlement notice) of the shopping settlement from a server or the like, and other processing that is somehow related to performing shopping settlement. More specifically, it includes all the processing executed by the terminal 20 as processing related to performing shopping settlement. "Code information" includes a code image and the information stored in the code image (stored information, encoded information).

[0014] Also, in this specification, "split payment" means that the paid amount based on one or more shopping settlement histories is borne by the users of a plurality of terminals 20. In addition, the split payment described in this specification is not necessarily limited to equally dividing the amount among the users of a plurality of terminals 20, but also includes the case of dividing the amount among the users of a plurality of terminals 20 according to different proportions. "Equal division" means dividing at the same ratio, and "division according to different proportions" means dividing at different ratios.

[0015] Also, the settlement of the money for split payment is referred to as "split payment settlement", and the process for realizing this split payment settlement is referred to as "split payment settlement process". Note that the split payment settlement may be expressed as "split payment settlement" in the sense of split payment settlement, and the split payment settlement process may be expressed as "split payment settlement process", or it may not be expressed in this way.

[0016] In addition, in this specification, when the terminal 20 transmits information, in addition to transmitting information to different terminals 20, it also includes transmitting information to servers such as the server 10 and the messaging server 40.

[0017] <First Embodiment> The first embodiment is an embodiment for realizing split payment of the settlement amount for shopping settlement by the user of one of the terminals 20 between the terminals 20 of two users.

[0018] The content described in the first embodiment is applicable to any of the other embodiments and other modification examples. Also, for the same components as the components already described, the same reference numerals are given, and repeated description is omitted.

[0019] [System Configuration] In the communication system according to this embodiment, by way of example and not limitation, at least a plurality of terminals 20 (terminal 20A, terminal 20B, terminal 20C, ···) are connected via a network (such as the Internet).

[0020] The terminal 20 (terminal 20A, terminal 20B, terminal 20C, ···) (not limited, an example of a terminal or an information processing device) can be any terminal as long as it is an information processing terminal capable of realizing the functions described in each embodiment. The terminal 20 includes, by way of example and not limitation, smartphones, mobile phones (feature phones), computers (by way of example and not limitation, desktops, laptops, tablets, etc.), media computer platforms (by way of example and not limitation, cable, satellite set-top boxes, digital video recorders), handheld computer devices (by way of example and not limitation, PDAs (personal digital assistants), email clients, etc.), wearable terminals (eyeglass-type devices, watch-type devices, etc.), or other types of computers, or communication platforms. Also, the terminal 20 may be referred to as an information processing terminal.

[0021] Since the configurations of terminal 20A, terminal 20B, and terminal 20C are basically the same, terminal 20 will be described in the following explanation. Also, as will be illustrated and described in detail from the second embodiment onwards, the control unit of terminal 20 will be described as control unit 21, and the communication unit of terminal 20 will be described as communication I / F (interface) 22.

[0022] FIG. 1 is a flowchart showing an example of the processing flow executed by each device in this embodiment. In order from the left, an example of the splitting calculation process executed by the control unit 21 of terminal A (by way of example and not limitation, the terminal 20 of user A.A) and an example of the splitting calculation process executed by the control unit 21 of terminal B (by way of example and not limitation, the terminal 20 of user B.B) are shown respectively. Hereinafter, the user of terminal A will be referred to as "user A.A", and the user of terminal B will be referred to as "user B.B" for explanation.

[0023] In this example, the case of splitting the shopping settlement history (more specifically, the shopping settlement amount) by user A.A with user B.B will be taken as an example for explanation.

[0024] In addition to the shopping settlement amount, the shopping settlement history can include, by way of example and not limitation, the name of the store where the goods were purchased or the service was received (store name), the name and type of the goods purchased or the service provided, the date and time of the settlement (shopping settlement date and time), the amount of the settlement (shopping settlement amount), and other information. Also, the shopping settlement history can be expressed as shopping settlement history information.

[0025] First, the control unit 21 of terminal A executes the first shopping settlement history selection process (A10). Specifically, by way of example and not limitation, the control unit 21 of terminal A selects at least one shopping settlement history from among a plurality of shopping settlement histories of user A.A stored in the storage unit 28 of terminal A based on an operation input for selecting the shopping settlement history for the input / output unit 23. The shopping settlement history in this embodiment is an example of first settlement information based on the process related to the first settlement by the user of the terminal.

[0026] After that, the control unit 21 of terminal A transmits the shopping settlement history selected in A10 to terminal B via the communication I / F 22 (A20). Specifically, by way of example and not limitation, based on an operation input for transmitting the shopping settlement history for the input / output unit 23, the shopping settlement history selected in A10 is transmitted. In this case, the shopping settlement history to be transmitted can include, by way of example and not limitation, at least the information on the shopping settlement amount. The shopping settlement amount is the amount actually settled in the shopping settlement (the amount actually paid by the user in the shopping settlement).

[0027] When receiving the shopping settlement history from terminal A (B \alpha), the control unit 21 of terminal B calculates the over / short amount in the split payment (hereinafter referred to as the "over / short amount") (B30). Specifically, based on the shopping settlement amount of the shopping settlement history received from terminal A, by way of example and not limitation, the over / short amount of user B.B (the amount that user B.B transfers to user A.A in this example) is calculated.

[0028] Here, the amount that a user has already paid for shopping settlement is referred to as the "amount already paid" of that user. For a user who has settled the shopping settlement history subject to splitting the bill, the shopping settlement amount of that shopping settlement history becomes the amount already paid. When multiple shopping settlement histories are subject to splitting the bill, the total amount of the shopping settlement amounts of those shopping settlement histories becomes the amount already paid. On the other hand, for a user who has not settled the shopping settlement history, the amount already paid is "0 yen".

[0029] In this embodiment, consider the case where user B.B does not register the shopping settlement history as subject to splitting the bill and only user A.A registers the shopping settlement history as subject to splitting the bill, and consider the case of splitting the amount already paid by user A.A with user B.B on an equal share basis. In this case, the amount to be borne per person (hereinafter referred to as the "amount per person") is calculated as "the amount already paid subject to splitting the bill (in this example, the amount already paid by user A.A) ÷ the number of people for whom splitting the bill is performed (in this example, 2 people)".

[0030] In this case, in B30, the excess or deficiency amount of the user is calculated as, by way of example and not limitation, "the excess or deficiency amount of that user = the amount already paid by that user - the amount per person". If the calculated excess or deficiency amount is a positive value, it means that the user is on the receiving side (receiving) of money, and if the calculated excess or deficiency amount is a negative value, it means that the user is on the paying side (payment) of money.

[0031] By way of example and not limitation, consider the case where the amount already paid (= shopping settlement amount) paid by user A.A for shopping settlement is "1,000 yen" and this is split with user B.B on an equal share basis. The amount already paid by user B.B is "0 yen", and the amount per person is "1,000 yen ÷ 2 people = 500 yen", so the excess or deficiency amount of user B.B is "0 yen - 500 yen = -500 yen", that is, it is calculated as "500 yen payment".

[0032] Note that this is only an example and is not limited thereto. In B30, instead of calculating the excess or deficiency amount of user B.B, the excess or deficiency amount of user A.A may or may not be calculated. In this case, in the above example, since the amount paid by user A.A is "1,000 yen" and the amount per person is "500 yen", the excess or deficiency amount of user A.A is calculated as "1,000 yen - 500 yen = +500 yen", that is, "Receive 500 yen".

[0033] Also, in B30, it may or may not be possible to calculate both the excess or deficiency amount of user A.A and the excess or deficiency amount of user B.B.

[0034] Also, the sharing ratio for the split payment may be an equal split (equal division) as described above, or a different ratio (unequal division).

[0035] Thereafter, the control unit 21 of terminal B transmits the information on the excess or deficiency amount calculated in B30 (hereinafter referred to as "excess or deficiency amount information") to terminal A via the communication I / F 22 (B40).

[0036] Here, the excess or deficiency amount information transmitted to terminal A may be the information on the excess or deficiency amount of user B.B, the information on the excess or deficiency amount of user A.A, or the information on the excess or deficiency amounts of both user A.A and user B.B.

[0037] When performing split payment settlement, the terminal 20 of the user who pays the amount performs a transfer process of transferring the excess or deficiency amount of that user to the terminal 20 of the other user by electronic money. On the other hand, the terminal 20 of the user who receives the money performs a receiving process of receiving the amount corresponding to the excess or deficiency amount of that user from the terminal 20 of the other user by electronic money.

[0038] The act of a user of terminal 20 sending money to a user of a different terminal 20 (or the act of terminal 20 sending money to a different terminal 20) is referred to as "transfer", and the process for realizing this transfer is referred to as "transfer process". On the other hand, when a user of terminal 20 receives money sent from a user of a different terminal 20 (or when terminal 20 receives money sent from a different terminal 20), it is referred to as "receiving", and the process for realizing this receiving is referred to as "receiving process".

[0039] Note that "receiving" and "receiving process" can also be expressed as "receiving payment" and "receiving payment process", respectively, in the sense of receiving money.

[0040] When the control unit 21 of terminal A receives the over / under amount information from terminal B (A40), it performs a split payment settlement process with the control unit 21 of terminal B (A50, B50). Specifically, by way of example and not limitation, the control unit 21 of terminal B transfers the over / under amount of user B.B to terminal A via the communication I / F 22. On the other hand, the control unit 21 of terminal A receives money corresponding to the over / under amount of user B.B from terminal B via the communication I / F 22. The split payment settlement process in this embodiment is an example of the sending process / receiving process executed by the control unit 21 of terminal 20.

[0041] As one method, the split payment settlement process can be performed between terminal A and terminal B by using, for example and not limitation, Internet banking (online banking), etc. Also, as another method, the split payment settlement process can be performed by using services related to electronic money such as the payment service (payment application) described later.

[0042] Thereafter, the control unit 21 of terminal A causes the display unit 24 to display the result of the split payment settlement (hereinafter referred to as the "split payment settlement result") (A60). Specifically, by way of example and not limitation, the received amount received in the receiving process (or the sent amount sent from the other party in the sending process) is caused to be displayed on the display unit 24.

[0043] After that, the control unit 21 of terminal A determines whether to end the process (A90). If it determines to continue the process (A90: NO), it returns the process to A10. On the other hand, if it determines to end the process (A90: YES), it ends the split payment process.

[0044] Similarly, the control unit 21 of terminal B causes the display unit 24 to display the split payment settlement result (B60). Specifically, by way of example and not limitation, the display unit 24 is caused to display the transfer amount transferred in the transfer process (or the amount received by the other party in the receipt process).

[0045] After that, the control unit 21 of terminal B determines whether to end the process (B90). If it determines to continue the process (B90: NO), it returns the process to B20. On the other hand, if it determines to end the process (B90: YES), it ends the split payment process.

[0046] <Relationship between transfer process / receipt process> Basically, as described above, the user of terminal 20 that transmits the shopping payment history (the first user) is the user who has already paid the amount by shopping payment and is the side that requests the split payment. Therefore, terminal 20 of the first user will execute the receipt process. In contrast, the user of terminal 20 that receives the shopping payment history (the second user) is the side that is requested for the split payment. Therefore, terminal 20 of the second user will execute the transfer process.

[0047] However, although details will be described later, by way of example and not limitation, in the method of the present disclosure, not only the shopping payment history by the first user but also the shopping payment history by the second user can be made the object of split payment together. In such a case, there may be a case where terminal 20 of the first user executes the transfer process and terminal 20 of the second user executes the receipt process. For this reason, terminal 20 will execute either the transfer process or the receipt process.

[0048] <Effect of the first embodiment> In the first embodiment, based on an operation input to the terminal 20 by the user of the terminal 20 (which is not limited and is an example of an input to the terminal by the user of the terminal), the shopping settlement history (which is not limited and is an example of the first settlement information) is transmitted by the communication I / F 22 (which is not limited and is an example of the communication unit of the terminal) to a different terminal 20. Also, the terminal 20 receives, by the communication I / F 22, information on the excess or deficiency amount (which is not limited and is an example of at least the first amount among the first amount that the user of the terminal remits or receives and the second amount that the user of a terminal different from the terminal remits or receives, based on the first settlement information) based on the transmitted shopping settlement history from a different terminal 20. Then, the terminal 20 shows a configuration in which, based on the excess or deficiency amount, a splitting settlement process (which is not limited and is an example of a remittance process or a receipt process based on the first amount) is executed by the control unit 21 (which is not limited and is an example of the control unit of the terminal). As an example of the effect obtained by such a configuration, based on transmitting the first settlement information based on the process related to the first settlement by the user of the terminal, the terminal can execute, by the control unit, a remittance process or a receipt process based on the first amount, and can easily remit or receive money, thereby improving the convenience for the user.

[0049] In addition, in the first embodiment, the control unit 21 of the terminal 20 includes a processor that reads a program stored in a memory and executes processing based on this program. Based on an operation input to the terminal 20 by the user of the terminal 20 (which is not limited and is an example of an input to the terminal by the user of the terminal), the processor transmits a shopping settlement history (which is not limited and is an example of first settlement information based on processing related to the first settlement by the user of the terminal) to a different terminal 20 via the communication I / F 22 (which is not limited and is an example of a communication unit of the terminal). Further, the processor receives, via the communication I / F 22, information on the excess or deficiency amount (which is not limited and is an example of at least the first amount among the first amount that the user of the terminal remits or receives and the second amount that the user of a terminal different from the terminal remits or receives, based on the first settlement information) based on the transmitted shopping settlement history from a different terminal 20. And the processor shows a configuration for executing a split settlement process (which is not limited and is an example of a remittance process or a receipt process based on the first amount) based on the excess or deficiency amount. Even with such a configuration, the same effects as described above can be obtained.

[0050] In addition, the first embodiment shows a configuration in which the above-mentioned remittance process or receipt process is a process including remittance to or receipt from a user of a different terminal 20 (which is not limited and is an example of a user of a different terminal). With such a configuration, remittance to a user of a different terminal or receipt of money from a user of a different terminal can be easily realized.

[0051] In addition, the first embodiment shows a configuration in which the shopping settlement history includes information on the shopping settlement amount (which is not limited and is an example of information on the amount of the first settlement by the user of the terminal). As an example of the effect obtained with such a configuration, the terminal can receive and acquire at least the information on the first amount by transmitting the first settlement information including the information on the amount of the first settlement by the user of the terminal.

[0052] In addition, the first embodiment shows a configuration in which the shopping payment history is a payment history of shopping payment (not limited, an example of the payment history of the first payment). As an example of the effect obtained by such a configuration, the terminal can receive and acquire at least information on the first amount by transmitting the payment history of the first payment.

[0053] In addition, in the first embodiment, among a plurality of shopping payment histories (not limited, an example of a plurality of payment information) by the user of the own terminal 20, the shopping payment history (not limited, an example of the first payment information) selected by the user of the own terminal 20 is transmitted by the communication I / F 22 (not limited, an example of the communication unit of the terminal) to a different terminal 20. Further, the terminal 20 receives, by the communication I / F 22, information on the excess / deficit amount (not limited, an example of at least the first amount among the first amount that the user of the terminal remits or receives and the second amount that the user of a terminal different from the terminal remits or receives) based on the transmitted shopping payment history. Then, the terminal 20 shows a configuration in which, based on the excess / deficit amount, a settlement calculation process (not limited, an example of a remittance process or a receipt process based on the first amount) is executed by the control unit 21 (not limited, an example of the control unit of the terminal). As an example of the effect obtained by such a configuration, based on transmitting the first payment information among a plurality of payment information regarding payments by the user of the terminal by the communication unit, the terminal can easily remit or receive money by executing, by the control unit, a remittance process or a receipt process based on the information on the first amount based on the first payment information.

[0054] Further, in the first embodiment, the terminal 20 includes a processor that reads a program stored in the memory and executes processing based on this program. The processor transmits, via the communication I / F 22 (which is an example of a communication unit of the terminal, not limited thereto), a shopping settlement history (which is an example of the first settlement information, not limited thereto) selected by the user of its own terminal 20 from among a plurality of shopping settlement histories (which is an example of a plurality of settlement information, not limited thereto) of the user of its own terminal 20 to a different terminal 20, and receives, via the communication I / F 22, information on the excess or deficiency amount (which is an example of at least the first amount among the first amount that the user of the terminal remits or receives and the second amount that the user of a terminal different from the terminal remits or receives, based on the first settlement information, not limited thereto) based on the transmitted shopping settlement history from the different terminal 20, and executes a split settlement process (which is an example of a remittance process or a receipt process based on the first amount, not limited thereto) based on the excess or deficiency amount. Even with such a configuration, the same effects as described above can be obtained.

[0055] <First Modification Example (1)> In the first embodiment, when one terminal 20 transmits a shopping settlement history to be subject to split settlement to another terminal 20 (A20 in the process of FIG. 1), in addition to the shopping settlement amount, information on the goods purchased in the shopping settlement corresponding to the shopping settlement history and information on the services provided in the shopping settlement corresponding to the shopping settlement history may or may not be included in the transmission.

[0056] In this case, the information on the goods purchased in the shopping settlement may include, by way of example and not limitation, a product ID for identifying the purchased product itself, a product type ID for identifying the type of the purchased product, information such as the quantity of the purchased product, and the like. Further, the information on the services provided in the shopping settlement may include, by way of example and not limitation, a service ID for identifying the provided service itself, a service type ID for identifying the type of the provided service, information such as the number of people to whom the service was provided, and the like.

[0057] In this case, the other terminal 20 can notify the user of the other terminal 20 of the detailed content of the split payment requested by the user of one terminal 20 by displaying, on the display unit 24, information about the goods or services included in the shopping settlement history received from one terminal 20.

[0058] In this modified example, the shopping settlement history includes information about the goods purchased in the shopping settlement (not limited to, for example, information about the goods purchased in the first settlement), or information about the services provided in the shopping settlement (not limited to, for example, information about the services provided in the first settlement). As an example of the effect obtained by such a configuration, the terminal can receive and acquire information about the amount of money each of the terminal and a plurality of terminals including different terminals sends or receives by transmitting first settlement information including information about the goods purchased in the first settlement or the services provided in the first settlement.

[0059] <First Modified Example (2)> In the first embodiment, the input to the terminal by the user of the terminal is an operation input to the terminal by the user of the terminal, but it is not limited to this. Not limited to, but as an example, the input to the terminal by the user of the terminal may be a voice input to the terminal by the user of the terminal, or it may not be so. Not limited to, but as an example, according to the voice input by the user of the terminal, processes such as selection of the shopping settlement history and transmission of the shopping settlement history may be performed, or it may not be so. This is the same in the embodiments described below.

[0060] As an example of the effect obtained by such a configuration, the input to the terminal can be realized by a simple method such as voice input.

[0061] <Second Embodiment> The second embodiment is an embodiment in which the terminal 20 performs a remittance / receipt process via the server 10 using a payment application. It is different from the first embodiment in that the server 10 is added as a component requirement.

[0062] The content described in the second embodiment is applicable to any of the other embodiments and any of the other variations. Also, for components identical to the components already shown, the same reference numerals are given and repeated description is omitted.

[0063] Hereinafter, an operator who provides a payment service using a payment application is referred to as an "operator of payment services".

[0064] Note that the operator of payment services can also be expressed as an operator who provides a payment application or an operator of the server 10. Also, in the sense of an operator who provides a settlement service, it can also be expressed as an operator of settlement services.

[0065] Also, hereinafter, it will be described that the server 10 is operated and managed by the operator of payment services. Also, hereinafter, the name of the payment application will be appropriately referred to as "Payment App" for illustration and description.

[0066] Also, the payment application may be provided by the server 10 as a single application that does not have the function of a so-called messaging service (MS: Messaging Service), or may be provided by the server 10 as a composite application having the function of MS. Also, the messaging service may or may not include an instant messaging service (IMS: Instant Messaging Service) that enables the transmission and reception of contents such as simple messages between terminals 20.

[0067] In addition, the payment application may be provided by the server 10 as a single application without the so-called Social Networking Service (SNS) function, or may be provided by the server 10 as a composite application with the SNS function.

[0068] Note that MS (including IMS) can also be considered as one form of SNS. Therefore, MS and SNS may or may not be distinguished.

[0069] <System Configuration> FIG. 2-1 is a diagram showing an example of the system configuration of the communication system 1A in this embodiment. In the communication system 1A, by way of example and not limitation, the server 10 and a plurality of terminals 20 (terminal 20A, terminal 20B, terminal 20C,...) are connected via the network 30.

[0070] The server 10 has a function of providing a payment service to the terminals 20 owned by the user via the network 30. The server 10 can also be expressed as a payment service server, a payment management server, a settlement service server, a settlement management server, etc. Note that the number of servers 10 and terminals 20 connected to the network 30 is not limited.

[0071] The network 30 plays a role of connecting one or more terminals 20 and one or more servers 10. That is, the network 30 means a communication network that provides a connection path so that data can be transmitted and received after the above various devices are connected.

[0072] One or more portions of the network 30 may or may not be a wired network or a wireless network. By way of example and not limitation, the network 30 can include an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a cellular telephone network, ISDN (integrated service digital networks), a wireless LAN, LTE (long term evolution), CDMA (code division multiple access), Bluetooth (registered trademark), satellite communication, etc., or any combination of two or more of these. The network 30 can include one or more networks 30.

[0073] Server 10 (an example of a server, an information processing device, or an information management device, not limited thereto) has a function of providing a predetermined service (a payment service in this embodiment) to terminal 20. Server 10 may be any device as long as it is an information processing device capable of realizing the functions described in each embodiment. Server 10 includes, by way of example and not limitation, a server device, a computer (by way of example and not limitation, a desktop, a laptop, a tablet, etc.), a media computer platform (by way of example and not limitation, a cable, a satellite set-top box, a digital video recorder), a handheld computer device (by way of example and not limitation, a PDA, an email client, etc.), or other types of computers, or a communication platform. Also, Server 10 may be referred to as an information processing device. When there is no need to distinguish between Server 10 and terminal 20, Server 10 and terminal 20 may each be referred to as an information processing device, or may not be.

[0074] [Hardware (HW) Configuration of Each Device] The HW configuration of each device included in communication system 1 will be described.

[0075] (1) HW Configuration of the Terminal FIG. 2-1 shows an example of the HW configuration of terminal 20. Terminal 20 includes a control unit 21 (CPU: central processing unit), a storage unit 28, a communication I / F 22 (interface), an input / output unit 23, a display unit 24, a microphone 25, a speaker 26, a camera 27, a clock unit 29A, and a position calculation information detection unit 29B. Each component of the HW of terminal 20 is interconnected via a bus B, by way of example and not limitation. Note that it is not essential to include all components as the HW configuration of terminal 20. By way of example and not limitation, terminal 20 may be configured to remove individual components such as microphone 25 and camera 27, or a plurality of components, or not.

[0076] The communication I / F 22 transmits and receives various data via the network 30. The communication may be performed either by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be executed. The communication I / F 22 has a function of executing communication with various devices such as the server 10 via the network 30. The communication I / F 22 transmits various data to various devices such as the server 10 according to an instruction from the control unit 21. Further, the communication I / F 22 receives various data transmitted from various devices such as the server 10 and transmits them to the control unit 21. Also, the communication I / F 22 may be simply referred to as a communication unit. Further, when the communication I / F 22 is composed of a physically structured circuit, it may be referred to as a communication circuit.

[0077] The input / output unit 23 includes a device for inputting various operations to the terminal 20 and a device for outputting a processing result processed by the terminal 20. The input / output unit 23 may have an integrated input unit and output unit, may be separated into an input unit and an output unit, or may not be so.

[0078] The input unit is realized by any one or a combination of all types of devices that can receive an input from a user and transmit information related to the input to the control unit 21. The input unit includes, by way of example and not limitation, hardware keys such as a touch panel, a touch display, a keyboard, a pointing device such as a mouse, a camera (operation input via a moving image), and a microphone (operation input by voice).

[0079] The output unit is realized by any one or a combination of all types of devices that can output a processing result processed by the control unit 21. The output unit includes, by way of example and not limitation, a touch panel, a touch display, a speaker (voice output), a lens (3D (three dimensions) output or hologram output by way of example and not limitation), a printer, and the like.

[0080] The display unit 24 is realized by any one or a combination of all types of devices that can display according to the display data written in the frame buffer. The display unit 24 includes, by way of example and not limitation, a touch panel, a touch display, a monitor (by way of example and not limitation, a liquid crystal display or an OELD (organic electroluminescence display)), a head-mounted display (HDM: Head Mounted Display), projection mapping, a hologram, a device that can display image, text information, etc. in the air (it may or may not be a vacuum). Note that these display units 24 may or may not be able to display display data in 3D.

[0081] When the input / output unit 23 is a touch panel, the input / output unit 23 and the display unit 24 may be arranged to face each other with substantially the same size and shape.

[0082] The clock unit 29A is the built-in clock of the terminal 20 and outputs time information (timing information). The clock unit 29A is configured to have, by way of example and not limitation, a clock using a crystal oscillator. The clock unit 29A can also be expressed as, by way of example and not limitation, a timing unit or a time information detection unit.

[0083] Note that the clock unit 29A may or may not have a clock that applies the NITZ (Network Identity and Time Zone) standard or the like.

[0084] The position calculation information detection unit 29B is a functional unit that detects (measures) information (hereinafter referred to as "position calculation information") necessary for the control unit 21 to calculate (measure) the position of its own terminal 20. The position calculation information detection unit 29B can also be expressed as, by way of example and not limitation, a position calculation sensor unit.

[0085] The position calculation information detection unit 29B includes, by way of example and not limitation, a satellite positioning sensor (satellite positioning unit), which is a sensor or unit for calculating the position of the terminal 20 using a satellite positioning system such as GPS (Global Positioning System), and an inertial measurement sensor (inertial measurement unit (IMU (Inertial Measurement Unit))), which is a sensor or unit for calculating the position of the terminal 20 using an inertial navigation system.

[0086] The satellite positioning unit includes, by way of example and not limitation, an RF receiving circuit that converts an RF (Radio Frequency) signal including a positioning satellite signal transmitted from a positioning satellite received by an antenna (not shown) into a digital signal, and a baseband processing circuit that performs correlation operation processing and the like on the digital signal output from the RF receiving circuit to capture the positioning satellite signal and outputs information such as satellite orbit data and time data extracted from the positioning satellite signal as position calculation information.

[0087] The inertial measurement unit has an inertial sensor, which is a sensor for detecting information necessary for calculating the position of the terminal 20 by inertial navigation calculation. The inertial sensor includes, by way of example and not limitation, a three-axis acceleration sensor and a three-axis gyro sensor, and outputs the acceleration detected by the acceleration sensor and the angular velocity detected by the gyro sensor as position calculation information.

[0088] The control unit 21 calculates the position of its own terminal 20 at regular timings or specific timings based on the position calculation information detected by the position calculation information detection unit 29B, by way of example and not limitation. The position of the terminal is referred to as the "terminal position", and the calculated terminal position is referred to as the "calculated terminal position". Then, the control unit 21 associates the calculated terminal position with the date and time when the calculated terminal position was calculated and stores it in the storage unit 28 as calculated terminal position history data.

[0089] The control unit 21 has a circuit physically structured to execute functions realized by codes or instructions included in a program, and is realized by, as an example but not limited to, a data processing device built into hardware. Therefore, the control unit 21 may or may not be expressed as a control circuit.

[0090] The control unit 21 includes, as an example but not limited to, a central processing unit (CPU), a microprocessor, a processor core, a multiprocessor, an application-specific integrated circuit (ASIC), and a field programmable gate array (FPGA).

[0091] The storage unit 28 has a function of storing various programs and various data required for the operation of the terminal 20. The storage unit 28 includes various storage media such as, as an example but not limited to, a hard disk drive (HDD), a solid state drive (SSD), a flash memory, a random access memory (RAM), and a read only memory (ROM). Also, the storage unit 28 may or may not be expressed as a memory.

[0092] The terminal 20 stores the program P in the storage unit 28 and, by executing this program P, the control unit 21 executes processes as each part included in the control unit 21. That is, the program P stored in the storage unit 28 causes the terminal 20 to realize each function executed by the control unit 21. Also, this program P may or may not be expressed as a program module.

[0093] The microphone 25 is used for input of audio data. The speaker 26 is used for output of audio data. The camera 27 is used for acquisition of moving image data.

[0094] (2) HW Configuration of the Server FIG. 2-1 shows an example of the HW configuration of server 10. Server 10 includes a control unit 11 (CPU), a storage unit 15, a communication I / F 14 (interface), an input / output unit 12, a display 13, and a clock unit 19. Each component of the HW of server 10 is interconnected via bus B as an example, not a limitation. Note that it is not essential for the HW of server 10 to include all components as the configuration of the HW of server 10. As an example, not a limitation, the HW of server 10 may or may not be configured to remove display 13.

[0095] The control unit 11 has a circuit physically structured to execute functions realized by codes or instructions included in a program, and is realized by, for example, not a limitation, a data processing device built into hardware.

[0096] The control unit 11 is typically a central processing unit (CPU), and may alternatively be a microprocessor, a processor core, a multiprocessor, an ASIC, an FPGA, etc., or not. In the present disclosure, the control unit 11 is not limited thereto.

[0097] The storage unit 15 has a function of storing various programs and various data required for the operation of server 10. The storage unit 15 is realized by various storage media such as HDD, SSD, and flash memory. However, in the present disclosure, the storage unit 15 is not limited thereto. Also, the storage unit 15 may or may not be expressed as a memory.

[0098] The communication I / F 14 transmits and receives various data via the network 30. The communication may be performed either by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be executed. The communication I / F 14 has a function of communicating with various devices such as the terminal 20 via the network 30. The communication I / F 14 transmits various data to various devices such as the terminal 20 according to an instruction from the control unit 11. Further, the communication I / F 14 receives various data transmitted from various devices such as the terminal 20 and transmits it to the control unit 11. Further, the communication I / F 14 may sometimes be simply expressed as a communication unit. Further, when the communication I / F 14 is composed of a physically structured circuit, it may sometimes be expressed as a communication circuit.

[0099] The input / output unit 12 is realized by a device that inputs various operations to the server 10. The input / output unit 12 is realized by any one or a combination of all types of devices that can receive an input from a user and transmit information related to the input to the control unit 11. The input / output unit 12 is typically realized by a hardware key typified by a keyboard or the like, or a pointing device such as a mouse. Note that the input / output unit 12 may or may not include, by way of example and not limitation, a touch panel, a camera (operation input via a moving image), a microphone (operation input by voice). However, in the present disclosure, the input / output unit 12 is not limited thereto.

[0100] The display 13 is typically realized by a monitor (by way of example and not limitation, a liquid crystal display or an OELD (organic electroluminescence display)). Note that the display 13 may or may not be a head-mounted display (HDM) or the like. Note that these displays 13 may or may not be able to display display data in 3D. In the present disclosure, the display 13 is not limited thereto.

[0101] The clock unit 19 is the built-in clock of the server 10 and outputs time information (timing information). The clock unit 19 is configured to have, by way of example and not limitation, an RTC (Real Time Clock) as a hardware clock, a system clock, and the like. The clock unit 19 can also be expressed as a timing unit or a time information detection unit, by way of example and not limitation.

[0102] (3) Others The server 10 stores the program P in the storage unit 15 and, by executing this program P, the control unit 11 executes the processes as each unit included in the control unit 11. That is, the program P stored in the storage unit 15 causes the server 10 to realize each function executed by the control unit 11. This program P may or may not be expressed as a program module. The same applies to other devices.

[0103] In each embodiment of the present disclosure, it will be described as being realized by the CPU of the terminal 20 and / or the server 10 executing the program P. The same applies to other devices.

[0104] Note that the control unit 21 of the terminal 20 and / or the control unit 11 of the server 10 may or may not realize each process by a logic circuit (hardware) formed in an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)), etc., or a dedicated circuit, in addition to a CPU having a control circuit. Further, these circuits may be realized by one or a plurality of integrated circuits, and it may or may not be the case that a plurality of processes shown in each embodiment are realized by one integrated circuit. Also, LSI may sometimes be referred to as VLSI, super LSI, ultra LSI, etc., depending on the degree of integration. Therefore, the control unit 21 may or may not be expressed as a control circuit. The same applies to other devices.

[0105] Also, the program P (by way of example and not limitation, a software program, a computer program, or a program module) of each embodiment of the present disclosure may or may not be provided in a state stored in a computer-readable storage medium. The storage medium can store the program P in a "non-transitory tangible medium". Also, the program P may or may not be for realizing a part of the functions of each embodiment of the present disclosure. Further, it may or may not be a so-called difference file (difference program) that can realize the functions of each embodiment of the present disclosure in combination with a program P already recorded in the storage medium.

[0106] The storage medium can include one or more semiconductor-based or other integrated circuits (ICs) (by way of example and not limitation, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC)), a hard disk drive (HDD), a hybrid hard drive (HHD), an optical disk, an optical disk drive (ODD), a magneto-optical disk, a magneto-optical drive, a floppy disk, a floppy disk drive (FDD), a magnetic tape, a solid state drive (SSD), a RAM drive, a secure digital card, or a drive, any other suitable storage medium, or a suitable combination of two or more of these. The storage medium can be volatile, non-volatile, or a combination of volatile and non-volatile, as appropriate. Note that the storage medium is not limited to these examples, and any device or medium can be used as long as it can store the program P. Also, the storage medium may or may not be expressed as a memory.

[0107] The server 10 and / or the terminal 20 can realize the functions of the plurality of functional units shown in each embodiment by reading out the program P stored in the storage medium and executing the read program P. The same applies to other devices.

[0108] Furthermore, the program P of the present disclosure may or may not be provided to the server 10 and / or the terminal 20 via any transmission medium capable of transmitting a program (such as a communication network or broadcast waves). The server 10 and / or the terminal 20, by way of example and not limitation, executes the program P downloaded via the Internet or the like to realize the functions of the multiple functional units shown in each embodiment. The same applies to other devices.

[0109] In addition, each embodiment of the present disclosure may also be realized in the form of a data signal in which the program P is embodied by electronic transmission. At least a part of the processing in the server 10 and / or the terminal 20 may or may not be realized by cloud computing configured by one or more computers. At least a part of the processing in the terminal 20 may or may not be performed by the server 10. In this case, at least a part of the processing of each functional unit of the control unit 21 of the terminal 20 may or may not be performed by the server 10. At least a part of the processing in the server 10 may or may not be performed by the terminal 20. In this case, at least a part of the processing of each functional unit of the control unit 11 of the server 10 may or may not be performed by the terminal 20. Unless explicitly stated otherwise, the judgment configuration in the embodiments of the present disclosure is not essential, and a predetermined process may or may not be performed when the judgment condition is met, or when the judgment condition is not met.

[0110] The programs of the present disclosure are implemented using, for example and without limitation, scripting languages such as ActionScript and JavaScript (registered trademark), compiler languages such as Objective-C and Java (registered trademark), and markup languages such as HTML5.

[0111] <Functional configuration> (1) Functional configuration of the server FIG. 2-2 is a diagram showing an example of functions realized by the control unit 11 of the server 10 in this embodiment.

[0112] As a function realized by the control unit 11, the server 10 has, by way of example and not limitation, a payment application management processing unit 111.

[0113] The payment application management processing unit 111 has a function of executing processing for managing various types of information / data related to the payment application executed on the terminal 20 and managing the settlement by electronic money of the terminal 20 or the user of the terminal 20 in accordance with the payment application management processing program 151 stored in the storage unit 15.

[0114] FIG. 2-3 is a diagram showing an example of information stored in the storage unit 15 of the server 10 in this embodiment. Stored in the storage unit 15 as a program, by way of example and not limitation, is a payment application management processing program 151 that is read out by the control unit 11 and executed as payment application management processing.

[0115] Also stored in the storage unit 15 as data, by way of example and not limitation, are payment application user registration data 153 and a user management database 155.

[0116] The payment application user registration data 153 is registration data related to the terminal 20 that uses the payment application or the user of that terminal 20, and an example of its data configuration is shown in FIG. 2-4. Stored in the payment application user registration data 153, by way of example and not limitation, are a user name, a payment application ID, a terminal phone number, and other registration information, which are stored in association with each other.

[0117] The user name is the name of the user of the terminal 20 that uses the payment application. By way of example and not limitation, the name registered by the user of the terminal 20 when using the payment application is stored.

[0118] The payment application ID is the account (account information) of the payment application and is an ID that can identify the terminal 20 or the user of the terminal 20. By way of example and not limitation, a unique ID is set and stored by the server 10 for this payment application ID.

[0119] The terminal phone number is the phone number of the terminal 20 of the user with this user name. By way of example and not limitation, the phone number of the terminal 20 registered by the user of the terminal 20 when using the payment application is stored.

[0120] Other registration information may include, by way of example and not limitation, the email address (terminal email address) of the terminal 20 of the user with this user name, authentication information such as an authentication password used for various authentications in the payment application, image data of an icon (icon image) used by this user, a user profile (user profile), and the like. However, these pieces of information are not essential.

[0121] The user management database 155 is a database for managing users based on the accounts (account information) stored in the payment application user registration data 153. A configuration example of a first user management database 155A, which is an example thereof, is shown in FIG. 2-5. In the first user management database 155A, user management data is stored as management data for each payment application ID stored in the payment application user registration data 153.

[0122] Each user management data stores, by way of example and not limitation, a payment application ID, an electronic money account balance, and shopping settlement history data.

[0123] The electronic money account balance is the balance of the account of the electronic money available in the payment service, which is associated with this payment application ID. The electronic money account balance can also be expressed as the electronic money account balance.

[0124] The shopping settlement history data is the data of the shopping settlement history (shopping settlement history information) associated with this payment application ID. By way of example and not limitation, the shopping settlement ID, which is an ID for uniquely identifying the shopping settlement history, the store ID, which is an ID for uniquely identifying the store where the shopping settlement was made, the store name of the store with that store ID, the shopping settlement date and time, and the shopping settlement amount are stored in association with each other.

[0125] (2) Functional configuration of the terminal FIG. 2-6 is a diagram showing an example of the functions realized by the control unit 21 of the terminal 20 in this embodiment.

[0126] As a function realized by the control unit 21, the terminal 20 has, by way of example and not limitation, a payment application processing unit 211.

[0127] The payment application processing unit 211 has a function of executing payment application processing in accordance with the payment application program 281 stored in the storage unit 28.

[0128] FIG. 2-7 is a diagram showing an example of the information stored in the storage unit 28 of the terminal 20 in this embodiment. Stored in the storage unit 28 as a program is, by way of example and not limitation, a payment application program 281 that is read out by the control unit 21 and executed as payment application processing.

[0129] Also stored in the storage unit 28 as data is, by way of example and not limitation, payment application account data 283, which is the data of the account of the payment application.

[0130] <Example display screen>

[0131] In the following example, it is assumed that user A.A becomes the "split payment master (split payment requester)" and conducts split payments with other users. Note that the split payment master, by way of example and not limitation, shall mean the user who first proposed to conduct a split payment.

[0132] FIG. 2-8 is a diagram showing an example of the menu screen of the payment application in this embodiment, and shows an example of the screen displayed on the display unit 24 of the terminal 20 of user A.A. On this menu screen, the characters "Payment App" are displayed at the upper part of the screen, and beside it, the user name of the user of the own terminal 20 (in this example, "user A.A") is displayed.

[0133] Further, below it, an electronic money account display area is provided, which includes the balance of the electronic money account stored and managed by the server 10 in association with the account of this user name, and a charge button for charging electronic money into the electronic money account.

[0134] Also, below the electronic money account display area, a function icon display area is provided, which includes function icons corresponding to each of a plurality of functions for executing processes based on the plurality of functions provided as functions of the payment application.

[0135] The function icon display area includes, by way of example and not limitation, a "deposit icon" for making a deposit, a "code payment icon" for making a payment using a code (such as a one-dimensional code or a two-dimensional code) displayed on the display unit 24 of the terminal 20, a "code reader icon" for making a payment by reading a code (such as a one-dimensional code or a two-dimensional code) installed in a store for purchasing goods or receiving services, a "remittance icon" for remitting money to a user of another terminal 20 (another account), a "split payment icon" for conducting split payments with a user of another terminal 20 (another account), and a plurality of other function icons.

[0136] FIG. 2-9 is a diagram showing an example of a split-bill member selection screen that is displayed when the split-bill icon is operated (by touch operation, as an example and not by way of limitation) on the menu screen.

[0137] The bill splitting member selection screen is a screen for selecting bill splitting members. A split-bill member is a user who participates in a split-bill, and in this specification, a split-bill master is also included in the split-bill members.

[0138] The bill splitting member selection screen in FIG. 2-9 is a screen for the bill splitting master (user AA in this example) to select bill splitting members other than himself. In the initial state, no other members are selected to split the bill with other users, so the message "There are no members to split the bill with" is displayed on the screen as an example, not a limitation. At the bottom of the screen, a "search icon" for searching for members to split the bill with is displayed, and by operating this search icon, it is possible to search for members to split the bill with.

[0139] FIG. 2-10 is a diagram showing an example of a split-bill member search screen that is displayed when the search icon is operated (by touch operation, as an example and not by way of limitation) on the split-bill member selection screen. This split-bill member search screen is a screen for the split-bill master to search for split-bill members other than himself, and displays the words "Enter phone number to search" as an example, but not as a limitation. Below that, a phone number input field for entering a phone number is displayed, along with a search execution button for searching for the terminal 20 (user of that terminal 20) with the entered phone number.

[0140] In this example, the phone number "080XXXXXXXX" is entered and displayed in the phone number input field. Then, when the search execution button is clicked, the server 10 performs a search, and the state where "User B.B" is obtained as the search result is shown. Also, below the search results, an "Add icon" for adding the users obtained as search results to the split payment members is displayed. By operating this add icon, the users obtained as search results are added to the split payment members by the server 10.

[0141] FIG. 2-11 is a diagram showing an example of a split payment member selection screen displayed based on the addition of split payment members by the search on the above split payment member search screen. This split payment member selection screen corresponds to the screen in FIG. 2-9, and based on the above search results, a list of users added as candidates for split payment members (hereinafter referred to as "split payment member candidates") is displayed. In this example, the state where "User B.B", "User C.C", "User D.D", and "User E.E" are added as split payment member candidates is shown.

[0142] Also, a checkbox is associated and displayed for each split payment member candidate. In the initial state, the checks for all split payment member candidates are set to "ON". By operating the corresponding checkbox, it is possible to switch the check between "ON" and "OFF", and by setting the check to "OFF", it is possible to exclude the split payment member candidate from the split payment members.

[0143] Also, in this example, in addition to the search icon shown in FIG. 2-9, a shopping payment history registration icon shown as "Register payment portion" (not limited to this, but as an example) for User A.A to register their shopping payment history as a split payment target is displayed.

[0144] FIG. 2-12 is a diagram showing an example of a shopping settlement history selection screen that is displayed based on the operation (touch operation as an example, not limited to this) of the shopping settlement history registration icon on the share calculation member selection screen of FIG. 2-11. On this shopping settlement history selection screen, a plurality of shopping settlement histories for the user of this terminal 20 are displayed. Specifically, as an example, not limited to this, as the shopping settlement history, the shopping settlement date and time, the store name, and the shopping settlement amount are displayed. In this example, shopping settlement histories of a plurality of stores such as "AA Rental Cycle", "BB Supermarket", and "CC Bento" are displayed.

[0145] In addition, a check box is provided in association with each shopping settlement history, and by operating the corresponding check box, it is possible to switch the check "ON / OFF". It is not limited to one shopping settlement history, and it is possible to set the checks of a plurality of shopping settlement histories to "ON", and the shopping settlement histories with the check set to "ON" are used as the share calculation targets, and it is configured to be possible to make a share calculation request (hereinafter referred to as a "share calculation request").

[0146] More specifically, a share calculation request icon shown as "Send a share calculation request" as an example, not limited to this, for making a share calculation request with the shopping settlement history with the check set to "ON" as the share calculation target is displayed at the bottom of the screen. When this share calculation request icon is operated, it is configured to be possible to send a share calculation request from its own terminal 20 to the previously selected share calculation member's terminal 20 via the server 10.

[0147] In this example, the checks for the shopping settlement histories of "AA Rent-a-Bicycle" and "BB Supermarket" are set to "ON", and it is shown that the user A.A has selected these two shopping settlement histories to be subject to splitting the bill. In this case, the amount already paid by the user A.A is the total of the shopping settlement amount of "1,500 yen" for "AA Rent-a-Bicycle" and the shopping settlement amount of "3,000 yen" for "BB Supermarket", which is "4,500 yen", and this amount of "4,500 yen" already paid by the user A.A will be split.

[0148] FIG. 2-13 is a diagram showing an example of a bill-splitting request notification screen that is displayed on the display unit 24 of the terminal 20 of a bill-splitting member other than the user A.A based on the operation (a touch operation as an example, not a limitation) of the bill-splitting request icon on the shopping settlement history selection screen of FIG. 2-12. This bill-splitting request notification screen is a screen that is displayed on the display unit 24 of the terminal 20 of the user B.B selected by the user A.A as a bill-splitting member, and is an example of a screen within the payment application executed on this terminal 20.

[0149] In this example, as an example, not a limitation, the characters "A request for bill splitting has been received from Mr. / Ms. A.A" are displayed, and below that, an over / under amount display area for displaying the over / under amount of the user B.B is provided. In this embodiment, the over / under amount for each bill-splitting member is calculated by the server 10 as will be described later.

[0150] In the over / under amount display area, as an example, not a limitation, a mark for identifying the type (receiving / paying) of the over / under amount is displayed together with the over / under amount of the user B.B. In this example, it is displayed as "￥900 Pay", indicating that the user B.B needs to pay "900 yen" to the user A.A.

[0151] As described above, the type (receiving / paying) of the over / under amount is determined by the positive / negative sign of the calculated over / under amount. The reason for using the expression "payment" is that, in addition to the case of paying the over / under amount with electronic money, as will be described in detail later, the case of paying the over / under amount in cash is also assumed. That is, "payment" includes payment with electronic money (=remittance) and payment in cash (=cash payment). Note that, without considering cash payment, it is also possible to use "remittance" instead of "payment", or not to do so.

[0152] At the bottom of the screen, there are displayed an "Settlement Icon" labeled "Settlement" as an example (not limited) for performing split settlement based on the above over / under amount, and a "Rejection Icon" labeled "Reject Split" as an example (not limited) for rejecting a split request.

[0153] When the settlement icon is operated, if the type of the over / under amount of the user is "payment", the over / under amount is remitted from the user's terminal 20 to the terminal 20 of the recipient user. On the other hand, if the type of the over / under amount of the user is "receipt", the over / under amount is received by the user's terminal 20.

[0154] However, the remittance / receipt in this embodiment is realized by the server 10 updating the balance of the electronic money account associated with the payment application ID of the user. That is, if the type of the over / under amount of the user is "payment", an amount corresponding to the over / under amount is subtracted / updated from the balance of the electronic money account associated with the payment application ID of the user. On the other hand, if the type of the over / under amount of the user is "receipt", an amount corresponding to the over / under amount is added / updated to the balance of the electronic money account associated with the payment application ID of the user.

[0155] In this example, since user B.B is the one who pays the amount, when the settlement icon is operated, 900 yen is remitted to the terminal 20 of user A.A by electronic money. More specifically, the server 10 subtracts / updates 900 yen from the balance of the electronic money account of the payment application ID of user B.B.

[0156] Note that, in reality, the server 10 adds and updates the subtracted amount of 900 yen to the electronic money account balance of the payment application ID of user A.A. However, in this embodiment, the update of the electronic money account balance of user A.A is executed by the server 10 based on the operation of the settlement icon on the terminal 20 of user A.A.

[0157] FIG. 2-14 is a diagram showing an example of an over / under amount display screen displayed on the display unit 24 of the terminal 20 of user A.A based on the operation (a touch operation as an example, not limited) of the split payment request icon on the shopping settlement history selection screen of FIG. 2-12. In this example, as an example and not limited, the characters "Calculation of over / under amount has been performed" are displayed, and below that, an over / under amount display area for displaying the over / under amount of user A.A is provided. In this example, "Received 3,600 yen" is displayed as the over / under amount of user A.A. That is, it is displayed that user A.A will receive a total of "3,600 yen" from other split payment members.

[0158] In this example, since user A.A is on the receiving side of money, when the settlement icon is operated, an amount of "3,600 yen" is received on the terminal 20 of user A.A. Specifically, 3,600 yen, which is the total amount subtracted from the electronic money account balances of each of the other split payment members, is added and updated by the server 10 to the electronic money account balance associated with the payment application ID of user A.A.

[0159] FIG. 2-15 is a diagram showing an example of a receipt notification screen displayed on the display unit 24 of the terminal 20 of user A.A. On this receipt notification screen, for each split payment member other than oneself (in this example, four members: "user B.B", "user C.C", "user D.D", and "user E.E"), a receipt completion notification associated with the transfer amount from that member and the date and time of the transfer (transfer date and time) is displayed.

[0160] FIG. 2-16 is a diagram showing an example of a split payment completion notice displayed on the reception notice screen of FIG. 2-15. By way of example and not limitation, after the display area of the reception notice screen in FIG. 2-15 is touched with a user's finger and a scroll-up operation is performed, the split payment completion notice displayed at the bottom of the screen appears in the display area. In this example, a split payment completion notice including the text "Split payment completed" and the settlement result (in this example, "3,600 yen received", the amount already paid by oneself "4,500 yen", the total payment amount of all members "4,500 yen", and the amount per person "900 yen") is displayed.

[0161] <Process> FIGS. 2-17 to 2-19 are flowcharts showing an example of the processing flow executed by each device in this embodiment. In order from the left, there are shown an example of the split payment processing executed by the control unit 21 of terminal A (by way of example and not limitation, the terminal 20 of user A.A), an example of the split payment processing executed by the control unit 21 of terminal B (by way of example and not limitation, the terminal 20 of user B.B), and an example of the split payment management processing executed by the control unit 11 of server 10, respectively.

[0162] By way of example, the terminal 20 of the split payment master is described as the terminal 20 of user A.A (terminal A), and the terminal 20 of the user who is requested to make a split payment from the split payment master is described as the terminal 20 of user B.B (terminal B). In actuality, the terminal 20 of the user who is requested to make a split payment from the split payment master is not necessarily one, but since the processing is the same as that of terminal B, the illustration is omitted.

[0163] Note that this processing is merely an example of the processing for realizing the method of the present disclosure and is not limited to this processing. Another step may be added to this processing, or some steps may be omitted (deleted). Note that the same applies to the processing described in each embodiment.

[0164] First, the control unit 21 of terminal A transmits member request information for requesting information on the split payment members (split payment member information) to server 10 via communication I / F 22 (A110). When receiving the member request information from terminal A via communication I / F 14 (S110), the control unit 11 of server 10 searches for the requested member information and transmits it to terminal A via communication I / F 14 (S120).

[0165] When receiving the member information from server 10 via communication I / F 22 (A120), the control unit 21 of terminal A causes the display unit 24 to display split payment member candidates based on the received member information. Then, the control unit 21 of terminal A executes a first member selection process for selecting split payment members based on a selection operation of the split payment members on the input / output unit 23 (A130). Then, the control unit 21 of terminal A transmits member selection information including the selection result of the split payment members to server 10 via communication I / F 22 (A140). Server 10 receives the member selection information from terminal A via communication I / F 14 (S140).

[0166] Thereafter, the control unit 21 of terminal A transmits shopping settlement history request information for requesting a shopping settlement history corresponding to the shopping settlement by the user of its own terminal 20 to server 10 via communication I / F 22 according to an operation on the input / output unit 23 (A150).

[0167] Here, in this embodiment, the shopping settlement history of each user of terminal 20 is stored and managed in the storage unit 15 of server 10 as described above and is not stored in the storage unit 28 of terminal 20. This is to prevent the shopping settlement history from being falsified or the like on the terminal 20 side. Therefore, in A150, in order to display the shopping settlement history on terminal 20, the shopping settlement history is requested from terminal 20 to server 10.

[0168] When receiving shopping settlement history request information from terminal A (S150), the control unit 11 transmits, via the communication I / F 22 to terminal A, a plurality of shopping settlement histories included in the shopping settlement history data of the user management data of the payment application ID of user A.A among the user management data included in the user management database 155 (S160).

[0169] When receiving a shopping settlement history from server 10 (A160), the control unit 21 of terminal A performs a second shopping settlement history selection process (A170). Specifically, by way of example and not limitation, the received plurality of shopping settlement histories are displayed in a list on the display unit 24. Then, at least one shopping settlement history is selected according to a selection operation on the input / output unit 23.

[0170] Thereafter, the control unit 21 of terminal A transmits, via the communication I / F 22 to server 10, shopping settlement history selection information, by way of example and not limitation (A180). Here, the shopping settlement history selection information transmitted from terminal 20 to server 10 may be information that can identify the selected shopping settlement history on the server 10 side. Specifically, as an example, it is possible to transmit the shopping settlement ID corresponding to the selected shopping settlement history. Also, as another example, it is also possible to transmit the selected shopping settlement history itself.

[0171] When receiving shopping settlement history selection information from terminal A (S180), the control unit 11 calculates the overage and shortage amounts of each split payment member based on the member selection information received in S140 and the shopping settlement history selection information received in S180 (S190).

[0172] Thereafter, the control unit 11 transmits, via the communication I / F 14, a split payment settlement request notice including the overage and shortage amounts calculated in S190 to each of terminal A and terminal B (S210).

[0173] When receiving a joint settlement request notification from server 10 (A210), the control unit 21 of terminal A causes the display unit 24 to display, by way of example and not limitation, the over / under amount included in the joint settlement request notification. Then, the control unit 21 of terminal A transmits, via the communication I / F 22, a joint settlement approval notification for notifying approval of joint settlement to server 10 in accordance with an operation on the input / output unit 23 (A230).

[0174] On the other hand, when receiving a joint settlement request notification from server 10 (B210), the control unit 21 of terminal B causes the display unit 24 to display, by way of example and not limitation, the over / under amount included in the joint settlement request notification. Then, the control unit 21 of terminal A determines whether user B.B has agreed to the joint settlement (B220). Specifically, by way of example and not limitation, it is determined whether an operation indicating an intention to agree to the joint settlement (by way of example and not limitation, an operation on the aforementioned "settlement icon") has been performed. If an operation indicating an intention to reject the joint settlement (by way of example and not limitation, an operation on the aforementioned "reject icon") has been performed, it is determined that the joint settlement is not agreed to.

[0175] If it is determined that the joint settlement is agreed to (B220: YES), the control unit 21 of terminal B transmits, via the communication I / F 22, a joint settlement approval notification for notifying approval of joint settlement to server 10 (B230). On the other hand, if it is determined that the joint settlement is not agreed to (B220: NO), the control unit 21 of terminal B transmits, via the communication I / F 22, a joint settlement rejection notification for notifying non-approval (rejection) of joint settlement to server 10 (B240).

[0176] After S210, the control unit 11 executes a first joint settlement approval management process (S230).

[0177] FIG. 2-20 is a flowchart showing an example of the flow of the first joint settlement approval management process. In this process, the joint settlement notification is either the aforementioned "joint settlement approval notification" or "joint settlement rejection notification".

[0178] When the control unit 11 receives a split payment settlement notice from the terminal 20 (S2310), it determines whether the received split payment settlement notice is a "split payment settlement rejection notice" (S2320). If it is determined that it is a split payment settlement rejection notice (S2320: YES), the control unit 11 determines that the split payment is not established (S2330) and ends the first split payment approval management process.

[0179] On the other hand, if it is determined that the received split payment settlement notice is not a "split payment settlement rejection notice" (i.e., it is a "split payment settlement approval notice") (S2320: NO), the control unit 11 determines whether it has received split payment settlement approval notices from all target terminals (S2340).

[0180] Here, the "target terminal" is the terminal 20 for which the server 10 is scheduled to receive a split payment settlement notice. In this example, both terminal A and terminal B are target terminals. Basically, the terminals 20 of all split payment members are target terminals, but even split payment members may be excluded from the target terminals. This will be described in detail in the embodiments described later.

[0181] If it is determined that split payment settlement approval notices have not been received from at least one target terminal (S2340: NO), the control unit 11 returns the process to S2310.

[0182] On the other hand, if it is determined that split payment settlement approval notices have been received from all target terminals (S2340: YES), the control unit 11 determines, for each target terminal, whether the amount that the user of that target terminal pays by split payment is equal to or more than the electronic money account balance associated with that user's payment application ID (S2350). If this condition is not met (S2350: NO), the control unit 11 moves the process to S2330.

[0183] On the other hand, when it is determined that the conditions of S2350 are satisfied (S2350: YES), the control unit 11 determines that the split payment is established (S2360). That is, when the balance of the electronic money accounts of the users of all target terminals does not become negative, it is determined that the split payment is established. Then, the control unit 11 ends the first split payment approval management process.

[0184] Returning to the process of FIG. 2-18, if it is determined that the split payment is established in the first split payment approval management process (S310: YES), the control unit 11 transmits a split payment establishment notice to each of the terminal A and the terminal B via the communication I / F 22 (S310).

[0185] On the other hand, if it is determined that the split payment is not established in the first split payment approval management process (S310: NO), the control unit 11 transmits a split payment non-establishment notice to each of the terminal A and the terminal B via the communication I / F 22 (S250).

[0186] After A230, the control unit 21 of the terminal A determines whether it has received a split payment non-establishment notice from the server 10 via the communication I / F 22 (A250). Similarly, after B240, the control unit 21 of the terminal B determines whether it has received a split payment non-establishment notice from the server 10 via the communication I / F 22 (B250).

[0187] If the terminal A does not receive a split payment non-establishment notice from the server 10 at A250 (A250: NO), the terminal A will receive a split payment establishment notice from the server 10 (A310). In this case, the control unit 21 of the terminal A executes a split payment settlement request process of transmitting information for requesting split payment settlement (hereinafter referred to as "split payment settlement request information") to the server 10 via the communication I / F 22 (A320).

[0188] Similarly, if the terminal B does not receive a split payment non-establishment notice from the server 10 at B250 (A250: NO), the terminal B will receive a split payment establishment notice from the server 10 (B310). In this case, the control unit 21 of the terminal B transmits split payment settlement request information to the server 10 via the communication I / F 22 (B320).

[0189] When the control unit 11 receives the split payment settlement request information from each of the terminal A and the terminal B (S320), the control unit 11 executes a split payment settlement process (S330). Specifically, by way of example and not limitation, an amount corresponding to the user's overage / shortage amount is added (when receiving money) / subtracted (when paying money) to / from the balance of the electronic money account with the payment application ID associated with the user.

[0190] The split payment settlement process in this embodiment is an example of a money transfer process / receiving process executed by the control unit 11 of the server 10.

[0191] Thereafter, the control unit 11 transmits the split payment settlement result to each of the terminal A and the terminal B via the communication I / F 14 (S340).

[0192] The terminal 20 executes a split payment settlement result receiving process of receiving the split payment settlement result from the server 10 via the communication I / F 22.

[0193] Specifically, when the control unit 21 of the terminal A receives the split payment settlement result from the server 10 via the communication I / F 22 (A340), the control unit 21 of the terminal A causes the received split payment settlement result to be displayed on the display unit 24 (A350). Similarly, when the control unit 21 of the terminal B receives the split payment settlement result from the server 10 via the communication I / F 22 (B340), the control unit 21 of the terminal B causes the received split payment settlement result to be displayed on the display unit 24 (B350).

[0194] Here, the split payment settlement result includes, by way of example and not limitation, at least one of the aforementioned receipt completion notification and the split payment completion notification. Both the receipt completion notification and the split payment completion notification may be used as the split payment settlement result, or only one of them may be used as the split payment completion notification.

[0195] In this embodiment, the split payment settlement request process and the split payment settlement result receiving process are examples of a money transfer process / receiving process executed by the control unit 21 of the terminal 20.

[0196] Thereafter, the control unit 21 of terminal A determines whether to end the process (A390). If it determines to continue the process (A390: NO), the process returns to A110. If it determines to end the process (A390: YES), the control unit 21 of terminal A ends the splitting calculation process.

[0197] Similarly, the control unit 21 of terminal B determines whether to end the process (B390). If it determines to continue the process (B390: NO), the process returns to B110. If it determines to end the process (B390: YES), the control unit 21 of terminal B ends the splitting calculation process.

[0198] Similarly, the control unit 11 determines whether to end the process (S390). If it determines to continue the process (S390: NO), the process returns to S110. If it determines to end the process (S390: YES), the control unit 11 ends the splitting management process.

[0199] In this embodiment, since the splitting settlement process is executed by the server 10, the terminal 20 does not directly send or receive money. However, since the splitting settlement process is executed by the server 10 based on the fact that the terminal 20 has executed the splitting settlement request process, it can also be said that the terminal 20 has executed the money sending process / receiving process.

[0200] <Effects of the Second Embodiment> In the second embodiment, based on an input to its own terminal 20 by the user of its own terminal 20 (not limited thereto, an example of an input to a terminal), the terminal 20 transmits a shopping settlement history (shopping settlement history selection information) (not limited thereto, an example of first settlement information) to the server 10 via the communication I / F 22 (not limited thereto, an example of a communication unit of a terminal). Also, the terminal 20 receives, via the communication I / F 22, information on the over / under amount of each user (not limited thereto, an example of at least the first amount among the first amount that the user of the terminal remits or receives and the second amount that the user of a terminal different from the terminal remits or receives) based on the transmitted shopping settlement history. Then, the terminal 20 shows a configuration in which, based on the over / under amount, the control unit 21 (not limited thereto, an example of a control unit of a terminal) executes a split settlement request process or a split settlement result reception process (not limited thereto, an example of a remittance process or a reception process based on the first amount). As an example of the effect obtained by such a configuration, based on transmitting the first settlement information based on the process related to the first settlement by the user of the terminal, the terminal can execute, by the control unit, a remittance process or a reception process based on the first amount, and can easily remit or receive money, improving the convenience for the user.

[0201] Also, in the second embodiment, the remittance process or the reception process based on the above first amount is a process including remittance to a user of a different terminal 20 (different accounts in the payment application) (not limited thereto, an example of a user of a different terminal) or reception from a user of a different terminal 20 (different accounts in the payment application). With such a configuration, it is possible to realize remittance to a user of a different terminal or reception of money from a user of a different terminal.

[0202] Further, in the second embodiment, the excess / deficiency amount (not limited to, for example, the first amount and the second amount) is determined by the server 10 (not limited to, for example, a server that executes settlement processing related to the first settlement) based on the shopping settlement history (not limited to, for example, the first settlement information) selected by the user of the terminal 20. As an example of the effect obtained by such a configuration, since it is not necessary to determine the first amount and the second amount at the terminal, the processing load on the terminal can be reduced.

[0203] Further, in the second embodiment, the server 10 determines the amount that each of a plurality of terminals 20 (not limited to, for example, the terminal 20 of the split payment master who is the user of the transmitting source and not limited to, for example, different terminals) including the terminal 20 of the split payment master who is the user of the transmitting source and the terminal 20 of other split payment members sends or receives based on the received shopping settlement history. As an example of the effect obtained by such a configuration, by transmitting the first settlement information, the terminal can cause the server to determine the amount that each of the terminal and a plurality of terminals including different terminals sends or receives.

[0204] Further, in the second embodiment, the server 10 receives, via the communication I / F 14, the shopping settlement history (shopping settlement history selection information) from the terminal 20 based on the input to the terminal 20 by the user of the terminal 20 (not limited to, for example, an example of the input to the terminal). Further, the server 10 transmits, via the communication I / F 14, information on at least the first excess / deficiency amount (not limited to, for example, an example of the first amount that the user of the terminal sends or receives based on the first settlement information) to the terminal 20, and transmits, via the communication I / F 14, information on at least the second excess / deficiency amount (not limited to, for example, an example of the second amount that the user of a terminal different from the terminal sends or receives based on the first settlement information) to a different terminal 20. Then, the server 10 shows a configuration for executing a split payment settlement process (not limited to, for example, an example of a remittance process or a receipt process based on the first amount and a remittance process or a receipt process based on the second amount) based on the first excess / deficiency amount and the second excess / deficiency amount. As an example of the effects obtained by such a configuration, based on receiving first settlement information based on processing related to a first settlement by a user of the terminal, the server causes the control unit to execute a remittance process or a receipt process based on a first amount and a remittance process or a receipt process based on a second amount, enabling the terminal to easily remit or receive money.

[0205] Further, in the second embodiment, among a plurality of shopping settlement histories (not limited thereto, an example of a plurality of settlement information) by the user of the own terminal 20, the terminal 20 transmits a shopping settlement history (not limited thereto, an example of the first settlement information) selected by the user of the own terminal 20 to the server 10 via the communication I / F 22 (not limited thereto, an example of a communication unit of the terminal). Further, the terminal 20 receives information on an excess / deficit amount (not limited thereto, an example of at least the first amount among the first amount that the user of the terminal remits or receives and the second amount that the user of a terminal different from the terminal remits or receives based on the first settlement information) based on the transmitted shopping settlement history from the server 10 via the communication I / F 22. Then, the terminal 20 shows a configuration in which, based on the excess / deficit amount, the control unit 21 (not limited thereto, an example of a control unit of the terminal) executes a split settlement request process or a split settlement result reception process (not limited thereto, an example of a remittance process or a receipt process based on the first amount). As an example of the effects obtained by such a configuration, based on transmitting the first settlement information among a plurality of settlement information related to settlement by the user of the terminal by the communication unit, the terminal causes the control unit to execute a remittance process or a receipt process based on information on the first amount based on the first settlement information, enabling the terminal to easily remit or receive money.

[0206] <Second Variant Example (1)> In the second embodiment, it is assumed that the shopping settlement history is stored and managed in the storage unit 15 of the server 10, but it is not limited thereto. Similar to the first embodiment, the shopping settlement history can be stored in the storage unit 28 of the terminal 20.

[0207] By way of example rather than limitation, when the server 10 performs shopping settlement processing, the shopping settlement information is transmitted to the terminal 20. Then, the terminal 20 stores the shopping settlement information received from the server 10 in the storage unit 28 as a shopping settlement history.

[0208] In this case, the terminal 20 can transmit the selected shopping settlement history from among the shopping settlement histories stored in the storage unit 28 to the server 10. This is the same for each embodiment including the server 10 as a constituent element.

[0209] <Second Modification Example (2)> In the second embodiment, although the settlement sharing processing is performed by the control unit 11 of the server 10, it is not limited to this. Specifically, by way of example rather than limitation, similar to the first embodiment, the settlement sharing processing may or may not be executed by the control unit 21 of the terminal 20. This is the same for each embodiment including the server 10 as a constituent element.

[0210] <Second Modification Example (3)> In the server 10, the shopping settlement history data included in each user management data may or may not include the specific content of the shopping settlement (hereinafter referred to as "shopping settlement content").

[0211] FIG. 2-21 is a diagram showing a data configuration example of a second user management database 155B which is another example of the user management database 155 in this modification example. In this example, in addition to the shopping settlement ID, the store ID, and the shopping settlement date and time, the shopping settlement content is stored in association with the shopping settlement history data.

[0212] The shopping settlement content includes, by way of example rather than limitation, information on the products purchased at the store with the store ID and information on the services provided at the store with the store ID.

[0213] In this case, the information regarding the purchased goods can include, by way of example and not limitation, information such as a product ID for identifying the purchased goods themselves, a product type ID for identifying the type of the purchased goods, and the number of the purchased goods. In addition, the information regarding the provided services can include, by way of example and not limitation, information such as a service ID for identifying the provided services themselves, a service type ID for identifying the type of the provided services, and the number of people to whom the services were provided.

[0214] By doing so, by way of example and not limitation, in accordance with the inquiry request for the shopping settlement details received from the terminal 20, the control unit 11 of the server 10 can disclose the shopping settlement details to the terminal 20.

[0215] <Second Modification Example (4)> The display screen and user interface (UI) shown in the second embodiment are merely examples and are not limited thereto.

[0216] FIG. 2-22 is a diagram showing another example of the split payment request notification screen of FIG. 2-13, and shows an example of a screen displayed on the display unit 24 of the terminal 20 of user B.B. This split payment request notification screen corresponds to the split payment request notification screen of FIG. 2-15, but is configured such that the breakdown of the split payment requested by the split payment master is displayed when the over / under amount display area is operated (by way of example and not limitation, a touch operation). In this example, as the breakdown of the split payment, "AA Rent-a-Bicycle 1,500 yen" and "BB Supermarket 3,000 yen" are displayed, and in addition, their total amount "4,500 yen" and the amount per person "4,500 yen ÷ 5 people = 900 yen" are displayed.

[0217] In this example, it shows the case of dividing the paid amount paid by user A.A through shopping payment among 5 users. Since the paid amount of user A.A is "4,500 yen" and the number of people for the split is "5 people", the amount per person is "4,500 yen ÷ 5 people = 900 yen".

[0218] Specifically, based on the operation of the over / under amount display area, the control unit 21 of the terminal 20 sends a query request for the breakdown of the split payment to the server 10. The server 10, based on the shopping payment history data included in the user management data in which the payment application ID of the split master is stored in the first user management database 155A (see FIG. 2-5), sends information on the store name, shopping payment date and time, and shopping payment amount to the terminal 20. Then, the control unit 21 of the terminal 20 displays the breakdown of the split payment based on the received information.

[0219] Note that it is also possible for the control unit 21 of the terminal 20 to send a query request for the above-mentioned shopping payment details from the terminal 20 to the server 10 based on the operation of the over / under amount display area. In this case, the server 10, based on the shopping payment history data included in the user management data in which the payment application ID of the split master is stored in the second user management database 155B (see FIG. 2-21), sends, in addition to the store name, shopping payment date and time, and shopping payment amount, the shopping payment details to the terminal 20. Then, the control unit 21 of the terminal 20 displays the breakdown of the split payment including the shopping payment details based on the received information.

[0220] FIG. 2-23 is a diagram showing another example of the receipt notification screen shown in FIG. 2-15, and shows an example of the screen displayed on the display unit 24 of the terminal 20 of user A.A. On this receipt notice screen, different from the receipt notice screen in Fig. 2-15, along with the total amount of the electronic money received by user A.A (in this example, "3,600 yen"), the text "There has been a transfer from the split payment members." and the icon images of the split payment members other than oneself (in this example, the icon images of four users: "User B.B", "User C.C", "User D.D", and "User E.E") are included in the displayed receipt notice. Also, below the receipt notice, a split payment completion notice similar to the one shown in Fig. 2-16 is displayed.

[0221] By making such a display, the user of the split payment master can easily grasp at a glance the total amount of money transferred to themselves and the split payment members who transferred money to themselves.

[0222] <Second Modification Example (5)> Regarding the terminal 20 of the user who does not make a transfer despite making a split payment request, a reminder may or may not be sent from the terminal 20 of the split payment master via the server 10.

[0223] Fig. 2-24 is a diagram showing an example of the split payment reminder notice screen in this embodiment, and shows an example of the screen displayed on the display unit 24 of the terminal 20 of user B.B. On this split payment reminder notice screen, the text "A reminder for split payment has been received from Mr. / Ms. A.A." is displayed, and below it, a surplus / deficit amount display area including the surplus / deficit amount of user B.B is displayed in the same way as on the split payment request notice screen.

[0224] By making such a display, even if the user who has been requested to make a split payment forgets (or has forgotten) to settle, it is possible to ensure that the settlement is made.

[0225] <Second Modification Example (6)> In the second embodiment, it was explained that when the balance of the electronic money accounts of the users of all target terminals does not become negative, it is determined that the split payment is established. Regarding this, by way of example and not limitation, when there is a user of the target terminal whose electronic money account balance becomes negative, the server 10 (by the operator of the payment application) may replenish the electronic money account by advancing the insufficient amount, etc., and determine that the split payment is established. In this case, the advanced amount may be settled with the user later.

[0226] <Example 3> Example 3 is an example in which each split payment member can confirm not only their own surplus or deficit amount but also the surplus or deficit amounts of other split payment members on their own terminal 20. Example 3 is an example in which, in the process of Example 2, a process is added in which the terminal 20 receives information on the surplus or deficit amounts of at least each split payment member from the server 10 and displays it on the display unit 24.

[0227] The content described in Example 3 is applicable to any of the other examples and other modification examples. Also, the same reference numerals are assigned to the same components as those already described, and the repeated description is omitted.

[0228] <Example of display screen> FIG. 3-1 is a diagram showing an example of a shopping payment history selection screen in this example, and shows an example of a screen displayed on the display unit 24 of the terminal 20 of user A.A. On this shopping payment history selection screen, similar to the shopping payment history selection screen in FIG. 2-12, a plurality of shopping payment histories for the user of the own terminal 20 are displayed. In this example, a state where the checks for the shopping payment histories of "AA Rental Cycle" and "BB Supermarket" are "ON" is shown.

[0229] In addition, the shopping settlement history selection screen in Fig. 3-1 is different from the shopping settlement history selection screen in Fig. 2-12 in that the icons displayed at the lower part of the screen are different. Specifically, in the shopping settlement history selection screen in Fig. 2-12, the split payment request icon was displayed at the lower part of the screen, while in the shopping settlement history selection screen in Fig. 3-1, instead of the split payment request icon, a split payment content confirmation icon labeled "Confirm Split Payment Content" (shown as an example rather than a limitation) for checking the content of the split payment is displayed.

[0230] Fig. 3-2 is a diagram showing an example of a split payment content confirmation screen displayed based on the operation (touch operation shown as an example rather than a limitation) of the split payment content confirmation icon on the shopping settlement history selection screen in Fig. 3-1. On this split payment content confirmation screen, for each split payment member including the user of the own terminal 20, there are provided a paid amount list display area for displaying the paid amount and an excess / deficiency amount list display area for displaying the excess / deficiency amount.

[0231] In this example, in the paid amount list display area, for the user of the own terminal 20 (User A.A), "4,500 yen" is displayed as the paid amount, and for the other split payment member users (User B.B, User C.C, User D.D, User E.E), "0 yen" is displayed as the paid amount.

[0232] Also, in this example, since the amount per person is "900 yen", in the excess / deficiency amount list display area, for the user of the own terminal 20 (User A.A), "Received 3,600 yen" is displayed as the excess / deficiency amount, and for the other split payment member users (User B.B, User C.C, User D.D, User E.E), "Payment of 900 yen" is displayed as the excess / deficiency amount.

[0233] Also, below the paid amount list display area and the excess / deficiency amount list display area, there is provided an amount per person display area for displaying the amount per person. In this example, "900 yen" is displayed as the amount per person.

[0234] Also, below the amount display area per person, there is a comment input area for entering comments. In this example, a comment with the content "This is a split payment for the trip the other day." is entered and displayed by user A.A, who is the split payment master.

[0235] Also, on this split payment content confirmation screen, the "split payment request icon" that was displayed on the shopping payment history selection screen in Fig. 2-12 is displayed at the bottom of the screen. By operating this split payment request icon, a split payment request is sent to the terminals 20 of other split payment members.

[0236] The above various types of information are displayed, for example but not limited to, by the split payment confirmation information being sent from the server 10 to the terminal 20. In this example, the split payment confirmation information can include information on the paid amount based on the registered shopping payment history, information on the excess or deficiency amount of each split payment member, and information on the registered comment.

[0237] Note that it is not necessarily required to include all of the above information in the split payment confirmation information, and a part of the information may be included in the split payment confirmation information. For example but not limited to, the information on the excess or deficiency amount of each split payment member may be included in the split payment confirmation information so that the information on the excess or deficiency amount of each split payment member can be confirmed on the terminal 20.

[0238] Fig. 3-3 is a diagram showing an example of a split payment request notification screen displayed on the display unit 24 of the terminal 20 of user B.B based on the operation (touch operation in this example but not limited to) of the split payment request icon on the split payment content confirmation screen in Fig. 3-2. On this split bill request notification screen, unlike the split bill request notification screen in Fig. 2-13, comments entered by user A.A, who is the split bill master, are displayed below the over / under amount display area. In this example, a comment "This is for the split bill of the payment during the trip the other day." is displayed in a speech bubble in association with the icon image and user name of user A.A.

[0239] Also, on the split bill request notification screen in Fig. 3-3, unlike the split bill request notification screen in Fig. 2-13, an icon for "Check settlement details" (shown as an example rather than a limitation) for checking the details of the settlement is displayed.

[0240] Fig. 3-4 is a diagram showing an example of the settlement details confirmation screen displayed when the settlement details confirmation icon on the split bill request notification screen in Fig. 3-3 is operated (a touch operation is shown as an example rather than a limitation). On this settlement details confirmation screen, in order from the top, the icon images and user names of user B.B, who is the user of one's own terminal 20, user A.A, who is the split bill master, and other split bill members (user C.C, user D.D, user E.E) are displayed. Also, in association with each split bill member, the paid amount of that split bill member is displayed in the paid amount list display area, and the over / under amount of that split bill member is displayed in the over / under amount list display area.

[0241] Fig. 3-5 is a diagram showing an example of the display when the paid amount list display area on the settlement details confirmation screen in Fig. 3-4 is operated (a touch operation is shown as an example rather than a limitation). When the display area of the paid amount of a single user is operated in the paid amount list display area, the payment details corresponding to the paid amount, that is, the breakdown of the split payment, are configured to be viewable. In this example, based on the fact that the display area of the paid amount (in this example, "4,500 yen") associated with user A.A, who is the split payment master, in the paid amount list display area was touched by user B.B, the payment details corresponding to the paid amount are displayed in a pop-up format.

[0242] <Processing> FIG. 3-6 is a flowchart showing an example of the processing flow executed by each device in this embodiment. This processing is the processing in which steps A410 and A420 are added as the processing of terminal A and step S410 is added as the processing of server 10 to the processing part of FIG. 2-17 among the processes of FIGS. 2-17 to 2-19.

[0243] After S180 and S190, the control unit 11 of server 10 transmits the above-described split payment confirmation information to terminal A via communication I / F 14 (S410). Then, the control unit 11 transfers the processing to S210 in FIG. 2-18.

[0244] When receiving the split payment confirmation information from server 10 via communication I / F 22 (A410), the control unit 21 of terminal A causes the received split payment confirmation information to be displayed on the display unit 24 (A420). As a result, various types of information including the above-described overage / shortage amount information are displayed on the display unit 24. Then, the control unit 21 of terminal A transfers the processing to A210 in FIG. 2-18.

[0245] <Effect of the Third Embodiment> In the third embodiment, the terminal 20 receives, via the communication I / F 22 from the server 10, settlement confirmation information (an example of amount information, not limited thereto) including at least information on the excess or deficiency amount (an example of the first amount, not limited thereto) of the user of its own terminal 20 based on the shopping settlement history by the user of its own terminal 20 and information on the excess or deficiency amount (an example of the second amount, not limited thereto) of the user of a different terminal 20. Then, the terminal 20 is configured to display the received settlement confirmation information on the display unit 24. As an example of the effect obtained by such a configuration, it is possible to enable the user of the terminal to confirm amount information including at least the information on the first amount and the information on the second amount.

[0246] <Third Modification Example (1)> In the third embodiment, it is also possible to enable the user of the terminal 20 to confirm the status of the settlement of the share (hereinafter referred to as the "share settlement status") based on the excess or deficiency amount of each share member.

[0247] FIG. 3-7 is a diagram showing an example of the share content confirmation screen in this modification example, and shows an example of the screen displayed on the display unit 24 of the terminal 20 of user B.B. On this share content confirmation screen, as an example, not limited thereto, the excess or deficiency amount of each share member and the share settlement status of that share member are displayed in association with the icon image of each share member.

[0248] In the column of the share master (user A.A), as an example, not limited thereto, the excess or deficiency amount of the share master (the amount to be received) and the status of receiving money from other share members (received / not received) are displayed as the share settlement status. When money has been received from some of the other share members, "received" is displayed together with the received amount.

[0249] In addition, in the columns of the split - payment members other than the split - payment master (in this example, oneself (User B.B), User C.C, User D.D, and User E.E), as the split - payment settlement status, by way of example rather than limitation, the over - or - under amount (the amount to be paid) of that split - payment member and the status of payment of the amount of that split - payment member (settled / unsettled) are displayed.

[0250] In addition, below the display area of the split - payment settlement status, by way of example rather than limitation, a split - payment settlement status update icon including, by way of example rather than limitation, an update mark and the character "Update" is provided to update this split - payment settlement status to the latest state. When this split - payment settlement status update icon is operated, the latest split - payment settlement status is transmitted from the server 10 to the terminal 20 and the display is updated.

[0251] In this example, as the split - payment settlement status of oneself (User B.B), "Pay 900 yen" and "Unsettled" are displayed. In addition, as the split - payment settlement status of the split - payment members other than the split - payment master (User A.A) and oneself (User B.B), for User C.C, "Pay 900 yen" and "Unsettled" are displayed, for User D.D, "Pay 900 yen" and "Settled" are displayed, and for User E.E, "Pay 900 yen" and "Unsettled" are respectively displayed. In addition, since User D.D has settled and the split - payment master (User A.A) has already received "900 yen" from User D.D, as the split - payment settlement status of the split - payment master (User A.A), "Receive 3,600 yen" and "Received 900 yen" are displayed.

[0252] By making such a display, the users of each terminal 20 can check the settlement status of users other than themselves, so the convenience of the users can be improved.

[0253] <Third Variant Example (2)> It may also be possible to change the amount that each split - payment member bears in the split - payment or the ratio of bearing the amount based on the input by the user of the terminal 20.

[0254] FIG. 3-8 is a diagram showing another example of the share settlement content confirmation screen, and shows an example of the screen displayed on the display unit 24 of the terminal 20 of user A.A. On this share settlement content confirmation screen, as an example rather than a limitation, next to the amount display area per person in the share settlement content confirmation screen of FIG. 3-5, there is provided a share ratio confirmation icon shown as "Confirm Share Ratio" as an example rather than a limitation for displaying the ratio of the amount borne by each share settlement member in the share settlement (hereinafter referred to as the "share ratio"). Note that in this example of the display screen, the share ratio is displayed as the "share ratio".

[0255] FIG. 3-9 is a diagram showing an example of the share ratio confirmation screen displayed based on the operation (touch operation as an example rather than a limitation) of the share ratio confirmation icon in the share settlement content confirmation screen of FIG. 3-8. On this share ratio confirmation screen, the characters "Please confirm the share ratio of the share settlement" are displayed, and below that, a total payment amount display area for displaying the total amount of the payment amount (total payment) by the shopping settlement is provided.

[0256] Here, the "total payment" is the amount obtained by summing up the paid amounts based on the shopping settlement history registered by each share settlement member. In this embodiment, since only user A.A registers the shopping settlement history, "the paid amount of user A.A = total payment". As a result, in this example, "4,500 yen" is displayed as the total payment. Note that when only one user registers the shopping settlement history as in this example, the display of the total payment may also be the display of the paid amount of that user.

[0257] Also, below that, a graph display area for displaying the amount of the settled amount among the over / under amounts in a graph in association with the icon images of each share settlement member is provided. In this example, a horizontal bar graph whose length changes according to the settled amount is displayed in the graph display area.

[0258] Specifically, in this example, the split payment master (User A.A) has already paid "4,500 yen" for shopping and has not yet received any money from any other split payment members. Therefore, a bar graph with a length corresponding to "4,500 yen" is displayed next to the icon image of User A.A. Also, since none of the other split payment members have paid the amount to User A.A yet and the length of the bar graph is "0", "0 yen" enclosed by a dashed line is displayed in association with the icon images of the split payment members other than User A.A.

[0259] In this state, if someone among the split payment members transfers money to User A.A, the length of the bar graph associated with that split payment member is updated and displayed to a length corresponding to the amount transferred to User A.A.

[0260] Also, the over / under amount of each split payment member is displayed horizontally in the graph display area. In this example, "3,600 yen, received" is displayed as the over / under amount for the split payment master (User A.A), and "900 yen, payment" is displayed as the over / under amount for the other split payment members.

[0261] Also, at the bottom of the screen, a split payment ratio change icon shown as "Change sharing ratio" (not limited to this example) for changing the split payment ratio is displayed.

[0262] FIG. 3-10 is a diagram showing an example of a split payment ratio change screen displayed based on the operation (touch operation as an example, not limited to this) of the split payment ratio change icon on the split payment ratio confirmation screen of FIG. 3-9, and shows an example of the screen displayed on the display unit 24 of the terminal 20 of User A.A. On this split bill ratio change screen, a graph for changing the split bill ratio of each split bill member is displayed. In this example, as the graph for changing the split bill ratio, a donut-shaped graph (hereinafter referred to as the "donut graph") is displayed. This donut graph is a graph with a hole in the center of a pie chart. In this example, the total payment amount is displayed in the area with the hole in the center.

[0263] Also, the donut graph has a plurality of regions corresponding to each split bill member. Associated with the icon image of each split bill member, the split bill ratio of that split bill member and the over / under amount calculated based on that split bill ratio and the total payment amount (= total payment amount × split bill ratio) are displayed.

[0264] The split bill ratio of each split bill member is configured to be changeable by swiping the boundary between the display region corresponding to that split bill member and the display region corresponding to the adjacent split bill member in the donut graph in any direction.

[0265] By way of example and not limitation, when the boundary between the display regions of user B.B and user C.C in the donut graph is touched with a finger and then an operation is performed to move the finger to the side of user B.B or user C.C, the split bill ratios of user B.B and user C.C are changed.

[0266] Specifically, by way of example and not limitation, when the finger is moved to the side of user B.B, the ratio occupied by the display region of user B.B in the donut graph decreases, the split bill ratio of user B.B decreases, and the split bill ratio of user C.C increases. On the other hand, when the finger is moved to the side of user C.C, the ratio occupied by the display region of user B.B in the donut graph increases, the split bill ratio of user B.B increases, and the split bill ratio of user C.C decreases. In this case, the split bill ratios of other split bill members do not change.

[0267] In this example, the case of changing the sharing ratio using a donut graph is illustrated. However, you may or may not change the sharing ratio using a graph other than the donut graph, such as a bar graph, a pie graph, or a band graph. Also, you may or may not change the sharing ratio by inputting a numerical value. Alternatively, instead of the sharing ratio, you may or may not change the excess / deficiency amount according to the same method.

[0268] FIG. 3-11 is a flowchart showing an example of the flow of processing executed by each device in this modified example. This processing is the processing in which steps A430 and A440 are added as the processing of terminal A and step S440 is added as the processing of server 10 to the processing in FIG. 3-6.

[0269] After A420, the control unit 21 of terminal A determines whether to change the sharing ratio (A430) based on whether a sharing ratio change operation is input to the input / output unit 23, by way of example and not limitation.

[0270] If it is determined to change the sharing ratio (A430: YES), the control unit 21 of terminal A transmits, by way of example and not limitation, sharing change request information including the sharing ratio specified by the sharing ratio change operation to server 10 via the communication I / F 22 (A440), and then returns the processing to A410.

[0271] On the other hand, if it is determined not to change the sharing ratio (A430: NO), the control unit 21 of terminal A transfers the processing to A210 in FIG. 2-18.

[0272] After S410, the control unit 11 determines whether it has received sharing change request information from terminal A via the communication I / F 14 (S440). If it is determined that it has received the information (S440: YES), the processing returns to S190. That is, the excess / deficiency amount is recalculated based on the sharing ratio included in the sharing change request information received from terminal A.

[0273] The control unit 11 repeats the processes of S190 and S410 until it stops receiving the split payment change request information from the terminal 20 (S440: NO). If it is determined that the control unit 11 has stopped receiving the split payment change request information from the terminal 20 (S440: NO), the control unit 11 moves the process to S210 in FIG. 2-18.

[0274] According to this modification example, the terminal can easily change at least one of the information on the first amount and the information on the second amount by transmitting information for changing at least one of the information on the first amount and the information on the second amount.

[0275] <Fourth Embodiment> The fourth embodiment is an embodiment in which the excess / deficiency amount is calculated based on the shopping settlement history by the user of the own terminal 20 and the shopping settlement history by the user of a different terminal 20. The first to third embodiments are different in that it is configured such that the shopping settlement history can be added and registered by the user of the terminal 20 or the user of a different terminal 20.

[0276] The content described in the fourth embodiment is applicable to any of the other embodiments and other modification examples. In addition, the same reference numerals are given to the same components as those already described, and the repeated description is omitted.

[0277] <Example of Display Screen> FIG. 4-1 is a diagram showing an example of the split payment content confirmation screen in this embodiment, and shows an example of the screen displayed on the display unit 24 of the terminal 20 of user B.B. In this embodiment, it is configured such that, in a state where the shopping settlement history to be split by the first user has been registered, the shopping settlement history to be split by a second user different from the first user can be further added and registered. Here, as exemplified above, the case where user B.B adds and registers his / her own shopping settlement history in a state where the shopping settlement history of user A.A has been registered is exemplified.

[0278] This split payment content confirmation screen is almost the same as the split payment content confirmation screen in Fig. 3-4, but the icons displayed at the bottom of the screen are different. Specifically, in addition to the payment icon labeled "Settle" as an example (not a limitation), there is a shopping payment history addition icon labeled "Add Payment Portion" as an example (not a limitation) for adding and registering the user's (User B.B) shopping payment history.

[0279] Fig. 4-2 is a diagram showing an example of a shopping payment history selection screen displayed based on the operation (touch operation as an example, not a limitation) of the shopping payment history addition icon on the split payment content confirmation screen in Fig. 4-1. Multiple shopping payment histories by User B.B are displayed on this shopping payment history selection screen. In this example, shopping payment histories at multiple stores such as "DD Cafe", "EE Restaurant", and "FF Convenience Store" are displayed. At the bottom of the screen, there is a shopping payment history registration icon labeled "Register" as an example (not a limitation) for registering the selected shopping payment history.

[0280] Fig. 4-3 is a diagram showing an example of the split payment content confirmation screen displayed on the display unit 24 of User B.B's terminal 20 based on the operation (touch operation as an example, not a limitation) of the shopping payment history registration icon on the shopping payment history selection screen in Fig. 4-2. In this example, in addition to the shopping payment history of "4,500 yen" previously registered by User A.A, the state where a shopping payment history of "5,500 yen" by User B.B has been additionally registered is shown. As a result, in the paid amount list display area, the paid amount "5,500 yen" is displayed in association with the icon image of the user himself (User B.B), and the paid amount "4,500 yen" is displayed in association with the icon image of User A.A.

[0281] Here, as described above, the total amount of the paid amounts based on the shopping settlement history registered by each sharing member is defined as the "total payment amount". And in this embodiment, it is calculated as "amount per person = total payment amount ÷ number of people for sharing".

[0282] In this example, since user A.A and user B.B have each registered a shopping settlement history, "the paid amount of user A.A + the paid amount of user B.B = total payment amount". The paid amount of user A.A is "4,500 yen", and the paid amount of user B.B is "5,500 yen", so the total payment amount is "4,500 yen + 5,500 yen = 10,000 yen". The number of people for sharing is "5 people", so "amount per person = 10,000 ÷ 5 people = 2,000 yen". As a result, "2,000 yen" is displayed as the amount per person.

[0283] Also, in the over / under amount list display area, the paid amount of each user and the over / under amount calculated based on the amount per person are displayed. Specifically, as the over / under amount of oneself (user B.B), "5,500 yen - 2,000 yen = +3,500 yen (receive 3,500 yen)" is displayed, as the over / under amount of user A.A, "4,500 yen - 2,000 yen = +2,500 yen (receive 2,500 yen)" is displayed, and as the over / under amount of the other sharing members, "0 yen - 2,000 yen = -2,000 yen (pay 2,000 yen)" is displayed.

[0284] FIG. 4-4 is a diagram showing an example of a sharing request notification screen displayed on the display unit 24 of the terminal 20 of user B.B based on the operation (touch operation as an example rather than a limitation) of the settlement icon on the sharing content confirmation screen of FIG. 4-3. On this sharing request notification screen, "receive 3,500 yen" is displayed in the over / under amount display area as the over / under amount of user B.B.

[0285] Also, when the over / under amount display area is operated, below it, the comment of User A.A and the breakdown of the split payment are displayed. In this example, as the breakdown of the split payment, the shopping settlement history registered by User A.A and the shopping settlement history registered by User B.B are displayed. As the total amount, "10,000 yen" is displayed, and as the amount per person, "2,000 yen" is displayed. Also, in this example, in order to indicate that the shopping settlement history of "EE Restaurant" is the shopping settlement history newly registered by User B.B, a mark of "N (New)" is attached and displayed at the upper left of the icon image of User B.B associated with the shopping settlement history of "EE Restaurant".

[0286] FIG. 4-5 is a diagram showing an example of a split payment request notification screen displayed on the display unit 24 of the terminal 20 of User A.A based on the operation (touch operation as an example, not limited) of the settlement icon on the split payment content confirmation screen of FIG. 4-3. On this split payment request notification screen, "Receive 2,500 yen" is displayed in the over / under amount display area as the over / under amount of User A.A.

[0287] Also, when the over / under amount display area is operated, below it, the comment of oneself (User A.A) and the breakdown of the split payment are displayed. The displayed comment and the breakdown of the split payment are the same as those in FIG. 4-4.

[0288] <Functional Configuration> FIG. 4-6 is a diagram showing an example of information stored in the storage unit 15 of the server 10 in this embodiment. In the storage unit 15, in addition to the payment application management processing program 151, the payment application user registration data 153, and the user management database 155, as an example (not limited), a split payment management database 157 is stored.

[0289] The split payment management database 157 is a database for the server 10 to manage split payments by the users of the terminal 20, and a configuration example of a first split payment management database 157A, which is an example thereof, is shown in FIGS. 4-7. In the first split payment management database 157A, split payment management data is stored as management data for each split payment.

[0290] Each split payment management data stores, by way of example and not limitation, a split payment management ID, a split payment master ID, a split payment member ID, and shopping settlement history management data.

[0291] The split payment management ID stores an ID (identification information) for uniquely identifying the split payment. By way of example and not limitation, when it is determined that split payments are to be made by a group of multiple users, a unique ID is set and stored by the server 10 with the split payment within the group as one unit.

[0292] The split payment master ID stores, by way of example and not limitation, the payment application ID of the split payment master.

[0293] The split payment member ID stores the payment application IDs of the respective split payment members.

[0294] The shopping settlement history management data is data for managing one or more shopping settlement histories subject to split payment, and stores, by way of example and not limitation, a settler ID, a shopping settlement ID, and a split payment target amount in association with each other.

[0295] The settler ID stores the payment application ID of the user who made the settlement for the shopping settlement history. This settler ID can store not only the split payment master ID but also the IDs of each user included in the split payment member ID. That is, not only the shopping settlement histories registered by the split payment master but also the shopping settlement histories registered by split payment members other than the split payment master are stored in the shopping settlement history management data.

[0296] The shopping settlement ID stores, in the user management data corresponding to the payment application ID of the user with the payer ID in the user management database 155, the shopping settlement ID corresponding to the shopping settlement history registered by the user with the payer ID among the shopping settlement IDs in the shopping settlement history data included in the shopping settlement history data.

[0297] The amount subject to split payment is an amount with the shopping settlement amount of the shopping settlement history corresponding to the shopping settlement ID as the upper limit, and the amount specified by the user with the payer ID is stored as the amount subject to split payment.

[0298] Regarding the split payment member ID, it may or may not store the payment application IDs of split payment members other than the split payment master. That is, the split payment master ID may or may not be excluded from the column of the split payment member ID.

[0299] <Process> Figures 4-8 are flowcharts showing an example of the processing flow executed by each device in this embodiment. The processing in Figure 4-8 is the processing in which, in the processing part of Figure 2-18 among the processing in Figures 2-16 to 2-18, steps of A530 are added as the processing of terminal A, steps of A530 are added as the processing of terminal B, and steps of S530 to S570 are added as the processing of server 10. For steps that are the same as the previously described processing, the same reference numerals are used and the description is omitted again.

[0300] After A210, the control unit 21 of terminal A executes split payment additional registration processing (A530). Similarly, after B210, the control unit 21 of terminal B executes split payment additional registration processing (A530).

[0301] Figure 4-9 is a flowchart showing an example of the flow of split payment additional registration processing. The control unit 21 determines whether the user of its own terminal 20 has agreed to split the bill (A5310). Specifically, by way of example and not limitation, it determines whether an operation for indicating the intention to agree to split the bill has been input to the input / output unit 23.

[0302] If it determines that the user has not agreed to split the bill (A5310: NO), the control unit 21 determines whether to add a shopping settlement history (A5320). Specifically, by way of example and not limitation, it determines whether an operation for adding a shopping settlement history has been input to the input / output unit 23.

[0303] If it determines to add a shopping settlement history (A5320: YES), the control unit 21 executes a split-bill settlement addition process (A5330). Then, the control unit 21, by way of example and not limitation, transmits a split-bill settlement addition notice including the shopping settlement ID of the shopping settlement history to be added to the server 10 via the communication I / F 22 (A5340).

[0304] On the other hand, if it determines not to add a shopping settlement history (A5320: NO), the control unit 21 transmits a split-bill settlement rejection notice to the server 10 via the communication I / F 22 (A5350). Also, if it determines that the user has agreed to split the bill (A5310: YES), the control unit 21 transmits a split-bill settlement approval notice to the server 10 via the communication I / F 22 (A5360).

[0305] After A5340, A5350, or A5360, the control unit 21 determines whether it has received a split-bill change notice from the server 10 via the communication I / F 22 (A5370). If it determines that it has received the notice (A5370: YES), it causes the received split-bill change notice to be displayed on the display unit 24 (A5380). Then, the control unit 21 returns the process to A5310.

[0306] On the other hand, if it determines that it has not received a split-bill change notice (A5370: NO), the control unit 21 ends the split-bill addition registration process.

[0307] After S210, the control unit 11 of the server 10 executes a second split payment approval management process (S530).

[0308] FIG. 4-10 is a flowchart showing an example of the flow of the second split payment approval management process. This process is a process in which the step of S2310 in the first split payment approval management process (see FIG. 2-20) is replaced with S5310, and the steps of S5320 to S5340 are added. In this process, the split payment settlement notice is any one of the aforementioned "split payment settlement approval notice", "split payment settlement rejection notice", and "split payment settlement additional notice". For steps that are the same as the previously described processes, the same reference numerals are used and repeated description is omitted.

[0309] When the control unit 11 receives a split payment settlement notice from the terminal 20 (S5310), it determines whether the received split payment settlement notice is a "split payment settlement additional notice" (S5320). If it is determined that the received split payment settlement notice is not a split payment settlement additional notice (5320: NO), the control unit 11 transfers the process to S2320.

[0310] On the other hand, if it is determined that the received split payment settlement notice is a split payment settlement additional notice (S5320: YES), the control unit 11 updates the shopping settlement history management data in the corresponding split payment management data in the first split payment management database 157A. Then, the control unit 11 calculates the excess or deficiency amount based on the shopping settlement history identified by the shopping settlement ID included in the received split payment settlement additional notice (S5330).

[0311] Thereafter, the control unit 11 changes the split payment details based on the calculated excess or deficiency amount (S5340). Then, the control unit 11 ends the second split payment approval management process.

[0312] Returning to FIGS. 4-8, the control unit 11 determines whether the split payment details have been changed in the second split payment approval management process (S550). If it is determined that the details have been changed (S550: YES), the control unit 11 transmits a split payment change notice to each of the terminal A and the terminal B via the communication I / F 14 (S570). Then, the control unit 11 returns the process to S530.

[0313] On the other hand, if it is determined that the split payment details have not been changed in the second split payment approval management process (S550: NO), the control unit 11 moves the process to S240.

[0314] After A530, the control unit 21 of the terminal A moves the process to A250. Similarly, after A530, the control unit 21 of the terminal B moves the process to B250.

[0315] <Effect of the Fourth Embodiment> In the fourth embodiment, the over / under amount (not limited, an example of the first amount and the second amount) of each split payment member is determined based on the shopping settlement history (not limited, an example of the second settlement information regarding the second settlement by users of different terminals) by a split payment member different from the user of one terminal 20 and the shopping settlement history (not limited, an example of the first settlement information) by one user. As an example of the effect obtained by such a configuration, since the first amount and the second amount can be determined in consideration of not only the first settlement information but also the second settlement information regarding the second settlement by users of different terminals, the convenience of the user can be improved.

[0316] <Fourth Modification Example (1)> In the fourth embodiment, the user of the split payment master may or may not be able to set the permission / forbidden addition of the shopping settlement history by other split payment members.

[0317] FIG. 4-11 is a diagram showing an example of a split payment content confirmation screen displayed on the display unit 24 of the terminal 20 of user A.A, who is the split payment master, based on the operation of the split payment content confirmation icon on the shopping payment history selection screen of FIG. 3-1 in this modified example. On this split payment content confirmation screen, in the paid amount display area, an icon image and user name of a split payment member other than oneself (user A.A) are associated with a shopping payment history addition request icon shown as "addition request" as an example rather than a limitation for that split payment member to add their own shopping payment history. The user A.A, who is the split payment master, is configured to be able to set the permission / forbiddance of adding the shopping payment history by that split payment member by touching the shopping payment history addition request icon associated with each split payment member.

[0318] 、 The shopping payment history addition request icon is, as an example rather than a limitation, displayed in an active state for split payment members whose addition of the shopping payment history is permitted, and in an inactive state for split payment members whose addition of the shopping payment history is prohibited. In this example, the user A.A, who is the split payment master, has set to prohibit the addition of the shopping payment history by user E.E, and as a result, the addition request icon associated with user E.E is displayed in an inactive state.

[0319] This is the case where, for example rather than a limitation, when user A.A proposed to split the shopping payment history when the group of users A.A to E.E went on a trip, user A.A remembered that user E.E did not pay a single yen for this trip, and user A.A judged that it was impossible (or did not recognize) for user E.E to add the shopping payment history.

[0320] This is merely an example, but when the split payment master determines that no shopping payment history will be added for a specific split payment member, or when it determines not to allow the addition of a shopping payment history, it is possible to prohibit the addition of a shopping payment history by that split payment member.

[0321] FIG. 4-12 is a diagram showing an example of a split payment content confirmation screen displayed on the display unit 24 of the terminal 20 of user E.E in this example. On this split payment content confirmation screen, a shopping payment history addition icon for adding a shopping payment history is provided at the bottom of the screen. However, as described above, since the addition of a shopping payment history by user E.E is prohibited, the shopping payment history addition icon is displayed in an inactive state, and operations on this shopping payment history addition icon are disabled (even if an operation is performed, no processing related to adding a shopping payment history is executed).

[0322] In this case, from the terminal 20 of the split payment master, via the server 10, shopping payment history addition prohibition information for prohibiting the addition of a shopping payment history is transmitted to at least the terminal 20 of the split payment member for whom the addition of a shopping payment history is prohibited. Then, the terminal 20 that has received the shopping payment history addition prohibition information may perform a setting for prohibiting the addition of a shopping payment history and invalidate the addition operation of the shopping payment history.

[0323] Note that in the above example, the entity that sets the permission / prohibition for adding a shopping payment history is the split payment master, but it is not limited to this. In addition to or instead of the split payment master, a split payment member other than the split payment master may be able to set the permission / prohibition for adding a shopping payment history, or may not do so.

[0324] <Example 5> Example 5 is an example in which split payment is performed among users of a plurality of terminals 20 using a messaging service. The fifth embodiment is an embodiment in which a configuration related to a messaging service is added to the configurations of the first to fourth embodiments.

[0325] The content described in the fifth embodiment is applicable to any of the other embodiments and any of the other modified examples. Also, for components identical to the components already described, the same reference numerals are given and repeated description is omitted.

[0326] <System Configuration> FIG. 5-1 is a diagram showing an example of the system configuration of the communication system 1B in this embodiment. Note that the same reference numerals are given to the same configurations as those of the communication system 1A, and repeated description is omitted.

[0327] In the communication system 1B, by way of example and not limitation, the server 10, the messaging server 40, and a plurality of terminals 20 (terminal 20A, terminal 20B, terminal 20C,...) are connected via the network 30.

[0328] The messaging server 40 (an example of a server, an information processing device, and an information management device, not limited thereto) has a function of providing a messaging service to the terminal 20.

[0329] The messaging server 40 may be any device as long as it is an information processing device capable of realizing functions related to the messaging service. The messaging server 40 includes, by way of example and not limitation, a server device, a computer (by way of example and not limitation, a desktop, a laptop, a tablet, etc.), a media computer platform (by way of example and not limitation, a cable, a satellite set-top box, a digital video recorder), a handheld computer device (by way of example and not limitation, a PDA, an email client, etc.), or another type of computer, or a communication platform.

[0330] The messaging server 40 includes a control unit 41 (CPU), a storage unit 45, a communication I / F 44 (interface), an input / output unit 42, a display 43, and a clock unit 49. Each component of the HW of the messaging server 40 is interconnected via a bus B as an example, not a limitation. Note that it is not essential for the HW of the messaging server 40 to include all components as the configuration of the HW of the messaging server 40. As an example, not a limitation, the HW of the messaging server 40 may or may not be configured to remove the display 43.

[0331] The control unit 41 has a circuit physically structured to execute functions realized by codes or instructions included in a program, and is realized by, for example, not a limitation, a data processing device built into the hardware.

[0332] Typically, the control unit 41 is a central processing unit (CPU), and may also be, for example, a microprocessor, a processor core, a multiprocessor, an ASIC, or an FPGA, or not. In the present disclosure, the control unit 41 is not limited thereto.

[0333] The storage unit 45 has a function of storing various programs and various data required for the operation of the messaging server 40. The storage unit 45 is realized by various storage media such as an HDD, an SSD, and a flash memory. However, in the present disclosure, the storage unit 45 is not limited thereto. Also, the storage unit 45 may or may not be expressed as a memory.

[0334] The communication I / F 44 transmits and receives various data via the network 30. The communication may be performed either by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be executed. The communication I / F 44 has a function of executing communication with various devices such as the terminal 20 via the network 30. The communication I / F 44 transmits various data to various devices such as the terminal 20 according to an instruction from the control unit 41. Further, the communication I / F 44 receives various data transmitted from various devices such as the terminal 20 and transmits the data to the control unit 41. Further, the communication I / F 44 may be simply referred to as a communication unit. Further, when the communication I / F 44 is composed of physically structured circuits, it may be referred to as a communication circuit.

[0335] The input / output unit 42 is realized by a device that inputs various operations to the messaging server 40. The input / output unit 42 is realized by any one or a combination of all types of devices that can receive an input from a user and transmit information related to the input to the control unit 41. The input / output unit 42 is typically realized by a hardware key typified by a keyboard or the like, or a pointing device such as a mouse. Note that the input / output unit 42 may or may not include, by way of example and not limitation, a touch panel, a camera (operation input via a moving image), and a microphone (operation input by voice). However, in the present disclosure, the input / output unit 42 is not limited thereto.

[0336] The display 43 is typically realized by a monitor (by way of example and not limitation, a liquid crystal display or an OELD (organic electroluminescence display)). Note that the display 43 may or may not be a head-mounted display (HDM) or the like. Note that these displays 43 may or may not be able to display display data in 3D. In the present disclosure, the display 43 is not limited thereto.

[0337] The clock unit 49 is the built-in clock of the messaging server 40 and outputs time information (timekeeping information). The clock unit 49 is configured to include, by way of example and not limitation, an RTC (Real Time Clock) as a hardware clock, a system clock, and the like. The clock unit 49 can also be expressed as, by way of example and not limitation, a timekeeping unit or a time information detection unit.

[0338] <Example display screen> FIG. 5-2 is a diagram showing an example of a talk room screen in the present embodiment, and shows an example of a screen displayed on the display unit 24 of the terminal 20 of user A.A. This talk room screen is an example of a screen for user A.A to talk with user B.B using the messaging application executed on the terminal 20. The talk is an example of a chat, and the talk room is an example of a chat room.

[0339] Here, "chat" is a means for users of the terminal 20 to communicate with each other using a data communication line on a computer network, and a "chat room" is a virtual room for conducting this chat. Chats include those using a messaging service MS (including an instant messaging service (IMS)), and those using a social networking service SNS. Also, by way of example and not limitation, those using a so-called short message service may be included.

[0340] In the present embodiment, the chat includes a talk using a messaging service, and the chat room includes a talk room for conducting a talk. The talk room includes, as in the present embodiment, a talk room for users to talk one-on-one, and in addition, as will be described later, a group talk room for conducting a talk in a group including a plurality of users formed in the messaging service.

[0341] By way of example and not limitation, on the right side facing the screen, messages sent by user A.A are displayed in speech bubbles. On one side, on the left side facing the screen, a message (not limited to, for example, content) sent by user B.B, the conversation partner, is displayed in a speech bubble in association with the icon image of user B.B.

[0342] After sending a message, when the chat room screen of the messaging application is opened on the destination terminal 20, it means that the sent message has been read by the other user. And on the chat room screen of the source terminal 20, based on the control of the server 10, the character "read" is displayed in association with the sent message.

[0343] Note that the character "read" can be made not to be displayed until the chat room screen of the messaging application is opened on the destination terminal 20. By doing so, the user of the source terminal 20 can be made to recognize that the message is in the "unread" state.

[0344] In this example, a message requesting a split of the amount spent on the previous trip is displayed from user A.A to user B.B, and as a reply message from user B.B, a message approving the split request is displayed.

[0345] Also, at the bottom of the screen, function icons corresponding to a plurality of functions provided as functions of the messaging application are displayed. This function icon includes a split icon for performing a split.

[0346] FIG. 5-3 is a diagram showing an example of a shopping settlement history selection screen displayed based on the operation (not limited to, for example, a touch operation) of the split icon on the chat room screen of FIG. 5-2. The configuration of this shopping settlement history selection screen is almost the same as the shopping settlement history selection screen shown in the previous embodiment, but it is different in that it is a screen displayed as a function of the messaging application. On this shopping settlement history selection screen, similar to the example shown in the previous embodiment, shopping settlement histories at a plurality of stores such as "AA Rent-a-Bike", "BB Supermarket", and "CC Bento" are displayed, and in association with each shopping settlement history, a checkbox for making the shopping settlement history subject to splitting the bill is provided.

[0347] Also, at the bottom of the screen, a split bill request icon shown as "Send Split Bill Request" (not limited to this, just an example) for sending a split bill request from the terminal 20 of user A.A to the terminal 20 of user B.B is displayed.

[0348] FIG. 5-4 is a diagram showing an example of a talk room screen displayed on the display unit 24 of the terminal 20 of user B.B based on the operation of the split bill request icon on the shopping settlement history selection screen of FIG. 5-3. On this talk room screen, under the message for approving the split bill request from user B.B to user A.A on the talk room screen of FIG. 5-3, an example of the content transmitted and received between the terminals 20 using the messaging application, which is a message corresponding to the split bill request notification, a "split bill request message" is displayed in a balloon in association with the icon image of user A.A.

[0349] Here, the split bill request message is a message in a broad sense that includes not only simple text but also various types of information that can be transmitted and received, such as images (including still images, moving images, etc.), operation information (including buttons, icons, etc.), communication information, and access information (including URIs, URLs, etc.).

[0350] Note that in order to distinguish it from a normal text message, it may or may not be expressed as split bill request content instead of the split bill request message.

[0351] This split payment request message includes, by way of example and not limitation, the name of the payment application (in this example, "Payment App"), a statement that a split payment is requested, the over / under amount of User B.B, and details of the shopping settlement history that is the subject of the split payment. In this example, "2,250 yen payment" is displayed as the over / under amount of User B.B.

[0352] In addition, the split payment request message includes, by way of example and not limitation, a settlement icon for User B.B to transfer the over / under amount of money to User A.A for settlement, and a rejection icon for rejecting the split payment.

[0353] FIG. 5-5 is a diagram showing an example of a talk room screen displayed based on the operation of the settlement icon on the talk room screen of FIG. 5-4, and shows an example of the screen displayed on the display unit 24 of the terminal 20 of User B.B. On this talk room screen, by way of example and not limitation, based on the operation of the settlement icon, a message "Settle" is displayed in a balloon as a message from User B.B to User A.A, and a remittance completion message indicating that the over / under amount (in this example, "2,250 yen") has been transferred from User B.B to User A.A using the payment application is displayed.

[0354] <Data Configuration> FIG. 5-6 is a diagram showing an example of functions realized by the control unit 41 of the messaging server 40 in this embodiment. The control unit 41 has, by way of example and not limitation, a messaging application management processing unit 411 for executing messaging application management processing according to the messaging application management processing program 451 stored in the storage unit 45.

[0355] FIG. 5-7 is a diagram showing an example of information stored in the storage unit 45 of the messaging server 40 in this embodiment. The storage unit 45 stores, as an example rather than a limitation, a messaging application management processing program 451 as a program.

[0356] The storage unit 45 also stores, as an example rather than a limitation, messaging application user registration data 453 and a split expense management database 457 as data.

[0357] The messaging application user registration data 453 is registration data related to the terminal 20 that uses the messaging application or the user of that terminal 20, and an example of its data configuration is shown in FIGS. 5-8. The messaging application user registration data 453 stores, as an example rather than a limitation, a user name, a messaging application ID, a terminal phone number, and other registration information in association with each other.

[0358] The user name is the name of the user of the terminal 20 that uses the messaging application, and stores, as an example rather than a limitation, the name registered by the user of the terminal 20 when using the messaging application.

[0359] The messaging application ID is an account (account information) of the messaging application and is an ID that can identify the terminal 20 or the user of the terminal 20. This messaging application ID stores, as an example rather than a limitation, a unique ID set by the messaging server 40.

[0360] The terminal phone number is the phone number of the terminal 20 of the user with this user name, and stores, as an example rather than a limitation, the phone number of the terminal 20 registered by the user of the terminal 20 when using the messaging application.

[0361] Other registration information may include, by way of example and not limitation, the email address of the terminal 20 of the user with this username (terminal email address), the authentication password used for various authentications in the messaging application, the image data of the icon used by this user (user icon image), the user's profile (user profile), and the like. However, these pieces of information are not essential.

[0362] The split payment management database 457 is a database for the messaging server 40 to manage split payments among users of the terminal 20, and a configuration example of a third split payment management database 457A, which is an example thereof, is shown in FIGS. 5-9. In the third split payment management database 457A, split payment management data is stored as management data for each split payment.

[0363] Each split payment management data stores, by way of example and not limitation, a split payment management ID, a split payment master ID, a split payment member ID, and shopping settlement history management data. The split payment management ID, the split payment master ID, and the split payment member ID are the same as those of the split payment management database 157 described above.

[0364] In the shopping settlement history management data, by way of example and not limitation, a payer ID, a split payment target amount, a store name, a shopping settlement date and time, and other information are stored in association with each other.

[0365] <Process> FIGS. 5-10 to 5-12 are flowcharts showing an example of the processing flow executed by each device in this embodiment. In order from the left, there are shown the messaging split payment process (hereinafter referred to as the "MSG split payment process") executed by the control unit 21 of terminal A, the MSG split payment process executed by the control unit 21 of terminal B, the messaging split payment management process (hereinafter referred to as the "MSG split payment management process") executed by the control unit 41 of the messaging server 40, and the split payment settlement management process executed by the control unit 11 of the server 10.

[0366] First, the control unit 21 of terminal A transmits a split payment start notification to the messaging server 40 via the communication I / F 22 (A610). When receiving the split payment start notification from terminal A via the communication I / F 44 (M610), the control unit 41 of the messaging server 40 transmits shopping payment history request information for requesting the shopping payment history of the user of terminal A to the server 10 via the communication I / F 44 (M620).

[0367] When receiving the shopping payment history request information from the messaging server 40 via the communication I / F 14 (S620), the control unit 11 of the server 10 transmits the shopping payment history associated with the payment application ID of the user of terminal A to the messaging server 40 via the communication I / F 14 (S630).

[0368] When receiving the shopping payment history from the server 10 via the communication I / F 44 (M630), the control unit 41 transmits the received shopping payment history to terminal A via the communication I / F 44 (M640).

[0369] When receiving the shopping payment history from the messaging server 40 via the communication I / F 22 (A640), the control unit 21 of terminal A executes a second shopping payment history selection process (A650). Specifically, the control unit 21 of terminal A selects at least one shopping payment history from among a plurality of shopping payment histories of user A.A stored in the storage unit 28 of terminal A based on a selection operation on the input / output unit 23, by way of example and not limitation.

[0370] Next, the control unit 21 of terminal A transmits shopping payment history selection information to the messaging server 40 via the communication I / F 22 based on the processing result of A650 (A660).

[0371] When the communication I / F 44 receives shopping settlement history selection information from terminal A (M660), the control unit 41 updates the shopping settlement history management data in the corresponding split settlement management data in the third split settlement management database 457A based on the received shopping settlement history selection information. Then, the control unit 41 calculates the over / under amount based on the received shopping settlement history selection information (M670).

[0372] After that, based on the calculated over / under amount, the control unit 41 transmits split settlement request notices to terminal A and terminal B respectively via the communication I / F 44 (M710).

[0373] When the communication I / F 22 receives a split settlement request notice from the messaging server 40 (A710), the control unit 21 of terminal A determines whether to agree to the split settlement based on an operation input to the input / output unit 23 (A720).

[0374] If it is determined to agree to the split settlement (A720: YES), the control unit 21 of terminal A transmits a split settlement approval notice to the messaging server 40 via the communication I / F 22 (A730).

[0375] On the contrary, if it is determined not to agree to the split settlement (A720: NO), the control unit 21 of terminal A transmits a split settlement rejection notice to the messaging server 40 via the communication I / F 22 (A740).

[0376] The control unit 21 of terminal B performs the same processing as A710 - A740 of terminal A (B710 - B740).

[0377] After M710, the control unit 41 executes messaging split settlement approval management processing (hereinafter referred to as "MSG split settlement approval management processing"). (S)

[0378] FIG. 5 - 13 is a flowchart showing an example of the flow of MSG split settlement approval management processing. This MSG split bill approval management process is the same as the first split bill approval management process (see Fig. 2-20). That is, the control unit 41 performs the same processes as S2310 to S2360 of the first split bill approval management process (M7310 to M7360).

[0379] Returning to Fig. 5-11, if it is determined that the split bill is not established in the MGS split bill approval management process (M740: NO), the control unit 41 transmits a split bill non-establishment notice to terminal A and terminal B respectively through the communication I / F 44 (M750).

[0380] When receiving a split bill non-establishment notice from the messaging server 40 through the communication I / F 22 (A750), the control unit 21 of terminal A causes the received split bill non-establishment notice to be displayed on the display unit 24 (A760). Then, the control unit 21 of terminal A transfers the process to A890.

[0381] Similarly, when receiving a split bill non-establishment notice from the messaging server 40 through the communication I / F 22 (B750), the control unit 21 of terminal B causes the received split bill non-establishment notice to be displayed on the display unit 24 (B760). Then, the control unit 21 of terminal B transfers the process to B890.

[0382] On the other hand, if it is determined that the split bill is established in the MGS split bill approval management process (M740: YES), the control unit 41 transmits a split bill establishment notice to terminal A and terminal B respectively through the communication I / F 44 (M810).

[0383] When receiving a split bill establishment notice from the messaging server 40 through the communication I / F 22 (A810), the control unit 21 of terminal A transmits split bill settlement request information to the messaging server 40 through the communication I / F 22 (A820).

[0384] Similarly, when receiving a split bill establishment notice from the messaging server 40 through the communication I / F 22 (B810), the control unit 21 of terminal B transmits split bill settlement request information to the messaging server 40 through the communication I / F 22 (B820).

[0385] When the communication I / F 44 receives the split settlement request information from the terminal A and the terminal B respectively (M820), the control unit 41 transmits the split settlement request information to the server 10 through the communication I / F 44 (M830).

[0386] When the communication I / F 14 receives the split settlement request information from the messaging server 40 (S830), the control unit 11 of the server 10 performs the split settlement process (S840).

[0387] Next, the control unit 11 transmits the split settlement result to the messaging server 40 through the communication I / F 14 (B850).

[0388] Thereafter, the control unit 11 determines whether to end the process (S890). If it is determined to continue the process (S890: NO), the process returns to S620. On the other hand, if it is determined to end the process (S890: YES), the control unit 11 ends the split settlement management process.

[0389] When the communication I / F 44 receives the split settlement result from the server 10 (M850), the control unit 41 transmits the received split settlement result to the terminal A and the terminal B respectively through the communication I / F 44 (M860).

[0390] Thereafter, the control unit 41 determines whether to end the process (M890). If it is determined to continue the process (M890: NO), the process returns to M610. On the other hand, if it is determined to end the process (M890: YES), the control unit 41 ends the MSG split settlement management process.

[0391] When the communication I / F 22 receives the split settlement result from the messaging server 40 (A860), the control unit 21 of the terminal A causes the received split settlement result to be displayed on the display unit 24 (A870).

[0392] Similarly, when the communication I / F 22 receives the split settlement result from the messaging server 40 (B860), the control unit 21 of terminal B causes the received split settlement result to be displayed on the display unit 24 (B870).

[0393] Thereafter, the control unit 21 of terminal A determines whether to end the process (A890). If it is determined to continue the process (A890: NO), the process returns to A610. On the other hand, if it is determined to end the process (A890: YES), the control unit 21 of terminal A ends the split settlement process.

[0394] Similarly, the control unit 21 of terminal B determines whether to end the process (B890). If it is determined to continue the process (B890: NO), the process returns to B610. On the other hand, if it is determined to end the process (B890: YES), the control unit 21 of terminal B ends the split settlement process.

[0395] <Effect of the Fifth Embodiment> In the fifth embodiment, the terminal 20 includes the user of its own terminal 20 and the user of a different terminal 20, and displays a chat room (an example of a chat room, not limited) including messages and the like (not limited, an example of content) sent from its own terminal 20 to a different terminal 20 and messages and the like sent from a different terminal 20 to its own terminal 20 on the screen of the messaging application. In this case, it shows a configuration in which at least information on the surplus or deficit amount of the user of its own terminal 20 (not limited, an example of information on the first amount) is displayed in the chat room. As an example of the effect obtained by such a configuration, the user can be made to confirm the information on the first amount in the chat room.

[0396] Further, in the fifth embodiment, it shows a configuration in which the user of a different terminal 20 is selected based on the chat room selected by the user of the terminal 20. As an example of the effect obtained by such a configuration, based on the chat room selected by the user of the terminal, users of different terminals can be easily selected.

[0397] Further, in the fifth embodiment, the terminal 20 includes users of its own terminal 20 and users of different terminals 20, and displays in the display unit 24 a chat room (an example of a chat room, not limited) that includes a message (an example of content, not limited) transmitted from its own terminal 20 to a different terminal 20 and a message (an example of content, not limited) transmitted from a different terminal 20 to its own terminal 20. Then, the terminal 20 shows a configuration of displaying a split payment request message (an example of a notification regarding a request for a money transfer process or a receipt process between at least different terminals based on the first settlement information, not limited) in the chat room. As an example of the effect obtained by such a configuration, a notification regarding a request for a money transfer process or a receipt process between at least different terminals can be notified to the user in an easy-to-understand form of display in the chat room.

[0398] Also, in the fifth embodiment, the terminal 20 includes at least the user of its own terminal 20, and displays in the display unit 24 a chat room (an example of a chat room, not limited) that includes a message (an example of content, not limited) transmitted from its own terminal 20. Then, the terminal 20 shows a configuration of displaying a split payment request message (an example of a notification regarding the transmission of the first settlement information, not limited) in the chat room. As an example of the effect obtained by such a configuration, a notification regarding the transmission of the first settlement information can be notified to the user in an easy-to-understand form of display in the chat room.

[0399] <Fifth Modification Example (1)> In the fifth embodiment, in the messaging application, the terminal 20 can also display in the chat room content such as a message sent from the account of a company that provides a service related to a money transfer process or a receipt process.

[0400] FIG. 5-14 is a diagram showing an example of a talk room screen in this modified example, and shows an example of a screen displayed on the display unit 24 of the terminal 20 of user B.B. This talk room screen is almost the same as the talk room screen in FIG. 5-5, but the difference is that the talk partner of user B.B. displayed in the talk room is not user A.A., but the official account of the payment application (not limited to this, an example of an account of a company that provides services related to money transfer processing or receipt processing). In this example, user B.B. registers the official account of the payment application as a friend in advance in the messaging application.

[0401] In this case, when the money transfer from user B.B. to user A.A. is completed, on the talk room screen of the messaging application of the terminal 20 of user B.B., as an example (not limited to this), an icon image of the official account of the payment application (in this example, "Pay") is associated with a message sent from the official account of the payment application (more specifically, the server 10), and a money transfer completion message indicating that the money transfer to the user of user A.A. has been completed is displayed. This money transfer completion message is a message corresponding to a money transfer completion notification, and as an example (not limited to this), it includes the content indicating that the over - under amount (in this example, "2,250 yen") has been transferred from user B.B. to user A.A. using the payment application, together with the name of the payment application (in this example, "Payment App").

[0402] Also, below the money transfer completion message, as a message sent from the official account of the payment application, a split payment completion message is displayed.

[0403] This modified example shows a configuration in which the talk room screen of the messaging application includes the user of the terminal 20 and the official account of the payment service (not limited to this, an example of an account of a company that provides services related to money transfer processing or receipt processing). As an example of the effects obtained by such a configuration, information distributed from the account of a company that provides services related to remittance processing or receipt processing can be notified to the user in an easy-to-understand form of display in a chat room.

[0404] <Fifth Modification Example (2)> In the fifth embodiment, by way of example and not limitation, in a case where, after a split payment request is made, the split payment members do not perform the settlement of the split payment for some time, it is also possible to issue a reminder or a notice of urging for the split payment from the terminal 20 of the split payment master via the messaging server 40.

[0405] FIG. 5-15 is a diagram showing an example of a split payment request reminder notification displayed on the display unit 24 of the terminal 20 of user B.B when a certain period of time has elapsed without user B.B replying to user A.A in FIG. 5-4. In this example, on the OS standard standby screen of the terminal 20, by way of example and not limitation, a push notification from the messaging server 40, as a split payment request reminder notification for notifying that there is a reminder of the split payment request from user A.A, together with the text "Messaging App A.A: There is a request for split payment", an activation icon shown as "Open" by way of example and not limitation for starting the messaging application is displayed.

[0406] FIG. 5-16 is a diagram showing an example of a talk room screen displayed on the display unit 24 of the terminal 20 of user B.B based on the operation of the activation icon in FIG. 5-15. On this talk room screen, below the split payment request message on the talk room screen of FIG. 5-4, there is displayed a split payment reminder message, which is an example of the content transmitted and received between the terminals 20 using the messaging application and is a type of split payment reminder notification for prompting the user to reconfirm (remind) the split payment.

[0407] This split bill reminder message shows, by way of example and not limitation, the same content as the split bill request message on the chat room screen in FIG. 5-4, along with the text “Reminder” and the name of the payment application “Payment App”. By checking this split bill reminder message, user B.B. can ensure that the split bill is settled without forgetting.

[0408] FIG. 5-17 shows another example of the chat room screen in this case. This chat room screen, similar to FIG. 5-14, shows an example of a chat screen between user B.B. and the official account of the payment application. In this example, a split bill reminder message similar to FIG. 5-16 is displayed in association with the icon image of the official account as a message sent from the official account of the payment application.

[0409] <Example 6> Example 6 is an example for performing split billing within a group including users (multiple accounts) of a plurality of terminals 20 formed within a messaging application. Example 6 is an example in which the concept of a group is added to Example 5.

[0410] The content described in Example 6 is applicable to any of the other examples and any of the other variations. Also, the same reference numerals are given to the same components as those already shown, and repeated descriptions are omitted.

[0411] <Example Display Screen> FIG. 6-1 shows an example of a group chat room screen by the messaging application in this embodiment. This group chat room screen shows, by way of example and not limitation, a chat room screen for conducting group chat in a group (in this example, a "travel circle" group) that includes five users (User A.A to User E.E), and shows an example of the group chat room screen displayed on the display unit 24 of the terminal 20 of User A.A. Group chat is an example of chat, and a group chat room is an example of a chat room.

[0412] In this group chat room screen, by way of example and not limitation, messages sent from oneself (User A.A) are displayed on the right side of the screen, and messages sent from other users (User B.B to User E.E) are displayed on the left side of the screen.

[0413] In this example, a message sent from User A.A requesting a split of the money used in the previous trip is displayed, along with a message from User B.B approving User A.A's request and a message from User D.D proposing to go on a trip again.

[0414] At the bottom of the screen, function icons corresponding to a plurality of functions of the messaging application are displayed. In this example, the "split bill icon" displayed in the lower right is shown in a state where it has been touched by User A.A.

[0415] FIG. 6-2 is a diagram showing an example of a shopping settlement history selection screen displayed on the display unit 24 of the terminal 20 based on the operation of the split bill icon on the group chat room screen of FIG. 6-1. On this shopping settlement history selection screen, a plurality of shopping settlement histories by oneself (User A.A) are displayed. In this example, a plurality of shopping settlement histories such as "AA Rent-a-Bike", "BB Supermarket", and "CC Bento" are displayed.

[0416] FIG. 6-3 is a diagram showing an example of a group chat room screen displayed on the display unit 24 of the terminal 20 based on the operation of the split payment request icon on the shopping settlement history selection screen of FIG. 6-2, and shows an example of a screen displayed on the display unit 24 of the terminal 20 of user B.B. On this group chat room screen, as a split payment request message from user A.A, a message including the name of the payment application (in this example, "Payment App"), the over / under amount of user B.B (in this example, "Pay 900 yen"), and the details of the split payment for each split payment member (breakdown of the split payment) is displayed. Also, the split payment request message includes, by way of example and not limitation, a settlement icon for performing settlement, a shopping settlement history registration icon for registering the payment amount based on one's own shopping settlement history, and a rejection icon for rejecting the split payment request.

[0417] <Data Configuration> FIG. 6-4 is a diagram showing an example of information stored in the storage unit 15 of the server 10 in this embodiment. The storage unit 15 stores, by way of example and not limitation, a messaging application management processing program 451, messaging application user registration data 453, a split payment management database 457, and in addition, a group management database 459.

[0418] FIG. 6-5 is a diagram showing a data configuration example of a fourth split payment management database 457B which is an example of the split payment management database 457 in this embodiment. In the fourth split payment management database 457B, in each split payment management data, a split payment group ID is stored instead of the split payment member ID in each split payment management data of the third split payment management database 457A (see FIG. 5-9).

[0419] The split payment group ID stores the group ID stored in the group management database 459 for this group.

[0420] In addition, each sharing management data stores a sharing member ID. The sharing member ID stores the messaging application ID of the user included in the group identified by the sharing group ID.

[0421] Note that in this embodiment, it is assumed that the messaging application IDs of all users included in the group identified by the sharing group ID are included in the sharing member ID, but it is not limited thereto. As an example rather than a limitation, instead of all users included in the group, some users included in the group can be set as sharing members. In this case, the messaging application ID of the user selected as the sharing member among the users included in the group may be stored in the column of the sharing member ID.

[0422] FIG. 6-6 is a diagram showing an example of the data configuration of the group management database 459. The group management database 459 stores group management data generated for each group. Each group management data stores, as an example rather than a limitation, a group ID, a group name, and group member data.

[0423] The group member data stores, as an example rather than a limitation, the user name of the user included in this group and the messaging application ID of this user in association with each other.

[0424] <Process> FIG. 6-7 is a flowchart showing an example of the processing flow executed by each device in this embodiment. This process is a process in which steps of A910 as the process of terminal A, steps of MSG sharing management process 910 as the process of messaging server 40, and steps of S620 and S630 as the process of server 10 are added to the process part of FIG. 5-10 among the processes of FIGS. 5-10 to 5-12.

[0425] First, the control unit 21 of terminal A transmits a group settlement start notification for requesting the start of group settlement to the messaging server 40 via the communication I / F 22 (A910). Then, the control unit 21 of terminal A transfers the process to A640.

[0426] When the messaging server 40 receives a group settlement start notification from terminal A via the communication I / F 44 (M910), the control unit 41 of the messaging server 40 transfers the process to M620.

[0427] <Effect of the Sixth Embodiment> In the sixth embodiment, the terminal 20 includes a group chat room (not limited to, for example, a chat room) that includes a plurality of settlement members other than the settlement master, information on the excess or deficiency amount of the settlement master (not limited to, for example, information on the first amount), and information on the excess or deficiency amount of each settlement member other than the settlement master (not limited to, for example, information on the amount that each of a plurality of users sends or receives based on the first settlement information). The configuration shows that the excess or deficiency amount information is displayed in the group chat room. As an example of the effect obtained by such a configuration, the first amount that the user of the terminal sends or receives and the amounts that each of a plurality of users including users of different terminals send or receive can be notified to the user in an easy-to-understand form of display in the chat room.

[0428] <Sixth Variation (1)> In the sixth embodiment, a process of excluding at least one user among the plurality of users included in the group from the settlement members may or may not be performed.

[0429] FIGS. 6-8 are diagrams showing an example of a settlement target member selection screen for selecting (setting) settlement target members displayed on the display unit 24 of the terminal 20, and showing an example of a screen displayed on the display unit 24 of the terminal 20 of user A.A. On this split bill target member selection screen, checkboxes are provided in association with the icon images and user names of members other than oneself (User B.B to User E.E) included in the group for which split billing is to be performed (in this example, the group of "travel circle") (hereinafter referred to as the "target group").

[0430] As an example rather than a limitation, in the initial state, all checkboxes are checked, but by performing an operation to uncheck a checkbox, the user whose checkbox has been unchecked can be configured to be excluded from the split bill members. In this example, checkboxes are checked for User B.B, User D.D, and User E.E, but the unchecked state of User C.C is shown.

[0431] Also, at the bottom of the screen, there is a split bill target member display area where the users currently set as split bill target members (users with checkboxes checked) are displayed. In the split bill target member display area, as an example rather than a limitation, the icon images and user names of the users currently set as split bill target members are displayed. Also, an "X mark" is displayed in the upper right of the icon image, and by operating this "X mark", the user can be configured to be excluded from the split bill target members. In this example, the state where User B.B, User D.D, and User E.E are set as split bill target members is shown.

[0432] FIGS. 6-9 are flowcharts showing an example of the flow of processing executed by each device in this modification. This processing is the processing in which steps A920 to A940 are added as the processing of terminal A and steps M920 and M940 are added as the processing of messaging server 40 to the processing in FIG. 6-7.

[0433] After M910, the control unit 41 of the messaging server 40 transmits the information of the members included in the group (hereinafter referred to as "group member information") to the terminal A via the communication I / F 44 (M920).

[0434] When the communication I / F22 receives group member information from the messaging server 40 (A920), the control unit 21 of terminal A executes a second member selection process (A930). Specifically, by way of example and not limitation, a split expense member selection screen as shown in FIGS. 6-8 is displayed on the display unit 24, and based on a selection operation on the input / output unit 23, a member who requests a split expense is selected.

[0435] Thereafter, the control unit 21 of terminal A transmits member selection information regarding the member selected in A930 to the messaging server 40 via the communication I / F22 (A940). Then, the control unit 21 of terminal A moves the process to A640.

[0436] When the control unit 41 receives member selection information from terminal A via the communication I / F44 (M940), it adds / removes the user based on the received member selection information from / to the split expense members, and then moves the process to M620.

[0437] This modified example shows a configuration in which one terminal 20 executes a process of deleting at least one user from among a plurality of users included in a group talk room (an example of a chat room, by way of example and not limitation). As an example of the effect obtained by such a configuration, by executing a process of deleting at least one user from among a plurality of users including users of different terminals included in a chat room, by way of example and not limitation, an arbitrary user can be excluded from the target of the split expense.

[0438] <Sixth Modified Example (2)> In the sixth embodiment, by way of example and not limitation, in the terminal 20 of the split expense master, a process of adding a user not included in the group talk room (hereinafter referred to as an "off-group member") to the split expense members may or may not be performed.

[0439] FIG. 6-10 is a diagram showing an example of a split-the-bill member selection screen in this modified example. Unlike the split-bill member selection screen in Figure 6-8, this split-bill member selection screen has an add icon labeled "Add friends outside the group" as an example, not a limitation, to add split-bill member candidates from among users other than those included in the target group.

[0440] FIG. 6-11 is a diagram showing an example of a screen that is displayed when the add icon is operated on the bill splitting member selection screen of FIG. 6-10. In the center of this screen, a friend list display area is provided for selecting and setting potential split-bill members from among users registered as friends. The friend list display area displays a list of icon images and usernames of users who are not members of the target group who are split-bill members, but who are registered as friends by user AA. In this example, user XX, user YY, user ZZ, etc. are displayed in a list, with the check mark for user ZZ set to "ON."

[0441] As in Figures 6-8 and 6-9, a split-the-bill member display area is provided at the bottom of the screen. In this example, in addition to users BB, DD, and EE, user ZZ is set as a split-the-bill candidate.

[0442] In addition, an "OK icon" is displayed at the bottom of the screen, and by operating this OK icon, the currently set users can be confirmed as the members to be split.

[0443] FIG. 6-12 is a diagram showing an example of a bill splitting member selection screen that is displayed when the OK icon is operated on the bill splitting member selection screen of FIG. 6-11. On this split payment target member selection screen, a list of users included in the target group is displayed as group members, and below that, as friends, the icon image and user name of user Z.Z, who is a non-group member added as a split payment target member on the screen of FIG. 6-11, are displayed. In this example, among the users included in the target group, the checks for three users, user B.B, user D.D, and user E.E, are set to "ON", and the check for the added user Z.Z is also shown to be "ON".

[0444] Also, in the split payment target member display area at the bottom of the screen, in addition to user B.B, user D.D, and user E.E, the state where user Z.Z is set as a split payment target member candidate is shown.

[0445] FIG. 6-13 is a diagram showing an example of a shopping payment history selection screen displayed based on the operation of the shopping payment history registration icon on the split payment target member selection screen of FIG. 6-6. This shopping payment history selection screen corresponds to the shopping payment history selection screen of FIG. 6-2. In this example, the state where the split payment request icon at the bottom of the screen has been operated by user A.A is shown.

[0446] FIG. 6-14 is a diagram showing an example of a group talk room screen displayed on the display unit 24 of terminal 20 based on the operation of the split payment request icon on the shopping payment history selection screen of FIG. 6-13, and shows an example of the screen displayed on the display unit 24 of the terminal 20 of user Z.Z. On this group talk room screen, similar to FIG. 6-3, a split payment request message from user A.A is displayed. And in this example, the state where the shopping payment history registration icon included in the split payment request message has been operated by user Z.Z is shown.

[0447] FIG. 6-15 is a diagram showing an example of a shopping settlement history selection screen displayed based on the operation of the shopping settlement history registration icon on the group talk room screen of FIG. 6-14, and shows an example of a screen displayed on the display unit 24 of the terminal 20 of user Z.Z. On this shopping settlement history selection screen, as an example and not by way of limitation, a plurality of shopping settlement histories such as "HH Supermarket", "II Cafe", and "JJ Electric Appliance" are displayed as the shopping settlement histories by user Z.Z. And in this example, a state where the shopping settlement history of "II Cafe" is checked is shown.

[0448] FIG. 6-16 is a diagram showing an example of a group talk room screen displayed based on the operation of the registration icon on the shopping settlement history selection screen of FIG. 6-15, and shows an example of a screen displayed on the display unit 24 of the terminal 20 of user A.A. On this group talk room screen, as an example and not by way of limitation, as a split payment request message associated with user Z.Z, a split payment request message including the split payment content based on the shopping settlement history registered by user A.A and the split payment content based on the shopping settlement history registered by user Z.Z is displayed.

[0449] FIG. 6-17 is a diagram showing another example of the split payment member selection screen displayed on the display unit 24 of the terminal 20. On this split payment member selection screen, different from the split payment member selection screen of FIG. 6-10, for the purpose of adding users other than the users included in the target group as split payment member candidates, as an example and not by way of limitation, in the area indicated as "Add friends outside the group", a first addition icon indicated as "Add from friends" for selecting a user to be a split payment member candidate from among the users registered as friends in the messaging application, and a second addition icon indicated as "Search by phone number" for selecting a user to be a split payment member candidate by inputting a phone number are displayed.

[0450] FIG. 6-18 is a flowchart showing an example of the flow of processing executed by each device in this modification. This processing is the processing in which steps of A950 are added as the processing of terminal A and steps of M950 are added as the processing of the messaging server 40 to the processing of FIG. 6-9.

[0451] After M940, the control unit 21 of terminal A causes the display unit 24 to display, as an example and not by limitation, a split-member selection screen as shown in FIGS. 6-10 and 6-11, and selects a non-group member based on a selection operation on the input / output unit 23. Then, the control unit 21 of terminal A transmits group-out member selection information regarding the selected non-group member to the messaging server 40 via the communication I / F 22 (A950). Then, the control unit 21 of terminal A moves the processing to A640.

[0452] When receiving group-out member selection information from terminal A via the communication I / F 44 (M950), the control unit 41 adds the non-group member based on the received group-out member selection information to the split members, and then moves the processing to M620.

[0453] In this modification, one terminal 20 executes processing for adding a user not included in a group talk room (an example of a chat room, not by limitation) as a split member. Then, the terminal 20 receives, from the server 10 via the communication I / F 22, shortage / excess amount information including information on the shortage / excess amount of the user added to the group talk room (an example of the third amount that the added user not included in the chat room sends or receives), information on the shortage / excess amount of the user of one terminal 20 (an example of the first amount, not by limitation), and information on the shortage / excess amount of the users of other terminals 20 included in the group (an example of the second amount, not by limitation). Then, the terminal 20 shows a configuration in which the received shortage / excess amount information is displayed in the group talk room. As an example of the effects obtained by such a configuration, after adding a user not included in the chat room, not only the first amount and the second amount, but also the amount information considering the third amount that the added user sends or receives can be notified to the user in an easy-to-understand form of display in the chat room.

[0454] In addition, this modified example shows a configuration in which the first amount, the second amount, and the third amount are determined based on the shopping settlement history by an added user not included in the group talk room and the shopping settlement history by the split payment master. As an example of the effects obtained by such a configuration, the first amount, the second amount, and the third amount can be appropriately determined based on the third settlement information related to the third settlement based on the processing by an added user not included in the chat room and the first settlement information.

[0455] <Sixth Modified Example (3)> In the sixth embodiment, it is considered that some users may feel uncomfortable requesting a split payment from other users and may hesitate to request a split payment. Therefore, by way of example and not limitation, the split payment request notification may or may not be displayed on the display unit 24 of the terminal 20 based on the group name.

[0456] FIG. 6-19 is a diagram showing an example of a split payment request notification displayed on the standby screen of the display unit 24 of the terminal 20 in this modified example, and shows an example of a screen displayed on the display unit 24 of the terminal 20 of user B.B. On this standby screen, by way of example and not limitation, a push notification associated with the messaging application, which is a split payment request notification for notifying that there has been a split payment request, is displayed together with the characters "There is a request for split payment in the Messaging App Travel Circle", and an activation icon shown as "Open" by way of example and not limitation for activating the messaging application.

[0457] Rather than being a split - bill request from the user of the split - bill master, as shown in the standby screen shown in FIG. 5 - 15, it is displayed as a split - bill request from the group (in this example, the group with the group name "Travel Circle") for which the split - bill master has requested a split - bill, which is different from the split - bill request notification in FIG. 5 - 15.

[0458] FIG. 6 - 20 is a diagram showing an example of a talk - room screen displayed on the display unit 24 of the terminal 20 of user B.B. based on the operation of the start icon on the standby screen of FIG. 6 - 19. On this talk - room screen, as a split - bill request from the group "Travel Circle", a split - bill request message is displayed in association with the icon image and the group name of this group.

[0459] In this modified example, the terminal 20 includes the user of its own terminal 20 and the users of different terminals 20, and displays a group talk - room including the messages sent from its own terminal 20 to different terminals 20 and the messages sent from different terminals 20 to its own terminal 20 on the display unit 24. And when the terminal 20 receives a split - bill request notification from a different terminal 20 through the communication I / F 22, it shows a configuration of displaying the split - bill request notification in the group talk - room based on the group name of this group talk - room. As an example of the effect obtained by such a configuration, when receiving a notification of a risk request for a remittance process or a receipt process based on settlement information related to settlement from different terminals through the communication unit, the request notification is displayed in the chat - room based on the group name of the chat - room, so that it is possible to conceal that it is a request notification from different terminals. As a result, the psychological burden of making a request to other users can be reduced.

[0460] <Example 7> Example 7 is an example in which users of different terminals 20 add split - bill members. The seventh embodiment is an embodiment in which a configuration for adding a split - payment member by a user of a different terminal 20 is added to the above - described embodiments.

[0461] The content described in the seventh embodiment is applicable to any of the other embodiments and any of the other modification examples. Also, for components identical to the components already described, the same reference numerals are given, and repeated descriptions are omitted.

[0462] <Example display screen> FIG. 7 - 1 is a diagram showing an example of a split - payment content confirmation screen in this embodiment, and shows an example of a screen displayed on the display unit 24 of the terminal 20 of user B.B. The configuration of this split - payment content confirmation screen is, by way of example and not limitation, substantially the same as that of FIG. 3 - 2, but the display is somewhat different. Specifically, on this split - payment content confirmation screen, by way of example and not limitation, a settlement icon for performing settlement, a shopping settlement history addition icon for adding a shopping settlement history, and a split - payment member addition icon for adding a split - payment member are displayed at the lower part of the screen.

[0463] FIG. 7 - 2 is a diagram showing an example of a split - payment member search screen displayed based on the operation of the split - payment member addition icon on the split - payment content confirmation screen of FIG. 7 - 1. On this split - payment member search screen, a telephone number display column in which the input telephone number is displayed is provided together with the text "Please enter a telephone number and search". To the right of the telephone number display column, a search button for searching for the user of the input telephone number is provided, and based on the operation of this search button, the user of the input telephone number is searched. In this example, "User F.F" is obtained as the search result, and a state in which the icon image and user name of User F.F are displayed is shown.

[0464] Also, below the search result, a split - payment member addition icon shown as "Add to member" by way of example and not limitation for adding the user obtained as the search result to the split - payment members is displayed.

[0465] FIG. 7-3 is a diagram showing an example of a split payment content confirmation screen displayed based on the operation of the split payment member addition icon on the split payment member search screen of FIG. 7-2. On this split payment content confirmation screen, as a result of adding user F.F obtained as a search result in FIG. 7-2 as a split payment member, in addition to oneself (user B.B), user A.A, user C.C, user D.D, and user E.E, an area for displaying a list of paid amounts and an area for displaying a list of excess / deficit amounts associated with the icon image and user name of user F.F are displayed.

[0466] <Effect of the Seventh Embodiment> In the seventh embodiment, a process of adding a user of a terminal 20 (not limited, an example of a second terminal) different from the initially set split payment members is executed by a terminal 20 (not limited, an example of a first terminal) of split payment members different from the split payment master. And in the excess / deficit amount information in this case, it shows a configuration including information on the excess / deficit amount (not limited, the fourth amount) of the added user. As an example of the effect obtained by such a configuration, after adding a user of a second terminal different from the first terminal, it is possible to acquire information on the fourth amount that the added user of the second terminal sends or receives.

[0467] <Eighth Embodiment> The eighth embodiment is an embodiment in which the terminal 20 automatically selects a shopping settlement history to be subject to split payment from among a plurality of shopping settlement histories by the user of its own terminal 20. Depending on the user of the terminal 20, it may be troublesome to search and select the shopping settlement history to be subject to split payment by oneself. This is remarkable when the number of shopping settlement histories is large.

[0468] The content described in the eighth embodiment is applicable to any of the other embodiments and any of the other modified examples. Also, for components identical to the components already shown, the same reference numerals are given and repeated explanations are omitted.

[0469] In this embodiment, the control unit 21 of the terminal 20 automatically selects a shopping payment history based on the user information of the user of its own terminal 20. In this embodiment, the user information of the user of its own terminal 20 is taken as an example (not limited to this) to be the information of its own terminal 20 or the location information regarding the user of its own terminal 20.

[0470] The automatic selection of the shopping payment history includes, in addition to finally determining (finally determining and registering) the automatically selected shopping payment history as the object of splitting the bill, also proposing (also referred to as suggesting) the automatically selected shopping payment history as a candidate for the object of splitting the bill. In the latter case, the user manually selects a shopping payment history from among the shopping payment histories automatically selected and proposed by the control unit 21 and makes a final decision. This is the same in the embodiments described later.

[0471] <Example display screen> FIG. 8-1 is a diagram showing an example of a shopping payment history selection screen in this embodiment, and shows an example of a screen displayed on the display unit 24 of the terminal 20 of user A.A. On this shopping payment history selection screen, a search icon shown as "Search for payment candidates" (not limited to this, but as an example) for automatically selecting a shopping payment history to be the object of splitting the bill is displayed.

[0472] FIG. 8-2 is a diagram showing a display example displayed based on the operation of the search icon on the shopping payment history selection screen of FIG. 8-1. On this screen, among the plurality of shopping payment histories on the shopping payment history selection screen of FIG. 8-1, the shopping payment history of "AA Rental Cycle" and the shopping payment history of "BB Supermarket" are displayed in a state of being selected (hereinafter referred to as "selected display"), in a different manner from other shopping payment histories (for example, the shopping payment history of "CC Bento" as an example, not limited to this). The shopping payment history displayed in this selected state is the shopping payment history automatically selected and proposed (suggested) by the control unit 21 of the terminal 20.

[0473] Note that the selected display can be in a form different from that of the unselected shopping settlement history. By way of example and not limitation, examples of the form of the selected display include applying a specific color (such as blue, green, red, etc.) or hatching (such as cross-hatching) to the display area of the selected shopping settlement history, applying a specific color to the frame (outer frame) of the display area of the selected shopping settlement history, blinking the frame (outer frame) of the display area of the selected shopping settlement history, representing the font of the characters of the selected shopping settlement history in a special font, and any of a plurality of such forms can be applied as the form of the selected display.

[0474] In this way, when the split payment request icon at the lower part of the screen is operated with at least one shopping settlement history being selected and displayed, it becomes possible to register the selected and displayed shopping settlement history as the target for split payment.

[0475] <Data Configuration> FIG. 8-3 is a diagram showing an example of a third user management database 155C which is an example of the user management database 155 stored in the storage unit 15 of the server 10 in this embodiment. In each user management data of this third user management database 155C, by way of example and not limitation, a payment application ID, an electronic money account balance, and shopping settlement history data are stored.

[0476] In the shopping settlement history data, by way of example and not limitation, a shopping settlement ID, a store ID, a store name, a shopping settlement date and time, a shopping settlement amount, a shopping settlement content, and shopping settlement location information are stored in association. The shopping settlement ID to the shopping settlement content are as described above.

[0477] In the shopping settlement location information, by way of example and not limitation, the location information of the terminal 20 at the time when the shopping settlement is made, or the user of the terminal 20 is stored. Note that the shopping payment location information may store two-dimensional location information or three-dimensional location information.

[0478] In this case, as one method, at regular intervals or at the timing when an operation to perform payment is made on the terminal 20, the terminal 20 can transmit information on the calculated terminal position to the server 10. Then, in the shopping payment process, the server 10 can store, as the shopping payment location information, the latest information on the calculated terminal position received from the terminal 20 in the user management data in association with other information.

[0479] Note that if the user always has the terminal 20 with them, the position of the terminal 20 is the same as the position of the user of the terminal 20. Therefore, the calculated terminal position is both the calculated position of the terminal 20 and the calculated position of the user of the terminal 20.

[0480] In this embodiment, by way of example and not limitation, according to a registration operation by the user of the terminal 20, location information assumed to be the daily living range or activity range of the user of the terminal 20, such as the place of residence (or the surrounding area) of the user of the terminal 20, the place of work (or the surrounding area) of the user of the terminal 20, the places of residence (or the surrounding areas) of the relatives and friends of the user of the terminal 20, and the places frequently visited by the user of the terminal 20, is registered in advance as specific location information in a payment application or the like.

[0481] Note that the specific location information may be stored and managed in the storage unit 15 of the server 10, or may be stored and managed in the storage unit 28 of the terminal 20. Alternatively, it may be stored and managed in both the server 10 and the terminal 20.

[0482] <Process> FIG. 8-4 is a diagram showing an example of the flow of processing executed by each device in this embodiment. This process is a process in which, for the processing part of FIG. 2-17 among the processes of FIGS. 2-17 to 2-19, as the processing of terminal A, the step of A170 is replaced with the step of A175.

[0483] After S150, the control unit 11 of the server 10 transmits a plurality of shopping settlement histories (including shopping settlement position information) associated with the user of terminal A to terminal 20 via the communication I / F 14 (S160).

[0484] When receiving the shopping settlement history (including shopping settlement position information) from the server 10 via the communication I / F 22 (A160), the control unit 21 of terminal A executes a shopping settlement history automatic selection process (A175). Specifically, by way of example and not limitation, among the plurality of shopping settlement histories, the shopping settlement histories whose shopping settlement positions are at a set distance or more (or exceeding the set distance) away from a specific position corresponding to the pre-registered specific position information are identified. Then, the identified shopping settlement histories are selected as the shopping settlement histories to be subject to the split payment.

[0485] If the shopping settlement history is automatically selected in this way, the control unit 21 of terminal A, by way of example and not limitation, picks up and displays the automatically selected shopping settlement history as a candidate for the split payment to propose (suggest) to the user of terminal 20. Then, the control unit 21 of terminal A moves the process to A180.

[0486] By doing so, it is possible to automatically select the shopping settlement history corresponding to the shopping settlement made at a position far from the position registered as the daily life range or activity range of the user of terminal 20.

[0487] Note that the process of proposing the selected shopping settlement history to the user of terminal 20 is not essential, and this process may be omitted.

[0488] Also, here, an example is given where the control unit 21 of the terminal 20 executes a shopping settlement history automatic selection process instead of the second shopping settlement history selection process in the process of FIG. 2-17, but it is not limited thereto. By way of example rather than limitation, the control unit 21 of the terminal 20 may or may not execute a shopping settlement history automatic selection process instead of the first shopping settlement history selection process in the process of FIG. 1.

[0489] <Effect of the Eighth Embodiment> In the eighth embodiment, the terminal 20 automatically selects a shopping settlement history (an example of the first settlement information, not a limitation) from among a plurality of shopping settlement histories (an example of a plurality of settlement information, not a limitation) by the user of its own terminal 20, and transmits it to the server 10 through the communication I / F 22 (an example of the communication unit of the terminal, not a limitation). Further, the terminal 20 receives, through the communication I / F 22, information on the excess or shortage amount (an example of at least the first amount among the first amount that the user of the terminal remits or receives and the second amount that the user of a terminal different from the terminal remits or receives, based on the first settlement information, not a limitation) based on the transmitted shopping settlement history from the server 10. Then, the terminal 20 shows a configuration in which, based on the excess or shortage amount, a split settlement request process or a split settlement result reception process (an example of a remittance process or a reception process based on the first amount, not a limitation) is executed by the control unit 21 (an example of the control unit of the terminal, not a limitation). As an example of the effect obtained by such a configuration, based on the fact that the terminal has transmitted the first settlement information among a plurality of settlement information regarding the settlement by the user of the terminal through the communication unit, the terminal can execute, by the control unit, a remittance process or a reception process based on the information on the first amount based on the first settlement information, and can easily remit or receive money, thereby improving the convenience for the user.

[0490] In addition, in the eighth embodiment, the terminal 20 includes a processor that reads a program stored in the memory and executes processing based on this program. The processor automatically selects a shopping payment history (an example of first payment information, not limited) from among a plurality of shopping payment histories (an example of a plurality of payment information, not limited) made by the user of its own terminal 20, and transmits it to the server 10 via the communication I / F 22 (an example of a communication unit of the terminal, not limited). The processor also receives, via the communication I / F 22, information on the excess or deficiency amount (an example of at least the first amount among the first amount that the user of the terminal remits or receives and the second amount that the user of a terminal different from the terminal remits or receives, based on the first payment information, not limited) based on the transmitted shopping payment history from the server 10. Based on the excess or deficiency amount, the processor executes a split settlement request process and a split settlement result reception process (an example of a remittance process or a receipt process based on the first amount, not limited). Even with such a configuration, the same effects as described above can be obtained.

[0491] In addition, the eighth embodiment shows a configuration in which the terminal 20 selects a shopping payment history based on the user information of the user of the terminal 20. As an example of the effect obtained by such a configuration, the terminal can select first payment information in accordance with the user of the terminal.

[0492] In addition, the eighth embodiment shows a configuration in which the above user information includes information on the calculated terminal position (an example of a position related to the terminal or the user of the terminal, not limited). As an example of the effect obtained by such a configuration, the terminal can appropriately select the first payment information in consideration of the position related to the terminal or the user of the terminal.

[0493] <Eighth Variation (1)> The method of selecting the shopping payment history in the shopping payment history automatic selection process described in the eighth embodiment is merely an example and is not limited thereto.

[0494] By way of example rather than limitation, the prefecture or municipality where the user of the terminal 20 resides, etc. may be registered in advance, and a shopping settlement history settled in a prefecture different from the registered prefecture may be selected, or a shopping settlement history settled in a municipality different from the registered municipality may be selected, or it may not be done so.

[0495] Also, the position information of well-known tourist spots is stored in the storage unit 28 in advance in association with the map data. Then, the control unit 21 may select a shopping settlement history settled at a position corresponding to the tourist spot stored in the storage unit 28, or it may not be done so.

[0496] <Eighth Modification Example (2)> In the eighth embodiment, the user information of the own terminal 20 is described as information related to the position, but it is not limited thereto. By way of example rather than limitation, the schedule information of the user of the terminal 20 may be included in the user information, and the control unit 21 of the terminal 20 may select a shopping settlement history based on the schedule information of the user of the terminal 20, or it may not be done so.

[0497] FIG. 8-5 is a diagram showing an example of a shopping settlement history selection screen in this modification example, and shows an example of a screen displayed on the display unit 24 of the terminal 20 of user A.A. On this shopping settlement history selection screen, based on the operation of the shopping settlement history search icon, together with the characters "Payment App is requesting access to the calendar. If you grant access, candidate dates can be searched from the calendar.", a "Do not allow" button and an "OK" button are displayed in a pop-up form in the center of the screen.

[0498] In this case, when the "OK" button is operated, the control unit 21 refers to the user's schedule information registered by, for example but not limited to, a calendar function provided as a standard function of the OS of the terminal 20. Then, the control unit 21 selects a shopping payment history based on the event information included in the referred schedule information.

[0499] Instead of or in addition to the user's schedule information registered using the standard calendar function of the OS of terminal 20, the user's schedule information registered using the calendar function of a payment application or messaging application may be referenced, or it is not necessary to do so.

[0500] The user's schedule information registered by the calendar function may include, by way of example and not limitation, event information entered by the user of terminal 20 .

[0501] As one method, the control unit 21 identifies, from the user's schedule information, event information that multiple users are expected to participate in, such as a trip, a barbecue, or a drinking party. Then, from multiple shopping payment histories, it selects shopping payment histories that were paid on a date (for example, but not limited to, a date within the past week) close to the date and time associated with the identified event information (the date and time of the event).

[0502] As another method, the control unit 21 identifies, from the user's schedule information, event information in which multiple users are expected to participate, such as a trip, a barbecue, or a drinking party. Then, from multiple shopping payment histories, it selects shopping payment histories in which products related to the identified event information have been purchased. As a non-limiting example, if the event "barbecue" is identified, it selects shopping payment histories in which products related to the barbecue are included in the shopping payment details.

[0503] In this case, as an example rather than a limitation, the control unit 21 selects, as the shopping settlement history related to the manually selected shopping settlement history, the shopping settlement history that includes, as the shopping settlement content, products necessary for ignition such as charcoal, ignition agents, and work gloves, the shopping settlement history that includes, as the shopping settlement content, products necessary for cooking such as kitchen knives, knives, and cutting boards, the shopping settlement history that includes, as the shopping settlement content, products that are food ingredients such as meat (beef, pork, chicken, etc.), vegetables, seafood, and seasonings, and so on.

[0504] Alternatively, by combining these, the control unit 21 may or may not select the shopping settlement history that was settled on a date close to the holding date and time of the specified event information (for example, a date within the past one week, as an example rather than a limitation) and that includes, as the shopping settlement content, products related to the specified event information.

[0505] In addition to the above, as an example rather than a limitation, information regarding a message sent by the user of the terminal 20 using a messaging application or the like may or may not be included in the user information, and the control unit 21 of the terminal 20 may or may not select the shopping settlement history based on the information regarding this message.

[0506] FIG. 8-6 is a diagram showing an example of a shopping settlement history selection screen in this modified example, and shows an example of a screen displayed on the display unit 24 of the terminal 20 of user A.A. On this shopping settlement history selection screen, based on the operation of the shopping settlement history search icon, a "Search for payment candidates from chat history? Propose payment candidates from previous chat history." button and a "Not now" button are displayed in a pop-up format in the center of the screen, along with the text.

[0507] In this case, when the "Search" button is operated, as an example rather than a limitation, the message history of the chat room of the messaging application is referred to by the control unit 21. Then, based on the content of the referred message, the shopping settlement history is selected by the control unit 21.

[0508] As one method, the control unit 21, as an example rather than a limitation, searches for messages that propose a split payment or imply a split payment from among the past messages sent by the user of the terminal 20. As an example rather than a limitation, the control unit 21 searches for messages that request a split payment from the other party (messages such as "Shall we split the bill?" and "I would like to split the bill" as examples rather than limitations). Then, it is determined whether there is information in the messages obtained as the search result or in messages separate from that message that can be used to estimate the shopping settlement history subject to split payment. As an example rather than a limitation, if date or time information is included, the shopping settlement history that includes the shopping settlement date and time corresponding to that date or time can be selected as the proposed shopping settlement history.

[0509] Also, as another method, the control unit 21 identifies a group within the messaging application in which the group name includes a term that implies a split payment. As an example rather than a limitation, it identifies groups that include terms such as "split payment", "waria kan", "settlement", "seisan", "payment", "kessai", "remittance", "sokin" in the group name. Then, for the identified group, based on the content of the messages included in the group chat room, in the same manner as above, it is selected as the proposed shopping settlement history.

[0510] This modification example shows a configuration in which the user information includes the schedule information of the user of the terminal 20, and the shopping settlement history is selected based on the event information included in the schedule information. As an example of the effects obtained by such a configuration, the terminal can appropriately select the first settlement information in consideration of the events in which the user of the terminal participated, based on the event information included in the schedule information of the user of the terminal.

[0511] In addition, in this modified example, the user information includes information regarding a message transmitted from the user of the terminal 20, and the shopping settlement history is shown to be selected based on the information regarding this message. As an example of the effects obtained by such a configuration, the terminal can appropriately select the first settlement information based on the information regarding the message transmitted based on the user of the terminal.

[0512] In addition to the above, by way of example and not limitation, attribute information such as the gender, age, occupation, etc. of the user of the own terminal 20 may or may not be included in the user information, and the control unit 21 of the terminal 20 may select the shopping settlement history based on this attribute information.

[0513] Specifically, by way of example and not limitation, an event in which the participation of the user of the own terminal 20 is assumed is estimated based on at least one piece of information among the attribute information such as the gender, age, occupation, etc. of the user of the own terminal 20. Then, based on the estimation result, a shopping settlement history related to the estimated event is selected from among the shopping settlement histories of the user of the own terminal 20.

[0514] <Eighth Modified Example (3)> In the eighth embodiment, the control unit 21 of the terminal 20 executes the automatic selection process of the shopping settlement history, but it is not limited to this.

[0515] The data of the shopping settlement history of each user of the terminal 20 is stored and managed in the storage unit 15 of the server 10. For this reason, instead of the control unit 21 of the terminal 20, the control unit 11 of the server 10 may or may not execute the automatic selection process of the shopping settlement history. This is the same in the embodiments described below.

[0516] FIG. 8-7 is a flowchart showing an example of the flow of processing executed by each device in this modified example. This processing is the processing in which, for the processing part of FIG. 2-17 among the processes of FIGS. 2-17 to 2-19, as the processing of terminal A, the step of A150 is replaced with the step of A151, the step of A160 is replaced with the step of A163, and the step of A170 is deleted. Also, as the processing of server 10, the step of S150 is replaced with the step of S151, the step of S161 is added, and the step of S160 is replaced with the step of S163.

[0517] After A130, the control unit 21 of terminal A, by way of example and not limitation, transmits shopping settlement history selection request information for requesting selection of a shopping settlement history to server 10 via communication I / F 22 (A151).

[0518] When receiving the shopping settlement history selection request information from terminal A via communication I / F 14 (S151), the control unit 11 of server 10 executes an automatic shopping settlement history selection process (S161). As a method for selecting the shopping settlement history in this processing, a method similar to the selection method by the control unit 21 of terminal 20 described above can be applied.

[0519] Thereafter, the control unit 11 transmits automatic shopping settlement history selection information including the selection result of the shopping settlement history to terminal A via communication I / F 14 (S163).

[0520] If receiving the automatic shopping settlement history selection information from server 10 via communication I / F 22 (A163), the control unit 21 of terminal A, by way of example and not limitation, picks up and displays the shopping settlement history selected by server 10 as a candidate for splitting the bill and makes a suggestion (suggest) to the user of terminal 20. Then, the control unit 21 of terminal A moves the processing to A180.

[0521] The process of suggesting the shopping payment history selected by the server 10 to the user of the terminal 20 is not essential, and this process may be omitted.

[0522] According to this modification, the server 10 executes a process of selecting one shopping payment history from among multiple shopping payment histories related to payments made by users of the terminals 20, using the control unit 11. The server 10 transmits information on the excess or deficit amount (not limited to, a first amount) of at least one user of the terminal 20 based on the shopping payment history of the selected location to the one terminal 20, and transmits information on the excess or deficit amount (not limited to, a second amount) of at least another user of the terminal 20 to the other terminals 20 via the communication I / F 14. The server 10 then executes a split payment process (not limited to, an example of a remittance process or a receipt process to a terminal based on the first amount, and a remittance process or a receipt process to a different terminal based on the second amount) using the control unit 11. As an example of the effect obtained by such a configuration, the server executes a process of selecting first payment information from multiple payment information related to payments made by the user of the terminal, and based on the result, the server's control unit executes a process of sending or receiving money to the terminal based on the first amount, and a process of sending or receiving money to a different terminal based on the second amount.This makes it possible to send or receive an amount to or from a terminal and to send or receive money to a different terminal while reducing the processing load on the terminal, thereby improving user convenience.

[0523] <Ninth Example> The ninth embodiment is an embodiment in which, like the eighth embodiment, the terminal 20 automatically selects a shopping payment history to be split from among a plurality of shopping payment histories of the user of the terminal 20 itself. The ninth embodiment differs from the eighth embodiment in that the terminal 20 selects the shopping payment history based on information related to the shopping payment history of the user of the terminal 20 itself.

[0524] The contents described in the ninth embodiment can be applied to any of the other embodiments and other modified examples. Also, for components identical to the previously described components, the same reference numerals are used, and repeated descriptions are omitted.

[0525] In this embodiment, the control unit 21 of the terminal 20 automatically selects a shopping settlement history based on information related to the shopping settlement history. The information related to this shopping settlement history includes, by way of example and not limitation, information related to time such as the date, time, date and time of a shopping settlement history different from the shopping settlement history (hereinafter referred to as the "manually selected shopping settlement history") manually selected by the user of the terminal 20.

[0526] Specifically, the control unit 21, by way of example and not limitation, identifies a shopping settlement history with the same date as the manually selected shopping settlement history. Then, the identified shopping settlement history is selected as the proposed shopping settlement history. This is because it is considered that a shopping settlement history with the same date as the manually selected shopping settlement history is also likely to be a target for splitting the bill, similar to the manually selected shopping settlement history.

[0527] <Example display screen> FIG. 9-1 is a diagram showing an example of a shopping settlement history selection screen in this embodiment, and shows an example of a screen displayed on the display unit 24 of the terminal 20 of user A.A. On this shopping settlement history selection screen, among a plurality of shopping settlement histories such as "AA Rent-a-Bicycle", "BB Supermarket", and "CC Bento", in accordance with the operation of user A.A., a state where the check for the shopping settlement history of "BB Supermarket" is "ON" is shown.

[0528] FIG. 9-2 is a diagram showing an example of a screen displayed based on the operation of the search icon on the shopping settlement history selection screen of FIG. 9-1. On this shopping settlement history selection screen, "AA Rent-a-Bicycle", which is a shopping settlement history settled on the same date as the shopping settlement history of "BB Supermarket" whose check was "ON" in FIG. 9-1, is displayed in a different manner from other shopping settlement histories.

[0529] Note that, different from the above and by way of example rather than limitation, the control unit 21 may or may not select a shopping settlement history whose manual selection shopping settlement history and the day of settlement are the same. Also, by way of example rather than limitation, the control unit 21 may or may not select a shopping settlement history whose manual selection shopping settlement history and the time or time zone of settlement are the same.

[0530] <Effect of the Ninth Embodiment> The ninth embodiment shows a configuration in which the terminal 20 selects a shopping settlement history to be subject to the split payment based on information related to the shopping settlement history. As an example of the effect obtained by such a configuration, the terminal can appropriately select the first settlement information based on information related to the settlement information.

[0531] Also, the ninth embodiment shows a configuration in which the information related to the shopping settlement history includes information on the date or time of a shopping settlement history different from the manually selected shopping settlement history. As an example of the effect obtained by such a configuration, the terminal can appropriately select the first settlement information based on information on the date or time of the second settlement information different from the first settlement information.

[0532] <Ninth Modification Example (1)> In the ninth embodiment, the control unit 21 of the terminal 20 may or may not select a shopping settlement history based on product information or service information included in a shopping settlement history different from the manually selected shopping settlement history.

[0533] Specifically, the control unit 21 identifies, by way of example and not limitation, the purchased product or provided service based on the payment details of the manually selected shopping payment history. Then, based on the details of the identified product or service, the control unit 21 estimates an event related to the shopping payment corresponding to the manually selected shopping payment history (the event that made it necessary to make the shopping payment). Then, the control unit 21 selects a shopping payment history based on the estimated event and the payment details of other shopping payment histories.

[0534] For example, and not by way of limitation, if the shopping payment details of the manually selected shopping payment history include equipment products such as a grill stove, griddle, plate, grate, tongs, etc., the control unit 21 estimates that the event that required the payment is a "barbecue" based on the details of these products. Then, based on the estimation result, for example, and not by way of limitation, selects shopping payment history that includes barbecue-related products in the shopping payment details from shopping payment histories with payment dates close to those of the manually selected shopping payment history.

[0535] In this case, the control unit 21 selects, as shopping payment history related to the manually selected shopping payment history, shopping payment history including, but not limited to, shopping payment history including items necessary for fire starting such as charcoal, fire starter, and work gloves, shopping payment history including items necessary for cooking such as knives, cutting boards, and shopping payment history including food items such as meat (beef, pork, chicken, etc.), vegetables, seafood, and seasonings.

[0536] In addition, in the ninth embodiment, the control unit 21 of the terminal 20 may or may not select a shopping payment history based on store information included in a shopping payment history that is different from the manually selected shopping payment history.

[0537] Specifically, as an example (not by way of limitation), based on the store name included in the manually selected shopping payment history, the control unit 21 estimates an event related to the shopping payment history corresponding to the manually selected shopping payment history (the event that gave rise to the need to make the shopping payment). Then, based on the estimated event and the store names included in other shopping payment histories, the control unit 21 selects a shopping payment history.

[0538] As an example (not by way of limitation), when the store name included in the manually selected shopping payment history is the name of a store located at a tourist destination (as an example, not by way of limitation, the store name of a "souvenir shop"), the control unit 21 estimates the event that gave rise to the need to make the payment as "travel" based on the store name. Then, based on the estimation result, as an example (not by way of limitation), among the shopping payment histories with a payment date close to that of the manually selected shopping payment history, the control unit 21 selects a shopping payment history that includes the store name of a store that handles goods and services related to travel.

[0539] This modified example shows a configuration in which the terminal 20 selects a shopping payment history to be split based on product information included in a shopping payment history different from the manually selected shopping payment history. As an example of the effect obtained by such a configuration, the terminal can appropriately select the first payment information based on product information included in the second payment information different from the first payment information.

[0540] Further, this modified example shows a configuration in which the terminal 20 selects a shopping payment history to be split based on store information included in a shopping payment history different from the manually selected shopping payment history. As an example of the effect obtained by such a configuration, the terminal can appropriately select the first payment information based on store information included in the second payment information different from the first payment information.

[0541] <Modified Example 9 (2)> In the ninth embodiment, instead of having the control unit 21 of the terminal 20 execute the automatic selection process for shopping settlement history as in the eighth modification (3), the control unit 11 of the server 10 may execute the automatic selection process for shopping settlement history, or may not do so.

[0542] <Tenth Embodiment> The tenth embodiment is an embodiment in which, similar to the eighth and ninth embodiments, the terminal 20 automatically selects a shopping settlement history to be subject to splitting from among a plurality of shopping settlement histories by the user of its own terminal 20. Unlike the eighth and ninth embodiments, in the tenth embodiment, the terminal 20 selects a shopping settlement history based on information of a user of a terminal 20 different from its own terminal 20.

[0543] The content described in the tenth embodiment is applicable to any of the other embodiments and any of the other modifications. Also, for components identical to the previously described components, the same reference numerals are assigned and repeated description is omitted.

[0544] In this embodiment, the control unit 21 of the terminal 20 selects a shopping settlement history based on information of a user (information of other splitting members) selected as a splitting member by the user of its own terminal 20.

[0545] In this case, the information of other splitting members may include, by way of example and not limitation, information of shopping settlement histories settled by users of other splitting members. In this embodiment, a case is exemplified in which the control unit 21 selects the shopping settlement history of its own terminal 20 based on information of shopping settlement histories settled by other splitting members.

[0546] FIG. 10 is a flowchart showing an example of the flow of processing executed by each device in this embodiment. This process is the one where, in the process of FIG. 8-4, the step of A150 in the process of terminal A is replaced with the step of A153, the step of A160 is replaced with the step of A165, the step of S150 in the process of server 10 is replaced with the step of S153, and the step of S160 is replaced with the step of S165.

[0547] After A140, the control unit 21 of terminal A transmits the second shopping settlement history request information to server 10 via communication I / F 22 (A153). Specifically, by way of example and not limitation, it executes a process of requesting from server 10 the shopping settlement history of the user of its own terminal 20 and the shopping settlement history of the split payment members selected at A130.

[0548] When receiving the second shopping settlement history request information from terminal A via communication I / F 14 (S153), the control unit 11 of server 10 reads from the user management database 155 the shopping settlement history of the user of the terminal 20 that is the source of the received shopping settlement history request information and the shopping settlement history of the split payment members selected by terminal A, and transmits it to terminal A via communication I / F 14 as the second shopping settlement history (S165).

[0549] When receiving the second shopping settlement history from server 10 via communication I / F 22 (A165), the control unit 21 of terminal A moves the process to A175.

[0550] In this case, in the shopping settlement history automatic selection process of A175, the control unit 21 of terminal A refers to the shopping settlement date and time of the shopping settlement history of the user of its own terminal 20 and the shopping settlement date and time of the shopping settlement history of the selected split payment members, and by way of example and not limitation, selects the shopping settlement history carried out in the same period. This is because when shopping settlements are carried out in the same period, there is a possibility that the user of its own terminal 20 and the selected split payment members have acted together.

[0551] Note that, not limited to this, the shopping settlement history of the user of the own terminal 20 and the shopping settlement history of the selected split payment member may be selected, not limited to but by way of example, the shopping settlement history including the same type of goods or services, or goods or services related to each other in the shopping settlement content.

[0552] The tenth embodiment shows a configuration in which the terminal 20 selects the shopping settlement history to be subject to split payment based on the information of the user of the terminal 20 different from the user of the own terminal 20. As an example of the effect obtained by such a configuration, the terminal can appropriately select the first settlement information based on the information of the users of different terminals.

[0553] Further, the tenth embodiment shows a configuration in which the terminal 20 selects the shopping settlement history to be subject to split payment based on the shopping settlement history (not limited to, an example of the third settlement information) by the user of the terminal 20 different from the user of the own terminal 20. As an example of the effect obtained by such a configuration, the terminal can appropriately select the first settlement information based on the third settlement information regarding the settlement by the users of different terminals.

[0554] <Tenth Modification Example (1)> In the tenth embodiment, the control unit 21 of the terminal 20 may or may not select the shopping settlement history to be subject to split payment based on the information input by the user of the own terminal 20 associated with each of the plurality of shopping settlement histories by the user of the own terminal 20.

[0555] Specifically, for each of the plurality of shopping settlement histories, the control unit 21 of the terminal 20 sets a memo or a tag according to the operation on the input / output unit 23. The memo is for the user to be able to confirm later what kind of shopping settlement history it is. Not limited to but by way of example, the use of the goods purchased by the settlement can be input and set as the memo.

[0556] Also, the tags are for classifying shopping settlement histories by type and purpose (labels or tags for classifying information). As tags, without limitation, by way of example, a plurality of types such as "shopping", "work", "date", "travel", "gift", "other", etc. can be prepared, and the user of the terminal 20 can select and set tags corresponding to the type and purpose for each shopping settlement history.

[0557] In this case, the control unit 21 refers to the content of the memo associated with each of the plurality of shopping settlement histories, and identifies and selects the shopping settlement history associated with a memo that directly indicates or suggests the content related to an event where a split payment may occur.

[0558] Also, the control unit 21, without limitation, by way of example, refers to the tags associated with each of the plurality of shopping settlement histories, and identifies and selects the shopping settlement history associated with tags related to an event where a split payment may occur, such as tags for shopping, travel, etc. without limitation. Note that the memo and tags will be described in more detail in the embodiments described later.

[0559] <10th Modification Example (2)> Regarding the information of the users of other split payment members, without limitation, by way of example, similar to the user information of the user of the terminal 20, it can include attribute information such as the gender, age, occupation, etc. of the users of other split payment members. And based on the attribute information of these split payment members, the shopping settlement history may or may not be automatically selected.

[0560] Specifically, without limitation, by way of example, based on at least one piece of information among the attribute information such as the gender, age, occupation, etc. of other split payment members, an event in which the participation of other split payment members is assumed is estimated. And based on the estimation result, from the shopping settlement histories of the user of the own terminal 20, the shopping settlement history related to the estimated event is selected.

[0561] <Tenth Modification (3)> In the tenth embodiment, as in the eighth variant example (3), instead of the control unit 21 of the terminal 20 executing the shopping payment history automatic selection process, the control unit 11 of the server 10 may or may not execute the shopping payment history automatic selection process.

[0562] In this case, the control unit 11 of the server 10, by way of example and not limitation, references the location information of the terminal 20 and the location information of the terminal 20 of a user selected as a split-bill member by the user of this terminal 20. Then, it can search for shopping payment histories in which payments were made between the user of terminal 20 and the other split-bill members in locations close to each other, and select the shopping payment history obtained as a result of the search.

[0563] <Eleventh Example> The eleventh embodiment is an embodiment in which a terminal 20 automatically selects a member other than its own terminal 20 to split the bill with. Depending on the user of the terminal 20, it may be troublesome for them to search for and select split-the-bill members by themselves, especially when there are a large number of users who wish to split the bill. The eleventh embodiment differs from the eighth to tenth embodiments in that the target selected by the terminal 20 is not the shopping payment history but the members who will split the bill.

[0564] The contents described in the eleventh embodiment can be applied to any of the other embodiments and other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0565] In this embodiment, the control unit 21 of the terminal 20, by way of example and not limitation, performs notification between the terminals 20 (so-called peer-to-peer communication) without going through the server 10, and searches for terminals 20 located near the own terminal 20. Then, the control unit 21 selects the users of the terminals 20 obtained as search results as bill splitting member candidates.

[0566] <Display screen example> FIG. 11-1 is a diagram showing an example of a split-the-bill member selection screen in this embodiment, and shows an example of a screen displayed on the display unit 24 of the terminal 20 of user AA. On this bill splitting member selection screen, no bill splitting members have been selected yet, and there are currently no bill splitting members. At the bottom of the screen are two search icons: a first icon labeled "Search by phone number" for searching for split-bill members by phone number, and a second icon labeled "Search for people nearby" for searching for split-bill members by location, but not by way of limitation.

[0567] FIG. 11-2 is a diagram showing an example of a screen displayed when the second search icon is operated on the bill splitting member selection screen of FIG. 11-1. Based on the display of the second search icon, for example and not limitation, the user's own terminal 20 attempts to communicate (peer-to-peer communication) with a nearby terminal 20, and based on information acquired from the terminal 20 with which communication was successful, the user of that terminal 20 is suggested as a potential split-the-bill member. In this example, four people (users) nearby, user BB, user BC, user DD, and user EE, are obtained as search results, and are displayed in color, for example and not limitation.

[0568] Furthermore, each user obtained as a search result has a check box associated with their icon image and user name. The user of their own terminal 20 can remove that user from the split-bill members by checking the check box "OFF." In this example, the check box associated with user BC is checked "OFF," indicating that user BC has been removed from the split-bill members.

[0569] <Effects of the 11th embodiment> In the 11th embodiment, split - bill member candidates other than the split - bill master (not limited, an example of users of different terminals) are selected based on the location information of the terminal 20 of the split - bill master and the location information of different terminals 20. As an example of the effect obtained by such a configuration, users of different terminals can be easily selected based on the location information of the terminals and the location information of different terminals.

[0570] <11th Variation (1)> In the 11th embodiment, the server 10 may or may not execute the search for users to be split - bill members instead of the terminal 20.

[0571] Specifically, not limited but by way of example, when the control unit 21 of the terminal 20 detects that a search operation for split - bill members has been performed in the terminal 20, the control unit 21 transmits a user search request to the server 10 via the communication I / F 22.

[0572] Upon receiving the user search request from the terminal 20, the control unit 11 of the server 10, not limited but by way of example, based on the latest calculated terminal position of the terminal 20 that is the source of the user search request and the latest calculated terminal positions of each terminal 20 stored and managed in the database, searches for terminals 20 whose distance from the latest calculated terminal position of the terminal 20 that is the source of the user search request is within (or less than) a set distance. The set distance can be, not limited but by way of example, a distance of about "10 meters". Then, the users of the terminals 20 obtained as search results are proposed (suggested) as split - bill member candidates.

[0573] In this case, if an attempt is made to search for split - bill member candidates for all terminals 20 using the payment application, there is a problem that the processing load on the server 10 increases. Therefore, the server 10 can also set a search range and search for split - bill member candidates.

[0574] In this case, if the user of the terminal 20 has registered a messaging application, the server 10 communicates with the messaging server 40 to obtain information on the users registered as friends by the user of the terminal 20 that is the source of the user search request. Then, based on the obtained user information, the users registered as friends by the user of the terminal 20 that is the source of the user search request are set as the search targets, and as described above, users to be candidate members for the split expense are searched based on the location information of the terminal 20.

[0575] <11th Modification Example (2)> In the 11th Modification Example (1), the server 10 may or may not search for users to be candidate members for the split expense based on, as an example and not by limitation, the date information input by the user of the terminal 20, the location information of its own terminal 20 on the input date, and the location information of different terminals 20 on the input date.

[0576] Specifically, as an example and not by limitation, when searching for split expense members, the control unit 21 of the terminal 20 prompts the user to input a date. Then, the control unit 21 transmits a user search request including the input date information to the server 10 via the communication I / F 22.

[0577] Upon receiving a user search request from the terminal 20, the control unit 11 of the server 10 searches for candidate members for the split expense based on, as an example and not by limitation, the history of the calculated terminal positions of the terminal 20 on that date, which is the source of the user search request, based on the date included in the received user search request, and the history of the calculated terminal positions of each terminal 20 on that date stored and managed in the database. Specifically, as an example and not by limitation, among different terminals 20, the users of the terminals 20 located near the terminal 20 that is the source of the user search request during the same time period on that date are selected as the users to be candidate members for the split expense.

[0578] In this modification example, the split payment member candidates other than the split payment master (not limited, but an example of a user of a different terminal) are selected based on the location information of the terminal 20 of the split payment master on the input date and the location information of a terminal 20 different from the terminal 20 of the split payment master on the input date. As an example of the effect obtained by such a configuration, considering the information of the date input by the user of the terminal, users of different terminals can be easily selected based on the location information of the terminal and the location information of different terminals.

[0579] <11th Modification Example (3)> In the 11th embodiment, the control unit 21 of the terminal 20 may or may not select split payment member candidates based on the call history between the user of its own terminal 20 and the users of different terminals 20.

[0580] Specifically, the control unit 21 refers to, not limited but by way of example, the information of the call history with the users of other terminals 20 called by the call function (telephone function) of its own terminal 20. Then, the control unit 21, not limited but by way of example, identifies the users of the terminals 20 who called the user of its own terminal 20 on the same date or in the same time period as the shopping settlement date and time of the manually selected shopping settlement history, and selects them as split payment member candidates.

[0581] This modification example shows a configuration in which the split payment member candidates are selected based on the call history with the user of its own terminal 20. As an example of the effect obtained by such a configuration, users of different terminals can be appropriately selected based on the call history with the user of the terminal.

[0582] <11th Modification Example (4)> In the 11th embodiment, the control unit 21 of the terminal 20 may or may not select split payment member candidates based on the content (including messages and image information) transmitted and received using the messaging application.

[0583] By way of example and not limitation, the content sent and received using the messaging application of the user's own terminal 20 is referenced, and by way of example and not limitation, users who sent and received content on the same date or in the same time period as the shopping payment date and time in the manually selected shopping payment history are identified and selected as potential split-the-bill members.

[0584] Furthermore, image recognition processing is performed on captured images captured by the camera 27 of the terminal 20 and live view images displayed on the screen by a so-called live view function. Users recognized by the image recognition processing may or may not be selected as split-the-bill member candidates.

[0585] <Twelfth Example> The twelfth embodiment is an embodiment in which at least one user included in the split-bill members splits the bill in cash, rather than electronic money. Some users may not wish to transfer money by electronic money, but may wish to pay in cash. The twelfth embodiment differs from the above embodiments in that a process for realizing splitting the bill in cash has been added.

[0586] The contents described in the twelfth embodiment can be applied to any of the other embodiments and other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0587] In this embodiment, when selecting a bill splitting member, the control unit 21 of the terminal 20 selects a bill splitting type (either electronic money splitting or cash splitting) in association with the bill splitting member in accordance with a user operation. Then, shopping payment history selection information including the selected shopping payment history, the selected bill splitting member, and the selected bill splitting type is sent to the server 10 via the communication I / F 22.

[0588] When the communication I / F 14 receives shopping payment history selection information from the terminal 20, the control unit 11 of the server 10 calculates the excess or shortage amount for each splitting member based on the received shopping payment history selection information, the splitting type associated with the splitting member, and the selected shopping payment history.

[0589] <Display screen example> 12-1 is a diagram showing an example of a bill-splitting member selection screen in this embodiment, showing an example of a messaging application screen displayed on the display unit 24 of user AA's terminal 20. This example illustrates a case where a travel circle group consisting of five users, user AA, user BB, user CC, user DD, and user EE, is splitting the bill, and is formed in the messaging application.

[0590] On this bill-splitting member selection screen, in addition to check boxes associated with the icon image and username of each user who is a bill-splitting member candidate, a circular bill-splitting type selection button similar to a radio button is provided for setting the bill-splitting type to "cash." The bill-splitting type selection button is configured so that it can be switched "ON / OFF" for each bill-splitting member candidate.

[0591] As a non-limiting example, in the initial state, the split bill type selection button is in the "OFF" state (the split bill type is "electronic money"), and when the split bill type selection button is touched, a black circle is added inside the circle of the split bill type selection button, changing it to the "ON" state and the split bill type to "cash." In this example, the split bill type selection button associated with user CC, one of the split bill member candidates, is shown checked "ON."

[0592] Figure 12-2 shows an example of a split-bill request notification screen that is displayed based on the operation of the registration icon on the split-bill member selection screen of Figure 12-1, and shows an example of a screen that is displayed on the display unit 24 of the terminal 20 of user CC, who is one of the split-bill members. This split bill request notification screen is a group chat room screen for the travel circle group, and displays a split bill request message sent by user AA, who is the split bill master.

[0593] The split payment request message displays the amount of the surplus or shortfall for user CC (in this example, "900 yen"), as well as "cash payment" indicating the type of split payment for user CC.

[0594] In addition, in the split payment details display field below, for users BB, DD, and EE, "Electronic Money" was selected as the split payment type, so "Payment of 900 yen" is displayed in the Over / Shortfall Amount field. In contrast, for user CC, "Cash" was selected as the split payment type, so "Payment of 900 yen" is displayed in the over / shortfall Amount field, along with the amount to be paid in cash ("900 y...

Claims

1. A program for causing a terminal that executes processing related to settlement to execute, based on an input to the terminal by a user of the terminal, transmitting, by a communication unit of the terminal, first settlement information based on processing related to a first settlement by the user of the terminal; receiving, by the communication unit, information on at least the first amount among a first amount that a user of the terminal remits or receives as a result of settlement of a settlement amount and a second amount that a user of a terminal different from the terminal remits or receives as a result of settlement of the settlement amount, based on the first settlement information; executing, by a control unit of the terminal, a first remittance process or a first receipt process based on the first amount; after the first remittance process or the first receipt process based on the first amount is executed, if the first settlement information is corrected to second settlement information, causing the terminal to execute, by the control unit, a second remittance process or a second receipt process based on the second settlement information.

2. The program according to claim 1, wherein the second remittance process or the second receipt process is executed based on a difference between the second settlement information and the first settlement information.

3. The program according to claim 1 or claim 2, wherein the second remittance process or the second receipt process is executed based on permission from a user of the different terminal.

4. The program according to claim 3, wherein the second remittance process or the second receipt process is executed without the permission of the different terminal when the settlement amount of the second settlement information is reduced compared to the first settlement information.

5. The program according to claim 1 or claim 2, receiving, by the communication unit, information on at least the third amount among a third amount that a user of the terminal remits or receives and respective amounts that users of each of a plurality of terminals including a user of a terminal different from the terminal remit or receive, based on the first settlement information; executing, by the control unit, a third remittance process or a third receipt process based on the third amount; when the first settlement information is corrected to the second settlement information, causing the terminal to execute, by the control unit, a fourth remittance process or a fourth receipt process based on the second settlement information, The fourth remittance process or the fourth receipt process is executed based on the permission of each user of the plurality of terminals.

6. The program according to claim 5, wherein the fourth remittance process or the fourth receipt process is executed based on the permission of a user among the users of the plurality of terminals who incurs a loss due to the correction from the first settlement information to the second settlement information.

7. The program according to any one of claims 1 to 6, wherein at least information on the fifth amount that the user of the terminal remits or receives, based on the first settlement information and third settlement information based on processing related to second settlement by a user of a different terminal, and the sixth amount that the user of a terminal different from the terminal remits or receives, is received by the communication unit; the control unit executes a fifth remittance process or a fifth receipt process based on the fifth amount; and the terminal is caused to transmit, by the communication unit, information regarding correction from the third settlement information to the fourth settlement information.

8. The program according to claim 7, wherein when the third settlement information is corrected to the fourth settlement information, the terminal is caused to execute, by the control unit, a sixth remittance process or a sixth receipt process based on the fourth settlement information.

9. The program according to claim 1, wherein the second settlement information is requested to be corrected by a user of a different terminal.

10. The program according to any one of claims 1 to 9, wherein the terminal is caused to display, in a display area of the terminal, a notification regarding completion of the first remittance process or the first receipt process.

11. The program according to claim 10, wherein the terminal is caused to execute, by the control unit, processing regarding correction from the first settlement information to the second settlement information based on an input of the user of the terminal with respect to the notification regarding completion of the first remittance process or the first receipt process.

12. The program according to claim 10 or claim 11, wherein the notification regarding completion of the first remittance process or the first receipt process includes the user of the terminal and the user of a different terminal, and is displayed in a chat room including content transmitted from the terminal to the different terminal and content transmitted from the different terminal to the terminal.

13. A program according to any one of Claims 1 to 9, including a user of the terminal and a user of the different terminal, and displaying, in a display area of the terminal, a chat room including content transmitted from the terminal to the different terminal and content transmitted from the different terminal to the terminal; and causing the terminal to display a request for correction of the second payment information in the chat room.

14. A program according to Claim 13, wherein the request for correction of the second payment information is transmitted from the different terminal, and the second remittance process or the second receipt process is executed based on an input by the user of the terminal in response to the request for correction.

15. A program according to any one of Claims 1 to 14, wherein the first remittance process or the first receipt process is executed based on at least permission of the user of the terminal and permission of the user of the different terminal.

16. An information processing method for a terminal that executes a process related to payment, wherein, based on an input to the terminal by the user of the terminal, a communication unit of the terminal transmits first payment information based on a process related to a first payment by the user of the terminal, and the communication unit receives at least information on the first amount that the user of the terminal remits or receives and the second amount that a user of a terminal different from the terminal remits or receives by settlement of the settlement amount, based on the first payment information, a control unit of the terminal executes a first remittance process or a first receipt process based on the first amount, and when the first payment information is corrected to second payment information after the first remittance process or the first receipt process based on the first amount is executed, the control unit executes a second remittance process or a second receipt process based on the second payment information.

17. A terminal that executes a process related to payment, wherein, based on an input to the terminal by the user of the terminal, a communication unit transmits first payment information based on a process related to a first payment by the user of the terminal, and receives at least information on the first amount that the user of the terminal remits or receives and the second amount that a user of a terminal different from the terminal remits or receives by settlement of the settlement amount, based on the first payment information; A control unit that executes a first remittance process or a first receipt process based on the first amount, after the first remittance process or the first receipt process based on the first amount is executed, when the first settlement information is corrected to second settlement information, the control unit executes a second remittance process or a second receipt process based on the second settlement information.

18. A terminal that executes a process related to settlement, comprising a processor that reads a program stored in a memory and executes a process based on the program, wherein the processor transmits, by a communication unit of the terminal, first settlement information based on a process related to a first settlement by the user of the terminal based on an input to the terminal by the user of the terminal; receives, by the communication unit, information on at least the first amount among a first amount that the user of the terminal remits or receives by settlement of a settlement amount and a second amount that the user of a terminal different from the terminal remits or receives by settlement of the settlement amount, based on the first settlement information; executes a first remittance process or a first receipt process based on the first amount; after the first remittance process or the first receipt process based on the first amount is executed, when the first settlement information is corrected to second settlement information, executes a second remittance process or a second receipt process based on the second settlement information.

19. A program for causing a server that communicates with a terminal that executes a process related to settlement to execute, receiving, by a communication unit of the server, from the terminal, first settlement information based on a process related to a first settlement by the user of the terminal based on an input to the terminal by the user of the terminal; transmitting, by the communication unit, information on at least the first amount among a first amount that the user of the terminal remits or receives by settlement of a settlement amount and a second amount that the user of a terminal different from the terminal remits or receives by settlement of the settlement amount, based on the first settlement information, to the terminal, and transmitting information on at least the second amount to the different terminal by the communication unit; executing, by a control unit of the server, a first remittance process or a first receipt process for the terminal based on the first amount and a second remittance process or a second receipt process for the different terminal based on the second amount. After the first remittance process or the first receipt process for the terminal and the second remittance process or the second receipt process for the different terminal are executed, the communication unit receives information regarding correction from the first settlement information to the second settlement information. When the second settlement information is corrected, the server is made to execute, by the control unit, a third remittance process or a third receipt process for the terminal and a fourth remittance process or a fourth receipt process for the different terminal based on the second settlement information.

Images