JP2022011965A - Program, information processing method, and terminal - Google Patents

Abstract

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

Description

The present disclosure relates to programs, information processing methods, and terminals.

In recent years, services that realize management of electronic money (electronic money) of a terminal or a user of the terminal, remittance / receipt, etc. by an application that can be executed on a terminal such as a smartphone are becoming widespread. For example, Patent Document 1 discloses a technique for settling the purchase price of a product.

Japanese Unexamined Patent Publication No. 2002-176671

According to the first aspect of the present invention, the program executed by the terminal transmits the first information regarding the remittance from the first user to the user of the terminal or the remittance request transmitted from the first user to the user of the terminal. Remittance request sent from the second user to the user of the terminal based on the reception of the first information and the display of the first display based on the first information on the display unit of the terminal. Alternatively, the terminal displays the second display based on the second information regarding the remittance request sent from the terminal user to the second user on the display unit, and the terminal user displays the first display and the second display. Based on the input to, the terminal performs the first processing regarding the remittance, the receipt of the remittance, or the request for the remittance by the control unit of the terminal.
According to the second aspect of the present invention, in the information processing method of the terminal, the first information regarding the remittance from the first user to the user of the terminal or the remittance request transmitted from the first user to the user of the terminal is transmitted to the terminal. Remittance request sent from the second user to the user of the terminal based on the reception by the communication unit and the first display based on the first information is displayed on the display unit of the terminal, or based on the reception of the first information. Displaying the second display based on the second information regarding the remittance request sent from the terminal user to the second user on the display unit, and the terminal user displaying the first display and the second display. Based on the input, the first process relating to the remittance, the receipt of the remittance, or the request for the remittance is performed by the control unit of the terminal.
According to the third aspect of the present invention, the terminal is a communication unit that receives the first information regarding the remittance from the first user to the user of the terminal or the remittance request transmitted from the first user to the user of the terminal. The first display based on the first information is displayed, and the remittance request sent from the second user to the terminal user or the remittance request sent from the terminal user to the second user based on the reception of the first information is displayed. Remittance, or receipt of remittance, based on the input to the terminal displaying the first and second displays by the display unit that displays the second display based on the second information about. It is provided with a control unit that performs the first process related to the remittance request.
According to a fourth aspect of the present invention, the terminal comprises a processor that reads a program stored in a memory and executes a process based on the program, and the processor relates to or a remittance from a first user to a user of the terminal. 1 To receive the first information about the remittance request sent from the user to the user of the terminal by the communication unit of the terminal, and to display the first display based on the first information on the display unit of the terminal to receive the first information. Based on this, the display unit displays a second display based on the second information regarding the remittance request sent from the second user to the user of the terminal or the remittance request sent from the user of the terminal to the second user. Based on the input by the user of the terminal to the terminal on which the first display and the second display are displayed, the first process relating to the remittance, the receipt of the remittance, or the request for the remittance is executed.

The figure which shows an example of the structure of the communication system in one aspect of Embodiment. The figure which shows an example of the function realized by the control part of the server which concerns on 1st Embodiment. The figure which shows an example of the information stored in the storage part of the server which concerns on 1st Embodiment. The figure which shows an example of the user registration data which concerns on 1st Embodiment. The figure which shows an example of the user management database which concerns on 1st Embodiment. The figure which shows an example of the remittance request management data which concerns on 1st Example. The figure which shows an example of the function realized by the control part of the terminal which concerns on 1st Embodiment. The figure which shows an example of the information stored in the storage part of the terminal which concerns on 1st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 1st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 1st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 1st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 1st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 1st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 1st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 1st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 1st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 1st Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 1st Embodiment. The flowchart which shows an example of the flow of the settlement process which concerns on 1st Example. The figure which shows an example of the table for demonstrating the batch settlement which concerns on 1st Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 1st Embodiment. The flowchart which shows an example of the flow of the settlement process which concerns on 1st Example. The figure which shows an example of the display screen of the terminal which concerns on the 1st modification. The figure which shows an example of the display screen of the terminal which concerns on the 1st modification. The figure which shows an example of the display screen of the terminal which concerns on 2nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 2nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 2nd Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 2nd Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 2nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 3rd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 3rd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 4th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 4th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 5th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 5th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 6th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 6th Embodiment. The flowchart which shows an example of the flow of the batch remittance request creation process which concerns on 6th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 7th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 7th Embodiment. The flowchart which shows an example of the flow of the settlement process which concerns on 7th Embodiment. The flowchart which shows an example of the flow of the settlement process which concerns on 7th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 8th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 8th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 8th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 8th modification. The figure which shows an example of the table for demonstrating the processing method which concerns on 9th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 9th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 9th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 9th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 9th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 9th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 10th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 10th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 10th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 10th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 10th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 10th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on eleventh embodiment. The figure which shows an example of the display screen of the terminal which concerns on eleventh embodiment. The figure which shows an example of the display screen of the terminal which concerns on eleventh embodiment. The figure which shows an example of the display screen of the terminal which concerns on eleventh embodiment. The figure which shows an example of the display screen of the terminal which concerns on eleventh embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on eleventh embodiment. The figure which shows an example of the display screen of the terminal which concerns on the twelfth embodiment. The figure which shows an example of the display screen of the terminal which concerns on the twelfth embodiment. The figure which shows an example of the display screen of the terminal which concerns on the twelfth embodiment. The figure which shows an example of the display screen of the terminal which concerns on the twelfth embodiment. The figure which shows an example of the display screen of the terminal which concerns on 13th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 13th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 13th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 16th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 16th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 16th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 17th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 17th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 17th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 17th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 17th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on the 17th modification. The figure which shows an example of the table for demonstrating the processing method which concerns on 18th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 18th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 18th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 18th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 19th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 19th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 20th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 20th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 20th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 20th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 21st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 21st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 21st Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 21st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 22nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 22nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 22nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 22nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 26th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 26th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 27th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 27th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 27th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 27th Embodiment.

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

An embodiment for implementing the program and the like according to the present disclosure will be described with reference to the drawings.

In the present specification, the expression "by communication I / F" is used as appropriate. This indicates that the device sends and receives various information and data via the communication I / F (via the communication unit) based on the control of the control unit (processor or the like), for example, without limitation. ..

<System configuration>
FIG. 1-1 is a diagram showing an example of the system configuration of the communication system 1 in this embodiment.
In the communication system 1, the server 10 and a plurality of terminals 20 (terminals 20A, terminals 20B, terminals 20C, ...) Are connected to each other via a network 30 as an example, not limited to the above.

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, or the like. In the present embodiment, as an example, not limited to, the user of the server 10 is a payment service operator or a messaging service operator.

The terminal 20 (terminal 20A, terminal 20B, terminal 20C, ...) Can be any terminal as long as it is an information processing terminal capable of realizing the functions described in each embodiment. The terminal 20 is not limited but, as an example, a smartphone, a mobile phone (feature phone), a computer (not limited, as an example, a desktop, a laptop, a tablet, etc.), a media computer platform (not limited, as an example, a cable, a satellite set). Top boxes, digital video recorders), handheld computer devices (not limited to, for example, PDAs (personal digital assistants), e-mail clients, etc.), wearable terminals (glasses-type devices, clock-type devices, etc.), VR (Virtual Reality) Includes terminals, smart speakers (devices for voice recognition), or other types of computers, or communication platforms. Further, the terminal 20 may be expressed as an information processing terminal.

The configurations of the terminal 20A, the terminal 20B and the terminal 20C are basically the same. Further, if necessary, the terminal used by the user X may be expressed as the terminal 20X, and the user information in the predetermined service associated with the user X or the terminal 20X may be expressed as the user information X.
The user information is user information associated with an account used by the user in a predetermined service. User information is not limited, but as an example, input by the user or given by a predetermined service, the user's name, the user's icon image, the user's age, the user's gender, the user's address, the user's hobby. It includes information associated with the user such as taste, user's identifier, and may or may not be any one or combination of these.

The network 30 is responsible for connecting one or more terminals 20 and one or more servers 10. That is, the network 30 means a communication network that provides a connection route so that data can be transmitted and received after the above-mentioned various devices are connected.
The number of servers 10 and the number of terminals 20 connected to the network 30 are not limited.

One or more parts of the network 30 may or may not be a wired or wireless network. The network 30 is not limited, but by example, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), and a wireless. LAN (wireless LAN: WLAN), wide area network (WAN), wireless WAN (wireless WAN: WWAN), metropolitan area network (MAN), part of the Internet, public exchange telephone network (Public) Part of Switched Telephone Network (PSTN), mobile phone network, ISDN (integrated service digital networks), wireless LAN, LTE (long term evolution), CDMA (code division multiple access), Bluetooth (Bluetooth (registered trademark)), satellite It can include communication, etc., or a combination of two or more of these. The network 30 may include one or more networks 30.

The server 10 (not limited to an example of a server, an information processing device, and an information management device) has a function of providing a predetermined service (payment service, messaging service, etc. in this embodiment) to the terminal 20. The server 10 may be any device as long as it can realize the functions described in each embodiment. The server 10 is not limited, but by example, a server device, a computer (not limited, by example, a desktop, a laptop, a tablet, etc.), a media computer platform (not limited, by example, a cable, a satellite set-top box, a digital video recorder). ), Handheld computer devices (for example, but not limited to, PDA, e-mail client, etc.), or other types of computers, or communication platforms. Further, the server 10 may 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, respectively.

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

(1) HW configuration of the terminal FIG. 1-1 shows an example of the HW configuration of the terminal 20.
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. .. Each component of the HW of the terminal 20 is connected to each other via the bus B as an example, but not a limitation. It is not essential that the HW configuration of the terminal 20 includes all the components. As an example, but not limited to, the terminal 20 may or may not be configured to remove individual components or a plurality of components.

The communication I / F 22 transmits / receives various data via the network 30. Communication may be performed by wire or wirelessly, and any communication protocol may be used as long as communication with each other can be performed. The communication I / F 22 has a function of executing communication with various devices such as a 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. Further, the communication I / F 22 receives various data transmitted from various devices such as the server 10 and transmits the various data to the control unit 21. Further, the communication I / F 22 may be simply expressed as a communication unit. Further, when the communication I / F 22 is composed of a physically structured circuit, it may be expressed as a communication circuit.

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

The input unit is realized by any or a combination of all kinds of devices capable of receiving input from the user and transmitting information related to the input to the control unit 21. The input unit includes, but is not limited to, hardware keys such as a touch panel, a touch display, and a keyboard, a pointing device such as a mouse, a camera (operation input via a moving image), and a microphone (operation input by voice).

The output unit is realized by any or a combination of all kinds of devices capable of outputting the processing result processed by the control unit 21. The output unit includes, as an example, not limited, a touch panel, a touch display, a speaker (audio output), a lens (not limited, as an example, 3D (three dimensions) output, hologram output), a printer, and the like.

As one embodiment, the input / output unit 23 includes, but is not limited to, a display unit 24, a sound input unit 25, a sound output unit 26, and an image pickup unit 27.

The display unit 24 is realized by any or a combination of all kinds of devices that can be displayed according to the display data written in the frame buffer. The display unit 24 is not limited but, as an example, a touch panel, a touch display, a monitor (not limited but, as an example, a liquid crystal display or an OLELD (organic electroluminescence display)), a head mounted display (HDM), a projection mapping, a hologram. , Includes a device capable of displaying images, text information, etc. in air (which may or may not be vacuum). It should be noted that these display units 24 may or may not be able to display display data in 3D.

The sound input unit 25 is used for inputting sound data (including voice data; the same applies hereinafter). The sound input unit 25 includes a microphone and the like.
The sound output unit 26 is used for outputting sound data. The sound output unit 26 includes a speaker and the like.
The image pickup unit 27 is used for acquiring moving image data. The image pickup unit 27 includes a camera and the like.

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

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, a clock using a crystal oscillator and the like, without limitation. The clock unit 29A can be expressed as a time measuring unit or a time information detecting unit as an example without limitation.

The clock unit 29A may or may not have a clock to which the NITZ (Network Identity and Time Zone) standard or the like is applied.

The position calculation information detection unit 29B has a function of detecting (measuring) information necessary for the control unit 21 to calculate (measure) the position of its own terminal 20 (hereinafter referred to as "position calculation information"). It is a department. The position calculation information detection unit 29B can be expressed as a position calculation sensor unit as an example without limitation.

The position calculation information detection unit 29B is not limited to the satellite positioning sensor (satellite positioning), 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). Unit), a sensor for calculating the position of the terminal 20 using an inertial navigation system, an inertial measurement sensor (IMU (Inertial Measurement Unit)), and a UWB (Ultra Wide). Band) includes a sensor for calculating the position of the terminal 20 and a UWB positioning sensor (UWB positioning unit) which is a unit.

The satellite positioning unit is not limited to, for example, an RF receiving circuit that converts an RF (Radio Frequency) signal including a positioning satellite signal transmitted from a positioning satellite received by an antenna (not shown) into a digital signal. Correlation calculation processing is performed on the digital signal output from the RF reception circuit to capture the positioning satellite signal, and information such as satellite orbit data and time data extracted from the positioning satellite signal is used as position calculation information. It has a baseband processing circuit to output.

The inertial measurement unit has an inertial sensor, which is a sensor that detects information necessary for calculating the position of the terminal 20 by inertial navigation calculation. The inertial sensor includes, for example, a 3-axis acceleration sensor and a 3-axis gyro sensor, and the acceleration detected by the acceleration sensor and the angular velocity detected by the gyro sensor are used as position calculation information. Output.

The UWB positioning unit, as an example, is not limited to, and converts an ultra-wideband RF (Radio Frequency) signal including a positioning ultra-wideband pulse signal transmitted from a positioning beacon received by an antenna (not shown) into a digital signal. It has a wideband RF receiving circuit, a relative position calculation processing circuit that calculates the relative position between the terminal 20 and the positioning beacon based on a digital signal output from the ultra-wideband RF receiving circuit, and the like.
As an example without limitation, the UWB positioning unit may make the terminal 20 function as a positioning beacon by transmitting an ultra-wideband RF signal including a positioning ultra-wideband pulse signal from an antenna (not shown). You don't have to.

As an example, the control unit 21 calculates the position of its own terminal 20 at a periodic timing or a specific timing based on the position calculation information detected by the position calculation information detection unit 29B. The position of the terminal is referred to as "terminal position", and the calculated terminal position is referred to as "calculated terminal position". Then, the control unit 21 associates the calculated terminal position with the calculated date and time and stores the calculated terminal position in the storage unit 28 as the calculated terminal position history data.

The control unit 21 has a circuit physically structured to execute a function realized by a code or an instruction contained in the program, and is not limited, but as an example, a data processing device built in hardware. Is realized by. Therefore, the control unit 21 may or may not be expressed as a control circuit.

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

The storage unit 28 has a function of storing various programs and various data required for the terminal 20 to operate. The storage unit 28 includes various storage media such as HDD (hard disk drive), SSD (solid state drive), flash memory, RAM (random access memory), and ROM (read only memory) as examples without limitation. Further, the storage unit 28 may or may not be expressed as a memory.

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

(2) HW configuration of the server FIG. 1-1 shows an example of the HW configuration of the server 10.
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. Each component of the HW of the server 10 is connected to each other via bus B, as an example, but not by 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. As an example, but not limited to, the HW of the server 10 may or may not be configured to remove individual components or a plurality of components.

The control unit 11 has a circuit physically structured to execute a function realized by a code or an instruction contained in the program, and is not limited, but as an example, a data processing device built in hardware. Is realized by.

The control unit 11 is typically a central processing unit (CPU), and may or may not be a microprocessor, a processor core, a multiprocessor, an ASIC, or an FPGA. In the present disclosure, the control unit 11 is not limited to these.

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

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

The input / output unit 12 is realized by a device that inputs 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 the user and transmitting information related to the input to the control unit 11. The input unit is typically realized by a hardware key typified by a keyboard or the like, or a pointing device such as a mouse. The input unit may or may not include, as an example, a touch panel, a camera (operation input via a moving image), and a microphone (operation input by voice), without limitation.

The output unit is realized by any one or a combination of all kinds of devices capable of outputting the processing result processed by the control unit 11. The output unit includes, as an example, not limited, a touch panel, a touch display, a speaker (audio output), a lens (not limited, as an example, 3D (three dimensions) output, hologram output), a printer, and the like.

As a primary embodiment, the input / output unit 12 includes a display unit 13.

The display unit 13 is typically realized by a monitor (not limited, but as an example, a liquid crystal display or an OELD (organic electroluminescence display)). The display unit 13 may or may not be a head-mounted display (HDM) or the like. It should be noted that these display units 13 may or may not be able to display display data in 3D. In the present disclosure, the display unit 13 is not limited to these.

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, an RTC (Real Time Clock) as a hardware clock, a system clock, or the like, without limitation. The clock unit 19 is not limited, but may be expressed as a time measuring unit or a time information detecting unit as an example.

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

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

The control unit 21 of the terminal 20 and / or the control unit 11 of the server 10 are formed not only in a CPU having a control circuit but also in an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)) and the like. Each process may or may not be realized by a logic circuit (hardware) or a dedicated circuit. Further, these circuits may be realized by one or a plurality of integrated circuits, and the plurality of processes shown in each embodiment may or may not be realized by one integrated circuit. In addition, LSI may be referred to as VLSI, super LSI, 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.

Further, the program P (not limited to, as an example, a software program, a computer program, or a program module) of each embodiment of the present disclosure may be provided in a state of being stored in a storage medium readable by a computer. It does not have to be done. The storage medium can store the program P in a "non-temporary tangible medium". Further, the program P may or may not be for realizing a part of the functions of each embodiment of the present disclosure. Further, it may or may not be a so-called difference file (difference program) that can realize the functions of each embodiment of the present disclosure in combination with the program P already recorded in the storage medium.

The storage medium may be one or more semiconductor-based or other integrated circuits (ICs) (for example, but not limited to field programmable gate arrays (FPGAs) or application-specific ICs (ASICs)), hard disks. Disk drive (HDD), hybrid hard drive (HHD), optical disk, optical disk drive (ODD), optical magnetic disk, optical magnetic drive, floppy diskette, floppy disk drive (FDD), magnetic tape, solid It can include a drive (SSD), a RAM drive, a secure digital card, or drive, any other suitable storage medium, or any suitable combination of two or more thereof. The storage medium may be volatile, non-volatile, or a combination of volatile and non-volatile, where appropriate. The storage medium is not limited to these examples, and may be any device or medium as long as the program P can be stored. Further, the storage medium may or may not be expressed as a memory.

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

Further, 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 (communication network, broadcast wave, etc.) capable of transmitting the program. .. The server 10 and / or the terminal 20 is not limited to, but as an example, by executing the program P downloaded via the Internet or the like, the functions of the plurality of functional units shown in each embodiment are realized.
The same applies to other devices.

In addition, each embodiment of the present disclosure can also be realized in the form of a data signal in which the program P is embodied by electronic transmission.
At least part of the processing in the server 10 and / or the terminal 20 may or may not be realized by cloud computing composed of 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 of the processing of each functional unit of the control unit 21 of the terminal 20 or all the processing 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 of the processing of each functional unit of the control unit 11 of the server 10 or all the processing may or may not be performed by the terminal 20.
Unless explicitly mentioned, the configuration of the determination in the embodiment of the present disclosure is not essential, and a predetermined process may be operated when the determination condition is satisfied, or a predetermined process may be performed when the determination condition is not satisfied. It may or may not be.

The program disclosed in this disclosure is not limited to the use of script languages such as ActionScript and JavaScript (registered trademark), compiler languages such as Objective-C and Java (registered trademark), and markup languages such as HTML5. Will be implemented.

Hereinafter, an embodiment in which the present invention is realized by a server-client system will be described.

However, the present invention can be realized not only by a server-client system but also by a system that does not include a server. This is not a limitation, but as an example, the following system.
-A system that gives the terminal 20 the function of a server (distributed system). This can be achieved by using blockchain (chain) technology as an example, not a limitation.
-A system in which terminals 20 communicate wirelessly with each other. This is not limited, but can be realized by communicating by a P2P (peer-to-peer) method or the like using a short-range wireless communication technology such as Bluetooth as an example.

Further, in the following, the expression "by communication I / F" is used as appropriate. This indicates that the device sends and receives various information and data via the communication I / F (via the communication unit) based on the control of the control unit (processor or the like) as an example, not limited to the device. ..

<Overview>
In recent years, as applications related to network services (application software), applications for making payments in electronic currency (payment applications), applications for making payments in electronic currency (payment applications), and sending / receiving in electronic currency are performed. Applications such as applications for money transfer (money transfer applications) and applications that aggregate some or all of the functions of these applications are becoming widespread, and users of the terminal 20 can use these applications for electronic currency (electronic). It has become possible to receive various services using money).

The "electronic money" is an electronic money that is distinguished from physical money, and means the terminal 20 managed in the above-mentioned various applications or the electronic money owned by the user of the terminal 20.

Note that electronic money may or may not be expressed as "electronic money" or "digital currency (digital currency)".
Further, legal tender or virtual currency may be used as "electronic money (electronic money)" or "digital currency (digital currency)".
In addition, cryptocurrency (cryptocurrency) may be included in "electronic money (electronic money)" and "digital currency (digital currency)".
Further, the virtual currency may include physical money such as a coupon.

In the present specification, the term "electronic money" is used as an example, and the balance of the electronic money account of the user of the terminal 20 is referred to as "electronic money account balance" as an example without limitation.

Further, in the following, requesting a user of a different terminal 20 (a other user) to perform a remittance from a user of the terminal 20 is referred to as a "remittance request" (synonymous with a remittance request). The information regarding this remittance request is referred to as "remittance request information".
Requesting remittance may be expressed as "requesting remittance", "requesting remittance", etc.
In addition, the request for remittance may be expressed as "a remittance request", "a remittance request is made", or the like.

Further, sending a remittance request is expressed as "sending a remittance request", "sending a remittance request", etc., but these are substantially synonymous.
Conversely, receiving a remittance request is expressed as "receiving a remittance request", "receiving a remittance request", etc., but these are substantially synonymous.

In the following, the term that means to remind, remind, reconfirm, etc. the contents of the remittance request to the other user is referred to as "remittance reminder", and the information about this remittance reminder is referred to as "remittance reminder information". It is called.
Remittance remittance may be expressed as "remittance remittance", "remittance remittance", etc.
In addition, remittance reminders may be expressed as "remittance reminders", "remittance reminders", and the like.

In addition, the remittance request information (the same applies to the remittance reminder information) includes at least information indicating that the remittance has been requested, information on the user of the remittance requester (remittance request source), and information on the user of the remittance request destination. It should be.

As will be described later, information such as the amount for which remittance is requested (hereinafter referred to as "remittance request amount"), the reason for remittance, and the deadline for payment by remittance (hereinafter referred to as "payment deadline") is provided. It can also be included in the remittance request information.

Further, in the following, it will be described that various processes according to the present invention are executed by the application (payment application or messaging application) installed in the terminal 20.

It should be noted that a chat service (not limited but a messaging service as an example) function is provided as one function of the payment application, or a payment service function is provided as a function of the chat application (not limited but an example messaging application). You can also do it.

The messaging service is configured to allow users to chat using a chat room.
In the following description, a UI (User Interface) or GUI (Graphical User Interface) that allows each user to browse content transmitted / received between terminals of a plurality of users is appropriately referred to as a "talk room". Further, the talk room may be referred to as a chat room.

The talk room is not limited to the talk room of one-to-one users, and may include a talk room of a group including a plurality of users (group talk room). In this case, the talk room means a UI or GUI that allows users included in the group to view contents transmitted / received between terminals of the group including a plurality of users.

Further, the messaging service may or may not include an instant messaging service (IMS: Instant Messaging Service) that enables transmission and reception of contents such as simple messages between terminals 20.

There is also an idea that the messaging service: MS (including IMS) is regarded as one form (one form) of the social networking service: SNS.
Therefore, the messaging service: MS and the social networking service: SNS may or may not be distinguished.

<Example>
Hereinafter, examples to which the present invention is applied will be described.
Multiple remittance requests are sent to the terminal without processing the remittance request (remittance request) from the other user (first user) to yourself (terminal user) or the remittance request (remittance request) from yourself to the other user. It may accumulate in 20. As an example, not a limitation, if you inadvertently forget to process a remittance request.

In this case, it is inconvenient to process unprocessed remittance requests one by one because it takes time. In addition, if you try to process unprocessed remittance requests one by one, the user's balance may run out.

Therefore, a method for collectively processing a plurality of remittance requests (here, a plurality of unprocessed remittance requests) will be described. This batch processing is called "batch processing".
The batch processing can be broadly divided into at least the following processing.
(1) Processing related to batch settlement (hereinafter referred to as "collective settlement") (2) Processing related to offsetting remittance requests (hereinafter referred to as "request offset") (3) Batch remittance request (hereinafter referred to as "request offset") , Processing related to creation of "Batch remittance request" (4) Processing related to special batch settlement (hereinafter referred to as "special batch settlement") ・ Special batch remittance request (hereinafter referred to as "special batch remittance request") ) Process related to creation

Further, 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) is illustrated.
As will be described in a modified example, when the other user is a plurality of different users, that is, the first user is a user different from the second user (the second user is a user different from the first user). In some cases, the method described below can be applied in the same manner.

<First Example>
The first embodiment is an example relating to batch settlement among the above batch processes.
The contents described in the first embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

<Functional configuration>
(1) Server FIG. 1-2 is a diagram showing an example of a function realized by the control unit 11 of the server 10 in this embodiment.
The control unit 11 of the server 10 is not limited to, but as an example, in order to provide various payment services by the payment application to the terminal 20 or the user of the terminal 20 according to the payment application management processing program 151 stored in the storage unit 15. The payment application management processing unit 111 that performs the processing of is included as a functional unit.

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 storage unit 15, as an example, is not limited to the payment application management processing program 151, which is read by the control unit 11 and executed as the payment application management process, the user registration data 153, the user management database 155, and the remittance request. The management data 157 and the like are stored.

The user registration data 153 is registration data relating to the terminal 20 using the payment application or the user of the terminal 20, and an example of the data structure is shown in FIG. 1-4.
In the user registration data 153, as an example, the user name, the application ID, the terminal telephone number, and other registration information are stored in association with each other.

The user name is the name of the user of the terminal 20 who uses the payment application, and the name registered when the user of the terminal 20 uses the payment application is stored as an example without limitation.

The application ID is the information used to identify the account of the payment application, or the account itself.
This application ID is preferably a unique value for each account, and is not limited, but as an example, a unique value (unique value) is set and stored for each account by the server 10.
The application ID is information associated with the terminal 20 or the user of the terminal 20, and is an example of information about the terminal or information about the user of the terminal.

The terminal telephone number is the telephone number of the terminal 20 of the user with this user name, and the telephone number of the terminal 20 registered when the user of the terminal 20 uses the payment application is stored as an example without limitation.

Other registration information includes, as an example, not a limitation, the ID of the terminal 20: the terminal ID (IMEI (International Mobile Equipment Identity), as an example, not the limitation), and the email address (terminal email address) of the terminal 20 of the user with this user name. ), Information such as authentication information such as passwords (login password, authentication password) used for various authentications in payment applications can be included.

The identification information for identifying the terminal 20 is not limited, but may be a terminal ID as an example.
Further, the identification information for identifying the user of the terminal 20 is not limited, but may be an application ID as an example. It should be noted that this may or may not be a "user ID".

Further, in the case of an application in which only one account can be registered for one terminal 20, the application is not limited, but as an example, "identification information for identifying the terminal 20 = identification information for identifying the user of the terminal 20 =". It can be an application ID.

Further, as an example, not limited to, it may be possible to assign a plurality of terminal IDs to one user ID, and it is not necessary to do so.

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

It is also possible to apply a method of managing an account by a terminal telephone number instead of various IDs such as an application ID. In this case, instead of storing the ID such as the application ID in the user registration data 153, the terminal telephone number can be stored in the user registration data 153.

The user management database 155 is a database that stores data for managing information about the terminal 20 that uses the payment application or the user, and is an example of the configuration of the first user management database 155A. It is shown in FIG. 1-5.

User management data is stored in the first user management database 155A as management data for each application ID.
Each user management data stores, as an example, without limitation, an application ID, a user's electronic commerce account balance identified by the application ID, remittance history data, and receipt history data.

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

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

The remittance request management data 157 is a database that stores data for managing information related to the remittance request in an accumulated manner, and FIG. 1-6 shows a configuration example of the first remittance request management data 157A, which is an example thereof.
In the first remittance request management data 157A, as an example, the date and time, the remittance request management ID, the remittance master ID, the remittance request destination ID, the remittance request amount, and the remittance completed flag are stored in association with each other. Will be done.

At the time of day, as an example, not limited to, 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.

The remittance request management ID stores an ID uniquely set by the server 10 for each remittance request.

The application ID of the user who requested the remittance (also referred to as the remittance master user) is stored in the remittance master ID.
The application ID of the user requested to remittance (also referred to as the remittance request destination user) is stored in the remittance request destination ID.

The remittance request amount stores the amount of remittance requested by the remittance master user to the remittance request destination user by the remittance request.

The remittance completed flag is a flag indicating whether or not the remittance corresponding to the remittance request is completed by executing the settlement process by the control unit 11, and the default is "OFF", and the remittance is completed. Is set to "ON".

The following two patterns can be considered as a method for the server 10 to manage the remittance request.
(1) Pattern A: The remittance request that executed the remittance is left without being deleted.
(2) Pattern B: The remittance request that executed the remittance is deleted.

Either of these patterns can be applied, but when pattern A is applied, the data of the remittance request with the remittance completed flag set to "ON" is left without being deleted.
On the other hand, when pattern B is applied, the record of the data of the remittance request that executed the remittance is deleted.

(2) Terminal FIG. 1-7 is a diagram showing an example of a function realized by the control unit 21 of the terminal 20 in this embodiment.
The control unit 21 includes, as an example, not limited to, a payment application processing unit 211 that executes payment application processing according to the payment application processing program 281 stored in the storage unit 28 as a functional unit.

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 storage unit 28 stores, as an example, not limited to, the payment application processing program 281 read by the control unit 21 and executed as the payment application processing, and the application ID 283 associated with its own terminal 20 or its user. Will be done.

<Display screen>
In the following, not only but as an example, a case where the terminal 20 is a smartphone provided with a display unit 24 of a vertically long display will be illustrated.

As an example, not limited to a smartphone, a touch panel that functions as an input unit is arranged facing the display, thereby forming a touch screen. When an element such as an icon, button, item, or input area is displayed on the display, if the user operates a part of the touch panel that faces the area where the element is displayed. The program associated with the element or the subroutine of that program is executed.

In the following, the operation by the user will be described as a tap (tap operation) as an example without limitation.
The tap (tap operation) is not limited to, but as an example, the user touches the display unit 24 (touch screen) in which the touch panel is integrated by tapping it with a finger or a pen tip, and then releases the touch panel. It is an operation.

The transition of the display screen described below is only an example of the transition of the display screen for realizing the method of the present disclosure. Regarding the transition of the display screens exemplified below, the display of some display screens may be omitted, or another display screen may be added.

FIG. 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 not limited, but as an example, User A. This is the main menu screen of the payment application displayed on the display unit 24 of the terminal 20A of A.

In the center of the top of the menu screen, the characters "Payment App" are displayed as the name of the payment application. Further, on the upper right side of the screen, an icon image and a user name (user A.A. in this example) in the payment application of the user of the terminal 20 are displayed.

Below that, the current position display area CLR1 indicating the current position in the payment application is configured, and in this example, the characters "wallet main menu" indicating that the current position is the main menu of the payment application are displayed. , Is displayed in the current position display area.

When the remittance request list icon IC1 displayed at the bottom of the main menu screen is tapped, information requesting remittance request list information is transmitted from the terminal 20A to the server 10, and the server 10 sends the information requesting the remittance request list information to the terminal 20A. Remittance request list information is sent. As a result, the remittance request list screen as shown in FIG. 1-10 is displayed as an example, not limited.

In the current position display area CLR1, the characters of "remittance request list" indicating that the remittance request list information is displayed are displayed.

This remittance request list screen is an unprocessed remittance request with a user of a different terminal 20 (hereinafter referred to as "unprocessed request") as a remittance request for a user (user A.A.) of his / her terminal 20. Is displayed for each user of different terminals 20.

In the following, a user who proposes to perform batch processing is appropriately referred to as a "proposer user".
Further, a user whose batch processing is proposed by the proposer's user is appropriately referred to as a "other user".

Specifically, as a partner, the user B. B, user C. C, user D. D, user E. When multiple users such as E are associated with the icon image and user name of each user, and the number of unprocessed requests with that user and the unprocessed requests with that user are collectively processed. The settlement amount in (hereinafter referred to as "lump-sum settlement amount") is displayed.

Here, the amount of money that oneself will pay to the other party by the remittance request requested by the other party is appropriately referred to as "payment amount", and the amount of money that oneself receives from the other party by the remittance request requested by the other party is appropriately "received". Called "amount".
In this case, the "lump sum settlement amount" is the sum of the payment amount and the received amount corresponding to each unprocessed request when all the unprocessed requests are processed in a batch by reversing the positive and negative codes. .. This lump sum settlement amount is not limited, but is calculated in the settlement process executed by the control unit 11 of the server 10 as an example.

