Program, information processing method, and terminal

Abstract

To perform more appropriate processing related to remittance or remittance requests.SOLUTION: A program executed by a terminal causes the terminal to make, on at least a display unit of the terminal, a first display based on first information about a remittance request from a first user to a user of the terminal or a remittance request from the user of the terminal to the first user and a second display based on second information about a remittance request from a second user to the user of the terminal or a remittance request from the user of the terminal to the second user, and perform, by a control unit of the terminal, first processing based on the first information and the second information based on an input to the terminal on which the first display and the second display are made.SELECTED DRAWING: Figure 1-1

Description

[Technical field]

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

[0002] Recently, services that use applications executable on terminals such as smartphones to manage the terminal or the terminal user's electronic currency (electronic money) and to send / receive money are becoming widespread. For example, Patent Document 1 discloses a technology for settling the purchase amount of a product. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2002-176671 A Summary of the Invention

[0004] According to a first aspect of the present invention, a program executed by the terminal displays, on at least a display unit of the terminal, a first display based on first information relating to a remittance request from a first user to a user of the terminal, or from the user of the terminal to the first user, and a second display based on second information relating to a remittance request from a second user to the user of the terminal, or from the user of the terminal to the second user, and performs a first process based on the first information and the second information by a control unit of the terminal based on an input to the terminal on which the first display and the second display are displayed. According to a second aspect of the present invention, an information processing method for a terminal includes displaying, on at least a display unit of the terminal, a first display based on first information relating to a remittance request from a first user to a user of the terminal, or a remittance request from the user of the terminal to the first user, and a second display based on second information relating to a remittance request from a second user to a user of the terminal, or a remittance request from the user of the terminal to the second user, and performing a first process based on the first information and the second information by a control unit of the terminal based on an input to the terminal on which the first display and the second display are displayed. According to a third aspect of the present invention, the terminal comprises a display unit that displays at least a first display based on first information relating to a remittance request from a first user to a user of the terminal, or a remittance request from the user of the terminal to the first user, and a second display based on second information relating to a remittance request from a second user to the user of the terminal, or a remittance request from the user of the terminal to the second user, and a control unit that performs a first processing based on the first information and the second information based on an input to the terminal on which the first display and the second display are displayed. According to a fourth aspect of the present invention, the terminal includes a processor that reads a program stored in a memory and performs processing based on the program, and the processor executes the following operations: displaying, on at least a display unit of the terminal, a first display based on first information relating to a remittance request from a first user to a user of the terminal, or from the user of the terminal to the first user, and a second display based on second information relating to a remittance request from a second user to the user of the terminal, or from the user of the terminal to the second user; and performing a first process based on the first information and the second information based on an input to the terminal on which the first display and the second display are displayed. [Brief description of the drawings]

[0005] [Figure 1-1] FIG. 1 illustrates an example of a configuration of a communication system according to an embodiment. [Figure 1-2] FIG. 2 is a diagram showing an example of functions realized by a control unit of the server according to the first embodiment. [Figure 1-3] FIG. 4 is a diagram showing an example of information stored in a storage unit of the server according to the first embodiment. [Figure 1-4] FIG. 4 is a diagram showing an example of user registration data according to the first embodiment. [Figure 1-5] FIG. 2 is a diagram showing an example of a user management database according to the first embodiment. [Figure 1-6] FIG. 2 is a diagram showing an example of remittance request management data according to the first embodiment. [Figure 1-7] FIG. 2 is a diagram showing an example of functions realized by a control unit of the terminal according to the first embodiment. [Figure 1-8]FIG. 4 is a diagram showing an example of information stored in a storage unit of the terminal according to the first embodiment. [Figure 1-9] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 1-10] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 1-11] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 1-12] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 1-13] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 1-14] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 1-15] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 1-16] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 1-17] FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. [Figure 1-18] 5 is a flowchart showing an example of the processing flow of the terminal and the server according to the first embodiment. [Figure 1-19] 6 is a flowchart showing an example of the flow of a settlement process according to the first embodiment. [Figure 1-20] FIG. 11 is a diagram showing an example of a table for explaining lump-sum settlement according to the first embodiment. [Figure 1-21] 5 is a flowchart showing an example of the processing flow of the terminal and the server according to the first embodiment. [Figure 1-22] 6 is a flowchart showing an example of the flow of a settlement process according to the first embodiment. [Figure 1-23] FIG. 13 is a diagram showing an example of a display screen of a terminal according to a first modified example. [Figure 1-24] FIG. 13 is a diagram showing an example of a display screen of a terminal according to a first modified example. [Figure 2-1] FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second embodiment. [Figure 2-2] FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second embodiment. [Figure 2-3]FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second embodiment. [Figure 2-4] 10 is a flowchart showing an example of the flow of processing by a terminal and a server according to the second embodiment. [Figure 2-5] 10 is a flowchart showing an example of the flow of processing by a terminal and a server according to the second embodiment. [Figure 3-1] FIG. 13 is a diagram showing an example of a display screen of a terminal according to a third embodiment. [Figure 3-2] FIG. 13 is a diagram showing an example of a display screen of a terminal according to a third embodiment. [Figure 4-1] FIG. 13 is a diagram showing an example of a display screen of a terminal according to the fourth embodiment. [Figure 4-2] FIG. 13 is a diagram showing an example of a display screen of a terminal according to the fourth embodiment. [Figure 5-1] FIG. 13 is a diagram showing an example of a display screen of a terminal according to the fifth embodiment. [Figure 5-2] 13 is a flowchart showing an example of the processing flow of a terminal and a server according to the fifth embodiment. [Figure 6-1] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the sixth embodiment. [Figure 6-2] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the sixth embodiment. [Figure 6-3] 23 is a flowchart showing an example of the flow of a batch remittance request creation process according to the sixth embodiment. [Figure 7-1] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the seventh embodiment. [Figure 7-2] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the seventh embodiment. [Figure 7-3] 23 is a flowchart showing an example of the flow of a settlement process according to the seventh embodiment. [Figure 7-4] 23 is a flowchart showing an example of the flow of a settlement process according to the seventh embodiment. [Figure 8-1] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the eighth embodiment. [Figure 8-2] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the eighth embodiment. [Figure 8-3] 23 is a flowchart showing an example of the processing flow of a terminal and a server according to the eighth embodiment. [Figure 8-4]13 is a flowchart showing an example of the processing flow of a terminal and a server according to an eighth modified example. [Figure 9-1] FIG. 13 is a diagram showing an example of a table for explaining a processing method according to the ninth embodiment. [Figure 9-2] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the ninth embodiment. [Figure 9-3] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the ninth embodiment. [Figure 9-4] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the ninth embodiment. [Figure 9-5] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the ninth embodiment. [Figure 9-6] 23 is a flowchart showing an example of the processing flow of a terminal and a server according to the ninth embodiment. [Figure 10-1] FIG. 23 is a diagram showing an example of a display screen of a terminal according to a tenth embodiment. [Figure 10-2] FIG. 23 is a diagram showing an example of a display screen of a terminal according to a tenth embodiment. [Figure 10-3] FIG. 23 is a diagram showing an example of a display screen of a terminal according to a tenth embodiment. [Figure 10-4] FIG. 23 is a diagram showing an example of a display screen of a terminal according to a tenth embodiment. [Figure 10-5] FIG. 23 is a diagram showing an example of a display screen of a terminal according to a tenth embodiment. [Figure 10-6] 23 is a flowchart showing an example of the processing flow of a terminal and a server according to a tenth embodiment. [Figure 11-1] FIG. 23 is a diagram showing an example of a display screen of a terminal according to an eleventh embodiment. [Figure 11-2] FIG. 23 is a diagram showing an example of a display screen of a terminal according to an eleventh embodiment. [Figure 11-3] FIG. 23 is a diagram showing an example of a display screen of a terminal according to an eleventh embodiment. [Figure 11-4] FIG. 23 is a diagram showing an example of a display screen of a terminal according to an eleventh embodiment. [Figure 11-5] FIG. 23 is a diagram showing an example of a display screen of a terminal according to an eleventh embodiment. [Figure 11-6] 23 is a flowchart showing an example of the processing flow of a terminal and a server according to an eleventh embodiment. [Figure 12-1]FIG. 23 is a diagram showing an example of a display screen of a terminal according to a twelfth embodiment. [Figure 12-2] FIG. 23 is a diagram showing an example of a display screen of a terminal according to a twelfth embodiment. [Figure 12-3] FIG. 23 is a diagram showing an example of a display screen of a terminal according to a twelfth embodiment. [Figure 12-4] FIG. 23 is a diagram showing an example of a display screen of a terminal according to a twelfth embodiment. [Figure 13-1] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the thirteenth embodiment. [Figure 13-2] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the thirteenth embodiment. [Figure 13-3] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the thirteenth embodiment. [Figure 14-1] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the sixteenth embodiment. [Figure 14-2] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the sixteenth embodiment. [Figure 14-3] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the sixteenth embodiment. [Figure 15-1] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the seventeenth embodiment. [Figure 15-2] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the seventeenth embodiment. [Figure 15-3] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the seventeenth embodiment. [Figure 15-4] 23 is a flowchart showing an example of the processing flow of a terminal and a server according to the seventeenth embodiment. [Figure 15-5] 23 is a flowchart showing an example of the processing flow of a terminal and a server according to the seventeenth embodiment. [Figure 15-6] 23 is a flowchart showing an example of the processing flow of a terminal and a server according to a seventeenth modified example. [Figure 16-1] FIG. 23 is a diagram showing an example of a table for explaining a processing method according to the eighteenth embodiment. [Figure 16-2] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the eighteenth embodiment. [Figure 16-3] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the eighteenth embodiment. [Figure 16-4]23 is a flowchart showing an example of the processing flow of a terminal and a server according to the eighteenth embodiment. [Figure 17-1] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the 19th embodiment. [Figure 17-2] FIG. 23 is a diagram showing an example of a display screen of a terminal according to the 19th embodiment. [Figure 18-1] FIG. 29 is a diagram showing an example of a display screen of a terminal according to the twentieth embodiment. [Figure 18-2] FIG. 29 is a diagram showing an example of a display screen of a terminal according to the twentieth embodiment. [Figure 18-3] FIG. 29 is a diagram showing an example of a display screen of a terminal according to the twentieth embodiment. [Figure 18-4] 20 is a flowchart showing an example of the processing flow of a terminal and a server according to the 20th embodiment. [Figure 19-1] FIG. 21 is a diagram showing an example of a display screen of a terminal according to the twenty-first embodiment. [Figure 19-2] FIG. 21 is a diagram showing an example of a display screen of a terminal according to the twenty-first embodiment. [Figure 19-3] FIG. 21 is a diagram showing an example of a display screen of a terminal according to the twenty-first embodiment. [Figure 19-4] 21 is a flowchart showing an example of the processing flow of a terminal and a server according to the twenty-first embodiment. [Figure 20-1] FIG. 22 is a diagram showing an example of a display screen of a terminal according to the twenty-second embodiment. [Figure 20-2] FIG. 22 is a diagram showing an example of a display screen of a terminal according to the twenty-second embodiment. [Figure 20-3] FIG. 22 is a diagram showing an example of a display screen of a terminal according to the twenty-second embodiment. [Figure 20-4] FIG. 22 is a diagram showing an example of a display screen of a terminal according to the twenty-second embodiment. [Figure 21-1] FIG. 26 is a diagram showing an example of a display screen of a terminal according to the twenty-sixth embodiment. [Figure 21-2] FIG. 26 is a diagram showing an example of a display screen of a terminal according to the twenty-sixth embodiment. [Figure 22-1] FIG. 27 is a diagram showing an example of a display screen of a terminal according to the 27th embodiment. [Figure 22-2] FIG. 27 is a diagram showing an example of a display screen of a terminal according to the 27th embodiment. [Figure 22-3]FIG. 27 is a diagram showing an example of a display screen of a terminal according to the 27th embodiment. [Figure 22-4] FIG. 27 is a diagram showing an example of a display screen of a terminal according to the 27th embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0006] <Compliance with legal matters> It should be noted that the disclosures described herein are subject to compliance with the laws of the country of implementation, such as communications secrecy, as necessary for the implementation of the disclosure.

[0007] An embodiment for implementing a program or the like according to the present disclosure will be described with reference to the drawings.

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

[0009] <System configuration> FIG. 1-1 is a diagram illustrating an example of a system configuration of a communication system 1 according to the present embodiment. In the communication system 1, as an example and not a limitation, a server 10 and a plurality of terminals 20 (terminal 20A, terminal 20B, terminal 20C, . . . ) are connected via a network 30.

[0010] The server 10 has a function of providing a payment service and a messaging service to a terminal 20 owned by a user via a network 30. The server 10 can also be expressed as a payment management server, a payment service server, a messaging server, a messaging service server, etc. In this embodiment, as an example and not a limitation, the user of the server 10 is a payment service provider or a messaging service provider.

[0011] The terminal 20 (terminal 20A, terminal 20B, terminal 20C, ...) may be any information processing terminal capable of implementing the functions described in each embodiment. The terminal 20 includes, but is not limited to, a smartphone, a mobile phone (feature phone), a computer (such as, but not limited to, a desktop, laptop, tablet, etc.), a media computer platform (such as, but not limited to, a cable or satellite set-top box, digital video recorder), a handheld computer device (such as, but not limited to, a PDA (personal digital assistant), email client, etc.), a wearable device (such as a glasses-type device, a watch-type device, etc.), a VR (Virtual Reality) terminal, a smart speaker (a device for voice recognition), or other types of computers or communication platforms. The terminal 20 may also be expressed as an information processing terminal.

[0012] The configurations of the terminals 20A, 20B, and 20C are basically the same. In addition, if necessary, the terminal used by the user X may be expressed as the terminal 20X, and the user information in a predetermined service associated with the user X or the terminal 20X may be expressed as the user information X. The user information is information of a user associated with an account used by the user in a specific service. The user information includes, but is not limited to, information associated with a user, such as the user's name, the user's icon image, the user's age, the user's sex, the user's address, the user's hobbies and interests, and the user's identifier, which is input by the user or given by a specific service, and may be any one of these, or a combination of these, or may not be the same.

[0013] The network 30 plays a role of connecting one or more terminals 20 and one or more servers 10. In other words, the network 30 refers to a communication network that provides a connection path so that the above-mentioned various devices can be connected and then transmit and receive data. The number of servers 10 and the number of terminals 20 connected to the network 30 are not limited.

[0014] One or more portions of network 30 may or may not be wired or wireless networks. Network 30 may include, by way of example and not limitation, 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 network, integrated service digital networks (ISDN), wireless LAN, long term evolution (LTE), code division multiple access (CDMA), Bluetooth, satellite communications, or the like, or a combination of two or more thereof. Network 30 may include one or more networks 30.

[0015] The server 10 (not limited to, but an example of a server, information processing device, or information management device) has a function of providing a predetermined service (such as a payment service or messaging service in this embodiment) to the terminal 20. The server 10 may be any device as long as it is an information processing device capable of realizing the functions described in each embodiment. The server 10 includes, not limited to, but an example of a server device, a computer (not limited to, but an example of a desktop, laptop, tablet, etc.), a media computer platform (not limited to, but an example of a cable or satellite set-top box, digital video recorder), a handheld computer device (not limited to, but an example of a PDA, email client, etc.), or other types of computers or communication platforms. The server 10 may also be expressed as an information processing device. When it is not necessary to distinguish between the server 10 and the terminal 20, the server 10 and the terminal 20 may or may not be expressed as information processing devices.

[0016] [Hardware (HW) configuration of each device] The hardware configuration of each device included in the communication system 1 will be described.

[0017] (1) Terminal hardware configuration FIG. 1-1 shows an example of the hardware configuration of the terminal 20. In FIG. The 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 clock unit 29A, and a position calculation information detection unit 29B. The HW components of the terminal 20 are connected to each other via a bus B, for example and not for limitation. It is not essential that the HW configuration of the terminal 20 includes all of the components. For example and not for limitation, the terminal 20 may or may not be configured such that individual components or multiple components are removable.

[0018] The communication I / F 22 transmits and receives various data via the network 30. The communication may be performed either wired or wirelessly, and any communication protocol may be used as long as the communication between the two devices is possible. The communication I / F 22 has a function of communicating 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 instructions from the control unit 21. The communication I / F 22 also receives various data transmitted from various devices such as the server 10 and transmits it to the control unit 21. The communication I / F 22 may also be simply referred to as a communication unit. When the communication I / F 22 is configured with a physically structured circuit, it may also be referred to as a communication circuit.

[0019] The input / output unit 23 includes a device for inputting various operations to the terminal 20, and a device for outputting the results of processing performed by the terminal 20. The input / output unit 23 may be an integrated input unit and an output unit, or may be separate from the input unit and the output unit, or may not be.

[0020] The input unit is realized by any one or a combination of all kinds of devices that can receive input from a user and transmit information related to the input to the control unit 21. Examples of the input unit include, but are not limited to, a touch panel, a touch display, hardware keys such as a keyboard, a pointing device such as a mouse, a camera (operation input via moving images), and a microphone (operation input by voice).

[0021] The output unit is realized by any one or a combination of all kinds of devices capable of outputting the processing results processed by the control unit 21. Examples of the output unit include, but are not limited to, a touch panel, a touch display, a speaker (audio output), a lens (for example, but not limited to, 3D (three dimensions) output and hologram output), a printer, etc.

[0022] In one embodiment, the input / output unit 23 includes, by way of example and not limitation, a display unit 24, a sound input unit 25, a sound output unit 26, and an imaging unit 27.

[0023] The display unit 24 is realized by any one of all kinds of devices capable of displaying according to the display data written in the frame buffer, or a combination thereof. 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 organic electroluminescence display (OLED)), a head mounted display (HDM), a projection mapping, a hologram, a device capable of displaying images, text information, and the like in air (which may or may not be a vacuum). Note that these display units 24 may or may not be capable of displaying display data in 3D.

[0024] The sound input unit 25 is used to input sound data (including voice data; the same applies below). The sound input unit 25 includes a microphone and the like. The sound output unit 26 is used to output sound data and includes a speaker and the like. The imaging unit 27 is used to acquire moving image data and includes a camera.

[0025] When the input / output unit 23 is a touch panel, the input / output unit 23 and the display unit 24 may be disposed facing each other and have approximately the same size and shape.

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

[0027] The clock unit 29A may or may not have a clock that conforms to the Network Identity and Time Zone (NITZ) standard or the like.

[0028] 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 a position calculation sensor unit, for example and not by way of limitation.

[0029] 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), 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, a UWB positioning sensor (UWB positioning unit) which is a sensor or unit for calculating the position of the terminal 20 using UWB (Ultra Wide Band), and the like.

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

[0031] The inertial measurement unit has an inertial sensor that is a sensor that detects information required for calculating the position of the terminal 20 by inertial navigation calculation. The inertial sensor includes, but is not limited to, 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 information for position calculation.

[0032] The UWB positioning unit includes, by way of example and not limitation, an ultra-wideband RF receiving circuit that converts an ultra-wideband RF (Radio Frequency) signal, including an ultra-wideband pulse signal for positioning transmitted from a positioning beacon and received by an antenna not shown, into a digital signal, and a relative position calculation processing circuit that calculates the relative position between the terminal 20 and the positioning beacon based on the digital signal output from the ultra-wideband RF receiving circuit. As an example and not by way of limitation, the UWB positioning unit may or may not cause the terminal 20 to function as a positioning beacon by transmitting an ultra-wideband RF signal including an ultra-wideband pulse signal for positioning from an antenna not shown.

[0033] As a non-limiting example, the control unit 21 calculates the position of its own terminal 20 at regular or specific timing based on the position calculation information detected by the position calculation information detection unit 29B. The terminal position 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 is calculated, and stores the calculated terminal position in the storage unit 28 as calculated terminal position history data.

[0034] The control unit 21 has a circuit physically structured to execute the functions realized by the code or instructions contained in the program, and is realized by a data processing device built into hardware, for example and not by way of limitation. Therefore, the control unit 21 may or may not be expressed as a control circuit.

[0035] The control unit 21 includes, by way of example and not limitation, 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).

[0036] 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, by way of example and not limitation, various storage media such as a hard disk drive (HDD), a solid state drive (SSD), a flash memory, a random access memory (RAM), and a read only memory (ROM). In addition, the storage unit 28 may or may not be expressed as a memory.

[0037] Terminal 20 stores program P in storage unit 28, and executes this program P, causing control unit 21 to execute processing as each unit included in control unit 21. In other words, program P stored in storage unit 28 causes terminal 20 to realize each function executed by control unit 21. Also, this program P may or may not be expressed as a program module.

[0038] (2) Server hardware configuration FIG. 1-1 shows an example of the HW configuration of the server 10. In FIG. The server 10 includes a control unit 11 (CPU), a storage unit 15, a communication I / F 14 (interface), an input / output unit 12, and a clock unit 19. The components of the HW of the server 10 are connected to each other via a bus B, for example and not for limitation. It is not essential that the HW of the server 10 includes all the components as the configuration of the HW of the server 10. For example and not for limitation, the HW of the server 10 may or may not be configured such that individual components or multiple components are removable.

[0039] The control unit 11 has circuits physically structured to execute functions realized by codes or instructions contained in a program, and is realized, for example and not by way of limitation, by a data processing device embedded in hardware.

[0040] The control unit 11 is typically a central processing unit (CPU), but may also be a microprocessor, a processor core, a multiprocessor, an ASIC, or an FPGA, but is not limited to these in the present disclosure.

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

[0042] The communication I / F 14 transmits and receives various data via the network 30. The communication may be performed either wired or wirelessly, and any communication protocol may be used as long as the communication between the two devices is possible. 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 instructions from the control unit 11. The communication I / F 14 also receives various data transmitted from various devices such as the terminal 20 and transmits it to the control unit 11. The communication I / F 14 may also be simply referred to as a communication unit. When the communication I / F 14 is configured with a physically structured circuit, it may also be referred to as a communication circuit.

[0043] The input / output unit 12 is realized by a device for inputting various operations to the server 10 . The input unit is realized by any one or a combination of all kinds of devices capable of receiving input from a user and transmitting information related to the input to the control unit 11. The input unit is typically realized by hardware keys such as a keyboard or a pointing device such as a mouse. Note that the input unit may or may not include a touch panel, a camera (operation input via moving images), or a microphone (operation input by voice), as examples and without limitation.

[0044] The output unit is realized by any one or a combination of all kinds of devices capable of outputting the processing results processed by the control unit 11. Examples of the output unit include, but are not limited to, a touch panel, a touch display, a speaker (audio output), a lens (for example, but not limited to, 3D (three dimensions) output and hologram output), a printer, etc.

[0045] In the first embodiment, the input / output unit 12 includes a display unit 13 .

[0046] The display unit 13 is typically realized by a monitor (for example, but not limited to, a liquid crystal display or an organic electroluminescence display (OLED)). The display unit 13 may or may not be a head mounted display (HDM) or the like. These display units 13 may or may not be capable of displaying display data in 3D. In the present disclosure, the display unit 13 is not limited to these.

[0047] The clock unit 19 is a built-in clock of the server 10, and outputs time information (timekeeping information). The clock unit 19 is configured to include, for example and not limitation, an RTC (Real Time Clock) as a hardware clock, a system clock, etc. The clock unit 19 can also be expressed as a timekeeping unit or a time information detection unit, for example and not limitation.

[0048] (3)Other The server 10 stores a program P in the storage unit 15, and by executing this program P, the control unit 11 executes the processes of each unit included in the control unit 11. In other words, 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.

[0049] In each embodiment of the present disclosure, the description will be given assuming that the CPU of the terminal 20 and / or the server 10 executes the program P to realize the present invention. The same applies to other devices.

[0050] 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 CPU having a control circuit, but may also realize each process by a logic circuit (hardware) formed in an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)) or a dedicated circuit. These circuits may or may not be realized by one or more integrated circuits, and the multiple processes shown in each embodiment may or may not be realized by one integrated circuit. Furthermore, an LSI may be called a VLSI, a super LSI, an ultra LSI, or the like, 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.

[0051] In addition, the program P (as an example, but not limited to, 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." In addition, the program P may or may not be for realizing part of the functions of each embodiment of the present disclosure. Furthermore, the program P 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 a storage medium.

[0052] The storage medium may include one or more semiconductor-based or other integrated circuits (ICs) (such as, by way of example and not limitation, a field programmable gate array (FPGA) or an application specific IC (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 diskette, 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 may be volatile, non-volatile, or a combination of volatile and non-volatile, where appropriate. It should be noted that the storage medium is not limited to these examples and may be any device or medium capable of storing the program P. In addition, the storage medium may or may not be referred to as a memory.

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

[0054] 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 executes the program P downloaded via the Internet or the like, for example and not for limitation, to realize the functions of the multiple functional units shown in each embodiment. The same applies to other devices.

[0055] 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 with one or more computers. At least a part or all of the processing in the terminal 20 may or may not be performed by the server 10. In this case, at least a part or all 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 or all of the processing in the server 10 may or may not be performed by the terminal 20. In this case, at least a part or all 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, the judgment configuration in the embodiments of the present disclosure is not essential, and a specified process may or may not be executed when the judgment condition is satisfied, or a specified process may or may not be executed when the judgment condition is not satisfied.

[0056] Note that the programs of the present disclosure are implemented using, by way of example and not 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.

[0057] An embodiment in which the present invention is realized by a server-client system will be described below.

[0058] However, the present invention is not limited to a server-client system, and may be implemented by a system that does not include a server, such as the following system, which is an example and not a limitation of the present invention. A system (distributed system) that provides the terminal 20 with the functionality of a server. This can be realized, for example and without limitation, by using block chain technology. A system in which terminals 20 communicate wirelessly with each other. This can be realized, for example and not by way of limitation, by communicating in a peer-to-peer (P2P) manner using short-range wireless communication technology such as Bluetooth.

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

[0060] <Summary> In recent years, applications (application software) related to network services, such as applications for making payments with electronic currency (payment applications), applications for making settlements with electronic currency (settlement applications), applications for sending / receiving remittances with electronic currency (remittance applications), and applications that aggregate some or all of the functions of these applications, are becoming more widespread, and users of terminal 20 are now able to use these applications to receive various services using electronic currency (electronic money).

[0061] "Electronic currency" refers to electronic currency that is distinct from physical currency and that is owned by the terminal 20 or the user of the terminal 20 and is managed in the various applications described above.

[0062] In addition, electronic currency may or may not be expressed as "electronic money" or "digital currency (digital coin)." Furthermore, as "electronic currency (electronic money)" or "digital currency (digital money)", legal tender currency or virtual currency may be used. In addition, "electronic currency (electronic money)" and "digital currency (digital currency)" may include cryptocurrency (crypto assets). Virtual currency may also include physical currency such as coupons.

[0063] The term "electronic money" will be used herein by way of example and not by way of limitation, and the balance in an electronic money account of a user of terminal 20 will be referred to as the "electronic money account balance."

[0064] In the following, a request from a user of a terminal 20 to a user (other user) of another terminal 20 to remit money is referred to as a "remittance request" (synonymous with a remittance request). Information related to this remittance request is referred to as "remittance request information." Requesting a remittance may be expressed as "requesting a remittance" or "making a remittance request." In addition, a request to remit may be expressed as "a remittance is requested" or "a remittance request is made", etc.

[0065] In addition, sending a remittance request will be expressed as "sending a remittance request" or "delivering a remittance request," but these are essentially synonymous. Conversely, receiving a remittance request is expressed as "receiving a remittance request" or "accepting a remittance request," but these are essentially synonymous.

[0066] In addition, in the following, the term meaning to remind, recollect, or reconfirm the contents of a remittance request to the other user will be referred to as a "remittance reminder," and information regarding this remittance reminder will be referred to as "remittance reminder information." Reminding someone to remit may be expressed as "reminding someone to remit" or "making a remittance reminder." In addition, being reminded to remit may be expressed as "being reminded to remit" or "a remittance reminder is made."

[0067] In addition, the remittance request information (the same applies to remittance reminder information) only needs to include at least information indicating that a remittance has been requested, information about the user requesting the remittance (the source of the remittance request), and information about the user to whom the remittance is requested.

[0068] As will be described later, the remittance request information may also include information such as the amount requested for remittance (hereinafter referred to as the "remittance request amount"), the reason for the remittance, and the deadline for payment by remittance (hereinafter referred to as the "payment deadline").

[0069] In the following description, it is assumed that various processes according to the present invention are executed by applications (a payment application and a messaging application) installed on the terminal 20.

[0070] It is also possible for a payment application to have a chat service (for example, but not limited to, a messaging service) as one of its functions, or for a chat application (for example, but not limited to, a messaging application) to have a payment service as one of its functions.

[0071] The messaging service is configured to allow users to chat using chat rooms. In the following description, a UI (User Interface) or GUI (Graphical User Interface) that allows each user to view content transmitted and received between terminals of multiple users is referred to as a "talk room" as appropriate. A talk room may also be referred to as a chat room.

[0072] Note that talk rooms can include, by way of example and not limitation, one-to-one user talk rooms as well as talk rooms for groups including multiple users (group talk rooms). In this case, the talk room refers to a UI or GUI that allows users in the group to view content transmitted and received between terminals in the group including multiple users.

[0073] Furthermore, the messaging service may or may not include an instant messaging service (IMS) that enables the sending and receiving of content such as simple messages between terminals 20.

[0074] In addition, there is also a view that considers messaging services (MS) (including IMS) as one form of social networking services (SNS). Therefore, a distinction may or may not be made between messaging services (MS) and social networking services (SNS).

[0075] <Example> An embodiment to which the present invention is applied will be described below. There may be cases where a remittance request from a second user (first user) to you (the user of the terminal) or from you to a second user is not processed, resulting in multiple remittance requests accumulating in the terminal 20. By way of example and not limitation, this may be the case when you accidentally forget to process a remittance request.

[0076] In this case, if the pending remittance requests are processed one by one, it takes time and is inconvenient. Furthermore, if the pending remittance requests are processed one by one, the user's balance may become insufficient.

[0077] Therefore, a method for processing multiple remittance requests (here, multiple unprocessed remittance requests) in a batch will be described. This batch processing will be called "batch processing". Batch processing can be broadly divided into at least the following processes: (1) Processing related to lump-sum settlement (hereinafter referred to as "lump-sum settlement") (2) Processing related to offsetting remittance requests (hereinafter referred to as "Request Offsetting"). (3) Processing related to the creation of bulk remittance requests (hereinafter referred to as "Bulk Remittance Requests"). (4) Processing related to special lump sum settlements (hereinafter referred to as "special lump sum settlements") and processing related to the creation of special lump sum remittance requests (hereinafter referred to as "special lump sum remittance requests").

[0078] In addition, in the embodiment described below, a case where the other user is one user, that is, a case where the second user is the first user (or the first user is the second user) will be exemplified. As will be explained in the modified examples, the method described below can also be applied in the case where the other users are different users, that is, where the first user is a different user from the second user (and the second user is a different user from the first user).

[0079] <First Example> The first embodiment is an embodiment relating to lump-sum settlement of the above lump-sum processing. The contents described in the first embodiment are applicable 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.

[0080] <Functional configuration> (1) Server FIG. 1-2 is a diagram showing an example of functions realized by the control unit 11 of the server 10 in this embodiment. The control unit 11 of the server 10 includes, as a functional unit and not by way of limitation, a payment application management processing unit 111 which performs processing to provide various payment services via payment applications to the terminal 20 or the user of the terminal 20 in accordance with a payment application management processing program 151 stored in the memory unit 15.

[0081] FIG. 1-3 is a diagram showing an example of information stored in the storage unit 15 of the server 10 in this embodiment. The memory unit 15 stores, by way of example and not limitation, a payment application management processing program 151 which is read by the control unit 11 and executed as a payment application management process, user registration data 153, a user management database 155, and remittance request management data 157.

[0082] The user registration data 153 is registration data relating to the terminal 20 that uses the payment application or the user of that terminal 20, and an example of the data configuration is shown in FIG. 1-4. In the user registration data 153, for example and not for limitation, a user name, an application ID, a terminal phone number, and other registration information are stored in association with each other.

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

[0084] The application ID is information used to identify a payment application account, or the account itself. This application ID is preferably a value unique to each account, and as a non-limiting example, a unique value (proper value) is set and stored by the server 10 for each account. The application ID is information associated with the terminal 20 or the user of the terminal 20, and is an example of information related to the terminal or information related to the user of the terminal.

[0085] The terminal phone number is the phone number of the terminal 20 of the user of this username, and by way of example and not limitation, the phone number of the terminal 20 that the user of the terminal 20 registers when using a payment application is stored.

[0086] Other registration information may include, by way of example and not limitation, the ID of terminal 20: terminal ID (by way of example and not limitation, IMEI (International Mobile Equipment Identity)), the email address (terminal email address) of terminal 20 of the user of this username, and authentication information such as passwords (login password, authentication password) used for various authentications in the payment application.

[0087] The identification information for identifying the terminal 20 may be, for example and not by way of limitation, a terminal ID. Furthermore, the identification information for identifying the user of the terminal 20 can be, for example and without limitation, an application ID. Note that this may or may not be a "user ID."

[0088] Furthermore, if the application allows only one account to be registered per terminal 20, then, as a non-limiting example, "identification information for identifying terminal 20 = identification information for identifying the user of terminal 20 = application ID" can be used.

[0089] Also, by way of example and not limitation, it may or may not be possible to assign multiple terminal IDs to one user ID.

[0090] It should be noted that registration of the terminal telephone number is not essential, and the terminal telephone number may not be stored in the user registration data 153 .

[0091] Also, it is possible to apply a method of managing accounts by terminal telephone numbers instead of various IDs such as application IDs. In this case, instead of storing IDs such as application IDs in user registration data 153, terminal telephone numbers can be stored in user registration data 153.

[0092] The user management database 155 is a database that cumulatively stores data for managing information about the terminal 20 that uses the payment application or its user, and one example of the configuration of the first user management database 155A is shown in Figure 1-5.

[0093] In the first user management database 155A, user management data is stored as management data for each application ID. Each user management data includes, by way of example and not limitation, an application ID, the balance of an electronic money account of a user identified by the application ID, remittance history data, and receipt history data.

[0094] The remittance history data is data in which information on the history of remittances from a user of this application ID to a user of another application ID (remittance history information) is stored.

[0095] The receipt history data is data in which information on the history of receipts by the user of this application ID from users of other application IDs (receipt history information) is stored.

[0096] The remittance request management data 157 is a database that cumulatively stores data for managing information related to remittance requests, and an example of the configuration of the first remittance request management data 157A is shown in FIG. 1-6. In the first remittance request management data 157A, for example and not by way of limitation, a date and time, a remittance request management ID, a remittance master ID, a remittance request destination ID, a remittance request amount, and a remittance completion flag are stored in association with each other.

[0097] As the date and time, for example and not by way of limitation, the date and time when the remittance request information of the corresponding remittance request is transmitted from the server 10 to the terminal 20 of the remittance request destination user is stored.

[0098] The remittance request management ID stores an ID that is uniquely set by the server 10 for each remittance request.

[0099] The remittance master ID stores the application ID of the user who requested the remittance (also called the remittance master user). The remittance request destination ID stores the application ID of the user who has requested remittance (also called the remittance request destination user).

[0100] The remittance request amount stores the amount of money requested by the remittance master user to be remitted to the remittance request destination user by the remittance request.

[0101] The remittance completed flag is a flag that indicates whether or not the remittance corresponding to the remittance request has been completed by the control unit 11 executing the settlement process. The default is set to "OFF" and is set to "ON" when the remittance is completed.

[0102] There are two possible methods for the server 10 to manage remittance requests: (1) Pattern A: Leave the remittance request after the remittance has been executed without deleting it. (2) Pattern B: Delete the remittance request that has been executed.

[0103] Either of these patterns can be applied, but when pattern A is applied, the data of the remittance request with the remittance completion flag set to "ON" is left intact and not deleted. On the other hand, when pattern B is applied, the record of the data of the remittance request for which the remittance was executed is deleted.

[0104] (2) Terminal FIG. 1-7 is a diagram showing an example of functions realized by a control unit 21 of a terminal 20 in this embodiment. The control unit 21 includes, as a functional unit, a payment application processing unit 211 that executes payment application processing in accordance with a payment application processing program 281 stored in the storage unit 28, for example and not by way of limitation.

[0105] FIG. 1-8 is a diagram showing an example of information stored in the storage unit 28 of the terminal 20 in this embodiment. The memory unit 28 stores, by way of example and not limitation, a payment application processing program 281 that is read by the control unit 21 and executed as a payment application process, and an application ID 283 associated with the terminal 20 itself or its user.

[0106] <Display screen> In the following, as an example and not a limitation, a case will be illustrated in which the terminal 20 is a smartphone equipped with a display unit 24 having a portrait display.

[0107] For example, but not by way of limitation, a smartphone has a touch panel that functions as an input unit and is disposed opposite the display, thereby forming a touch screen. When an element such as an icon, button, item, or input area is displayed on the display, and a part of the touch panel that faces the area where the element is displayed is operated by a user, a program associated with the element or a subroutine of the program is executed.

[0108] In the following, the operation by the user will be described as a tap (tap operation) as an example and not as a limitation. A tap (tap operation) is, by way of example and not limitation, an action in which a user lightly touches the display unit 24 (touch screen) that is integrally configured with a touch panel with a finger or the tip of a pen, and then releases the touch.

[0109] The transition of the display screens described below is merely an example of the transition of the display screens for implementing the method of the present disclosure. In the transition of the display screens illustrated below, some of the display screens may be omitted, or other display screens may be added.

[0110] 1-9 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment. This screen is, by way of example and not by way of limitation, a main menu screen of a payment application displayed on the display unit 24 of the terminal 20A of the user AA.

[0111] The name of the payment application, "Payment App," is displayed in the center of the top of the menu screen. Also, the icon image and user name (user AA in this example) of the payment application of the user of this terminal 20 are displayed in the top right of the screen.

[0112] Also below that is a current location display area CLR1 which shows the current location in the payment application. In this example, the words “Wallet Main Menu” are displayed in the current location display area, indicating that the current location is the main menu of the payment application.

[0113] When a remittance request list icon IC1 displayed at the bottom of the main menu screen is tapped, information requesting remittance request list information is sent from the terminal 20A to the server 10, and the remittance request list information is sent from the server 10 to the terminal 20A. As a result, a remittance request list screen such as that shown in FIG. 1-10 is displayed, by way of example and not limitation.

[0114] The current location display area CLR1 displays the words "Remittance Request List," which indicates that remittance request list information is being displayed.

[0115] This remittance request list screen displays unprocessed remittance requests (hereinafter referred to as "unprocessed requests") between users of different terminals 20 as remittance requests related to the user of the user's own terminal 20 (user AA), sorted by user of the different terminals 20.

[0116] In the following, the user who proposes performing batch processing will be referred to as the "proposer user" as appropriate. Furthermore, a user to whom a batch process is proposed by the proposer user is appropriately referred to as a "partner user."

[0117] Specifically, for multiple users such as user BB, user CC, user DD, and user EE, the number of unprocessed requests between the user and the user is displayed in association with each user's icon image and user name, along with the settlement amount (hereinafter referred to as the "lump sum settlement amount") that would be incurred if all unprocessed requests between the user and the user were processed together.

[0118] Here, the amount that you will pay to the other party through a remittance request made to you by the other party will be referred to as the "payment amount" as appropriate, and the amount that you will receive from the other party through a remittance request made to you by yourself will be referred to as the "received amount" as appropriate. In this case, the "lump sum settlement amount" is the sum of the payment amount and the receipt amount corresponding to each unprocessed request with the positive and negative signs reversed when all the unprocessed requests are processed at once. This lump sum settlement amount is calculated in the settlement process executed by the control unit 11 of the server 10, as an example and not a limitation.

[0119] Furthermore, in this example display screen, a payment mark indicating "payment" is displayed next to the lump sum settlement amount if you are paying that lump sum settlement amount to the other party, and a receipt mark indicating "receipt" is displayed next to the lump sum settlement amount if you are receiving that lump sum settlement amount from the other party.

[0120] As a non-limiting example, it is shown that user AA (self) has four outstanding requests with user BB (other party), and if these four outstanding requests are processed together, user AA will pay user BB a lump sum settlement amount of "1,000 yen."

[0121] Similarly, by way of example and not limitation, it is shown that user AA (self) has four outstanding requests between user CC (other party), and if these four outstanding requests are processed together, user AA will receive "4,000 yen" as a lump-sum settlement amount from user CC.

[0122] Also displayed at the bottom of the screen is a settlement button BT1 for requesting the server 10 to settle all outstanding requests at once.

[0123] In this screen, by way of example and not limitation, when the display area WR1 of the user CC is tapped, a remittance request details screen shown in FIG. 1-11 is displayed. In this remittance request details screen, details of the pending request between the user CC and the remittance request are displayed.

[0124] Bulk settlement refers to settling multiple unprocessed requests at once, and examples include, but are not limited to, "all-selection lump-sum settlement," in which all unprocessed requests are settled at once, and "partial-selection lump-sum settlement," in which some and multiple unprocessed requests are settled at once.

[0125] The current location display area CLR1 at the top of the screen displays the words "Transfer request with CC," indicating that an unprocessed request between the user CC and the screen is being displayed. In addition, below the current location display area CLR1, the lump sum settlement amount (in this example, "4,000 yen") and a mark (in this example, a "receive mark") are displayed in association with the icon image and user name of user CC, assuming that all items are selected and settled at once.

[0126] Next to the icon image of user CC, there is provided a check area ASR1 configured so that the check can be switched "ON / OFF" by tapping, and by checking "ON", a check mark is displayed in the check area, making it possible to settle all outstanding requests in one lump sum.

[0127] Below that, remittance requests with user CC as the recipient are listed. In this example, unprocessed requests with user CC as the recipient are listed in chronological order from the top to the bottom, and processed requests (hereinafter referred to as "processed requests") are listed in chronological order from the top to the bottom below the list of unprocessed requests. Processed requests are displayed in a different manner (grayed out in this example) to distinguish them from unprocessed requests.

[0128] In the following, a remittance request that has already been sent from one party to another party is referred to as a "sent remittance request", and a remittance request that has already been received from another party is referred to as a "received remittance request". In this case, a request sending mark indicating "Request Sent" is displayed for a remittance request that has been sent among the unprocessed requests, and a request receiving mark indicating "Request Received" is displayed for a remittance request that has been received among the unprocessed requests.

[0129] In addition, for each unprocessed request, the date and time when the request was sent from the user's own terminal 20 to the other user's terminal 20 is displayed in association with the sent remittance request, and for each received remittance request, the date and time when the request was received by the user's own terminal 20 from the other user's terminal 20 is displayed in association with the received remittance request.

[0130] Additionally, each outstanding request may have associated therewith, by way of example and not limitation, a reason for the transfer of funds resulting from that outstanding request.

[0131] It is also possible to not include the information on the remittance request amount in the remittance request information and not display the information on the remittance request amount. In this case, by way of example and not of limitation, the proposer user can inquire about the information on the remittance request amount from the server 10 or from the other user.

[0132] Also, information on the remittance request amount may be included in the remittance request information but not displayed on the remittance request list screen or the individual remittance request screen. In this case, as a non-limiting example, a remittance request details screen including information on the remittance request amount may be displayed based on an input made to confirm the details of the remittance request on the individual remittance request screen.

[0133] The same applies to other information related to a remittance request, such as information on the reason for remittance.

[0134] In addition, for each unprocessed request, by way of example and not limitation, for a sent remittance request, a receipt mark is displayed in association with the receipt amount that the user will receive from the other party by processing the sent remittance request, and for a received remittance request, a payment mark is displayed in association with the payment amount that the user will pay to the other party by processing the received remittance request.

[0135] In addition, next to each unprocessed request, there is a check area SR1 that can be turned "ON / OFF" by tapping. By turning the check "ON", a check mark is displayed in the check area SR1, and the unprocessed request can be selected as a target for lump-sum settlement.

[0136] Also displayed at the bottom of the screen is a settlement button BT2 for requesting the server 10 to settle all selected unprocessed requests at once.

[0137] In FIG. 1-11, the processed requests are displayed together with the unprocessed requests, but the processed requests may not be displayed.

[0138] As a non-limiting example, when the third sent remittance request (received 10,000 yen) and the fourth received remittance request (paid 3,000 yen) are selected by checking them as “ON” and the settlement button BT2 is tapped, the display shown in Figure 1-12 will be displayed.

[0139] In Figure 1-12, lump-sum settlement confirmation information is displayed at the bottom of the screen in Figure 1-11 to allow the user to confirm the contents of the lump-sum settlement. In this example, a settlement content confirmation area ACR1 is provided within an electronic money account balance display area WBR1, which contains the text "Wallet Balance," to show how the user's current electronic money account balance will change as a result of the lump-sum settlement.

[0140] In the settlement details confirmation area ACR1, by way of example and not limitation, the current balance of the user's (user AA's) electronic money account is displayed on the left side, and the balance of the user's electronic money account after settlement is displayed on the right side. Also below that are displayed the text "Do you want to propose payment with this amount?" along with a proposal button BT3 marked "Propose" for proposing payment and a cancel button marked "Cancel" for cancelling the payment.

[0141] In this example, the current balance in the user AA's electronic money account is "500 yen." When the two requests selected above are settled in a lump sum, the total for user AA will be "Received 10,000 yen" and "Payed 3,000 yen", resulting in "Received 7,000 yen". This shows that the lump sum settlement amount of "7,000 yen" will be added to the current electronic money account balance of "500 yen", resulting in the electronic money account balance after settlement being "7,500 yen".

[0142] 1-13 is a diagram showing an example of a notification screen of the payment application that is displayed when the proposal button BT3 is tapped on the above screen. This notification screen is an example of a screen that is displayed on the display unit 24 of the terminal 20C of the user CC who is the other party of the user AA.

[0143] When the proposal button BT3 is tapped on the screen displayed on the display unit 24 of the terminal 20A in FIG. 1-12, the terminal 20A requests the server 10 to execute lump-sum settlement. Then, the server 10 transmits lump-sum settlement approval confirmation information to the terminal 20C of the other party, user CC, to confirm whether or not to approve the lump-sum settlement, and the lump-sum settlement approval confirmation information is displayed on the display unit 24 of the terminal 20C.

[0144] A current location display area CLR2 is configured at the top of this notification screen, and displays the word "Notice" to indicate that a notification about a payment application is being displayed.

[0145] Below the current location display area CLR2, a notification NT1 is displayed containing a bell mark and the words “A settlement proposal for your remittance request has been received” as a notification indicating that a settlement proposal for the remittance request has been received from user AA's terminal 20A via server 10.

[0146] Below that, a notice information display area NTR1 for displaying notice information is configured, and in this notice information display area NTR1, information corresponding to the above-mentioned notification NT1 is displayed. In this example, the lump-sum settlement approval confirmation information includes the text "Settlement proposal," the icon image of the other party, user AA, and the lump-sum settlement amount. In this example, the lump-sum settlement amount is displayed, indicating that user CC needs to pay "7,000 yen" to user AA.

[0147] In addition, the lump-sum settlement approval confirmation information includes a link LK1 with the text "Check details" to confirm the details of the lump-sum settlement, and by tapping this link LK1, the details of the lump-sum settlement (for example, but not limited to, the breakdown) can be confirmed.

[0148] In addition, instead of displaying the details of the lump-sum settlement from the "Check details" link LK1, the details of the lump-sum settlement may be displayed in a manner that allows switching between left and right directions or depth directions, for example and not limitation. One example of this is a carousel display, for example and not limitation. This technique is equally applicable to any of the embodiments.

[0149] In addition, the lump-sum settlement approval confirmation information displays a settlement button marked "Settle" for approving the settlement with the above content, and a rejection button marked "Reject" for rejecting the settlement with the above content.

[0150] When the above link LK1 is tapped, a screen such as that shown in FIG. 1-14 is displayed, by way of example and not limitation. This screen is one of the remittance request list screens displayed on the display unit 24 of the terminal 20C, which displays a list of pending requests between the remittance request and the other user AA. This screen corresponds to the screen displayed on the display unit 24 of the terminal 20A shown in FIG. 1-12.

[0151] The current location display area CLR2 displays the words "Remittance request with AA," which indicates that an unprocessed request between user AA and the user is being displayed.

[0152] In the settlement details confirmation area ACR2 at the bottom of the screen, by way of example and not limitation, the current balance of the user's (user CC's) electronic money account is displayed on the left, and the balance of the user's electronic money account after settlement is displayed on the right. Also below that are displayed, along with the text "Do you want to settle with this amount?", a settlement button BT4 labeled "Settlement" for approving the settlement, and a revision proposal button labeled "Suggest revision" for suggesting revisions to the settlement without approving the settlement.

[0153] In this example, the current balance of the user CC's electronic money account is "11,000 yen." When the two requests proposed by user AA are settled in a lump sum, the total for user CC is "Payment 10,000 yen" and "Received 3,000 yen", which amounts to "Payment 7,000 yen". Therefore, by subtracting the lump sum settlement amount "7,000 yen" from the current electronic money account balance of "11,000 yen", the electronic money account balance after settlement will be "4,000 yen".

[0154] FIG. 1-15 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20A when the settlement button BT4 is tapped. In this example, in the notification information display area NTR2 of the notification screen, two sets of settlement result information are displayed as the contents of a lump sum settlement that has been made between the user CC and the notification information display area NTR2 of the notification screen. Specifically, by way of example and not limitation, settlement result information corresponding to the third and fourth remittance requests selected in Figures 1-11 and 1-12 is displayed.

[0155] Each settlement result information shows the individual amount along with "Request settlement" and the icon image of the other user.

[0156] In addition, rather than displaying settlement result information corresponding to each selected remittance request, it is also possible to display a single settlement result information as a result of a lump-sum settlement, as shown in Figure 1-16, by way of example and not limitation.

[0157] As a non-limiting example, when the details confirmation link LK2 included in the payment result information in FIG. 1-16 is tapped, a screen such as that shown in FIG. 1-17 is displayed. The current location display area CLR1 on this screen displays the words "Request Settlement," indicating that the results of lump-sum settlement are being displayed.

[0158] Below the current location display area CLR1, the lump-sum settlement amount for the executed lump-sum settlement (in this example, "7,000 yen") and a mark (in this example, a "received mark") are displayed in association with the icon image and user name of user CC. Below that is a list of transfer requests that have been processed in bulk.

[0159] Also, at the bottom of the screen, an electronic money account balance display area WBR1 is displayed. This electronic money account balance display area WBR1 displays the words "Wallet Balance," and below that is a settlement result balance display area ARR1 that shows how your electronic money account balance has changed as a result of the lump-sum settlement.

[0160] In the settlement result balance display area ARR1, as a non-limiting example, the current electronic money account balance of the user (user AA) is displayed on the left side, and the electronic money account balance of the user as a result of lump-sum settlement is displayed on the right side. Also, below that, the text "Two requests have been settled" is displayed to indicate that a bulk settlement has been made.

[0161] In this example, it is shown that the balance of the electronic money account of user AA has changed from "500 yen" to "7,500 yen" as a result of a lump-sum settlement.

[0162] <Processing> (1) An example of processing First, an example of the process in this embodiment will be described. The processes described below are merely examples of processes for implementing the method of the present disclosure, and the present disclosure is not limited to these processes. Moreover, other steps may be added to the processes described below, or some steps may be omitted (deleted). This also applies to each of the flowcharts (processes) described below.

[0163] FIG. 1-18 is a flowchart showing an example of the flow of processing executed by each device in this embodiment. From the left, there are shown a process executed by the control unit 21 of the terminal 20A, a process executed by the control unit 21 of the terminal 20B, and a process executed by the control unit 11 of the server 10, respectively. By way of example and not limitation, a case may be taken where user AA at terminal 20A requests that remittance requests made to user BB at terminal 20B be processed in bulk. In this process, for simplicity, the determination of whether the process is complete is omitted.

[0164] First, the control unit 21 of the terminal 20A transmits, based on an input to the input unit, by way of example and not limitation, remittance request list request information for requesting a list of remittance requests to the server 10 via the communication I / F 22 (A110).

[0165] In response to this, the control unit 11 of the server 10 refers to the first remittance request management data 157A and transmits the remittance request list information for user AA to the terminal 20A via the communication I / F 14 (S120).

[0166] When the remittance request list information is received via the communication I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received remittance request list information (A120).

[0167] Thereafter, the control unit 21 of the terminal 20A determines whether one or more remittance requests have been selected (A130), and if it determines that they have been selected (A130: YES), it transmits request selection information regarding the selected remittance requests to the server 10 via the communication I / F 22 (A140).

[0168] The control unit 11 of the server 10 determines whether or not the request selection information has been received from the terminal 20A via the communication I / F 14 (S140), and if it is determined that the request selection information has been received, executes a settlement process (S150).

[0169] FIG. 1-19 is a flowchart showing an example of the flow of a first settlement process, which is an example of the settlement process. The control unit 11 of the server 10 judges whether the settlement object is a lump-sum settlement object based on the request selection information received from the terminal 20A (S1510). Specifically, it judges whether the selected remittance request is two or more (plural) remittance requests.

[0170] If it is determined that the remittance requests are eligible for lump-sum settlement (S1510: YES), the control unit 11 of the server 10 calculates the lump-sum settlement amount based on the remittance request amount of the selected remittance request and the type of each selected remittance request (received remittance request (payment) / sent remittance request (receive)) (S1515).

[0171] Thereafter, the control unit 11 of the server 10 determines whether or not the balance of the electronic money account of at least one of the proposer user and the other user will become negative, based on the calculated lump-sum settlement amount (S1520).

[0172] If it is determined that the amount will be negative (S1520: YES), the control unit 11 of the server 10 sends, by way of example and not limitation, lump-sum settlement NG information indicating that lump-sum settlement is not possible to the terminal 20A via the communication I / F 14 (S1523). Then, the control unit 11 of the server 10 ends the first settlement process.

[0173] On the other hand, if it is determined that the electronic money account balance will not become negative (S1520: NO), the control unit 11 of the server 10 sends settlement confirmation information including lump-sum settlement amount information, which is information on the calculated lump-sum settlement amount, to the terminal 20A via the communication I / F 14 (S1525).

[0174] When the settlement confirmation information is received from the server 10 via the communication I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received settlement confirmation information (A150).

[0175] Thereafter, the control unit 21 of the terminal 20A determines whether or not to request the server 10 to execute settlement (A160) based on whether or not an input has been made to the settlement confirmation information displayed on the display unit 24, for example and not as a limitation. Then, if it is determined that settlement is to be requested (A160: YES), the control unit 21 of the terminal 20A transmits settlement execution request information to the server 10 via the communication I / F 22 (A170).

[0176] The control unit 11 of the server 10 determines whether or not to execute settlement based on whether or not settlement execution request information has been received from the terminal 20A via the communication I / F 14 (S1530). If it is determined that settlement is to be executed (S1530: YES), the control unit 11 of the server 10 executes lump-sum settlement (S1540).

[0177] FIG. 1-20 is a diagram illustrating an example of a table for explaining lump-sum settlement. This table shows the types of unprocessed requests of the user who proposed the lump-sum settlement (user AA in this processing example) vertically and horizontally, and shows the process for lump-sum settlement of two unprocessed requests based on a proposal by the proposer user, assuming that the other user (user BB in this processing example) is a single user. The vertical and horizontal pending requests include received remittance requests and sent remittance requests, respectively.

[0178] (1-1) Combination of received remittance requests and received remittance requests In this combination, the proposer's user (user AA) makes a transfer to the other user (user BB) based on two outstanding transfer requests already received from the other user.

[0179] In this case, the control unit 11 of the server 10 executes a process for transferring the sum of the remittance request amounts of the two received remittance requests from the proposer user to the other user as the lump-sum settlement amount in the lump-sum settlement. Specifically, the control unit 11 of the server 10 updates the electronic money account balance of the proposer user by subtracting the lump-sum settlement amount from the electronic money account balance of the proposer user, and updates the electronic money account balance of the other user by adding the lump-sum settlement amount to the electronic money account balance of the other user.

[0180] (1-2) Combination of received remittance requests and sent remittance requests (1-3) Combination of sent remittance requests and received remittance requests In this combination, the proposer user remits / receives money to / from the other user based on the unprocessed remittance request already received from the other user and the unprocessed remittance request already sent to the other user. In this case, since the relationship is one of payment and receipt, the lump-sum settlement amount is the difference between the remittance request amount of the received remittance request and the remittance request amount of the sent remittance request. Hereinafter, taking the difference in the remittance request amount (subtracting an amount) will be referred to as "subtracting an amount."

[0181] In addition, deduction of amounts includes offsetting of amounts (hereinafter referred to as "amount offset"). By way of example and not limitation, offsetting amounts means that the amounts of the remittance requests selected for processing are offset against each other to produce zero amounts. Amount offsetting occurs when the net result of deduction of amounts is zero.

[0182] In this example, if the remittance request amount of the received remittance request (the amount to be remitted) and the remittance request amount of the sent remittance request (the amount to be received) are the same amount, the amounts will be offset.

[0183] In this case, if the remittance request amount of the received remittance request (second amount) is greater than the remittance request amount of the sent remittance request (first amount), the control unit 11 of the server 10 calculates the lump-sum settlement amount as the amount obtained by subtracting the remittance request amount of the sent remittance request from the remittance request amount of the received remittance request (third amount), and then updates the electronic money account balance of the proposer's user by subtracting the lump-sum settlement amount, and updates the electronic money account balance of the other user by adding the lump-sum settlement amount.

[0184] In the opposite case, the lump-sum settlement amount is subtracted from the balance of the other user's electronic money account to update it, and the lump-sum settlement amount is added to the balance of the proposer's user's electronic money account to update it.

[0185] Furthermore, if the remittance request amount (second amount) of the received remittance request and the remittance request amount (first amount) of the sent remittance request are the same amount, the amounts are offset, and no remittance is made.

[0186] As will be explained in detail in a later embodiment, in the case of a combination of a received remittance request and a sent remittance request, it is also possible to process "remittance + remittance reminder (or new remittance request)" by way of example and not by way of limitation. In other words, it is possible to send money to the other user based on the received remittance request, and also to send a remittance reminder (or a new remittance request) to the other user based on the sent remittance request.

[0187] (1-4) Combination of sent remittance requests and sent remittance requests In this combination, the user proposing the lump-sum settlement sends a new remittance request to the other user that combines two unprocessed remittance requests (sent remittance requests) addressed to the other user.

[0188] This remittance request is a type of remittance request that consolidates multiple remittance requests (hereinafter referred to as a "bulk remittance request") and is used for purposes such as encouraging the remittance of the amount already requested to be remitted in one lump sum. For convenience, this remittance request will be referred to as a "confirmation batch remittance request."

[0189] In this case, the control unit 11 of the server 10 creates a confirmation lump sum remittance request based on a request from the proposer's terminal 20. Then, the control unit 11 of the server 10 transmits confirmation lump sum remittance request information corresponding to the created confirmation lump sum remittance request to the other user's terminal 20.

[0190] In addition, in this combination (1-4), the control unit 11 of the server 10 may or may not send remittance reminder information corresponding to each of the selected multiple sent remittance requests to the other user's terminal 20, instead of sending confirmation bulk remittance request information to the other user's terminal 20.

[0191] In addition, in the combination of (1-4), the user who proposes the lump-sum settlement (user AA in this processing example) may or may not receive money from the other user (user BB in this processing example) based on two unprocessed remittance requests that he or she has made to the other user.

[0192] In this case, the control unit 11 of the server 10 executes a process for transferring the total amount of the remittance requests of the selected transmitted remittance requests from the other user to the proposer user as the lump-sum settlement amount in the lump-sum settlement. Specifically, the control unit 11 of the server 10 updates the balance of the other user's electronic money account by subtracting the lump-sum settlement amount, and updates the balance of the proposer's electronic money account by adding the lump-sum settlement amount.

[0193] Strictly speaking, making a confirmation batch remittance request (sending a confirmation batch remittance request information) and making a remittance reminder (sending remittance reminder information) can be considered to have a different meaning and concept from "settlement." However, for the sake of simplicity, this specification will be illustrated and described as including these in settlement (as a type of settlement).

[0194] Returning to FIG. 1-19, after executing the lump-sum settlement in S1540, the control unit 11 of the server 10 ends the first settlement process.

[0195] On the other hand, if it is determined that the settlement target is not a lump-sum settlement target, that is, only one remittance request has been selected (S1510: NO), the control unit 11 of the server 10 determines whether the balance of the proposer's user's electronic money account will be negative (S1570). If it is determined that the balance will be negative (S1570: YES), the control unit 11 of the server 10 transmits, by way of example and not limitation, settlement NG information indicating that settlement is not possible to the terminal 20A via the communication I / F 14 (S1573). Then, the control unit 11 of the server 10 ends the first settlement process.

[0196] On the other hand, if it is determined that the electronic money account balance will not become negative (S1570: NO), the control unit 11 of the server 10 sends settlement confirmation information including the settlement amount (the remittance request amount of the selected received remittance request) to the terminal 20A via the communication I / F 14 (S1575).

[0197] When the settlement confirmation information is received from the server 10 via the communication I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received settlement confirmation information (A150).

[0198] Thereafter, the control unit 21 of the terminal 20A determines whether or not to request execution of settlement (A160) based on whether or not an input has been made in response to the settlement confirmation information displayed on the display unit 24, for example and not as a limitation. If it is determined that execution of settlement is to be requested (A160: YES), the control unit 21 of the terminal 20A transmits settlement execution request information to the server 10 via the communication I / F 22 (A170).

[0199] The control unit 11 of the server 10 determines whether or not to execute the settlement (S1580) based on whether or not settlement execution request information has been received from the terminal 20A via the communication I / F 14. Then, if it is determined to execute the settlement (S1580: YES), the control unit 11 of the server 10 executes the settlement (S1590). Then, the control unit 11 of the server 10 ends the first settlement process.

[0200] Returning to FIG. 1-18, once the settlement process has been executed, the control unit 11 of the server 10 judges whether the settlement result is "OK" or not (S170). If it is judged to be "OK" (S170: YES), the control unit 11 of the server 10 transmits the settlement result information to the terminal 20A and the terminal 20B via the communication I / F 14 (S190). Then, the control unit 11 of the server 10 ends the process.

[0201] When the settlement result information is received from the server 10 via the communication I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received settlement result information (A190). Then, the control unit 21 of the terminal 20A ends the process.

[0202] Similarly, when the settlement result information is received from the server 10 via the communication I / F 22, the control unit 21 of the terminal 20B causes the display unit 24 to display the received settlement result information (B190). Then, the control unit 21 of the terminal 20B ends the process.

[0203] (2) Other examples of processing Next, another example of the process in this embodiment will be described. When making a lump sum settlement, it is also possible to require the approval of the other user. This is because the following cases can be considered:

[0204] (A) A malicious user intends to gain an advantage by making a lump-sum settlement This is an unavoidable problem in a system where remittance requests are created by user input.

[0205] As a non-limiting example, a malicious user may send a false remittance request to a different user. Specifically, it is assumed that a malicious user creates a false remittance request, sends it to the different user, and then offsets the amount by settling in a lump sum. More specifically, as a non-limiting example, when user AA receives a remittance request from user BB for a specific remittance request amount (e.g., "3,000 yen"), user AA creates a remittance request for the same amount (e.g., "3,000 yen") and sends it back to user BB, and then user AA sets off the lump sum.

[0206] In addition, a malicious user may also send a false remittance request to a recipient without the recipient's knowledge, and then use the false remittance request to settle a lump sum of payments.

[0207] In these cases, not requiring the other user's approval would leave the other user open to deception.

[0208] (B) Cases where a lump sum settlement is made against the other party's wishes As an example, and not as a limitation, when a lump sum settlement is made that includes at least one of the remittance requests that have already been sent to the other user, the other user may feel that they have suffered a loss because the remittance request that is the remittance (payment) request from the other user's perspective is included in the lump sum settlement. However, if all transfer requests are processed, the end result will be the same, as long as legitimate transfer requests are processed.

[0209] In either of the above cases, approval from the other user may be required in order to allow the other user to confirm whether the remittance request that is the subject of bulk settlement is a legitimate remittance request (whether it is truly correct).

[0210] Fig. 1-21 is a flow chart showing another example of the flow of the processes executed by each device in this embodiment. The view of the figure is the same as that of Fig. 1-18. In this process, the control unit 11 of the server 10 executes a second settlement process in S150.

[0211] FIG. 1-22 is a flowchart showing an example of the flow of the second settlement process. If it is determined in S1530 that a request for lump-sum settlement execution has been made (S1530: YES), the control unit 11 of the server 10 determines whether approval of the other user is required (S1531). Specifically, by way of example and not limitation, it determines whether the remittance request management IDs of the two or more selected remittance requests include a remittance request management ID whose associated remittance master ID is the application ID of user AA and whose associated remittance request destination ID is the application ID of a user other than user AA, that is, whether a remittance request from the other party (user BB) to the proposer's user (user AA) is included.

[0212] If it is determined that approval from the other user is required (S1531: YES), the control unit 11 of the server 10 sends lump-sum settlement approval confirmation information including lump-sum settlement amount information to terminal 20B via the communication I / F 14 as information to confirm with the other user (user BB in this example) whether or not he or she approves the lump-sum settlement (S1533).

[0213] The control unit 21 of the terminal 20B determines whether or not lump-sum settlement approval confirmation information has been received from the server 10 via the communication I / F 22 (B150), and if it determines that it has been received (B150: YES), it displays the received lump-sum settlement approval confirmation information on the display unit 24 (B160).

[0214] Thereafter, the control unit 21 of the terminal 20B determines whether or not to approve the lump-sum settlement based on whether or not an input for approving the lump-sum settlement has been made to the input unit (B170). If it is determined to approve (B170: YES), the control unit 21 of the terminal 20B transmits lump-sum settlement approval information indicating approval of the lump-sum settlement to the server 10 via the communication I / F 22 (B180).

[0215] After S1533, the control unit 11 of the server 10 determines whether the lump-sum settlement has been approved by the other user (S1535) based on whether lump-sum settlement approval information has been received from the terminal 20B via the communication I / F 14. If it is determined that the lump-sum settlement has been approved (S1535: YES), the process proceeds to S1540.

[0216] <First process by terminal> The first processing, which is executed by the control unit of the terminal and is based on the first information and the second information, can include, by way of example and without limitation, processing somehow related to a remittance from a user of the proposer (user of the terminal) to a user of the other party (first user, second user) and processing somehow related to the user of the proposer receiving (receiving) an amount remitted from the other party. Not only processing directly related to remittance or receipt of money, but also processing indirectly related to remittance or receipt of money can be included in the first processing.

[0217] By way of example and not limitation, the first process includes at least the following processes: · Processing of transfer requests - Processing to notify the server 10 of the selected remittance request A process of acquiring settlement confirmation information from the server 10 and displaying the information on the display unit 24 A process for requesting the server 10 to execute settlement A process of acquiring settlement result information from the server 10 and displaying the same on the display unit 24 A process of requesting the server 10 to deduct an amount (including offsetting an amount) Requesting server 10 to create a confirmation batch transfer request

[0218] <Input to terminal, etc.> In the above process, the input to the terminal or the input by the user of the terminal is regarded as the operation input to the input unit (operation unit), but this is not limiting.

[0219] As an example and not as a limitation, instead of or in addition to operational input to the input unit (operation unit), sound (including voice) input to the input unit (sound input unit 25) may or may not be possible. The same is true for other inputs to the terminal or by the user of the terminal.

[0220] <Effects of the First Embodiment> According to this embodiment, by way of example and not limitation, multiple remittance requests can be processed in a batch, thereby improving user convenience. In addition, by way of example and not limitation, users can send and receive money up to the limit of their balance, thereby improving user convenience.

[0221] More specifically, in this embodiment, the terminal 20 displays, on at least the display unit 24, remittance request information (not limiting, an example of the first information) regarding a remittance request from a first user (not limiting, an example of the first user) of the terminal 20 of a first user different from the terminal 20 itself to a user of the terminal 20 itself (not limiting, an example of the user of the terminal), or a display (not limiting, an example of the first display) based on first remittance request information (not limiting, an example of the first information) regarding a remittance request from the user of the terminal 20 itself to the first user, and a display (not limiting, an example of the second display) based on second remittance request information between the above-mentioned first user (not limiting, an example of the second user). Terminal 20 is configured to perform a first process (not limited to this, but an example of a first process based on the first information and the second information) based on the first remittance request information and the second remittance request information through control unit 21, based on an input to terminal 20 on which the above-mentioned first display and second display are displayed. As an example of an effect of an embodiment obtained by such a configuration, it becomes possible to process multiple pieces of information related to remittance requests at once based on input to a terminal that displays a first display based on first information related to a remittance request from a first user to a user of the terminal, or from the user of the terminal to the first user, and a second display based on second information related to a remittance request from a second user to a user of the terminal, or from the user of the terminal to the second user, thereby improving user convenience.

[0222] In addition, this embodiment shows a configuration in which the first remittance request information includes information regarding a remittance request from a counterpart user to a user of one's own terminal 20 (not limited to this, but an example of information regarding a remittance request from a first user to a user of a terminal), and the second remittance request information includes information regarding a remittance request from a user of one's own terminal 20 to a counterpart user (not limited to this, but an example of information regarding a remittance request from a user of a terminal to a second user). As an example of the effect of the embodiment obtained by such a configuration, the above-mentioned batch processing can be used to send to the first user or to be sent from the second user the difference between the amount sent by the user of the terminal to the first user (the amount paid by the user of the terminal) and the amount sent by the user of the terminal from the second user (the amount received by the user of the terminal), for example and not by way of limitation. In this case, the amount sent or received is smaller (the absolute value of the difference is smaller) than when multiple pieces of information related to a remittance request are processed one by one. Therefore, as one effect and not by way of limitation, it is more likely that the processing can be performed within the user's balance, and the user does not need to go through the trouble of recharging or taking a loan to send money. In addition, as one effect and not by way of limitation, since multiple pieces of information can be processed in a batch, an increase in the number of cases to be processed can be expected.

[0223] In addition, this embodiment illustrates a configuration in which the first remittance request information includes information on a first remittance request amount (not limiting, an example of a first amount related to a remittance), and the second remittance request information includes information on a second remittance request amount (not limiting, an example of a second amount related to a remittance). As an example of the effect of the embodiment obtained by such a configuration, the first amount related to the remittance and the second amount related to the remittance can be notified to the user of the terminal by the first display and the second display.

[0224] In this embodiment, the first process includes a process based on the first remittance request amount and the second remittance request amount. As an example of an effect of an embodiment obtained by such a configuration, by way of example and not limitation, it becomes possible to carry out processing such as lump-sum settlement based on the amount of the difference between the first amount and the second amount.

[0225] In this embodiment, the terminal 20 transmits lump-sum settlement confirmation information based on the second remittance request information to the terminal 20 of the first user (not limited to this, but an example of the terminal of the second user) via the server 10 through the communication I / F 22. In this case, the first process is configured to be executed by the control unit 21 based on approval of the execution of the first process by the first user based on the lump-sum settlement confirmation information. As an example of the effect of the embodiment obtained by such a configuration, the first process can be executed if the other party approves it. Also, as a non-limiting example, if the other party does not approve it, the first process can be not executed.

[0226] Moreover, this embodiment shows a configuration in which the second user is the first user. As an example of an effect of an embodiment obtained by such a configuration, the first process can be executed based on information regarding multiple remittance requests between a single user (first user) other than the user of the terminal 20.

[0227] In addition, in this embodiment, the first process is configured to include a process of transferring an amount obtained by subtracting the first remittance request amount from the second remittance request amount (this is an example of a third amount, but is not limited to this) to the first user when the second remittance request amount is greater than the first remittance request amount. As an example of an effect of an embodiment obtained by such a configuration, since the difference between the second amount and the first amount can be transferred to the first user, the amount to be paid can be made smaller than when transferring money based on a single piece of information, thereby improving user convenience.

[0228] Furthermore, this embodiment illustrates a configuration in which the first remittance request information (not limiting, an example of the first information) includes information on the first remittance request amount (not limiting, an example of the first amount), the second remittance request information (not limiting, an example of the second information) includes information on the second remittance request amount (not limiting, an example of the second amount), and the first process is performed by the control unit 21 based on the first remittance request amount, the second remittance request amount, and the electronic money account balance of the user of the terminal 20 (not limiting, an example of the balance of the terminal user). As an example of an effect of an embodiment obtained by such a configuration, a first process based on a first amount and a second amount can be executed taking into account the balance of the user of the terminal, so that, by way of example and not limitation, the first process can be executed when the balance of the user of the terminal is sufficient, but the first process can be prevented from being executed when the balance of the user of the terminal is insufficient.

[0229] In addition, this embodiment shows a configuration in which the first process is executed based on an operation of the user of one's own terminal 20 on the proposal button (not a limitation, but an example of an input to the fifth display) and approval of the other user regarding lump-sum settlement (not a limitation, but an example of approval of the first user or the second user regarding the execution of the first process). As an example of an effect of an embodiment obtained by such a configuration, the first process can be prevented from being executed without not only input by the user of the terminal to the fifth display, but also approval of the first user or the second user regarding the execution of the first process.

[0230] Furthermore, this embodiment illustrates a configuration in which the first process is executed based on the proposer's user's electronic money account balance (not limited to, but an example of the balance of a terminal user) and the other party's user's electronic money account balance (not limited to, but an example of the balance of a first user or a second user). As an example of an effect of an embodiment obtained by such a configuration, the first process can be executed taking into consideration not only the balance of the user of the terminal, but also the balance of the first user or the second user, so that, by way of example and not of limitation, the first process is executed when the balance of the first user or the second user is sufficient, but the first process is not executed when the balance of the first user or the second user is insufficient.

[0231] Furthermore, in this embodiment, the first process is configured to include processing based on the first remittance request information and the second remittance request information, based on input to the terminal 20 by the user of the proposer, from among a plurality of remittance request information related to the user of the proposer, including the first remittance request information and the second remittance request information (an example of a plurality of pieces of information related to a remittance request to or by the user of the terminal, including at least the first information and the second information, but not limited to the first information and the second information). As an example of an effect of an embodiment obtained by such a configuration, the first information and the second information can be appropriately processed based on input by the user of the terminal to the terminal from a remittance request to the user of the terminal or a plurality of pieces of information related to a remittance request by the user of the terminal, which includes at least the first information and the second information.

[0232] In addition, this embodiment shows a configuration in which the other user is one user (not limited to this, but is an example of the second user being the first user), and the first process includes a process related to a transfer of money from the other user to the proposer's user, or a process related to a transfer of money from the proposer's user to the other user. As an example of the effect of an embodiment obtained by such a configuration, it is possible to realize a remittance from the first user to the user of the terminal, or a remittance from the user of the terminal to the first user, based on multiple pieces of information regarding a remittance request, with the same single user (first user = second user) as the other user.

[0233] In addition, in this embodiment, the above-mentioned remittance-related processing is configured to include processing for displaying lump-sum settlement confirmation information and lump-sum settlement result information (which are not limited to the above, but are examples of information indicating that processing of a remittance request based on the first information and processing of a remittance request based on the second information have been executed) on the display unit 24. As an example of the effect of the embodiment obtained by such a configuration, it is possible to inform the user of the terminal that the remittance request based on the first information and the remittance request based on the second information have been processed.

[0234] <First Modification (1)> As described above, the method of the above embodiment can be similarly applied to the case where the other users are different users.

[0235] Fig. 1-23 is a diagram showing an example of a remittance request list screen displayed on the display unit 24 of the terminal 20 in this modified example. This screen is an example of a remittance request list screen displayed on the display unit 24 of the terminal 20A, and is an example, by way of example and not limitation, of a screen displayed when the remittance request list icon is tapped on the main menu screen of Fig. 1-9.

[0236] The current location display area CLR1 displays the words "Remittance Request List," which indicates that remittance request list information is being displayed. Below the current location display area CLR1, pending requests transmitted to and received from users of different terminals 20 are displayed, by way of example and not limitation, in chronological order from the top to the bottom starting from the oldest remittance request. In this example, from the top, a received remittance request from user BB, a received remittance request from user CC, a received remittance request from user BB, a received remittance request from user CC, a received remittance request from user DD, a remittance request sent to user CC, ... are displayed.

[0237] Next to each remittance request is a check area SR2 that can be turned "ON / OFF" by tapping. By turning the check "ON", a check mark is displayed in the check area SR2, allowing the remittance request between the user and the requester to be selected for lump-sum settlement.

[0238] In this example, a received remittance request (payment of 2,000 yen) from the first user BB and a received remittance request (payment of 1,000 yen) from the fourth user CC are shown to be selected. When the settlement button BT5 at the bottom of the screen is tapped in this state, settlement request information for requesting lump-sum settlement of the two selected remittance requests is transmitted from the terminal 20A to the server 10.

[0239] In this example, the transfer (payment) is from user AA to user BB, and the transfer (payment) is from user CC to user CC, and there is no transfer (receipt) from the other users, so approval from the other users is not required. Then, a lump sum settlement is executed by the server 10, and a remittance (payment) of "2,000 yen" from user AA to user BB and a remittance (payment) of "1,000 yen" from user AA to user CC are realized.

[0240] This modification illustrates a configuration in which the first user is a different user than the second user. As an example of the effect of the modified example obtained by such a configuration, the first process can be executed based on information regarding multiple remittance requests between at least two users (a first user and a second user different from the second user) other than the user of the terminal 20.

[0241] <First Modification (2)> In the first embodiment, the proposer user manually selects the remittance requests to be subject to lump-sum settlement, but the present invention is not limited to this. The terminal 20 of the user who proposes the transaction or the server 10 may or may not automatically select the remittance requests to be subject to lump-sum settlement. This automatic selection of remittance requests to be subject to lump-sum settlement by the terminal 20 of the proposer's user or the server 10 also includes the meaning of proposing (suggesting) the selected remittance requests to the proposer's user.

[0242] Specifically, the control unit 21 of the proposer's terminal 20 performs a process of inquiring of the server 10 about the current electronic money account balance of the proposer's user. Then, the control unit 21 of the proposer's terminal 20 selects one or more remittance requests from among the remittance requests included in the remittance request list information received from the server 10, based on the amount of each remittance request and the type of each remittance request (received remittance request (payment) / sent remittance request (receive)), by way of example and not limitation, such that the current electronic money account balance of the proposer's user is the upper limit of the payment amount. In other words, one or more remittance requests are selected within a range that does not cause the current electronic money account balance of the proposer's user to become negative.

[0243] When the control unit 11 of the server 10 selects a remittance request, the control unit 11 may carry out a similar process based on the data of the remittance request stored in the first remittance request management data 157A.

[0244] This modified example shows a configuration in which the first process selects at least first remittance request information and second remittance request information from multiple pieces of remittance request information (not limited to, one example of multiple pieces of information) based on the proposer's user's electronic money account balance (not limited to, one example of the terminal user's balance), and includes processing based at least on this first remittance request information and second remittance request information. As an example of the effect of the embodiment obtained by such a configuration, at least the first information and the second information among the multiple pieces of information can be automatically selected in consideration of the balance of the user of the terminal, and settlement can be performed. In this case, the user of the terminal does not need to manually select the information, and therefore the convenience of the user can be improved.

[0245] <First Modification (3)> The user interface of the display screen shown in the <Display Screen> of the first embodiment is merely an example, and is not limited to this.

[0246] Fig. 1-24 is a diagram showing another example of a UI (user interface) of a display screen displayed on the display unit 24 of the terminal 20. This display screen is an example of a remittance request list screen displayed on the display unit 24 of the terminal 20A, and shows another example of the remittance request list screen corresponding to Fig. 1-12. In this display screen, received remittance requests and sent remittance requests are displayed in a table format as a list of remittance requests to and from user CC. In this example, the left column of the table displays a list of received remittance requests, and the right column of the table displays a list of sent remittance requests.

[0247] For each of the lists of received remittance requests and sent remittance requests, the display field for each remittance request displays information such as the received date / time / sent date / time, the reason for payment, the request type (payment / receipt), and the amount of the remittance request.

[0248] By displaying the remittance requests in this manner, it becomes possible to compare the received remittance requests with the sent remittance requests, thereby improving the convenience for the user.

[0249] In the above embodiment, the unprocessed remittance requests are displayed on the remittance request list screen, but the present invention is not limited to this. In addition, by way of example and not limitation, a list of pending remittance requests may or may not be available for viewing from a screen such as a notification screen of the payment application, a profile screen of the payment application, or a home page of the payment application.

[0250] <First Modification (4)> In the above embodiment, the case where approval of the other user is required for lump-sum settlement has been described. However, if the system is configured so that a remittance request cannot be created based on a user's operation, approval of the other user may not be required.

[0251] One possible example of such a system is a system that links and manages a user's electronic money or electronic payment with a remittance request. More specifically, a system is possible in which, after one user makes an electronic payment using electronic money, at least a portion of the payment amount can be charged to another user via a remittance request as an advance (advance amount). One possible use of this system is, by way of example and not limitation, when multiple users split the bill.

[0252] In this case, the server 10 can create a remittance request in which the advance payment amount is set as the remittance request amount according to a user operation after performing electronic settlement, and transmit the remittance request to the terminal 20 of the other user.

[0253] In such a system, a user who wishes to settle a lump sum payment must first consume his or her electronic money account balance to make the electronic payment, thereby minimizing the risk that the lump sum processing will be misused.

[0254] <First Modification (5)> When making a lump-sum settlement, a settlement proposal proposed to one user by another user to make a payment (a settlement proposal in which one user needs to make a payment to the other user) may be treated as a new remittance request requested by the other user to send money, and this new remittance request may be managed on the server 10 side as an unprocessed received remittance request of the one user.

[0255] Specifically, as an example and not by way of limitation, in the example of Figure 1-13, a settlement proposal in which user CC (one user) is suggested to make a payment of "7,000 yen" by user AA (the other user) may be treated as a new remittance request requested by user AA to remit "7,000 yen", and this remittance request may be managed on the server 10 side as an unprocessed received remittance request for user CC's "payment 7,000 yen".

[0256] Furthermore, as a non-limiting example, on a remittance request list screen displayed on display unit 24 of terminal 20, when a newly created received remittance request is tapped, information about the remittance request that contributed to the creation of the received remittance request (the remittance request that caused the creation of the received remittance request) (as a non-limiting example, detailed information such as the type of remittance request, the remittance request amount, date and time, and reason) can be displayed hierarchically along the time axis, thereby enabling the user to trace the history of a single remittance request.

[0257] Specifically, when the unprocessed received remittance request "Payment 7,000 yen" of the above user CC is tapped, information about each of the remittance requests that contributed to the creation of this received remittance request, such as, but not limited to, the third received remittance request "Payment 10,000 yen" and the fourth sent remittance request "Receive 3,000 yen" in the example of Figure 1-14, may be displayed. This technique can also be applied to previously sent remittance requests.

[0258] <First Modification (6)> In the first embodiment, the first user and the second user are described as general users of the terminal 20, but the present invention is not limited to this. At least one of the first user and the second user may or may not be a user of a business such as a store, rather than a general user. In this case, the business may include, but is not limited to, a business (store) that is expected to request money from the user of the terminal 20 by making a remittance request, such as a business that sells products (including the provision of services) or a business that operates a money lending business.

[0259] In this case, in the above embodiment, these businesses obtain an account for the payment service (payment application), and can use this account to transmit remittance request information and remittance reminder information to the terminal 20 of the user to whom money is to be billed (remittance request destination user) via the server 10.

[0260] The account acquired by the business (store) may be a general account, which is an account for the user of the terminal 20, or may be an account for the business.

[0261] In this modified example, at least one of the first user and the second user is a shop that sells the product related to the remittance request. As an example of the effect of this modified example obtained by such a configuration, not only general users but also users at shops can be made users who can make remittance requests to users of terminals.

[0262] <First Modification (7)> It is assumed that some users of terminal 20 may feel awkward and hesitate to propose lump-sum settlement to the other user. For example and without limitation, this may be the case when the other user is a senior or a close friend.

[0263] Therefore, instead of the user of the terminal 20, the user who makes the collective proposal may be a user who uses a business account. A business account is, by way of example and not limitation, a user who has an official account (hereinafter referred to as an "official account" and, where appropriate, expressed as an "OA: Official Account") in the service (the payment service in the above example).

[0264] As an example, a user with an official account may be, by way of example and not limitation, a payment service provider or a messaging service provider. In this case, the server 10 can transmit lump-sum settlement approval confirmation information to the terminal 20 of the other user, treating the user who proposed the lump-sum settlement as a payment service provider or messaging service provider.

[0265] This modified example shows a configuration in which the user who proposes lump-sum settlement is a user who uses an official account (not limited to this, but is an example of a business account). As an example of the effect of this modified example obtained by such a configuration, a user using a business account can be allowed to request lump-sum settlement on behalf of the user who wishes to settle the bill in one lump sum, thereby improving user convenience.

[0266] <Second Example> The second embodiment is an embodiment relating to a process when the user's balance is insufficient in the lump-sum settlement described in the first embodiment. The contents described in the second embodiment are applicable 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.

[0267] <Display screen> FIG. 2-1 is a diagram showing an example of a remittance request list screen displayed on the display unit 24 of the terminal 20 in this embodiment. This remittance request list screen is a screen displayed on the display unit 24 of the terminal 20A of the user AA, and is a screen listing remittance requests addressed to the user BB. The current location display area CLR1 at the top of the screen displays the words "Remittance request with BB," indicating that an unprocessed request between user BB and the user is being displayed.

[0268] Below the current location display area CLR1, a list of remittance requests addressed to user BB is displayed. In this example, the first received remittance request, the second received remittance request, and the fourth sent remittance request are selected, and the change in the user's (user AA's) electronic money account balance is shown in the settlement details confirmation area ACR3 in the electronic money account balance display area WBR2 at the bottom of the screen. In this example, the user's current electronic money account balance is "500 yen," and it is shown that the user's electronic money account balance will become "0 yen" after lump-sum settlement. In this case, the balance is sufficient, so lump-sum settlement is possible.

[0269] In addition, to the right of the words "Wallet Balance" in the electronic money account balance display area WBR2, a charge button, indicated by a plus icon in a circle, for charging the wallet balance is also displayed.

[0270] FIG. 2-2 shows a remittance request list screen similar to that of FIG. 2-1, but with a different remittance request selected. In this example, in addition to the first received remittance request, the second received remittance request, and the fourth sent remittance request, the third received remittance request is selected, and the change in the user's (user AA's) electronic money account balance is shown in settlement content confirmation area ACR4 in electronic money account balance display area WBR2 at the bottom of the screen. In this example, the user's current electronic money account balance is "500 yen," and it is shown that the lump-sum settlement will result in the user's electronic money account balance being "-500 yen." In this example, the payment is "1000 yen," while the user's current electronic money account balance is "500 yen," meaning that there is a shortfall of "500 yen," and lump-sum settlement is not possible.