Also, in this display screen example, a payment mark indicating that it is "payment" is displayed next to the lump sum payment amount when you pay the lump sum payment amount to the other party, and you are the other party. When receiving the lump sum payment amount from, a receipt mark indicating "receipt" is displayed in association with it.

As an example, not a limitation, User A. A (self) is user B. When there are four unprocessed requests with B (the other party) and these four unprocessed requests are collectively processed, the user A. A is user B. It is shown that "1,000 yen" will be paid to B as a lump sum settlement amount.

Similarly, as an example, not a limitation, User A. A (self) is user C. When there are four unprocessed requests with C (the other party) and these four unprocessed requests are collectively processed, the user A. A is user C. It is shown that you will receive "4,000 yen" as a lump sum settlement amount from C.

Further, at the bottom of the screen, a settlement button BT1 for requesting the server 10 to collectively settle all unprocessed requests is displayed.

In this screen, as an example, not a limitation, the user C.I. When the display area WR1 of C is tapped, the remittance request details screen shown in FIG. 1-11 is displayed. On this remittance request details screen, user C.I. The details of the outstanding request with C are displayed.

Batch settlement is to perform batch settlement based on multiple unprocessed requests. As an example, not limited to all unprocessed requests, "all-select batch settlement" and unprocessed requests "Partial selection batch settlement" is included to settle a part and a plurality of of.

In the current position display area CLR1 at the top of the screen, the user C.I. The characters "Remittance request with CC" indicating that the unprocessed request with C is displayed are displayed.
Further, under the current position display area CLR1, the user C.I. The batch settlement amount ("4,000 yen" in this example) and the mark ("receipt mark" in this example) are displayed on the assumption that all selection batch settlement is performed in association with the icon image of C and the user name. ing.

User C. Next to the icon image of C, there is a check area ASR1 configured so that the check "ON / OFF" can be switched by tapping, and a check mark is displayed in the check area by setting the check to "ON". It is configured so that all unprocessed requests can be settled at once.

Below that, the other party is the user C.I. A list of remittance requests with C is displayed. In this example, the other party is the user C.I. The unprocessed requests designated as C are listed in chronological order from the top to the oldest, and the processed requests (hereinafter referred to as "processed requests") are listed in chronological order from the top to the oldest under the list of unprocessed requests. It is listed in chronological order. Further, the processed request is displayed in a different display mode (grayed out in this example) in order to distinguish it from the unprocessed request.

In the following, a remittance request sent by oneself to the other party is referred to as a "sent remittance request", and a remittance request received by oneself from the other party is referred to as a "received remittance request".
In this case, the request send mark indicating "Request transmission" is displayed for the sent remittance request among the unprocessed requests, and "Request received" is displayed for the received remittance request among the unprocessed requests. The request reception mark is displayed.

Further, for each unprocessed request, the date and time when the request was sent from the own terminal 20 to the terminal 20 of the other user for the sent remittance request, and the request for the received remittance request is sent to the own terminal. The date and time when 20 received from the terminal 20 of the other user are displayed in association with each other.

Further, each unprocessed request is not limited, but as an example, the reason for remittance by the unprocessed request is associated and displayed.

The remittance request amount information may not be included in the remittance request information, and the remittance request amount information may not be displayed. In this case, as an example, not limited to, the proposer user can inquire the server 10 or the other user for the information of the remittance request amount.

Further, although the information on the remittance request amount is included in the remittance request information, it may not be displayed on the remittance request list screen or the individual remittance request screen. Also, in this case, as an example, not limited to, on the individual screen of the remittance request, the details screen of the remittance request including the information of the remittance request amount is displayed based on the input for confirming the detailed contents of the remittance request. It may be displayed.

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

Also, for each unprocessed request, as an example, but not limited to, for a sent remittance request, the receipt amount that you will receive from the other party by processing the sent remittance request is associated with the receipt mark. For received remittance requests, the payment amount that you will pay to the other party by processing the received remittance request is displayed in association with the payment mark.

Further, next to each unprocessed request, a check area SR1 configured so that the check "ON / OFF" can be switched by tapping is provided, and by setting the check to "ON", the check area SR1 is set. A check mark is displayed so that the unprocessed request can be selected for batch settlement.

Further, at the bottom of the screen, a settlement button BT2 for requesting the server 10 to collectively settle the selected unprocessed requests is displayed.

In FIG. 1-11, the processed request is displayed together with the unprocessed request, but the processed request may not be displayed.

As an example, not limited to, the check of two requests, the third sent remittance request (receipt 10,000 yen) and the fourth received remittance request (payment 3,000 yen), is "ON". When the payment button BT2 is tapped, the display as shown in FIG. 1-12 is displayed.

In FIG. 1-12, batch settlement confirmation information for allowing the user to confirm the contents of batch settlement is displayed at the lower part of the screen of FIG. 1-11. In this example, in the electronic commerce account balance display area WBR1 including the text of "wallet balance", a settlement content confirmation area ACR1 showing how one's current electronic commerce account balance changes by batch settlement is provided. ing.

In the settlement content confirmation area ACR1, as an example, the current electronic commerce account balance of oneself (user A.A) is displayed on the left side, and the balance of one's own electronic commerce account after settlement is displayed on the right side.
Below that, along with the text "Do you propose settlement with this content?", The suggestion button BT3 indicating "suggestion" for proposing settlement, and "cancel" for canceling settlement. Is displayed with the cancel button indicated.

In this example, User A. The current electronic commerce account balance of A is "500 yen".
Then, when the two requests selected above are settled in a batch, the user A. For A, "receipt 10,000 yen" and "payment 3,000 yen" will be "receipt 7,000 yen". Therefore, it is shown that the electronic commerce account balance after settlement becomes "7,500 yen" by adding the lump sum settlement amount "7,000 yen" to the current electronic commerce account balance "500 yen". There is.

FIG. 1-13 is a diagram showing an example of a payment application notification screen displayed based on the tapping of the proposal button BT3 on the above screen. This notification screen is displayed by User A. User C. who is the other party of A. This is an example of a screen displayed on the display unit 24 of the terminal 20C of C.

By tapping the proposal button BT3 on the screen displayed on the display unit 24 of the terminal 20A of FIG. 1-12, the terminal 20A requests the server 10 to execute the batch settlement. Then, from the server 10, the other user C.I. The batch settlement approval confirmation information for confirming the intention of whether or not to approve the batch settlement is transmitted to the terminal 20C of C, and is displayed on the display unit 24 of the terminal 20C.

At the top of this notification screen, the current position display area CLR2 is configured, and the characters "notification" indicating that the notification regarding the payment application is displayed are displayed.

Below the current position display area CLR2, the user A. As a notification indicating that the remittance request settlement proposal has been received from the terminal 20A of A, a notification NT1 including the text "The remittance request settlement proposal has arrived" is displayed together with the bell mark.

Further, below that, a notification information display area NTR1 for displaying notification information is configured, and information corresponding to the above notification NT1 is displayed in this notification information display area NTR1.
In this example, as the batch settlement approval confirmation information, the text of "settlement proposal" and the user A. The icon image of A and the lump sum settlement amount are displayed. In this example, as the lump sum settlement amount, the user C.I. C is user A. It is displayed that it is necessary to pay "7,000 yen" to A.

In addition, the link LK1 showing the text of "confirm details" for confirming the detailed contents of the batch settlement is formed in the batch settlement approval confirmation information, and when this link LK1 is tapped, the details of the batch settlement are formed. It is structured so that the contents (breakdown as an example, not limitation) can be confirmed.

In addition, instead of displaying the detailed contents of the batch settlement from the link LK1 of "Confirm details", the detailed contents of the batch settlement can be displayed in the left-right direction and the depth direction as an example, not limited. You may do so. An example of this is not limited, but a carousel display as an example.
This method is similarly applicable to any of the examples.

In addition, the batch settlement approval confirmation information includes a settlement button indicating "Settlement" to approve the settlement with the above contents, and "Refuse" to decline the settlement without approving the settlement with the above contents. The reject button was displayed.

When the above link LK1 is tapped, a screen as shown in FIG. 1-14 is displayed as an example, not a limitation.
This screen is a remittance request list screen displayed on the display unit 24 of the terminal 20C, and the other user A. This screen displays a list of unprocessed requests with A. This screen corresponds to the screen displayed on the display unit 24 of the terminal 20A shown in FIG. 1-12.

In the current position display area CLR2, the user A. The characters "Remittance request with A." indicating that the unprocessed request with A is displayed are displayed.

In the settlement content confirmation area ACR2 at the bottom of the screen, as an example, the current electronic commerce account balance of yourself (user CC) is displayed on the left side, and your electronic commerce account balance after settlement is displayed on the right side. To.
In addition, below that, along with the text "Do you want to settle with this content?", The settlement button BT4 indicating "Settlement" to approve the settlement, and the correction proposal of the settlement without approving the settlement. A correction suggestion button labeled "correction suggestion" to do is displayed.

In this example, user C.I. The current electronic commerce account balance of C is "11,000 yen".
And user A. When the two requests proposed by A are settled in a batch, the user C.I. For C, "payment 10,000 yen" and "receipt 3,000 yen" result in "payment 7,000 yen". Therefore, by subtracting the lump sum settlement amount "7,000 yen" from the current electronic money account balance "11,000 yen", it is shown that the electronic money account balance after settlement becomes "4,000 yen". Has been done.

FIG. 1-15 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20A based on the tapping of the settlement button BT4.
In this example, the user C.I. Since the batch settlement has been performed with C, the settlement result information of two cases is displayed as the content of the batch settlement.
Specifically, the settlement result information corresponding to each of the third remittance request and the fourth remittance request selected in FIGS. 1-11 and 1-12 is displayed, not as a limitation.

In each settlement result information, an individual amount of money is displayed together with "request settlement" and an icon image of the other user.

In addition, instead of displaying the settlement result information corresponding to each of the selected remittance requests, as an example, not limited to, as shown in FIG. 1-16, the settlement result information is collected as a result of the batch settlement. Can also be displayed.

As an example, not a limitation, when the detailed confirmation link LK2 included in the settlement result information of FIG. 1-16 is tapped, the screen as shown in FIG. 1-17 is displayed.
In the current position display area CLR1 of this screen, the character "request settlement" indicating that the result of the batch settlement is displayed is displayed.

Below the current position display area CLR1, the user C.I. In association with the icon image of C and the user name, the batch settlement amount (“7,000 yen” in this example) and the mark (“receipt mark” in this example) of the executed batch settlement are displayed.
Below that, a list of remittance requests processed by bulk settlement is displayed.

Further, at the bottom of the screen, the electronic commerce account balance display area WBR1 is displayed.
In this electronic commerce account balance display area WBR1, the characters "wallet balance" are displayed, and below that, the settlement result balance display area ARR1 showing how the own electronic commerce account balance has changed due to the batch settlement. Is displayed.

In the settlement result balance display area ARR1, as an example, the current electronic commerce account balance of oneself (user A.A) is displayed on the left side, and the own electronic commerce account balance of the collective settlement result is displayed on the right side. ..
In addition, below that, the text "The two requests have been settled." Is displayed as the text indicating that the batch settlement has been performed.

In this example, User A. It is shown that the electronic commerce account balance of A has changed from "500 yen" to "7,500 yen" due to the lump sum settlement.

<Processing>
(1) Example of processing First, an example of processing in this embodiment will be described.
The processes described below are merely examples of processes for realizing the method of the present disclosure, and are not limited to these processes.
Further, another step may be added to the process described below, or some steps may be omitted (deleted).
This is the same for each flowchart (process) described below.

FIG. 1-18 is a flowchart showing an example of the flow of processing executed by each device in this embodiment.
From the left side, the processing executed by the control unit 21 of the terminal 20A, the processing executed by the control unit 21 of the terminal 20B, and the processing executed by the control unit 11 of the server 10 are shown.
As an example, not a limitation, the user A. of the terminal 20A. A is the user B. of the terminal 20B. An example is an example of requesting that remittance requests made with B be processed in a batch.
In this process, the end determination of the process is omitted for the sake of simplicity.

First, the control unit 21 of the terminal 20A transmits, as an example, not limited to, the remittance request list request information for requesting the list of remittance requests to the server 10 by the communication I / F 22 based on the input to the input unit. (A110).

In response to this, the control unit 11 of the server 10 refers to the first remittance request management data 157A, and the user A. The remittance request list information regarding A is transmitted to the terminal 20A by the communication I / F14 (S120).

When the remittance request list information is received by 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).

After that, the control unit 21 of the terminal 20A determines whether or not one or more remittance requests are selected (A130), and if it is determined that the remittance request is selected (A130: YES), the request selection information regarding the selected remittance request. Is transmitted to the server 10 by the communication I / F22 (A140).

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

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

If it is determined that the payment is to be made in a lump sum (S1510: YES), the control unit 11 of the server 10 determines the remittance request amount of the selected remittance request and the type of each selected remittance request (received remittance request (received remittance request). The lump sum settlement amount is calculated based on (payment) / sent remittance request (receipt)) (S1515).

After that, the control unit 11 of the server 10 determines whether or not the balance of at least one of the proposer's user and the other user's electronic commerce account balance becomes negative based on the calculated lump sum settlement amount (). S1520).

If it is determined to be negative (S1520: YES), the control unit 11 of the server 10 transmits, as an example, not limited to, batch settlement NG information indicating that batch settlement is not possible to the terminal 20A by communication I / F14. (S1523).
Then, the control unit 11 of the server 10 ends the first settlement process.

On the other hand, if it is determined that the electronic commerce account balance does not become negative (S1520: NO), the control unit 11 of the server 10 communicates the settlement confirmation information including the batch settlement amount information which is the calculated batch settlement amount information. It is transmitted to the terminal 20A by I / F14 (S1525).

When the settlement confirmation information is received from the server 10 by 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).

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

The control unit 11 of the server 10 determines whether or not to execute the settlement based on whether or not the settlement execution request information is received from the terminal 20A by the communication I / F 14 (S1530). Then, if it is determined that the settlement is to be executed (S1530: YES), the control unit 11 of the server 10 executes the batch settlement (S1540).

FIG. 1-20 is a diagram showing an example of a table for explaining batch settlement.
In this table, the types of unprocessed requests of the user who proposes the batch settlement (user AA in this processing example) are shown vertically and horizontally, and the other user (user BB in this processing example) is one person. The process in which two unprocessed requests are collectively settled based on the proposal by the proposer's user is shown.
The vertical and horizontal outstanding requests include a received remittance request and a sent remittance request, respectively.

(1-1) Combination of Received Remittance Request and Received Remittance Request In this combination, the proposer user (User A.A.) is the unprocessed 2 received from the other user (User BB). Send money to the other user based on one remittance request.

In this case, the control unit 11 of the server 10 performs a process of remittance from the proposer user to the other user by adding the remittance request amounts of the two received remittance requests as the remittance amount. Execute. Specifically, the control unit 11 of the server 10 subtracts and updates the lump sum settlement amount from the electronic money account balance of the proposer user, and adds and updates the lump sum settlement amount to the electronic money account balance of the other user. do.

(1-2) Combination of received remittance request and sent remittance request ・ (1-3) Combination of sent remittance request and received remittance request In this combination, the proposer user receives from the other user. Based on the completed unprocessed remittance request and the unprocessed remittance request sent to the other user, the remittance to the other user / the receipt from the other user is performed. In this case, since there is a relationship between payment and receipt, the difference between the remittance request amount of the received remittance request and the remittance request amount of the sent remittance request is the lump sum settlement amount.
In the following, taking the difference between the remittance request amounts (deducting the amount) is referred to as "amount deduction".

The amount deduction includes offsetting the amount (hereinafter referred to as "amount offset").
Amount offsetting means, as an example, not a limitation, that by deducting the amount of remittance requests selected for processing, the amounts cancel each other out and become zero.
When the deduction of the amount is zero, the amount is offset.

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 amount is offset. Will be done.

In this case, if the remittance request amount (second amount) of the received remittance request is larger than the remittance request amount (first amount) of the sent remittance request, the control unit 11 of the server 10 requests the remittance of the received remittance request. The amount (third amount) obtained by subtracting the remittance request amount of the sent remittance request from the amount is calculated as the lump sum settlement amount. Then, the lump sum settlement amount is subtracted from the electronic money account balance of the proposer user and updated, and the lump sum settlement amount is added to the electronic money account balance of the other user and updated.

In the opposite case, the lump sum settlement amount is subtracted from the electronic commerce account balance of the other user and updated, and the lump sum settlement amount is added to the electronic money account balance of the proposer user and updated.

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 amount is offset and the remittance is not performed.

As will be described in detail in a later embodiment, in the combination of the received remittance request and the sent remittance request, the process of "remittance + remittance reminder (or new remittance request)" is performed as an example, not limited. It is also possible to.
That is, it is possible to send money to the other user based on the received remittance request and to remind the other user (or a new remittance request) based on the sent remittance request.

(1-4) Combination of Sent Remittance Request and Sent Remittance Request In this combination, the user who proposes the batch settlement is based on two unprocessed remittance requests (sent remittance request) addressed to the other user. Then, a new remittance request that combines these into one is sent to the other user.

This remittance request is a type of remittance request (hereinafter referred to as "lump-sum remittance request") that combines multiple remittance requests, and is used for the purpose of encouraging the remittance requested amount to be transferred together. Is to be done.
For convenience, this remittance request is referred to as a "confirmation batch remittance request".

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

In the combination of (1-4), the control unit 11 of the server 10 instead of transmitting the confirmation batch remittance request information to the terminal 20 of the other user, a plurality of selected transmitted remittance requests. The remittance reminder information corresponding to each of the above may or may not be transmitted to the terminal 20 of the other user.

Further, in the combination of (1-4), the unprocessed 2 requested by the user of the proposer of the batch settlement (user A.A in this processing example) to the other user (user BB in this processing example). You may or may not receive money from the other user based on one remittance request.

In this case, in the batch settlement, the control unit 11 of the server 10 remits the sum of the remittance request amounts of the selected transmitted remittance requests to the proposer user as the batch settlement amount. To execute. Specifically, the control unit 11 of the server 10 subtracts and updates the lump sum settlement amount from the electronic commerce account balance of the other user, and adds and updates the lump sum settlement amount to the electronic money account balance of the proposer user. do.

Strictly speaking, making a batch remittance request for confirmation (sending confirmation batch remittance request information) and remittance reminding (sending remittance reminder information) have different meanings and concepts from "payment". You can also.
However, for the sake of brevity, these are also included in the settlement (a type of settlement) in the present specification.

Returning to FIG. 1-19, after executing the batch settlement in S1540, the control unit 11 of the server 10 ends the first settlement process.

On the other hand, if it is determined that the settlement target is not the batch settlement target, that is, the selected remittance request is one (S1510: NO), the control unit 11 of the server 10 is the electronic money account of the proposer user. It is determined whether or not the balance becomes negative (S1570). Then, if it is determined to be negative (S1570: YES), the control unit 11 of the server 10 is not limited, but as an example, the settlement NG information indicating that the settlement cannot be performed is transmitted to the terminal 20A by the communication I / F14. (S1573).
Then, the control unit 11 of the server 10 ends the first settlement process.

On the other hand, if it is determined that the electronic commerce account balance does not become negative (S1570: NO), the control unit 11 of the server 10 inputs the settlement confirmation information including the settlement amount (the remittance request amount of the selected received remittance request). , Transmit to the terminal 20A by communication I / F14 (S1575).

When the settlement confirmation information is received from the server 10 by 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).

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

The control unit 11 of the server 10 determines whether or not to execute the settlement based on whether or not the settlement execution request information is received from the terminal 20A by the communication I / F 14 (S1580). Then, if it is determined to execute (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.

Returning to FIG. 1-18 and executing the settlement process, the control unit 11 of the server 10 determines whether or not the settlement result is “OK” (S170). Then, if it is determined that the result is "OK" (S170: YES), the control unit 11 of the server 10 transmits the settlement result information to the terminal 20A and the terminal 20B by the communication I / F14 (S190). Then, the control unit 11 of the server 10 ends the process.

When the settlement result information is received from the server 10 by 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.

Similarly, when the settlement result information is received from the server 10 by 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.

(2) Another example of processing Next, another example of processing in this embodiment will be described.
It is also possible to require the approval of the other user when performing batch settlement. This is because the following cases can be considered.

(A) A case where a malicious user wants to make a profit by batch settlement This can be said to be an unavoidable problem in a system in which a remittance request can be created by the user's operation.

As an example, but not a limitation, a malicious user may send a false remittance request to the other user. Specifically, it is assumed that a malicious user creates a false remittance request, sends it to the other user, and then offsets the amount by batch settlement. More specifically, as an example, not a limitation, User A. A is user B. When a remittance request of a predetermined remittance request amount (for example, "3,000 yen") is received from B, the user A. A creates a remittance request with the same amount as the remittance request amount (for example, "3,000 yen"), and the user B. After sending back to B, user A. This is a case where batch settlement is performed by A.

In addition to this, it is also conceivable that a malicious user may include a false remittance request in the remittance request. Specifically, there is a case where some false remittance requests are created and sent without the other user noticing, and the batch settlement is performed using the false remittance requests.

In these cases, the other user can be fooled if the other user's approval is not required.

(B) Case where batch settlement is performed according to the intention of the other party This is not a limitation, but as an example, batch settlement is performed by including at least one remittance request among the remittance requests sent to the partner user. As a result, the remittance request, which is the position of remittance (payment) for the other user, is included in the batch settlement target, so that the other user may feel that he / she has lost money.
However, once all remittance requests have been processed, the end result will be the same as long as the legitimate remittance request is processed.

In any of the above cases, the approval of the other user is required to confirm whether the remittance request targeted for batch settlement is a legitimate remittance request (whether it is really correct). Can be.

FIG. 1-21 is a flowchart showing another example of the flow of processing executed by each device in this embodiment. The way of reading the figure is the same as that of FIG. 1-18.
In this process, the control unit 11 of the server 10 executes the second settlement process in S150.

FIG. 1-22 is a flowchart showing an example of the flow of the second settlement process.
If it is determined in S1530 that the batch settlement execution request has been made (S1530: YES), the control unit 11 of the server 10 determines whether or not the approval of the other user is required (S1531). Specifically, as an example, not limited to, the remittance master ID associated with the remittance request management ID of two or more selected remittance requests is the user A. The application ID of A, and the associated remittance request destination ID is the user A. Whether or not the remittance request management ID, which is the application ID of the user other than A, is included, that is, whether or not the remittance request from the other party (user BB) to the proposer user (user A.A) is included. Is determined.

If it is determined that the approval of the other user is required (S1531: YES), the control unit 11 of the server 10 decides whether or not to approve the batch settlement by the other user (user BB in this example). ), The batch settlement approval confirmation information including the batch settlement amount information is transmitted to the terminal 20B by the communication I / F14 (S1533).

The control unit 21 of the terminal 20B determines whether or not the batch settlement approval confirmation information has been received from the server 10 by the communication I / F 22 (B150), and if it is determined that the batch settlement approval confirmation information has been received (B150: YES), the received batch settlement approval unit 21. The settlement approval confirmation information is displayed on the display unit 24 (B160).

After that, the control unit 21 of the terminal 20B determines whether or not to approve the batch settlement based on whether or not an input for approving the batch settlement has been made to the input unit (B170). Then, if it is determined to approve (B170: YES), the control unit 21 of the terminal 20B transmits the batch settlement approval information indicating that the batch settlement is approved to the server 10 by the communication I / F 22 (B180).

After S1533, the control unit 11 of the server 10 determines whether or not the batch settlement has been approved by the other user based on whether or not the batch settlement approval information has been received from the terminal 20B by the communication I / F 14. S1535). Then, if it is determined that the approval is made (S1535: YES), the process is transferred to S1540.

<First processing by terminal)>
The process executed by the terminal by the control unit, and the first process based on the first information and the second information is not limited, but as an example, the proposer user (terminal user) to the other user (first). Processing related to remittance to user, second user), processing related to receiving (receipt) the amount of money sent from the other user by the proposer user may be included. can. The first process can include not only processes directly related to remittance or receipt, but also processes indirectly related to remittance or receipt.

As an example, not a limitation, at least the following processing is included in the first processing.
-Processing to select a remittance request-Processing to notify the server 10 of the selected remittance request-Processing to acquire settlement confirmation information from the server 10, processing to display this on the display unit 24-Requesting the server 10 to execute settlement Processing-Processing to acquire settlement result information from the server 10, processing to display this on the display unit 24-Processing to request the server 10 to deduct the amount of money (including offsetting the amount of money) -Create a batch remittance request for confirmation on the server 10 Requested processing

<Input to the terminal, etc.>
In the above process, the input to the terminal or the input by the user of the terminal is an operation input to the input unit (operation unit), but the present invention is not limited to this.

As an example without limitation, it may be possible to input sound (including voice) to the input unit (sound input unit 25) in place of or in addition to the operation input to the input unit (operation unit). It does not have to be.
This also applies to other inputs to the terminal and other inputs by the user of the terminal.

<Effect of the first embodiment>
According to this embodiment, as an example, not limited to, a plurality of remittance requests can be processed at once, so that the convenience of the user can be improved.
Further, as an example, the remittance can be performed within a range not exceeding the user's balance, so that the user's convenience can be improved.

More specifically, in this embodiment, the terminal 20 is a user of the terminal 20 from the first user (not limited to the example of the first user) of the terminal 20 of the first user different from the terminal 20 of the terminal 20. Remittance request information regarding a remittance request to (an example of a terminal user, not a limitation) (an example of the first information, not a limitation), or the first remittance regarding a remittance request from a user of the terminal 20 to the first user. The first between the display based on the request information (an example of the first information, not the limitation) (an example of the first display, not the limitation) and the first user (an example of the second user, not the limitation) described above. 2 The display based on the remittance request information (not limited, but an example of the second display) is displayed on at least the display unit 24.
Then, the terminal 20 has a first process (limited) based on the first remittance request information and the second remittance request information based on the input to its own terminal 20 in which the first display and the second display are displayed. Instead, the configuration is shown in which the control unit 21 performs the first processing (an example) based on the first information and the second information.
As an example of the effect of the embodiment obtained by such a configuration, a first display based on the first information regarding a remittance request from the first user to the terminal user or a remittance request from the terminal user to the first user, and Multiple remittance requests based on input to the terminal that displays a remittance request from the second user to the terminal user, or a second display based on the second information about the remittance request from the terminal user to the second user. Information can be processed collectively, and user convenience can be improved.

Further, in this embodiment, the first remittance request information is an example of information regarding a remittance request from the other user to the user of the terminal 20 (not limited, but not limited to information regarding a remittance request from the first user to the user of the terminal). ), And the second remittance request information includes information on a remittance request from the user of the own terminal 20 to the other user (not limited, but an example of information on a remittance request from the terminal user to the second user). The configuration is shown.
As an example of the effect of the embodiment obtained by such a configuration, the amount of money remittance by the terminal user to the first user (the amount paid by the terminal user) and the terminal by the above-mentioned batch processing are not limited but as an example. The amount of the difference from the amount of money sent by the user of the second user (the amount received by the user of the terminal) can be sent to the first user or sent from the second user. In this case, the amount to be remitted or the amount to be remitted is smaller than when a plurality of pieces of information regarding the remittance request are processed one by one (the absolute value of the difference amount becomes smaller). Therefore, as one effect, not limited, there is a high possibility that processing can be performed within the range of the user's balance, and the user does not have to take troublesome work such as charging and loan for remittance. Further, as one effect, not limited, it is possible to process a plurality of pieces of information at once, so that the number of cases to be processed can be expected to increase.

Further, in this embodiment, the first remittance request information includes information on the first remittance request amount (not limited, but an example of the first amount related to remittance), and the second remittance request information is the second remittance request amount (not limited). It is not a limitation, but shows a structure including information on a second amount of money related to remittance).
As an example of the effect of the embodiment obtained by such a configuration, the first display and the second display can inform the user of the terminal of the first amount of money for remittance and the second amount of money for remittance.

Further, in this embodiment, the first process shows a configuration including a process based on the first remittance request amount and the second remittance request amount.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to perform processing such as lump-sum settlement based on the amount of the difference between the first amount and the second amount, not as a limitation but as an example. ..

Further, in this embodiment, the terminal 20 communicates the batch settlement confirmation information based on the second remittance request information to the terminal 20 of the first user (not limited, but an example of the terminal of the second user) via the server 10. It is transmitted by I / F22. In this case, the first process shows a configuration in which the process is executed by the control unit 21 based on the approval of the first user to execute the first process based on the batch settlement confirmation information.
As an example of the effect of the embodiment obtained by such a configuration, the first process can be executed when approved by the other party. Further, as an example, not limited to this, if the other party does not approve, the first process can be prevented from being executed.

Further, this embodiment shows a configuration in which the second user is the first user.
As an example of the effect of the embodiment obtained by such a configuration, the first process is based on the information regarding a plurality of remittance requests with one user (first user) different from the user of the own terminal 20. Can be executed.

Further, in this embodiment, in the first process, when the second remittance request amount is larger than the first remittance request amount, the amount obtained by subtracting the first remittance request amount from the second remittance request amount (not limited, but the third). An example of the amount of money) is shown in the configuration including the process of remittance to the first user.
As an example of the effect of the embodiment obtained by such a configuration, the amount of the difference between the second amount and the first amount can be remitted to the first user, so that the remittance is performed based on one piece of information. It is possible to reduce the amount of money to be paid as compared with the above, and it is possible to improve the convenience of the user.

Further, in this embodiment, the first remittance request information (not limited, but an example of the first information) includes the information of the first remittance request amount (not limited, but an example of the first amount), and the second remittance request. The information (an example of the second information, not the limitation) includes the information of the second remittance request amount (an example of the second remittance, not the limitation), and the first processing is the first remittance request amount and the second remittance. The configuration performed by the control unit 21 based on the request amount and the electronic money account balance of the user of the terminal 20 (not limited, but an example of the balance of the user of the terminal) is shown.
As an example of the effect of the embodiment obtained by such a configuration, the first process based on the first amount and the second amount can be executed in consideration of the balance of the user of the terminal. Thereby, as an example, not limited, the first process can be executed when the balance of the terminal user is sufficient, but the first process can be prevented from being executed when the balance of the terminal user is insufficient.

Further, in this embodiment, in the first process, the user of the terminal 20 owns the operation for the suggestion button (not a limitation, but an example of the input for the fifth display), and the approval of the other user regarding the batch settlement (in the limitation). Instead, the configuration to be executed based on the approval of the first user or the second user regarding the execution of the first process) is shown.
As an example of the effect of the embodiment obtained by such a configuration, not only the input to the fifth display by the user of the terminal but also the first user or the second user regarding the execution of the first process is not approved. You can prevent the process from being executed.

Further, in this embodiment, in the first process, the proposer's user's electronic commerce account balance (not limited, but an example of the terminal user's balance) and the other user's electronic money account balance (not limited, but the first). An example of the balance of one user or a second user) is shown.
As an example of the effect of the embodiment obtained by such a configuration, the first process is executed in consideration of not only the balance of the user of the terminal but also the balance of the first user or the second user. Can be done. As a result, the first process is executed when the balance of the first user or the second user is sufficient, but the first process is executed when the balance of the first user or the second user is insufficient. Can be prevented from being executed.

Further, in the present embodiment, the first process includes a plurality of remittance request information (not limited to the first information and the second information) regarding the user of the proposer, including the first remittance request information and the second remittance request information. Of the plurality of information regarding the remittance request to the terminal user or the remittance request by the terminal user), the first remittance request information and the second remittance request information are based on the input to the terminal 20 by the proposer user. The configuration including the processing based on the remittance request information is shown.
As an example of the effect of the embodiment obtained by such a configuration, among a plurality of information regarding a remittance request to the terminal user or a remittance request by the terminal user, which includes at least the first information and the second information, the terminal The first information and the second information can be appropriately processed based on the input to the terminal by the user.

Further, in this embodiment, the other user is one user (not limited, but an example in which the second user is the first user), and the first process is from the other user to the proposer user. The configuration including the process related to remittance or the process related to remittance from the proposer user to the other user is shown.
As an example of the effect of the embodiment obtained by such a configuration, the same one user (first user = second user) is used as the other user, and the first user can use the terminal based on a plurality of information regarding the remittance request. Remittance to the user or remittance from the terminal user to the first user can be realized.

Further, in this embodiment, the above-mentioned remittance-related processing includes batch settlement confirmation information and batch settlement result information (not limited, but processing of a remittance request based on the first information and processing of a remittance request based on the second information. A configuration including a process of displaying an example of information indicating that the information has been executed) on the display unit 24 is shown.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to notify the terminal user that the processing of the remittance request based on the first information and the processing of the remittance request based on the second information have been executed. can.

<First modification (1)>
As described above, the method of the above embodiment can be similarly applied to the case where the other user is a plurality of different users.

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 modification. This screen is an example of the remittance request list screen displayed on the display unit 24 of the terminal 20A, and is not limited, but as an example, based on the fact that the remittance request list icon is tapped on the main menu screen of FIG. 1-9. This is an example of the displayed screen.