[0271] In this case, the text "Insufficient balance!" is displayed in the settlement details confirmation area ACR4 along with a warning mark as insufficient balance information indicating that the electronic money account balance is insufficient. When the suggestion button BT6 is tapped in this state, the display shown in Figure 2-3 is displayed.

[0272] In Figure 2-3, charge confirmation information CG1 is displayed as a pop-up in the center of the remittance request list screen in Figure 2-2 as information for confirming with the user whether or not to charge the balance of the electronic money account. Specifically, along with the text "Do you want to charge the 500 yen shortfall?", an OK button for confirming the charge and a Cancel button for canceling the charge are displayed.

[0273] When the OK button is tapped in this state, the server 10 executes a charge process to charge "500 yen" to the balance of the electronic money account of the user AA. Then, a lump sum settlement is performed.

[0274] <Processing> 2-4 and 2-5 are flow charts showing an example of the flow of a third settlement process which is an example of the settlement process executed by the control unit 11 of the server 10 in this embodiment. If it is determined in S1520 that the electronic money account balance of any user will be negative (S1520: YES), the control unit 11 of the server 10 determines whether or not the user whose electronic money account balance will be negative is the user of the proposer (S1550). If it is determined that the user is the user of the proposer (S1550: YES), the control unit 11 of the server 10 transmits lump-sum settlement confirmation information including, by way of example and not limitation, lump-sum settlement amount information and insufficient balance information to the terminal 20A via the communication I / F 14 (S1551).