In the current position display area CLR1, the characters of "remittance request list" indicating that the remittance request list information is displayed are displayed.
Under the current position display area CLR1, unprocessed requests sent and received between users of a plurality of different terminals 20 are displayed in chronological order from the top, as an example, not limited to the oldest date. In this example, in order from the top, user B. Received remittance request from B, user C. Received remittance request from C, user B. Received remittance request from B, user C. Received remittance request from C, User D. Received remittance request from D, User C. The sent remittance request to C, ..., Is displayed.

Next to each remittance request, there is a check area SR2 configured to switch the check "ON / OFF" by tapping, and by setting the check to "ON", a check mark is placed in the check area SR2. It is displayed and configured so that the remittance request with the user can be selected for batch settlement.

In this example, the first user B. Received remittance request from B (payment 2,000 yen) and 4th user C.I. The state in which the received remittance request (payment 1,000 yen) from C is selected is shown. When the settlement button BT5 at the bottom of the screen is tapped in this state, settlement request information for requesting batch settlement of the two selected remittance requests is transmitted from the terminal 20A to the server 10.

In this example, User A. From A to user B. Remittance (payment) to B and user C. From C to user C. Since it is a remittance (payment) to C and there is no remittance (receipt) from the other user, the approval of the other user can be unnecessary.
Then, the batch settlement is executed by the server 10, and the user A. From A to user B. Remittance (payment) of "2,000 yen" to B and user A. From A to user C. Remittance (payment) of "1,000 yen" to C is realized.

This modification shows a configuration in which the first user is a different user from the second user.
As an example of the effect of the modification obtained by such a configuration, a plurality of users (first user and second user different from the second user) different from the user of the own terminal 20 are present. The first process can be executed based on the information regarding the remittance request.

<First modification (2)>
In the first embodiment, the user of the proposer manually selects the remittance request to be settled in a lump sum, but the present invention is not limited to this.
The terminal 20 of the proposer's user or the server 10 may or may not automatically select the remittance request to be settled in a lump sum.
The automatic selection of the remittance request to be collectively settled by the terminal 20 or the server 10 of the proposer's user also includes the meaning of proposing (suggesting) the selected remittance request to the proposer's user.

Specifically, the control unit 21 of the proposer's terminal 20 performs a process of inquiring 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 determines each remittance request amount and each remittance request type (received remittance request (received remittance request) from among the remittance requests included in the remittance request list information received from the server 10. Based on (payment) / sent remittance request (receipt)), as an example, but not limited to, one or more remittance requests so that the proposer's user's current e-commerce account balance is the upper limit of the payment amount. select. That is, one or more remittance requests are selected within the range where the current electronic commerce account balance of the proposer user is not negative.

When the control unit 11 of the server 10 selects a remittance request, the same processing may be performed based on the remittance request data stored in the first remittance request management data 157A.

In this modification, the first process is based on the balance of the proposer's user's electronic money account (not limited, but an example of the balance of the terminal user), and a plurality of remittance request information (not limited, but a plurality of information). Of the example), at least the first remittance request information and the second remittance request information are selected, and a configuration including at least processing based on the first remittance request information and the second remittance request information is shown.
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 plurality of information are automatically selected in consideration of the balance of the user of the terminal, and the settlement is performed. Can be done. In this case, since the user of the terminal does not have to manually select the information, the convenience of the user can be improved.

<First modification (3)>
The user interface of the display screen shown in <Display screen> of the first embodiment is merely an example, and is not limited thereto.

1-24 is a diagram showing another example of the UI (user interface) of the display screen displayed on the display unit 24 of the terminal 20. This display screen is an example of the remittance request list screen displayed on the display unit 24 of the terminal 20A, and is a diagram showing another example of the remittance request list screen corresponding to FIGS. 1-12.
On this display screen, the user C.I. As a list of remittance requests with C, received remittance requests and sent remittance requests are displayed in a table format. In this example, a list of received remittance requests is displayed in the left column of the table, and a list of sent remittance requests is displayed in the right column of the table.

For each of the list of received remittance requests and the list of sent remittance requests, in the display column of each remittance request, the date and time of receipt / transmission date and time of the remittance request, the reason for payment, the request type "payment / receipt", Information such as the amount of the remittance request is displayed.

By performing such a display, it is possible to confirm the received remittance request and the transmitted remittance request while comparing them, and it is possible to improve the convenience of the user.

Further, in the above embodiment, the unprocessed remittance request is displayed on the remittance request list screen, but the present invention is not limited to this.
In addition to this, as an example, not limited to this, it is possible to check the list of unprocessed remittance requests from the screen of the payment application, the profile screen of the payment application, the top screen of the payment application, etc. It may or may not be.

<First modification (4)>
In the above embodiment, the case where the approval of the other user is required in the batch settlement has been described. However, if the system is configured so that the remittance request cannot be created based on the user's operation, the approval of the other user can be omitted.

As such a system, as an example, not limited to a system, a system that manages a user's electronic money or electronic payment in association with a remittance request can be considered. More specifically, after an electronic payment is made by one user using electronic money, at least a part of the payment amount is repaid (reimbursement amount) and charged to another user by a remittance request. A system that can be used is conceivable. The use of this system is not limited to the case where a plurality of users split the bill.

In this case, after making an electronic payment, the server 10 can create a remittance request with the advance amount as the remittance request amount according to the user operation and send it to the terminal 20 of another user.

In such a system, a user who intends to make a batch payment needs to consume his / her electronic money account balance once to make an electronic payment, so that the risk of misuse of the above batch processing can be reduced as much as possible. can.

<First modification (5)>
When performing a batch payment, the other user requests remittance of a payment proposal (a payment proposal that one user needs to pay to the other user) that one user is proposed to pay from the other user. A new remittance request may be made, and the new remittance request may be managed on the server 10 side as an unprocessed received remittance request of one user.

Specifically, as an example, not a limitation, in the example of FIG. 1-13, the user C.I. C (one user) is user A. The settlement proposal proposed by A (the other user) to pay "7,000 yen" is made by the user A. A new remittance request requested by A to remit "7,000 yen" is used, and this remittance request is made by the user C.I. It may be managed on the server 10 side as an unprocessed received remittance request of "payment 7,000 yen" of C.

Further, as an example, not limited to, the received remittance request newly created as described above is tapped on the remittance request list screen or the like displayed on the display unit 24 by the terminal 20, and the remittance has been received. Information about the remittance request that contributed to the creation of the remittance request (the remittance request that caused the received remittance request to be created) (details such as the type of remittance request, the amount of the remittance request, the date and time, the reason, etc. Information) can also be displayed hierarchically in the time axis direction so that the user can trace the history of one remittance request.

Specifically, the above-mentioned user C.I. When the unprocessed received remittance request of "Payment 7,000 yen" of C is tapped, the remittance request that contributed to the creation of this received remittance request is not limited, but as an example, 3 in the example of FIG. 1-14. Information about each remittance request for the fourth received remittance request "payment 10,000 yen" and the fourth sent remittance request "receipt 3,000 yen" may be displayed.
This method can also be applied to a sent remittance request.

<First modification (6)>
In the first embodiment, the first user and the second user are described as users of the terminal 20 which is a general user, but the present invention is not limited thereto.
At least one of the first user and the second user may or may not be a user of a business operator such as a store instead of a general user. In this case, the business operator is not limited to the business operator who sells products (including the provision of services) or a business operator who runs a money lending business. Businesses (stores) that are expected to make bills are included.

In this case, in the above embodiment, these businesses acquire an account for a payment service (payment application). Then, using this account, the remittance request information and the remittance reminder information can be transmitted to the terminal 20 of the user (remittance request destination user) who is the billing destination of money via the server 10.

The account acquired by the above-mentioned business operator (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 operator.

This modification shows a configuration in which at least one of the first user and the second user is a store that sells products related to a remittance request.
As an example of the effect of the modification obtained by such a configuration, not only a general user but also a store user can be a user who can make a remittance request to a terminal user.

<First modification (7)>
It is assumed that some users of the terminal 20 may feel awkward and hesitate to propose a batch settlement to the other user. As an example, not a limitation, there is a case where the other user is a person superior to himself / herself, or the other user is a person who has a particularly close relationship such as a close friend.

Therefore, it is also possible to replace the user who proposes the batch proposal with the user of the terminal 20 and use a business account.
The business account is not limited, but as an example, a user who has an official account (hereinafter referred to as "official account" and appropriately referred to as "OA: Official Account") in the service (payment service in the above example). Is.

As an example, a user having an official account can be, for example, a payment service operator or a messaging service operator, without limitation.
In this case, the server 10 can cause the user who proposes the batch settlement to send the batch settlement approval confirmation information to the terminal 20 of the other user as a payment service provider or a messaging service provider. ..

This modification shows a configuration in which the user who proposes the batch settlement is a user who uses an official account (not limited, but an example of a business account).
As an example of the effect of the modification obtained by such a configuration, it is possible to make the user who uses the business account request the batch settlement on behalf of the user who desires the batch settlement, which is convenient for the user. Can be improved.

<Second Example>
The second embodiment is an example relating to the processing when the balance of the user is insufficient in the batch settlement described in the first embodiment.
The contents described in the second embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

<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 displayed by User A. It is a screen displayed on the display unit 24 of the terminal 20A of A, and the other party is the user B. It is a list screen of the remittance request to be B.
In the current position display area CLR1 at the upper part of the screen, the user B. The characters "Remittance request with BB" indicating that the unprocessed request with B is displayed are displayed.

Under the current position display area CLR1, the other party is the user B. A list of remittance requests with B 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 settlement content confirmation area in the electronic money account balance display area WBR2 at the bottom of the screen. ACR3 shows the change in the balance of the electronic money account of oneself (user A.A.). In this example, it is shown that one's current electronic commerce account balance is "500 yen" and one's electronic commerce account balance becomes "0 yen" by lump-sum payment. In this case, since the balance is sufficient, it is possible to settle in a lump sum.

Further, on the right side of the character of "wallet balance" in the electronic commerce account balance display area WBR2, a charge button for executing a charge to the wallet balance, which is indicated by a plus icon in a circle, is displayed.

FIG. 2-2 is a diagram showing a remittance request list screen similar to the screen of FIG. 2-1 but the selected remittance requests are different.
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 electronic money at the bottom of the screen. The change in the electronic commerce account balance of oneself (user A.A) is shown in the settlement content confirmation area ACR4 in the account balance display area WBR2. In this example, it is shown that one's current electronic commerce account balance is "500 yen" and one's electronic commerce account balance becomes "-500 yen" by lump-sum payment. In this example, the payment is 1000 yen, but your current e-commerce account balance is 500 yen, which means that you are short of 500 yen and cannot make a lump sum payment. ..

In this case, in the settlement content confirmation area ACR4, the text "Insufficient balance!" Is displayed together with a warning mark as an example, not limited, as the balance shortage information indicating that the electronic commerce account balance is insufficient. ing. When the proposal button BT6 is tapped in this state, the display as shown in FIG. 2-3 is displayed.

In FIG. 2-3, the charge confirmation information CG1 is popped up in the center of the screen of the remittance request list screen of FIG. 2-2 as information for confirming to the user whether or not to charge the electronic commerce account balance. Has been done. Specifically, along with the text "Do you want to charge the shortfall of 500 yen?", An OK button for approving the charge and a cancel button for canceling the charge are displayed.

When the OK button is tapped in this state, the server 10 causes the user A. A charge process for charging "500 yen" to the electronic money account balance of A is executed. Then, after that, a lump sum settlement is performed.

<Processing>
2-4 to 2-5 are flowcharts showing an example of the flow of the 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 commerce account balance of any user becomes negative (S1520: YES), the control unit 11 of the server 10 determines whether the user whose electronic commerce account balance becomes negative is the proposer user. It is determined whether or not (S1550). Then, if it is determined that the user is the proposer user (S1550: YES), the control unit 11 of the server 10 is not limited to, but as an example, the batch settlement confirmation information including the batch settlement amount information and the balance shortage information. , Transmit to the terminal 20A by communication I / F14 (S1551).

After that, the control unit 11 of the server 10 determines whether or not the batch settlement execution is requested based on whether or not the settlement execution request information is received from the terminal 20A by the communication I / F 14 (S1553). Then, if it is determined that the request has been made (S1553: YES), the control unit 11 of the server 10 may use the user A. It is determined whether or not to charge the electronic money account balance of A (S1555). Specifically, as an example, not limited, the above-mentioned charge confirmation information is transmitted to the terminal 20A and displayed on the display unit 24, and it is determined whether or not the information for approving the charge is received from the terminal 20A.

If it is determined to charge (S1555: YES), the control unit 11 of the server 10 executes the charge process (S1557). Specifically, the pre-registered user A. Using A's bank account or credit card, the amount of the shortfall in the lump sum payment can be used by User A. Execute the process of replenishing the electronic money account balance of A. Then, the control unit 11 of the server 10 shifts the processing to S1531.

On the other hand, if it is determined that the user whose electronic commerce account balance is negative is not the proposer's user, that is, the user whose electronic commerce account balance is negative is the other user, the server 10 (S1550: NO) The control unit 11 transmits the batch settlement confirmation information including the batch settlement amount information to the terminal 20A by the communication I / F 14 (S1559).

After that, if it is determined that the terminal 20A has requested the execution of the batch settlement (S1561: YES), the control unit 11 of the server 10 communicates the batch settlement approval confirmation information including the batch settlement amount information and the balance shortage information. It is transmitted to the terminal 20B by I / F14 (S1563).

After that, the control unit 11 of the server 10 determines whether or not the batch settlement is approved based on whether or not the batch settlement approval information is received from the terminal 20B by the communication I / F 14 (S1565).

If it is determined that the batch settlement is approved (S1565: YES), the control unit 11 of the server 10 may use the user B. It is determined whether or not to charge the electronic money account balance of B (S1567). Specifically, as an example, not limited, the above-mentioned charge confirmation information is transmitted to the terminal 20B and displayed on the display unit 24, and it is determined whether or not the information for approving the charge is received from the terminal 20B.

If it is determined that charging is to be performed (S1567: YES), the control unit 11 of the server 10 executes the charging process (S1569). Specifically, the user B. registered in advance. Using B's bank account or credit card, the amount of the shortfall in the lump sum payment can be used by User B. Execute the process of replenishing the electronic money account balance of B.
Then, the control unit 11 of the server 10 shifts the processing to S1540.

When it is determined in S1553 that execution of batch settlement is not requested (S1553: NO), or when it is determined in S1555 that charging is not performed (S1555: NO), the control unit 11 of the server 10 determines that the third settlement process is performed. To finish.

Further, when it is determined in S1561 that the execution of the batch settlement is not requested (S1561: NO), when it is determined in S1565 that the batch settlement is not approved (S1565: NO), or in S1567 it is determined that the charge is not performed. In the case (S1567: NO), the control unit 11 of the server 10 ends the third settlement process.

Before executing the process of S1540, the same process as S1520 may be executed again, and if it is determined that the electronic commerce account balance of any user becomes negative, the process of S1540 may be suspended. And you don't have to.

<Effect of the second embodiment>
In this embodiment, the first remittance request information (not limited, but an example of the first information) includes the information of the first remittance request amount (not limited, but an example of the first amount), and the second remittance request information (an example of the first amount, not limited). The second remittance request amount (an example of the second information, not the limitation) includes the information of the second remittance request amount (an example of the second remittance amount, not the limitation), and the first process is the first remittance request amount and the second remittance request amount. And, the configuration performed by the control unit 21 based on the electronic money account balance of the user of the own terminal 20 (not limited, but an example of the balance of the user of the terminal) is shown.
As an example of the 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 in consideration of the balance of the user of the terminal.

Further, in this embodiment, when the total of the first remittance request amount and the second remittance request amount exceeds the electronic money account balance of the user of the own terminal 20, and the remittance is performed from the user of the own terminal 20, the balance. The display of the lack information (not limited, but an example of the third display indicating that the first process cannot be executed) is displayed on the display unit 24 of the own terminal 20.
As an example of the effect of the embodiment obtained by such a configuration, remittance is performed from the terminal user even though the total of the first amount and the second amount exceeds the balance of the terminal user. In such a case, it is possible to notify the user of the terminal that the first process cannot be executed.

Further, in this embodiment, when the total of the first remittance request amount and the second remittance request amount exceeds the electronic money account balance of the user of the own terminal 20, the remittance is performed from the user of the own terminal 20. Display of charge confirmation information to the user's electronic commerce account balance of the terminal 20 (an example of a fourth display indicating that the balance is charged, not limited) is displayed on the display unit 24 of the terminal 20. Shows.
As an example of the effect of the embodiment obtained by such a configuration, remittance is performed from the terminal user even though the total of the first amount and the second amount exceeds the balance of the terminal user. In such a case, it is possible to inform the user of the terminal that it is possible to charge the balance and make up for the shortfall.

<Second modification>
In the second embodiment, information (charge information) indicating that the terminal 20 can charge the balance of its own electronic money account when displaying the remittance request list screen on the display unit 24 as an example, not limited to it. Or, information (loan information) indicating that a loan (loan) can be made may or may not be displayed together with the display unit 24.

The loan operator is not limited, but as an example, it may be a payment service operator (payment application operator) / messaging service operator (messaging application operator), or a financial institution such as a bank. can.

In this case, the server 10 may lend money in the form of electronic money (by means of electronic money) within a certain loan amount based on the input for requesting the loan by the user. can. Alternatively, the server 10 can communicate with the server of the affiliated financial institution to request a loan and have the loan approved.
In this case, the electronic commerce account balance may be treated as a minus or a plus.

If the loan is settled, the user can be made to repay the loan amount by a set repayment deadline, as an example, but not a limitation.
As the repayment method in this case, the same repayment method as a general loan can be applied.

In this modification, the terminal 20 has a display based on the first remittance request information (an example of the first display, not the limitation) and a display based on the second remittance request information (an example of the second display, not the limitation). , Display of charge information (an example of display regarding charge of balance, not limitation) or loan information (example of display regarding loan, not limitation) is displayed on the display unit 24. ..
As an example of the effect of the modification obtained by such a configuration, when displaying the first display based on the first information and the second display based on the second information, the display related to the charge of the balance or the loan is performed. By also displaying the display related to the fact, the user can easily charge the balance or make a loan.

<Third Example>
The third embodiment is an embodiment in which the display mode of the display related to the execution of the batch settlement is changed in relation to the second embodiment.
The contents described in the third embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

<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 is displayed by User A. It is a screen corresponding to the screen of FIG. 2-1 displayed on the display unit 24 of the terminal 20A of A, and is a screen corresponding to the user A. This screen is displayed when the balance of the electronic money account of A is sufficient.

In the settlement content confirmation area ACR5 at the bottom of the screen, it is shown that the balance of one's electronic commerce account becomes "0 yen" by the batch settlement, but the batch settlement is possible.
In this case, when the operation (tap) for the proposal button BT7 is performed, the terminal 20A accepts the operation of proposing the batch settlement.

FIG. 3-2 is a diagram showing another example of the remittance request list screen displayed on the display unit 24 of the terminal 20 in this embodiment.
This remittance request list screen is displayed by User A. It is a screen corresponding to the screen of FIG. 2-2 displayed on the display unit 24 of the terminal 20A of A, and is a screen corresponding to the user A. This screen is displayed when the balance of the electronic money account of A is insufficient.
On this screen, User A. Based on the fact that the electronic commerce account balance of A is insufficient, the proposal button BT7 displayed in the settlement content confirmation area ACR5 at the bottom of the screen is displayed in a display mode different from that of FIG. 3-1. Specifically, as an example, the proposal button BT7 is grayed out and displayed, and even if an operation (tap) is performed on the proposal button BT7, the terminal 20A does not accept the operation.

In FIG. 3-2, the charge button for the electronic commerce account may or may not be displayed in the electronic commerce account balance display area WBR1 to prompt the user to charge.
In addition, if the business operator that operates the payment service is affiliated with a financial institution, a loan function button for receiving a loan from the financial institution and charging the electronic money account may be displayed. It does not have to be.

<Effect of the third embodiment>
In this embodiment, the terminal 20 displays the display of the proposal button (not limited, but an example of the fifth display relating to the execution of the first process) on the display unit 24. In this case, the display of the proposal button shows a configuration in which the display mode is changed based on the first remittance request amount, the second remittance request amount, and the balance of one's own electronic money account.
As an example of the effect of the embodiment obtained by such a configuration, the display mode 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. Therefore, as an example, not a limitation, it is possible to simply and appropriately inform the terminal user that the first process cannot be executed in consideration of the balance of the terminal user.

Further, in this embodiment, the display of the proposal button is such that the total of the first remittance request amount and the second remittance request amount exceeds the electronic commerce account balance of the user of the own terminal 20 and is displayed by the user of the own terminal 20. When remittance is performed, the configuration displayed on the display unit 24 of the own terminal 20 is shown in a display mode indicating that the operation is not accepted (not limited, but an example of a display mode indicating that the first process cannot be executed). There is.
As an example of the effect of the embodiment obtained by such a configuration, remittance is performed from the terminal user even though the total of the first amount and the second amount exceeds the balance of the terminal user. In such a case, it is possible to notify the user of the terminal that the first process cannot be executed.

<Fourth Example>
The fourth embodiment is an example relating to a method (algorithm) of processing for batch settlement.
The contents described in the fourth embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

<Processing>
The batch settlement executed by the server 10 can include the following two methods as an example without limitation.
(1) Batch settlement (batch settlement)
(2) Sequential settlement (sequential settlement)

The batch settlement of (1) is not limited, but is, as an example, a batch settlement method in which two or more selected remittance requests are processed at one time.
In this method, the control unit 11 of the server 10 determines the final remittance amount based on the remittance request amount of each selected remittance request and its type (received remittance request / sent remittance request). calculate.
In this case, if both the electronic commerce account balance of the user of the proposer terminal 20 and the electronic commerce account balance of the other user do not become negative even if the settlement is performed based on the calculated lump sum settlement amount, the settlement is made. OK.
On the other hand, when the settlement is performed based on the calculated lump sum settlement amount, if either the electronic money account balance of the user of the proposer terminal 20 or the electronic money account balance of the other user becomes negative, the settlement is made. It is NG.

The sequential settlement of (2) is not limited, but is, as an example, a batch settlement method in which two or more selected remittance requests are sequentially processed.
In this method, the control unit 11 of the server 10 determines the settlement amount of the two or more selected remittance requests based on each remittance request amount and its type (received remittance request / sent remittance request). The calculation and the sequential processing including the update of the electronic money account balance of the proposer user and the electronic money account balance of the other user are repeated.
If either the electronic commerce account balance of the user of the proposer terminal 20 or the electronic commerce account balance of the other user becomes negative during the sequential processing, the settlement in that order is NG. 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 at least one of the electronic commerce account balance of the user of the proposer terminal 20 and the electronic commerce account balance of the other user does not become negative as a result of sequentially processing up to the final remittance request. , Settlement is OK, and the settlement is performed in that order.

Even if the remittance request is processed in a different order and brute force is performed, either the electronic money account balance of the user of the proposer terminal 20 or the electronic money account balance of the other user is in the middle of the sequential processing. If one of them is negative, the settlement cannot be executed sequentially, so the settlement can be NG.

<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, consider the following two cases.
(Case 1) User A. A's current e-commerce account balance = 500 yen, user B. B's current e-commerce account balance = 1,500 yen (Case 2) User A. A's current e-commerce account balance = 500 yen, user B. B's current e-commerce account balance = 1,000 yen

First, (Case 1) will be described.
(1) When applying batch settlement When applying batch settlement, the first received remittance request, the second received remittance request, and the fourth sent remittance selected in Fig. 3-1 are applied. The request will be processed at the same time.
In this case, the lump sum payment is "payment 2,000 yen", "payment 500 yen", and "receipt 2,000 yen", and "payment 500 yen" (500 yen from user AA to user BB). Payment).
User A. The current electronic commerce account balance of A is "500 yen", and the user A. Since the balance of A is not negative, if the batch settlement is performed, the user B. Settlement is possible regardless of B's electronic commerce account balance.

(2) When applying sequential settlement When applying sequential settlement, the first received remittance request, the second received remittance request, and the fourth sent remittance selected in Fig. 3-1 are applied. Requests will be processed one by one.
As an example, not a limitation, consider the case of processing in the order of the second received remittance request → the fourth sent remittance request → the first received remittance request.

First, the second received remittance request is made by User A. From A to user B. Since it is a payment of "500 yen" to B, when this settlement is performed, the user A. The balance of the electronic money account of A becomes "500 yen → 0 yen", and the user B. The balance of B's electronic money account is "1,500 yen → 2,000 yen".

Next, the fourth sent remittance request is made by User A. A is user B. Since it is the receipt of "2,000 yen" from B, when this settlement is performed, the user A. The balance of the electronic money account of A becomes "0 yen → 2,000 yen", and the user B. The balance of B's electronic money account is "2,000 yen → 0 yen".

Finally, the first received remittance request is from User A. From A to user B. Since it is a payment of "2,000 yen" to B, when this settlement is performed, the user A. The balance of the electronic money account of A becomes "2,000 yen → 0 yen", and the user B. The balance of B's electronic money account is "0 yen → 2,000 yen".

User B. Since the current balance of the electronic commerce account of B is "1,500 yen", the above settlement results in the user B. B is user A. You will receive "500 yen" from A.
In this example, User A. A's electronic commerce account balance and user B. Since neither the balance of the electronic commerce account with B is negative, the settlement can be performed by the sequential settlement.

Next, (Case 2) will be described.
(1) When applying batch settlement The case of applying batch settlement is the same as in (Case 1).
That is, the user A. The current electronic commerce account balance of A is "500 yen", and the user A. Since the balance of A is not negative, if the batch settlement is performed, the user B. Settlement is possible regardless of B's electronic commerce account balance.

(2) When applying sequential settlement When applying sequential settlement, the first received remittance request and the second received remittance request selected in FIG. 3-1 are the same as in (Case 2). And the fourth sent remittance request will be processed one by one.
However, in (Case 2), unlike (Case 1), User B. Due to the fact that B's current e-commerce account balance is "1,000 yen", the first received remittance request, the second received remittance request, and the fourth selected in FIG. 3-1. Regardless of the order in which the sent remittance requests are processed, User A. A's electronic commerce account balance and user B. It is not possible to settle so that neither the balance of the electronic commerce account with B will be negative.

From the above, in (Case 1), settlement by batch settlement or sequential settlement is possible, but in (Case 2), settlement by batch settlement is possible, but settlement by sequential settlement is not possible. become.

In both of the above cases, as an example, not limited to, when the business operator operating the payment service is affiliated with a financial institution, the insufficient balance of the user's electronic commerce account is temporarily regarded as a negative value of the account balance. Allowance may or may not allow payment.

FIG. 4-1 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20B when the sequential settlement is applied in the above (case 1).
At the top of the notification screen, the current position display area CLR3 is configured, and the characters "notification" indicating that the notification regarding the payment application is displayed are displayed.
In the information display area NTR3 below the current position display area CLR3, the user A. The batch settlement approval confirmation information transmitted from the server 10 to the terminal 20B based on the proposal from A is displayed.
In (Case 1), since settlement by sequential settlement is possible, the settlement button BT8 included in the batch settlement approval confirmation information is displayed in a state where the operation can be accepted.

On the other hand, FIG. 4-2 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20B when the sequential settlement is applied in the above (case 2).
The information displayed on this notification screen is the same as in Fig. 4-1. However, in (Case 2), since settlement by sequential settlement is not possible, the settlement button BT8 included in the batch settlement approval confirmation information is grayed out and displayed. Even if an operation (tap) is performed on the payment button, the terminal 20B does not accept the operation.

<Fifth Example>
The fifth embodiment is an example relating to "request offset" in the above-mentioned batch processing.
The contents described in the fifth embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

As mentioned above, 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. If so, it is possible to offset the amount by lump-sum payment.

However, in such a case, it is possible to offset the request instead of performing the batch settlement.
Request offsetting means, by example, but not by limitation, canceling each other's remittance requests selected for processing, eliminating those remittance requests, and deleting the data in those remittance requests.

<Display screen>
FIG. 5-1 shows the user A. It is a figure which shows an example of the remittance request list screen displayed on the display part 24 of the terminal 20A of A. On this remittance request list screen, the other user can be referred to as user B. It is a screen to be B.
On this remittance request list screen, the state in which the first received remittance request (payment 2,000 yen) and the fourth sent remittance request (receipt 2,000 yen) are selected is shown.

In the settlement content confirmation area ACR6 at the bottom of the screen, the user A. A's current e-commerce account balance and user A. The balance of the electronic commerce account after the settlement of A is displayed. If a lump sum payment is made based on the above two selected remittance requests, the amount will be offset. Therefore, in this example, the user A. A's current e-commerce account balance and user A. The balance of the electronic commerce account after the settlement of A is the same amount (500 yen).

Below that, a suggestion button and a cancel button are displayed, along with the text "Do you want to suggest offsetting the request?".
As an example, not a limitation, when the suggestion button is tapped, information for requesting request offset is transmitted from the terminal 20A to the server 10. Then, the request offset processing is executed by the server 10, and the data of the two selected remittance requests is deleted.

<Processing>
(1) Example of Processing FIG. 5-2 is a flowchart showing an example of the flow of processing 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 the request offset processing (S350).

In the request offset processing, the control unit 11 of the server 10 calculates the remittance amount based on the remittance request selected by the terminal 20A, and determines whether or not the remittance request can be offset based on the calculated remittance amount. do. Then, if it is determined that the offset can be made, the control unit 11 of the server 10 transmits the request offset confirmation information to the terminal 20A.

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

The control unit 11 of the server 10 executes request offset based on receiving the request offset execution request information from the terminal 20A. Specifically, the remittance request data to be offset is deleted from the first remittance request management data 157A.
The remittance completed flag of the remittance request to be offset may be set to "ON" without deleting the remittance request data.
Then, the control unit 11 of the server 10 ends the request offset processing.

After that, the control unit 11 of the server 10 determines whether or not the request offset result is “OK” (S370). Then, if it is determined that the result is "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 by the communication I / F14 (S390). Then, the control unit 11 of the server 10 ends the process.

When the request offset result information is received from the server 10 by 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.

Similarly, when the request offset result information is received from the server 10 by 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.

(2) Another example of processing When canceling the above request, the approval of the other user may be required. The case that requires the approval of the other user is the same as the case described in the batch settlement.

The process in this case can be similarly configured following the process when the approval of the other user is required in the batch settlement (not limited, but as an example, the process of FIGS. 1-21 to 1-22). Therefore, illustration and detailed description will be omitted.

<Effect of the fifth embodiment>
In this embodiment, the first process includes a plurality of remittance request information (not limited to, but not limited to, at least the first information and the second information) including the first remittance request information and the second remittance request information. Of the plurality of information regarding the remittance request to the terminal user or the remittance request by the terminal user), the first remittance request information and the second remittance request are based on the input to the terminal 20 by the proposer user. The configuration including the processing based on the information is shown.
As an example of the effect of the embodiment obtained by such a configuration, among a plurality of information regarding a remittance request to the terminal user or a remittance request by the terminal user, which includes at least the first information and the second information, the terminal The first information and the second information can be appropriately processed based on the input to the terminal by the user.

Further, in this embodiment, the first remittance request information and the second remittance request information are information on the same remittance request amount, and the first process is based on the first remittance request information and the second remittance request information. It shows a configuration which is a process of offsetting a request between the first remittance request information and the second remittance request information (not limited, but an example of offsetting between 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 of money, these information can be offset. As a result, it is possible to improve the convenience of both the user who requested the remittance based on the first information and the user who requested the remittance based on the second information.

<Fifth variant>
In the fifth embodiment, when the remittance request amount of the remittance request selected as the processing target is not offset, the difference amount is used as the remittance request amount. You may or may not create a new remittance request that will determine.

<Sixth Example>
The sixth embodiment is an example relating to "creating a batch remittance request" in the above-mentioned batch processing.
The contents described in the sixth embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

<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.
In the current position display area CLR1 at the upper part of the screen, the user D. The characters "Remittance request with DD" indicating that the unprocessed request with D is displayed are displayed.
Further, in the current position display area CLR1, the user D. Among the unprocessed requests with D, the state in which the first to fourth remittance requests are selected is shown.

When the selected 1st to 4th remittance requests are settled in a lump sum, the lump sum settlement will be "payment 1,100 yen", and the user A. From A to user D. You will pay "1,100 yen" to D. However, in this example, User A. Since the current balance of the electronic money account of A is "500 yen", the payment amount will be insufficient by "600 yen".

Therefore, in this embodiment, the server 10 creates a batch remittance request based on the amount of the shortage of payment when the batch settlement is performed.
However, in this embodiment, the batch remittance request is created, but the batch settlement is not performed.

Specifically, in the settlement content confirmation area ACR7 at the bottom of the screen, "500 yen" is displayed as one's current electronic commerce account balance and one's own electronic commerce account balance when settlement is performed. ..

Below that, a suggestion button BT9 and a cancel button are displayed along with the text "Do you want to make a suggestion to put together the request?".
When the proposal button BT9 is tapped in this state, a new remittance request is created based on the amount of the shortage of payment, "1,100 yen". As a result, the screen as shown in FIG. 6-2 is displayed.

In Fig. 6-2, as a newly created remittance request, a batch remittance request with a payment amount of "1,100 yen", which is a received remittance request and is a collection of four remittance requests, is displayed. ing.
In this display screen example, the batch remittance request includes the four remittance requests selected in FIG. 6-1, that is, the remittance request (collected remittance request) used to create the batch remittance request. It is displayed in the format. Further, for the user to easily recognize, these remittance requests are displayed in a display mode different from other remittance requests (grayed out in this example).

Note that unlike this display screen example, the remittance request used to create the batch remittance request may not be displayed.
Also, based on the tapping of the batch remittance request, the remittance request used to create the batch remittance request may be displayed.

<Processing>
FIG. 6-3 is a flowchart showing an example of the flow of the batch 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 determines whether or not the terminal 20 has requested the creation of the batch remittance request based on whether or not the batch remittance request creation request information has been received from the terminal 20 (S510).
The bulk remittance request creation request information may include, as an example, not limited to, selection information of the remittance request for which the batch remittance request is created.

If it is determined that the request has been made (S510: YES), the control unit 11 of the server 10 refers to the remittance request management data 157, and the remittance request amount of each selected remittance request and its type (received remittance request). Based on (payment) / sent remittance request (receipt)), the remittance request amount (hereinafter referred to as "lump-sum remittance request amount") of the batch remittance request to be created is calculated (S530).

After that, the control unit 11 of the server 10 creates a batch remittance request based on the calculated batch remittance request amount, and stores the created batch remittance request data in the remittance request management data 157 (S550).

Next, the control unit 11 of the server 10 transmits the batch remittance request creation result information regarding the creation result of the batch remittance request to the requesting terminal 20 by the communication I / F 14 (S570).
Then, the control unit 11 of the server 10 ends the batch remittance request creation process.

After performing this process, the terminal 20 displays the batch remittance request information corresponding to the batch remittance request on the remittance request list screen or the like displayed on the display unit 24. Then, based on this batch remittance request, it becomes possible to execute the batch settlement.

When it is determined in S510 that the terminal 20 has not requested the creation of the batch remittance request (S510: NO), the control unit 11 of the server 10 is not limited to the above, but as an example, based on the request from the terminal 20. It is also possible to perform other batch processing such as batch settlement and the request offset described above.

In addition, a malicious user may create the above-mentioned false remittance request and then create a batch remittance request including the remittance request.
Therefore, the approval of the other party may be required or not required to create the batch remittance request.

<Effect of the sixth embodiment>
In this embodiment, the other user is one user (not limited, but an example in which the second user is the first user), and the first process includes the first remittance request information and the second remittance request information. Remittance request information (not limited to, but an example of the third information regarding the remittance request from the first user to the terminal user or the remittance request from the terminal user to the other user) The configuration including the process of displaying the display of the remittance request (not limited, but an example of the sixth display) on the display unit 24 is shown.
As an example of the effect of the embodiment obtained by such a configuration, when the other user is one user, the sixth display based on the third information summarizing the information on a plurality of remittance requests is displayed, and the third display is displayed. 3 Information can be notified to the user of the terminal. Further, as an example, not limited to this, it is possible to perform comprehensive settlement based on the third information that summarizes information on a plurality of remittance requests, so that the convenience of the user can be improved.

<7th Example>
The seventh embodiment is an example relating to "creation of a special batch settlement / special batch remittance request" in the above-mentioned batch processing.
The contents described in the seventh embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

<Display screen>
FIG. 7-1 is a diagram showing an example of the remittance request list screen displayed on the display unit 24 of the terminal 20A in this embodiment, and is the same as that of FIG. 6-1. Shows a screen displaying a list of remittance requests with D. Here, as in FIG. 6-1 the state in which the first to fourth remittance requests are selected is shown.

When the selected 1st to 4th remittance requests are settled in a lump sum, the lump sum settlement will be "payment 1,100 yen", and the user A. From A to user D. You will pay "1,100 yen" to D. However, in this example, User A. Since the current balance of the electronic money account of A is "500 yen", the payment amount will be insufficient by "600 yen".

In this case, in this embodiment, the control unit 11 of the server 10 is the user A. All amounts of A's current e-commerce account balance are used by User D. Make a lump sum payment by sending money to D and making a payment.
Further, the control unit 11 of the server 10 creates a new remittance request in which the amount of the shortage of payment in the lump sum settlement is used as the remittance request amount.
That is, in this embodiment, unlike the sixth embodiment, a new remittance request is made in which the amount that cannot be paid is set as the remittance request amount after payment is made to the extent that the balance of the proposer's user can be paid. create.

For convenience, a lump sum payment that makes payments to the extent possible based on multiple remittance requests is called a "special lump sum payment", and a lump sum remittance request that is newly created after performing a special lump sum payment is called a "special lump sum payment". Called "Remittance Request".

Specifically, in the settlement content confirmation area ACR8 at the bottom of the screen, "500 yen" is the current electronic commerce account balance of oneself, and "0 yen" is the balance of one's own electronic commerce account when the settlement is performed. It is displayed. Then, when the suggestion button is tapped in this state, the user A. User A. "500 yen", which is the total amount of A's current electronic commerce account balance. From A to user D. A special lump sum payment that is sent to and paid to D is executed. After that, a special batch remittance request is created based on the amount of the shortage of payment, "600 yen". As a result, the screen as shown in FIG. 7-2 is displayed.

In FIG. 7-2, as a special batch remittance request, a special batch remittance request with a payment amount of "600 yen" is displayed.
In this display screen example, the special remittance request includes the four remittance requests selected in FIG. 7-1, that is, the remittance request used to create the special remittance request (collected remittance request). Is displayed in a hanging format. Further, for the user's convenience, these remittance requests are displayed in a display mode (grayed out in this example) different from the normal remittance request.

Note that unlike this display screen example, the remittance request used to create the special batch remittance request may not be displayed.
Also, based on the tapping of the special batch remittance request, the remittance request used to create the special batch remittance request may be displayed.

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

After S1515, the control unit 11 of the server 10 determines whether or not the electronic money account balance of any user is negative (S1520), and if it is determined to be negative (S1520: YES), the electronic money. It is determined whether or not it is the proposer's user that the account balance becomes negative (S1570).

If it is determined that it is the proposer's user that the electronic commerce account balance becomes negative (S1570: YES), the control unit 11 of the server 10 includes the type of batch settlement to be executed (normal). The batch settlement type confirmation information for confirming the batch settlement / special batch settlement) is transmitted to the terminal 20A by the communication I / F14 (S1571).
In this case, the above-mentioned balance shortage information may or may not be included in the batch settlement type confirmation information and transmitted.

After that, the control unit 11 of the server 10 determines whether or not the execution of the special batch settlement is requested based on the receipt of the settlement execution request information including the information of the type of the batch settlement requesting execution from the terminal 20A. (S1574). When it is determined that the execution of the above-mentioned normal batch settlement is requested instead of the special batch settlement (S1574: NO), the control unit 11 of the server 10 processes the process in S1555 of FIG. 2-5 as an example, not a limitation. Move.

On the other hand, if it is determined that the execution of the special batch settlement is requested (S1574: YES), the control unit 11 of the server 10 determines whether or not the approval of the other user is required (S1575).
If it is determined that the approval of the other user is required (S1575: YES), the control unit 11 of the server 10 uses the information of the settlement amount by the special batch settlement (hereinafter referred to as "special batch settlement amount"). The special lump sum settlement approval confirmation information including a certain special lump sum settlement amount information is transmitted to the terminal 20B by the communication I / F14 (S1577).
The special lump sum settlement amount is not limited, but can be, as an example, an amount corresponding to the current electronic money account balance of the proposer user.

Not limited to this, the special lump sum settlement amount may be any amount as long as it is larger than "0" and equal to or less than the current electronic money account balance of the proposer user.

After that, the control unit 11 of the server 10 determines whether or not the special batch settlement has been approved by determining whether or not the special batch settlement approval information indicating that the special batch settlement is approved has been received from the terminal 20B. (S1579).

Then, if it is determined that the approval is made (S1579: YES), the control unit 11 of the server 10 executes the special batch settlement (S1581). Specifically, the control unit 11 of the server 10 updates the electronic commerce account balance of the proposer user (user A.A. in this example) to zero, and sets the special lump sum settlement amount to the other user (in this example). It is updated by adding it to the electronic money account balance of user BB).

After that, the control unit 11 of the server 10 creates a special batch remittance request (S1583). Specifically, the control unit 11 of the server 10 creates a remittance request from the other user to the proposer user as a special batch remittance request, in which the amount obtained by subtracting the special batch settlement amount from the batch settlement amount is used as the remittance request amount. do.
Then, the control unit 11 of the server 10 ends the fourth settlement process.

As described above, the method of paying up to the point where the balance of the proposer's user can be paid is not limited to the case where multiple remittance requests are selected as described above, but also when one remittance request is selected. Is also applicable.
That is, when one received remittance request whose remittance request amount is larger than the amount of the current electronic money account balance of the proposer user is selected, the control unit 11 of the server 10 electronically uses the remittance request amount. Create a remittance request with the amount obtained by subtracting the amount of the money account balance (the amount of the shortfall) as the remittance request amount.

<Second processing by terminal)>
In this embodiment, the control unit 21 of the terminal 20 processes at least one piece of information based on the electronic money account balance (balance of the terminal user) of the user of the terminal 20 in addition to the first process described above. 2 It is possible to execute the process.

As an example, not a limitation, at least the following processing is included in the second processing.
-Processing to send request selection information to server 10-Processing to receive batch settlement confirmation information from server 10-Processing to display batch settlement confirmation information-Processing to receive batch settlement result information from server 10-Processing to receive batch settlement result information Process to display-Process to request server 10 to deduct amount (including amount offset) -Process to request server 10 to execute special batch settlement-Process to request server 10 to create special batch remittance request

<Effect of the 7th Example>
In this embodiment, out of a plurality of remittance request information regarding a remittance request to a user of a batch settlement proposer (not limited to an example of a terminal user) or a remittance request by a user of a batch settlement proposer, the batch settlement is performed. Second process (not limited, but at least one) for batch settlement for at least one remittance request information based on the proposer's user's e-commerce account balance (not limited, but an example of the terminal user's balance) An example of the second process for processing information) shows a configuration executed by the terminal 20 of the user who proposes the batch settlement.
As an example of the effect of the embodiment obtained by such a configuration, at least one of a plurality of information regarding a remittance request to the terminal user or a remittance request by the terminal user in consideration of the balance of the terminal user. Since the information can be processed by the second process, the convenience of the user can be improved.

<7th modification>
Although related to the first modification (3), in the seventh embodiment, the proposer's terminal 20 or the server 10 automatically selects a remittance request based on the current electronic money account balance of the proposer's user. (Including suggestions.) It may or may not be.

Specifically, the control unit 21 of the proposer's terminal 20 performs a process of inquiring 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 determines each remittance request amount and each remittance request type (received remittance request (received remittance request) from among the remittance requests included in the remittance request list information received from the server 10. Based on (payment) / sent remittance request (receipt)), as an example, but not limited to, identify and select a combination of remittance requests that results in payments that exceed the proposer's user's current e-commerce account balance.

In this case, as an example, not a limitation, in FIG. 7-1, the user D. Among the unprocessed requests with D, as an example, not limited, the remittance request that is automatically selected as the request to be processed for batch settlement in order from the past remittance request and the balance becomes insufficient (the fourth remittance request in this example). ) May or may not be suggested to the user.

When the control unit 11 of the server 10 selects a remittance request, the same processing may be performed based on the remittance request data stored in the remittance request management data 157.

In this modification, in the second process, the remittance request information that can be processed by the electronic money account balance of the proposer user (not limited, but an example of the balance of the terminal user) is selected from a plurality of remittance request information. Shows a configuration that includes processing and processes selected information.
As an example of the effect of the embodiment obtained by such a configuration, since the information that can be processed by the balance of the terminal user is selected and processed, it is not limited, but as an example, the range in which the balance of the terminal user does not become negative. Since the information can be processed by the user, the convenience of the user can be further improved.

<Eighth Example>
The eighth embodiment is an embodiment in which an unprocessed request is displayed when the user of the terminal 20 makes a remittance to the other user or makes a remittance request to the other user.
The contents described in the eighth embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

<Display screen>
FIG. 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 not limited, but as an example, User A. It is a remittance screen of the payment application displayed on the display unit 24 of the terminal 20A of A.
In the current position display area CLR1 indicating the current position in the payment application, the character "remittance" indicating that the current position is the remittance function of the payment application is displayed.

Below the current position display area CLR1, an icon image and a user name (user EE in this example) in the payment application of the user selected as the remittance destination are displayed. Below that, the remittance amount to the user selected as the remittance destination (in this example, "500 yen") and the function button for increasing the remittance amount by a certain amount are displayed.

Below that, it is configured to make it possible to confirm unprocessed requests between the user selected as the remittance destination (user EE in this example) and the user who makes the remittance (user AA in this example). The unprocessed request confirmation area URR1 that has been created is displayed.

At the top of the unprocessed request confirmation area URR1, the user E.I. The characters "Unsettled request with EE" indicating that the unprocessed request with E is displayed are displayed.

Further, below that, the lump sum settlement amount (“1,500 yen” in this example) and the mark (“payment mark” in this example) are displayed on the assumption that all selection batch settlement is performed.
In addition, it is not necessary to have a display column when it is assumed that this all-selection batch settlement is performed.

Below that, the other party is the user E. A list of remittance requests with E is displayed. In this example, the other party is the user E.I. The unprocessed requests set to E are listed in chronological order from the top to the oldest.

Further, below the unprocessed request confirmation area URR1, a remittance button indicating "remittance" is displayed for executing remittance (remittance processing).
When the remittance button is tapped, the remittance process (remittance from user AA to user EE) is executed by the server 10.

The remittance button is not limited, but may be displayed in an area above the unprocessed request confirmation area URR1 under the display area of the function button for increasing the remittance amount by a certain amount.

As described above, in this embodiment, by displaying the unprocessed request together with the information for remittance, the user can confirm the unprocessed request at the time of remittance.

FIG. 8-2 is a diagram showing another example of the screen displayed on the display unit 24 of the terminal 20 in this embodiment. This screen is not limited, but as an example, User A. It is a remittance request screen of the payment application displayed on the display unit 24 of the terminal 20A of A.
In the current position display area CLR1 indicating the current position in the payment application, the characters "remittance request" indicating that the current position is the remittance request function of the payment application are displayed.

Below the current position display area CLR1, an icon image and a user name (user EE in this example) in the payment application of the user selected as the destination of the remittance request are displayed. Below that, the remittance request amount ("500 yen" in this example) for the user selected as the destination of the remittance request and the function button for increasing the remittance request amount by a certain amount are displayed. There is.

When the user selected as the destination of the remittance request accepts the remittance request, the electronic money account of the user who made (sent) the remittance request from the electronic money account of the user selected as the destination of the remittance request Then, the remittance for the amount of the remittance request is executed.

Further, below that, the unprocessed request confirmation area URR1 is displayed as in FIG. 8-1. Below that, a remittance request button indicating "request for remittance" is displayed for executing the transmission of the remittance request (remittance request transmission processing).
When the remittance request button is tapped, the remittance request transmission process (transmission of remittance request information from the user AA to the user EE) is executed by the server 10.

The remittance request button is not limited, but may be displayed in an area above the unprocessed request confirmation area URR1 under the display area of the function button for increasing the remittance request amount by a certain amount.

As described above, in this embodiment, by displaying the unprocessed request together with the information for sending the remittance request, the user can confirm the unprocessed request at the same time when making the remittance request. ing.

<Processing>
FIG. 8-3 is a flowchart showing an example of the flow of processing executed by each device in this embodiment. Here, as an example, the process of displaying an unprocessed request when the user makes a remittance, which was described with reference to FIG. 8-1, will be described.

First, the control unit 21 of the terminal 20A determines whether or not an input for displaying the remittance screen has been made to the input unit (A105).
If it is determined that the input has been made (A105: YES), the control unit 21 of the terminal 20A performs the processing of the A110, and the remittance is based on the fact that the remittance request list information is received from the server 10 by the communication I / F22. The remittance screen (remittance screen) including the request list information is displayed on the display unit 24 (A125).

After that, the control unit 21 of the terminal 20A determines whether or not an input for executing the remittance (not limited but, as an example, an operation of the remittance button) has been made (A630).
If it is determined that the input for executing the remittance has not been made (A630: NO), the control unit 21 of the terminal 20A ends the process.

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

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

On the other hand, if it is determined that the remittance request information has been received (S640: YES), the control unit 11 of the server 10 executes the remittance process (S650). Specifically, as an example, not limited, the remittance confirmation information for confirming the remittance content is transmitted to the terminal 20A by the communication I / F14, and the remittance execution request information is received from the terminal 20A by the communication I / F14. Based on User A. From A to user B. Execute the remittance to B.
In this case, the control unit 21 of the terminal 20A executes the processing of A650 to A670 as an example without limitation.

After that, the control unit 11 of the server 10 determines whether or not the remittance result is "OK" (S670). Then, if it is determined that the result is "OK" (S670: YES), the control unit 11 of the server 10 transmits the remittance result information to the terminal 20A and the terminal 20B by the communication I / F14 (S690).
Then, the control unit 11 of the server 10 ends the process.

When the remittance result information is received from the server 10 by the communication 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.

Similarly, when the remittance result information is received from the server 10 by the communication 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.

Regarding the process of displaying the unprocessed request when the user makes a remittance request described in FIG. 8-2, similarly, by replacing "remittance" in the process of FIG. 8-3 with "remittance request transmission". Since it can be configured, the illustration and description will be omitted.
Specifically, in the processing of the terminal 20A, it is determined whether or not the input for displaying the remittance request transmission screen is made in A105, the remittance request transmission screen including the remittance request list information is displayed in A125, and the remittance request transmission screen is displayed in A630. It is determined whether or not to execute the remittance request transmission, the remittance request transmission request information is transmitted by A640, the remittance request transmission confirmation information is displayed by A650, and it is determined whether or not the remittance request transmission execution request is made by A660. , A670 remittance request transmission execution request information is transmitted, and A690 displays remittance request transmission result information.
Further, in the processing of the terminal 20B, the remittance request transmission result information is displayed on the B690.
Further, in the process of the server 10, it is determined in S640 whether or not the remittance request transmission request information is received, in S650 the remittance request transmission process is executed, and in S670 it is determined whether or not the remittance request transmission result is OK. Then, the remittance request transmission result information is transmitted in S690.

<Display of unprocessed requests>
The unprocessed request to be displayed on the display unit 24 of the terminal 20 is not limited, but may be one or both of the following as an example.
-Unprocessed request corresponding to the user of the other party to send money (remittance destination user) or the user of the other party to send the remittance request (remittance request destination user) -The user of the other party to send remittance (remittance destination user) or send the remittance request Unprocessed request corresponding to a user different from the other user (remittance request destination user)

It is possible to display the outstanding request corresponding to the other user. As an example, not a limitation, as shown in FIG. 8-1, User A. A is user E. When remittance is made with E as the remittance destination user, or as shown in FIG. 8-2, the user A. A is user E. When sending a remittance request with E as the remittance request destination user, the user E. The unprocessed request corresponding to E can be displayed.

However, some users may want to see outstanding requests that correspond to a user different from the other user.
Therefore, as an example, not limited to, in FIG. 8-1 and FIG. 8-2, the user E.I. In addition to the unprocessed request corresponding to E, as an example, not a limitation, User B. B and user C. It is also possible to display the unprocessed request corresponding to C.
In this case, the user E.I. The unprocessed request corresponding to E is not displayed, and as an example, not limited to the user B. B and user C. It is also possible to display the unprocessed request corresponding to C.

That is, as a pattern for displaying an unprocessed request, the following three patterns can be considered as an example, not limited.
(Pattern 1) Unprocessed request corresponding to the other user (Pattern 2) Unprocessed request corresponding to the other user + Unprocessed request corresponding to a user different from the other user (Pattern 3) Different from the other user Outgoing request corresponding to user

Further, when applying any of the above patterns, for each user, all the unprocessed requests corresponding to the user may be displayed, or some unprocessed requests corresponding to the user may be displayed. It may be displayed.
That is, the user who displays the unprocessed request (the other user / the user different from the other user) and the range of the unprocessed request to be displayed (all / part) can be arbitrarily combined. As an example, not limited to (Pattern 2), the unprocessed requests corresponding to the other user display all the unprocessed requests, but the unprocessed requests corresponding to the user different from the other user are partially unprocessed. You may also display the request.

Further, when displaying some unprocessed requests, it is possible to determine the unprocessed requests to be displayed based on various information (conditions).
In this case, the contents of the 16th embodiment described later can be combined. As will be described in the 16th embodiment, the following information is mentioned as an example without limitation as various kinds of information.
-Date and time when the remittance request was sent / received-Remittance request amount-Payment deadline for the remittance request-A remittance request in which a user other than the user who requested the remittance and the user who requested the remittance is involved in the remittance request amount or reason , These information are merely examples and are not limited to these.
It is also possible to apply a plurality of of these pieces of information in combination.

Unprocessed requests with dates or dates older than a certain date may be forgotten by the user. Therefore, even an unprocessed request corresponding to a user different from the other user can be determined to be displayed.
Unprocessed requests with a remittance request amount larger than a certain amount may be of high importance. Therefore, even an unprocessed request corresponding to a user different from the other user can be determined to be displayed.
Remittance requests in which the user who requested the remittance and other users other than the user who requested the remittance are involved in the amount or reason of the remittance request may also be of high importance. Therefore, even an unprocessed request corresponding to a user different from the other user can be determined to be displayed.
Unprocessed requests whose payment deadline is approaching within a certain period may require immediate processing. Therefore, even an unprocessed request corresponding to a user different from the other user can be determined to be displayed.

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

In addition to these, the unprocessed request to be displayed on the display unit 24 of the terminal 20 can be hidden based on the input of the user of the terminal 20 to the input unit, as an example without limitation.
In this case, as an example, the unprocessed requests corresponding to some users may be hidden, or the unprocessed requests corresponding to all users may be hidden.

In addition, depending on the user, it may be annoying to display the unprocessed request.
Therefore, it may be possible to set the display / non-display of the unprocessed request on a setting screen (not shown) or the like.

Specifically, on the setting screen of the application, as setting information regarding the display of the unprocessed request, a slide button or a check box that can switch the display / non-display of the unprocessed request is displayed as an example, not limited. Then, based on the operation for the slide button and the check box, the terminal 20 or the server 10 can be made to perform the display / non-display setting.

In this case, it may be possible to set the display / non-display of unprocessed requests collectively for all users, or it may be possible to set the display / non-display of unprocessed requests individually for each user.
Further, it may be possible to set the display / non-display of all unprocessed requests, or it may be possible to set the display / non-display of some unprocessed requests.

These contents are the same for the following examples.

<Effect of the eighth embodiment>
In this embodiment, the terminal 20 of the proposer user is remittance information from the proposer user (not limited, but an example of a terminal user) to the other user (not limited, an example of a first user). (Not limited, but an example of the first information regarding the remittance from the terminal user to the first user), or the information for sending the remittance request from the proposer user to the other user (not limited, but the terminal user to the first). 1 The first display based on (an example of the first information about the remittance request to be sent to the user) and the remittance request information about the received remittance request that the proposer user has received from the other user (not limited, but from the second user). (An example of the second information about the remittance request sent to the user of the terminal), or the remittance request information about the sent remittance request sent to the other user by the proposer user (not limited to the second user from the user of the terminal). A configuration is shown in which the display unit 24 displays the second display based on (an example of the second information regarding the remittance request transmitted to).
As an example of the effect of the embodiment obtained by such a configuration, when the user of the terminal confirms the first information, the second information can be confirmed at the same time.

Further, in this embodiment, the terminal 20 of the proposer user is a process for remittance based on the input to the terminal 20 on which the first display is displayed by the proposer user (processing related to remittance, not limitation). An example) is shown in which the control unit 21 performs the operation.
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 the input to the terminal on which the first display is displayed.

<8th modification>
In the above embodiment, settlement (collective settlement of unprocessed requests) is performed based on the input for the information of the unprocessed request displayed together with the information for remittance to the other user and the information for sending the remittance request to the other user. Including.) Can also be executed.

Specifically, not limited to the screen example of FIG. 8-1, in addition to the remittance button, a settlement button for executing settlement of selected unprocessed requests (collective settlement if multiple selections are made) is displayed. Let me.
Then, when the settlement button is tapped, the settlement process of the selected unprocessed request can be executed by the server 10.

Similarly, in the screen example of FIG. 8-2, not limited to this, in addition to the remittance request button, a settlement button for executing settlement of the selected unprocessed request (collective settlement if multiple selections are made) is displayed. ..
Then, when the settlement button is tapped, the settlement process of the selected unprocessed request can be executed by the server 10.

Since the settlement processing of the unprocessed request is as described above, the description thereof will be omitted again.

FIG. 8-4 is a flowchart showing an example of the flow of processing executed by each device in this modification. Here, as an example, in the process of displaying the unprocessed request when the user performs the remittance shown in FIG. 8-3, a process of performing either the remittance or the settlement of the unprocessed request will be described.

After A125, the control unit 21 of the terminal 20A determines the execution target based on the input to the input unit (A631).
If it is determined that the execution target is the settlement of unprocessed requests (collective settlement when multiple selections are made) (A631: settlement of unprocessed requests), the control unit 21 of the terminal 20A selects the selected unprocessed requests. Request selection information including the indicated unprocessed request selection information is set (A632).

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

After A632 or A133, the control unit 21 of the terminal 20A transmits the set request selection information to the server 10 by the communication I / F22 (A140).
Then, the control unit 21 of the terminal 20A shifts the processing to the A150.

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

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 the settlement target (in the case of multiple selections, the batch settlement target) ( S642).
On the other hand, if it is determined that the processing target is "remittance", the control unit 11 of the server 10 sets the remittance as the settlement target (S143).

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

When applying the first settlement process described in FIG. 1-19 as an example rather than a limitation,
When S642 is set and there are a plurality of unprocessed requests to be processed, the determination result of whether or not the settlement target in S1510 is a batch settlement target is "YES". As a result, the processing after S1515 is executed with the plurality of unprocessed requests as the batch settlement target. Further, when S642 is set and there is only one unprocessed request to be processed, the determination result of whether or not the settlement target in S1510 is the batch settlement target is "NO". As a result, the processing after S1570 is executed with this one unprocessed request as the settlement target.
On the other hand, when the setting of S143 is made, the determination result of whether or not the settlement target in S1510 is the batch settlement target is "NO". As a result, the process after S1570 is executed with the remittance as the settlement target.

For the process of displaying the unprocessed request when the user makes the remittance request and performing either the transmission of the remittance request or the settlement of the unprocessed request, refer to "Remittance" in the process of FIG. 8-4. Since it can be configured in the same way by replacing it with "remittance request transmission", the illustration and description are omitted.
Specifically, in the processing of the terminal 20A, it is determined whether or not the input for displaying the remittance request transmission screen is made in A105, the remittance request transmission screen including the remittance request list information is displayed in A125, and the remittance request transmission screen is displayed in A631. It is determined whether the execution target is the settlement of the unprocessed request or the remittance request transmission, and the request selection information including the remittance request transmission information is set in A133.
Further, in the processing of the server 10, S641 determines whether the processing target is the settlement of the unprocessed request or the remittance request transmission, and the remittance request transmission is set as the settlement target in S143.

In this modification, the terminal 20 of the proposer user is remittance information from the proposer user (not limited, but an example of a terminal user) to the other user (not limited, an example of a first user). (Not limited, but an example of the first information regarding the remittance from the terminal user to the first user), or the information for sending the remittance request from the proposer user to the other user (not limited, but the terminal user to the first). 1 The first display based on (an example of the first information about the remittance request to be sent to the user) and the remittance request information about the received remittance request that the proposer user has received from the other user (not limited, but from the second user). (An example of the second information about the remittance request sent to the user of the terminal), or the remittance request information about the sent remittance request sent to the other user by the proposer user (not limited to the second user from the user of the terminal). The second display based on (an example of the second information regarding the remittance request sent to) is displayed on the display unit 24.
Then, the terminal 20 of the proposer's user is to process for remittance or receive the remittance amount based on the input to the terminal 20 on which the first display or the second display is displayed by the proposer's user. Processing, or processing for transmitting / receiving a remittance request (remittance reminding) (not limited to, but an example of the first processing relating to remittance, receiving remittance, or requesting remittance) is performed by the control unit 21. The configuration is shown.
As an example of the effect of the embodiment obtained by such a configuration, remittance to the other user or receipt of remittance from the other user based on the input to the terminal on which the first display or the second display is displayed, It is possible to easily send / receive a remittance request to the other user.

Next, as an embodiment related to the eighth embodiment, when the user of the terminal 20 remits money to the other user or sends a remittance request to the other user, a selection is made from the displayed unprocessed requests. An embodiment in which the unprocessed request is also processed will be described.

In the following examples, the following five patterns will be roughly described.
(A) Remittance + Received remittance request processing pattern (B) Remittance + Sent remittance request processing pattern (C) Remittance request transmission + Received remittance request processing pattern (D) Remittance request transmission + Patterns for processing sent remittance requests (E) Patterns for processing remittance requests + received remittance requests + sent remittance requests Each pattern will be described separately with examples.

As shown in the eighth modification, the process (first process, etc.) executed by the terminal 20 by the control unit 21 is not limited, but as an example, a process for performing remittance (not limited, but a process related to remittance). (Example), processing for receiving (receipt) remittance (an example of processing related to receiving remittance, not limitation), processing for sending / receiving remittance request (processing related to request for remittance, not limitation) Example) processing such as) is included.
In the following, a server-client system will be illustrated, and remittance, remittance request transmission, and the like will be performed via the server 10.

Further, 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) is illustrated.
As described above, when the other user is a plurality of different users, that is, the first user is a user different from the second user (the second user is a user different from the first user). Similarly, the method described below can be applied to the above.

<9th Example>
The ninth embodiment is an example relating to the processing of the pattern of the above (A).
The contents described in the ninth embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

In this embodiment, in addition to including the "received remittance request" among the unprocessed requests in the batch settlement target, the batch settlement is performed by including the "remittance" in the batch settlement target.

FIG. 9-1 is a diagram showing an example of a table for explaining a processing method corresponding to each pattern.
The vertical direction of the table shows the processing target (new processing target) to be newly executed as an item, and the horizontal direction of the table shows the type of unprocessed request as an item. And, in the column where the vertical item and the horizontal item intersect, an example of the processing realized by the combination of the new processing target and the unprocessed request of the type is shown.

In this embodiment, the processing of the pattern of (A) remittance + received remittance request will be described. In this pattern, (A1) remittance [remittance + remittance] can be processed.
That is, when making a new remittance to the other user, the remittance to the other party is also performed based on the received remittance request from the other user. More specifically, the sum of the amount to be remitted to the other user by a new remittance and the remittance request amount included in the received remittance request information (the amount requested by the other user to remit) is the other party. Send money to your users.

<Display screen>
An example of a display screen when the above process (A1) is performed will be described.
FIG. 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 not limited, but as an example, User A. It is a remittance screen of the payment application displayed on the display unit 24 of the terminal 20A of A.
In the current position display area CLR1 indicating the current position in the payment application, the character "remittance" indicating that the current position is the remittance function of the payment application is displayed.

Below the current position display area CLR1, an icon image and a user name (user EE in this example) in the payment application of the user selected as the remittance destination are displayed. Below that, the remittance amount to the user selected as the remittance destination (in this example, "500 yen") and the function button for increasing the remittance amount by a certain amount are displayed.

Below that, it is configured to make it possible to confirm unprocessed requests between the user selected as the remittance destination (user EE in this example) and the user who makes the remittance (user AA in this example). The unprocessed request confirmation area URR1 that has been created is displayed.

At the top of the unprocessed request confirmation area URR1, the user E.I. The characters "Unsettled request with EE" indicating that the unprocessed request with E is displayed are displayed.
Further, below that, the lump sum settlement amount (“1,500 yen” in this example) and the mark (“payment mark” in this example) are displayed on the assumption that all selection batch settlement is performed.

Below that, the other party is the user E. A list of remittance requests with E is displayed. In this example, the other party is the user E.I. The unprocessed requests set to E are listed in chronological order from the top to the oldest. Since the display mode of each unprocessed request can be configured in the same manner as in FIG. 1-11 as an example without limitation, the description thereof will be omitted again.

Below the unprocessed request confirmation area URR1, a remittance all-selection batch settlement button indicating "all settlement and remittance" is displayed for executing the remittance processing and all-selection batch settlement. Below that, the remittance batch settlement indicated as "one settlement and transmission" for executing the remittance processing and the partial selection batch settlement of the unprocessed request selected in the unprocessed request confirmation area URR1. Button BT11 is displayed. Below that, there is a remittance button that says "Remittance only" to execute only the remittance process.