[0275] Thereafter, the control unit 11 of the server 10 judges whether or not a request to execute lump-sum settlement has been made based on whether or not settlement execution request information has been received from the terminal 20A via the communication I / F 14 (S1553). If it is judged that a request has been made (S1553: YES), the control unit 11 of the server 10 judges whether or not to charge the balance of the electronic money account of the user AA (S1555). Specifically, by way of example and not limitation, the control unit 11 of the server 10 transmits the charge confirmation information described above to the terminal 20A and causes it to be displayed on the display unit 24, and judges whether or not information for approving the charge has been received from the terminal 20A.

[0276] If it is determined that recharge is to be performed (S1555: YES), the control unit 11 of the server 10 executes a recharge process (S1557). Specifically, a process is executed to replenish the shortfall in the lump-sum settlement to the balance of the electronic money account of the user AA using the bank account or credit card of the user AA that has been registered in advance. Then, the control unit 11 of the server 10 proceeds to S1531.

[0277] On the other hand, if it is determined that the user whose electronic money account balance will become negative is not the proposer's user, that is, that the user whose electronic money account balance will become negative is the other party's user (S1550: NO), the control unit 11 of the server 10 sends lump-sum settlement confirmation information including lump-sum settlement amount information to the terminal 20A via the communication I / F 14 (S1559).

[0278] Thereafter, if it is determined that a request to execute a lump-sum settlement has been made from terminal 20A (S1561: YES), the control unit 11 of the server 10 sends lump-sum settlement approval confirmation information, including lump-sum settlement amount information and insufficient balance information, to terminal 20B via the communication I / F 14 (S1563).

[0279] Thereafter, the control unit 11 of the server 10 determines whether or not the lump-sum settlement has been approved based on whether or not lump-sum settlement approval information has been received from the terminal 20B via the communication I / F 14 (S1565).

[0280] If it is determined that the lump sum settlement has been approved (S1565: YES), the control unit 11 of the server 10 determines whether or not to charge the balance of the electronic money account of the user BB (S1567). Specifically, as a non-limiting example, the control unit 11 transmits the above-mentioned charge confirmation information to the terminal 20B and causes it to be displayed on the display unit 24, and determines whether or not information for approving the charge has been received from the terminal 20B.

[0281] If it is determined that recharge is to be performed (S1567: YES), the control unit 11 of the server 10 executes a recharge process (S1569). Specifically, the control unit 11 executes a process of replenishing the shortfall in the lump-sum settlement to the balance of the electronic money account of the user BB using the bank account or credit card of the user BB that has been registered in advance. Then, the control unit 11 of the server 10 advances the process to S1540.

[0282] If it is determined in S1553 that execution of lump-sum settlement has not been requested (S1553: NO), or if it is determined in S1555 that charging will not be performed (S1555: NO), the control unit 11 of the server 10 ends the third settlement process.

[0283] In addition, if it is determined in S1561 that lump-sum settlement has not been requested (S1561: NO), if it is determined in S1565 that lump-sum settlement has not been approved (S1565: NO), or if it is determined in S1567 that charging will not be performed (S1567: NO), the control unit 11 of the server 10 terminates the third settlement process.

[0284] Before executing the process of S1540, a process similar to S1520 may be executed again, and if it is determined that the balance of any user's electronic money account will become negative, the process of S1540 may be suspended, or it may not be suspended.

[0285] <Effects of the second embodiment> In this embodiment, the first remittance request information (not limiting, an example of the first information) includes information on the first remittance request amount (not limiting, an example of the first amount), the second remittance request information (not limiting, an example of the second information) includes information on the second remittance request amount (not limiting, an example of the second amount), and the first process is performed by the control unit 21 based on the first remittance request amount, the second remittance request amount, and the electronic money account balance of the user of the terminal 20 (not limiting, an example of the balance of the terminal user). As an example of an effect of the embodiment obtained by such a configuration, the first process can be appropriately executed based on the first amount and the second amount, taking into consideration the balance of the user of the terminal.

[0286] Furthermore, this embodiment illustrates a configuration in which, when the sum of the first remittance request amount and the second remittance request amount exceeds the balance of the electronic money account of the user of one's own terminal 20 and the user of one's own terminal 20 makes a remittance, a display of insufficient balance information (not limited to this, but an example of a third display indicating that the first process cannot be executed) is displayed on the display unit 24 of one's own terminal 20. As an example of an effect of an embodiment obtained by such a configuration, in a case where the sum of the first amount and the second amount exceeds the terminal user's balance but the terminal user attempts to transfer money, the terminal user can be notified that the first process cannot be executed.

[0287] Furthermore, this embodiment illustrates a configuration in which, when the sum of the first remittance request amount and the second remittance request amount exceeds the electronic money account balance of the user of one's own terminal 20 and a remittance is made from the user of one's own terminal 20, a display of confirmation information for charging the electronic money account balance of the user of one's own terminal 20 (not limiting, an example of a fourth display indicating that the balance will be charged) is displayed on the display unit 24 of one's own terminal 20. As an example of the effect of an embodiment obtained by such a configuration, in a case where the sum of the first amount and the second amount exceeds the terminal user's balance but the terminal user is about to transfer money, the terminal user can be informed that it is possible to top up the balance to make up for the shortfall.

[0288] <Second Modification> In the second embodiment, by way of example and not limitation, when the terminal 20 displays a remittance request list screen on the display unit 24, it may or may not display on the display unit 24 information indicating that one's electronic money account balance can be topped up (top-up information) and information indicating that a loan (financing) can be made (loan information).

[0289] The business entity that provides the loan may be, by way of example and not limitation, a payment service business (payment application business) / messaging service business (messaging application business) or a financial institution such as a bank.

[0290] In this case, based on the input of the user requesting a loan, the server 10 can provide a loan in the form of electronic money (using electronic money as a means) within a certain loan amount. Alternatively, the server 10 can communicate with a server of an affiliated financial institution to request a loan and have the loan approved. In this case, the balance of the electronic money account may be treated as either a negative or positive value.

[0291] Once the loan has been settled, by way of example and not limitation, the user may be prompted to repay the loan amount by a set repayment deadline. In this case, the repayment method may be the same as that for a general loan.

[0292] This modified example illustrates a configuration in which the terminal 20 displays, on the display unit 24, a display based on the first remittance request information (not limiting, an example of a first display), a display based on the second remittance request information (not limiting, an example of a second display), a display of charge information (not limiting, an example of a display related to charging a balance), or loan information (not limiting, an example of a display related to making a loan). As an example of the effect of the modified example obtained by such a configuration, when displaying a first display based on the first information and a second display based on the second information, a display regarding topping up the balance or taking out a loan can be displayed together, enabling the user to easily top up the balance or take out a loan.

[0293] <Third Example> The third embodiment is related to the second embodiment and is an embodiment in which the display mode of the display related to the execution of lump-sum settlement is changed. The contents described in the third embodiment are applicable 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.

[0294] <Display screen> FIG. 3-1 is a diagram showing an example of a remittance request list screen displayed on the display unit 24 of the terminal 20 in this embodiment. This remittance request list screen corresponds to the screen shown in FIG. 2-1 displayed on the display unit 24 of the terminal 20A of the user AA, and is displayed when the balance in the electronic money account of the user AA is sufficient.

[0295] The settlement details confirmation area ACR5 at the bottom of the screen indicates that the balance of one's electronic money account will become "0 yen" if the payment is settled in a lump sum, but that lump sum settlement is possible. In this case, when an operation (tap) is performed on the proposal button BT7, the terminal 20A accepts the operation of proposing the lump-sum settlement.

[0296] FIG. 3-2 is a diagram showing another example of a remittance request list screen displayed on the display unit 24 of the terminal 20 in this embodiment. This remittance request list screen corresponds to the screen shown in FIG. 2-2 displayed on the display unit 24 of the terminal 20A of the user AA, and is displayed when the balance in the electronic money account of the user AA is insufficient. In this screen, the proposal button BT7 displayed in the settlement content confirmation area ACR5 at the bottom of the screen is displayed in a different display mode from that in Fig. 3-1, based on the fact that the balance of the electronic money account of the user AA is insufficient. Specifically, by way of example and not limitation, the proposal button BT7 is displayed grayed out, and even if an operation (tap) is performed on the proposal button BT7, the terminal 20A will not accept the operation.

[0297] In FIG. 3-2, a charge button for the electronic money account may be displayed in the electronic money account balance display area WBR1 to prompt the user to charge the account, but this is not essential. In addition, if the company that operates the payment service has a partnership with a financial institution, it may or may not display a loan function button to obtain a loan from the financial institution and charge an electronic money account.

[0298] <Effects of the third embodiment> In this embodiment, the terminal 20 displays a suggestion button (not limited to this, but an example of the fifth display related to the execution of the first process) on the display unit 24. In this case, the suggestion button is configured to change its display mode based on the first remittance request amount, the second remittance request amount, and the user's electronic money account balance. As an example of an effect of an embodiment obtained by such a configuration, the display manner of the fifth display regarding the execution of the first process is changed based on the first amount, the second amount, and the balance of the user of the terminal, so that, by way of example and not limitation, the user of the terminal can be simply and appropriately notified that the first process cannot be executed, taking into account the balance of the user of the terminal.

[0299] Furthermore, in this embodiment, when the sum of the first remittance request amount and the second remittance request amount exceeds the balance of the electronic money account of the user of the user's terminal 20 and remittance is made by the user of the user's terminal 20, the suggested button is displayed on the display unit 24 of the user's terminal 20 in a display mode indicating that the operation is not accepted (this is not limiting, but is an example of a display mode indicating that the first process cannot be executed). As an example of an effect of an embodiment obtained by such a configuration, in a case where the user of the terminal attempts to transfer money even though the sum of the first amount and the second amount exceeds the terminal user's balance, the user of the terminal can be informed that the first process cannot be executed.

[0300] <Fourth Example> The fourth embodiment is an embodiment relating to a processing method (algorithm) for lump-sum settlement. The contents described in the fourth embodiment are applicable 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.

[0301] <Processing> The bulk settlement performed by the server 10 may include, by way of example and not limitation, the following two schemes. (1) Batch settlement (2) Sequential settlement

[0302] (1) Batch settlement is, by way of example and not limitation, a method of batch settlement in which two or more selected remittance requests are processed at once. In this method, the control unit 11 of the server 10 calculates the final lump sum settlement amount based on the remittance request amount of each selected remittance request and its type (received remittance request / sent remittance request). In this case, even if settlement is made based on the calculated lump-sum settlement amount, if the balance of the electronic money account of the user of the proposer's terminal 20 and the balance of the electronic money account of the other user do not both become negative, settlement is deemed to be OK. On the other hand, if settlement based on the calculated lump-sum settlement amount results in a negative balance in either the electronic money account of the user of the proposer's terminal 20 or the electronic money account of the other user, settlement is not allowed.

[0303] (2) Sequential settlement is, by way of example and not limitation, a method of batch settlement in which two or more selected remittance requests are processed sequentially. In this method, the control unit 11 of the server 10 repeats sequential processing for two or more selected remittance requests, including calculating the settlement amount and updating the electronic money account balance of the proposer's user and the electronic money account balance of the recipient user, based on the amount of each remittance request and its type (received remittance request / sent remittance request). If either the balance of the electronic money account of the user of the terminal 20 of the proposer or the balance of the electronic money account of the recipient user becomes negative during the sequential processing, the settlement in that order is rejected. Then, the order of processing the remittance requests is changed and the sequential processing is performed again from the beginning. On the other hand, if, as a result of sequential processing up to the final remittance request, at least one of the balance of the electronic money account of the user of the proposer's terminal 20 and the balance of the electronic money account of the other user is not negative, settlement is deemed OK and settlement is carried out in that order.

[0304] Even if a brute force approach is taken by changing the order in which remittance requests are processed, if either the balance of the electronic money account of the user of the proposer's terminal 20 or the balance of the electronic money account of the recipient user becomes negative during sequential processing, sequential settlement cannot be performed, and settlement can be denied.