As an example, not limited, in the unprocessed request confirmation area URR1, the check of the request of the first received remittance request (payment 2,500 yen) is selected as "ON", and the remittance batch settlement button BT11 is tapped. Then, the terminal 20A requests the server 10 to execute the remittance and the batch settlement of the selected unprocessed requests. Then, from the server 10, the user E. Settlement result information regarding the execution result is transmitted to the terminal 20E of E.

FIG. 9-3 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20E based on the tapping of the remittance batch settlement button BT11.
In this example, in the notification information display area NTR4 of the notification screen, two settlement result information is displayed as the contents of the remittance and the batch settlement.
Specifically, as an example, not a limitation, the user A. A is user E. User A. by receiving the remittance amount "500 yen" sent to E and the first remittance request selected in FIG. 9-2. A is user E. The settlement result information corresponding to the receipt of the remittance amount "2,500 yen" sent based on the remittance request amount "2,500 yen" by the remittance request received from E is displayed.

As shown in FIG. 9-4, the two settlement result information may be combined and displayed as one settlement result information in the notification information display area NTR4 on the notification screen, or the payment result information may not be displayed. May be good.
As an example, not a limitation, in FIG. 9-4, as the settlement result information, the user E.I. E is the user A. The remittance amount "500 yen" by receiving the remittance from A and the user A. Information regarding receiving "3,000 yen", which is the sum of the remittance request amount "2,500 yen" by the remittance request to A and the remittance amount "2,500 yen" by receiving the remittance request amount "2,500 yen", is displayed.

In FIG. 9-2, the unprocessed request confirmation area URR1 displays the unprocessed requests between the user selected as the remittance destination and the user who performs the remittance, but the present invention is not limited to this.

FIG. 9-5 shows an example of a display screen when displaying all unprocessed requests of the user who makes the remittance. FIG. 9-5 is another example of the remittance screen of FIG. 9-2.

In FIG. 9-5, in the unprocessed request confirmation area URR2, all unprocessed requests of the user who performs remittance are listed in chronological order from the top to the oldest. Further, below the unprocessed request confirmation area URR2, a remittance batch settlement button BT11 and a remittance button are displayed. As an example, not a limitation, in the unprocessed request confirmation area URR2, the fourth user E.I. When the check of the received remittance request (payment 2,500 yen) request from E is selected as "ON" and the remittance batch settlement button BT11 is tapped, the display screen of Fig. 9-3 is displayed on the terminal 20E. It is displayed on the display unit 24.

<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 flowchart in which the flowchart of FIG. 1-18 is rewritten into a process in which the new processing target is “remittance”.

In the processing of the pattern (A) remittance + received remittance request in this embodiment, remittance is unilaterally sent to the other user, so that the approval of the other user is not required when performing batch settlement. be able to. Therefore, here, it is illustrated and described as a process that does not require the approval of the other user.
It should be noted that the present invention is not limited to this, and the approval of the other user may be required.

After A125, the control unit 21 of the terminal 20A determines whether or not an unprocessed request is selected from the remittance request list information (A131).

If an unprocessed request is selected, that is, if it is determined that the remittance + processing of the unprocessed request is requested (A131: YES), the control unit 21 of the terminal 20A selects the remittance information regarding the remittance to be executed. Request selection information including unprocessed request selection information indicating the processed unprocessed request is set (A132).

On the other hand, when an unprocessed request is not selected from the remittance request list information, that is, when it is determined that only the remittance is executed (A131: NO), the control unit 21 of the terminal 20A inputs the remittance information regarding the remittance to be executed. The request selection information to be included is set (A133).

It should be noted that this process will be described on the premise that remittance is performed.
In reality, it may be selected to process only unprocessed requests without remittance, but the processing in this case is the same as the processing of batch settlement of unprocessed requests described above, so it is shown in the figure.・ Omitting the explanation again,

After A132 or A133, the control unit 21 of the terminal 20A transmits the set request selection information to the server 10 by the communication I / F22 (A140).
Then, the control unit 21 of the terminal 20A shifts the processing to the A150.

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 makes a remittance + unprocessed request based on the information included in the received request selection information. It is determined whether or not to process (S141). Then, if it is determined to be processed (S141: YES), the control unit 11 of the server 10 sets remittance + settlement of the selected unprocessed request (collective settlement when a plurality of selections are made) as the batch settlement target. (S142).

On the other hand, if it is determined that the remittance + unprocessed request is not processed, that is, only the remittance is executed (S141: NO), the control unit 11 of the server 10 sets the remittance as the settlement target (S143).

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

When applying the first settlement process described in FIG. 1-19 as an example rather than a limitation,
When the setting of S142 is made, the determination result of whether or not the settlement target in S1510 is the batch settlement target is "YES". As a result, the processing after S1515 is executed with the remittance + the settlement of the selected unprocessed request as the batch settlement target.
On the other hand, when the setting of S143 is made, the determination result of whether or not the settlement target in S1510 is the batch settlement target is "NO". As a result, the process after S1570 is executed with the remittance as the settlement target.

<Effect of 9th Example>
In this embodiment, the terminal 20 of the proposer user has remittance information (limited) from the proposer user (not limited, but an example of a terminal user) to the other user (not limited, an example of a first user). Not the remittance request information about the remittance request from the terminal user to the first user) or the remittance request sent from the proposer user to the other user (not limited, but the first from the terminal user). The first display based on (an example of the first information regarding the remittance request to be sent to the user) and the remittance request information regarding the received remittance request that the proposer user has received from the other user (not limited, but from the second user to the terminal). (An example of the second information about the remittance request sent to the user), or the remittance request information about the sent remittance request sent to the other user by the proposer user (not limited to the terminal user to the second user) The second display based on (an example of the second information regarding the transmitted remittance request) is displayed on the display unit 24.
Then, the terminal 20 of the proposer's user is to process for remittance or receive the remittance amount based on the input to the terminal 20 on which the first display or the second display is displayed by the proposer's user. Processing, or processing for transmitting / receiving a remittance request (remittance reminding) (not limited to, but an example of the first processing relating to remittance, receiving remittance, or requesting remittance) is performed by the control unit 21. The configuration is shown.
As an example of the effect of the embodiment obtained by such a configuration, remittance to the other user and receipt of remittance from the other user based on the input to the terminal displaying the first display or the second display ( (Receipt), sending a remittance request to the other user, receiving a remittance request from the other user, etc. can be easily realized.

Further, in this embodiment, the first process shows a configuration in which the process based on the first information and the second information is performed by the control unit 21 based on the input to the first display and the second display.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to easily perform the processing based on the first information and the second information based on the input to the first display and the second display. can.

Further, in this embodiment, the first information is remittance information from the proposer user to the other user (not limited, but an example of information regarding remittance from the terminal user to the first user), and the second information. Is the received remittance request information regarding the received remittance request from the other user (not limited, but an example of the information regarding the remittance request sent from the second user to the terminal user), and the first process is the remittance. The configuration including the process of remittance to the other user based on the information and the received remittance request information is shown.
As an example of the effect of the embodiment obtained by such a configuration, information on remittance from the terminal user to the first user and from the second user to the terminal user based on the input to the first display and the second display. Remittance between the first user and the second user can be easily realized based on the information regarding the transmitted remittance request.

Further, in this case, the other user is one user (not limited, but an example that the second user is the first user), and the first process remits money from the proposer user to the other user. Remittance to the other user the sum of the amount and the remittance request amount included in the received remittance request information from the other user (not limited, but an example of the amount based on the first information and the second information). It can include processing.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to remit the amount of money based on the first information and the second information to one and the same user.

<9th modification>
In the above embodiment, as an example of the amount of money based on the first information and the second information, the amount of money to be remitted from the proposer user to the other user and the remittance request included in the received remittance request information from the other user. The case where the total amount of money is sent to the other user is illustrated, but the present invention is not limited to this.

It is assumed that the proposer's user borrows money from the other user. In such a case, as an example, not limited to the case, the proposer's user may transfer money to the other user with interest.
Specifically, as an example, not a limitation, on the terminal 20 side of the proposer user or on the server 10 side, the interest of a preset ratio to the sum of the above amounts (as an example, not a limitation). It is possible to perform a process of automatically adding interest (5%), and to use the amount to which interest is added as the remittance amount to remit from the proposer user to the other user.

Note that this method is also the same when the amount of money based on the first information and the second information is remitted from the other user.

<10th Example>
The tenth embodiment is an example relating to the processing of the pattern (B) described above.
The contents described in the tenth embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

In this embodiment, in addition to including the "sent remittance request" among the unprocessed requests in the batch settlement target, the batch settlement is performed by including the "remittance" in the batch settlement target.

The table of FIG. 9-6 will be described again with reference to the table.
In this embodiment, the pattern of (B) remittance + sent remittance request is processed.
In this pattern, either (B1) remittance + remittance reminder or (B2) [remittance + receipt] (amount can be deducted) can be processed.

In the process of (B1), when a new remittance is sent to the other user, a remittance remind to the other user is also performed based on the sent remittance request to the other user.
Instead of the remittance reminder, a new remittance request may or may not be made at the same time.

In the process of (B2), when a new remittance is made to the other user, the other user sends the money based on the sent remittance request to the other user and receives the money.
In this case, since there is a conflicting relationship between payment and receipt of money, it is possible to send / receive the amount of the difference between the remittance request amounts.
Also, if the remittance request amount is the same amount, it is possible to offset the amount.

Specifically, the amount of money sent from the proposer's user to the other user minus the amount of the remittance request included in the sent remittance request information is sent to the other user.
Or, conversely, the amount of the remittance request included in the sent remittance request information minus the amount of money to be remitted from the proposer's user to the other user is received from the other user.

<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 not limited, but as an example, User A. It is a remittance screen of the payment application displayed on the display unit 24 of the terminal 20A of A. The details of the screen configuration are not limited, but can be configured in the same manner as in FIG. 9-2 as an example, and thus the details thereof will be omitted.

As an example, not a limitation, in the unprocessed request confirmation area URR1, the check of the request of the second sent remittance request (receipt 1,000 yen) is selected as "ON", and the remittance batch settlement button BT11 is tapped. Then, the terminal 20A requests the server 10 to execute the remittance and the batch settlement of the selected unprocessed requests. Then, from the server 10, the user E. Settlement result information regarding the execution result is transmitted to the terminal 20E of E.

FIG. 10-2 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20E based on the tapping of the remittance batch settlement button BT11.
In this example, in the notification information display area NTR4 of the notification screen, two settlement result information is displayed as the contents of the remittance and the batch settlement.
Specifically, as an example, not a limitation, the user A. A is user E. Settlement result information corresponding to the receipt of the remittance amount "500 yen" sent to E, and the second remittance request selected in FIG. 10-1 (remittance request amount sent by user AA to user E.E. Reminders corresponding to the remittance request of "1,000 yen") are displayed.

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 not limited, but as an example, User A. It is a remittance screen of the payment application displayed on the display unit 24 of the terminal 20A of A. The details of the screen configuration are not limited, but can be configured in the same manner as in FIG. 9-2 as an example, and thus the details thereof will be omitted. In FIG. 10-3, the remittance amount to the user selected as the remittance destination is set to "1,500 yen" as an example, not a limitation.

As an example, not a limitation, in the unprocessed request confirmation area URR1, the check of the request of the second sent remittance request (receipt 1,000 yen) is selected as "ON", and the remittance batch settlement button BT11 is tapped. Then, the terminal 20A requests the server 10 to execute the remittance and the batch settlement of the selected unprocessed requests. Then, from the server 10, the user E. The batch settlement approval confirmation information for confirming the intention of whether or not to approve the batch settlement is transmitted to the terminal 20E of E, and is displayed on the display unit 24 of the terminal 20E.

FIG. 10-4 is a diagram showing an example of a notification screen displayed based on the tapping of the remittance batch settlement button BT11.
In the notification information display area NTR4, the user A. The icon image of A and the lump sum settlement amount are displayed.

In the batch settlement approval confirmation information, the content of the batch settlement includes the user E.I. E is the user A. From A to user E. By this remittance sent to E, "1,500 yen" is received, and the user A. It is displayed that the remittance request amount "1,000 yen" will be paid based on the receipt of the past remittance request from A.

The contents of the batch settlement can be stored by tapping the "close" icon of the batch settlement approval confirmation information, and can be expanded by tapping the "summary" icon from the stored state. It is possible.

Further, in the batch settlement approval confirmation information, the user E.I. E is user A. From A, it is displayed that "500 yen" is received by subtracting the remittance request amount "1000 yen" by the remittance request from the remittance received amount "1,500 yen".

At the bottom of the batch settlement approval confirmation information, there is a settlement button BT12 that says "Settle" to approve the settlement with the above contents, and "Refuse" to decline without approving the settlement with the above contents. The indicated reject button is displayed.

FIG. 10-5 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20A based on the tapping of the settlement button BT12.
Below the current position display area CLR1, the user E.I. As a notification that the batch settlement of the remittance request has been approved from the terminal 20E of E and the remittance has been performed as a result, the notification NT2 including the characters "500 yen has been remitted" is displayed together with the bell mark.

Further, the information corresponding to the above notification NT2 is displayed in the notification information display area NTR2 on the notification screen.
In this example, the user E.I. Since the batch settlement was performed with E, the content of the batch settlement is the settlement result information (in this example, the payment of the remittance amount "500 yen" that the user AA sent to the user E.E). Is displayed.

In FIG. 10-3, when the remittance batch settlement button BT11 is tapped, the display unit 24 of the terminal 20A displays the user A. A displays a confirmation screen to the effect that the lump sum settlement amount "500 yen" will be paid, and the user A. It may or may not be requested to execute the remittance and the bulk settlement of the selected unprocessed requests based on A's approval.

<Processing>
The process executed by each device in this embodiment can be similarly realized by following the process of FIG. 9-6.
However, when the process of (B2) [remittance + receipt] (amount can be deducted) is executed, the process of remittance by the other user is included. Therefore, as described above, the approval of the other user may be required for the batch settlement.

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

<Effect of the tenth embodiment>
In this embodiment, the first information described above is remittance information from the proposer user to the other user (not limited, but an example of information regarding remittance from the terminal user to the first user), and the second information. Shows a configuration which is the sent remittance request information (not limited, but an example of the information about the remittance request sent from the terminal user to the second user) regarding the remittance request sent from the proposer user to the other user. ing.
As an example of the effect of the embodiment obtained by such a configuration, the remittance from the terminal user to the first user and the remittance request sent from the terminal user to the second user can be processed together. ..

Further, 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, the remittance to the first user and the remittance request to the second user can be performed at the same time.

Further, in this embodiment, the other user is one user (not limited, but an example in which the second user is the first user), and the first process remits money from the proposer user to the other user. The process of remittance to the other user (not limited, but an example of the amount based on the first information and the second information) based on the amount to be remitted and the remittance request amount included in the sent remittance request information. However, the configuration including the process of remittance to the first user) or the process of receiving money from the first user (not limited to the process of remittance from the first user) is shown.
As an example of the effect of the embodiment obtained by such a configuration, the amount of money based on the first information and the second information is remitted to the same user, or the amount of money based on the first information and the second information. Can be sent and received.

Further, in this case, in the first process, the remittance request amount included in the sent remittance request information (in the limitation, not limited) from the amount of money transferred from the proposer user to the other user (not a limitation, but an example of the first amount). No, the process of remittance to the other user after deducting the second amount (an example of the second amount) (an example of the process of remittance to the first user, not limited), or the remittance request amount included in the sent remittance request information (first) 2 Amount) minus the amount to be remitted from the proposer's user to the other user (1st amount) is the process of receiving money from the other user (not limited, but the process of remittance from the 1st user) An example) is shown.
As an example of the effect of the embodiment obtained by such a configuration, the amount of the difference between the first amount and the second amount is remitted to the same user, or the first amount and the second amount are transferred. You can have the difference amount sent and received.

Further, this embodiment shows a configuration in which the first process is executed based on the input to the terminal of the other user and the approval by the other user.
As an example of the effect of the embodiment obtained by such a configuration, the first process can be executed based on the approval by the first user based on the input to the terminal of the first user. Thereby, as an example, not limited, it is possible to prevent the first process from being executed without the intention of the first user.

<Eleventh Example>
The eleventh embodiment is an example relating to the processing of the pattern (C) described above.
The contents described in the eleventh embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

In this embodiment, in addition to including the "received remittance request" among the unprocessed requests in the batch settlement target, the batch settlement is performed by including the "sending remittance request" in the batch settlement target.

The table of FIG. 9-6 will be described again with reference to the table.
In this embodiment, the pattern of (C) transmission of remittance request + received remittance request is processed.
In this pattern, either (C1) remittance request + remittance or (C2) [receipt + remittance] (amount can be deducted) can be processed.

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

In the process of (C2), when a new remittance request is made to the other user, the remittance is received from the other user based on the new remittance request, and the received remittance from the other user is received. Remittance to the other user is also performed based on the request.
In this case, it is possible to receive / remit the amount of the difference between the remittance request amounts.
Also, if the remittance request amount is the same amount, it is possible to offset the amount.

<Display screen>
First, an example of a display screen when the above process (C1) is performed will be described.
FIG. 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 not limited, but as an example, User A. It is a remittance request screen of the payment application displayed on the display unit 24 of the terminal 20A of A.
In the current position display area CLR1 indicating the current position in the payment application, the characters "remittance request" indicating that the current position is the remittance request function of the payment application are displayed.

Below the current position display area CLR1, an icon image and a user name (user EE in this example) in the payment application of the user selected as the destination of the remittance request are displayed. Below that, the remittance request amount ("500 yen" in this example) for the user selected as the destination of the remittance request and the function button for increasing the remittance request amount by a certain amount are displayed. There is. When the user selected as the destination of the remittance request accepts the remittance request, the e-commerce account of the user who made (sent) the remittance request from the e-commerce account of the user selected as the destination of the remittance request is Remittance The amount of money requested will be remitted.

Further below, the unprocessed request confirmation area URR1 is displayed. The unprocessed request confirmation area URR1 is not limited and can be configured in the same manner as in FIG. 9-2 as an example, and thus the description thereof will be omitted.

Under the unprocessed request confirmation area URR1, a remittance request transmission all-select batch settlement button indicating "all settlement and remittance request" is displayed to execute the remittance request transmission processing and all-select batch settlement. Has been done. Below that, "one settlement and remittance request" is shown to execute the transmission process of the remittance request and the partial selection batch settlement of the unprocessed request selected in the unprocessed request confirmation area URR1. The remittance request transmission batch settlement button BT13 is displayed. Further below, a remittance request transmission button indicating "only remittance request" is displayed to execute only the remittance request transmission process.

As an example, not a limitation, in the unprocessed request confirmation area URR1, the check of the request of the first received remittance request (payment 2,500 yen) is selected as "ON", and the remittance request transmission batch settlement button BT13. When is tapped, the terminal 20A requests the server 10 to send a new remittance request and execute the batch settlement of the selected unprocessed requests. Then, from the server 10, the user E. The remittance request information and the settlement result information regarding the execution result of the batch settlement are transmitted to the terminal 20E of E.

FIG. 11-2 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20E based on the tapping of the remittance request transmission batch settlement button BT13.
In this example, in the notification information display area NTR4 of the notification screen, the settlement result information regarding one remittance request selected in FIG. 11-1 and the new remittance request information are displayed.

The settlement result information includes the user E. E is the user A. Information regarding the receipt of the remittance request amount "2,500 yen" by the remittance request to A is displayed.

The remittance request information is not limited, but as an example, the user A. A is user E. A remittance request with a remittance request amount of "500 yen" sent to E, a remittance request remittance button indicating "send" to accept this remittance request and send money based on the remittance request, and this remittance request There is a remittance request refusal button that says "decline" to decline without approval.

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 not limited, but as an example, User A. It is a remittance request screen of the payment application displayed on the display unit 24 of the terminal 20A of A. The details of the screen configuration are not limited, but can be configured in the same manner as in FIG. 11-1 as an example, and thus the details thereof will be omitted. In FIG. 11-3, 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" as an example, not limited.

As an example, not a limitation, in the unprocessed request confirmation area URR1, the check of the request of the first received remittance request (payment 2,500 yen) is selected as "ON", and the remittance request transmission batch settlement button BT13. When is tapped, the terminal 20A requests the server 10 to send a new remittance request and execute the batch settlement of the selected unprocessed requests. Then, from the server 10, the user E. The batch settlement approval confirmation information for confirming the intention of whether or not to approve the batch settlement is transmitted to the terminal 20E of E, and is displayed on the display unit 24 of the terminal 20E.

FIG. 11-4 is a diagram showing an example of a notification screen displayed based on the tapping of the remittance request transmission batch settlement button BT13.
In the notification information display area NTR4, the user A. who is the other party of the "request settlement and remittance request" as the batch settlement approval confirmation information. The icon image of A and the lump sum settlement amount are displayed.

In this example, the batch settlement approval confirmation information includes the user E.I. E is the user A. Based on the remittance request sent to A, the remittance request amount "2,500 yen" is received, and the user A. It is displayed that the remittance request amount "1,000 yen" will be paid based on the receipt of this remittance request from A.

Further, in the batch settlement approval confirmation information, the user E.I. E is user A. From A, it is displayed that "1,500 yen" is received by subtracting the remittance request amount "1,000 yen" for payment from the remittance request amount "2,500 yen" received.

At the bottom of the batch settlement approval confirmation information, there is a settlement button BT14 that says "Settle" to approve the settlement with the above contents, and "Refuse" to decline without approving the settlement with the above contents. The indicated reject button is displayed.

FIG. 11-5 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20A based on the tapping of the settlement button BT14.
Below the current position display area CLR1, the user E.I. As a notification that the batch settlement of the remittance request was approved from the terminal 20E of E and the remittance was made as a result, the notification NT3 containing the characters "1,500 yen has been remitted" is displayed together with the bell mark. There is.

Further, the information corresponding to the above notification NT3 is displayed in the notification information display area NTR2 on the notification screen.
As a specific example, the user E.I. The settlement result information is displayed because the batch settlement has been performed with E. In the settlement result information, in this example, the user A. From A to user E. It is displayed that the remittance of "1,500 yen" has been made to E.

In addition, for the settlement result information, as the content of the batch settlement, "2,500 yen" will be paid based on the receipt of the past remittance request, and "1,000 yen" will be received based on the transmission of this remittance request. Is displayed.

In FIG. 11-3, when the remittance request transmission batch settlement button BT13 is tapped, when the settlement is performed on the display unit 24 of the terminal 20A, the user A. A displays a confirmation screen to the effect that "1,000 yen" will be received, and the user A. Based on A's approval, the remittance request may or may not be requested to be executed with the batch settlement of the selected unprocessed requests.

<Processing>
FIG. 11-6 is a flowchart showing an example of the flow of processing executed by each device in this embodiment.
This flowchart is a flowchart in which the flowchart of FIG. 1-18 is rewritten into a process in which the new processing target is "send a remittance request".

Strictly speaking, making a remittance request (sending a remittance request) can be considered to have a different meaning and concept from settlement (including batch settlement). However, for the sake of simplicity, the process (flow chart) will be illustrated and explained here assuming that making a remittance request (sending a remittance request) is also a type of settlement.
In addition, unlike this, it is also possible to configure a flowchart by making a remittance request (sending a remittance request) as a process different from the settlement.

Further, the processing of the pattern (C) in this embodiment is not limited, but as an example, the approval of the other user is not required when the processing of (C1) is performed, and the approval of the other party is not required when the processing of (C2) is performed. Can require user approval.
Here, for the sake of simplicity, a process (flow chart) when approval of the other user is not required is illustrated.

First, the control unit 21 of the terminal 20A determines whether or not to transmit the remittance request based on whether or not the input for executing the remittance request transmission is made to the input unit (A107). ..

If it is determined that the remittance request is to be transmitted (A107: YES), the control unit 21 of the terminal 20A executes the process of A110. After that, based on the fact that the remittance request list information is received from the server 10 by the communication I / F 22, the control unit 21 of the terminal 20A has a remittance request transmission screen (screen for remittance request transmission) including the received remittance request list information. Is displayed on the display unit 24 (A127).

After that, the control unit 21 of the terminal 20A determines whether or not an unprocessed request is selected from the remittance request list information (A135).

If an unprocessed request is selected, that is, if it is determined that the remittance request is transmitted + the unprocessed request is processed (A135: YES), the control unit 21 of the terminal 20A transmits the remittance request to be executed. The request selection information including the remittance request transmission information regarding the remittance request and the unprocessed request selection information indicating the selected unprocessed request is set (A136).

On the other hand, when an unprocessed request is not selected from the remittance request list information, that is, when it is determined that only the remittance request is transmitted (A135: NO), the control unit 21 of the terminal 20A determines the remittance request transmission information. Request selection information including (A137) is set.

In this process, it is assumed that the remittance request is transmitted.
In reality, it may be selected to process only the unprocessed request without sending the remittance request, but the processing in this case is the same as the processing of the batch settlement of the unprocessed request described above. Therefore, the illustration and the description will be omitted again.

After A136 or A137, the control unit 21 of the terminal 20A transmits the set request selection information to the server 10 by the communication I / F22 (A140).
Then, the control unit 21 of the terminal 20A shifts the processing to the A150.

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 sends a remittance request + an unprocessed request based on the information included in the received request selection information. , Is determined (S144). Then, if it is determined to be processed (S145: YES), the control unit 11 of the server 10 sets the remittance request transmission + the settlement of the selected unprocessed request (in the case of multiple selections, the batch settlement) as the batch settlement target. Set (S146).

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

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

When applying the first settlement process described in FIG. 1-19 as an example rather than a limitation,
When the setting of S146 is made, the determination result of whether or not the settlement target in S1510 is the batch settlement target is "YES". As a result, the processing after S1515 is executed with the remittance request transmission + the settlement of the selected unprocessed request as the batch settlement target.
On the other hand, when S147 is set, the determination result of whether or not the settlement target in S1510 is a batch settlement target is "NO". As a result, the processing after S1570 is executed with the remittance request transmission as the settlement target.

<Effect of 11th Example>
In this embodiment, the first information is the remittance request transmission information for transmitting the remittance request from the proposer user to the other user (not limited to the information regarding the remittance request transmitted from the terminal user to the first user). The second information is the received remittance request information regarding the remittance request received from the other user (not limited to the example of the information regarding the remittance request sent from the second user to the terminal user). The configuration is shown.
As an example of the effect of the embodiment obtained by such a configuration, the remittance request transmitted from the terminal user to the first user and the remittance request transmitted from the second user to the terminal user are processed together. Can be done.

Further, in this case, the first process includes a process of transmitting remittance request information to the other user based on the remittance request transmission information and remittance to the other user based on the received remittance request information. Can be done.
As an example of the effect of the embodiment obtained by such a configuration, the remittance request to the first user and the remittance to the second user can be performed at the same time.

Further, in this embodiment, the other user is one user (not limited, but an example in which the second user is the first user), and the first process is the remittance request information to be transmitted to the other user. Shows a configuration including a process of sending money to the other user or receiving money from the other user based on the included remittance request amount and the remittance request amount included in the received remittance request information from the other user. ing.
As an example of the effect of the embodiment obtained by such a configuration, the amount of money based on the first information and the second information can be remitted to the first user or received from the first user.

In this case, the first process is from the remittance request amount (second amount) included in the received remittance request information from the other user to the remittance request amount included in the remittance request information transmitted to the other user (second amount). The amount of money after deducting the first amount) is sent to the other user, or the remittance request amount (first amount) included in the remittance request information sent to the other user is used to receive the remittance request from the other user. The amount obtained by subtracting the remittance request amount (second amount) included in the information can be included in the process of receiving the remittance from the other user.
As an example of the effect of the embodiment obtained by such a configuration, the amount of the difference between the first amount and the second amount is remitted to the same user, or the first amount and the second amount are transferred. You can have the difference amount sent and received.

Further, this embodiment shows a configuration in which the first process is executed based on the input to the terminal of the other user and the approval by the other user.
As an example of the effect of the embodiment obtained by such a configuration, the first process can be executed based on the approval by the first user based on the input to the terminal of the first user. Thereby, as an example, not limited, it is possible to prevent the first process from being executed without the intention of the first user.

<12th Example>
The twelfth embodiment is an example relating to the processing of the pattern (D) described above.
The contents described in the twelfth embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

In this embodiment, in addition to including the "sent remittance request" among the unprocessed requests in the batch settlement target, the batch settlement is performed by including the "sending remittance request" in the batch settlement target.

The table of FIG. 9-6 will be described again with reference to the table.
In this embodiment, the pattern of (D) transmission of remittance request + transmitted remittance request is performed.
In this pattern, either (D1) remittance request + [remittance request or remittance reminder] or (D2) integrated remittance request can be processed.

In the process of (D1), when making a new remittance request to the other user, the remittance request to the other user or the remittance remind to the other user is based on the sent remittance request to the other user. At the same time.

In this case, the remittance request based on the sent remittance request is regarded as the same remittance request as the sent remittance request, and two different remittance requests, a new remittance request and a sent remittance request, are sent to the other user. Alternatively, the remittance request based on the sent remittance request may be used as the remittance reminder, and the new remittance request and the remittance reminder may be sent to the other user.

In the process of (D2), when making a new remittance request to the other user, this new remittance request and the remittance request based on the sent remittance request to the other user are combined (integrated). To send an integrated remittance request to the other user.

<Display screen>
An example of a display screen when each of the above (D1) and (D2) processes is performed 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 not limited, but as an example, User A. It is a remittance request screen of the payment application displayed on the display unit 24 of the terminal 20A of A. The details of the screen configuration are not limited, but can be configured in the same manner as in FIG. 11-3 as an example, and thus the details thereof will be omitted.

As an example, not a limitation, in the unprocessed request confirmation area URR1, the check of the request of the second sent remittance request (receipt 1,000 yen) is selected as "ON", and the remittance request transmission batch settlement button BT13. When is tapped, the terminal 20A requests the server 10 to send a new remittance request and execute the batch settlement of the selected unprocessed requests. Then, from the server 10, the user E. New remittance request information and remittance reminder information based on past remittance request transmissions are transmitted to the terminal 20E of E and displayed on the display unit 24 of the terminal 20E.

FIG. 12-2 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20E based on the tapping of the remittance request transmission batch settlement button BT13.
In this example, in the notification information display area NTR4 of the notification screen, remittance information regarding one remittance request selected in FIG. 12-1 (in this example, the remittance request amount from the user AA to the user EE). Remittance request for "1,000 yen" remittance request) and new remittance request information (in this example, remittance request amount "1,500 yen" from user AA to user EE) It is displayed.

It is also possible to integrate a new remittance request and a past remittance request in the batch settlement process.
FIG. 12-3 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20E in this case.
In the notification information display area NTR4, as the batch settlement approval confirmation information, the user A. The icon image of A and the lump sum settlement amount are displayed. In this example, as the lump sum settlement amount, the user E.I. E is the user A. It is displayed that "2,500 yen", which is the sum of the remittance request amount "1,000 yen" and the remittance request amount "1,500 yen", is paid to A.

Further, in the batch settlement approval confirmation information, the content of the batch settlement includes the user E.I. E is the user A. A is user E. It is displayed that the remittance request amount "1,000 yen" is paid based on the past remittance request sent to E, and the remittance request amount "1,500 yen" is paid based on the current remittance request.

At the bottom of the batch settlement approval confirmation information, there is a settlement button BT15 that says "Settle" to approve the settlement with the above contents, and "Refuse" to decline without approving the settlement with the above contents. The indicated reject button is displayed.

FIG. 12-4 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20A based on the tapping of the settlement button BT15.
Below the current position display area CLR1, the user E.I. The batch settlement of the remittance request is approved from the terminal 20E of E, and as a result, the user E. As a notification of receiving the remittance from E, the notification NT4 including the characters "There was a remittance" is displayed together with the bell mark.

Further, the information corresponding to the above notification NT4 is displayed in the notification information display area NTR2 on the notification screen.
As a specific example, the user E.I. The settlement result information is displayed because the batch settlement has been performed with E. In this example, the settlement result information includes the user A. A is user E. It is displayed that the remittance of the lump sum settlement amount "2,500 yen" which is the sum of the remittance request amount "1,000 yen" and the remittance request amount "1,500" to E has been received.

In addition, the settlement result information includes the contents of the batch settlement as the user A. A is user E. It is displayed that the remittance request amount "1,000 yen" has been received based on the transmission of the past remittance request to E, and the remittance request amount "1,500 yen" has been received based on the transmission of this remittance request. There is.

<Processing>
Since the processing executed by each device in this embodiment can be similarly realized by following the processing of FIGS. 11-6, illustration and detailed description thereof will be omitted.

<Effect of the 12th Example>
In this embodiment, the first information is the remittance request transmission information for transmitting the remittance request from the proposer user to the other user (not limited to the information regarding the remittance request transmitted from the terminal user to the first user). The second information is the sent remittance request information regarding the remittance request sent from the proposer user to the other user (not limited to the remittance request sent from the terminal user to the second terminal user). An example of information about) is shown.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to process both the remittance request from the terminal user to the first user and the remittance request from the terminal user to the second terminal user. can.

Further, in the above, the other user is one user (not limited, but an example that the second user is the first user), and the first process remittances to the other user based on the remittance request transmission information. The process of sending a request (an example of a first remittance request, not a limitation) and sending a remittance request or a remittance reminder (an example of a second remittance request, not a limitation) to the other user based on the sent remittance request information. Can be included.
As an example of the effect of the embodiment obtained by such a configuration, the first remittance request to the first user and the second remittance request to the first user can be performed at the same time.

Further, in the above, the other user is one user (not limited, but an example that the second user is the first user), and the first process is the remittance request amount of the remittance request to be sent to the other user. , A configuration that includes a process of sending an integrated remittance request (not limited to an example of a third remittance request) to the first user with the total amount of the remittance request amount included in the sent remittance request information as the remittance request amount. Shows.
As an example of the effect of the embodiment obtained by such a configuration, a terminal is provided by transmitting a set third remittance request to the first user based on the third amount, which is the sum of the first amount and the second amount. The first user can be effectively encouraged to send money to the user.

<13th Example>
The thirteenth embodiment is an example relating to the processing of the pattern (E) described above.
The contents described in the thirteenth embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

In this embodiment, in addition to including the "received remittance request" and the "sent remittance request" among the unprocessed requests in the batch settlement target, the "sending remittance request" is included in the batch settlement target. I do.

The table of FIG. 9-6 will be described again with reference to the table.
In this pattern, (E1) remittance request + [remittance + remittance] (amount deduction possible), (E2) [remittance + remittance] (amount deduction possible) + [remittance request or remittance remind], (E3) [receipt Either [Remittance + Remittance] (Amount can be deducted) + [Remittance + Remittance] (Amount can be deducted) can be processed.

In the process of (E1), when making a new remittance request to the other user, the remittance and the receipt are made based on the received remittance request from the other user and the sent remittance request to the other user. Do it at the same time. In this case, the amount of the difference between the remittance request amounts can be sent / received. Also, if the remittance request amount is the same amount, it is possible to offset the amount.

In the process of (E2), when a new remittance request is made to the other user, the remittance is received from the other user based on the new remittance request, and the received remittance from the other user is received. Remittance to the other user is also performed based on the request. In this case, it is possible to receive / remit the amount of the difference between the remittance request amounts. Also, if the remittance request amount is the same amount, it is possible to offset the amount.
Also, based on the sent remittance request to the other user, the same remittance request is made to the other user, or the remittance remind is made to the other user.

In the process of (E3), when a new remittance request is made to the other user, the remittance is received from the other user based on the new remittance request, and the received remittance from the other user is received. Remittance to the other user is also performed based on the request. In this case, it is possible to receive / remit the amount of the difference between the remittance request amounts. Also, if the remittance request amount is the same amount, it is possible to offset the amount.
In addition, remittance is sent to the other user based on the received remittance request from the other user, and remittance is received from the other user based on the sent remittance request to the other user. In this case, the amount of the difference between the remittance request amounts can be sent / received. Also, if the remittance request amount is the same amount, it is possible to offset the amount.

<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 not limited, but as an example, User A. It is a remittance request screen of the payment application displayed on the display unit 24 of the terminal 20A of A. The details of the screen configuration are not limited, but can be configured in the same manner as in FIG. 11-1 as an example, and thus the details thereof will be omitted. In FIG. 13-1, 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" as an example, not limited.

As an example, not a limitation, both the first received remittance request (payment 2,500 yen) and the second sent remittance request (receipt 1,000 yen) in the unprocessed request confirmation area URR1. Check is set to "ON" and selected, and when the remittance request transmission batch settlement button BT13 is tapped, a new remittance request transmission and batch settlement of the selected unprocessed request are sent from the terminal 20A to the server 10. Is requested to execute. Then, from the server 10, the user E. The batch settlement approval confirmation information for confirming the intention of whether or not to approve the batch settlement is transmitted to the terminal 20E of E, and is displayed on the display unit 24 of the terminal 20E.

FIG. 13-2 is a diagram showing an example of a notification screen displayed based on the tapping of the remittance request transmission batch settlement button BT13.
In the notification information display area NTR4, the user A. who is the other party of the "request settlement and remittance request" as the batch settlement approval confirmation information. The icon image of A and the lump sum settlement amount are displayed.

In this example, the batch settlement approval confirmation information includes the user E.I. E is the user A. Upon receiving the remittance request amount "2,500 yen" based on the transmission of the past remittance request to A, the user A. Based on the receipt of the past remittance request from A, the remittance request amount "1,000 yen" is paid, and the user A. It is displayed that the remittance request amount "1,200 yen" will be paid based on the receipt of this remittance request from A.

Further, in the batch settlement approval confirmation information, the user E.I. E is the user A. From the remittance request amount "2,500 yen" received from A, user A. It is displayed that you will receive "300 yen", which is obtained by subtracting the remittance request amount "1,000 yen" to be paid to A and the remittance request amount "1,200 yen".

At the bottom of the batch settlement approval confirmation information, there is a settlement button BT16 that says "Settle" to approve the settlement with the above contents, and "Refuse" to decline without approving the settlement with the above contents. The indicated reject button is displayed.

FIG. 13-3 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20A based on the tapping of the settlement button BT16.
Below the current position display area CLR1, the user E.I. As a notification that the batch settlement of the remittance request has been approved from the terminal 20E of E and the remittance has been performed as a result, the notification NT5 including the characters "300 yen has been remitted" is displayed together with the bell mark.

Further, the information corresponding to the above notification NT5 is displayed in the notification information display area NTR2 on the notification screen.
As a specific example, the user E.I. The settlement result information is displayed because the batch settlement has been performed with E. In the settlement result information, in this example, the user A. A is user E. It is displayed that "300 yen" has been paid to E.

In addition, the settlement result information includes the contents of the batch settlement as the user A. A is user E. Based on the receipt of the past remittance request from E, the remittance request amount "2,500 yen" is paid, and the user E. Upon receiving the remittance request amount "1,000 yen" based on the transmission of the past remittance request to E, the user E. It is displayed that the remittance request amount "1,200 yen" has been received based on the transmission of this remittance request to E.

<Processing>
The processes related to the above (E1) to (E3) can be similarly configured based on the processes described in the previous examples, and are self-evident, so illustration and detailed description thereof will be omitted.

<14th Example>
The fourteenth embodiment is an example relating to the processing of a pattern different from the above-mentioned pattern.
The contents described in the 14th embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

In addition to the above-mentioned patterns, as an example, not a limitation, a pattern of combinations of new processing targets in the table of FIG. 9-6, that is,
-It is also possible to process the remittance + remittance request transmission pattern.

The processing of this pattern is the same as the processing of the pattern (C).
That is, either "remittance + remittance request transmission" or "remittance + receipt (amount deduction is possible)" can be performed.
In addition, when performing the process of "remittance + receipt (amount deduction is possible)", the approval of the other user may be required and the approval of the other user may or may not be obtained.

<Effect of 14th Example>
In this embodiment, the first information is the remittance request information from the proposer user to the other user, and the terminal 20 of the proposer user is the remittance request information transmitted from the proposer user to the other user ( The display unit 24 displays a third display based on (an example of the third information), not a limitation. Then, the terminal 20 of the proposer's user displays a remittance display (not a limitation but an example of the first display) by the proposer's user from the proposer's user to the other user, and the above-mentioned third display. A configuration is shown in which the control unit 21 performs a second process relating to a remittance, a receipt, or a remittance request based on an input to the terminal 20.
As an example of the effect of the embodiment obtained by such a configuration, remittance, remittance receipt, or remittance request can be performed together.

Further, in the above, the second process remits money to the other user based on the remittance information (not limited, but an example of the first information), and is based on the remittance request information transmitted from the proposer user to the other user. The configuration including the process of sending a remittance request to the other user is shown.
As an example of the effect of the embodiment obtained by such a configuration, remittance to the first user based on the first information and remittance request to the first user based on the third information can be performed at the same time. ..

Further, in the above, the second process is an amount based on the amount of money sent by the proposer user to the other user and the amount of the remittance request requested by the proposer user to the other user (not limited to the first information). An example of the amount of money based on the third information and the third information) is shown to include a process of sending money to the other user or receiving money from the other user.
As an example of the 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.

Further, in this case, the second process remits to the other user the amount obtained by subtracting the remittance request amount requested by the proposer user from the other user from the amount of money sent by the proposer user to the other user. Alternatively, it shows a configuration including a process of receiving a remittance request amount from the other user, which is obtained by subtracting the amount of money sent by the proposer user to the other user from the remittance request amount requested by the proposer user to the other user.
As an example of the effect of the embodiment obtained by such a configuration, the amount of the difference between the first amount and the third amount can be paid to the first user or received from the first user.

Further, in this case, the second process may be executed based on the approval by the other user based on the input to the terminal 20 of the other user (not limited, but an example of the first user).
As an example of the effect of the embodiment obtained by such a configuration, the second process can be executed based on the approval by the first user based on the input to the terminal of the first user. This makes it possible to prevent the second process from being executed unintentionally according to the intention of the first user, as an example, not a limitation.

<15th Example>
The fifteenth embodiment is the same as the fourteenth embodiment, and is an example relating to the processing of a pattern different from the above-mentioned pattern.
The contents described in the fifteenth embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

In addition to the above-mentioned pattern, as an example, not a limitation, the pattern of the combination of unprocessed requests shown in the horizontal direction of the table in FIG. 9-6, that is,
-It is also possible to process the pattern of received remittance request + sent request.

The processing of this pattern is the same as the processing of the pattern (B).
That is, it is possible to perform either "remittance + receipt (amount deduction is possible)" or "remittance + remittance request transmission".
In addition, when performing the process of "remittance + receipt (amount deduction is possible)", the approval of the other user may be required and the approval of the other user may or may not be obtained.

<Effect of the 15th example>
In this embodiment, the second information is the remittance request information from the other user to the proposer user, and the terminal 20 of the proposer user is the transmitted remittance transmitted from the proposer user to the other user. The fourth display based on the request information (not limited, but an example of the fourth information) is displayed on the display unit 24. Then, the terminal 20 of the proposer user has a second display based on the received remittance request information (not limited, but an example of the second information) regarding the received remittance request received by the proposer user from the other user. , The configuration is shown in which the control unit 21 performs a third process related to remittance, remittance, or remittance request based on the input to the terminal 20 in which the above-mentioned fourth display is displayed.
As an example of the effect of the embodiment obtained by such a configuration, remittance, remittance receipt, or remittance request can be performed together.

Further, the above-mentioned third process shows a configuration including a process of sending money to the other user based on the received remittance request information and sending a remittance request 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, remittance to the second user based on the second information and remittance request to the second user based on the fourth information can be performed at the same time. ..

Further, the above-mentioned third process shows a configuration including a process of transferring an amount based on the received remittance request information and the transmitted remittance request information to the other user or receiving the money from the other user.
As an example of the 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.

In addition, in the above third process, the amount obtained by subtracting the remittance request amount of the sent remittance request information from the remittance request amount of the received remittance request information is remitted to the other user, or the remittance request amount of the sent remittance request information. It shows a configuration including a process of receiving a remittance from the other user by subtracting the remittance request amount of the received remittance request information from.
As the amount of money of the embodiment obtained by such a configuration, the amount of the difference between the second amount and the fourth amount can be paid to the second user or received from the second user.

Further, in this case, the third process may be executed based on the approval by the other user based on the input to the terminal 20 of the other user (not limited, but an example of the second user).
As an example of the effect of the embodiment obtained by such a configuration, the third process can be executed based on the approval by the second user based on the input to the terminal of the second user. As a result, it is possible to prevent the third process from being executed without the intention of the second user, as an example but not a limitation.

<16th Example>
The sixteenth embodiment is an embodiment relating to a method for displaying remittance request information.
The contents described in the 16th embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

<Display screen>
FIG. 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 not limited, but as an example, User A. It is a remittance screen of the payment application displayed on the display unit 24 of the terminal 20A of A.
Below the current position display area CLR1, an icon image and a user name (user CC in this example) in the payment application of the user selected as the remittance destination are displayed.

Under the function button for increasing the remittance amount by a certain amount, the user selected as the remittance destination (user CC in this example) and the user who performs the remittance (user AA in this example) are not yet displayed. The unprocessed request confirmation area URR3 configured to enable confirmation of the processing request is displayed.

At the top of the unprocessed request confirmation area URR3, the user C.I. The characters "Unsettled request with CC" indicating that the unprocessed request with C is displayed are displayed.
On the right side, a remittance request history sort button STB1 for changing the display order of unprocessed remittance requests is displayed. Other display modes are the same as the unprocessed request confirmation area URR1.

When the remittance request history sort button STB1 is touched, the sort selection area for selecting the sort order is displayed from the bottom of the screen as an example, not limited to the above.
Based on the user operation for the sort selection area, the display order of unprocessed remittance requests is not limited, but as an example, in ascending / descending order according to the date order in which the remittance request was sent / received, the remittance request amount of the remittance request, etc. It can be rearranged and displayed.

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

FIG. 14-2 shows, as an example, not a limitation, an example of a display screen in which the remittance requests in the unprocessed request confirmation area URR3 are sorted in descending order by the remittance request amount based on the user operation for the sort selection area. It is a figure.

In FIG. 14-1, the remittance requests in the unprocessed request confirmation area URR3 are arranged in ascending order regarding the date, but in FIG. 14-2, they are arranged in descending order regarding the remittance request amount.

When the payment deadline is set for the remittance request, the remittance request may or may not be displayed in the order in which the payment deadline is approaching, as an example, not limited. Setting the payment deadline is not limited to payment between general users (CtoC), but also includes setting the repayment deadline for loans and loans (CtoB) from businesses such as financial institutions. ..

Further, the remittance request in which the user who requested the remittance and the user other than the user who requested the remittance are related to the remittance request amount or the reason may be preferentially displayed. As an example, not a limitation, when another user is included as a member of the Dutch bill.

Further, the unprocessed remittance request is displayed in the unprocessed request confirmation area URR3, but the present invention is not limited to this.

FIG. 14-3 is an example of a display screen when processed remittance requests are mixed in the unprocessed request confirmation area URR3.
In FIG. 14-3, as an example, not limited to the fact that the first remittance request in the unprocessed request confirmation area URR3 has received the remittance request for payment of the remittance request amount “1,000 yen” has been processed. It is displayed in a grayed out display mode indicating that it is a remittance request. There is no check area because the processed remittance request is not selected for batch settlement.

<Effect of 16th Example>
In this embodiment, the terminal 20 of the proposer user has remittance request information (not limited to, but not limited to, transmitted from the second user to the terminal user) regarding the received remittance request received by the proposer user from the other user. (An example of the fourth information regarding the remittance request), or the remittance request information regarding the sent remittance request sent by the proposer user to the other user (not limited, but regarding the remittance request sent from the terminal user to the second user). The fourth display based on (an example of the fourth information) is displayed on the display unit 24. The terminal 20 of the proposer's user shows a configuration in which the second display and the fourth display are displayed on the display unit 24 in the order based on the above-mentioned second information and the above-mentioned fourth information.
As an example of the effect of the embodiment obtained by such a configuration, the second display and the fourth display can be displayed in an appropriate order based on the second information and the fourth information.

Further, in this embodiment, the above-mentioned second information and fourth information are information on the date when the remittance request is transmitted / received (not limited to an example of information on the date), or the date and time when the remittance request is transmitted / received. The order in which the second and fourth displays are displayed, including information about (but not limited to, an example of information about a date and time), indicates a configuration that is determined based on this date or information about the date and time.
As an example of the effect of the embodiment obtained by such a configuration, by displaying the second display and the fourth display in the order based on the date and time or the information on the date, it is possible to realize a display that is intuitively easy for the user to understand. Can be done.

Further, in this embodiment, the above-mentioned second information and fourth information include information on the amount of money to be remitted (an example of information on the amount of money, not a limitation), and the order in which the second display and the fourth display are displayed. Shows a configuration that is determined based on information about this amount.
As an example of the effect of the embodiment obtained by such a configuration, by displaying the second display and the fourth display in the order based on the information on the amount of money, it is possible to realize a display that is intuitively easy for the user to understand. ..

Further, in this case, the information regarding the amount of the remittance request may include information regarding the payment deadline as an example, not limited to, in addition to the remittance request amount.
As an example of the effect of the embodiment obtained by such a configuration, by displaying the second display and the fourth display in the order based on the information regarding the payment deadline, it is possible to realize a display that is intuitively easy for the user to understand. can.

Next, as a contradictory idea to the ninth to sixteenth embodiments, the user of the terminal 20 receives (receives) the amount of money sent from the other user, or makes a remittance request from the other user. An embodiment relating to processing in the case of receiving will be described.

<17th Example>
A seventeenth embodiment is an embodiment in which a user of the terminal 20 displays an unprocessed request when receiving a remittance amount from the other user or receiving a remittance request from the other user.
The contents described in the 17th embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

FIG. 15-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 not limited, but as an example, User A. This is a payment application notification screen displayed on the display unit 24 of the terminal 20A of A.
In the current position display area CLR1 indicating the current position in the payment application, the character "notice" indicating that the current position is the notification function of the payment application is displayed.

In the notification information display area NTR2 on the notification screen, the remittance result information NC1 is displayed as the content related to the receipt (receipt) of the remittance.
It should be noted that the server 10 is the result of the remittance process, so it is the remittance result information, and the other user (user BB in this example) is also the remittance result information. For A), it can be said that it is the remittance result information because it is the result of the remittance.

The remittance result information NC1 is not limited to the user A. A is user B. The contents corresponding to the receipt of the remittance amount "500 yen" sent (received) from B are displayed.

Below that, a list of unprocessed remittance requests for the user who received the remittance at the time the remittance was received (user AA in this example) is displayed. In this example, four unprocessed requests are listed in chronological order in chronological order. Since the display mode of each unprocessed request can be configured in the same manner as in FIG. 1-23 as an example without limitation, the description thereof will be omitted again.

As the unprocessed request, only the unprocessed request between the remittance user (user A.A. in this example) and the remittance user (user BB in this example) may be displayed. And you don't have to do that.

As described above, in this embodiment, the unprocessed request is combined with the information of the remittance result (receipt result) when confirming that the user has received the remittance amount by displaying the unprocessed request. It is configured so that it can be confirmed.

FIG. 15-2 is a diagram showing another example of the screen displayed on the display unit 24 of the terminal 20 in this embodiment. This screen corresponds to FIG. 15-1, but its display contents are partially different.
Specifically, as an example, not limited, a remittance receiving button indicated as "Remittance receipt" is displayed in the remittance result information NC1 for accepting and receiving the remittance.
User A. The remittance process is not completed until the remittance receiving button is tapped by A, and when the remittance receiving button is tapped, the remittance is sent to the electronic money account balance of the transferred user (user A.A in this example). The amount ("500 yen" in this example) is added.

In this example, when the other user (first user or second user) sends money to the proposer's user (terminal user), the proposer's user receives (receives) the amount to be sent. It is configured so that it can be stopped.
Details will be described later, but this is referred to as "holding receipt of remittance" or "holding receipt".
Since the remittance is incomplete, this can be regarded as a "holding of remittance".

As described above, in this embodiment, it is determined whether or not the user receives the remittance amount by displaying the unprocessed request together with the information of the remittance result (receipt result) in which the receipt of the remittance is suspended. In some cases, it is configured so that unprocessed requests can also be confirmed.

FIG. 15-3 is a diagram showing another example of the screen displayed on the display unit 24 of the terminal 20 in this embodiment. This screen is not limited, but as an example, User A. This is a payment application notification screen displayed on the display unit 24 of the terminal 20A of A.

The remittance request information NC7 is displayed in the remittance information display area NTR2 on the remittance screen as the content related to the reception of the remittance request.
The remittance request information NC7 is not limited to the user A. A is user B. The contents corresponding to the remittance request of the remittance request amount "500 yen" received from B are displayed. In addition, the remittance request information NC7 indicates a remittance request remittance button indicating "send money" to accept the remittance request and perform remittance, and "decline" to reject this remittance request. The remittance request rejection button that was sent is displayed.

Below that, a list of remittance requests that have not been processed by the user (user AA in this example) who received the remittance request at the time of receiving the remittance request is displayed.

As unprocessed requests, only the unprocessed requests of the user who received the remittance request (user A.A in this example) and the user who sent the remittance request (user BB in this example) are displayed. It may or may not be.

As described above, in this embodiment, by displaying the unprocessed request together with the information on the reception result of the remittance request, when the user confirms that the remittance request has been received, the unprocessed request can also be confirmed. It is configured to be able to.

<Processing>
FIG. 15-4 is a flowchart showing an example of the flow of processing executed by each device in this embodiment. Here, as an example, a process described with reference to FIG. 15-1 for displaying an unprocessed request when a user receives (receives) a remittance will be described.

The control unit 11 of the server 10 determines that the user A. of the terminal 20A is based on a request from the terminal 20B (not shown). The remittance process for A is executed (S210). Specifically, as an example, not a limitation, the user B. The remittance amount is subtracted from the balance of B's electronic money account to update it, and the user A. Update by adding the remittance amount to the electronic money account balance of A.

Then, the control unit 11 of the server 10 transmits the remittance result information and the remittance request list information to the terminal 20A by the communication I / F14 (S220).
Then, the control unit 11 of the server 10 ends the process.

In this case, the control unit 11 of the server 10 may or may not transmit the remittance result information to the terminal 20B.

The control unit 21 of the terminal 20A determines whether or not the remittance result information and the remittance request list information have been received from the server 10 by the communication I / F 22 (A205), and if it is determined that the remittance request list information has been received (A205: YES). , The display unit 24 displays the batch settlement screen including the remittance result information and the remittance request list information (A225).
The batch settlement screen is not limited, but is the notification screen shown in the display screen example as an example.
Then, the control unit 21 of the terminal 20A ends the process.

FIG. 15-5 is a flowchart showing another example of the flow of processing executed by each apparatus in this embodiment. Here, as an example, a process in the case of applying the hold of receiving remittance (holding of receipt) described with reference to FIG. 15-2 will be described.

The control unit 11 of the server 10 determines that the user A. of the terminal 20A is based on a request from the terminal 20B (not shown). The first remittance process for A is executed (S310a). Specifically, as an example, not a limitation, the user B. Update by subtracting the remittance amount from B's electronic money account balance.
In the first remittance process, unlike the remittance process (S210) in FIG. 15-4, the remittance amount is subtracted from the electronic money account balance of the sender user, but the remittance amount is added to the electronic money account balance of the recipient user. Do not add. In this state, the remittance is incomplete.

After that, the control unit 11 of the server 10 transmits the remittance result information of the first remittance process and the remittance request list information to the terminal 20A by the communication I / F14 (S320).

In this case, the control unit 11 of the server 10 may or may not transmit the remittance result information of the first remittance process to the terminal 20B.

After A225, the control unit 21 of the terminal 20A determines whether or not the input for receiving the remittance has been made to the input unit (A730), and if it is determined that the input has been made (A730: YES), requests the receipt of the remittance. The remittance receipt information for the purpose is transmitted to the server 10 by the communication I / F22 (A740).

After S320, the control unit 11 of the server 10 determines whether or not the remittance receipt information has been received from the terminal 20A by the communication I / F 14 (S740), and if it is determined that the remittance receipt information has been received (S740: YES), the first step is made. 2 Remittance processing is executed (S310b). Specifically, as an example, not a limitation, based on the result of the first remittance processing, the user A. Update by adding the remittance amount to the electronic money account balance of A. That is, the state in which the receipt (receipt) of the remittance is suspended is released, and the remittance is completely remitted.

After that, the control unit 11 of the server 10 transmits the remittance result information of the second remittance process to the terminal 20A and the terminal 20B by the communication I / F14 (S790).
Then, the control unit 11 of the server 10 ends the process.

When the remittance result information is received from the server 10 by the communication I / F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received remittance result information (A790).
Then, the control unit 21 of the terminal 20A ends the process.

Similarly, when the remittance result information is received from the server 10 by the communication I / F 22, the control unit 21 of the terminal 20B causes the display unit 24 to display the received remittance result information (B790).
Then, the control unit 21 of the terminal 20B ends the process.

Regarding the process of displaying the unprocessed request when the user receives the remittance request described in FIG. 15-3, "remittance" (receipt for user AA) in the process of FIG. 15-4 is performed. Since it can be configured in the same way by replacing it with "remittance request reception", the illustration and description are omitted.
Specifically, in the processing of the terminal 20A, it is determined whether or not the remittance request transmission result information and the remittance request list information are received by the A205, and the batch settlement screen including these information is displayed by the A225.
Further, in the process of the server 10, the remittance request transmission process is executed in S210, and the remittance request transmission result information and the remittance request list information are transmitted in S220.

<Display of unprocessed requests>
The unprocessed request to be displayed on the display unit 24 of the terminal 20 is not limited, but may be one or both of the following as an example.
-Unprocessed request corresponding to the other user (remittance source user) who sends money to himself or the other user (remittance request source user) who sends remittance request to himself-The other party who sends money to himself Unprocessed request corresponding to a user different from the user (remittance source user) or the user (remittance request source user) to whom the remittance request is sent to himself / herself.

It is possible to display the outstanding request corresponding to the other user. As an example, not a limitation, User A. A is user B. When receiving remittance with B as the remittance source user, or when user A. A is user B. When receiving a remittance request with B as the remittance request source user, user B. The unprocessed request corresponding to B can be displayed.

However, some users may want to see outstanding requests that correspond to a user different from the other user.
Therefore, as illustrated in FIGS. 15-1 to 15-3, the user B. In addition to the unprocessed request corresponding to B, as an example, but not a limitation, the user C.I. It is also possible to display the unprocessed request corresponding to C.
In this case, the user B. The unprocessed request corresponding to B is not displayed, and as an example, not limited to the user C.I. It is also possible to display the unprocessed request corresponding to C.

That is, as in the eighth embodiment, the following three patterns can be considered as an example, not limited, as the pattern for displaying the unprocessed request.
(Pattern 1) Unprocessed request corresponding to the other user (Pattern 2) Unprocessed request corresponding to the other user + Unprocessed request corresponding to a user different from the other user (Pattern 3) Different from the other user Outgoing request corresponding to user

Further, when applying any of the above patterns, for each user, all the unprocessed requests corresponding to the user may be displayed, or some unprocessed requests corresponding to the user may be displayed. It may be displayed.
That is, the user who displays the unprocessed request (the other user / the user different from the other user) and the range of the unprocessed request to be displayed (all / part) can be arbitrarily combined. As an example, not limited to (Pattern 2), the unprocessed requests corresponding to the other user display all the unprocessed requests, but the unprocessed requests corresponding to the user different from the other user are partially unprocessed. You may also display the request.

Further, when displaying some unprocessed requests, it is possible to determine the unprocessed requests to be displayed based on various information (conditions).
In this case, the contents of the 26th embodiment described later can be combined. As will be described in the 26th embodiment, the following information is mentioned as an example without limitation as various kinds of information.
-Date and time when the remittance request was sent / received-Remittance request amount-Payment deadline for the remittance request-A remittance request in which a user other than the user who requested the remittance and the user who requested the remittance is involved in the remittance request amount or reason , These information are merely examples and are not limited to these.
It is also possible to apply a plurality of of these pieces of information in combination.

Unprocessed requests with dates or dates older than a certain date may be forgotten by the user. Therefore, even an unprocessed request corresponding to a user different from the other user can be determined to be displayed.
Unprocessed requests with a remittance request amount larger than a certain amount may be of high importance. Therefore, even an unprocessed request corresponding to a user different from the other user can be determined to be displayed.
Remittance requests in which the user who requested the remittance and other users other than the user who requested the remittance are involved in the amount or reason of the remittance request may also be of high importance. Therefore, even an unprocessed request corresponding to a user different from the other user can be determined to be displayed.
Unprocessed requests whose payment deadline is approaching within a certain period may require immediate processing. Therefore, even an unprocessed request corresponding to a user different from the other user can be determined to be displayed.

Further, as described in the 26th embodiment, the unprocessed requests can be sorted and displayed in ascending / descending order based on the above-mentioned various information (conditions). As an example, the more important the unprocessed request is, the higher it can be displayed.

In addition to these, the unprocessed request to be displayed on the display unit 24 of the terminal 20 can be hidden based on the input of the user of the terminal 20 to the input unit, as an example without limitation.
In this case, as an example, the unprocessed requests corresponding to some users may be hidden, or the unprocessed requests corresponding to all users may be hidden.

In addition, depending on the user, it may be annoying to display the unprocessed request.
Therefore, it may be possible to set the display / non-display of the unprocessed request on a setting screen (not shown) or the like.

Specifically, on the setting screen of the application, as setting information regarding the display of the unprocessed request, a slide button or a check box that can switch the display / non-display of the unprocessed request is displayed as an example, not limited. Then, based on the operation for the slide button and the check box, the terminal 20 or the server 10 can be made to perform the display / non-display setting.

In this case, it may be possible to set the display / non-display of unprocessed requests collectively for all users, or it may be possible to set the display / non-display of unprocessed requests individually for each user.
Further, it may be possible to set the display / non-display of all unprocessed requests, or it may be possible to set the display / non-display of some unprocessed requests.

These contents are the same for the following examples.

<Effect of 17th Example>
In this embodiment, the terminal 20 of the proposer user is from the remittance result information from the other user (not limited to, an example of the first information regarding the remittance from the first user to the terminal user) or from the other user. The transmitted remittance request information (not limited, but an example of the first information regarding the remittance request transmitted from the first user to the user of the terminal) is received from the server 10 by the communication I / F22.
Then, the terminal 20 of the proposer user displays the first display based on the received information on the display unit 24, and based on the reception of the first information, the received remittance request regarding the received remittance request from the other user. Information (not limited, but an example of the second information about the remittance request sent from the second user to the user of the terminal) and the sent remittance request information about the sent remittance request to the other user (not limited, but the terminal A configuration is shown in which a second display based on (an example of a second information regarding a remittance request transmitted from a user to a second user) is displayed on the display unit 24.
As an example of the effect of the embodiment obtained by such a configuration, when the user of the terminal confirms the first information, the second information can be confirmed at the same time.

Further, in the present embodiment, the terminal 20 of the proposer user receives the remittance amount based on the input to the terminal 20 in which the first display and the second display are displayed by the proposer user. A configuration is shown in which the control unit 21 performs a process (not limited to an example of a first process relating to the receipt of remittance).
As an example of the effect of the embodiment obtained by such a configuration, it is possible to easily realize the reception of remittance from the other user based on the input to the terminal in which the first display and the second display are displayed. ..

<17th variant (1)>
In the 17th embodiment, settlement (including batch settlement of unprocessed requests) is performed based on the input for the information of the unprocessed request displayed together with the remittance result information from the other user and the remittance request information transmitted from the other user. .) May be executed.

Specifically, not limited to the screen example of FIGS. 15-1 to 15-3, a settlement button for executing settlement of selected unprocessed requests (collective settlement when multiple selections are made) is displayed. ..
Then, when the settlement button is tapped, the settlement process of the selected unprocessed request can be executed by the server 10.

Since the settlement processing of the unprocessed request is as described above, the description thereof will be omitted again.

FIG. 15-6 is a flowchart showing an example of the flow of processing executed by each device in this modification. Here, as an example, in the process of remittance receipt hold (receipt hold) shown in FIG. 15-5, a process in which either the remittance receipt or the settlement of the unprocessed request is performed will be described.

After A225, the control unit 21 of the terminal 20A determines the execution target based on the input to the input unit (A831).
If it is determined that the execution target is the settlement of unprocessed requests (collective settlement when a plurality of selected items are selected) (A831: settlement of unprocessed requests), the control unit 21 of the terminal 20A transfers the processing to A632. That is, the request selection information including the unprocessed request selection information indicating the selected unprocessed request is set.

On the other hand, if it is determined that the execution target is the receipt of remittance (A831: remittance receipt), the control unit 21 of the terminal 20A sets the request selection information including the remittance receipt information (A333).

After A632 or A333, the control unit 21 of the terminal 20A transmits the set request selection information to the server 10 by the communication I / F22 (A140).
Then, the control unit 21 of the terminal 20A shifts the processing to the A150.

When 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 determines the processing target based on the received request selection information (S841).

If it is determined that the processing target is the settlement of the unprocessed request (S841: settlement of the unprocessed request), the control unit 11 of the server 10 transfers the processing to S642. That is, the selected unprocessed request is set as the settlement target (when multiple selections are made, the batch settlement target). Then, the control unit 11 of the server 10 executes the settlement process of S150.

On the other hand, if it is determined that the processing target is the receipt of remittance (S841: remittance receipt), the control unit 11 of the server 10 transfers the processing to S310b. That is, the second remittance process is executed.
Then, the control unit 11 of the server 10 shifts the processing to S170.

When applying the first settlement process described in FIG. 1-19 as an example rather than a limitation,
When S642 is set and there are a plurality of unprocessed requests to be processed, the determination result of whether or not the settlement target in S1510 is a batch settlement target is "YES". As a result, the processing after S1515 is executed with the plurality of unprocessed requests as the batch settlement target.
Further, when S642 is set and there is only one unprocessed request to be processed, the determination result of whether or not the settlement target in S1510 is the batch settlement target is "NO". As a result, the processing after S1570 is executed with this one unprocessed request as the settlement target.