[0305] <Display screen> The difference between batch settlement and sequential settlement will be described with reference to the example of FIG. 3-1 described above. Here, the following two cases are considered. (Case 1) User AA's current electronic money account balance = 500 yen, User BB's current electronic money account balance = 1,500 yen (Case 2) User AA's current electronic money account balance = 500 yen, User BB's current electronic money account balance = 1,000 yen

[0306] First, (Case 1) will be explained. (1) When installment payment is applied When batch settlement is applied, the first received remittance request, the second received remittance request, and the fourth sent remittance request selected in Figure 3-1 will be processed simultaneously. In this case, the lump sum settlement will be "Payment 2,000 yen", "Payment 500 yen", and "Received 2,000 yen", totalling "Payment 500 yen" (a payment of 500 yen from user AA to user BB). The current balance of user AA's electronic money account is "500 yen," and since user AA's balance cannot be negative, if an instalment is made, settlement can be made regardless of user BB's electronic money account balance.

[0307] (2) When progressive settlement is applied When sequential settlement is applied, the first received remittance request, the second received remittance request, and the fourth sent remittance request selected in Figure 3-1 will be processed one by one. By way of example and not limitation, consider the case where the second received remittance request is processed first, followed by the fourth sent remittance request, followed by the first received remittance request.

[0308] First, the second received remittance request is a payment of "500 yen" from user AA to user BB, so when this settlement is made, the balance of user AA's electronic money account will change from "500 yen to 0 yen," and the balance of user BB's electronic money account will change from "1,500 yen to 2,000 yen."

[0309] Next, the fourth sent remittance request is for user AA to receive 2,000 yen from user BB, so when this settlement is made, the balance in user AA's electronic money account will change from 0 yen to 2,000 yen, and the balance in user BB's electronic money account will change from 2,000 yen to 0 yen.

[0310] Finally, since the first received remittance request is a payment of "2,000 yen" from user AA to user BB, when this settlement is made, the balance of user AA's electronic money account will change from "2,000 yen to 0 yen", and the balance of user BB's electronic money account will change from "0 yen to 2,000 yen".

[0311] Since the current balance of user BB's electronic money account is "1,500 yen," as a result of the above settlement, user BB will receive "500 yen" from user AA. In this example, since neither the balance of user AA's electronic money account nor the balance of user BB's electronic money account is negative, settlement is possible even by sequential settlement.

[0312] Next, (Case 2) will be explained. (1) When installment payment is applied When batch settlement is applied, the procedure is the same as (Case 1). In other words, the current balance of user AA's electronic money account is "500 yen," and since user AA's balance cannot be negative, if an instalment is made, settlement can be made regardless of user BB's electronic money account balance.

[0313] (2) When progressive settlement is applied When sequential settlement is applied, as in Case 2, the first received remittance request, the second received remittance request, and the fourth sent remittance request selected in Figure 3-1 will be processed one by one. However, in (Case 2), unlike (Case 1), because the current electronic money account balance of user BB is 1,000 yen, no matter in what order the first received remittance request, the second received remittance request, and the fourth sent remittance request selected in Figure 3-1 are processed, it is not possible to settle the electronic money account balance of user AA and the electronic money account balance with user BB so that they do not become negative.

[0314] From the above, in (Case 1), settlement is possible through either lump-sum settlement or successive settlement, but in (Case 2), settlement through lump-sum settlement is possible but successive settlement is not possible.

[0315] In both of the above cases, by way of example and not limitation, if the operator of the payment service is affiliated with a financial institution, it may or may not allow settlement by temporarily allowing a shortfall in the user's electronic money account balance to be counted as a negative value in the account balance.

[0316] FIG. 4-1 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20B when successive settlement is applied in the above (Case 1). A current location display area CLR3 is configured at the top of the notification screen, and displays the word "Notice" to indicate that a notification about a payment application is being displayed. In the notice information display area NTR3 below the current location display area CLR3, lump-sum settlement approval confirmation information transmitted from the server 10 to the terminal 20B based on the proposal from the user AA is displayed. In (Case 1), since settlement by successive settlement is possible, the settlement button BT8 included in the lump-sum settlement approval confirmation information is displayed in a state where it is ready to accept an operation.

[0317] In contrast, FIG. 4-2 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20B when successive settlement is applied in the above (Case 2). The information displayed on this notification screen is the same as that shown in Figure 4-1, however, since successive settlement is not possible in (Case 2), the settlement button BT8 included in the lump-sum settlement approval confirmation information is displayed grayed out, and even if an operation (tap) is performed on the settlement button, terminal 20B will not accept the operation.

[0318] <Fifth Example> The fifth embodiment is an embodiment related to the "request offset" of the batch processing described above. The contents described in the fifth embodiment are applicable 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.

[0319] As mentioned above, if the remittance request amount (amount to be remitted) of the selected received remittance request and the remittance request amount (amount to be received) of the selected sent remittance request are the same amount, it is possible to offset the amounts through a lump sum settlement.

[0320] However, in such a case, it is also possible to offset the requests instead of making a lump sum settlement. By way of example and not limitation, request offsetting means cancelling out remittance requests selected for processing against each other, eliminating those remittance requests, and deleting the data for those remittance requests.

[0321] <Display screen> 5-1 is a diagram showing an example of a remittance request list screen displayed on the display unit 24 of the terminal 20A of the user AA in this embodiment. This remittance request list screen is a screen in which the other user is the user BB. This remittance request list screen shows the first received remittance request (payment 2,000 yen) and the fourth sent remittance request (received 2,000 yen) in a selected state.

[0322] The settlement details confirmation area ACR6 at the bottom of the screen displays user AA's current electronic money account balance and user AA's post-settlement electronic money account balance. When lump-sum settlement is performed based on the two selected remittance requests, the amounts are offset. Therefore, in this example, user AA's current electronic money account balance and user AA's post-settlement electronic money account balance are the same amount (500 yen).

[0323] Also, below that is the text "Would you like to propose offsetting the request?" along with a propose button and a cancel button. By way of example and not limitation, when the suggest button is tapped, information for requesting a request offset is sent from the terminal 20A to the server 10. Then, the request offset process is executed by the server 10, and the data of the two selected remittance requests is deleted.

[0324] <Processing> (1) An example of processing FIG. 5-2 is a flowchart showing an example of the flow of processes executed by each device in this embodiment. If it is determined in S140 that the request selection information has been received from the terminal 20A (S140: YES), the control unit 11 of the server 10 executes a request cancellation process (S350).

[0325] In the request offset process, the control unit 11 of the server 10 calculates a lump sum settlement amount based on the remittance request selected by the terminal 20A, and determines whether the remittance request can be offset based on the calculated lump sum settlement amount. If it is determined that the remittance request can be offset, the control unit 11 of the server 10 transmits request offset confirmation information to the terminal 20A.

[0326] In the terminal 20A, request offset confirmation information is displayed on the display unit 24 (A350), and when it is determined that a request for executing request offset is to be made based on input on this display (A360: YES), request offset execution request information is transmitted from the terminal 20A to the server 10 (A370).

[0327] The control unit 11 of the server 10 executes the request offset based on the request offset execution request information received from the terminal 20A. Specifically, the control unit 11 deletes the data of the remittance request to be offset from the first remittance request management data 157A. It is also possible to set the remittance completion flag of the remittance request to be offset to "ON" without deleting the remittance request data. Then, the control unit 11 of the server 10 ends the request offset process.

[0328] Thereafter, the control unit 11 of the server 10 judges whether the request offset result is "OK" or not (S370). If it is judged to be "OK" (S370: YES), the control unit 11 of the server 10 transmits the request offset result information to the terminal 20A and the terminal 20B via the communication I / F 14 (S390). Then, the control unit 11 of the server 10 ends the process.

[0329] When the request offset result information is received from the server 10 via the communication I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received request offset result information (A390). Then, the control unit 21 of the terminal 20A ends the process.

[0330] Similarly, when the request offset result information is received from the server 10 via the communication I / F 22, the control unit 21 of the terminal 20B causes the display unit 24 to display the received request offset result information (B390). Then, the control unit 21 of the terminal 20B ends the process.

[0331] (2) Other examples of processing When offsetting requests, approval from the other user may be required. Cases where approval from the other user is required are similar to those described in the lump-sum settlement.

[0332] The processing in this case can be configured in a similar manner to the processing when approval from the other user is required for lump-sum settlement (as an example, not a limitation, the processing in Figures 1-21 to 1-22), so illustrations and detailed explanations will be omitted.

[0333] <Effects of the Fifth Example> In this embodiment, the first process is configured to include processing based on the first remittance request information and the second remittance request information, based on input by the user of the proposer to the terminal 20, out of multiple remittance request information regarding the user of the proposer, including the first remittance request information and the second remittance request information (an example of multiple information regarding a remittance request to a user of the terminal or a remittance request by a user of the terminal, including at least the first information and the second information, but not limited to this). As an example of an effect of an embodiment obtained by such a configuration, the first information and the second information can be appropriately processed based on input by the user of the terminal to the terminal from a remittance request to the user of the terminal or a plurality of pieces of information related to a remittance request by the user of the terminal, which includes at least the first information and the second information.

[0334] Furthermore, this embodiment illustrates a configuration in which the first remittance request information and the second remittance request information are information on the same remittance request amount, and the first process is a process of request offsetting the first remittance request information and the second remittance request information based on the first remittance request information and the second remittance request information (this is not a limitation, but an example of offsetting the first information and the second information). As an example of the effect of the embodiment obtained by such a configuration, when the first information and the second information are information of the same amount, these pieces of information can be offset, thereby improving the convenience of both the user who requests remittance using the first information and the user who requests remittance using the second information.

[0335] <Fifth Modification> In the fifth embodiment, if the remittance request amount of the remittance request selected for processing is not offset, a new remittance request may or may not be created, with the difference amount being the remittance request amount, and the type (payment / receipt) being determined by the positive or negative sign of the amount deduction result.

[0336] <Sixth Example> The sixth embodiment is an embodiment of the "creation of a bulk remittance request" from the bulk processing described above. The contents described in the sixth embodiment are applicable 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.

[0337] <Display screen> FIG. 6-1 is a diagram showing an example of a remittance request list screen displayed on the display unit 24 of the terminal 20A in this embodiment. The current location display area CLR1 at the top of this screen displays the words "Transfer request with DD," indicating that an unprocessed request between user DD and the screen is being displayed. Also, the current location display region CLR1 shows a state in which the first to fourth remittance requests are selected from among the pending requests between the user DD and the user.

[0338] When the first through fourth selected remittance requests are settled in a lump sum, the lump sum settlement will be "Payment 1,100 yen", and user AA will pay "1,100 yen" to user DD. However, in this example, user AA's current electronic money account balance is "500 yen", so there will be a shortfall of "600 yen" in the payment amount.

[0339] Therefore, in this embodiment, the server 10 creates a lump-sum remittance request based on the amount of the shortfall in payment when lump-sum settlement is performed. However, in this embodiment, although a lump sum remittance request is created, no lump sum settlement is performed.

[0340] Specifically, the settlement details confirmation area ACR7 at the bottom of the screen displays the user's current electronic money account balance, and the user's electronic money account balance after settlement, which is "500 yen."

[0341] Below that, a suggestion button BT9 and a cancel button are displayed along with the text "Would you like to suggest consolidating the requests?". If the Proposal button BT9 is tapped in this state, a new remittance request will be created based on the shortfall in the payment, 1,100 yen. As a result, the screen shown in Figure 6-2 will be displayed.

[0342] In Figure 6-2, a newly created remittance request is displayed, which is a previously received remittance request that consolidates four remittance requests and sets the payment amount at 1,100 yen. In this example display screen, the four remittance requests selected in Figure 6-1, that is, the remittance requests used to create the bulk remittance request (combined remittance requests), are displayed in a hanging format under the bulk remittance request. In addition, to make it easier for the user to recognize, these remittance requests are displayed in a different manner (grayed out in this example) from the other remittance requests.

[0343] Unlike this example display screen, the remittance requests used to create the lump sum remittance request may not be displayed. Also, when a lump sum remittance request is tapped, the remittance requests used to create the lump sum remittance request may be displayed.

[0344] <Processing> FIG. 6-3 is a flowchart showing an example of the flow of the lump-sum remittance request creation process executed by the control unit 11 of the server 10 in this embodiment. The control unit 11 of the server 10 judges whether or not the creation of a lump sum remittance request has been requested from the terminal 20, based on whether or not lump sum remittance request creation request information has been received from the terminal 20 (S510). The bulk remittance request creation request information may include, by way of example and not limitation, a selection of remittance requests for which the bulk remittance request is to be created.

[0345] If it is determined that a request has been made (S510: YES), the control unit 11 of the server 10 refers to the remittance request management data 157 and calculates the remittance request amount of the bulk remittance request to be created (hereinafter referred to as the "bulk remittance request amount") based on the remittance request amount of each selected remittance request and its type (received remittance request (payment) / sent remittance request (receive)) (S530).

[0346] Thereafter, the control unit 11 of the server 10 creates a lump sum remittance request based on the calculated lump sum remittance request amount, and stores the data of the created lump sum remittance request in the remittance request management data 157 (S550).

[0347] Next, the control unit 11 of the server 10 transmits lump sum remittance request creation result information regarding the result of creating the lump sum remittance request to the requesting terminal 20 via the communication I / F 14 (S570). Then, the control unit 11 of the server 10 ends the lump-sum remittance request creation process.

[0348] After this process is performed, lump sum remittance request information corresponding to the lump sum remittance request is displayed on the remittance request list screen or the like displayed on the display unit 24 of the terminal 20. Then, it becomes possible to execute lump sum settlement based on this lump sum remittance request.

[0349] In addition, if it is determined in S510 that the creation of a lump-sum transfer request has not been requested from the terminal 20 (S510: NO), the control unit 11 of the server 10 may, by way of example and not limitation, perform other lump-sum processing, such as the lump-sum settlement described above or the request offset described above, based on a request from the terminal 20.

[0350] There is also a risk that a malicious user may create a false remittance request as described above and then create a bulk remittance request that includes that false remittance request. Thus, creation of a bulk remittance request may or may not require the other party's approval.

[0351] <Effects of the Sixth Embodiment> In this embodiment, the other user is one user (this is an example, not limiting, of the second user being the first user), and the first process shows a configuration including a process of displaying on the display unit 24 a display of a lump-sum remittance request (this is an example, not limiting, of a sixth display) based on remittance request information (this is an example, not limiting, of a third information relating to a remittance request from the first user to the terminal user, or a remittance request from the terminal user to the other user) in which the remittance request amounts of the first remittance request information and the second remittance request information are added together. As an example of the effect of the embodiment obtained by such a configuration, when the other user is a single user, the sixth display based on the third information summarizing information on a plurality of remittance requests can be displayed to inform the user of the terminal of the third information. Also, by way of example and not of limitation, it becomes possible to perform comprehensive settlement based on the third information summarizing information on a plurality of remittance requests, thereby improving the convenience for the user.

[0352] <Seventh Example> The seventh embodiment is an embodiment relating to "creation of a special lump-sum settlement / special lump-sum remittance request" among the above-mentioned bulk processing. The contents described in the seventh embodiment are applicable 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.

[0353] <Display screen> Fig. 7-1 is a diagram showing an example of a remittance request list screen displayed on the display unit 24 of the terminal 20A in this embodiment, and shows a screen displaying a list of remittance requests between the user DD, similar to Fig. 6-1. Here, similar to Fig. 6-1, the first to fourth remittance requests are shown selected.

[0354] When the first through fourth selected remittance requests are settled in a lump sum, the lump sum settlement will be "Payment 1,100 yen", and user AA will pay "1,100 yen" to user DD. However, in this example, user AA's current electronic money account balance is "500 yen", so there will be a shortfall of "600 yen" in the payment amount.

[0355] In this case, in this embodiment, the control unit 11 of the server 10 performs a lump-sum settlement by transferring the entire amount of the current balance of the electronic money account of the user AA to the user DD. In addition, the control unit 11 of the server 10 creates a new remittance request with the amount of the shortfall in the lump-sum payment set as the remittance request amount. In other words, in this embodiment, unlike the sixth embodiment, the proposer's user makes payments up to the amount that can be paid with his / her balance, and then creates a new remittance request with the amount that cannot be paid as the remittance request amount.

[0356] For convenience, a lump sum settlement in which payments are made up to the maximum extent possible based on multiple remittance requests will be referred to as a "special lump sum settlement," and a new lump sum remittance request created after a special lump sum settlement will be referred to as a "special lump sum remittance request."

[0357] Specifically, the settlement details confirmation area ACR8 at the bottom of the screen displays "500 yen" as the current balance of the user's electronic money account, and "0 yen" as the balance of the user's electronic money account after settlement. When the Proposal button is tapped in this state, a special lump-sum settlement is executed in which the entire amount of user AA's current electronic money account balance, "500 yen," is transferred from user AA to user DD and paid. After that, a special lump-sum remittance request is created based on the shortfall in the payment, "600 yen." As a result, the screen shown in Figure 7-2 is displayed.

[0358] In Figure 7-2, a special lump sum remittance request with a payment amount of "600 yen" is displayed. In this example display screen, the special bulk remittance request is displayed with the four remittance requests selected in Figure 7-1, that is, the remittance requests (combined remittance requests) used to create the special bulk remittance request, hanging down. Also, to make it easier for the user to understand, these remittance requests are displayed in a different manner (grayed out in this example) than normal remittance requests.

[0359] Unlike this example display screen, the remittance request used to create the special lump remittance request may not be displayed. In addition, when a special lump sum remittance request is tapped, the remittance request used to create the special lump sum remittance request may be displayed.

[0360] <Processing> 7-3 and 7-4 are diagrams showing an example of the fourth settlement process executed by the control unit 21 of the server 10 in this embodiment.

[0361] After S1515, the control unit 11 of the server 10 determines whether the electronic money account balance of any user will become negative (S1520), and if it is determined that the balance will become negative (S1520: YES), determines whether the electronic money account balance will become negative for the user of the proposer (S1570).

[0362] If it is determined that the user whose electronic money account balance is negative is the proposer (S1570: YES), the control unit 11 of the server 10 sends lump-sum settlement type confirmation information, including the lump-sum settlement amount, to the terminal 20A via the communication I / F 14 to confirm the type of lump-sum settlement to be performed (normal lump-sum settlement / special lump-sum settlement) (S1571). In this case, the aforementioned insufficient balance information may or may not be included in the lump-sum settlement type confirmation information and sent.

[0363] Thereafter, the control unit 11 of the server 10 judges whether or not the execution of special lump-sum settlement has been requested based on the receipt of settlement execution request information including information on the type of lump-sum settlement to be executed from the terminal 20A (S1574). When it is judged that the execution of the above-mentioned normal lump-sum settlement has been requested, rather than the special lump-sum settlement (S1574: NO), the control unit 11 of the server 10 proceeds to S1555 in FIG. 2-5, for example and not limitation.

[0364] On the other hand, if it is determined that execution of special lump-sum settlement has been requested (S1574: YES), the control unit 11 of the server 10 determines whether approval of the other user is required (S1575). If it is determined that approval from the other user is required (S1575: YES), the control unit 11 of the server 10 sends special lump-sum settlement approval confirmation information including special lump-sum settlement amount information, which is information on the settlement amount based on the special lump-sum settlement (hereinafter referred to as the "special lump-sum settlement amount"), to the terminal 20B via the communication I / F 14 (S1577). The special lump sum settlement amount may be, by way of example and not by way of limitation, an amount equivalent to the proposer's user's current electronic money account balance.

[0365] However, without being limited to this, the special lump-sum settlement amount can be any amount as long as it is greater than "0" and less than or equal to the current balance in the electronic money account of the proposer's user.

[0366] Thereafter, the control unit 11 of the server 10 determines whether or not the special lump-sum settlement has been approved by determining whether or not special lump-sum settlement approval information indicating that the special lump-sum settlement is approved has been received from the terminal 20B (S1579).

[0367] If it is determined that the request has been approved (S1579: YES), the control unit 11 of the server 10 executes special lump-sum settlement (S1581). Specifically, the control unit 11 of the server 10 updates the electronic money account balance of the proposer's user (user AA in this example) to zero, and adds the special lump-sum settlement amount to the electronic money account balance of the other user (user BB in this example) to update it.

[0368] Thereafter, the control unit 11 of the server 10 creates a special lump-sum remittance request (S1583). Specifically, the control unit 11 of the server 10 creates a special lump-sum remittance request from the other user to the proposer user, with the remittance request amount being the lump-sum settlement amount minus the special lump-sum settlement amount. Then, the control unit 11 of the server 10 ends the fourth settlement process.

[0369] In addition, as described above, the method of making payments up to the proposer's user's balance that can be used to pay is not limited to the case where multiple remittance requests are selected as described above, but can also be applied when a single remittance request is selected. In other words, when one received remittance request is selected whose remittance request amount is greater than the proposer user's current electronic money account balance, the control unit 11 of the server 10 creates a remittance request whose remittance request amount is the amount obtained by subtracting the electronic money account balance from the remittance request amount (the shortfall).

[0370] <Second process by terminal> In this embodiment, in addition to the first process described above, the control unit 21 of the terminal 20 can be configured to execute a second process that processes at least one piece of information based on the electronic money account balance of the user of the terminal 20 (the balance of the user of the terminal).

[0371] By way of example and not limitation, the second process includes at least the following processes: · Processing for sending request selection information to the server 10 · Processing for receiving lump-sum settlement confirmation information from server 10 - Displaying lump sum settlement confirmation information · Processing for receiving lump-sum settlement result information from server 10 - Displaying the results of a lump sum payment A process of requesting the server 10 to deduct an amount (including offsetting an amount) - Processing to request the server 10 to execute special lump-sum settlement Requesting the server 10 to create a special bulk remittance request

[0372] <Effects of the Seventh Embodiment> This embodiment illustrates a configuration in which a second process (not limiting, an example of a second process for processing at least one piece of information) for lump-sum settlement for at least one piece of remittance request information is executed by the terminal 20 of the user of the proposer of lump-sum settlement based on the electronic money account balance (not limiting, an example of the balance of the user of the terminal) of the user of the proposer of lump-sum settlement among multiple remittance request information related to remittance requests to the user of the proposer of lump-sum settlement (not limiting, an example of the balance of the user of the terminal). As an example of an effect of an embodiment obtained by such a configuration, at least one of a plurality of pieces of information related to a remittance request to a user of the terminal or a remittance request by a user of the terminal can be processed by the second processing, taking into account the balance of the user of the terminal, thereby improving convenience for the user.

[0373] <Seventh Modification> This is related to the first variant example (3), but in the seventh embodiment, the proposer's terminal 20 or the server 10 may or may not automatically select (including suggest) a remittance request based on the proposer's user's current electronic money account balance.

[0374] Specifically, the control unit 21 of the proposer's terminal 20 performs a process of inquiring of the server 10 about the current electronic money account balance of the proposer's user. Then, the control unit 21 of the proposer's terminal 20 identifies and selects, from among the remittance requests included in the remittance request list information received from the server 10, a combination of remittance requests that will result in a payment that exceeds the current electronic money account balance of the proposer's user, by way of example and not limitation, based on the amount of each remittance request and the type of each remittance request (received remittance request (payment) / sent remittance request (receive)).

[0375] In this case, as an example and not a limitation, in Figure 7-1, among the unprocessed requests between user DD, by way of example and not a limitation, the requests to be automatically selected as requests to be processed for lump-sum settlement, starting with the most recent remittance request, may or may not be proposed to the user as being selected up to the remittance request for which the balance is insufficient (the fourth request in this example).

[0376] When the control unit 11 of the server 10 selects a remittance request, the control unit 11 may carry out a similar process based on the data of the remittance request stored in the remittance request management data 157 .