The process of displaying the unprocessed request when the user receives the remittance amount without suspending the receipt of the remittance and settling the unprocessed request can be similarly configured according to FIG. 15-6. Therefore, the illustration and description will be omitted.
Further, the process of displaying the unprocessed request when the user receives the remittance request and performing either the remittance or the settlement of the unprocessed request can be similarly configured according to FIG. 15-6. Therefore, the illustration and description are omitted.

In this modification, the terminal 20 of the proposer user is from the remittance result information from the other user (not limited, but an example of the first information regarding the remittance from the first user to the terminal user) or from the other user. The transmitted remittance request information (not limited, but an example of the first information regarding the remittance request transmitted from the first user to the user of the terminal) is received from the server 10 by the communication I / F22.
Further, the terminal 20 of the proposer user displays the first display based on the received information on the display unit 24, and based on the reception of the first information, the received remittance request regarding the received remittance request from the other user. Information (not limited, but an example of the second information about the remittance request sent from the second user to the user of the terminal) and the sent remittance request information about the sent remittance request to the other user (not limited, but the terminal The second display based on (an example of the second information regarding the remittance request transmitted from the user to the second user) is displayed on the display unit 24.
Then, the terminal 20 of the proposer's user receives the process for remittance or the remittance amount based on the input to the terminal 20 in which the first display and the second display are displayed by the proposer's user. Controls the process for sending a remittance request, the process for sending a remittance request, or the process for receiving a remittance request (not limited to, but an example of the first process relating to a remittance, receiving a remittance, or requesting a remittance). The configuration performed by the unit 21 is shown.
As an example of the effect of the embodiment obtained by such a configuration, remittance to the other user and remittance from the other user are received based on the input to the terminal displaying the first display and the second display. , It is possible to easily realize the transmission / reception of the remittance request to the other user.

<17th variant (2)>
In the above embodiment, the settlement result information in the display screen is rendered and displayed based on the first information. That is, the first display and the second display are displayed substantially at the same time.
However, in the above embodiment, the display of the first display and the display of the second display includes the following two cases.
(1) Reception of first information → first display → second display (2) reception of first information → first display, reception of first information → second display

(1) is a case where the first display is displayed based on the received first information and the second display is displayed based on the displayed first display.
(2) is a case where the first display is displayed based on the received first information and the second display is displayed based on the received first information.
In any case, the reception of the first information is still the trigger.

Further, the order in which the first display and the second display are displayed may be in any order.
That is, the case of the above (1) is set as "reception of the first information-> the second display-> the first display", and the case of the above (2) is set as "reception of the first information-> the second display, the first information". It is also possible to select "Reception-> 1st display".

This also applies to the examples described below.

Next, as an embodiment related to the 17th embodiment, when the user of the terminal 20 receives (receives money) the amount of money remitted from the other user, or receives a remittance request from the other user. An embodiment in which an unprocessed request selected from the displayed unprocessed requests is also processed will be described.

In the following examples, the following five patterns will be roughly described.
(A) Pattern to process receipt + received remittance request (b) Pattern to process receipt + sent remittance request (c) Pattern to process receipt + received remittance request + process sent remittance request (D) Pattern of receiving remittance request + processing of received remittance request (e) Pattern of receiving remittance request + processing of sent remittance request Each pattern will be described separately.

As shown in the 17th modification, the process (first process, etc.) executed by the terminal 20 by the control unit 21 is not limited, but as an example, a process for performing remittance (not limited, but a process related to remittance). (Example), processing for receiving (receipt) remittance (an example of processing related to receiving remittance, not limitation), processing for sending / receiving remittance request (processing related to request for remittance, not limitation) Example) processing such as) is included.
In the following, a server-client system will be illustrated, and remittance, remittance request transmission, and the like will be performed via the server 10.

Further, 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) is illustrated.
As described above, when the other user is a plurality of different users, that is, the first user is a user different from the second user (the second user is a user different from the first user). Similarly, the method described below can be applied to the above.

<18th Example>
This embodiment is an example relating to the processing of the pattern of the above (a).
The contents described in the eighteenth embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

FIG. 16-1 is a diagram showing an example of a table for explaining a processing method corresponding to each of the above patterns.
The vertical direction of the table shows the processing target (new processing target) to be newly executed as an item, and the horizontal direction of the table shows the type of unprocessed request as an item. In the column where the vertical item and the horizontal item intersect, an example of the processing realized by the combination of the new processing target and the type of the unprocessed request is shown.
I will explain in order.

In the pattern of (a) receipt + received remittance request, (a1) receipt + remittance can be processed. That is, when receiving money from the other user, the money is also sent to the other user based on the received remittance request from the other user.

<Display screen>
FIG. 16-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 not limited, but as an example, User A. This is a payment application notification screen displayed on the display unit 24 of the terminal 20A of A.
In the current position display area CLR1 indicating the current position in the payment application, the character "notice" indicating that the current position is the notification function of the payment application is displayed.

In the notification information display area NTR2 on the notification screen, the remittance result information NC1 is displayed as the content related to the receipt (receipt) of the remittance.
In the following, for convenience, the remittance request list information may be included in the remittance result information. In this case, the remittance result information may be referred to as collective settlement information.

Further, for the server 10, it is the remittance result information because it is the result of performing the remittance processing, and for the other user (user BB in this example), it is also the remittance result information. For A), it can be said that it is the remittance result information because it is the result of the remittance.

The remittance result information NC1 is not limited to the user A. A is user B. The contents corresponding to the receipt of the remittance amount "500 yen" sent (received) from B are displayed.

Below that, a list of unprocessed remittance requests for the user who received the remittance at the time the remittance was received (user AA in this example) is displayed. In this example, four unprocessed requests are listed in chronological order in chronological order. Since the display mode of each unprocessed request can be configured in the same manner as in FIG. 1-23 as an example without limitation, the description thereof will be omitted again.

As the unprocessed request, only the unprocessed request between the remittance user (user A.A. in this example) and the remittance user (user BB in this example) may be displayed. And you don't have to do that. In this case, the display mode of each unprocessed request is not limited, but can be configured as in FIG. 1-11 as an example.

At the bottom of the remittance result information NC1, a all-selection batch settlement button indicating "all-selection batch settlement" is displayed for executing the all-selection batch settlement. In addition, next to the all-select batch settlement button, "one case" for executing partial selection batch settlement of unprocessed requests selected by the user among the unprocessed requests displayed in the remittance result information NC1. A partial selection batch settlement button BT17 indicating "Settlement" is displayed.

As an example, not a limitation, in the remittance result information NC1, the check of the request of the first received remittance request (payment to user CC of 2,000 yen) is selected as "ON" and partially selected. When the batch settlement button BT17 is tapped, the terminal 20A requests the server 10 to execute the batch settlement of the selected unprocessed request. Then, from the server 10, the other user C.I. Terminal 20C of C and our user A. Settlement result information regarding the execution result is transmitted to the terminal 20A of A.

FIG. 16-3 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20A based on the tapping of the partial selection batch settlement button BT17.
In this example, in the notification information display area NTR2 on the notification screen, the settlement result information NC2 is displayed as the content of the batch settlement under the remittance result information NC1.

The settlement result information NC2 is not limited to the user A. A is the user C.I. By the settlement regarding the payment of the remittance request amount "2,000 yen" by the remittance request from C, the user C. Information about the remittance of the remittance amount "2,000 yen" to C is displayed.

In addition, user C. The settlement result information displayed on the terminal 20C of C includes the user A. In addition to displaying the receipt of the remittance amount "2,000 yen" from A, the user C.I. A list of unprocessed requests of C is added and displayed.

<Processing>
FIG. 16-4 is a flowchart showing an example of the flow of processing executed by each device in this embodiment.
The control unit 11 of the server 10 determines that the user A. of the terminal 20A is based on the request from the terminal 20B. The remittance process for A is executed (S210). Specifically, as an example, not a limitation, the user B. The remittance amount is subtracted from the balance of B's electronic money account to update it, and the user A. Update by adding the remittance amount to the electronic money account balance of A.
Then, the control unit 11 of the server 10 transmits the remittance result information and the remittance request list information to the terminal 20A by the communication I / F14 (S220).

The control unit 21 of the terminal 20A determines whether or not the remittance result information and the remittance request list information have been received from the server 10 by the communication I / F 22 (A205), and if it is determined that the remittance request list information has been received (A205: YES). , The display unit 24 displays the batch settlement screen including the remittance result information and the remittance request list information (A225).

If it is determined in A131 that an unprocessed request has been selected (A131: YES), the control unit 21 of the terminal 20A sets the unprocessed request selection information as the request selection information (A232). Then, the control unit 21 of the terminal 20A shifts the processing to the A140.
On the other hand, if it is determined that the unprocessed request has not been selected (A131: NO), the control unit 21 of the terminal 20A ends the process.

If it is determined in S141 to process the unprocessed request (S141: YES), the control unit 11 of the server 10 sets the batch settlement of the selected unprocessed request as the batch settlement target (S242). Then, the control unit 11 of the server 10 shifts the processing to S150.
Further, if it is determined that the processing is not the processing of the unprocessed request (S141: NO), the control unit 11 of the server 10 ends the processing.

<Effect of 18th Example>
In this embodiment, the terminal 20 of the proposer user transmits the remittance result information from the other user (not limited to the first example of the remittance from the first user to the terminal user) by the communication I / F22. Receive from server 10.
Further, the terminal 20 of the proposer's user displays the first display (not limited, but an example of the first display) based on the received remittance result information on the display unit 24, and based on the reception of the remittance result information, the other party. Second display (not limited, but an example of the second information regarding the remittance request sent from the second user to the terminal user) based on the received remittance request information regarding the received remittance request from the user of 2 An example of display) is displayed on the display unit 24.
Then, the terminal 20 of the proposer's user relates to remittance or receives money (not limited, but remittance) based on the input to the terminal 20 in which the first display and the second display are displayed by the proposer's user. An example of receiving) shows a configuration in which the first process is executed by the control unit 21.
As an example of the effect of the embodiment obtained by such a configuration, the first process relating to remittance or receiving remittance is simplified and appropriately performed based on the input to the terminal displaying the first display and the second display. It can be carried out.

Further, in this embodiment, the second information is remittance result information (not limited, but an example of information regarding remittance from the first user to the user of the terminal), and the second information is the received remittance request information (not limited). It is not a limitation, but is an example of information regarding a remittance request sent from a second user to a user of a terminal), and the first process is based on an input to the terminal 20 in which the second display is displayed, and the other user (another user (an example). It is not limited to the present invention, and shows a configuration including a process of remittance to a second user).
As an example of the effect of the embodiment obtained by such a configuration, the terminal user is notified that the remittance is scheduled to be performed from the first user to the terminal user, and the input to the terminal on which the second display is displayed is displayed. The money can be sent to the second user based on.

Further, in the present embodiment, the first display and the second display are displayed on the display unit 24 by the payment application installed on the terminal 20 of the proposer user, and the payment application is included in the program according to the present disclosure. The configuration is shown.
As an example of the effect of the embodiment obtained by such a configuration, the first display and the second display can be displayed on the display unit of the terminal by the application installed on the terminal.

<18th modification>
In the above embodiment, it is assumed that the remittance from the other user is completed when the remittance result information is received by the terminal 20 of the proposer user, but the present invention is not limited to this.
Specifically, the above-mentioned method of holding remittance receipt (holding receipt) is applied, and based on the fact that the input (operation, etc.) of receiving remittance is made while the second display is displayed. The remittance from the other user may or may not be completed.
This also applies to the other examples.

<19th Example>
The nineteenth embodiment is an example relating to the processing of the pattern (b) described above.
The contents described in the 19th embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

In the pattern of (b) receipt + remittance request sent, (b1) receipt + remittance reminder can be processed. That is, when receiving money from the other user, remittance reminding is performed for this remittance request based on the sent remittance request to the other user.
In this case, a new remittance request may or may not be made instead of the remittance reminder.

<Display screen>
FIG. 17-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 not limited, but as an example, User A. This is a payment application notification screen displayed on the display unit 24 of the terminal 20A of A. The details of the screen configuration are not limited, but can be configured in the same manner as in FIG. 16-2 as an example, and thus the details thereof will be omitted.

As an example, not a limitation, in the remittance result information NC1, the check of the request for the third received remittance request (received from user CC of 1,000 yen) is selected as "ON" and partially selected. When the batch settlement button BT17 is tapped, the terminal 20A requests the server 10 to execute the batch settlement of the selected unprocessed requests. Then, from the server 10, the other user C.I. Settlement result information regarding the execution result is transmitted to the terminal 20C of C.

FIG. 17-2 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20C based on the tapping of the partial selection batch settlement button BT17.
In this example, the settlement result information NC3 is displayed as the content of the batch settlement in the notification information display area NTR1 on the notification screen.
The settlement result information NC3 is not limited to the third remittance request selected in FIG. 17-1 (the remittance request amount "1,000 yen" sent by the user AA to the user CC). The reminder corresponding to the remittance request) is displayed.

When the above-mentioned partial selection batch settlement button BT17 is tapped, the user C.I. Information such as that indicated by the text "Sent remittance reminders to user CC" may or may not be displayed to indicate that the remittance reminder has been sent to C. ..

<Processing>
Since the processing executed by each device in this embodiment can be similarly realized by following the processing of FIG. 16-4, illustration and detailed description thereof will be omitted.

<Effect of 19th Example>
In this embodiment, the terminal 20 of the proposer user transmits the remittance result information from the other user (not limited to the first example of the remittance from the first user to the terminal user) by the communication I / F22. Receive from server 10.
Further, the terminal 20 of the proposer's user displays the first display (not limited, but an example of the first display) based on the received remittance result information on the display unit 24, and based on the reception of the remittance result information, the other party. Display based on sent remittance request information (not limited, but an example of the second information regarding the remittance request sent from the terminal user to the second user) regarding the sent remittance request to the user (second display, not limited) An example) is displayed on the display unit 24.
Then, the terminal 20 of the proposer's user receives money (not limited, but an example of receiving remittance) based on the input by the proposer's user to the terminal 20 in which the first display and the second display are displayed. The control unit 21 executes the first process regarding remittance reminders, remittance reminders, and new remittance requests (not limited to, but an example of remittance requests).
As an example of the effect of the embodiment obtained by such a configuration, the first process regarding the receipt of remittance or the request for remittance can be simplified and performed based on the input to the terminal displaying the first display and the second display. Can be done properly.

Further, in this embodiment, the first information is remittance result information from the other user (not limited, but an example of information regarding remittance from the first user to the terminal user), and the second information is a proposal. It shows a configuration which is the sent remittance request information (not limited, but an example of the information about the remittance request sent from the terminal user to the second user) about the sent remittance request from the user of the user to the other user. ..
As an effect of the embodiment obtained by such a configuration, it is possible to collectively perform the process based on the remittance from the first user to the user of the terminal and the remittance request sent from the user of the terminal to the second user. can.

Further, in this case, the first process sends a remittance reminder or a new remittance request to the other user (not limited to an example of the second user) based on the input to the terminal 20 in which the second display is displayed. The configuration including the processing is shown.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to easily request the second user to remittance based on the input to the terminal on which the second display is displayed.

<20th Example>
The twentieth embodiment is an example relating to the processing of the pattern (c) described above.
The contents described in the twentieth embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

(C) In the pattern of receipt + received remittance request + sent remittance request, the process of (c1) [receipt + remittance] (amount deduction possible) + [remittance + receipt] (amount deduction possible) is performed. It can be carried out.

In this process, when receiving money from the other user, remittance to the other user is also performed based on the received remittance request from the other user. In this case, it is possible to receive / remit the amount of the difference between the remittance request amounts. Also, if the remittance request amount is the same amount, it is possible to offset the amount.
In addition, remittance is sent to the other user based on the received remittance request from the other user, and remittance is received from the other user based on the sent remittance request to the other user. In this case, the amount of the difference between the remittance request amounts can be sent / received. Also, if the remittance request amount is the same amount, it is possible to offset the amount.

<Display screen>
Here, as an example, an example of a display screen in the case of applying the above-mentioned hold of receipt of remittance (hold of receipt) will be described.

FIG. 18-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 not limited, but as an example, User A. This is a payment application notification screen displayed on the display unit 24 of the terminal 20A of A.
In the notification information display area NTR2 on the notification screen, the remittance result information NC4 is displayed as the content related to the receipt (receipt) of the remittance.
The remittance result information NC4 is not limited to the user A. A is user C. The contents corresponding to the receipt of the remittance amount "500 yen" sent from C are displayed.

The remittance result information NC4 displays a remittance receiving button indicated as "Remittance receipt" for accepting and receiving the remittance. That is, User A. The remittance process is not completed until the remittance receiving button is tapped by A, and when the remittance receiving button is tapped, the remittance is sent to the electronic money account balance of the transferred user (user A.A in this example). The amount ("500 yen" in this example) is added.

Further, in the remittance result information NC4, similarly to the remittance result information NC1, a list of remittance requests in which the user (user AA in this example) who has remittance at the time of receiving the remittance is unprocessed is displayed.

At the bottom of the remittance result information NC4, a remittance all-selection batch settlement button indicating "Settle all and receive remittance" is displayed to execute the all-selection batch settlement assuming that the remittance has been accepted. There is. In addition, next to the payment all selection batch settlement button, it is assumed that the remittance has been accepted, and among the unprocessed requests displayed in the remittance result information NC4, some of the unprocessed requests selected by the user are collectively selected and batch settlement. The remittance lump sum settlement button BT18, which is indicated as "one settlement", is displayed for executing the above.

Remittance result information The remittance receiving button of NC4 is the user A. When tapped by A, the display mode of the remittance result information NC4 is not limited to the user C.I. When C is set, the remittance result information changes in the same manner as NC1.

As an example, not limited to, in the remittance result information NC4, the first received remittance request (payment to user CC 2,000 yen) and the third sent remittance request (user CC). When the check for the request to receive from (1,000 yen) is set to "ON" and selected, and the receipt batch settlement button BT18 is tapped, remittance (user CC) is sent from the terminal 20A to the server 10. (Remittance to User A.A.) and batch settlement of selected unprocessed requests are requested to be executed. This remittance is made by User A. For A, it is the receipt (receipt) of remittance.

Then, from the server 10, the other user C.I. The batch settlement approval confirmation information for confirming the intention of whether or not to approve the batch settlement is transmitted to the terminal 20C of C, and is displayed on the display unit 24 of the terminal 20C.

FIG. 18-2 is a diagram showing an example of a notification screen displayed based on the tapping of the receipt batch settlement button BT18.
In the notification information display area NTR1, the batch settlement approval confirmation information NC5 is used as the user A. The icon image of A and the lump sum settlement amount are displayed.

The batch settlement approval confirmation information NC5 contains the contents of the batch settlement as the user C.I. C is the user A. Upon receiving the remittance request amount "2,000 yen" based on the transmission of the past remittance request to A, the user A. Based on the receipt of the past remittance request from A, the remittance request amount "1,000 yen" is paid, and the user A. It is displayed that "500 yen" will be paid by this remittance to A.

Further, in the batch settlement approval confirmation information NC5, the user C.I. C is user A. Receive "500 yen" from A, which is obtained by subtracting the remittance request amount "1000 yen" and the current remittance amount "500 yen" from the amount received by sending the remittance request "2,000 yen". Is displayed.

At the bottom of the batch settlement approval confirmation information NC5, there is a settlement button BT19 indicating "to settle" to approve the settlement with the above contents, and "decline" to decline the settlement without approving the settlement with the above contents. The refusal button indicated as is displayed.

FIG. 18-3 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20A based on the tapping of the settlement button BT19.
In this example, in the notification information display area NTR2 on the notification screen, the settlement result information NC6 is displayed as the content of the batch settlement under the remittance result information NC4.

The settlement result information NC6 is not limited to the user A. A and user C. Since the lump sum settlement was performed with C, the payment of the settlement result amount (in this example, the remittance amount "500 yen" that the user AA sent to the user CC is paid as the content of the lump sum settlement. ) Is displayed.

That is, in this embodiment, even if the remittance result information NC4 is tapped, the remittance all-selection batch settlement button or the receipt batch settlement button BT18 is not immediately executed. By suspending the receipt of the remitted amount once (holding the receipt of the remittance, holding the receipt) and including it in the contents of the batch settlement, the settlement is executed collectively.

The remittance may be canceled after a certain period of time has passed since the remittance result information was transmitted by the server 10. On the contrary, the remittance may be forcibly completed.

In FIG. 18-1, when the payment batch settlement button BT18 is tapped, the display unit 24 of the terminal 20A displays the user A. A displays a confirmation screen to the effect that the lump sum settlement amount "500 yen" will be paid, and the user A. Based on A's approval, you may or may not be asked to receive the remittance and perform the bulk settlement of the selected outstanding requests.

<Processing>
FIG. 18-4 is a flowchart showing an example of the flow of processing executed by each device in this embodiment.

If it is determined that the unprocessed request is selected in A131 (A131: YES), the control unit 21 of the terminal 20A requests the remittance receipt information regarding the receipt of the remittance in the first remittance process and the unprocessed request selection information. It is set as selection information (A332).

On the other hand, if it is determined that the unprocessed request has not been selected (A131: NO), the control unit 21 of the terminal 20A sets the remittance receipt information as the request selection information (A333).

In A131, the process of A333 may be executed only when the receipt of remittance is explicitly selected, and if not selected, the control unit 21 of the terminal 20A may end the process. You don't have to.
After A332 or A333, the control unit 21 of the terminal 20A transfers processing to A140.

If it is determined in S141 to process the unprocessed request (S141: YES), the control unit 11 of the server 10 remittance (remittance from user BB to user AA) and batch settlement of the unprocessed request. Is set as a batch settlement target (S342). Then, the control unit 11 of the server 10 shifts the processing to S150.

On the other hand, if it is determined that the unprocessed request is not processed (S141: NO), the control unit 11 of the server 10 shifts the processing to S310b. That is, the second remittance process is executed.
Then, the control unit 11 of the server 10 shifts the processing to S170.

The control unit 21 of the terminal 20B executes the processes of B150 to B190.
Then, the control unit 21 of the terminal 20B ends the process.

<Effect of 20th Example>
In this embodiment, the terminal 20 of the proposer user communicates unfinished remittance result information from the other user (not limited to, but an example of the first information regarding the remittance from the first user to the terminal user). Received from the server 10 by / F22.
Further, the terminal 20 of the proposer user displays the first display (not limited, but an example of the first display) based on the received incomplete remittance result information on the display unit 24, and is based on the reception of the remittance result information. The received remittance request information (not limited, but an example of the second information regarding the remittance request sent from the second user to the terminal user), or the sent remittance request information (not limited, but the second from the terminal user). The second display (not limited, but an example of the second display) based on the second information regarding the remittance request transmitted to the user) is displayed on the display unit 24.
Then, the terminal 20 of the proposer's user sends or receives money (not limited, but receives the remittance) based on the input by the proposer's user to the terminal 20 on which the first display and the second display are displayed. An example is shown in which the control unit 21 executes the first process relating to (1).
As an example of the effect of the embodiment obtained by such a configuration, the first process relating to remittance or receiving remittance is simplified and appropriately performed based on the input to the terminal displaying the first display and the second display. It can be carried out.

Further, in this case, the first process is based on the operation of receiving remittance (not limited, but an example of input to the terminal on which the first display is displayed) after the first display is displayed on the display unit 24. The configuration including the process of receiving the remittance amount from the other user (not limited, but an example of the process of receiving the amount of remittance from the first user to the user of the terminal) is shown.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to receive the amount of money remitted from the first user based on the input to the terminal on which the first display is displayed.

Further, in this embodiment, the other user is one user (not limited, but an example in which the second user is the first user), and the first process is the received remittance request information and the transmitted remittance request. It shows a configuration including a process of remittance of an amount based on information to a partner user or remittance from the partner user.
As an example of the effect of the embodiment obtained by such a configuration, the amount of money based on the first information and the second information can be remitted to the first user, or remittance can be received from the first user.

In this case, the first process remits the amount obtained by subtracting the remittance request amount included in the sent remittance request information from the remittance request amount included in the received remittance request information, or remits the sent remittance request to the other user. It is possible to include the process of remittance from the other user in the amount obtained by subtracting the remittance request amount included in the received remittance request information from the remittance request amount included in the information.
As an example of the effect of the embodiment obtained by such a configuration, the difference amount can be remitted to the first user, or the remittance can be received from the first user.

Further, in this case, the first process can be executed based on the approval by the other user based on the input to the terminal 20 of the other user.
As an example of the effect of the embodiment obtained by such a configuration, the first process can be executed based on the approval by the first user based on the input to the terminal of the first user. Thereby, as an example, not limited, it is possible to prevent the first process from being executed without the intention of the first user.

<20th modification>
Although related to the above embodiment, the “receipt” in the new processing target in the table of FIG. 16-1 may be set as the “receipt hold”.

in this case,
-Receipt hold + Received remittance request-Receipt hold + Sent remittance request-Receipt hold + Received remittance request + Sent remittance request can be processed.

The processing of these patterns is the same as the processing of the patterns (a) to (c), respectively. This is because it is just the difference between receiving the remitted amount immediately or receiving it later after a while.

<21st Example>
The 21st embodiment is an example relating to the processing of the pattern (d) described above.
The contents described in the 21st Example can be applied to any of the other Examples and the other variants.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

In the pattern of (d) receiving remittance request + received remittance request, (d1) remittance [remittance + remittance] can be processed. That is, the remittance is sent to the other user based on the receipt of the remittance request from the other user, and the remittance is sent to the other user based on the received remittance request from the other user.

<Display screen>
FIG. 19-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 not limited, but as an example, User A. This is a payment application notification screen displayed on the display unit 24 of the terminal 20A of A.

In the notification information display area NTR2 on the notification screen, the remittance request information NC7 is displayed as the content related to the reception of the request remittance.
The remittance request information NC7 is not limited to the user A. A is user B. The contents corresponding to the remittance request of the remittance request amount "500 yen" received from B are displayed. In addition, the remittance request information NC7 indicates a remittance request remittance button indicating "send money" to accept the remittance request and perform remittance, and "decline" to reject this remittance request. The remittance request rejection button that was sent is displayed.

Below that, a list of remittance requests that have not been processed by the user (user AA in this example) who received the remittance request at the time of receiving the remittance request is displayed. Since the display mode of the unprocessed request can be configured in the same manner as in FIG. 16-2 as an example without limitation, detailed description thereof will be omitted.

As unprocessed requests, only the unprocessed requests of the user who received the remittance request (user A.A in this example) and the user who sent the remittance request (user BB in this example) are displayed. It may or may not be.

At the bottom of the remittance request information NC7, a remittance request remittance all-selection batch settlement button indicating "all settlement and remittance" is displayed to execute the remittance by this remittance request and all-selection batch settlement. There is. In addition, next to the remittance request remittance all selection batch settlement button, there is a partial selection batch settlement of the remittance by this remittance request and the unprocessed request displayed in the remittance request information NC7. A remittance request remittance partial selection batch settlement button BT20, which is indicated as "one settlement and remittance", is displayed.

As an example, not a limitation, in the remittance request information NC7, the check of the request for the second received remittance request (payment to user BB is 3,500 yen) is selected as "ON", and the remittance request remittance is selected. When the partial selection batch settlement button BT20 is tapped, the terminal 20A requests the server 10 to execute the batch settlement of the selected unprocessed requests. Then, the user B. who is the other party from the server 10. Terminal 20B of B and our user A. Settlement result information regarding the execution result is transmitted to the terminal 20A of A.

FIG. 19-2 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20A based on the tapping of the remittance request partial remittance partial selection batch settlement button BT20.
In this example, in the notification information display area NTR2 on the notification screen, the settlement result information NC8 and the settlement result information NC9 are displayed as the contents of the batch settlement under the remittance request information NC7.

The settlement result information NC8 is not limited to the user A. A is user B. By the settlement regarding the payment of the remittance request amount "3,500 yen" by the past remittance request from B, the user B. Information about the remittance of the remittance amount "3,500 yen" to B is displayed.
The settlement result information NC9 is not limited to the user A. A is user B. By the settlement regarding the payment of the remittance request amount "500 yen" by this remittance request from B, the user B. Information regarding the execution of the remittance of the remittance amount of "500 yen" to B is displayed.

In addition, user B. The settlement result information displayed on the terminal 20B of B includes the user A. In addition to the display of remittance receipt from A, the user B. A list of unprocessed requests of B is added and displayed.

FIG. 19-3 is another example of the display screen of FIG. 19-2.
In this example, in the notification information display area NTR2 on the notification screen, the settlement result information NC10 is displayed as the content of the batch settlement under the remittance request information NC7.

The settlement result information NC10 is not limited to the user A. A and user B. Since the lump sum settlement was performed with B, the user A. A is user B. We paid B "1,000 yen", which is the sum of the remittance request amount "3,500 yen" due to the receipt of the past remittance request and the remittance request amount "500 yen" due to the receipt of the current remittance request. It is displayed that the money has been sent).

In addition, user B. In the settlement result information displayed on the terminal 20B of B, the contents of the batch settlement may or may not be collectively displayed as one settlement result information.

<Processing>
FIG. 19-4 is a flowchart showing an example of the flow of processing executed by each device in this embodiment.
The control unit 11 of the server 10 determines that the user B. is based on the request from the terminal 20B. The remittance request information from B and the remittance request list information are transmitted to the terminal 20A by the communication I / F14 (S420).
Then, the control unit 11 of the server 10 shifts the processing to S140.

The control unit 21 of the terminal 20A determines whether or not the remittance request information and the remittance request list information have been received from the server 10 by the communication I / F 22 (A405), and if it is determined that the remittance request information has been received (A405: YES). , The batch settlement screen including these information is displayed on the display unit 24 (A425).

When it is determined that the unprocessed request is selected in A131 (A131: YES), the control unit 21 of the terminal 20A shifts the processing to A132. That is, the request selection information including the remittance information related to the remittance based on the received remittance request information and the unprocessed request selection information indicating the selected unprocessed request is set.
On the other hand, when it is determined that the unprocessed request is not selected in A131 (A131: NO), the control unit 21 of the terminal 20A shifts the processing to A133. That is, the request selection information including the remittance information regarding the remittance based on the received remittance request information is set.

In this process, it is assumed that the remittance is performed based on the received remittance request information.
In reality, it may be selected to process only the unprocessed request without making a remittance based on the received remittance request information, but in this case, the processing in this case is the processing of the batch settlement of the unprocessed request described above. Since it is the same as the above, the illustration and the description will be omitted again.

When it is determined in S141 that the unprocessed request is processed (S141: YES), the control unit 11 of the server 10 transfers the processing to S142.
On the other hand, when it is determined in S141 that the processing of the unprocessed request is not performed (S141: NO), the control unit 11 of the server 10 transfers the processing to S143.

<Effect of 21st Example>
In this embodiment, the first information is the remittance request information regarding the remittance request received from the other user, and the second information is the received remittance request information regarding the remittance request received from the other user. The first process shows a configuration including a process of remittance to a partner user based on an input to the terminal 20 for displaying the first display and the second display.
As an example of the effect of the embodiment obtained by such a configuration, remittance can be easily sent to the first user and the second user based on the input to the terminal displaying the first display and the second display.

Further, in this case, the other user is one user, and the first process includes a process of remittance to the other user based on the input to the terminal 20 displaying the first display and the second display. can do.
As an example of the effect of the embodiment obtained by such a configuration, one user (first user) is easily remitted as the other user based on the input to the terminal displaying the first display and the second display. be able to.

<22nd Example>
The 22nd embodiment is an example relating to the processing of the pattern (e) described above.
The contents described in the 22nd embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

In the pattern of (e) Remittance request received + Sent remittance request, either (e1) Remittance + Remittance reminding or (e2) [Remittance + Receiving] (amount deduction is possible) can be performed. ..

In the process of (e1), remittance is performed to the other user based on the receipt of the remittance request from the other user, and remittance reminding is also performed based on the sent remittance request to the other user.
In this case, a new remittance request may or may not be made instead of the remittance reminder.

In the process of (e2), the remittance is sent to the other user based on the receipt of the remittance request from the other user, and the remittance is sent from the other user based on the sent remittance request to the other user. Receive money. In this case, the amount of the difference between the remittance request amounts can be sent / received. Also, if the remittance request amount is the same amount, it is possible to offset the amount.
In this case, the approval of the other user may or may not be required to obtain the approval of the other user.

<Display screen>
FIG. 20-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 not limited, but as an example, User A. This is a payment application notification screen displayed on the display unit 24 of the terminal 20A of A. The details of the screen configuration are not limited, but as an example, the sender of the remittance request is the user C.I. Since it can be configured in the same manner as in FIG. 19-1 in the case of C, the description thereof will be omitted in detail.
The sender of the remittance request is the user C.I. Here, the remittance request information in the case of C is the remittance request information NC11.