[0377] In this modified example, the second process includes a process of selecting, from among multiple remittance request information, remittance request information that can be processed with the proposer's user's electronic money account balance (not limited to this, but an example of the terminal user's balance), and shows a configuration in which the selected information is processed. As an example of the effect of an embodiment obtained by such a configuration, information that can be processed with the balance of the user of the terminal is selected and processed, so that, by way of example and not limitation, information can be processed within a range that does not cause the balance of the user of the terminal to become negative, thereby further improving user convenience.

[0378] <Eighth Example> The eighth embodiment is an embodiment in which, when a user of a terminal 20 remits money to a partner user or makes a remittance request to a partner user, an outstanding request is displayed. The contents described in the eighth embodiment are applicable 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.

[0379] <Display screen> 8-1 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment. This screen is, by way of example and not by way of limitation, a remittance screen of a payment application displayed on the display unit 24 of the terminal 20A of user AA. In the current location display area CLR1 which shows the current location in the payment application, the word "Remittance" is displayed, indicating that the current location is the remittance function of the payment application.

[0380] Below the current location display area CLR1, the icon image and user name (user EE in this example) of the payment application of the user selected as the remittance recipient are displayed. Also displayed below that are the remittance amount (500 yen in this example) to the user selected as the remittance recipient, and a function button for increasing the remittance amount by a certain amount.

[0381] Further below that is displayed an outstanding request confirmation area URR1, which is configured to enable confirmation of outstanding requests between the user selected as the recipient of the transfer (user EE in this example) and the user making the transfer (user AA in this example).

[0382] At the top of the unprocessed request confirmation area URR1, the words "Unsettled request with EE" are displayed, indicating that an unprocessed request between the user and EE is being displayed.

[0383] Also, below that, the lump sum payment amount (in this example, "1,500 yen") and a mark (in this example, a "payment mark") are displayed assuming that all selected items are paid in one lump sum. It should be noted that the display column for the case where it is assumed that all selected items will be settled at once does not need to be provided.

[0384] Below that, remittance requests to user EE are listed. In this example, pending requests to user EE are listed in chronological order from the top to the bottom.

[0385] Also, under the outstanding request confirmation area URR1, a remittance button labeled "Remit" is displayed for executing a remittance (remittance process). When the remittance button is tapped, the server 10 executes a remittance process (remittance from user AA to user EE).

[0386] Note that the remittance button may be displayed, for example and not by way of limitation, below the display area of ​​the function button for increasing the remittance amount by a certain amount, in an area above the outstanding request confirmation area URR1, or the like.

[0387] In this manner, in this embodiment, by displaying the pending request together with the remittance information, the user is able to check the pending request at the same time as making the remittance.

[0388] 8-2 is a diagram showing another example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment. This screen is, by way of example and not by way of limitation, a remittance request screen of a payment application displayed on the display unit 24 of the terminal 20A of the user AA. In the current location display area CLR1 which shows the current location in the payment application, the words "Remittance Request" are displayed, which indicates that the current location is the remittance request function of the payment application.

[0389] Below the current location display area CLR1, the icon image and user name (user EE in this example) of the payment application of the user selected as the recipient of the remittance request are displayed. Also displayed below that are the remittance request amount (500 yen in this example) for the user selected as the recipient of the remittance request, and a function button for increasing the remittance request amount by a certain amount.

[0390] In addition, if the user selected as the recipient of the remittance request accepts the remittance request, the amount of the remittance request is transferred from the electronic money account of the user selected as the recipient of the remittance request to the electronic money account of the user who made (sent) the remittance request.

[0391] Also, just like in Figure 8-1, an unprocessed request confirmation area URR1 is displayed below that, and a remittance request button labeled "Request remittance" is displayed below that to execute the remittance request transmission (remittance request transmission process). When the remittance request button is tapped, the server 10 executes a remittance request transmission process (transmission of remittance request information from user AA to user EE).

[0392] Note that the remittance request button may be displayed, for example and not by way of limitation, below the display area for the function button for increasing the remittance request amount by a certain amount, above the outstanding request confirmation area URR1, or the like.

[0393] In this manner, in this embodiment, by displaying the pending request together with the information for sending the remittance request, the user is able to check the pending request when making the remittance request.

[0394] <Processing> Fig. 8-3 is a flowchart showing an example of the flow of the process executed by each device in this embodiment. Here, as an example, the process of displaying pending requests when a user remits money, as described in Fig. 8-1, is described.

[0395] First, the control unit 21 of the terminal 20A judges whether or not an input for displaying a remittance screen has been made to the input unit (A105). If it is determined that input has been made (A105: YES), the control unit 21 of the terminal 20A performs processing of A110 and, based on the remittance request list information received from the server 10 via the communication I / F 22, causes the display unit 24 to display a remittance screen (a screen for remittances) including the remittance request list information (A125).

[0396] Thereafter, the control unit 21 of the terminal 20A determines whether or not an input for executing a remittance (for example, but not limited to, the operation of the remittance button) has been made (A630). If it is determined that no input has been made to execute remittance (A630: NO), the control unit 21 of the terminal 20A ends the process.

[0397] On the other hand, if it is determined that an input for executing a remittance has been made (A630: YES), the control unit 21 of the terminal 20A transmits remittance request information for requesting a remittance to the server 10 via the communication I / F 22 (A640).

[0398] After S120, the control unit 11 of the server 10 judges whether or not remittance request information has been received from the terminal 20A via the communication I / F 14 (S640). If it is determined that no remittance request information has been received (S640: NO), the control unit 11 of the server 10 ends the process.

[0399] On the other hand, if it is determined that remittance request information has been received (S640: YES), the control unit 11 of the server 10 executes remittance processing (S650). Specifically, by way of example and not limitation, remittance confirmation information for confirming the remittance contents is sent to the terminal 20A via the communication I / F 14, and based on receipt of remittance execution request information from the terminal 20A via the communication I / F 14, remittance from user AA to user BB is executed. In this case, the control unit 21 of the terminal 20A executes the processes A650 to A670, for example and not for limitation.

[0400] Thereafter, the control unit 11 of the server 10 judges whether the remittance result is "OK" or not (S670). If it is judged to be "OK" (S670: YES), the control unit 11 of the server 10 transmits the remittance result information to each of the terminals 20A and 20B via the communication I / F 14 (S690). Then, the control unit 11 of the server 10 ends the process.

[0401] When the remittance result information is received from the server 10 via the communications I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received remittance result information (A690). Then, the control unit 21 of the terminal 20A ends the process.

[0402] Similarly, when the remittance result information is received from the server 10 via the communications I / F 22, the control unit 21 of the terminal 20B causes the display unit 24 to display the received remittance result information (B690). Then, the control unit 21 of the terminal 20B ends the process.

[0403] As for the process of displaying pending requests when a user makes a remittance request, as explained in Figure 8-2, it can be configured in the same way by replacing "Remittance" in the process in Figure 8-3 with "Send Remittance Request", so illustration and explanation are omitted here. Specifically, in the processing of terminal 20A, A105 determines whether or not an input has been made to display a remittance request sending screen, A125 displays the remittance request sending screen including remittance request list information, A630 determines whether or not to execute the remittance request sending, A640 sends remittance request sending request information, A650 displays remittance request sending confirmation information, A660 determines whether or not a request to execute the remittance request sending has been made, A670 sends remittance request sending execution request information, and A690 displays remittance request sending result information. Furthermore, in the processing of terminal 20B, information on the result of remittance request transmission is displayed on B690. In addition, in the processing of the server 10, it is determined in S640 whether or not remittance request transmission request information has been received, the remittance request transmission processing is executed in S650, it is determined in S670 whether or not the remittance request transmission result is OK, and the remittance request transmission result information is transmitted in S690.

[0404] <View pending requests> The pending requests displayed on the display 24 of the terminal 20 may be, by way of example and not limitation, either or both of the following: -An outstanding request corresponding to the user to whom you are sending money (the recipient user) or the user to whom you are sending a money request (the recipient user) - Pending requests that correspond to a user other than the user to whom you are sending money (the recipient user) or the user to whom you are sending a money transfer request (the recipient user)

[0405] It is possible to display a pending request corresponding to the other user. By way of example and not limitation, when user AA sends a remittance to user EE as the remittance destination user as shown in FIG. 8-1, or when user AA sends a remittance request to user EE as the remittance request destination user as shown in FIG. 8-2, a pending request corresponding to user EE can be displayed.

[0406] However, some users may wish to view pending requests corresponding to different users than the other user. Therefore, by way of example and not limitation, in addition to the unprocessed requests corresponding to user EE in Figures 8-1 and 8-2, by way of example and not limitation, it is also possible to display unprocessed requests corresponding to users BB and CC. In this case, it is also possible to not display the pending requests corresponding to user EE, but to display the pending requests corresponding to users BB and CC, for example and without limitation.

[0407] In other words, the following three patterns are possible for displaying pending requests, by way of example and not limitation: (Pattern 1) An unprocessed request corresponding to the other user (Pattern 2) Pending requests for the other user + Pending requests for a user other than the other user (Pattern 3) An unprocessed request that corresponds to a different user than the other user

[0408] Furthermore, in any of the above patterns, for each user, all of the unprocessed requests corresponding to that user may be displayed, or only a portion of the unprocessed requests corresponding to that user may be displayed. In other words, the user (the other user / a user different from the other user) who displays the unprocessed requests and the range of unprocessed requests to be displayed (all / some) can be combined as desired. As a non-limiting example (Pattern 2), all unprocessed requests corresponding to the other user may be displayed, but some of the unprocessed requests corresponding to a user different from the other user may be displayed.

[0409] In addition, when displaying some of the unprocessed requests, it is possible to determine which unprocessed requests to display based on various information (conditions). In this case, it is possible to combine the contents of the 16th embodiment described later. As will be explained in the 16th embodiment, the various types of information include, but are not limited to, the following information by way of example. Date and time when the transfer request was sent / received -Transfer request amount Payment deadline for remittance requests - Transfer requests in which users other than the user who made the transfer request and the user to whom the transfer request was made are involved in the amount or reason of the transfer request It should be noted that these are merely examples and are not limiting. Moreover, a combination of a plurality of pieces of information among these pieces of information can be applied.

[0410] Since a user may forget about pending requests whose dates or times are older than a certain number, it may be decided to display pending requests even if they correspond to a different user than the target user. Pending requests with a large remittance request amount may be of high importance, so it may be decided to display pending requests even if they correspond to a different user than the target user. Remittance requests where other users than the requesting user and the requested user are involved in the remittance request amount or reason may also be of high importance, so it may be decided to display pending requests even if they correspond to users other than the other user. Pending requests that are due for payment within a certain period of time may require urgent processing, so it may be decided to display pending requests even if they correspond to a different user than the target user.

[0411] As will be described in the 16th embodiment, the unprocessed requests can be sorted and displayed in ascending / descending order based on the various information (conditions) described above. As an example, the more important an unprocessed request is, the higher it can be displayed.

[0412] In addition to these, pending requests displayed on the display 24 of the terminal 20 can be hidden based on, for example and not by way of limitation, an input by the user of the terminal 20 on an input unit. In this case, by way of example and not limitation, pending requests corresponding to a portion of users may be hidden, or pending requests corresponding to all users may be hidden.

[0413] Also, it is considered that some users may find it annoying to see pending requests displayed. Therefore, it may be possible to set whether to display or not display the unprocessed requests on a setting screen (not shown) or the like.

[0414] Specifically, on the setting screen of the application, as setting information related to the display of unprocessed requests, for example and without limitation, a slide button or a check box capable of switching between displaying and hiding unprocessed requests is displayed. Then, based on an operation on the slide button or the check box, the terminal 20 or the server 10 can be made to set the display / hide.

[0415] In this case, it may be possible to set whether to display or hide unprocessed requests collectively for all users, or it may be possible to set whether to display or hide unprocessed requests individually for each user. Also, it may be possible to set whether to display all unprocessed requests or to display only some of the unprocessed requests.

[0416] The same applies to the following examples.

[0417] <Effects of the Eighth Example> This embodiment illustrates a configuration in which the terminal 20 of the proposer's user displays on the display unit 24 a first display based on information for remittance from the proposer's user (not limited to, an example of a user of the terminal) to the other user (not limited to, an example of a first user) (not limited to, an example of first information regarding a remittance from the user of the terminal to the first user) or information for sending a remittance request from the proposer's user to the other user (not limited to, an example of first information regarding a remittance request sent from the user of the terminal to the first user), and a second display based on remittance request information regarding a received remittance request that the proposer's user has received from the other user (not limited to, an example of second information regarding a remittance request sent from a second user to the user of the terminal) or remittance request information regarding a sent remittance request that the proposer's user has sent to the other user (not limited to, an example of second information regarding a remittance request sent from the user of the terminal to the second user). As an example of an effect of the embodiment obtained by such a configuration, when the user of the terminal checks the first information, the user can also check the second information.

[0418] Furthermore, this embodiment illustrates a configuration in which the terminal 20 of the proposer's user performs processing for transferring money (not limited to this, but an example of processing related to remittance) through the control unit 21 based on input by the proposer's user to the terminal 20 on which the first display is displayed. As an example of the effect of the embodiment obtained by such a configuration, remittance to the other user can be easily realized based on an input to the terminal on which the first display is displayed.

[0419] <Eighth Modification> In the above embodiment, settlement (including lump-sum settlement of outstanding requests) can also be performed based on input for information on outstanding requests that are displayed together with information for remittance to the other user and information for sending a remittance request to the other user.

[0420] Specifically, in the example screen of, but not limited to, Figure 8-1, in addition to the remittance button, a settlement button is displayed to execute settlement of the selected unprocessed requests (settlement in one lump sum if multiple requests are selected). Then, when the settlement button is tapped, the server 10 can execute the settlement process for the selected unprocessed request.

[0421] Similarly, in the example screen of FIG. 8-2, which is not limiting, in addition to the remittance request button, a settlement button is displayed for executing settlement of selected unprocessed requests (settlement in one go if multiple requests are selected). Then, when the settlement button is tapped, the server 10 can execute the settlement process for the selected unprocessed request.

[0422] The settlement process for unprocessed requests is as described above, so a repeated explanation will be omitted.

[0423] Fig. 8-4 is a flow chart showing an example of the flow of the process executed by each device in this modified example. Here, as an example, in the process of displaying pending requests when a user remits money as shown in Fig. 8-3, a process of either remittance or settlement of the pending request will be described.

[0424] After A125, the control unit 21 of the terminal 20A determines an execution target based on an input to the input unit (A631). If it is determined that the target of execution is settlement of unprocessed requests (lump sum settlement if multiple requests are selected) (A631: Settlement of unprocessed requests), the control unit 21 of terminal 20A sets request selection information including unprocessed request selection information indicating the selected unprocessed requests (A632).

[0425] On the other hand, if it is determined that the execution target is a remittance (A631: remittance), the control unit 21 of the terminal 20A sets request selection information including remittance information related to the remittance to be executed (A133).

[0426] After A632 or A133, the control unit 21 of the terminal 20A transmits the set request selection information to the server 10 via the communication I / F 22 (A140). Then, the control unit 21 of the terminal 20A transfers the processing to A150.

[0427] After S120, if it is determined that request selection information has been received from the terminal 20A (S140: YES), the control unit 11 of the server 10 determines the processing target based on the received request selection information (S641).

[0428] If it is determined that the processing target is "settlement of unprocessed requests", the control unit 11 of the server 10 sets the selected unprocessed requests as targets for settlement (if multiple requests are selected, they are set for lump-sum settlement) (S642). On the other hand, if it is determined that the transaction target is "remittance", the control unit 11 of the server 10 sets remittance as the settlement target (S143).

[0429] After S642 or S143, the control unit 11 of the server 10 executes the settlement process of S150.

[0430] When applying the first settlement process described in FIG. 1-19 by way of example and not by way of limitation, When S642 is set and there are multiple unprocessed requests to be processed, the result of the determination in S1510 as to whether the settlement target is a lump-sum settlement target is "YES". As a result, the processing from S1515 onwards is executed with these multiple unprocessed requests as the lump-sum settlement target. Also, when S642 is set and there is only one unprocessed request to be processed, the result of the determination in S1510 as to whether the settlement target is a lump-sum settlement target is "NO". As a result, the processing from S1570 onwards is executed with this one unprocessed request as the settlement target. On the other hand, if the setting of S143 has been made, the result of the determination in S1510 as to whether the settlement target is a lump-sum settlement target or not is “NO.” As a result, the processing from S1570 onwards is executed with the remittance as the settlement target.

[0431] As for the process of displaying pending requests when a user makes a remittance request and either sending the remittance request or settling the pending request, this can be configured in a similar manner by replacing "remittance" in the process in Figure 8-4 with "send remittance request," so illustrations and explanations are omitted here. Specifically, in the processing of terminal 20A, A105 determines whether an input has been made to display a remittance request sending screen, A125 displays a remittance request sending screen including remittance request list information, A631 determines whether the execution target is to settle an unprocessed request or to send a remittance request, and A133 sets request selection information including remittance request sending information. In the processing of the server 10, it is determined in S641 whether the processing target is the settlement of an unprocessed request or a remittance request transmission, and in S143 the remittance request transmission is set as the processing target for settlement.

[0432] In this modified example, the terminal 20 of the proposer's user displays on the display unit 24 a first display based on information for remittance from the proposer's user (not limited to, an example of a user of the terminal) to the other user (not limited to, an example of a first user) (not limited to, an example of first information regarding a remittance from the user of the terminal to the first user) or information for sending a remittance request from the proposer's user to the other user (not limited to, an example of first information regarding a remittance request sent from the user of the terminal to the first user), and a second display based on remittance request information regarding a received remittance request that the proposer's user has received from the other user (not limited to, an example of second information regarding a remittance request sent from a second user to the user of the terminal) or remittance request information regarding a sent remittance request that the proposer's user has sent to the other user (not limited to, an example of second information regarding a remittance request sent from the user of the terminal to the second user). The terminal 20 of the proposer's user is configured to perform, through the control unit 21, a process for transferring money, a process for receiving the transferred amount, or a process for sending / receiving a remittance request (remittance reminder) based on input by the proposer's user to the terminal 20 displaying the first or second display (not limited to this, an example of a first process related to transferring money, receiving a remittance, or requesting a remittance). As an example of the effect of an embodiment obtained by such a configuration, it is possible to easily transfer money to a partner user, receive money from a partner user, and send / receive a transfer request to a partner user based on input to a terminal showing the first or second display.

[0433] Next, as an embodiment related to the eighth embodiment, an embodiment will be described in which, when a user of terminal 20 transfers money to another user or sends a remittance request to the other user, an unprocessed request selected from the displayed unprocessed requests is also processed.

[0434] In the following examples, the following five patterns will be described broadly. (A) Transfer + Processing received transfer requests (B) Transfer + Processing a sent transfer request (C) Send a remittance request + process a received remittance request (D) Send a remittance request + process a sent remittance request (E) Processing a remittance request + received remittance request + sent remittance request Each pattern will be described separately with examples.

[0435] As also shown in the eighth variant example, the processing (first processing, etc.) executed by the terminal 20 via the control unit 21 includes, by way of example and not limitation, processing for making a remittance (not being limited to this, an example of a processing related to a remittance), processing for receiving (accepting) a remittance (not being limited to this, an example of a processing related to receiving a remittance), processing for sending / receiving a remittance request (not being limited to this, an example of a processing related to a remittance request), etc. In the following, a server-client system is exemplified, and it is assumed that remittances and transmission of remittance requests are carried out via the server 10.

[0436] In the following, as described above, a case where the other user is one user, that is, a case where the second user is the first user (or the first user is the second user) will be exemplified. As mentioned above, the method described below can also be applied when the other users are different users, that is, when the first user is a different user from the second user (and the second user is a different user from the first user).

[0437] <Ninth Example> The ninth embodiment is an embodiment relating to processing of the above pattern (A). The contents described in the ninth embodiment are applicable 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.

[0438] In this embodiment, in addition to including "received remittance requests" among the unprocessed requests as targets for lump-sum settlement, "remittances" are also included in the lump-sum settlement and lump-sum settlement is performed.

[0439] FIG. 9-1 is a diagram showing an example of a table for explaining a processing method corresponding to each pattern. The vertical column of the table shows the target of new processing that is about to be executed (new processing target), and the horizontal column shows the types of unprocessed requests. The intersection of the vertical column and the horizontal column shows an example of processing that is realized by combining the new processing target and an unprocessed request of that type.

[0440] In this embodiment, the process of the pattern (A) remittance + received remittance request will be described. In this pattern, the process of (A1) remittance [remittance + remittance] can be performed. In other words, when making a new remittance to the other user, a remittance is also made to the other user based on a remittance request already received from the other user. More specifically, the sum of the amount to be remitted to the other user by the new remittance and the remittance request amount included in the received remittance request information (the amount requested to be remitted by the other user) is remitted to the other user.

[0441] <Display screen> An example of a display screen when the above process (A1) is performed will be described. 9-2 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment. This screen is, by way of example and not by way of limitation, a remittance screen of a payment application displayed on the display unit 24 of the terminal 20A of the user AA. In the current location display area CLR1 which shows the current location in the payment application, the word "Remittance" is displayed, indicating that the current location is the remittance function of the payment application.

[0442] Below the current location display area CLR1, the icon image and user name (user EE in this example) of the payment application of the user selected as the remittance recipient are displayed. Also displayed below that are the remittance amount (500 yen in this example) to the user selected as the remittance recipient, and a function button for increasing the remittance amount by a certain amount.

[0443] Further below that is displayed an outstanding request confirmation area URR1, which is configured to enable confirmation of outstanding requests between the user selected as the recipient of the transfer (user EE in this example) and the user making the transfer (user AA in this example).

[0444] At the top of the unprocessed request confirmation area URR1, the words "Unsettled request with EE" are displayed, indicating that an unprocessed request between the user and EE is being displayed. Also, below that, the lump sum payment amount (in this example, "1,500 yen") and a mark (in this example, a "payment mark") are displayed assuming that all selected items are paid in one lump sum.

[0445] Below that, remittance requests with user EE as the recipient are listed. In this example, unprocessed requests with user EE as the recipient are listed in chronological order from the top to the bottom in order of oldest. The display mode of each unprocessed request can be configured in the same way as in Figure 1-11, but is not limited thereto, so a repeated explanation will be omitted.

[0446] Below the unprocessed request confirmation area URR1, a remittance all-selection lump-sum settlement button labeled "Settle all and send" is displayed to execute the remittance process and lump-sum settlement of all selected requests. Below that, a remittance lump-sum settlement button BT11 labeled "Settle and send one" is displayed to execute the remittance process and lump-sum settlement of some of the unprocessed requests selected in the unprocessed request confirmation area URR1. Below that, a remittance button labeled "Just transfer" is displayed to execute only the remittance process.

[0447] As a non-limiting example, when the check box for the first received remittance request (payment of 2,500 yen) is checked "ON" in the pending request confirmation area URR1 and the lump-sum remittance settlement button BT11 is tapped, the terminal 20A requests the server 10 to execute the remittance and lump-sum settlement of the selected pending requests. The server 10 then transmits settlement result information regarding the execution result to the terminal 20E of the user EE, which is the other party.

[0448] FIG. 9-3 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20E when the lump-sum remittance settlement button BT11 is tapped. In this example, the notification information display area NTR4 of the notification screen displays two sets of settlement result information, one for remittance and the other for lump sum settlement. Specifically, by way of example and not limitation, settlement result information corresponding to the receipt of the remittance amount of "500 yen" remitted by user AA to user EE, and the receipt of the remittance amount of "2,500 yen" remitted by user AA based on the remittance request amount of "2,500 yen" received by user AA from user EE due to the first remittance request selected in Figure 9-2, is displayed.

[0449] As shown in FIG. 9-4, the two pieces of settlement result information may be combined and displayed as one piece of settlement result information in the notification information display area NTR4 of the notification screen, but this is not essential. As an example and not as a limitation, Figure 9-4 displays settlement result information indicating that user EE will receive "3,000 yen", which is the sum of the remittance amount of "500 yen" received from user AA and the remittance amount of "2,500 yen" received from the remittance request amount of "2,500 yen" to user AA.

[0450] In FIG. 9-2, the pending request confirmation area URR1 displays pending requests between the user selected as the remittance recipient and the user making the remittance, but this is not limiting.

[0451] Figure 9-5 shows an example of a display screen that displays all pending requests for a user making a remittance. Figure 9-5 is an alternative example of the remittance screen of Figure 9-2.

[0452] In FIG. 9-5, the unprocessed request confirmation area URR2 displays all unprocessed requests of the user making the remittance in chronological order, starting from the oldest at the top. In addition, below the unprocessed request confirmation area URR2, a lump-sum remittance settlement button BT11 and a remittance button are displayed. As a non-limiting example, in the unprocessed request confirmation area URR2, when the check box for the received remittance request (payment of 2,500 yen) from the fourth user EE is checked "ON" and selected, and the lump-sum remittance settlement button BT11 is tapped, the display screen of FIG. 9-3 is displayed on the display unit 24 of the terminal 20E.

[0453] <Processing> FIG. 9-6 is a flowchart showing an example of the flow of processing executed by each device in this embodiment. This flowchart is a rewrite of the flowchart in Figure 1-18, in which the new transaction target is "remittance."

[0454] In the processing of the pattern (A) remittance + received remittance request in this embodiment, since the remittance is made unilaterally to the other user, approval of the other user is not required when making a lump-sum settlement. Therefore, the processing that does not require approval of the other user is illustrated and described here. However, the present invention is not limited to this, and approval of the other user may be required.

[0455] After A125, the control unit 21 of the terminal 20A judges whether or not an unprocessed request has been selected from the remittance request list information (A131).

[0456] If an unprocessed request is selected, that is, if it is determined that a request is made to transfer money + to process the unprocessed request (A131: YES), the control unit 21 of terminal 20A sets request selection information including remittance information related to the remittance to be executed and unprocessed request selection information indicating the selected unprocessed request (A132).

[0457] On the other hand, if no unprocessed request is selected from the remittance request list information, that is, if it is determined that only the remittance is to be executed (A131: NO), the control unit 21 of the terminal 20A sets request selection information including remittance information related to the remittance to be executed (A133).

[0458] In addition, this process will be described on the assumption that remittance is being carried out. In reality, there may be cases where a user chooses to process only the pending requests without making a remittance. In this case, the process is the same as the process for lump-sum settlement of pending requests described above, so illustrations and repeated explanations are omitted.

[0459] After A132 or A133, the control unit 21 of the terminal 20A transmits the set request selection information to the server 10 via the communication I / F 22 (A140). Then, the control unit 21 of the terminal 20A transfers the processing to A150.

[0460] If it is determined in S140 that request selection information has been received from terminal 20A (S140: YES), the control unit 11 of the server 10 determines whether or not to process the remittance + unprocessed request based on the information included in the received request selection information (S141). If it is determined to process the request (S141: YES), the control unit 11 of the server 10 sets the remittance + settlement of the selected unprocessed request (lump settlement if multiple requests are selected) as the target for lump-sum settlement (S142).

[0461] On the other hand, if it is determined that the processing is not a combination of remittance and unprocessed request, that is, that only remittance is to be executed (S141: NO), the control unit 11 of the server 10 sets the remittance as the settlement target (S143).

[0462] After S142 or S143, the control unit 11 of the server 10 executes the settlement process of S150.

[0463] When applying the first settlement process described in FIG. 1-19 by way of example and not by way of limitation, When the setting of S142 is made, the result of the determination in S1510 as to whether the settlement target is a lump-sum settlement target is "YES." As a result, the processing from S1515 onwards is executed with the settlement of the remittance + the selected unprocessed request as the lump-sum settlement target. On the other hand, if the setting of S143 has been made, the result of the determination in S1510 as to whether the settlement target is a lump-sum settlement target or not is “NO.” As a result, the processing from S1570 onwards is executed with the remittance as the settlement target.

[0464] <Effects of the ninth embodiment> In this embodiment, the terminal 20 of the proposer's user displays on the display unit 24 a first display based on remittance information (not limited to, an example of first information regarding a remittance from the user of the terminal to the first user) from the proposer's user (not limited to, an example of a user of the terminal) to the other user (not limited to, an example of a first user) or remittance request information regarding a remittance request to be sent from the proposer's user to the other user (not limited to, an example of first information regarding a remittance request sent from the user of the terminal to the first user), and a second display based on remittance request information regarding a received remittance request that the proposer's user has received from the other user (not limited to, an example of second information regarding a remittance request sent from a second user to the user of the terminal) or remittance request information regarding a sent remittance request that the proposer's user has sent to the other user (not limited to, an example of second information regarding a remittance request sent from the user of the terminal to the second user). The terminal 20 of the proposer's user is configured to perform, through the control unit 21, a process for transferring money, a process for receiving the transferred amount, or a process for sending / receiving a remittance request (remittance reminder) based on input by the proposer's user to the terminal 20 displaying the first or second display (not limited to this, an example of a first process related to transferring money, receiving a remittance, or requesting a remittance). As an example of the effect of an embodiment obtained by such a configuration, it is possible to easily realize, based on input to a terminal showing the first or second display, sending money to a partner user, receiving (accepting) a money transfer from a partner user, sending a money transfer request to a partner user, receiving a money transfer request from a partner user, etc.

[0465] Further, in this embodiment, a configuration is shown in which the first process is performed by the control unit 21 based on the first information and the second information, on the basis of inputs to the first display and the second display. As an example of an effect of the embodiment obtained by such a configuration, processing based on the first information and the second information can be easily performed based on input to the first display and the second display.

[0466] In addition, this embodiment illustrates a configuration in which the first information is remittance information from the proposer's user to the other user (not limited to, but an example of information regarding a remittance from a terminal user to a first user), the second information is received remittance request information regarding a remittance request already received from the other user (not limited to, but an example of information regarding a remittance request sent from the second user to the terminal user), and the first process includes a process of remittance to the other user based on the remittance information and the received remittance request information. As an example of an effect of an embodiment obtained by such a configuration, it is possible to easily realize a money transfer between a first user and a second user based on input on the first display and the second display, based on information regarding a money transfer from the user of the terminal to the first user and information regarding a money transfer request sent from the second user to the user of the terminal.

[0467] In this case, the other user is one user (this is an example, not a limitation, of the second user being the first user), and the first process can include a process of transferring to the other user an amount that is the sum of the amount to be transferred from the proposer user to the other user and the remittance request amount included in the remittance request information already received from the other user (this is an example, not a limitation, of an amount based on the first information and the second information). As an example of the effect of the embodiment obtained by such a configuration, it is possible to transfer an amount based on the first information and the second information to the same single user.

[0468] <Ninth Variation> In the above embodiment, as an example of an amount based on the first information and the second information, a case was given in which the sum of the amount to be remitted from the proposer's user to the other user and the remittance request amount included in the remittance request information already received from the other user is remitted to the other user, but the present invention is not limited to this.

[0469] It is envisioned that the proposer user may borrow money from the other user, in which case, by way of example and not limitation, the proposer user may transfer money to the other user with interest. Specifically, as an example and not as a limitation, a process can be performed on the terminal 20 of the proposer's user or on the server 10 to automatically add a preset percentage of interest (for example and not as a limitation, 5% interest) to the total amount of the above amounts, and the amount with the interest added can be used as the remittance amount to be remitted from the proposer's user to the other user.

[0470] This method also applies to the case where the other user remits an amount based on the first information and the second information.

[0471] <Tenth Example> The tenth embodiment is an embodiment relating to the processing of the above-mentioned pattern (B). The contents described in the tenth embodiment are applicable to the other embodiments and the other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0472] In this embodiment, in addition to including "sent remittance requests" among the unprocessed requests as targets for lump-sum settlement, "remittances" are also included in the lump-sum settlement and lump-sum settlement is performed.