As an example, not a limitation, in the remittance request information NC11, the check of the request for the third sent remittance request (receipt from user CC of 1,000 yen) is selected as "ON", and the remittance request remittance is selected. When the partial selection batch settlement button BT21 is tapped, the terminal 20A requests the server 10 to execute the batch settlement of the selected unprocessed requests. Then, from the server 10, the other user C.I. Terminal 20C of C and our user A. Settlement result information regarding the execution result is transmitted to the terminal 20A of A.

FIG. 20-2 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20E based on the tapping of the remittance request partial remittance partial selection batch settlement button BT21.
In this example, the settlement result information NC12 and the settlement result information NC13 are displayed as the contents of the batch settlement in the notification information display area NTR1 on the notification screen.

The settlement result information NC12 is not limited to, but as an example, based on this remittance request, the user C.I. C is the user A. It is displayed that the remittance request amount "500 yen" by the remittance request to A has been received. Below that, user C.I. It is displayed that there are two unprocessed requests of C as an example, not a limitation.

The settlement result information NC13 is not limited to the third remittance request selected in FIG. 20-1 (the remittance request amount "1,000 yen" sent by the user AA to the user CC). The reminder corresponding to the remittance request) is displayed.

FIG. 20-3 is another example of the display screen of FIG. 20-2.
In FIG. 20-3, the request for the third remittance request (receipt from user CC: 1,000 yen) is selected in the remittance request information NC11, and the remittance request partial remittance partial settlement button BT21 is pressed. When tapped, the terminal 20A requests the server 10 to execute the batch settlement of the selected unprocessed requests. Then, from the server 10, the other user C.I. The batch settlement approval confirmation information for confirming the intention of whether or not to approve the batch settlement is transmitted to the terminal 20C of C, and is displayed on the display unit 24 of the terminal 20C.

In FIG. 20-3, the batch settlement approval confirmation information NC14 is displayed in the notification information display area NTR1 on the notification screen instead of the settlement result information NC12 and the settlement result information NC13.

The batch settlement approval confirmation information NC14 contains the contents of the batch settlement as the user C.I. C is the user A. Based on the receipt of the past remittance request from A, the remittance request amount "1,000 yen" is paid, and the user A. It is displayed that the remittance request amount "500 yen" will be received based on the transmission of this remittance request to A.

Further, in the batch settlement approval confirmation information NC14, the user C.I. C is user A. From A, it is displayed that "500 yen" is paid by subtracting the remittance request amount "500 yen" due to the transmission of this remittance request from the remittance request amount "1,000 yen" due to the receipt of the remittance request.

FIG. 20-4 is a diagram showing an example of a notification screen displayed on the display unit 24 of the terminal 20A based on the tapping of the settlement button BT22 in FIG. 20-3.
In this example, in the notification information display area NTR2 on the notification screen, the settlement result information NC15 is displayed as the content of the batch settlement under the remittance request information NC11.

The settlement result information NC15 is not limited to the user A. A and user C. Since the batch settlement was performed with C, the content of the batch settlement is the amount of the settlement result (in this example, the remittance amount "500 yen" sent by the user AA from the user CC. Received) is displayed.
In addition, under the contents of the batch settlement, User A. The unprocessed request of A is displayed, and below that, a full selection batch settlement button and a partial selection batch settlement button are displayed.
As an example, not a limitation, the unprocessed request displayed in the settlement result information NC15 excludes the third sent remittance request processed this time among the unprocessed requests displayed in the remittance request information NC11 (). (Deleted) 3 remittance requests.

<Processing>
Since the processing executed by each device in this embodiment can be similarly realized by following the processing of FIG. 19-4, illustration and detailed description thereof will be omitted.

<Effect of 22nd Example>
In this embodiment, the first information is the remittance request information regarding the remittance request transmitted from the other user to the proposer user, and the second information is the remittance request already transmitted from the proposer user to the other user. Shows the configuration of sent remittance request information for.
As an example of the effect of the embodiment obtained by such a configuration, the remittance request from the first user to the terminal user and the remittance request sent from the terminal user to the second user are collectively performed. be able to.

Further, in this case, the first process sends money to the other user based on the input to the terminal 20 in which the first display and the second display are displayed, and sends a remittance reminder or a new remittance request to the other user. It is possible to include the processing to be performed.

Further, the other user is one user, and the first process is the remittance request information regarding the remittance request sent from the other user to the proposer user and the remittance sent from the proposer user to the other user. It is also possible to include a process of remittance to the other user or remittance from the other user based on the sent remittance request information regarding the request.
As an example of the effect of the embodiment obtained by such a configuration, the amount of money based on the first information and the second information can be remitted to the first user, or remittance can be received from the first user.

In this case, the first process is a remittance request sent from the proposer user to the other user from the remittance request amount included in the remittance request information related to the remittance request sent from the other user to the proposer user. Send money to the other user after deducting the amount of the remittance request included in the sent remittance request information, or the remittance request included in the sent remittance request information about the remittance request sent from the proposer user to the other user. It is possible to include a process of receiving a remittance from the other user by subtracting the remittance request amount included in the remittance request information regarding the remittance request sent from the other user to the proposer user from the amount.
As an example of the effect of the embodiment obtained by such a configuration, the difference amount can be remitted to the first user, or the remittance can be received from the first user.

Further, in this case, the first process may be executed based on the approval of the other user based on the input to the terminal 20 of the other user.
As an example of the effect of the embodiment obtained by such a configuration, the first process can be executed based on the approval by the first user based on the input to the terminal of the first user. Thereby, as an example, not limited, it is possible to prevent the first process from being executed without the intention of the first user.

<23rd Example>
The 23rd embodiment is an example relating to the processing of a pattern different from the above-mentioned pattern.
The contents described in the 23rd embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

In addition to the above-mentioned pattern, as an example, not a limitation, a pattern of a combination of new processing targets in the table of FIG. 16-1, that is,
-It is also possible to process the pattern of receiving the receipt + remittance request.

The processing of this pattern is the same as the processing of the pattern (a). That is, the process of "receipt + remittance" can be performed.

<Effect of the 23rd example>
In this embodiment, the first information is remittance result information from the other user (not limited, but an example of information regarding remittance from the first user to the terminal user), and the terminal 20 of the proposer user is , The remittance request information regarding the remittance request transmitted from the other user to the proposer user is received by the communication I / F 22, and the third display based on the received remittance request information is displayed on the display unit 24. Then, the terminal 20 of the proposer user executes the remittance process (not limited, but an example of the second process) by the control unit 21 based on the input to the terminal 20 displaying the third display by the proposer user. The configuration to be used is shown.
As an example of the effect of the embodiment obtained by such a configuration, the second process related to remittance can be performed based on the input to the terminal displaying the third display by the user of the terminal.

<24th Example>
The 24th embodiment is an example relating to the processing of a pattern different from the above-mentioned pattern.
The contents described in the 24th embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

In addition to the patterns described above, as an example, not a limitation, a pattern of combinations of unprocessed requests in the table of FIG. 16-1, that is,
-It is also possible to process the pattern of received remittance request + sent remittance request.

The processing of this pattern is the same as the processing of the pattern (e). That is, either "remittance + remittance reminding" or "[remittance + receipt] (amount can be deducted)" can be processed.
In addition, when processing "[Remittance + Receiving] (amount can be deducted)", the approval of the other user may be required, and the approval of the other user may or may not be obtained. You may.

<Effect of 24th Example>
In this embodiment, the second information is the received remittance request information regarding the remittance request received from the other user, and based on the fact that the remittance request is received from the other user, the proposer user to the other user. The fourth display based on the sent remittance request information regarding the sent remittance request is displayed on the display unit 24. Then, based on the input to the terminal 20 in which the second display and the fourth display are displayed by the proposer user, the control unit 21 performs a third process regarding remittance, receipt, or remittance request (remittance reminder). Shows the configuration to be performed.
As an example of the effect of the embodiment obtained by such a configuration, the remittance is related to, the remittance is received, or the remittance is made based on the input by the terminal user to the terminal in which the second display and the fourth display are displayed. The third process related to the request can be performed by the control unit.

Further, in this case, the third process includes a process of remittance to the other user and a remittance request or a remittance reminder to the other user based on the input to the second display and the fourth display. Can be done.
As an example of the effect of the embodiment obtained by such a configuration, the remittance to the second user and the remittance request to the second user can be performed together.

Further, in this embodiment, the other user is one user, and in the third process, the amount of money based on the received remittance request information and the sent remittance request information is remitted to the other user, or from the other user. The configuration including the process of remittance is shown.
As an example of the effect of the embodiment obtained by such a configuration, the amount of money based on the second information and the fourth information can be remitted to the second user or received from the second user.

In this case, the third process remits the amount of the remittance request amount included in the received remittance request information minus the remittance request amount included in the sent remittance request information to the other user, or remittance sent. It is possible to include the process of remittance from the other user in the amount obtained by subtracting the remittance request amount included in the received remittance request information from the remittance request amount included in the request information.
As an example of the effect of the embodiment obtained by such a configuration, the difference amount can be remitted to the second user or received from the second user.

Further, in this case, the third process can be executed based on the approval by the other user based on the 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 approval by the second user based on the input to the terminal of the second user. As a result, it is possible to prevent the third process from being executed without the intention of the second user, as an example but not a limitation.

<25th Example>
The 25th embodiment is an example relating to the processing of a pattern different from the above-mentioned pattern.
The contents described in the 25th embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

As an example, not limited to, "receipt" in the new processing target in the table of FIG. 16-1 can be set as "receipt refusal".
"Remittance refusal" is to prevent the remittance destination user from receiving the remittance amount.

in this case,
-Rejection + Received remittance request-Rejection + Sent remittance request-Rejection + Received remittance request + Sent remittance request can be processed.

In the pattern of refusal of receipt + received remittance request, only remittance processing can be performed.
In the pattern of refusal of receipt + sent remittance request, only the process of sending a remittance reminder (or a new remittance request) can be performed.
In the pattern of refusal of receipt + received remittance request + sent remittance request, [remittance + receipt] (amount can be deducted) can be processed.

<26th Example>
The 26th embodiment is an example relating to a method for displaying remittance request information.
The contents described in the 26th embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

<Display screen>
FIG. 21-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 not limited, but as an example, User A. This is a payment application notification screen displayed on the display unit 24 of the terminal 20A of A.
In the notification information display area NTR2 on the notification screen, the remittance result information NC16 is displayed as the content related to the receipt (receipt) of the remittance.
The remittance result information NC16 is not limited to the user A. A is user B. The contents corresponding to the receipt of the remittance amount "1,000 yen" sent (received) from B are displayed.

Below that, there is a list of remittance requests that have not been processed by the user (user AA in this example) who was remitted at the time the remittance was received. At the upper right of the remittance request list display, a remittance request history sort button STB2 for changing the display order of unprocessed remittance requests is displayed. Other display modes are the same as the remittance result information NC1.

When the remittance request history sort button STB2 is touched, the sort selection area for selecting the sort order is displayed from the bottom of the screen as an example, not limited to the above.
Based on the user operation for the sort selection area, the display order of unprocessed remittance requests is not limited, but as an example, in ascending / descending order according to the date order in which the remittance request was sent / received, the remittance request amount of the remittance request, etc. It can be rearranged and displayed.

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

FIG. 21-2 shows, as an example, not a limitation, an example of a display screen in which the unprocessed remittance requests of the remittance result information NC16 are sorted in descending order by the remittance request amount based on the user operation for the sort selection area. It is a figure which shows.

In FIG. 21-1, the unprocessed remittance requests of the remittance result information NC16 are arranged in ascending order regarding the date, but in FIG. 21-2, they are arranged in descending order regarding the remittance request amount.

When the payment deadline is set for the remittance request, the remittance request may or may not be displayed in the order in which the payment deadline is approaching, as an example, not limited. Setting the payment deadline includes not only payment between individuals (CtoC) but also setting the repayment deadline of a loan / loan (CtoB) from a financial institution as an example, not limited.

Further, the remittance request in which the user who requested the remittance and the user other than the user who requested the remittance are related to the remittance request amount or the reason may be preferentially displayed. As an example, not a limitation, when another user is included as a member of the Dutch bill.

In addition, it has been said that unprocessed remittance requests are displayed in the remittance result information and remittance request information, but the present invention is not limited to this. As an example, not limited to, the processed remittance request may or may not be displayed mixed with the unprocessed remittance request in a different display mode such as gray out.

<Effect of the 26th example>
In this embodiment, the terminal 20 of the proposer user has remittance request information (not limited to, but not limited to, transmitted from the second user to the terminal user) regarding the received remittance request received by the proposer user from the other user. (An example of the fourth information regarding the remittance request), or the remittance request information regarding the sent remittance request sent by the proposer user to the other user (not limited, but regarding the remittance request sent from the terminal user to the second user). The fourth display based on (an example of the fourth information) is displayed on the display unit 24. The terminal 20 of the proposer's user shows a configuration in which the second display and the fourth display are displayed on the display unit 24 in the order based on the above-mentioned second information and the above-mentioned fourth information.
As an example of the effect of the embodiment obtained by such a configuration, the second display and the fourth display can be displayed in an appropriate order based on the second information and the fourth information.

Further, in this embodiment, the above-mentioned second information and fourth information are information on the date when the remittance request is transmitted / received (not limited to an example of information on the date), or the date and time when the remittance request is transmitted / received. The order in which the second and fourth displays are displayed, including information about (but not limited to, an example of information about a date and time), indicates a configuration that is determined based on this date or information about the date and time.
As an example of the effect of the embodiment obtained by such a configuration, by displaying the second display and the fourth display in the order based on the date and time or the information on the date, it is possible to realize a display that is intuitively easy for the user to understand. Can be done.

Further, in this embodiment, the above-mentioned second information and fourth information include information on the amount of money to be remitted (an example of information on the amount of money, not a limitation), and the order in which the second display and the fourth display are displayed. Shows a configuration that is determined based on information about this amount.
As an example of the effect of the embodiment obtained by such a configuration, by displaying the second display and the fourth display in the order based on the information on the amount of money, it is possible to realize a display that is intuitively easy for the user to understand. ..

Further, in this case, the information regarding the amount of the remittance request may include information regarding the payment deadline as an example, not limited to, in addition to the remittance request amount.
As an example of the effect of the embodiment obtained by such a configuration, by displaying the second display and the fourth display in the order based on the information regarding the payment deadline, it is possible to realize a display that is intuitively easy for the user to understand. can.

<27th Example>
The 27th embodiment is an example when a chat service (chat application) is applied.
The contents described in the 27th embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

<Display screen>
In the following, User A., who is both a user of the messaging application and a user of the payment application. A and user B. B and user C. It is assumed that C and C all belong to group X and are registered as friends.

FIG. 22-1 is a diagram showing an example of a screen displayed on the display unit 24 of the terminals 20A to 20C in this embodiment. This screen is not limited, but as an example, is a group chat (in this example, the chat of "group X") screen of the messaging application displayed on the display unit 24 of the terminal 20 of each user.
In the center of the top of the screen, the characters "Messing App" are displayed as the name of the messaging application. Further, on the upper right side of the screen, an icon image and a user name in the messaging application of the user of the terminal 20 are displayed.

Further, below that, a current position display area indicating the current position in the messaging application is configured, and in this example, "group X" indicating that the current position is a group chat of "group X" of the messaging application. Character is displayed in the current position display area.

Below the current position display area, a message display area, which is a display area for group chat messages (contents), is displayed. The message display areas in the display units 24 of the terminals 20A to 20C are designated as the message display area MSG1 to the message display area MSG3, respectively.
In the message display area, the message sent from the own terminal is displayed as a balloon from the right side, and the message sent from other than the own terminal is displayed as a balloon from the left side together with the sender's icon.

As an example, not a limitation, User B. B is the user A. As an example, not limited to A, consider a case where a remittance request with a remittance request amount of "1,000 yen" is made by the remittance request transmission function in the messaging application.

Then, the remittance request information MC1 is displayed in the message display area MSG1 of the terminal 20A.
The remittance request information MC1 is not limited to the user A. A is user B. The contents corresponding to the remittance request of the remittance request amount "1,000 yen" received from B are displayed. Below that, a remittance request remittance button and a remittance request refusal button are displayed.
Below that, at the time of receiving the remittance request, between the user who sent the remittance request (user BB in this example) and the user who received the remittance request (user AA in this example) are not yet. The remittance request that is being processed is listed.
In addition, at the bottom of the remittance request information MC1, a remittance request remittance all-selection batch settlement button indicating "all remittances and remittances" is displayed to execute the remittance by this remittance request and all-selection batch settlement. Has been done.

Further, the remittance request information MC2 is displayed in the message display area MSG2 of the terminal 20B.
The remittance request information MC2 is not limited to the user B. B is user A. The contents corresponding to the remittance request of the remittance request amount "1,000 yen" sent to A are displayed. Below that, the remittance request remittance button and the remittance request refusal button are disabled and displayed in a grayed out display mode.
Below that, at the time of receiving the remittance request, between the user who sent the remittance request (user BB in this example) and the user who received the remittance request (user AA in this example) are not yet. The remittance request that is being processed is listed.
Further, at the bottom of the remittance request information MC2, an all-selection batch settlement button indicating "all-selection batch settlement" is displayed for executing the all-selection batch settlement.

The remittance request information MC3 is displayed in the message display area MSG3 of the terminal 20C.
The remittance request information MC3 is not limited to the user B. B is user A. The contents corresponding to the remittance request of the remittance request amount "1,000 yen" sent to A are displayed. Below that, the remittance request remittance button and the remittance request refusal button are disabled and displayed in a grayed out display mode.
Below that is a list of unprocessed remittance requests between the user who sent the remittance request (user BB in this example) and the user who received the remittance request (user AA in this example). The display is not displayed because you are not a party to these remittance requests.

It should be noted that unprocessed remittance requests other than the parties may or may not be displayed in the remittance request information.

FIG. 22-2 shows, as an example, not a limitation, that the remittance request information MC1 is swiped from right to left (swipe operation) (operation of sliding the finger while touching the screen) by the user operation. It is a figure which shows an example of the screen which is displayed on the display part 24 of the terminal 20A based on.
In FIG. 22-2, as an example, not a limitation, the settlement content confirmation area ACR9 is raised and displayed from the lower part of the display unit 24 of the terminal 20A of FIG. 22-1.

At the top of the settlement content confirmation area ACR9, the user A. A is user B. A remittance request is received from B, and user B. A display indicating that two unprocessed remittance requests (unsettled requests) remain with B is displayed.

Further, in the lower part of the settlement content confirmation area ACR9, the user A. A is user B. Remittance request with B When performing remittance all-selection batch settlement, the remittance request amount "1,000 yen" received this time, the previously received remittance request amount "3,500 yen" and " A confirmation display is displayed, which means that you will pay "5,000 yen", which is the sum of "500 yen". Below that, there is a remittance request remittance all-selection batch settlement button BT23 that indicates "OK" to execute the remittance request remittance all-selection batch settlement, and a "cancel" to cancel the remittance request remittance all-selection batch settlement. Is displayed with the cancel button indicated.

Even when the remittance request information MC1 remittance request remittance all selection batch settlement button is tapped, the settlement content confirmation area ACR9 may or may not be displayed.

FIG. 22-3 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20A when the remittance request remittance all selection batch settlement button BT23 is tapped in the settlement content confirmation area ACR9 of FIG. 22-2. be.
In FIG. 22-3, the remittance result information MC4 is displayed in the message display area MSG1 based on the remittance result of the remittance processing by the remittance request and the remittance processing by the all-selection batch settlement under the remittance request information MC1. ing.

At the top of the remittance result information MC4, the user A. A is user B. It is displayed that the remittance request amount "1,000 yen" has been paid (sent) to B, and "4,000 yen" has been paid (sent) as the amount of the batch settlement of the unprocessed remittance request.

At the bottom of the remittance result information MC4, the user A. In A, it is displayed that the remittance amount is "5,000 yen", which is the sum of the remittance request amount "1,000 yen" and the lump sum settlement amount "4,000 yen".

The display corresponding to the remittance result information MC4 may or may not be displayed on terminals 20 other than the terminal 20A and the terminal 20B.
Further, the terminals 20A and the terminals 20 other than the terminals 20B, which are the parties concerned, may or may not display only the remittance result corresponding to the lower part of the remittance result information MC4.

FIG. 22-4 is a diagram showing an example of a screen when the unprocessed remittance request is hidden in the remittance request information MC1.
As an example, not a limitation, when the unprocessed request non-display button BT24 indicated by a cross in the remittance request information MC1 is tapped by the user, the unprocessed request display cancellation confirmation area DRR1 is set from the lower part of the message display area MSG1. It is displayed up.

In the unprocessed request display cancellation confirmation area DRR1, when a remittance or a remittance request is made, the remittance request information or the remittance result information is sent to the user (for example, user BB) who made the remittance request (remittance). The unprocessed request display cancel button indicated by "OK" for not displaying the list of unprocessed remittance requests and the unprocessed request display approval button indicated by "Cancel" for continuing the list display are displayed. There is.

As an example, not a limitation, when the unprocessed request display cancellation button in the unprocessed request display cancellation confirmation area DRR1 is tapped by the user, this user (for example, user B. The list of unprocessed remittance requests with B) disappears.

Similarly, the button for hiding the unprocessed request of the remittance request information MC2 is the user B. When tapped by B and the unprocessed request display cancel button in the unprocessed request display cancellation confirmation area is subsequently tapped, the user A. The list of unprocessed remittance requests with A disappears.

If the unprocessed request display cancel button in the unprocessed request display cancellation confirmation area is tapped, a list of unprocessed remittance requests will be included in the remittance request information and remittance result information received thereafter with all users. May or may not be hidden.

That is, in this embodiment, the unprocessed request is configured to be hidden based on the input of the user of the terminal 20 to the input unit.

In addition, instead of doing as described above, as described above, it may or may not be possible to set the display / non-display of unprocessed requests on a setting screen (not shown) or the like. good.

<Effect of 27th Example>
In this embodiment, the terminal 20 of the proposer user is a chat room including at least the proposer user (not limited to an example of the terminal user and the other user (not limited to an example of the first user)). (An example of a chat room, not a limitation) is displayed on the display unit 24, and the first display and the second display indicate the configuration displayed in this talk room.
As an example of the effect of the embodiment obtained by such a configuration, the first information and the second information can be notified to the user of the terminal in an easy-to-understand form of display in a chat room.

Further, in this case, the second display displayed in the talk room can be hidden based on the input to the terminal 20 by the user of the proposer.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to secure a wide space in the display area.

Further, in this case, the talk room includes a user other than the party (not limited to an example of the third user), and the second display is displayed in the talk room displayed on the terminal 20 of the user other than the party. You can also do it.
As an example of the effect of the embodiment obtained by such a configuration, it is based on the second information regarding the remittance request sent from the second user to the user of the terminal or the remittance request sent from the user of the terminal to the second user. The second display, that is, information about the user of the party to the remittance can be prevented from being viewed by a third user who is a user other than the party.

Further, in this case, the talk room displayed on the terminal 20 of the user other than the party is different from the second display, the remittance request information regarding the remittance request sent from the user other than this party, or the user other than this party. Includes a fifth display based on remittance request information regarding the remittance request sent. Then, the fifth display can be prevented from being displayed in the talk room displayed on the terminal 20 of the proposer user.
As an example of the effect of the embodiment obtained by such a configuration, a fifth information based on a fifth information regarding a remittance request sent from a third user or a remittance request sent to a third user, which is different from the second display. 5 Display, that is, the information on which the third user is a party to the remittance can be prevented from being viewed by the user of the terminal.

Further, in this case, the first display can be prevented from being displayed in the talk room displayed on the terminal 20 of a user other than the party concerned.
As an example of the effect of the embodiment obtained by such a configuration, the first display based on the first information regarding the remittance from the first user to the user of the terminal or the remittance request transmitted from the first user to the user of the terminal. That is, information about the user of the party to the remittance can be prevented from being viewed by the third user.

Further, in the present embodiment, the first display and the second display are displayed on the display unit 24 by the messaging application installed on the terminal 20 of the proposer user, and the messaging application is included in the program according to the present disclosure. The configuration is shown.
As an example of the effect of the embodiment obtained by such a configuration, the first display and the second display can be displayed on the display unit of the terminal by the application installed on the terminal.

<Others>
In the above embodiment, received remittance request information and sent remittance request information are exemplified as unprocessed information regarding the remittance request.

However, even if this information is replaced with the remittance reminder information, the same processing as in the above embodiment can be applied. That is, it is possible to apply the received remittance reminder information and the sent remittance reminder information as unprocessed information regarding the remittance request without distinguishing between the remittance request and the remittance reminder.
This is because remittance requests and remittance reminders can be treated as synonymous.

In addition, the remittance request information and the remittance reminder information can be arbitrarily combined. That is, the following four combinations can be applied as the combination of the received information and the transmitted information.

(1) First combination-Received: Remittance request information-Sent: Remittance request information This combination is the combination described in the above embodiment.

(2) Second combination-Received: Remittance request information-Sent: Remittance reminder information

(3) Third combination ・ Received: Remittance reminder information ・ Sent: Remittance request information

(4) Fourth combination-Received: Remittance reminder information-Sent: Remittance reminder information

1 Communication system 10 Servers 20 Terminals 30 Networks

Claims (34)

A program executed by a terminal
Receiving the first information regarding the remittance from the first user to the user of the terminal or the remittance request transmitted from the first user to the user of the terminal by the communication unit of the terminal.
The first display based on the first information is displayed on the display unit of the terminal, and the remittance request transmitted from the second user to the user of the terminal based on the reception of the first information, or the user of the terminal. The second display based on the second information regarding the remittance request sent from the second user to the second user is displayed on the display unit.
Control of the terminal for the first processing regarding remittance, receipt of remittance, or request for remittance, based on the input to the terminal on which the first display and the second display are displayed by the user of the terminal. What is done by the unit is performed by the terminal. The program according to claim 1.
The first information is information regarding remittance from the first user to the user of the terminal.
The second information is information regarding a remittance request transmitted from the second user to the user of the terminal.
The first process includes a process of remittance to the second user based on an input to the terminal on which the second display is displayed. The program according to claim 2.
In the first process, after the first display is displayed on the display unit, remittance is sent from the first user to the user of the terminal based on the input to the terminal on which the first display is displayed. Includes processing to receive the amount. The program according to claim 1.
The first information is information regarding remittance from the first user to the user of the terminal.
The second information is information regarding a remittance request transmitted from the user of the terminal to the second user. The program according to claim 4.
The first process includes a process of transmitting a remittance request to the second user based on an input to the terminal on which the second display is displayed. The program according to claim 1.
The second user is the first user.
The first information is information regarding a remittance request transmitted from the first user to the user of the terminal.
The second information is information regarding a remittance request transmitted from the user of the terminal to the second user.
The first process includes a process of remittance of an amount based on the first information and the second information to the first user, or remittance from the first user. The program according to claim 6.
The first information includes information on the first amount of money.
The second information includes information on the second amount of money.
In the first process, the amount obtained by subtracting the second amount from the first amount is remitted to the first user, or the amount obtained by subtracting the first amount from the second amount is remitted from the first user. Includes processing. The program according to claim 6 or 7.
The first process is executed based on the approval by the first user based on the input to the terminal of the first user. The program according to claim 1.
The first information is information regarding a remittance request transmitted from the first user to the user of the terminal.
The second information is information regarding a remittance request transmitted from the second user to the user of the terminal.
The first process includes a process of remittance to the first user and the second user based on an input to the terminal displaying the first display and the second display. The program according to claim 9.
The second user is the first user.
The first process includes a process of remittance to the first user based on an input to the terminal displaying the first display and the second display. The program according to claim 1.
The first information is information regarding a remittance request transmitted from the first user to the user of the terminal.
The second information is information regarding a remittance request transmitted from the user of the terminal to the second user. The program according to claim 11.
The first process includes a process of remittance to the first user and a remittance request to the second user based on the input to the terminal in which the first display and the second display are displayed. The program according to claim 11.
The second user is the first user.
The first process includes a process of remittance of an amount based on the first information and the second information to the first user, or remittance from the first user. The program according to claim 13.
The first information includes information on the first amount of money.
The second information includes information on the second amount of money.
In the first process, the amount obtained by subtracting the second amount from the first amount is remitted to the first user, or the amount obtained by subtracting the first amount from the second amount is remitted from the first user. Includes processing. The program according to claim 13 or claim 14.
The first process is executed based on the approval by the first user based on the input to the terminal of the first user. The program according to claim 1.
The first information is information regarding remittance from the first user to the user of the terminal.
Receiving the third information regarding the remittance request transmitted from the first user to the user of the terminal by the communication unit, and
Displaying the third display based on the third information on the display unit and
Based on the input to the terminal displaying the third display by the user of the terminal, the terminal executes the second process related to the remittance by the control unit. The program according to claim 1.
The second information is information regarding a remittance request transmitted from the second user to the user of the terminal.
Based on the reception of the first information, the display unit displays the fourth display based on the fourth information regarding the remittance request transmitted from the user of the terminal to the second user.
Based on the input to the terminal on which the second display and the fourth display are displayed by the user of the terminal, the control unit performs a third process regarding remittance, receipt of remittance, or request for remittance. What you do is performed by the terminal. The program according to claim 17.
The third process includes a process of remittance to the second user and a remittance request to the second user based on the input to the second display and the fourth display. The program according to claim 17.
The second user is the first user.
The third process includes a process of remittance of an amount based on the second information and the fourth information to the second user, or remittance from the second user. The program according to claim 19.
The second information includes information on the second amount of money.
The fourth information includes information on the fourth amount of money, and includes information on the fourth amount.
In the third process, the amount obtained by subtracting the fourth amount from the second amount is remitted to the second user, or the amount obtained by subtracting the second amount from the fourth amount is remitted from the second user. Includes processing. The program according to claim 19 or claim 20.
The third process is executed based on the approval by the second user based on the input to the terminal of the second user. The program according to claim 1.
A second based on the fourth information regarding the remittance request transmitted from the second user to the user of the terminal or the remittance request transmitted from the user of the terminal to the second user based on the reception of the first information. 4 Displaying the display on the display unit and
Displaying the second display and the fourth display on the display unit is executed on the terminal in the order based on the second information and the fourth information. The program according to claim 22.
The second information and the fourth information include information regarding a date or a date and time.
The order is determined based on the information on the date or the information on the date and time. 22 or the program according to claim 23.
The second information and the fourth information include information on the amount of money.
The order is determined based on the information regarding the amount. 24. The program according to claim 24.
The information regarding the amount thereof includes information regarding the payment deadline. The program according to any one of claims 1 to 25.
Displaying a chat room including at least a user of the terminal and the first user on the display unit is executed on the terminal.
The first display and the second display are displayed in the chat room. The program according to claim 26.
It is executed by the terminal to hide the second display displayed in the chat room based on the input to the terminal by the user of the terminal. The program according to claim 26.
The chat room includes a third user different from the first user and the second user.
The second display is not displayed in the chat room displayed on the terminal of the third user. 28. The program according to claim 28.
The chat room displayed on the terminal of the third user is different from the second display, and is related to a remittance request sent from the third user or a fifth information regarding a remittance request sent to the third user. Including the 5th indication based on
The fifth display is not displayed in the chat room displayed on the terminal. 28 or 29 of the program.
The first display is not displayed in the chat room displayed on the terminal of the third user. The program according to any one of claims 1 to 30.
The first display and the second display are displayed on the display unit by the application installed on the terminal.
The application is included in the program. Information processing method for terminals
Receiving the first information regarding the remittance from the first user to the user of the terminal or the remittance request transmitted from the first user to the user of the terminal by the communication unit of the terminal.
The first display based on the first information is displayed on the display unit of the terminal, and the remittance request transmitted from the second user to the user of the terminal based on the reception of the first information, or the user of the terminal. The second display based on the second information regarding the remittance request sent from the second user to the second user is displayed on the display unit.
Control of the terminal for the first processing regarding remittance, receipt of remittance, or request for remittance, based on the input to the terminal on which the first display and the second display are displayed by the user of the terminal. Including what to do by the department. It ’s a terminal,
A communication unit that receives the first information regarding the remittance from the first user to the user of the terminal or the remittance request transmitted from the first user to the user of the terminal.
The first display based on the first information is displayed, and based on the reception of the first information, the remittance request sent from the second user to the user of the terminal, or transmitted from the user of the terminal to the second user. A display unit that displays the second display based on the second information regarding the remittance request made, and
A control unit that performs a first process regarding remittance, receipt of remittance, or request for remittance based on an input to the terminal on which the first display and the second display are displayed by the user of the terminal. To prepare for. It ’s a terminal,
It is equipped with a processor that reads a program stored in memory and executes processing based on the program.
The processor
Receiving the first information regarding the remittance from the first user to the user of the terminal or the remittance request transmitted from the first user to the user of the terminal by the communication unit of the terminal.
The first display based on the first information is displayed on the display unit of the terminal, and the remittance request transmitted from the second user to the user of the terminal based on the reception of the first information, or the user of the terminal. The second display based on the second information regarding the remittance request sent from the second user to the second user is displayed on the display unit.
Based on the input to the terminal on which the first display and the second display are displayed by the user of the terminal, the first processing regarding remittance, receipt of remittance, or request for remittance is performed. Execute.

Images