[0473] Let us refer again to the table in FIG. 9-6. In this embodiment, the process for pattern (B) remittance + sent remittance request is performed. In this pattern, either (B1) remittance + remittance reminder or (B2) [remittance + receipt] (amount can be deducted) can be processed.

[0474] In the process of (B1), when a new remittance is made to the other user, a remittance reminder is also sent to the other user based on a remittance request that has already been sent to the other user. It should be noted that a new remittance request may or may not be sent in place of the remittance reminder.

[0475] In the process of (B2), when a new remittance is made to the other user, the other user remits the money based on a remittance request already sent to the other user, and the money is received. In this case, since the payment and receipt of money are in an opposing relationship, the difference between the remittance request amount can be sent / received. In addition, if the remittance request amounts are the same, the amounts can be offset.

[0476] Specifically, the proposer's user transfers to the other user an amount obtained by subtracting the remittance request amount included in the transmitted remittance request information from the amount to be transferred from the proposer's user to the other user. Conversely, the amount obtained by subtracting the amount to be remitted from the proposer's user to the other user from the remittance request amount included in the transmitted remittance request information is received from the other user.

[0477] <Display screen> First, an example of a display screen when the above process (B1) is performed will be described. Fig. 10-1 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment. This screen is, by way of example and not limitation, a remittance screen of a payment application displayed on the display unit 24 of the terminal 20A of the user AA. As the details of the screen configuration can be configured similarly to Fig. 9-2, by way of example and not limitation, a detailed description will be omitted.

[0478] As a non-limiting example, when the check box for the second sent remittance request (receive 1,000 yen) is checked "ON" in the pending request confirmation area URR1 and the lump-sum remittance settlement button BT11 is tapped, the terminal 20A requests the server 10 to execute the remittance and lump-sum settlement of the selected pending requests. The server 10 then transmits settlement result information regarding the execution result to the terminal 20E of the user EE, which is the other party.

[0479] FIG. 10-2 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20E when the lump-sum remittance settlement button BT11 is tapped. In this example, the notification information display area NTR4 of the notification screen displays two sets of settlement result information, one for remittance and the other for lump sum settlement. Specifically, by way of example and not limitation, settlement result information corresponding to receipt of the remittance amount of "500 yen" sent by user AA to user EE and a reminder corresponding to the second remittance request selected in Figure 10-1 (a remittance request for the amount of "1,000 yen" sent by user AA to user EE) are displayed.

[0480] Next, an example of a display screen when the above process (B2) is performed will be described. FIG. 10-3 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment. This screen is a remittance screen of a payment application displayed on the display unit 24 of the terminal 20A of user AA, by way of example and not limitation. As the screen configuration can be configured similarly to FIG. 9-2, by way of example and not limitation, detailed explanations will be omitted. Note that in FIG. 10-3, the remittance amount to the user selected as the remittance destination is set to "1,500 yen", by way of example and not limitation.

[0481] As a non-limiting example, when the check box for the second sent remittance request (receive 1,000 yen) is selected as "ON" in the pending request confirmation area URR1 and the lump-sum remittance settlement button BT11 is tapped, the terminal 20A requests the server 10 to remit the money and settle the lump-sum settlement of the selected pending requests. The server 10 then transmits lump-sum settlement approval confirmation information to the terminal 20E of the other party, user EE, to confirm whether or not to approve the lump-sum settlement, and the information is displayed on the display unit 24 of the terminal 20E.

[0482] FIG. 10-4 is a diagram showing an example of a notification screen that is displayed when the lump-sum remittance settlement button BT11 is tapped. In the notification information display area NTR4, an icon image of user AA, who is the other party of the "settlement proposal", and the lump-sum settlement amount are displayed as lump-sum settlement approval confirmation information.

[0483] The lump-sum settlement approval confirmation information displays the details of the lump-sum settlement as follows: User EE will receive "1,500 yen" from the current remittance sent from User AA to User EE, and will pay the remittance request amount of "1,000 yen" based on the receipt of a previous remittance request from User AA.

[0484] As a non-limiting example, the contents of the lump-sum settlement can be stored by tapping the ``Close'' icon in the lump-sum settlement approval confirmation information, and the contents can be expanded from the stored state by tapping the ``Summary'' icon.

[0485] In addition, the lump-sum settlement approval confirmation information indicates that the lump-sum settlement amount that user EE will receive from user AA is "500 yen," which is the amount received from the remittance, "1,500 yen," minus the remittance request amount of "1,000 yen."

[0486] At the bottom of the lump-sum settlement approval confirmation information, there are displayed a settlement button BT12 marked "Settle" for approving the settlement with the above details, and a rejection button marked "Decline" for declining to approve the settlement with the above details.

[0487] FIG. 10-5 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20A when the settlement button BT12 is tapped. Below the current location display area CLR1, a notification NT2 containing a bell mark and the words "500 yen has been transferred" is displayed to notify that the lump-sum settlement of the remittance request has been approved from user EE's terminal 20E via server 10, and that the remittance has been made as a result.

[0488] Moreover, in the notification information display area NTR2 of the notification screen, information corresponding to the above notification NT2 is displayed. In this example, the notification information display area NTR2 of the notification screen displays the settlement result information (in this example, the payment of the remittance amount of 500 yen sent by user AA to user EE) as the details of the lump-sum settlement that has been made with user EE.

[0489] In addition, in Figure 10-3, when the lump-sum remittance settlement button BT11 is tapped, a confirmation screen may be displayed on the display unit 24 of the terminal 20A to inform the user AA that if settlement is made, the user AA will pay a lump-sum settlement amount of "500 yen", and based on the user AA's approval, a request may be made to execute the remittance and the lump-sum settlement of the selected unprocessed requests, or it may not be possible to do so.

[0490] <Processing> In this embodiment, the processes executed by each device can be realized in a similar manner to the processes in FIG. 9-6. However, when executing the process of (B2) [Remit + Receive] (amount deduction possible), the process of remittance by the other user is included. Therefore, as mentioned above, it is possible to require the approval of the other user when making a lump-sum settlement.

[0491] FIG. 10-6 is a flowchart showing an example of the flow of the processes executed by each device in this case. This flowchart is an example, not a limitation, of the process of Figs. 1-21 applied to the process of Figs. 9-6. The difference from the process in FIG. 9-6 is that steps B150 to B190 are added as processes executed by the control unit 21 of the terminal 20B.

[0492] <Effects of the Tenth Example> This embodiment illustrates a configuration in which the first information described above is remittance information from the proposer user to the other user (not limited to this, but an example of information regarding a remittance from a terminal user to a first user), and the second information is sent remittance request information regarding a remittance request that has already been sent from the proposer user to the other user (not limited to this, but an example of information regarding a remittance request sent from a terminal user to a second user). As an example of an effect of an embodiment obtained by such a configuration, a remittance from a user of a terminal to a first user and a remittance request sent from a user of a terminal to a second user can be processed together.

[0493] In this case, the first process may include a process of sending money to the other user based on the remittance information, and sending a remittance reminder to the other user based on the sent remittance request information. As an example of the effect of the embodiment obtained by such a configuration, it is possible to simultaneously perform remittance to a first user and a request for remittance to a second user.

[0494] In addition, in this embodiment, the other user is one user (not limiting, this is an example of the second user being the first user), and the first process shows a configuration including a process of transferring an amount based on the amount to be transferred from the proposer user to the other user and the remittance request amount included in the sent remittance request information (not limiting, this is an example of an amount based on the first information and the second information) to the other user (not limiting, this is an example of a process of transferring money to the first user) or a process of receiving money from the first user (not limiting, this is an example of a process of receiving money from the first user). As an example of the effect of an embodiment obtained by such a configuration, it is possible to send an amount based on the first information and the second information to the same user, or to receive an amount based on the first information and the second information from the same user.

[0495] In this case, the first process is configured to include a process of transferring to the other user an amount obtained by subtracting the remittance request amount (not limiting, an example of the second amount) included in the transmitted remittance request information from the amount to be transferred from the proposer's user to the other user (not limiting, an example of the first amount), or a process of receiving from the other user an amount obtained by subtracting the amount to be transferred from the proposer's user to the other user (first amount) from the remittance request amount (second amount) included in the transmitted remittance request information (not limiting, an example of the process of transferring from the first user). As an example of the effect of an embodiment obtained by such a configuration, it is possible to send an amount equal to the difference between a first amount and a second amount to the same user, or to receive an amount equal to the difference between the first amount and a second amount from the same user.

[0496] Moreover, this embodiment shows a configuration in which the first process is executed based on an input to the terminal of the other user and based on approval by the other user. As an example of an effect of the embodiment obtained by such a configuration, the first process can be executed based on the input to the terminal of the first user and based on the approval of the first user. This can prevent the first process from being executed against the will of the first user, for example and not by way of limitation.

[0497] <Eleventh Example> The eleventh embodiment is an embodiment relating to processing of the above-mentioned pattern (C). The contents described in the eleventh embodiment are applicable to any of the other embodiments and the other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0498] In this embodiment, in addition to including "received remittance requests" among the unprocessed requests as targets for lump-sum settlement, "sent remittance requests" are also included in the lump-sum settlement.

[0499] Let us refer again to the table in FIG. 9-6. In this embodiment, the process for pattern (C) sending a remittance request + receiving a remittance request is performed. In this pattern, either (C1) remittance request + remittance or (C2) [receive + remittance] (amount can be deducted) can be processed.

[0500] In the process of (C1), when making a new remittance request to the other user, a remittance to the other user is also made based on a remittance request already received from the other user.

[0501] In the process of (C2), when making a new remittance request to the other user, the other user remits money based on this new remittance request and receives the money, and also remits money to the other user based on the remittance request already received from the other user. In this case, you can receive / send the difference between the remittance request amount. In addition, if the remittance request amounts are the same, the amounts can be offset.

[0502] <Display screen> First, an example of a display screen when the above process (C1) is performed will be described. 11-1 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment. This screen is, by way of example and not by way of limitation, a remittance request screen of a payment application displayed on the display unit 24 of the terminal 20A of the user AA. In the current location display area CLR1 which shows the current location in the payment application, the words "Remittance Request" are displayed, which indicates that the current location is the remittance request function of the payment application.

[0503] Below the current location display area CLR1, an icon image in the payment application and a user name (user EE in this example) of the user selected as the recipient of the remittance request are displayed. Also displayed below that are the remittance request amount ("500 yen" in this example) for the user selected as the recipient of the remittance request, and a function button for increasing the remittance request amount by a certain amount. If the user selected as the recipient of the remittance request accepts the remittance request, the remittance request amount is transferred from the electronic money account of the user selected as the recipient of the remittance request to the electronic money account of the user who made (sent) the remittance request.

[0504] Further below that, an unprocessed request confirmation area URR1 is displayed. The unprocessed request confirmation area URR1 can be configured similarly to that in FIG. 9-2 by way of example and not by way of limitation, and therefore a description thereof will be omitted.

[0505] Below the unprocessed request confirmation area URR1, there is a remittance request transmission all-selection lump-settlement button labeled "Settle all and request remittance," which allows the user to execute the remittance request transmission process and lump-settle all selected remittance requests. Below that, there is a remittance request transmission lump-settlement button BT13 labeled "Settle one item and request remittance," which allows the user to execute the remittance request transmission process and lump-settle some of the unprocessed requests selected in the unprocessed request confirmation area URR1. Below that, there is a remittance request transmission button labeled "Only make a remittance request," which allows the user to execute only the remittance request transmission process.

[0506] As a non-limiting example, when the check box for the first received remittance request (payment of 2,500 yen) is checked "ON" in the pending request confirmation area URR1 and the remittance request transmission / lump settlement button BT13 is tapped, the terminal 20A requests the server 10 to transmit a new remittance request and to perform the lump-sum settlement of the selected pending requests. The server 10 then transmits remittance request information and settlement result information regarding the execution result of the lump-sum settlement to the terminal 20E of the other party, the user EE.

[0507] FIG. 11-2 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20E when the remittance request transmission lump-sum settlement button BT13 is tapped. In this example, the notification information display area NTR4 of the notification screen displays settlement result information for one remittance request selected in FIG. 11-1 and new remittance request information.

[0508] The settlement result information indicates that user EE has received the remittance request amount of "2,500 yen" in response to the remittance request to user AA.

[0509] The remittance request information displays, by way of example and not limitation, a remittance request sent by user AA to user EE for the remittance request amount of "500 yen", a remittance request remittance button indicated as "Transfer" to approve the remittance request and transfer money based on the remittance request, and a remittance request rejection button indicated as "Reject" to reject the remittance request without approving it.

[0510] Next, an example of a display screen when the process (C2) is performed will be described. FIG. 11-3 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment. This screen is, by way of example and not limitation, a remittance request screen of a payment application displayed on the display unit 24 of the terminal 20A of user AA. Details of the screen configuration can be configured similarly to FIG. 11-1 by way of example and not limitation, so detailed explanations will be omitted. Note that in FIG. 11-3, by way of example and not limitation, the remittance request amount to the user selected as the destination of the remittance request (user EE in this example) is set to "1,000 yen."

[0511] As a non-limiting example, when the check box for the first received remittance request (payment of 2,500 yen) is checked "ON" and selected in the pending request confirmation area URR1 and the remittance request transmission lump-sum settlement button BT13 is tapped, the terminal 20A requests the server 10 to transmit a new remittance request and perform the lump-sum settlement of the selected pending requests. Then, the server 10 transmits lump-sum settlement approval confirmation information to the terminal 20E of the other party, the user EE, to confirm whether or not to approve the lump-sum settlement, and the information is displayed on the display unit 24 of the terminal 20E.

[0512] FIG. 11-4 is a diagram showing an example of a notification screen that is displayed when the remittance request transmission lump-sum settlement button BT13 is tapped. In the notification information display area NTR4, an icon image of user AA, who is the other party of the "Request Settlement and Remittance Request", and the lump-sum settlement amount are displayed as lump-sum settlement approval confirmation information.

[0513] In this example, the lump-sum settlement approval confirmation information displays the details of the lump-sum settlement as follows: User EE will receive the remittance request amount of "2,500 yen" based on the remittance request sent to User AA, and will pay the remittance request amount of "1,000 yen" based on the receipt of this remittance request from User AA.

[0514] In addition, the lump-sum settlement approval confirmation information indicates that the lump-sum settlement amount that user EE will receive from user AA is "1,500 yen", which is the sum of the receiving remittance request amount of "2,500 yen" and the paying remittance request amount of "1,000 yen".

[0515] At the bottom of the lump-sum settlement approval confirmation information, there are displayed a settlement button BT14 marked "Settle" for approving the settlement with the above content, and a rejection button marked "Decline" for declining to approve the settlement with the above content.

[0516] FIG. 11-5 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20A when the settlement button BT14 is tapped. Below the current location display area CLR1, a notification NT3 containing a bell mark and the words "1,500 yen has been transferred" is displayed to notify that the lump-sum settlement of the remittance request has been approved from user EE's terminal 20E via server 10, and that the remittance has been made as a result.

[0517] Furthermore, in the notification information display area NTR2 of the notification screen, information corresponding to the above notification NT3 is displayed. In this specific example, the settlement result information is displayed after a lump-sum settlement has been made with user EE. In this example, the settlement result information displays that a lump-sum settlement amount of 1,500 yen has been transferred from user AA to user EE.

[0518] The settlement result information also shows that the lump-sum settlement includes the payment of "2,500 yen" based on the receipt of a previous remittance request, and the receipt of "1,000 yen" based on the sending of this current remittance request.

[0519] In addition, in Figure 11-3, when the remittance request sending lump-sum settlement button BT13 is tapped, a confirmation screen may be displayed on the display unit 24 of the terminal 20A to inform the user AA that if settlement is made, the user AA will receive "1,000 yen", and based on the approval of the user AA, the remittance request may be sent and the selected outstanding requests may be settled in lump sum, or it may not be necessary to do so.

[0520] <Processing> FIG. 11-6 is a flowchart showing an example of the flow of the process executed by each device in this embodiment. This flowchart is a rewrite of the flowchart in Figure 1-18, in which the new process target is "send a remittance request."

[0521] Strictly speaking, making a remittance request (sending a remittance request) can be considered to have a different meaning and concept from settlement (including lump-sum settlement). However, for the sake of simplicity, the process (flowchart) will be illustrated and explained assuming that making a remittance request (sending a remittance request) is also a type of settlement. Alternatively, the flowchart may be configured so that making a remittance request (sending a remittance request) is a separate process from settlement.

[0522] In addition, in the processing of pattern (C) in this embodiment, by way of example and not limitation, when processing (C1) is performed, approval of the other user may not be required, and when processing (C2) is performed, approval of the other user may be required. For simplicity, a process (flowchart) in which approval from the other user is not required is exemplified here.

[0523] First, the control unit 21 of the terminal 20A judges whether or not to transmit a remittance request based on whether or not an input for executing transmission of a remittance request has been made to the input unit (A107).

[0524] If it is determined that a remittance request is to be sent (A107: YES), the control unit 21 of the terminal 20A executes the process of A110. After that, based on receiving the remittance request list information from the server 10 via the communication I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display a remittance request sending screen (a screen for sending a remittance request) including the received remittance request list information (A127).

[0525] Thereafter, the control unit 21 of the terminal 20A judges whether or not an unprocessed remittance request has been selected from the remittance request list information (A135).

[0526] If an unprocessed request is selected, that is, if it is determined that a request is made to send a remittance request + to execute the processing of the unprocessed request (A135: YES), the control unit 21 of terminal 20A sets request selection information including remittance request sending information regarding the sending of the remittance request to be executed and unprocessed request selection information indicating the selected unprocessed request (A136).

[0527] On the other hand, if no unprocessed request is selected from the remittance request list information, that is, if it is determined that only the remittance request is to be sent (A135: NO), the control unit 21 of terminal 20A sets request selection information including remittance request sending information (A137).

[0528] In addition, this process will be described on the assumption that a remittance request is to be sent. In reality, there may be cases where a user chooses to process only the outstanding requests without sending a remittance request. In this case, however, the process is the same as the process for lump-sum settlement of outstanding requests described above, so illustrations and repeated explanations will be omitted.

[0529] After A136 or A137, the control unit 21 of the terminal 20A transmits the set request selection information to the server 10 via the communication I / F 22 (A140). Then, the control unit 21 of the terminal 20A transfers the processing to A150.

[0530] If it is determined in S140 that request selection information has been received from the terminal 20A (S140: YES), the control unit 11 of the server 10 determines whether or not to process the remittance request transmission + unprocessed request based on the information included in the received request selection information (S144). If it is determined to process the remittance request transmission + unprocessed request (S145: YES), the control unit 11 of the server 10 sets the remittance request transmission + settlement of the selected unprocessed request (lump settlement if multiple requests are selected) as targets for lump-sum settlement (S146).

[0531] On the other hand, if it is determined that the processing is not a remittance request transmission + unprocessed request, that is, that only the remittance request transmission is to be executed (S145: NO), the control unit 11 of the server 10 sets the remittance request transmission as the settlement target (S147).

[0532] After S146 or S147, the control unit 11 of the server 10 executes the settlement process of S150.

[0533] When applying the first settlement process described in FIG. 1-19 by way of example and not by way of limitation, When the setting of S146 is made, the result of the determination in S1510 as to whether the settlement target is a lump-sum settlement target is "YES." As a result, the processing from S1515 onwards is executed with the remittance request transmission + settlement of the selected unprocessed request as the lump-sum settlement target. On the other hand, if the setting of S147 is made, the result of the determination in S1510 as to whether the settlement target is a lump-sum settlement target is “NO.” As a result, the processing from S1570 onwards is executed with the remittance request transmission as the settlement target.

[0534] <Effects of the 11th embodiment> In this embodiment, the first information is remittance request transmission information for sending a remittance request from the proposer user to the other user (not limited to, but an example of information regarding a remittance request sent from a terminal user to a first user), and the second information is received remittance request information regarding a remittance request that has already been received from the other user (not limited to, but an example of information regarding a remittance request sent from a second user to a terminal user). As an example of an effect of an embodiment obtained by such a configuration, a remittance request sent from a user of a terminal to a first user and a remittance request sent from a second user to a user of the terminal can be processed together.

[0535] In this case, the first process may include a process of transmitting remittance request information to the other user based on the remittance request transmission information, and transmitting money to the other user based on the received remittance request information. As an example of the effect of the embodiment obtained by such a configuration, a request for remittance to a first user and remittance to a second user can be performed simultaneously.

[0536] In addition, this embodiment shows a configuration in which the other user is one user (this is not a limitation, but an example in which the second user is the first user), and the first process includes a process of transferring to the other user or receiving from the other user an amount based on the remittance request amount included in the remittance request information to be sent to the other user and the remittance request amount included in the remittance request information already received from the other user. As an example of an effect of the embodiment obtained by such a configuration, it is possible to remit an amount based on the first information and the second information to the first user, or to receive remittance from the first user.

[0537] In this case, the first process may include a process of sending to the other user an amount obtained by subtracting the remittance request amount (first amount) included in the remittance request information to be sent to the other user from the remittance request amount (second amount) included in the remittance request information already received from the other user, or a process of receiving from the other user an amount obtained by subtracting the remittance request amount (second amount) included in the remittance request information to be sent to the other user from the remittance request amount (first amount) included in the remittance request information already received from the other user. As an example of the effect of an embodiment obtained by such a configuration, it is possible to send an amount equal to the difference between a first amount and a second amount to the same user, or to receive an amount equal to the difference between the first amount and a second amount from the same user.

[0538] Moreover, this embodiment shows a configuration in which the first process is executed based on an input to the terminal of the other user and based on approval by the other user. As an example of an effect of the embodiment obtained by such a configuration, the first process can be executed based on the input to the terminal of the first user and based on the approval of the first user. This can prevent the first process from being executed against the will of the first user, for example and not by way of limitation.

[0539] <Twelfth Example> The twelfth embodiment is an embodiment relating to processing of the above-mentioned pattern (D). The contents described in the twelfth embodiment are applicable 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.

[0540] In this embodiment, in addition to including "sent remittance requests" among the unprocessed requests as targets for lump-sum settlement, "sent remittance requests" are also included in the lump-sum settlement.

[0541] Let us refer again to the table in FIG. 9-6. In this embodiment, the process is carried out for the pattern (D) sending a remittance request + a sent remittance request. In this pattern, either (D1) remittance request + [remittance request or remittance reminder] or (D2) integrated remittance request can be processed.

[0542] In the process of (D1), when making a new remittance request to the other user, a remittance request to the other user or a remittance reminder to the other user is also made based on a remittance request already sent to the other user.

[0543] In this case, the remittance request based on the already sent remittance request may be treated as the same remittance request as the already sent remittance request, and two different remittance requests, the new remittance request and the already sent remittance request, may be sent to the other user, or the remittance request based on the already sent remittance request may be treated as a remittance reminder, and the new remittance request and the remittance reminder may be sent to the other user.

[0544] In the process of (D2), when making a new remittance request to the other user, an integrated remittance request is sent to the other user as a combined (integrated) request that combines this new remittance request with a remittance request based on a remittance request already sent to the other user.

[0545] <Display screen> An example of the display screen when performing each of the above processes (D1) and (D2) will be described. Fig. 12-1 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment. This screen is, by way of example and not limitation, a remittance request screen of a payment application displayed on the display unit 24 of the terminal 20A of the user AA. As the details of the screen configuration can be configured similarly to Fig. 11-3, by way of example and not limitation, a detailed description will be omitted.

[0546] As a non-limiting example, when the check box for the second remittance request (receive 1,000 yen) is selected as "ON" in the pending request confirmation area URR1 and the remittance request transmission lump-sum settlement button BT13 is tapped, the terminal 20A requests the server 10 to transmit a new remittance request and to lump-sum settle the selected pending requests. The server 10 then transmits the new remittance request information and remittance reminder information based on the past remittance request transmission to the terminal 20E of the other party, user EE, and displays them on the display unit 24 of the terminal 20E.

[0547] FIG. 12-2 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20E when the remittance request transmission lump-sum settlement button BT13 is tapped. In this example, the notification information display area NTR4 of the notification screen displays reminder information regarding the one remittance request selected in Figure 12-1 (in this example, a reminder regarding a remittance request from user AA to user EE for the amount of 1,000 yen) and new remittance request information (in this example, a remittance request from user AA to user EE for the amount of 1,500 yen).

[0548] It is also possible to consolidate new remittance requests with past remittance requests in a bulk settlement process. FIG. 12-3 is a diagram showing an example of a notice screen displayed on the display unit 24 of the terminal 20E in this case. In the notification information display area NTR4, the icon image of user AA, the other party of the "remittance request", and the lump-sum settlement amount are displayed as the lump-sum settlement approval confirmation information. In this example, it is displayed that user EE will pay user AA the lump-sum settlement amount of "2,500 yen", which is the sum of the remittance request amount of "1,000 yen" and the remittance request amount of "1,500 yen".

[0549] In addition, the lump-sum settlement approval confirmation information displays the contents of the lump-sum settlement as follows: User EE will pay the remittance request amount of "1,000 yen" based on the previous remittance request sent by User AA to User EE, and will pay the remittance request amount of "1,500 yen" based on the current remittance request.

[0550] At the bottom of the lump-sum settlement approval confirmation information, there are displayed a settlement button BT15 marked "Settle" for approving the settlement with the above details, and a rejection button marked "Decline" for declining to approve the settlement with the above details.

[0551] FIG. 12-4 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20A when the settlement button BT15 is tapped. Below the current location display area CLR1, a notification NT4 containing a bell mark and the words "A transfer has been made" is displayed as a notification that the lump-sum settlement of the remittance request has been approved from user EE's terminal 20E via server 10, and that as a result, a remittance has been received from user EE.

[0552] Furthermore, in the notification information display area NTR2 of the notification screen, information corresponding to the above notification NT4 is displayed. In this specific example, the settlement result information is displayed after a lump-sum settlement with user EE has been performed. In this example, the settlement result information displays that user AA has received a lump-sum settlement amount of "2,500 yen", which is the sum of the remittance request amount of "1,000 yen" and the remittance request amount of "1,500 yen" to user EE.

[0553] The settlement result information also displays the details of the lump-sum settlement, stating that User AA received a remittance request amount of "1,000 yen" based on a previous remittance request sent to User EE, and received a remittance request amount of "1,500 yen" based on the current remittance request sent.

[0554] <Processing> In this embodiment, the processes executed by each device can be realized in a similar manner to the processes in FIG. 11-6, and therefore illustrations and detailed descriptions thereof will be omitted.

[0555] <Effects of the twelfth embodiment> In this embodiment, the first information is remittance request transmission information for sending a remittance request from the proposer user to the other user (not limited to, but an example of information regarding a remittance request sent from a terminal user to a first user), and the second information is sent remittance request information regarding a remittance request that has already been sent from the proposer user to the other user (not limited to, but an example of information regarding a remittance request sent from a terminal user to a second terminal user). As an example of the effect of an embodiment obtained by such a configuration, a remittance request from a user of a terminal to a first user and a remittance request from a user of a terminal to a user of a second terminal can be processed together.

[0556] Also, in the above, the other user is one user (this is an example, not limiting, of the second user being the first user), and the first process can include a process of sending a remittance request (this is an example, not limiting, of the first remittance request) to the other user based on the remittance request sending information, and sending a remittance request or a remittance reminder (this is an example, not limiting, of the second remittance request) to the other user based on the sent remittance request information. As an example of an effect of the embodiment obtained by such a configuration, a first remittance request to a first user and a second remittance request to the first user can be made simultaneously.

[0557] In addition, in the above, the other user is one user (this is an example, not a limitation, of the second user being the first user), and the first process shows a configuration including a process of sending to the first user an integrated remittance request (this is an example, not a limitation, of a third remittance request) in which the remittance request amount is the sum of the remittance request amount of the remittance request to be sent to the other user and the remittance request amount included in the sent remittance request information. As an example of an effect of an embodiment obtained by such a configuration, by sending a lump sum third remittance request to the first user based on a third amount, which is the sum of the first amount and the second amount, it is possible to effectively prompt the first user to make a remittance to the user of the terminal.

[0558] <Thirteenth Example> The thirteenth embodiment is an embodiment relating to the processing of the above-mentioned pattern (E). The contents described in the thirteenth embodiment are applicable to any of the other embodiments and the other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0559] In this embodiment, in addition to including "received remittance requests" and "sent remittance requests" among the unprocessed requests as targets for lump-sum settlement, "sent remittance requests" are also included in the lump-sum settlement.

[0560] Let us refer again to the table in FIG. 9-6. In this pattern, any of the following processes can be performed: (E1) remittance request + [remittance + receipt] (amount can be deducted), (E2) [receive + remittance] (amount can be deducted) + [remittance request or remittance reminder], (E3) [receive + remittance] (amount can be deducted) + [remittance + receipt] (amount can be deducted).

[0561] In the process of (E1), when making a new remittance request to the other user, remittance and receipt are performed together based on the remittance request already received from the other user and the remittance request already sent to the other user. In this case, the difference in the remittance request amount can be sent / received. Also, if the remittance request amounts are the same, it is possible to offset the amounts.

[0562] In the process of (E2), when making a new remittance request to the other user, the other user remits money based on this new remittance request and receives the money, and also remits money to the other user based on the remittance request already received from the other user. In this case, it is possible to receive / transmit the difference in the remittance request amount. Also, if the remittance request amounts are the same, it is possible to offset the amounts. Also, based on a remittance request already sent to the other user, the same remittance request is sent to the other user, or a remittance reminder is sent to the other user.

[0563] In the process of (E3), when making a new remittance request to the other user, the other user remits money based on this new remittance request and receives the money, and also remits money to the other user based on the remittance request already received from the other user. In this case, it is possible to receive / send the difference in the remittance request amount. Also, if the remittance request amounts are the same, it is possible to offset the amounts. In addition, you can send money to a user based on a remittance request already received from the other user, and receive money from the other user based on a remittance request already sent to the other user. In this case, you can send / receive the difference in the remittance request amount. Also, if the remittance request amounts are the same, you can offset the amounts.

[0564] <Display screen> FIG. 13-1 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment. This screen is, by way of example and not limitation, a remittance request screen of a payment application displayed on the display unit 24 of the terminal 20A of user AA. Details of the screen configuration can be configured similarly to FIG. 11-1, by way of example and not limitation, and therefore will not be described in detail. Note that in FIG. 13-1, by way of example and not limitation, the remittance request amount to the user selected as the destination of the remittance request (user EE in this example) is set to "1,200 yen."

[0565] As a non-limiting example, when the first received remittance request (payment 2,500 yen) and the second sent remittance request (received 1,000 yen) are checked "ON" and selected in the pending request confirmation area URR1 and the remittance request sending lump-sum settlement button BT13 is tapped, the terminal 20A requests the server 10 to send a new remittance request and to lump-sum settle the selected pending requests. Then, the server 10 sends lump-sum settlement approval confirmation information to the terminal 20E of the other party, the user EE, to confirm whether or not to approve the lump-sum settlement, and the information is displayed on the display unit 24 of the terminal 20E.

[0566] FIG. 13-2 is a diagram showing an example of a notification screen that is displayed when the remittance request transmission lump-sum settlement button BT13 is tapped. In the notification information display area NTR4, an icon image of user AA, who is the other party of the "Request Settlement and Remittance Request", and the lump-sum settlement amount are displayed as lump-sum settlement approval confirmation information.

[0567] In this example, the lump-sum settlement approval confirmation information displays the following details of the lump-sum settlement: User EE will receive a remittance request amount of "2,500 yen" based on a previous remittance request sent to User AA, will pay a remittance request amount of "1,000 yen" based on a previous remittance request received from User AA, and will pay a remittance request amount of "1,200 yen" based on the current remittance request received from User AA.

[0568] In addition, the lump-sum settlement approval confirmation information indicates that the lump-sum settlement amount that User EE will receive is "300 yen", which is the sum of the remittance request amount of "2,500 yen" received from User AA minus the remittance request amount of "1,000 yen" to be paid to User AA and the remittance request amount of "1,200 yen".

[0569] At the bottom of the lump-sum settlement approval confirmation information, there are displayed a settlement button BT16 marked "Settle" for approving the settlement with the above details, and a rejection button marked "Decline" for declining to approve the settlement with the above details.

[0570] FIG. 13-3 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20A when the settlement button BT16 is tapped. Below the current location display area CLR1, a notification NT5 containing a bell mark and the words "300 yen has been transferred" is displayed to notify that the lump-sum settlement of the remittance request has been approved from user EE's terminal 20E via server 10, and that the remittance has been made as a result.

[0571] Moreover, in the notification information display area NTR2 of the notification screen, information corresponding to the above notification NT5 is displayed. In this specific example, the settlement result information is displayed after a lump sum settlement has been made with user EE. In this example, the settlement result information displays that user AA paid "300 yen" to user EE as the lump sum settlement amount.

[0572] The settlement result information also displays that, as the contents of the lump-sum settlement, user AA paid the remittance request amount of "2,500 yen" based on receiving a past remittance request from user EE, received the remittance request amount of "1,000 yen" based on sending a past remittance request to user EE, and received the remittance request amount of "1,200 yen" based on sending the current remittance request to user EE.

[0573] <Processing> The processes related to (E1) to (E3) above can be similarly configured based on the processes described in the previous embodiment, and are self-evident, so illustrations and detailed descriptions will be omitted.

[0574] <14th Example> The fourteenth embodiment is an embodiment relating to processing of a pattern different from the patterns described above. The contents described in the fourteenth embodiment are applicable to any of the other embodiments and the other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0575] In addition to the above patterns, as a non-limiting example, the combination patterns of new processing targets in the table in Figure 9-6, that is, Send money + Send a money request It is also possible to perform processing of the above pattern.

[0576] The processing of this pattern is the same as that of pattern (C). In other words, you can perform either of the following operations: "send money + send a remittance request" or "send money + receive money (amount can be deducted)." When performing the process of "transfer + receipt (amount can be deducted)", approval of the other user is required, and approval of the other user may or may not be obtained.

[0577] <Effects of the fourteenth embodiment> In this embodiment, the first information is remittance request information from the proposer's user to the other user, and the proposer's user terminal 20 displays a third display based on the remittance request information (not limited to, but an example of the third information) sent from the proposer's user to the other user on the display unit 24. The proposer's user terminal 20 is configured to perform a second process related to remittance, receipt, or remittance request through the control unit 21 based on an input by the proposer's user to the terminal 20 displaying the remittance display from the proposer's user to the other user (not limited to, but an example of the first display) and the third display. As an example of the effect of the embodiment obtained by such a configuration, remittance, receipt of remittance, or request for remittance can be performed all at once.

[0578] In addition, in the above, the second process is configured to include a process of sending money to the other user based on remittance information (not limited to, an example of the first information) and sending a remittance request to the other user based on remittance request information sent from the proposer user to the other user. As an example of an effect of an embodiment obtained by such a configuration, it is possible to simultaneously perform a remittance to the first user based on the first information and a remittance request to the first user based on the third information.

[0579] In addition, in the above, the second process shows a configuration including a process of transferring an amount based on the amount to be transferred by the proposer user to the other user and the remittance request amount requested by the proposer user to the other user (this is not limited to an example of an amount based on the first information and the third information) to the other user or receiving an amount from the other user. As an example of an effect of the embodiment obtained by such a configuration, an amount based on the first information and the third information can be paid to the first user or received from the first user.

[0580] In this case, the second process is configured to include a process of transferring to the other user an amount obtained by subtracting the amount of a remittance request made by the proposer user to the other user from the amount to be transferred by the proposer user to the other user, or receiving from the other user an amount obtained by subtracting the amount to be transferred by the proposer user to the other user from the amount of a remittance request made by the proposer user to the other user. As an example of an effect of the embodiment obtained by such a configuration, the difference between the first amount and the third amount can be paid to the first user or received from the first user.

[0581] In this case, the second process may be executed based on the approval of the other user (not limited to this, an example of the first user) based on an input to the terminal 20 of the other user. As an example of an effect of the embodiment obtained by such a configuration, the second process can be executed based on the input to the terminal of the first user and based on the approval of the first user. This can prevent the second process from being executed against the will of the first user, for example and not by way of limitation.

[0582] <Fifteenth Example> The fifteenth embodiment, like the fourteenth embodiment, is an embodiment relating to processing of a pattern different from the patterns described above. The contents described in the fifteenth embodiment are applicable 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.

[0583] In addition to the patterns mentioned above, by way of example and not limitation, the combinations of pending requests shown horizontally in the table in Figure 9-6, namely: · Received transfer requests + Sent requests It is also possible to perform processing of the above pattern.

[0584] The processing of this pattern is the same as that of pattern (B). In other words, you can perform either of the following operations: "send money + receive money (amount can be deducted)" or "send money + send a remittance request." When performing the process of "transfer + receipt (amount can be deducted)", approval of the other user is required, and approval of the other user may or may not be obtained.

[0585] <Effects of the 15th embodiment> In this embodiment, the second information is remittance request information from the other user to the proposer's user, and the proposer's user terminal 20 displays on the display unit 24 a fourth display based on the sent remittance request information (not limiting, an example of the fourth information) sent from the proposer's user to the other user. The proposer's user terminal 20 is configured to perform a third process related to remittance, receipt, or remittance request by the control unit 21 based on an input to the terminal 20 displaying the second display based on the received remittance request information (not limiting, an example of the second information) related to the received remittance request that the proposer's user has received from the other user, and the fourth display. As an example of the effect of the embodiment obtained by such a configuration, remittance, receipt of remittance, or request for remittance can be performed all at once.

[0586] The third process includes a process of sending money to the other user based on the received remittance request information, and a process of sending a remittance request to the other user based on the sent remittance request information. As an example of an effect of an embodiment obtained by such a configuration, it is possible to simultaneously perform a remittance to the second user based on the second information and a remittance request to the second user based on the fourth information.

[0587] The third process includes a process of remitting an amount based on the received remittance request information and the transmitted remittance request information to the other user or receiving an amount based on the received remittance request information and the transmitted remittance request information from the other user. As an example of an effect of the embodiment obtained by such a configuration, an amount based on the second information and the fourth information can be paid to the second user or received from the first user.

[0588] In addition, the above-mentioned third process shows a configuration including a process of transferring an amount obtained by subtracting the remittance request amount of the transmitted remittance request information from the remittance request amount of the received remittance request information to the other user, or receiving an amount obtained by subtracting the remittance request amount of the transmitted remittance request information from the remittance request amount of the received remittance request information from the other user. As the amount of money obtained by this configuration in the embodiment, the difference between the second amount and the fourth amount can be paid to the second user or received from the second user.

[0589] In this case, the third process may be executed based on the approval of the other user (not limited to this, an example of a second user) based on an input to the terminal 20 of the other user. As an example of the effect of the embodiment obtained by such a configuration, the third process can be executed based on the second user's approval based on the input to the second user's terminal. This makes it possible to prevent the third process from being executed against the second user's will, for example and not by way of limitation.

[0590] <16th Example> The sixteenth embodiment is an embodiment relating to a method for displaying remittance request information. The contents described in the sixteenth embodiment are applicable to any of the other embodiments and the other modified examples. Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

[0591] <Display screen> 14-1 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment. This screen is, by way of example and not by way of limitation, a remittance screen of a payment application displayed on the display unit 24 of the terminal 20A of user AA. Below the current location display area CLR1, an icon image of the payment application of the user selected as the remittance destination and the user name (user CC in this example) are displayed.

[0592] Below the function button for increasing the remittance amount by a fixed amount is displayed an outstanding request confirmation area URR3, which is configured to enable confirmation of outstanding requests between the user selected as the remittance recipient (user CC in this example) and the user making the remittance (user AA in this example).

[0593] At the top of the unprocessed request confirmation area URR3, the words "Unsettled request with CC" are displayed, indicating that an unprocessed request with user CC is being displayed. To the right of this is a remittance request history sort button STB1 for changing the display order of unprocessed remittance requests. The other display aspects are the same as those in the unprocessed request confirmation area URR1.

[0594] When the remittance request history sort button STB1 is touched, by way of example and not limitation, a sort selection area for selecting a sort order appears popping up from the bottom of the screen. Based on user operations on the sort selection area, the display order of unprocessed remittance requests can be rearranged and displayed in ascending / descending order, for example but not limited to, by the date the remittance request was sent / received, or by the remittance request amount of the remittance request.

[0595] It is also possible to rearrange and display the unprocessed remittance requests in the order of the date and time when the remittance requests were sent / received, instead of in the order of the date when the remittance requests were sent / received.

[0596] FIG. 14-2 is a diagram showing an example of a display screen in which remittance requests in the outstanding request confirmation area URR3 are sorted in descending order by remittance request amount based on a user operation on the sort selection area, by way of example and not by limitation.

[0597] In FIG. 14-1, the remittance requests in the pending request confirmation area URR3 are sorted in ascending order based on date, whereas in FIG. 14-2, they are sorted in descending order based on the remittance request amount.

[0598] In addition, when a payment deadline is set for a remittance request, by way of example and not limitation, the remittance requests may or may not be displayed in the order in which the payment deadline approaches. Setting a payment deadline includes, by way of example and not limitation, setting a repayment deadline for a loan from a financial institution or other business operator (CtoB) in addition to payments between general users (CtoC).

[0599] In addition, remittance requests in which the amount or reason of the remittance request is related to a user other than the user who made the remittance request and the user to whom the remittance request is made may be preferentially displayed, for example and without limitation, in cases where the other user is included as a member of a split payment.

[0600] In addition, the pending request confirmation area URR3 displays pending remittance requests, but is not limited to this.

[0601] FIG. 14-3 is an example of a display screen in which processed remittance requests are mixed in with the unprocessed request confirmation area URR3. In Figure 14-3, by way of example and not limitation, the first remittance request in the pending request confirmation area URR3 shows that a remittance request for the payment of the remittance request amount "1,000 yen" has been received, and is displayed in a grayed-out manner to indicate that it is a processed remittance request. Processed remittance requests are not selected for lump-sum settlement, so there is no check area.

[0602] <Effects of the 16th embodiment> In this embodiment, the terminal 20 of the proposer's user displays on the display unit 24 a fourth display based on remittance request information regarding a received remittance request that the proposer's user has received from the other user (not limited to, an example of fourth information regarding a remittance request sent from a second user to the terminal user) or remittance request information regarding a sent remittance request that the proposer's user has sent to the other user (not limit...

Claims

1. A program executed by a server in communication with a terminal, transmitting, via a communication unit of the server, to the terminal, first information relating to a remittance request from a first user to a user of the terminal or from the user of the terminal to the first user, and second information relating to a remittance request from the first user to the user of the terminal or from the user of the terminal to the first user; performing a first process by a control unit of the server, based on an input to the terminal by a user of the terminal, for transferring a first amount from the balance of the user of the terminal to the first user, or for requesting the first user to transfer a second amount, based on the first information and the second information; Based on the first process, the server executes transmitting to the terminal via the communication unit information on the first amount transferred from the balance of the user of the terminal to the first user, or information on the second amount requested by the user of the terminal to the first user.

2. The program according to claim 1, The first information includes information of a third amount related to the remittance request, The second information includes information of a fourth amount related to the remittance request; The first process is performed by the control unit based on the third amount, the fourth amount, and a balance of the user of the terminal.

3. The program according to claim 1 or 2, The first processing is performed based on the first information and the second information, based on input by the user of the terminal to the terminal, of a request to remit to the user of the terminal, or a plurality of pieces of information regarding a remittance request by the user of the terminal, which includes at least the first information and the second information.

4. The program according to claim 1 or 2, The server executes a second process by the control unit to process at least one piece of information related to a remittance request to the user of the terminal or a remittance request by the user of the terminal based on the balance of the user of the terminal.

5. An information processing method for a server communicating with a terminal, comprising: transmitting, via a communication unit of the server, to the terminal, first information relating to a remittance request from a first user to a user of the terminal or from the user of the terminal to the first user, and second information relating to a remittance request from the first user to the user of the terminal or from the user of the terminal to the first user; performing a first process by a control unit of the server, based on an input to the terminal by a user of the terminal, for transferring a first amount from the balance of the user of the terminal to the first user, or for requesting the first user to transfer a second amount, based on the first information and the second information; The method includes transmitting, to the terminal via the communication unit, information on the first amount transferred from the balance of the user of the terminal to the first user, or information on the second amount requested by the user of the terminal to the first user, based on the first process.

6. A server that communicates with a terminal, a communication unit that transmits to the terminal first information related to a remittance request from a first user to a user of the terminal or from the user of the terminal to the first user, and second information related to a remittance request from the first user to the user of the terminal or from the user of the terminal to the first user; a control unit that performs a first process related to transferring a first amount from the balance of the user of the terminal to the first user or requesting the first user to transfer a second amount based on the first information and the second information, based on an input to the terminal by a user of the terminal; The communication unit transmits to the terminal, based on the first process, information on the first amount transferred from the balance of the user of the terminal to the first user, or information on the second amount requested by the user of the terminal to the first user.

Images