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

Description

This disclosure relates to programs, information processing methods, terminals, etc.

Recently, services that enable the management of electronic currency (electronic money) of a terminal or a terminal user, as well as the sending and receiving of money, using applications that can be executed on terminals such as smartphones, are becoming more widespread. For example, Patent Literature 1 discloses a technology for settling the purchase amount of a product.

JP 2002-176671 A

According to a first aspect of the present invention, a program executed by the terminal receives first information regarding a remittance request by a first user through a communication unit of the terminal, displays a first display based on the first information on a display unit of the terminal, displays a second display based on the remittance request and different from the first display on the display unit, and executes a remittance process for a remittance from the user of the terminal to the first user based on the remittance request based on input by the user of the terminal to the second display displayed on the display unit.
According to a second aspect of the present invention, an information processing method of a terminal includes receiving first information regarding a remittance request by a first user by a communication unit of the terminal, displaying a first display based on the first information on a display unit of the terminal, displaying a second display on the display unit that is different from the first display and based on the remittance request, and executing a remittance process for a remittance from the user of the terminal to the first user based on the remittance request based on input by the user of the terminal to the second display displayed on the display unit by a control unit of the terminal.
According to a third aspect of the present invention, the terminal comprises a communication unit that receives first information regarding a remittance request by a first user, a display unit that displays a first display based on the first information and a second display different from the first display based on the remittance request, and a control unit that executes a remittance process for a remittance from the user of the terminal to the first user based on the remittance request based on an input to the second display displayed on the display unit.
According to a fourth aspect of the present invention, the terminal includes a processor that reads a program stored in a memory and executes processing based on the program, and the processor executes the following steps: receiving first information regarding a remittance request by a first user via a communication unit of the terminal; displaying a first display based on the first information on a display unit of the terminal; displaying a second display based on the remittance request and different from the first display on the display unit; and performing a remittance process for a remittance from the user of the terminal to the first user based on the remittance request based on input by the user of the terminal to the second display displayed on the display unit.
According to a fifth aspect of the present invention, a program executed by a server communicating with a terminal includes transmitting first information relating to a remittance request by a first user to the terminal by a communication unit of the server, transmitting second information based on the remittance request to the terminal by the communication unit, and executing a remittance process for a remittance from the user of the terminal to the first user based on the remittance request by a control unit of the server based on an input to a second display based on the second information displayed on a display unit of the terminal.

FIG. 1 illustrates an example of a configuration of a communication system according to an embodiment. FIG. 4 is a diagram showing an example of functions realized by a control unit of the server according to the first embodiment; FIG. 4 is a diagram showing an example of information stored in a storage unit of the server according to the first embodiment. FIG. 4 is a diagram showing an example of user registration data according to the first embodiment. FIG. 4 is a diagram showing an example of a user management database according to the first embodiment. FIG. 11 is a diagram showing an example of remittance request management data according to the first embodiment. FIG. 4 is a diagram showing an example of functions realized by a control unit of the terminal according to the first embodiment. FIG. 4 is a diagram showing an example of information stored in a storage unit of the terminal according to the first embodiment. FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. FIG. 4 is a diagram showing an example of a display screen of the terminal according to the first embodiment. 6 is a flowchart showing an example of a processing flow of the terminal and the server according to the first embodiment. 6 is a flowchart showing an example of a processing flow of the terminal and the server according to the first embodiment. 10 is a flowchart showing an example of a processing flow of a terminal and a server according to a first modified example. FIG. 13 is a diagram showing an example of remittance request management data according to the second embodiment. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second embodiment. 10 is a flowchart showing an example of a processing flow of a terminal and a server according to a second embodiment. 10 is a flowchart showing an example of a processing flow of a terminal and a server according to a second embodiment. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second modified example. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second modified example. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second modified example. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second modified example. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second modified example. FIG. 11 is a diagram showing an example of a display screen of a terminal according to a second modified example. FIG. 13 is a diagram showing an example of a timing chart according to the third embodiment. FIG. 13 is a diagram showing an example of a timing chart according to a third modified example. 13 is a flowchart showing an example of a processing flow of a terminal and a server according to the fourth embodiment. FIG. 13 is a diagram showing an example of remittance reminding condition data according to the fourth embodiment. FIG. 13 is a diagram showing an example of a display screen of a terminal according to the fourth embodiment. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fourth embodiment. 13 is a flowchart showing an example of a processing flow of a terminal and a server according to a fourth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth embodiment. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth embodiment. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth embodiment. 13 is a flowchart showing an example of a processing flow of a terminal and a server according to the fifth embodiment. 13 is a flowchart showing an example of a processing flow of a terminal and a server according to the fifth embodiment. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth modified example. FIG. 13 is a diagram showing an example of a table relating to a method for displaying a remittance request message or a remittance reminder message according to the fifth modified example. 13 is a flowchart showing an example of a processing flow of a terminal and a server according to a fifth modified example. 13 is a flowchart showing an example of a processing flow of a terminal and a server according to a fifth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a fifth modified example. 23 is a flowchart showing an example of a processing flow of a terminal and a server according to the sixth embodiment. 23 is a flowchart showing an example of a processing flow of a terminal and a server according to the sixth embodiment. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a sixth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a sixth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a sixth modified example. 13 is a flowchart showing an example of a processing flow of a terminal and a server according to a sixth modified example. 13 is a flowchart showing an example of a processing flow of a terminal and a server according to a sixth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a sixth modified example. FIG. 13 is a diagram showing an example of a display screen of a terminal according to a sixth modified example. 23 is a flowchart showing an example of a processing flow of a terminal and a server according to the seventh embodiment; 23 is a flowchart showing an example of a processing flow of a terminal and a server according to the seventh embodiment. FIG. 23 is a diagram showing an example of a table relating to a display mode of information related to a remittance request in the seventh modified example. 13 is a flowchart showing an example of a processing flow of a terminal and a server according to a seventh modified example. 13 is a flowchart showing an example of a processing flow of a terminal and a server according to a seventh modified example. FIG. 23 is a diagram showing an example of remittance request management data according to the eighth embodiment. FIG. 23 is a diagram showing an example of a remittance reminder determination table according to the eighth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the eighth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the eighth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the eighth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the eighth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the eighth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the eighth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the eighth embodiment. 23 is a flowchart showing an example of a processing flow of a terminal and a server according to the eighth embodiment; FIG. 23 is a diagram showing an example of reminder stop management data according to the eighth modified example. FIG. 23 is a diagram showing an example of a remittance reminder determination table according to the ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to the ninth embodiment.

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

An embodiment for implementing the program etc. disclosed herein will be described with reference to the drawings.

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

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

The server 10 has the function of providing payment services and messaging services to the terminals 20 owned by users via the network 30. The server 10 can also be expressed as a payment management (messaging management) server, a payment service (messaging service) server, etc.

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

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

The network 30 serves to connect one or more terminals 20 and one or more servers 10. In other words, the network 30 refers to a communication network that provides a connection path so that the above-mentioned various devices can transmit and receive data after being connected.
The number of servers 10 and the number of terminals 20 connected to the network 30 are not limited.

One or more portions of network 30 may or may not be wired or wireless. Network 30 may include, by way of example and not limitation, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a cellular network, integrated service digital networks (ISDN), wireless LAN, long term evolution (LTE), code division multiple access (CDMA), Bluetooth, satellite communications, or the like, or a combination of two or more thereof. Network 30 may include one or more networks 30.

The server 10 (not limited to, but an example of a server, information processing device, or information management device) has a function of providing a predetermined service (such as a payment service in this embodiment) to the terminal 20. The server 10 may be any device that is an information processing device that can realize the functions described in each embodiment. The server 10 includes, not limited to, but an example of a server device, a computer (not limited to, but an example of a desktop, laptop, tablet, etc.), a media computer platform (not limited to, but an example of a cable or satellite set-top box, digital video recorder, etc.), a handheld computer device (not limited to, but an example of a PDA, email client, etc.), or other types of computers or communication platforms. The server 10 may also be expressed as an information processing device. When there is no need 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.

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

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

The communication I/F 22 transmits and receives various data via the network 30. The communication may be performed either wired or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F 22 has a function of performing communication with various devices such as the server 10 via the network 30. The communication I/F 22 transmits various data to various devices such as the server 10 according to instructions from the control unit 21. The communication I/F 22 also receives various data transmitted from various devices such as the server 10 and transmits it to the control unit 21. The communication I/F 22 may also be simply referred to as a communication unit. When the communication I/F 22 is configured with a physically structured circuit, it may also be referred to as a communication circuit.

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

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

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

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

The display unit 24 is realized by any one of all types of devices or a combination thereof that can display according to the display data written to the frame buffer. Examples of the display unit 24 include, but are not limited to, touch panels, touch displays, monitors (for example, but not limited to, liquid crystal displays and organic electroluminescence displays (OELDs)), head mounted displays (HDMs), projection mapping, holograms, and devices that can display images, text information, etc. in air (which may or may not be a vacuum). Note that these display units 24 may or may not be capable of displaying display data in 3D.

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

If the input/output unit 23 is a touch panel, the input/output unit 23 and the display unit 24 may be arranged facing each other and have approximately 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 and not limitation, a clock that uses a crystal oscillator. The clock unit 29A can also be expressed as a timekeeping unit or a time information detection unit, for example and not limitation.

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

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

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

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

The inertial measurement unit has an inertial sensor that detects information required to calculate the position of the terminal 20 by inertial navigation calculation. Examples of inertial sensors include, but are not limited to, a three-axis acceleration sensor and a three-axis gyro sensor, and output the acceleration detected by the acceleration sensor and the angular velocity detected by the gyro sensor as information for position calculation.

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

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

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

The control unit 21 may include, by way of example and not limitation, a central processing unit (CPU), a microprocessor, a processor core, a multiprocessor, an application-specific integrated circuit (ASIC), and a field programmable gate array (FPGA).

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

The terminal 20 stores the program P in the memory unit 28, and by executing this program P, the control unit 21 executes the processing of each unit included in the control unit 21. In other words, the program P stored in the memory unit 28 causes the terminal 20 to realize each function executed by the control unit 21. Furthermore, this program P may or may not be expressed as a program module.

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

The control unit 11 has circuitry that is physically structured to execute the functions realized by the code or instructions contained in the program, and is realized, for example and not by way of limitation, by a data processing device built into hardware.

The control unit 11 is typically a central processing unit (CPU), but may also be a microprocessor, a processor core, a multiprocessor, an ASIC, or an FPGA, or may not be such a unit. In this 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 operation of the server 10. The storage unit 15 is realized by various storage media such as a HDD, SSD, and flash memory. However, in this disclosure, the storage unit 15 is not limited to these. Furthermore, the storage unit 15 may or may not be expressed as a memory.

The communication I/F 14 transmits and receives various data via the network 30. The communication may be performed either wired or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F 14 has a function of performing communication with various devices such as the terminal 20 via the network 30. The communication I/F 14 transmits various data to various devices such as the terminal 20 according to instructions from the control unit 11. The communication I/F 14 also receives various data transmitted from various devices such as the terminal 20 and transmits it to the control unit 11. The communication I/F 14 may also be simply referred to as a communication unit. When the communication I/F 14 is composed of a physically structured circuit, it may also be referred to as a communication circuit.

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

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

In the first embodiment, the input/output unit 12 is equipped with a display unit 13.

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

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

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

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

The control unit 21 of the terminal 20 and/or the control unit 11 of the server 10 may or may not realize each process by a CPU having a control circuit, but may also realize each process by a logic circuit (hardware) formed in an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)) or a dedicated circuit. These circuits may or may not be realized by one or more integrated circuits, and the multiple processes shown in each embodiment may or may not be realized by one integrated circuit. In addition, LSIs may be called VLSIs, super LSIs, ultra LSIs, etc. depending on the degree of integration. Therefore, the control unit 21 may or may not be expressed as a control circuit.
The same applies to other devices.

In addition, the program P (which may be, for example and not by way of limitation, a software program, computer program, or program module) of each embodiment of the present disclosure may or may not be provided in a state stored in a computer-readable storage medium. The storage medium is capable of storing the program P in a "non-transitory tangible medium." The program P may or may not be for realizing part of the functions of each embodiment of the present disclosure. Furthermore, the program P may or may not be a so-called difference file (difference program) that can realize the functions of each embodiment of the present disclosure in combination with a program P already recorded in the storage medium.

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

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

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

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

The programs disclosed herein are implemented using, by way of example and not limitation, scripting languages such as ActionScript and JavaScript (registered trademark), compiler languages such as Objective-C and Java (registered trademark), and markup languages such as HTML5.

The following describes an embodiment in which the present invention is implemented using a server-client system.

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

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

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

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

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

In this specification, the term "electronic money" will be used as a general rule, and by way of example and not limitation, the balance of the electronic money account of the user of terminal 20 will be referred to as the "electronic money account balance."

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

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

In the following description, for convenience, the user making the remittance request will be referred to as the "remittance master user," and the user receiving the remittance request will be referred to as the "remittance request recipient user."
The remittance master user may also be referred to as the "remittance requesting user" or the "remittance request main user."

The following description will be given on the assumption that various processes according to the present invention are executed by a payment application or messaging application installed on the terminal 20. In this case, by way of example and not limitation, a function of the payment application may include a messaging service function, or a function of the messaging application may include a payment service function.

The messaging service is configured to allow users to chat using chat rooms.
A chat room is a virtual room in which one or more users of terminals 20 can communicate using data communication lines on a computer network.
In messaging services, chat rooms are sometimes called "talk rooms."

Examples of chat rooms include, but are not limited to, chat rooms in which users can chat one-on-one, as well as group chat rooms in which a group of multiple users formed in a messaging service can chat.

The messaging service may or may not include an instant messaging service (IMS), which allows the sending and receiving of content such as simple messages between terminals 20.

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

In the embodiment described below, after a remittance request is made from the remittance master user to the remittance request destination user, a remittance reminder is sent. Then, a remittance from the remittance request destination user to the remittance master user is realized based on an input to a display based on the remittance reminder information displayed on the terminal 20 of the remittance request destination user (hereinafter referred to as the "remittance reminder display").

First Example
In the first embodiment, the terminal 20 of the remittance request destination user automatically displays a remittance reminder based on a remittance request that has already been received. Hereinafter, this method will be referred to as "terminal reminder."
The contents described in the first embodiment are applicable to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

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

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

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

The user name is the name of the user of the terminal 20 using the payment application, and by way of example and not limitation, the name registered by the user of the terminal 20 when using the payment application is stored.

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

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

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

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

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

As an example and not a limitation, it may or may not be possible to assign multiple terminal IDs to one user ID.

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

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

The remittance history data is data that stores information about the history of remittances from a user of this application ID to a user of another application ID (remittance history information).

The receipt history data is data that stores information about the history of receipts made by the user of this application ID from users of other application IDs (receipt history information).

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

As a non-limiting example, the date and time stored is the date and time when the remittance request information for the corresponding remittance request was sent from the server 10 to the terminal 20 of the remittance request destination user.

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

The remittance master ID stores the application ID of the remittance master user.
The remittance request destination ID stores the application ID of the remittance request destination user.

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

The remittance completed flag is a flag used to identify whether or not the remittance corresponding to the remittance request has been completed. It is initially set to "OFF" and is set to "ON" once the remittance has been completed.

Here, the method by which the server 10 manages remittance requests can be roughly divided into the following two patterns.
"Pattern A": Remittance requests that have been remitted (remittance completed flag is ON) are left without being deleted.
"Pattern B": Delete remittance requests that have been remitted (remittance completed flag is ON).

Either pattern can be applied, but in the following, the method of "Pattern A" will basically be applied.
In other words, the server 10 does not delete the data of a remittance request for which the remittance completion flag is set to "ON."

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

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

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

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

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

Note that the display screen transitions described below are merely examples of display screen transitions for implementing the method of the present disclosure. In the display screen transitions illustrated below, the display of some display screens may be omitted, or other display screens 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.
On the display unit 24, based on the function of the payment application executed by the terminal 20, a remittance request display MS1 is displayed to notify the user of the terminal 20 (the user of the payment application) that remittance request information has been received.

By way of example and not limitation, the remittance request display MS1 is a notification displayed in push format (hereinafter referred to as a "push notification") and includes the characters "Payment App" and an icon indicating that the display is based on the functionality of a payment application, and a message notifying that the remittance request information has been received and the username of the first user who made the remittance request (by way of example and not limitation, "A.A." and "You have a remittance request").

Also, on the left side of the remittance request display MS1, a button BT1 for confirming detailed information regarding the remittance request is displayed.
Without limitation, the remittance request display MS1 and button BT1 are an example of a first display that is displayed based on terminal 20 receiving first information (by way of example and not limitation, remittance request information) regarding a remittance request by a first user (in this example, A.A.).
When the user taps the button BT1 labeled "Open," the details of the remittance request are displayed based on the functionality of the payment application.

Fig. 1-10 shows an example in which the user of the terminal 20 that has received the remittance request information is B.B. That is, in Fig. 1-9, B.B., the user of the terminal 20, taps the button BT1, resulting in a transition to a screen shown in Fig. 1-10.
The words "Payment App" are displayed in the center of the top of the screen, indicating that this screen is based on the function of a payment application. To the right of this are an icon image and a user name (in this example, "B.B.") of the user in the payment application of this terminal 20.

Also displayed below is the username of the first user and a message indicating that remittance request information has been received from that user (for example, but not limited to, "A.A." and "You have a remittance request").
Further below, a remittance request display MS2 is displayed showing the details of the remittance request.

The remittance request display MS2 includes an icon indicating that the display is based on the receipt of remittance request information (in this example, an icon displaying the text "Request Received"), an icon image of the first user (A.A.) who made the remittance request, the amount specified in the remittance request information and that the user (B.B.) of terminal 20 should remit to the first user (in this example, "3,000 yen"), an icon notifying that the user of terminal 20 is in a position to make the payment (in this example, an icon displaying the text "Payment"), the date and time that terminal 20 received the remittance request information (in this example, "2020.04.20 21:30"), the user name of the first user, a message indicating that remittance request information has been received from the user (in this example, "A remittance request has been received from A.A."), and link information for displaying more detailed information regarding the remittance request (in this example, the portion displaying the text ">Check details").

Furthermore, the remittance request display MS2 includes a remittance button BT2 for executing a remittance process to the first user (A.A.) based on the functionality of the payment application.
Without limitation, the remittance request display MS2 is an example of a first display that is displayed based on first information regarding a remittance request by a first user (A.A. in this example).

When the user (B.B) of the terminal 20 taps the remittance button BT2 on this screen, the screen transitions to a remittance screen (the screen in FIG. 2-8, by way of example and not by way of limitation) for remittance of the amount specified in the remittance request information. When the user taps the remittance area RM2 at the bottom of the screen on this remittance screen, the screen transitions to a remittance confirmation screen (the screen in FIG. 2-9, by way of example and not by way of limitation).
When user B.B of terminal 20 taps the confirmation button BT6 on the remittance confirmation screen, the amount specified in the remittance request (remittance request amount: the amount shown on the remittance request display MS2) is remitted from the electronic money account of user B.B of terminal 20 to the electronic money account of the first user (A.A).

When an amount corresponding to the remittance request amount of the first user (A.A) has been remitted, a remittance reminder display (not limiting, but an example of a second display different from the first display based on a remittance request) that again urges the user (B.B) of the terminal 20 to remit money to the first user (A.A) will not be displayed on the display unit 24 of the terminal 20 of the user (B.B).

On the other hand, if the amount corresponding to the remittance request amount of another user (A.A) is not remitted, for example but not limited to, if the user (B.B) of the terminal 20 does not perform the remittance operation described above within a specified period of time, it is possible to display a remittance reminder on the display unit 24 of the terminal 20 of that user (B.B).

In the example of FIG. 1-11, the display unit 24 displays a remittance reminder display MS3 that notifies the user of the terminal 20 (user of the payment application) that a remittance reminder has been sent based on the function of the payment application executed by the terminal 20.

By way of example and not limitation, the remittance reminder display MS3 differs from the remittance request display MS1 shown in FIG. 1-9 in that it includes a message (by way of example and not limitation, "A.A.", "You have a (terminal reminder) remittance request.") informing the user that a remittance reminder has been generated based on the capabilities of the terminal 20 (i.e., that a terminal reminder has been generated) and the username of the first user related to the remittance reminder.

In addition, a button BT3 for checking detailed information regarding the remittance reminder is displayed on the left side of the remittance reminder display MS3. The remittance reminder display MS3 and the button BT3 are, without limitation, an example of a second display that is different from the first display based on a remittance request.
When the user taps the button BT3 labeled "Open," details of the remittance reminder are displayed based on the functionality of the payment application.

FIG. 1-12 shows an example in which the user of the terminal 20 that is the target of the remittance reminder is user B.B. That is, in FIG. 1-11, user B.B. taps button BT3, and the screen transitions to the screen shown in FIG. 1-12.

The screen shown in Figure 1-12 displays a remittance reminder display MS4 that shows the details of the remittance reminder.

As an example and not as a limitation, the remittance reminder display MS4 differs from the remittance request display MS2 shown in FIG. 1-12 in that it notifies the user that the remittance process corresponding to the remittance request information has not yet been executed, and includes an icon with the words "Terminal Remind" indicating that the notification is based on the function of the terminal 20 (the function of the payment application), and in that it displays the date and time when the remittance request information was received by the terminal 20 after a message indicating that a remittance request has been received from the first user (in this example, "A remittance request has been received from A.A. (2020.0420.21:30)").
That is, in the remittance reminder display MS4, the content or display form of the message notifies the user that a remittance reminder has been sent because the remittance process for the remittance request has not yet been carried out.

Further, the remittance reminder display MS4 includes a remittance button BT4 for executing a remittance process to the first user (A.A.) based on the functionality of the payment application.
Without limitation, the remittance reminder display MS4 is an example of a second display that is different from the first display based on a remittance request.

When the user (B.B) of the terminal 20 taps the remittance button BT4 on this screen, the screen transitions to a remittance screen (the screen in FIG. 2-8, by way of example and not limitation) for remittance of the amount specified by the remittance reminder display MS4. When the user taps the remittance area RM2 at the bottom of the screen on this remittance screen, the screen transitions to a remittance confirmation screen (the screen in FIG. 2-9, by way of example and not limitation).
When the user (B.B) of terminal 20 taps the confirmation button BT6 on the remittance confirmation screen, the amount specified in the remittance reminder display MS4 is remitted from the electronic money account of the user (B.B) of terminal 20 to the electronic money account of the first user (A.A).

Thus, as an example and not a limitation, based on an input by the user (B.B) of the terminal 20 to the second display (remittance reminder display MS3 and button BT3, remittance reminder display MS4 including remittance button BT4) displayed on the display unit 24, the control unit 21 of the terminal 20 executes a remittance process for remittance from the user (B.B) of the terminal to the first user (A.A) based on a remittance request.

<Processing>
1-13 and 1-14 are flow charts showing an example of the flow of processes executed by each device in this embodiment.

The processes described below are merely examples of processes for implementing the method of the present disclosure, and the present disclosure is not limited to these processes.
Further, other steps may be added to the processes described below, or some steps may be omitted (deleted).
This also applies to each of the flowcharts (processes) described below.

In this process, from the left, a process executed by the control unit 21 of the terminal 20A, a process executed by the control unit 21 of the terminal 20B, and a process executed by the control unit 11 of the server 10 are shown.
As an example and not by way of limitation, assume that user A.A of terminal 20A is the remittance master user and user B.B of terminal 20B is the remittance request destination user.

This process is an example of a process in which the terminal 20 of the remittance request destination user (terminal 20B in this example) automatically displays a remittance reminder display on the display unit 24.
In addition, the remittance reminder is not limited to one time, but can be sent two or more times, but for simplicity, the process of judging whether the process is completed is omitted here, and the process is illustrated and described as a process in which the remittance reminder is sent only once. The same applies to the case in which the remittance reminder is sent two or more times.

First, the control unit 21 of the terminal 20A determines whether or not to request the execution of a remittance request based on whether or not an input to request the execution of a remittance request (hereinafter referred to as a "remittance request execution input") has been made to the input unit (A110), by way of example and not limitation.
The remittance request execution input may be, by way of example and not limitation, an operation for requesting execution of a remittance request (hereinafter referred to as a "remittance request execution operation").

If it is determined that a request should be made (A110: YES), the control unit 21 of terminal 20A transmits information (hereinafter referred to as "remittance request transmission request information") to the server 10 via the communication I/F 22 to request (ask) the terminal 20 of the remittance request destination user (terminal 20B in this example) to transmit the remittance request information (A120).

The remittance request transmission request information may include, by way of example and not limitation, at least identification information of user A.A of terminal 20A (application ID, by way of example and not limitation), identification information of user B.B, the remittance request destination user (application ID, by way of example and not limitation), and the remittance request amount (amount requested to be remitted).

When the remittance request transmission request information is received from terminal 20A via communication I/F 14, control unit 11 of server 10 generates remittance request information with a remittance request management ID set based on the received remittance request transmission request information, and updates first remittance request management data 157A. Then, control unit 11 of server 10 transmits the generated remittance request information to terminal 20B of user B.B, the user to whom the remittance request is to be sent, via communication I/F 14 (S110).

The remittance request information may include, by way of example and not limitation, a remittance request management ID, information that allows a user to identify (recognize) that it is a remittance request (by way of example and not limitation, text, images, etc. indicating that it is a remittance request), information on the remittance request amount, and information on the remittance master user (by way of example and not limitation, the username of the remittance master user).

In addition, the information on the remittance master user is not limited to the user name, but may or may not include information such as the application ID, the remittance master user's terminal telephone number, and terminal email address.

When the remittance request information is received from the server 10 via the communication I/F 22, the control unit 21 of the terminal 20B causes the display unit 24 to display a remittance request display based on the received remittance request information (B110).
The remittance request display may include displaying some or all of the information contained in the received remittance request information, as well as displaying information related to the received remittance request information and information for realizing a remittance based on the received remittance request information (for example, but not limited to, operational images such as a remittance button, a remittance icon, etc.).

Thereafter, the control unit 21 of the terminal 20B judges whether or not to execute the remittance based on the remittance request (B120). By way of example and not of limitation, it judges whether or not an input for execution of remittance specifying the remittance request management ID has been made to the input unit.
If it is determined that the remittance is to be executed (B120: YES), the control unit 21 of the terminal 20B transmits remittance settlement request information for requesting settlement of the remittance to the server 10 via the communication I/F 22 (B130).

The remittance settlement request information may include, by way of example and not limitation, a remittance request management ID and a planned remittance amount.
The planned remittance amount is the amount that has been input as the amount to be remitted, but is the amount that has not yet been remitted.

The control unit 11 of the server 10 determines whether or not remittance settlement request information has been received from the terminal 20B via the communication I/F 14 (S120), and if it is determined that the remittance settlement request information has been received (S120: YES), executes the remittance settlement process (S130).
Specifically, by way of example and not limitation, the remittance amount is updated by subtracting the planned remittance amount from the balance of the electronic money account of user B.B, and the remittance amount is updated by adding the remittance amount to the balance of the electronic money account of user A.A.
The remittance amount is the amount remitted from the remittance request destination user to the remittance master user.
Also, the remittance completion flag corresponding to the received remittance request management ID in the first remittance request management data 157A is set to "ON."
For a remittance request management ID for which the remittance completion flag has been set to "ON", no further remittances will be made.

In addition, in the remittance settlement process, if the balance of the electronic money account is insufficient (if the amount to be remitted exceeds the balance of the electronic money account), the remittance will not be made.
In this case, the control unit 11 of the server 10 transmits information to the terminal 20B prompting the terminal 20B to top up the balance of the electronic money account. Then, based on receiving the information requesting top-up from the terminal 20B, the control unit 11 of the server 10 may or may not top up the balance of the electronic money account before transferring the money.

Thereafter, the control unit 11 of the server 10 transmits remittance information, which is information related to remittance, to the terminal 20B via the communication I/F 14 (S140).
The remittance information includes, by way of example and not limitation, a remittance completion notification for notifying that the remittance has been completed.

In addition, the control unit 11 of the server 10 transmits receipt information, which is information related to the receipt, to the terminal 20A via the communication I/F 14 (S150).
The receipt information includes, by way of example and not limitation, information such as a receipt completion notification for notifying that the receipt has been completed.

When receipt information is received from the server 10 via the communication I/F 22 (A140: YES), the control unit 21 of the terminal 20A displays the received receipt information on the display unit 24 (A150).

When remittance information is received from the server 10 via the communication I/F 22, the control unit 21 of the terminal 20B causes the display unit 24 to display the received remittance information (B140).

Then, the control unit 21 of the terminal 20B judges whether or not to issue a remittance reminder (terminal reminder in this embodiment) for the remittance request (B145). Specifically, by way of example and not limitation, if a remittance reminder (terminal reminder) is set to be issued, it is judged that a remittance reminder should be issued.

Basically, if remittance based on the remittance request is not executed in B120, a remittance reminder can be sent.
However, unlike this, a remittance reminder may be sent regardless of whether or not the remittance based on the remittance request has been executed.

In this case, instead of sending the remittance reminder immediately after receiving the remittance request information sent from the server 10 in S110 or after displaying the remittance request display on the display unit 24 in B110, the remittance reminder can be sent after a certain period of time has elapsed, for example and not by way of limitation.

When it is determined that a remittance reminder should be issued (B145: YES), the control unit 11 of the server 10 creates remittance reminder information based on the previously received remittance request information. Then, the control unit 21 of the terminal 20B causes the display unit 24 to display a remittance reminder display based on the created remittance reminder information (B150).

The content of the remittance reminder display can be the same as the remittance request display, except that the content includes, for example and not limitation, information that allows the user to identify (recognize) that it is a remittance reminder (for example and not limitation, text, images, etc. indicating that it is a remittance reminder).

The content of the remittance request display and the content of the remittance reminder display may or may not be the same.

The remittance reminder display can be understood as a concept that includes the display of some or all of the information contained in the received remittance reminder information, as well as the display of information related to the received remittance reminder information and the display of information for realizing a remittance based on the received remittance reminder information (for example, but not limited to, operational images such as a remittance button or remittance icon).

Next, the control unit 21 of the terminal 20B determines whether or not an input has been made in response to the remittance reminder displayed on the display unit 24 (B160).
An "input" can be, for example and not limitation, an operation on an input unit (operation unit), and for example and not limitation, a tap (tap operation).
This input can also include input to the various remittance reminder displays MS described above. It is not limited to tapping the remittance button, but as a non-limiting example, a remittance can be realized by tapping the display area of any of the various remittance reminder displays MS described above.

If it is determined that an input has been made (B160: YES), the control unit 21 of the terminal 20B transmits remittance settlement request information to the server 10 via the communication I/F 22 based on the remittance reminder information (B130).
In this case, too, by way of example and not limitation, the remittance request management ID and the planned remittance amount of the previously received remittance request information may be included in the remittance settlement request information.

The control unit 11 of the server 10 determines whether or not remittance settlement request information has been received from the terminal 20B via the communication I/F 14 (S120), and if it is determined that the remittance settlement request information has been received (S120: YES), executes the remittance settlement process (S130). This remittance settlement process is as described above.

Thereafter, the control unit 11 of the server 10 transmits the remittance information to the terminal 20B via the communication I/F 14 (S140).
Furthermore, the control unit 11 of the server 10 transmits the above-mentioned receipt information to the terminal 20A via the communication I/F 14 (S150).
Then, the control unit 11 of the server 10 ends the process.

When the remittance information is received from the server 10 via the communication I/F 22, the control unit 21 of the terminal 20B causes the display unit 24 to display the received remittance information (B140).Then, the control unit 21 of the terminal 20B ends the process.
Furthermore, when receipt information is received from the server 10 via the communication I/F 22 (A140: YES), the control unit 21 of the terminal 20A causes the received receipt information to be displayed on the display unit 24 (A150). Then, the control unit 21 of the terminal 20A ends the process.

<Remittance process executed by the terminal (first remittance process)>
The processing executed by the terminal 20 (for example, but not limited to, the terminal 20 of the remittance request destination user) through the control unit 21 includes a remittance processing (hereinafter, the remittance processing executed by this terminal is referred to as the “first remittance processing”).
The first remittance process is a process executed by the terminal 20 and is a process related to remittance from a remittance request destination user (user of the terminal) to a remittance master user (first user) based on a remittance request (remittance request).

This first remittance process may include, by way of example and not limitation, a process for realizing a remittance from the user of the terminal to the first user, or a process related in some way to a remittance from the user of the terminal to the first user. In addition to processes directly related to the remittance, processes indirectly related to the remittance may also be included in the remittance process executed by the terminal.

In the above process example, by way of example and not limitation, the first remittance process includes the following processes:
(1) A process of transmitting remittance settlement request information to the server 10 via the communication I/F 22. (2) A process of receiving remittance information from the server 10 via the communication I/F 22. (3) A process of displaying the received remittance information on the display unit 24.

<Device-related input>
In the above process, inputs to the terminal or inputs by the terminal user, such as input for executing a remittance request or input for displaying a remittance reminder, are considered to be operation inputs to the input unit (operation unit), but this is not limited to this.

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

Effects of the First Embodiment
In this embodiment, the terminal 20 receives remittance request information (not limiting, an example of first information related to a remittance request) from a remittance master user (not limiting, an example of a first user) via the communication I/F 22. Then, the terminal 20 displays a remittance request display (not limiting, an example of a first display) on the display unit 24.
Furthermore, the terminal 20 displays a remittance reminder display (not limiting, an example of a second display) different from the remittance request information based on the remittance request on the display unit 24. The terminal 20 then shows a configuration in which the control unit 21 executes a first remittance process (not limiting, an example of a remittance process relating to a remittance from the user of the terminal to the first user) based on the remittance request, based on an input to the remittance reminder display displayed on the display unit 24 (not limiting, an example of an input to the second display).
As an example of the effect of an embodiment obtained by such a configuration, a remittance process can be executed by the control unit of the terminal based on an input to a second display displayed on the display unit of the terminal, thereby easily realizing a remittance from the user of the terminal to the first user.

In addition, in this embodiment, the remittance request display includes information on the remittance request amount based on the remittance request (not limiting, but an example of information on the amount based on the remittance request), and the remittance reminder display includes information on a similar amount (not limiting, but an example of information on the amount based on the remittance request).
As an example of the effect of the embodiment obtained by such a configuration, the amount based on the remittance request can be reliably notified to the user of the terminal by the first display and the second display.

In addition, in this embodiment, the remittance request display includes information such as the username of the remittance master user (not limited to, but an example of information about the first user), and the remittance reminder display includes similar information such as the username (not limited to, but an example of information about the first user).
As an example of the effect of the embodiment obtained by such a configuration, the information of the user who has requested remittance can be reliably notified to the user of the terminal by the first display and the second display.

In addition, this embodiment shows a configuration in which the remittance request display (not limiting, an example of a first display) and the remittance reminder display (not limiting, an example of a second display) are displayed on the display unit 24 by a payment application (not limiting, an example of an application installed on the terminal) installed on the terminal 20.
As an example of the effect of the embodiment obtained by such a configuration, the user of the terminal can easily recognize the first display and the second display by an application installed on the terminal.

In addition, in this embodiment, the first remittance process is configured to include a process of receiving remittance information (not limited to information indicating that a remittance process based on a remittance request has been executed) via the communication I/F 22.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to inform the user of the terminal that the remittance processing based on the remittance request has been executed.

In addition, in this embodiment, the first remittance process is configured to include a process of transmitting remittance settlement request information (not limited to this, an example of information regarding a request for processing a remittance based on a remittance request) via the communication I/F 22.
As an example of an effect of the embodiment obtained by such a configuration, it is possible to request an external party to process a remittance based on a remittance request from the first user.

<First Modification (1)>
When the first remittance process is not being executed (not yet executed) on the terminal 20 of the remittance request destination user, a display (not limiting, an example of a fourth display) indicating that remittance based on the remittance request from the remittance master user has not been made is displayed on the display unit 24. On the other hand, when the first remittance process is being executed (already executed) on the terminal 20 of the remittance request destination user, a display (not limiting, an example of a fifth display) indicating that remittance based on the remittance request from the remittance master user is being made may or may not be displayed on the display unit 24.

Indications regarding a failure to transfer funds based on a transfer request from a transfer master user may include, by way of example and not limitation, text such as "Money not yet transferred" or "Money not transferred" or an image (such as a mark or icon) indicating an untransferred status.
Similarly, indications regarding the fact that a transfer is being made based on a transfer request from a transfer master user may include, by way of example and not limitation, text such as "Money has already been transferred" or "Money has been transferred," or an image (such as a mark or icon) indicating that the money has been transferred.

In this modified example, when the first remittance process (one example of a remittance process, not limiting) is not being executed, the terminal 20 of the remittance request destination user displays on the display unit 24 a display indicating that remittance has not been made based on the remittance request from the remittance master user (not limiting, an example of a fourth display) On the other hand, when the first remittance process is being executed (has been executed), the terminal 20 of the remittance request destination user is configured to display on the display unit 24 a display indicating that remittance has been made based on the remittance request from the remittance master user (not limiting, an example of a fifth display).
As an example of the effect of this modified example obtained by such a configuration, the status of remittance based on the remittance request (whether it is being carried out or not) can be appropriately notified to the user of the terminal.

<First Modification (2)>
In the first embodiment, a push notification can be sent as one of the reminder displays on the terminal 20 of the remittance request destination user. This push notification can be considered as one type of reminder display or one type of reminder notification.

In addition to this push notification, by way of example and not limitation, a reminder notification process can be performed based on the following control.
The control unit 21 controls the sound output unit 26 to output a predetermined sound.
The control unit 21 controls a vibration unit (not shown) to vibrate the housing of the terminal 20 .
The control unit 21 controls the light emitting unit (not shown) to emit a predetermined light.

In addition to when it is time to execute a device reminder, it is also possible to set conditions for issuing a reminder notification (hereinafter referred to as "remind notification conditions"), and execute the reminder notification process when the reminder notification conditions are met.

As a non-limiting example of the reminder notification conditions, a condition such as "the current time is not included in the time period when the user is likely to be asleep (the current time is not included in the time period late at night (until midnight the next day), before dawn (until 3:00 the next day), or in the early morning (from 3:00 the next day))" can be set.
By doing this, the reminder notification conditions are not met during these set time periods, and the reminder notification process is not executed, so that reminder notifications are not sent during times when the user is likely to be asleep.

In this modified example, the terminal 20 of the remittance request destination user is configured to execute a reminder notification process by the control unit 21 based on the set reminder notification condition (not limited to this, but an example of the second condition).
As an example of the effect of the modified example obtained by such a configuration, it is possible to notify the user of the terminal of the execution of a terminal reminder at an appropriate timing based on the set conditions.

<First Modification (3)>
In the first embodiment, when executing a remittance based on a remittance request at the terminal 20 of the remittance request destination user, by way of example and not limitation, the remittance can be executed based on input to the remittance request display displayed on the display unit 24, in the same way as when executing a remittance based on a remittance reminder.

FIG. 1-15 is a flowchart showing an example of the flow of processes executed by each device in this modified example.
This flowchart corresponds to the processing portion of FIG. 1-14 in the flowcharts of FIGS. 1-13 to 1-14.

After B110, the control unit 21 of the terminal 20B determines whether or not an input has been made in response to the remittance request displayed on the display unit 24 (B125).
The input in this case may be an operational input such as a tap (tap operation), a sound input, or the like, similar to the input for the remittance reminder display described above.
If it is determined that an input has been made (B125: YES), the control unit 21 of the terminal 20B advances the process to B130.

This modified example illustrates a configuration in which the terminal 20 of the remittance request destination user executes, via the control unit 21, a process (not limiting, an example of a remittance process relating to a remittance from the terminal user to the first user) for realizing a remittance from the remittance request destination user to the remittance master user based on a remittance request, based on input by the remittance request destination user to a remittance request display (not limiting, an example of a first display).
As an example of the effect of the embodiment obtained by such a configuration, remittance based on a remittance request can be easily realized based on an input by the user of the terminal to the first display.

<First Modification (4)>
In the first embodiment, the first user is described as a general user of the terminal 20 (user A.A. in the above example), but is not limited to this.
The first user may or may not be a user of a business such as a store, rather than a general user. In this case, the business may include, but is not limited to, a business (store) that is expected to request money from the user of the terminal 20 by making a remittance request, such as a business that sells products (including the provision of services) or a business that operates a money lending business.

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

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

In this modified example, the remittance master user (not limited to this, but an example of a first user) is a store that sells the product related to the remittance request.
As an example of the effect of this modified example obtained by such a configuration, not only general users but also users at shops can be made users (first users) who can make remittance requests to the user of the terminal.

<First Modification (5)>
It is assumed that some users of the terminal 20 may feel awkward and hesitate to make a remittance request or a remittance reminder to the remittance request destination user, for example, but not limited to, when the remittance request destination user is a person of higher rank than the user, or when the remittance request destination user is a close friend.

Therefore, the user who sends the remittance request or remittance reminder may be a user who uses a business account, rather than the user of the terminal 20 .
By way of example and not limitation, a business account is a user who has an official account (hereinafter referred to as an "official account" and appropriately expressed as "OA: Official Account") in that service (in the above example, a payment service).

As an example, a user with an official account can be, by way of example and not limitation, a payment service provider. In this case, the server 10 can transmit remittance request information or remittance reminder information to the terminal 20 of the user who is the recipient of the remittance request, assuming that the user who has requested the remittance request or remittance reminder is the payment service provider, rather than the user of the terminal 20.

This modified example illustrates a configuration in which the remittance requester (an example of a first user, not limiting) is a user who uses an official account (an example of a business account, not limiting).
As an example of the effect of this modified example obtained by such a configuration, it becomes possible to have a user using a business account make a remittance request on behalf of the user who wishes to make the remittance request, thereby improving user convenience.

Second Example
In the second embodiment, the terminal 20 of the remittance request destination user displays a remittance reminder based on receiving remittance reminder information from the server 10. Hereinafter, this method will be referred to as "server remind."
The contents described in the second embodiment are applicable to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<Data structure>
FIG. 2A is a diagram showing an example of the configuration of the second remittance request management data 157B, which is another example of the remittance request management data 157 described above, stored in the storage unit 15 of the server 10. As shown in FIG.
In the second remittance request management data 157B, in addition to the date and time, remittance request management ID, remittance master ID, remittance request destination ID, remittance request amount, and remittance completion flag in the first remittance request management data 157A, by way of example and not limitation, information type is stored in association with the date and time, remittance request management ID, remittance master ID, remittance request destination ID, remittance request amount, and remittance completion flag in the first remittance request management data 157A.

The information type is information for identifying whether the type of information corresponding to the remittance request management ID is a remittance request or a remittance reminder. By way of example and not limitation, "Request" is stored for a remittance request, and "Reminder" is stored for a remittance reminder.

As a non-limiting example, the date and time stored is when the information type of the corresponding remittance request is a "request," and when the remittance request information is sent from the server 10 to the terminal 20 of the remittance request destination user, and when the information type of the corresponding remittance request is a "remind," the date and time stored is when the remittance reminder information is sent from the server 10 to the terminal 20 of the remittance request destination user.

In addition, for each remittance request management ID, the remittance reminder information corresponding to the remittance request information identified by that remittance request management ID stores the same ID, the same amount, and the same flag as the remittance request management ID, the remittance request amount, and the remittance completion flag, regardless of the number of times a remittance reminder has been issued.
By way of example and not limitation, the data in the records enclosed in black boxes in the figure are data for the corresponding remittance requests and remittance reminders.

<Display screen>
FIG. 2-2 shows an example of information displayed on the display unit 24 when a payment application is executed on the terminal 20 of the first user (AA).
The display unit 24 displays the first user's (A.A.) electronic money account balance (in this example, "25,000 yen"), along with icons corresponding to each of the functions that can be executed in the payment application.
The first user (A.A) can check whether a remittance has been made, and if so, which user made the remittance and the remittance amount, by displaying the deposit history for his/her account on the display unit 24. In other words, it is possible to check whether a remittance has been made in response to a remittance request.

Functions that can be executed by the payment application include a remittance request function for requesting a payment from a specified user, and the words "Remittance Request" are displayed together with an icon IC1 including a "¥ mark" corresponding to the remittance request function.
When a first user (A.A) selects this icon, designates the user to whom the remittance request is to be made (B.B in this example), and inputs the remittance request amount (remittance request amount) (in this example, "3,000 yen"), the remittance request information is sent to terminal 20 of the designated user (B.B), and remittance request displays MS1 and MS2 are displayed on display 24 of terminal 20 of the designated user.

Then, in the terminal 20 of the first user (A.A.), information on the user who is the subject of the remittance request and the requested remittance amount are managed as a remittance request history in the payment application.
In the example of FIG. 2-2, the words "Transmission Request List" are displayed together with an icon IC2 corresponding to the function of viewing the remittance request history.
By selecting this icon, the first user (A.A.) can individually check users who have been the target of remittance requests in the past and the remittance amounts requested for those users.

In this example, as shown in Figure 2-3, information regarding remittance requests made in the past by the first user (A.A.) that have not yet been processed, i.e., requests that can be subject to remittance reminders, is displayed individually below the title "List of Remittance Requests."
In this example, the icon image and user name of the user who is the target of the remittance request (in this example, B.B.), the date and time when that user's terminal 20 received the remittance request information (in this example, 2020.04.20 21:30), the amount of the remittance request to that user (in this example, "3,000 yen"), and an icon indicating that the first user (A.A) is in the position to receive the remittance request amount (in this example, an icon with the word "Receive") are displayed in association with each other within a rectangular area R1.

In addition, area R1 is provided with check boxes, and when the user checks the check boxes, each piece of information displayed in area R1 is selected.

In the example of FIG. 2-3, an area RR displaying "Remind" is provided at the bottom of the screen. When the first user (A.A) taps the area RR with the checkbox checked, remittance reminder information based on the information displayed in the area R1 is transmitted to the terminal 20 of the user (B.B) who was the target of the remittance request information.
Then, the remittance reminder display is displayed on the display unit 24 of the terminal 20 that has received the remittance reminder information.

When the terminal 20 of the user (B.B) receives remittance reminder information or a remittance reminder display based on the reception of the remittance reminder information is displayed on the terminal 20 of the user (B.B), as shown in FIG. 2-4, a remittance reminder completion display MS5 is displayed on the terminal 20 of the first user (A.A), notifying that the remittance reminder has been completed.
The remittance reminder completion display MS5 includes the username of the user who was the subject of the remittance request (B.B. in this example).

The terminal 20 of the user (B.B) who received the remittance reminder information displays a remittance reminder display MS3A based on the receipt of the remittance reminder information, as shown in FIG. 2-5.

By way of example and not limitation, the remittance reminder display MS3A may include a message (by way of example and not limitation, "A.A.", "You have a remittance request [reminding you]") informing the first user of the username of the remittance reminder based on receiving the remittance reminder information.
The difference between the remittance reminder display MS3 shown in Figure 1-11 and the remittance reminder display MS3 is that it displays "Terminal Remind" because the remittance reminder display is based on the functions of the user's own terminal, whereas the remittance reminder display MS3A displays "Remind Received" because the remittance reminder display is based on the received remittance reminder information.

Also, on the left side of the remittance reminder display MS3A, a button BT3A for confirming detailed information regarding the remittance reminder is displayed.
Without being limiting, the remittance reminder display MS3A and the button BT3A are an example of a second display that is different from the first display based on a remittance request.
Without being limiting, the remittance reminder display MS3A and the button BT3A are an example of a second display that is displayed on the display unit 24 based on the terminal 20 receiving second information based on a remittance request.

When the user taps the button BT3A labeled "Open," details of the remittance reminder are displayed based on the functionality of the payment application.
In FIG. 2-5, when the user (B.B.) taps the button BT3A, the screen moves to that shown in FIG. 2-6, and a remittance reminder display MS4A showing details of the remittance reminder is displayed.

By way of example and not limitation, the remittance reminder display MS4A includes an icon with the text "Remind Received" based on receipt of the remittance reminder information, and a message notifying the first user of the username based on receipt of the remittance reminder information (by way of example and not limitation, "[Remind Received] A remittance request has been received from A.A.").

The difference between the remittance reminder display MS4 shown in Figure 1-12 and the remittance reminder display MS4 is that an icon with the words "Terminal Remind" is displayed because the remittance reminder display is based on the functions of the user's own terminal, whereas the remittance reminder display MS4A displays an icon with the words "Remind Received" because remittance reminder information has been received.
Another difference is that in the remittance reminder display MS4A in Figure 2-6, the word [Reminder Received] is displayed before the user name of the first user (A.A), indicating that the remittance reminder display is based on remittance reminder information, whereas in the remittance reminder display MS4 shown in Figure 1-12, there is no such display.

When the user (B.B.) of the terminal 20 taps on the link information displayed as “>Check details” on the remittance reminder display MS4A, the screen moves to that of FIG. 2-7.
2-7 screen notifies the user of the event that caused the remittance request reminded by the remittance reminder display MS4A (in this example, it is the membership fee for an event held on April 20th). It also notifies the user (B.B) of the terminal 20 that he or she is in a position to make a payment (in this example, an icon with the word "Payment") and the amount to be paid (in this example, "3,000 yen").

In the screen of FIG. 2-7, information about remittance reminders is displayed together with animal characters in an area larger than the remittance reminder display MS4A described above. Below that, an area RM1 is provided.

Area RM1 displays the username of the first user (A.A), information notifying the first user that a remittance request and remittance reminder have been made (in this example, the messages "Reminder received" and "A.A. has requested a remittance"), and link information for remittance to the first user in the amount corresponding to the remittance request and remittance reminder (in this example, the area displaying the words ">Send money").

When the user (B.B.) of the terminal 20 taps on the remittance link information, the remittance screen shown in FIG. 2-8 appears.
The remittance screen displays the icon image and user name (A.A) of the first user to whom the remittance is to be made, the amount to be remitted to the first user (in this example, "3,000 yen"), an icon notifying that the user of terminal 20 (B.B.) is in the position to make the payment (in this example, an icon with the word "Payment"), and the current amount that the user of terminal 20 (B.B.) can remit (in this example, "5,000 yen").

Based on the fact that the current remittance amount of the user (B.B) of terminal 20 is greater than the amount to be remitted to the first user, the user (B.B) of terminal 20 is now in a state where he or she can remit to the first user (A.A) the amount corresponding to the remittance request information and the remittance reminder information.

When the remittance area RM2 at the bottom of the remittance screen is tapped, the screen transitions to the remittance confirmation screen shown in FIG. 2-9.
By way of example and not limitation, the remittance confirmation screen is a screen superimposed on the remittance screen and includes an icon image and user name (A.A) of the first user to whom the remittance is to be sent, the remittance amount (3,000 yen in this example) to be sent to the first user using the payment application, and a confirmation button BT6 displaying the word “Confirm.”

When the user (B.B) of terminal 20 taps the confirmation button BT6, the amount displayed on the remittance confirmation screen (in this example, "3,000 yen") is transferred from the account of the user (B.B) of terminal 20 to the account of the first user (A.A).
When the remittance is completed, a remittance completion screen shown in FIG. 2-10 is displayed on the terminal 20 of the user (B.B.).
As an example and not as a limitation, the remittance completion screen is a screen superimposed on the remittance screen, and displays the username (A.A) of the first user to whom the remittance is to be made and a message notifying the user that the remittance process has been completed.

<Processing>
(1) Example of Processing FIG. 2-11 is a flowchart showing an example of the flow of processing executed by each device in this embodiment.
This flowchart corresponds to the processing portion of Figure 1-14 in the flowcharts of Figures 1-13 to 1-14, and is a flowchart showing the process in which the server 10 automatically sends remittance reminder information to the terminal 20 of the remittance request destination user (terminal 20B in this example).

The control unit 11 of the server 10 determines whether or not to issue a remittance reminder (in this embodiment, a server reminder) for the previous remittance request (S260). Specifically, by way of example and not limitation, if no remittance settlement request information is received from the terminal 20A in S120, it is determined that a remittance reminder is to be issued.

In this case, after the remittance request information is sent to the terminal 20 in S110, the remittance reminder is not sent immediately, but rather, by way of example and not limitation, the remittance reminder can be sent after a certain period of time has elapsed.

If it is determined that a remittance reminder should be issued (S260: YES), the control unit 11 of the server 10 creates remittance reminder information with the same ID as the remittance request management ID set in S110, and updates the second remittance request management data 157B. The control unit 11 of the server 10 then transmits the generated remittance reminder information together with the remittance request management ID to the terminal 20B via the communication I/F 14 (S270). The control unit 11 of the server 10 then proceeds to S120.

When remittance reminder information is received from the server 10 via the communication I/F 22 (B240: YES), the control unit 21 of the terminal 20B causes the display unit 24 to display a remittance reminder display (B250). Then, the control unit 21 of the terminal 20B transfers the process to B160.

(2) Another Example of Processing FIG. 2-12 is a flowchart showing another example of the flow of processing executed by each device in this embodiment.
This flowchart corresponds to the processing portion of Figure 1-14 in the flowcharts of Figures 1-13 to 1-14, and is a flowchart showing the processing by which the server 10 sends remittance reminder information to the terminal 20 of the remittance request destination user (terminal 20B in this example) based on receiving remittance reminder sending request information sent from the terminal 20 of the remittance master user (terminal 20A in this example).

After A150 in FIG. 1-13, the control unit 21 of the terminal 20A determines whether or not to request the execution of a remittance reminder based on, by way of example and not limitation, whether an input to request the execution of a remittance reminder (hereinafter referred to as a "remittance reminder execution input") has been made to the input unit (A260).
The remittance reminder execution input, like the remittance request execution input described above, can be realized by, for example and not by way of limitation, operation input or sound input.

If it is determined that a request should be made (A260: YES), the control unit 21 of the terminal 20A transmits remittance reminder transmission request information to the server 10 via the communication I/F 22 (A270). Then, the control unit 21 of the terminal 20A transfers the process to A150.

The control unit 11 of the server 10 determines whether remittance reminder sending request information has been received from the terminal 20A via the communication I/F 14 (S265), and if it is determined that the information has been received (S265: YES), the process proceeds to S270.

<Remittance process executed by server (second remittance process)>
The processes executed by the server 10 through the control unit 11 include a remittance process (hereinafter, this remittance process executed by the server is referred to as the "second remittance process").
The second remittance process is a process executed by the server 10 and is a process related to remittance from a remittance request destination user (user of the terminal) to a remittance master user (first user) based on a remittance request.

This second remittance process may include, by way of example and not limitation, a process for realizing a remittance from the user of the terminal to the first user, or a process related in some way to a remittance from the user of the terminal to the first user. In addition to processes directly related to the remittance, processes indirectly related to the remittance may also be included in the remittance process executed by the terminal.

In the above process example, the second remittance process includes, by way of example and not limitation, the following processes:
(1) A process of receiving remittance settlement request information from the terminal 20 via the communication I/F 14. (2) A remittance settlement process (including a process of adjusting the balance of the electronic money account, etc.).
(3) Processing for transmitting remittance information/received information to the terminal 20 via the communication I/F 14

<Effects of the Second Example>
In this embodiment, remittance request information (not limiting, an example of first information) regarding a remittance request by a remittance master user (not limiting, an example of a first user) is transmitted to the terminal 20 of the remittance request destination user via the server 10 based on input by the remittance master user (not limiting, an example of a first user) to the remittance master user's terminal 20.
On the other hand, the remittance reminder information (an example of the second information, not limiting) is sent by the server 10 to the terminal 20 of the remittance request destination user, and the remittance reminder display (an example of the second display, not limiting) is displayed on the display unit 24 of the terminal 20 of the remittance request destination user based on the remittance reminder information.
As an example of the effect of the embodiment obtained by such a configuration, the first information can be transmitted to the terminal via the server in response to the intention of the first user who has requested the remittance, and the second information can be transmitted from the server to the terminal, and then a second display can be displayed on the display unit of the terminal based on the second information.

In addition, in this embodiment, the server 10 transmits remittance request information (not limiting, an example of first information related to a remittance request) related to a remittance request by a remittance master user (not limiting, an example of a first user) to the terminal 20 (not limiting, an example of a terminal) of the remittance request destination user via the communication I/F 14. The server 10 also transmits remittance reminder information based on the remittance request (not limiting, an example of second information based on a remittance request) to the terminal 20 of the remittance request destination user via the communication I/F 14. The server 10 then performs a second remittance process (not limiting, an example of a remittance process related to a remittance from a user of the terminal to a first user based on a remittance request) via the control unit 11 based on an input to a remittance reminder display (not limiting, an example of a second display based on the second information) displayed on the display unit 24 of the terminal 20 of the remittance request destination user.
As an example of the effect of the modified example obtained by such a configuration, a remittance process can be executed by the control unit of the server based on input to a second display displayed on the display unit of the terminal, making it possible to easily realize a remittance from the user of the terminal to the first user.

<Second Modification Example (1)>
The user interface of the display screen of the payment application described in the second embodiment, the functions of the payment application, etc. can be modified as appropriate.

By way of example and not limitation, FIG. 2-13 illustrates a remittance request list screen displayed on the terminal 20 of user (B.B.).
On this remittance request list screen, as an example and not a limitation, below the title "Remittance Request List" is displayed a remittance request history of past remittance requests made to the terminal user (B.B.) for which the remittance process has not yet been completed.

In this example, based on the fact that the user (B.B) of terminal 20 has received remittance request information from the first user A.A, area R21 displays an icon image and user name of A.A, an icon with the text "Request Received", the date and time the remittance request information was received (2020.04.20 21:30), an icon with the text "Payment" indicating that the user is in a position to make a payment to A.A, and the amount to be paid to A.A (3,000 yen).

In addition, because the user (B.B) of terminal 20 has also received remittance request information from the first user D.D, area R23 displays information about the remittance request from D.D. In this example, the date and time of receipt of the remittance request information from D.D is 2020.04.21 08:42, and the amount to be paid to D.D is "500 yen."

For the remittance request from A.A, one of the multiple first users (A.A, B.B), terminal 20 has received the remittance reminder information after receiving the remittance request information. Based on this, in area R22 (not limited to this, an example of a display area for the remittance reminder information corresponding to the display area for the remittance request information) below area R21, an icon image and user name of A.A, an icon with the text "Remind Received", the date and time when the remittance reminder information was received (2020.04.23 17:00), an icon with the text "Payment" indicating that the user is in a position to make a payment to A.A, and the amount to be paid to A.A (3,000 yen) are displayed.

The information displayed in area R21 and the information displayed in area R22 are based on the same remittance request information, so the icon with the word "Payment" indicating that the person is in the position to make a payment to A.A. and the amount to be paid to A.A. (3,000 yen) are the same.

However, unlike region R21, region R22 displays an arrow indicating that the information is related to the information displayed in region R21. Also, A.A's icon image, user name, and the icon with the text "Receive Remind" in R22 are displayed to the right of A.A's icon image, user name, and the icon with the text "Receive Request" in region R21, respectively.

As a non-limiting example, the display positions of at least some of the information (as a non-limiting example, the image icon and user name of the first user and the icon displayed above them) are different between the information displayed in area 21, which is displayed based on the remittance request information received by terminal 20, and the information displayed in area 22, which is displayed based on the remittance reminder information based on the remittance request information, making it easier for the user to understand the correspondence between the remittance request and the remittance reminder.

By way of example and not limitation, the information displayed as the remittance request history may be sorted by operations of the user of the terminal 20 .
When the user taps on a blank area on the screen displaying the remittance request history shown in FIG. 2-13, a sort item selection area SR is displayed as shown in FIG. 2-14.

At the top of the sort item selection area SR, information (for example, but not limited to, the words "reorder requests") is displayed to notify that sorting will be performed based on the items shown below.
Below this are displayed a button BTS1 for sorting based on the date and time of receipt of the remittance request information or remittance reminder information, a button BTS2 for sorting based on the remittance amount (by way of example and not limitation, the amount requested to be remitted by the remittance request information or remittance reminder information), and a button BTS3 for sorting based on the user names registered as friends in the payment application or a messaging application linked to the payment application.

As a non-limiting example, a user (one account) of one terminal 20 performs a process to add a user (another account) of another terminal 20 as a friend from his/her own terminal 20, and the server 10 executes a process to add and register the friend (friend addition process, friend registration process), thereby making it possible to send and receive messages between the terminals 20 registered as friends via the server 10. An account of a messaging application owned by an individual user is called a "general account." A history of messages sent and received between terminals 20 of users who own general accounts is displayed as a talk room or the like on the display unit 24 of the terminal 20.

As an example and not a limitation, when a user (B.B) of terminal 20 taps button BTS3, the information displayed as the remittance request history is sorted as shown in FIG. 2-15, and the user names of users (A.A and D.D, as an example and not a limitation) who are registered as friends of the first user (A.A and D.D, as an example and not a limitation) who made the remittance request are displayed in alphabetical order.
In this example, an icon image and user name of a first user, A.A., are displayed in region R21, and an icon image and user name of a first user, B.B., are displayed in region R22.

The example shown in Figure 2-15 differs from the example shown in Figure 2-14 in that after sorting, neither the ``request received'' icon nor the ``reminder received'' icon is displayed as information about the first user, the date and time of receipt of the remittance request information and the date and time of receipt of the remittance reminder information are displayed, and no information regarding the remittance amount is displayed.
The screen shown in FIG. 2-15 is configured so that at least the first user who has made the remittance request can be identified.

On the screen shown in Figure 2-15, when a user (B.B) of terminal 20 taps on area R21 corresponding to a first user (A.A. as an example and not a limitation) who is registered as a friend, detailed information regarding the remittance request of the selected first user (A.A.) is displayed, as shown in Figure 2-16.
Area R20 at the top of the screen displays information notifying the user that this is a history of remittance requests from the selected first user (A.A.) (for example and not limitation, the words "List of remittance requests from A.A."), and below that, detailed history of remittance requests from the selected first user (A.A.) is displayed in the manner shown in Figure 2-13.

As an example and not as a limitation, each piece of information displayed in areas R21 and R22 of FIG. 2-13 (which are, but are not limited to, an example of a display based on remittance request information and an example of a display based on remittance reminder information) is displayed in areas R21 and R22 of FIG. 2-16.
It should be noted that the history of remittance requests from other first users (D.D.) who have not been selected is not displayed.

As an example and not a limitation, when a user (B.B) of terminal 20 taps button BTS1 on the screen of FIG. 2-14, the information displayed as the remittance request history is sorted as shown in FIG. 2-17, and the history (not a limitation, an example of a display based on remittance request information, an example of a display based on remittance reminder information) of the first user (A.A and D.D., as an example and not a limitation) who made the remittance request is displayed based on the date and time of receipt.

In this example, the most recent history is a history based on remittance reminder information (received date and time 2020.04.23 17:00) corresponding to a remittance request of 3,000 yen by the first user A.A., so the top region R21 displays a "Receive Reminder" icon along with A.A.'s icon image and user name.
Since the next most recent history is based on remittance request information (received date and time 2020.04.21 08:42) corresponding to a remittance request of 500 yen by another first user B.B, the second region R22 from the top displays a "request received" icon along with the icon image and user name of B.B.
Since the next most recent history is based on remittance request information (received date and time 2020.04.20 21:30) corresponding to a remittance request of 3,000 yen by the first user A.A, the third region R23 from the top displays a "request received" icon along with the icon image and user name of A.A.

The information displayed in area R21 and the information displayed in area R23 are both information relating to a common remittance request from one first user (A.A.).
However, after receiving the remittance request information based on the first remittance request of one first user (A.A), remittance request information based on the second remittance request of the other first user (D.D), and then remittance reminder information based on the first remittance request of one first user (A.A), is received. Therefore, information corresponding to the second remittance request is displayed in area R22, which is the area between area R21 in which information corresponding to the first remittance request is displayed and area R23 in which information corresponding to the first remittance request is displayed.

As an example and not a limitation, as shown in FIG. 2-18, a friend registration confirmation screen is displayed on the terminal 20 of the user (B.B) who is the target of the remittance request or remittance reminder to confirm whether the first user who made the remittance request or remittance reminder is a user who is registered as a friend in the payment application or a messaging application linked to the payment application.

As a non-limiting example, when a user (B.B) of terminal 20 taps on the link information for remittance displayed in area RM1 on the screen shown in Figure 2-7, the friend registration confirmation screen of Figure 2-18 is displayed before transitioning to the remittance screen of Figure 2-8.
As an example and not as a limitation, the friend registration confirmation screen is a screen superimposed on the screen of Figure 2-7, and displays a message (as an example and not as a limitation, "Please check again whether the person who requested the money transfer is a friend. Do you want to proceed with the transfer?") to allow the user of terminal 20 (B.B) to confirm whether the person to whom the money transfer is being made (as an example and not as a limitation, the first user with the username (A.A) displayed in RM1) is registered as a friend.

When the user (B.B.) of the terminal 20 taps the confirmation button BT7 on the friend registration screen, the screen transitions to a remittance screen shown in FIG. 2-8.
In this way, even if the link information for remittance is tapped, a screen is displayed before transitioning to the remittance screen, prompting the user to confirm whether or not the first user who sent the remittance reminder is a user registered as a friend, thereby preventing the user from inadvertently remitting money to a user who is not registered as a friend.

<Second Modification Example (2)>
In relation to the first modified example (2), the remittance request destination user's terminal 20 may execute a reminder notification process based on receiving the remittance reminder information. This reminder notification process may be realized by any of the following methods, for example and not by way of limitation:

Upon receiving remittance reminder information that is push-transmitted from the server 10, control is performed so that a push notification is displayed on the display unit 24.
The control unit 21 controls the sound output unit 26 to output a predetermined sound.
The control unit 21 controls a vibration unit (not shown) to vibrate the housing of the terminal 20 .
The control unit 21 controls the light emitting unit (not shown) to emit a predetermined light.

By way of example and not limitation, "push transmission" means that the information to be sent (in this example, remittance reminder information) is sent in such a way that a push notification is sent to the destination device (in this example, the server 10) that the information has been sent from the source device, or received by the destination device (in this example, the terminal 20 of the user to whom the remittance request was made).

In addition to receiving remittance reminder information, it is also possible to set reminder notification conditions similar to those in the first variant example (2), and execute the reminder notification process based on the fulfillment of the reminder notification conditions.

In this modified example, the terminal 20 of the remittance request destination user performs a reminder notification process (not limiting, but an example of a notification process by a terminal) by the control unit 21 based on the reception of remittance reminder information by the communication I/F 22. In this case, the reminder notification process is configured to be processed by the control unit 21 based on the set reminder notification condition (not limiting, but an example of a second condition).
As an example of an effect of the modified example obtained by such a configuration, it is possible to notify the user of the terminal at an appropriate timing based on the second condition that the second information has been received.

<Third Example>
The third embodiment is an embodiment relating to the method and timing of displaying and transmitting remittance reminder information.
The contents described in the third embodiment are applicable to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

FIG. 3A is a diagram showing an example of a timing chart for explaining the method and timing of displaying a remittance reminder on the terminal 20 of the remittance request destination user in this embodiment.
Here, the timing of displaying a remittance reminder on the terminal 20 of the remittance request destination user in the case where the terminal reminding technique described in the first embodiment is applied will be described.

In this timing chart, the horizontal axis is the time axis, and indicates the timing when the remittance request display and remittance reminder display are performed by the terminal 20 of the remittance request destination user. Remittance request information is indicated by a white circle, and remittance reminder information is indicated by a white diamond.

One setting is "auto," which indicates that the terminal 20 of the remittance request destination user automatically displays remittance reminder information.
In this setting, the terminal 20 of the remittance request destination user displays a remittance reminder every time the set time tm has elapsed since the remittance request was displayed, as an example and not a limitation.

In addition, differently from this, the terminal 20 of the remittance request destination user may, for example and not by way of limitation, display a remittance reminder each time a set time tm has elapsed since receiving the remittance request information from the server 10, or may not.

<Effects of the Third Embodiment>
In this embodiment, remittance request information (an example of first information, not limiting) is transmitted to the terminal 20 of the remittance request destination user via the server 10 based on input by a remittance master user (an example of a first user, not limiting) to the remittance master user's terminal 20.
In addition, the remittance reminder display (an example of a second display, not limiting) is configured to be displayed on the display unit 24 of the remittance request destination user's terminal 20 based on the time when the remittance request display (an example of a first display, not limiting) is displayed on the display unit 24 of the remittance request destination user's terminal 20, or the time when the remittance request information (an example of first information, not limiting) is received by the remittance request destination user's terminal 20.
As an example of an effect of an embodiment obtained by such a configuration, the second display can be displayed on the display unit of the terminal at an appropriate timing based on the time when the first display is displayed on the display unit of the terminal or the time when the first information is received by the terminal.

In this embodiment, the terminal 20 of the remittance request destination user displays a first remittance reminder display (not limiting, an example of a third display) on the display unit 24. Also, the terminal 20 of the remittance request destination user is configured to display a second remittance reminder display (not limiting, an example of a fourth display) on the display unit 24 based on the lapse of a set time since the display of the first remittance reminder display.
As an example of the effect of an embodiment obtained by such a configuration, the fourth display can be displayed on the display unit of the terminal based on the third display being displayed on the display unit of the terminal.

<Third Modification (1)>
The technique of the third embodiment can also be applied to the server reminder technique described in the second embodiment.

FIG. 3B is a diagram showing an example of a timing chart for explaining the server reminder in this modified example.
The diagram can be read in the same way as in Figure 3-1, but the diamonds corresponding to manually sent remittance reminder information are shown in "gray", while the diamonds corresponding to automatically sent remittance reminder information are shown in "white".

Setting A is "Manual", which is a setting in which the server 10 transmits remittance reminder information to the terminal 20 of the remittance request destination user based on a remittance reminder execution input being made on the terminal 20 of the remittance master user. Specifically, the server 10 transmits remittance reminder information to the terminal 20 of the remittance request destination user based on receiving remittance reminder transmission request information from the terminal 20 of the remittance master user.

Setting B is "Auto", which is a setting in which the server 10 automatically sends remittance reminder information to the terminal 20 of the remittance request destination user, regardless of the terminal 20 of the remittance master user. Specifically, the server 10 sends remittance reminder information to the terminal 20 of the remittance request destination user every time a set time tn has elapsed since sending the remittance request information to the terminal 20 of the remittance request destination user.

Setting C is "Auto & Manual", which is a combination of settings A and B. In this setting, the server 10 basically sends remittance reminder information according to setting B (Auto). However, if manual remittance reminder information is sent between automatic remittance reminder information sending, the automatic remittance reminder information sending will be delayed.

Specifically, by way of example and not limitation, the server 10 basically transmits remittance reminder information to the terminal 20 of the remittance request destination user each time a set time tn has elapsed since the remittance request information was transmitted to the terminal 20 of the remittance request destination user. However, if manual remittance reminder information is transmitted between automatic remittance reminder information transmissions, the server 10 transmits remittance reminder information each time a set time tn has elapsed since the latest manual remittance reminder information transmission, instead of the latest automatic remittance reminder information transmission timing.

As a non-limiting example of which of settings A to C is applied, information regarding the setting can be sent to the server 10 based on input by the remittance master user to his/her terminal 20, and the setting can be set by the server 10.

However, without being limited to this, the above settings may or may not be made on the server 10 side based on input from the payment service provider, the administrator of the server 10, etc.

In this modified example, remittance request information (an example of first information, not limiting) is transmitted to the terminal 20 of the remittance request destination user via the server 10 based on input by the remittance master user (an example of the first user, not limiting) to the remittance master user's terminal 20.
In addition, remittance reminder information (an example of second information, not limiting) is sent by the server 10 to the terminal 20 of the remittance request destination user, and a remittance reminder display (an example of a second display, not limiting) is displayed on the display unit 24 of the terminal 20 of the remittance request destination user based on the remittance reminder information.
As an example of the effect of the embodiment obtained by such a configuration, the first information can be transmitted to the terminal via the server in response to the intention of the first user who has requested the remittance, and the second information can be transmitted from the server to the terminal, and then a second display can be displayed on the display unit of the terminal based on the second information.

In addition, this modified example shows a configuration in which the remittance reminder information is sent to the terminal based on the elapse of a set time since the remittance request information was sent to the terminal 20 of the remittance request destination user (as an example, but not limited to, based on the time when the first information was sent to the terminal or the time when the first information was received by the terminal).
As an example of an effect of an embodiment obtained by such a configuration, it is possible to transmit the second information to the terminal at an appropriate timing based on the time when the first information is transmitted to the terminal or the time when the first information is received by the terminal.

In addition, in the above, in this modified example, the terminal 20 of the remittance request destination user receives first remittance reminder information (not limiting, an example of third information based on a remittance request) transmitted from the terminal 20 of the remittance master user based on an input by the remittance master user (not limiting, an example of a first user) to the terminal 20 of the remittance master user via the communication I/F 22. Then, the terminal 20 of the remittance request destination user displays a first remittance reminder display (not limiting, an example of a third display) on the display unit 24. In this case, as an example and not limiting, a configuration is shown in which second remittance reminder information (not limiting, an example of second information) is transmitted to the terminal 20 based on the lapse of a set time since the first remittance reminder information was transmitted.
As an example of an effect of an embodiment obtained by such a configuration, it is possible to appropriately transmit second information based on a remittance request to a terminal based on third information based on a remittance request being transmitted to the terminal.

<Third Modification (2)>
Regarding the terminal reminder method (setting: auto) described in the third embodiment, it is also possible to set different times for the display of the first remittance reminder information and the display of the second or subsequent remittance reminder information.

Specifically, as an example and not by way of limitation, the terminal 20 of the remittance request destination user displays a first remittance reminder when a first set time has elapsed since the remittance request was displayed or the remittance request information was received.
Furthermore, the terminal 20 of the remittance request destination user displays a second remittance reminder when a second set time has elapsed since the first display.
Furthermore, the terminal 20 of the remittance request destination user displays a third remittance reminder when a third set time has elapsed since the second display.
The same applies below.

In this case, by way of example and not limitation, the first set time can be the longest time.

As an example, the first set time can be "24 hours", and the other set times (second set time, third set time, ...) can be shorter than "24 hours". In this case, the other set times can all be the same time or different times.

When the time is set to be different, by way of example and not limitation, the set time may be shortened each time the remittance reminder display is performed.
Specifically, by way of example and not limitation, the first set time may be "24 hours", the second set time may be "18 hours", the third set time may be "12 hours", . . .
By doing this, the time interval (display time interval) for displaying a remittance request becomes gradually shorter, making the remittance request recipient user aware that the remittance has not yet been completed and alerting him or her to complete the remittance quickly.

Note that, conversely to the above, the first set time may or may not be the shortest time.

The above contents can also be applied to the time interval (transmission time interval) for sending remittance reminder information in the server reminder described in Figure 3-2.

In addition, in setting C (auto & manual) in FIG. 3-2, when manual remittance reminder information is sent between automatic remittance reminder information sent by server 10, the automatic remittance reminder information may or may not be skipped rather than being delayed.

<Fourth Example>
The fourth embodiment relates to conditions for carrying out a remittance reminder.
The contents described in the fourth embodiment are applicable to the other embodiments and the other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

In this embodiment, the method of terminal reminding described in the first embodiment is applied, and a case is described in which the terminal 20 of the remittance request destination user determines whether the remittance reminder conditions are met and performs the terminal reminder.

FIG. 4A is a flowchart showing an example of the flow of processes executed by each device in this embodiment.
This flowchart corresponds to the processing portion of FIG. 1-14 in the flowcharts of FIGS. 1-13 to 1-14.

After B140 in FIG. 1-13, the control unit 21 of the terminal 20B determines whether the remittance reminder condition is met (B450). If it is determined that the condition is met (B450: YES), the control unit 21 of the terminal 20B moves the process to B150.

FIG. 4B is a diagram showing an example of remittance reminder condition data that defines remittance reminder conditions in this embodiment.
In the remittance reminder condition data, by way of example and not limitation, a category and a remittance reminder condition are defined in association with each other.

Categories include, by way of example and not limitation, divisions based on different concepts such as "time," "balance," "deposit (transfer)," and "other."

The remittance reminder conditions include, by way of example and not limitation, a condition number indicating the number of the condition and the content of the remittance reminder conditions for that condition number.

A specific example will be given for explanation.
(1) Category "Time"
For condition No. "PA-1," the remittance reminder condition is set to "the time reaches the set time." The set time can be set to any time of day (for example, midnight or noon, but is not limited to this).
This condition is intended to inform the user that a remittance has not yet been made by displaying a remittance reminder on the display unit 24 at the timing when the current time reaches the set time each day.

In this case, the control unit 21 of the terminal 20 can determine whether the time measured by the clock unit 29A has reached the set time, and if so, can cause the display unit 24 to display a remittance reminder message.

For condition No. "PA-2," the remittance reminder condition is set as "the time for the reminder has come and the time is included in the first set time period." The first set time period can be set to any set time period each day.
This condition is intended to inform the user that the remittance has not yet been made by displaying a remittance reminder on the display unit 24 if the current time falls within the set time period when the time comes for a terminal reminder to be sent.

As a non-limiting example, a time period during which a user is likely to view the terminal 20, such as, for example and not for limitation, a time period between 9 p.m. and midnight, during which a user is likely to return home and spend his free time, can be set as the first set time period.

Regarding the timing of the terminal reminder when this condition is applied, the timing described in the third embodiment (FIG. 3A) can be applied as an example and not a limitation.
In this case, the control unit 21 of the terminal 20 judges whether it is time to perform a terminal reminder. If it is time to perform a terminal reminder, the control unit 21 judges whether the time measured by the clock unit 29A is included in the first set time period, and if it is judged that it is included, the control unit 21 can cause the display unit 24 to display a remittance reminder message.

For condition No. "PA-3," the remittance reminder condition is set as "the time for the reminder has come and the time is not included in the second set time period." The second set time period can be set to any set time period each day.
This condition is intended to inform the user that the remittance has not yet been made by displaying a remittance reminder on the display unit 24 if the current time is not within the set time period when the time for a terminal reminder arrives.

By way of example and not limitation, the second set time period can be set to a time period when the user is unlikely to view the terminal 20, such as late at night (until midnight the following day) when the user is likely to be asleep, before dawn (until 3 the following day), or before dawn (from 3 the following day).

Regarding the timing of the terminal reminder when this condition is applied, the timing described in the third embodiment (FIG. 3A) can be applied as an example and not a limitation.
In this case, the control unit 21 of the terminal 20 judges whether it is time to perform a terminal reminder. If it is time to perform a terminal reminder, the control unit 21 judges whether the time measured by the clock unit 29A is included in the second set time period, and if it is judged not to be included, the control unit 21 can cause the display unit 24 to display a remittance reminder message.

For condition No. "PA-4," the remittance reminder condition is set to "the date is the set date." In this case, the date can be set to any date (for example, "the 15th of every month" or "the 25th of every month," without any limitation).
This condition is intended to inform the user that the remittance has not yet been made by displaying a remittance reminder on the display unit 24 when the current date becomes the set date.

As a non-limiting example, the date on which the remittance request recipient user has spare cash can be set, and as a non-limiting example, the date on which salary is paid (payday).

In this case, the control unit 21 of the terminal 20 can determine whether the current date has reached the set date based on the timekeeping information of the clock unit 29A, and if it determines that the current date has reached the set date, can cause the display unit 24 to display a remittance reminder message.

(2) Category "Balance"
For condition No. "PB-1," the remittance reminder condition is set to "electronic money account balance is equal to or greater than a set amount." The set amount can be set to any amount (for example, "30,000 yen" and is not a limitation).
This condition is intended to inform the user that a remittance has not yet been made by displaying a remittance reminder on the display unit 24 when the balance of the electronic money account reaches or exceeds a set amount.

By way of example and not limitation, the set amount can be set to a relatively large amount, such as more than twice the maximum remittance request amount for the remittance request destination user, or 30,000 yen or more.

In this case, by way of example and not limitation, the control unit 21 of the terminal 20 inquires, via the communication I/F 22, about the electronic money account balance of the user of the terminal 20. Upon receiving an inquiry about the electronic money account balance from the terminal 20 via the communication I/F 14, the control unit 11 of the server 10 transmits information about the electronic money account balance of the user to the terminal 20 via the communication I/F 14.
Then, the control unit 21 of the terminal 20 determines whether or not the electronic money account balance has reached a set amount based on the received electronic money account balance information, and if it determines that the electronic money account balance has reached a set amount, it can cause a remittance reminder message to be displayed on the display unit 24.

For condition No. "PB-2," the remittance reminder condition is set to "the balance is equal to or greater than a set amount." The set amount can be set to any amount (for example, "30,000 yen" and is not a limitation).
This condition is intended to inform the user that the remittance has not yet been made by displaying a remittance reminder on the display unit 24 when the remaining balance entered by the user into the terminal 20 becomes equal to or exceeds a set amount.

In this case, the control unit 21 of the terminal 20 causes the user to input the balance by, for example, displaying a screen on the display unit 24 that prompts the user to input the balance. Then, it determines whether the input balance is equal to or greater than a set amount, and if it determines that the balance is equal to or greater than the set amount, it can cause the display unit 24 to display a remittance reminder message.

(3) Category "Deposit (Remittance)"
For condition number "PC-1", the remittance reminder condition is set to "receive payment by taking out a loan".
This condition is intended, by way of example and not by way of limitation, to inform a user that a remittance has not yet been made by displaying a remittance reminder on display unit 24 at the time a deposit is made to a bank or electronic money account balance when the user uses a loan service, by way of example and not by way of limitation a service provided by a loan service provider, which allows a user to borrow a loan using an application related to physical currency or electronic currency, such as a loan application.

The loan service operator may be the same operator as the payment application operator and messaging service operator mentioned above, or may be a different operator, by way of example and not limitation.
If different operators are used, the loan service operator can partner with the payment application operator and the messaging service operator and provide information regarding the loan amount of the user of terminal 20 to the payment application operator and the messaging application operator, for example by sending the information to server 10.

As a non-limiting example, a remittance reminder condition can be set as a situation in which the remittance request destination user has financial leeway due to a deposit (remittance) from a loan service provider into the balance of the remittance request destination user's bank (for example, but not limited to, an online bank) or electronic money account of a payment application.

In this case, the control unit 21 of the terminal 20 determines, by way of example and not limitation, whether or not the loan has been received based on information (including notifications) sent from the server 10. If it is determined that the loan has been received, the control unit 21 can cause a remittance reminder to be displayed on the display unit 24.

For condition No. "PC-2," the remittance reminder condition is set as "receive payment when the put up product is purchased."
This condition is intended, by way of example and not by way of limitation, when a user uses a flea market service, by way of example and not by way of limitation a service provided by a flea market service operator, which allows the user to list and purchase items using an application such as a flea market application (hereinafter referred to as a "flea market application"), and the listed item is purchased and the money is deposited into the electronic money account balance, a remittance reminder message is displayed on display unit 24 to inform the user that the remittance has not yet been made.

As a non-limiting example, a remittance reminder condition can be set as a situation in which the remittance request destination user has a financial surplus as a result of a deposit (remittance) from a flea market application being made to the balance of the electronic money account of the payment application of the remittance request destination user.

In this case, the control unit 21 of the terminal 20 determines whether or not a payment has been received by purchasing an item put up for sale in the flea market application, based on information (including notifications) sent from the server 10. If it is determined that a payment has been received, the control unit 21 can cause a remittance reminder to be displayed on the display unit 24.

(3) Category "Other"
For condition number "PD-1", the content of the remittance reminder condition is set as "the put up product has been purchased (payment not yet made)".
This condition is intended, by way of example and not of limitation, to inform the user that the remittance has not yet been made by displaying a remittance reminder on the display unit 24 at the time when an item put up for sale by the user via a flea market application or the like is purchased (at the time when the money has not yet been deposited in the electronic money account balance).

As a non-limiting example, if a product that the remittance request destination user has listed via a flea market application or the like is purchased, the remittance request destination user's electronic money account balance may be expected to be credited, even though it has not yet been credited via the flea market application, due to the purchase of the listed product. Therefore, the remittance reminder condition may be determined to include a case in which the remittance request destination user is expected to have some financial leeway.

In this case, the control unit 21 of the terminal 20 can determine whether or not the product put up for sale on the flea market application has been purchased based on information (including notifications) sent from the server 10, and if it is determined that the product has been purchased, can cause a remittance reminder to be displayed on the display unit 24.

For condition number "PD-2," the remittance reminder condition is set as "looking for work using a job search application."
This condition is intended to inform the user that a remittance has not yet been made by displaying a remittance reminder on the display unit 24 at a predetermined time during the period in which the user is searching for work in a service such as a job search service (job search application) (for example, but not limited to, when applying to a company or when receiving a job offer from the company, etc.).

As an example and not a limitation, if the remittance request destination user is seeking work in a job search service, etc., this can be determined as the content of the remittance reminder condition, since the remittance request destination user is looking for work when it is expected that the remittance request destination user will receive a wage after working and will have economic leeway.

In this case, the control unit 21 of the terminal 20 can determine whether or not a job search application is being executed on the terminal 20 itself, and if it is determined that a job search application is being executed, can cause a remittance reminder to be displayed on the display unit 24.

For condition No. "PD-3," the remittance reminder condition is set to "purchase an item through a flea market application."
This condition is intended to inform the user that the remittance has not yet been made by displaying a remittance reminder on the display unit 24 at the time the user purchases an item that has been put up for sale in a service such as a flea market application.

As a non-limiting example, when the remittance request destination user purchases an item through a flea market application or the like, and when the remittance request destination user purchases an item, the remittance reminder condition can be determined to be when the remittance request destination user is recognized to have financial leeway.

In this case, the control unit 21 of the terminal 20 can determine whether or not a product listed on the flea market application has been purchased based on information (including notifications) sent from the server 10, and if it is determined that the product has been purchased, can cause a remittance reminder to be displayed on the display unit 24.

The above remittance reminder conditions can be, by way of example and not limitation, set by the remittance request destination user's terminal 20 based on input by the remittance request destination user to his/her terminal 20, and stored in the memory unit 28 of the remittance request destination user's terminal 20.

In addition, as a non-limiting example, the remittance reminder conditions may or may not be set by the remittance master user's terminal 20 based on input by the remittance master user to his/her own terminal 20. In this case, as a non-limiting example, the remittance reminder conditions set by the remittance master user's terminal 20 may be transmitted and notified to the remittance request destination user's terminal 20 via the server 10, and stored in the memory unit 28 of the remittance request destination user's terminal 20.

In addition, when the remittance request destination user's terminal 20 determines whether the above remittance reminder conditions are met, it may determine whether one condition is met, or it may determine whether two or more conditions are met. In other words, it may make a determination by combining two or more conditions.

<Display screen>
Figure 4-3 shows, by way of example and not by way of limitation, an example in which a user (B.B) who has received remittance request information but has not yet completed the remittance makes a transaction using the flea market application described above, and a deposit is made in the user's (B.B) account in accordance with the sales amount.

The terminal 20 of the user (B.B.) receives a message MS25 from the official account of the payment application indicating that the transaction via the payment application has been completed.
By way of example and not limitation, this message MS25 includes the words "Transaction Completed" indicating that the transaction has been completed, the sales amount from the transaction (in this example, "1,600 yen"), an icon with the words "Receive" indicating that the user (B.B.) is in the position to receive the sales amount, and the date and time when the transaction was completed (in this example, 2020.0423 20:59).

When this message MS25 is displayed, it is highly likely that the user (B.B.) has at least an amount equivalent to the sales amount remaining in his/her electronic money account.

Next, the user (B.B.)'s terminal 20 receives a message MS26 from the official account of the payment application indicating that remittance reminder information has been received, as shown in FIG. 4-4.

The content of the message MS26 is similar to the content of the remittance reminder display MS4A described above, except that it contains an icon image of the official account instead of an icon image of the first user (A.A.).

For example and not for limitation, terminal 20 receives message MS26 immediately after receiving message MS25. Therefore, it can be said that there is a high possibility that user (B.B.) will check message MS26 when there is at least an amount equivalent to the sales amount remaining in the user's electronic money account.
By way of example and not limitation, the display of this message MS26 may prompt the user (B.B.) to immediately transfer funds based on the fact that a credit has been credited to his/her account.

<Effects of the Fourth Embodiment>
In this embodiment, a remittance reminder display (not limiting, an example of the second display) is configured to be displayed on the terminal 20 of the remittance request destination user based on the remittance reminder conditions (not limiting, an example of the first condition).
As an example of the effect of the embodiment obtained by such a configuration, the second display based on the remittance request can be appropriately displayed on the display unit of the terminal based on the set first condition.

In addition, in this embodiment, the remittance reminder conditions include conditions such as time, time period, date, and elapsed time (these are not limited to examples of conditions related to time).
As an example of the effect of the embodiment obtained by such a configuration, the second display based on the remittance request can be appropriately displayed on the display unit of the terminal based on a time-related condition.

In addition, in this embodiment, the remittance reminding condition includes a time or duration condition set by the terminal 20 (not limited to this, but an example of a terminal) of the remittance request destination user.
As an example of the effect of an embodiment obtained by such a configuration, a second display based on the remittance request can be displayed on the display unit of the terminal at an appropriate timing according to the wishes of the user of the remittance destination.

In addition, this embodiment shows a configuration in which the remittance reminding condition includes a time or duration condition set by the remittance master user terminal 20 (not limited to, but an example of the terminal of the first user).
As an example of the effect of an embodiment obtained by such a configuration, a second display based on a remittance request can be displayed on the display unit of the terminal at an appropriate timing according to the wishes of the first user who made the remittance request.

In addition, in this embodiment, the remittance reminder conditions include conditions related to the balance of the remittance request destination user, such as the electronic money account balance or possessed balance (not limited to this, an example of a balance associated with the terminal user).
As an example of the effect of an embodiment obtained by such a configuration, a second display based on the remittance request can be displayed on the display unit of the terminal at an appropriate timing depending on the balance of the user receiving the remittance request.

In addition, in this embodiment, the remittance reminding conditions include conditions regarding depositing (remittance) to the remittance request destination user.
As an example of the effect of the embodiment obtained by such a configuration, a second display based on a remittance request can be displayed on the display unit of the terminal, based on conditions related to remittance to the user of the terminal.

In addition, this embodiment shows a configuration in which the conditions regarding the deposit (remittance) to the remittance request destination user include that the deposit (remittance) is made by the remittance request destination user taking out a loan.
As an example of the effect of an embodiment obtained by such a configuration, a second display based on a remittance request can be displayed on the display unit of the terminal at a time when the user of the terminal is likely to have some extra money by taking out a loan.

In addition, this embodiment shows a configuration in which the conditions regarding the deposit (remittance) to the remittance request destination user include the deposit (remittance) to the remittance request destination user by the purchaser of a product listed by the remittance request destination user upon purchase of the product.
As an example of the effect of an embodiment obtained by such a configuration, a second display based on a remittance request can be displayed on the display unit of the terminal at a time when it is highly likely that the user of the terminal has some spare money after an item put up for sale by the user of the terminal is purchased and the buyer makes a payment (remittance).

In addition, in this embodiment, the remittance request conditions include a condition regarding the purchase of a product put up for sale by the remittance request destination user.
As an example of the effect of an embodiment obtained by such a configuration, a second display based on a remittance request can be displayed on the display unit of the terminal when a product listed by the terminal user is purchased, resulting in the terminal user having an expected amount of extra money.

<Fourth Modification (1)>
It is also possible to apply the server reminding method described in the second embodiment, so that the server 10 determines whether the remittance reminding conditions are met and then performs the server reminding.

In this case, basically, the same conditions as the remittance reminder conditions exemplified in the table in FIG. 4-2 can be applied. However, in this modified example, the server 10, not the terminal 20, determines the remittance reminder conditions.

The condition for the category “time” can be determined by the control unit 11 of the server 10 based on the timekeeping information of the clock unit 19 .
In this case, with regard to the timing of the reminder when applying condition No. “PA-2” or condition “PA-3”, the timing of the server reminder described in the third variant example (1) (Figure 3-2) can be applied as an example and not a limitation.

The conditions for the category "Balance" can be determined by the control unit 11 of the server 10 based on information about the balance of the electronic money account of the user of the terminal 20 that is stored and managed in the memory unit 15, and information about the balance on hand that is entered on the terminal 20 and transmitted to the server 10.

The conditions for the category "Deposit (Remittance)" can be determined by the control unit 11 of the server 10 based on whether the information on the balance of the electronic money account of the user of the terminal 20, which is stored and managed in the memory unit 15, has been updated by the remittance settlement process.

Regarding the conditions in the category "Other," condition No. "PD-1" can be determined by the control unit 11 of the server 10 detecting that an item listed by a user of the terminal 20 has been purchased using the flea market service if the flea market service is provided as one of the payment services.
In addition, if the business providing the flea market service is different from the business providing the payment service, this can be determined by configuring the control unit 11 of the server 10 to obtain information indicating that the item put up for sale by the user of the terminal 20 has been purchased from a device such as a server of the business providing the flea market service.

If a job search service is provided as one of the payment services, the condition No. "PD-2" can be determined by the control unit 11 of the server 10 detecting that a user of the terminal 20 is searching for job search information using the job search service.
In addition, if the provider providing the job-search service is different from the provider providing the payment service, this can be determined by configuring the control unit 11 of server 10 to obtain information indicating that the user of terminal 20 is using the job-search service from a device such as a server of the provider providing the job-search service.

If a flea market service is provided as one of the payment services, the condition No. "PD-3" can be determined by the control unit 11 of the server 10 detecting that a user of the terminal 20 has purchased an item listed for sale using the flea market service.
In addition, if the business providing the flea market service is different from the business providing the payment service, this can be determined by configuring the control unit 11 of the server 10 to obtain information indicating that the user of the terminal 20 has purchased an item being sold from a device such as a server of the business providing the flea market service.

FIG. 4-5 is a flowchart showing an example of the flow of processes executed by each device in this modified example.
This flowchart is a rewritten version of the process shown in FIG.

After S150 in FIG. 1-13, the control unit 11 of the server 10 determines whether the remittance reminder condition is met (S460). If it is determined that the condition is met (S460: YES), the control unit 11 of the server 10 proceeds to S270.

When remittance reminder information is received from server 10 via communication I/F 22, control unit 21 of terminal 20B executes processing on B250.

In this modified example, based on whether a remittance reminder condition (not limiting, an example of a first condition) is met, the terminal 20 of the remittance request destination user receives remittance reminder information (not limiting, an example of second information based on a remittance request) via the communication I/F 22. The remittance reminder display is configured to be displayed on the display unit 24 of the terminal 20 of the remittance request destination user based on the reception of the remittance reminder information.
As an example of the effect of the embodiment obtained by such a configuration, the second information based on the remittance request can be received and displayed by the terminal based on the first condition. Also, since the terminal does not need to determine whether the first condition is satisfied, the processing load on the terminal can be reduced.

<Fourth Modification (2)>
In the fourth variant example (1), the remittance reminder conditions determined by the control unit 11 of the server 10 may or may not include “receiving remittance reminder sending request information from the remittance master user's terminal.”
The process in this case can be realized by combining the process in FIG. 2-12 and the process in FIG.

Fifth Example
The fifth embodiment is an embodiment in which the remittance request display and the remittance reminder display described above are displayed in a chat room available through a chat service.
The contents described in the fifth embodiment are applicable to the other embodiments and the other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

In this embodiment, the chat service is a messaging service (for example, but not limited to, an instant messaging service (IMS)), and a remittance request display and a remittance reminder display are provided by a messaging application installed on the terminal 20.
In addition, a talk room will be exemplified below as a chat room when a messaging service (messaging application) is applied.

<Display screen>
In the following example, assume that A.A, B.B, and C.C, who are users of both a messaging application and a payment application, all belong to group X and are registered as friends.

In the example of FIG. 5-1, messages exchanged between friends in a talk room (not limited to a chat room) of group X are displayed on the display unit 24 of the terminal 20 of user A.
In this example, A.A has sent a message to B.B and C.C requesting them to remit money, and B.B and C.C have confirmed the message (read 2).
That is, A.A is an example of a first user who made a remittance request, and B.B and C.C are examples of users of the terminal 20 that received the remittance request information.

This example shows a state in which a user C.C. of one terminal 20 has replied that he has sent money, but there has been no reply from a user B.B. of the other terminal 20.
When A. A taps the remittance icon in the bottom right of the icons displayed at the bottom of the chat room, a remittance item selection area SMR is displayed in the chat room.

At the top of the remittance item selection area SMR is displayed information (as an example, and not as a limitation, the words "Remittance Menu") informing the user that by operating the button shown below, processing based on a remittance-related function will be performed.
Below this are displayed a button BTM1 for sending money to other users, a button BTM2 for sending money remittance request information to other users, and a button BTM3 for displaying the history of money remittance requests.

As an example and not by way of limitation, when a first user, A.A., taps button BTM3, a history of past remittance requests from A.A. that have not yet been processed is displayed in the chat room.

In this example, the first user (A.A.) has sent remittance request information to B.B., the user of terminal 20, but the remittance process for this remittance request has not yet been completed. Based on this, the icon image and user name of B.B., an icon with the text "Request Sent", the date and time when the remittance request information was sent (2020.04.20 21:30), an icon with the text "Received" indicating that the first user is in the position to receive payment from B.B., and the amount to be received from B.B. (3,000 yen) are displayed in area R1.

In this example, an area RR displaying "Remind" is provided at the bottom of the screen. When the first user (A.A) checks the check box in area R21, each piece of information displayed in area R21 is selected.
By tapping area RR in this state, remittance reminder information based on the information displayed in area R1 is sent to terminal 20 of user (B.B.) to whom the remittance request information was to be sent.

Figure 5-2 shows, by way of example and not limitation, the relationship between a message displayed on the terminal 20 of a first user (A.A) belonging to group X, a message displayed on the terminal 20 of a user (B.B) who is the target of a remittance reminder from the first user, and a message displayed on the terminal 20 of a user (C.C) who is not the target of a remittance reminder from the first user.

The message MS11 is displayed on the terminal 20 of the first user (A.A) as a message sent by the first user (A.A) based on the remittance reminder information being sent to the terminal 20 of B.B.

By way of example and not of limitation, message MS11 includes an icon with the text "Sent Reminder" indicating that a remittance reminder has been sent to a user in the group, the text [Payment App] indicating that the message is based on a function of a payment application, the user name of the user in the group who received the remittance reminder (in this example, the text "Request for remittance to B.B"), the amount requested to be remitted via the remittance reminder (in this example, 3,000 yen), and an icon with the text "Receive" indicating that you (A.A) are the one receiving the payment.

By way of example and not limitation, a remittance button BT11a containing the words "Remit" and a button BT11b containing the words "Decline" are displayed at the bottom of the message MS11.
Here, even if the first user (A.A.) taps the remittance button BT11a, since the remittance destination for this message MS11 is himself (A.A.), the remittance screen will not be displayed and the remittance process will not be executed.
Therefore, the remittance button BT11a is displayed in an unselectable state since the remittance process is not executed in response to the operation.

Furthermore, even if the first user (A.A.) taps button BT11b, since the recipient of this message MS11 is himself (A.A.), a message indicating that the remittance has been declined will not be sent to other users.
Therefore, the button BT11b is displayed in an unselectable state since no message is sent in response to the operation of the button BT11b.

On the terminal 20 of B.B, which received the remittance reminder information, a message MS21 is displayed as a message from the first user (A.A) based on the fact that the remittance reminder information was sent from the first user (A.A).

By way of example and not limitation, message MS21 includes an icon with the text "Received Reminder" indicating that a remittance reminder has been received from a user in the group, the text [Payment App] indicating that the message is based on the functionality of a payment application, the user name of the user (yourself) in the group who received the remittance reminder (in this example, the text "Request for remittance to B.B."), the amount requested to be remitted in the remittance reminder (in this example, 3,000 yen), and an icon with the text "Payment" indicating that you (B.B.) are the one making the payment.

By way of example and not limitation, a remittance button BT21a containing the words "Remit" and a button BT21b containing the words "Decline" are displayed at the bottom of the message MS21.
When the user (B.B.) of the terminal 20 taps the remittance button BT21a, the screen transitions to the remittance screen described above, where the remittance process can be executed.

That is, the remittance destination for this message MS21 is the first user (A.A) whose image icon and user name are displayed corresponding to the message MS21, so by operating the remittance button 21a, an amount equivalent to the requested remittance amount (3,000 yen in this example) is remitted from the account of B.B to the account of A.A.
Therefore, since the remittance button BT21a executes a remittance process in response to an operation, it is displayed in a selectable manner different from the remittance button BT11a described above and the remittance button 31a described later.

Furthermore, when the user (B. B) of the terminal 20 taps the button BT21b, a message indicating that the remittance has been declined is sent to the first user (A. A) associated with the message MS21.
Therefore, since the button BT21b transmits a message in response to the operation, it is displayed in a selectable manner different from the above-mentioned button BT11b and the button 31b described later.

On the terminal 20 of another user (C.C), who is neither the first user (A.A) nor the user (B.B) who is the target of the remittance reminder, a message MS31 is displayed as a message sent by the first user (A.A) based on the remittance reminder information sent by the first user A.A to B.B.

By way of example and not of limitation, message MS31 includes an icon with the word "Remind" indicating that a remittance reminder has been sent from a user other than the user (first user A.A) to another user other than the user (B.B), the word [Payment App] indicating that the message is based on a function of a payment application, the user name of the user in the group who received the remittance reminder (in this example, the word "Remittance request to B.B"), the amount requested to be remitted by the remittance reminder (in this example, 3,000 yen), and an icon image of the first user (A.A) and an icon image of the user who received the remittance reminder (B.B).

Note that an arrow is displayed pointing from the icon image of the first user (A.A) to the icon image of the user (B.B) who received the remittance reminder information. This allows the other user (C.C) to recognize that the remittance reminder information has been sent from a different user (A.A) to a different user (B.B).

Also, by way of example and not limitation, message MS31 does not include either the "Send reminder" text icon included in message MS11 or the "Receive reminder" text icon included in message MS21. This allows the user to recognize that the remittance reminder related to message MS31 is not from the user to another user, nor is it from another user to the user.

By way of example and not limitation, at the bottom of the message MS31, a remittance button BT31a containing the words "Remit" and a button BT31b containing the words "Decline" are displayed in an unselectable manner.

Next, a case where a user (B. B) who has received the remittance reminder information pays the remittance request amount will be described with reference to FIG. 5-3.
When the remittance process to the first user (A.A) is completed based on the user (B.B) who is the target of the remittance reminder tapping the remittance button BT21a, a message MS12 is displayed on the terminal 20 of the first user (A.A) as a message from the user (B.B) who has completed the remittance, as shown in FIG. 5-3.

By way of example and not limitation, message MS12 includes the words [Payment App], the user name of the first user, the requested remittance amount to the first user, and a message indicating that payment of the requested remittance amount has been completed (in this example, the words "3,000 yen has been remitted to A.A.").

Also, a message MS13 is displayed as a message from the first user (A.A).
As an example and not as a limitation, message MS13 includes the words [Payment App], along with the username of the user who is the subject of the remittance reminder, a message indicating that the remittance request amount has been received from that user (in this example, "Remittance Received", "Remittance received from B.B."), the remittance request amount (3,000 yen in this example), and an icon of the word "Received" indicating that you (A.A) are the one who has received the remittance request amount.

On the other hand, a message MS22 is displayed on the terminal 20 of a user (B.B.) who is the target of the remittance reminder and has made a payment of the amount specified in the remittance reminder information, as a message from the user (B.B.).
By way of example and not limitation, the content of message MS22 is similar to the content of message MS12.

Message MS23 is also displayed as a message from the first user (A.A). Message MS23 includes an icon with the word "Pay" indicating that the user (B.B) is in the position of having paid the requested remittance amount, and differs from message MS13 in that it does not include an icon with the word "Receive."

In addition, a message MS32 is displayed on the terminal 20 of another user (C.C) who is neither the first user (A.A) nor the target of the remittance reminder, as a message from the user (B.B) who has paid the amount specified in the remittance reminder information.
By way of example and not limitation, the content of message MS32 is similar to the content of message MS12.

Message MS33 is also displayed as a message from the first user (A.A). Message MS33 differs from messages MS13 and MS23 in that it does not include an icon with the letters "Receive" or "Pay," but instead includes an icon image of the first user (A.A) and an icon image of the user (B.B) who is the subject of the remittance reminder.

Note that an arrow is displayed pointing from the icon image of the first user (A.A) different from the user (C.C) to the icon image of a user (B.B) different from the user (C.C). This allows the other user (C.C) to recognize that a remittance reminder has been sent from a user (A.A) different from the user (C.C) to a user (B.B) different from the user (C.C).

<Processing>
5-4 to 5-5 are flowcharts showing an example of the flow of processes executed by each device in this embodiment.
These flowcharts are rewritten from the flowcharts of Figures 1-13 and 1-14 to display remittance request information and remittance reminder information in the chat room.

When the communication I/F 14 receives the remittance request transmission request information from terminal 20A, the control unit 11 of the server 10 adds the remittance request message to the group talk management data (group talk room) of the group members including at least user A.A, user B.B, and user C.C, and updates it (S510).

In this example, a group chat room including three users is illustrated, but instead, a chat room including only two users, user A.A and user B.B, may or may not be used. In other words, it is sufficient that the chat room includes at least the two parties involved in the remittance (the remittance master user and the remittance request destination user).

Thereafter, the control unit 11 of the server 10 transmits the added remittance request message to each of the terminals 20A, 20B, and 20C via the communication I/F 14 (S520).
In response to this, terminal 20A, terminal 20B, and terminal 20C each cause their respective control units 21 to display the received remittance request message in the group talk room (A520, B520, C520).

The control unit 21 of the terminal 20B determines whether or not there has been input in response to the remittance request message displayed in the group talk room (B525), and if it determines that there has been input (B525: YES), it transfers processing to B130.

After S130, the control unit 11 of the server 10 adds the remittance message or the receipt message to the above-mentioned group talk management data and updates it (S540).

Thereafter, the control unit 11 of the server 10 transmits the added remittance message or receipt message to the terminal 20A, the terminal 20B, and the terminal 20C via the communication I/F 14, respectively (S550).
In response to this, terminal 20A, terminal 20B, and terminal 20C cause their respective control units 21 to display the received remittance message or receipt message in the group talk room (A550, B550, C550).

After S550, when the communication I/F 14 receives remittance reminder sending request information from terminal 20A, the control unit 11 of server 10 adds the remittance reminder message to the above-mentioned group talk management data and updates it (S570).

Thereafter, the control unit 11 of the server 10 transmits the added remittance reminder message to each of the terminals 20A, 20B, and 20C via the communication I/F 14 (S580).
In response to this, terminal 20A, terminal 20B, and terminal 20C each cause their respective control units 21 to display the received remittance reminder message in the group talk room (A580, B580, C580).

The control unit 21 of the terminal 20B determines whether or not an input has been made in response to the remittance reminder message displayed in the group talk room (B590), and if it determines that an input has been made, the control unit 21 transfers processing to B130.

<Effects of the Fifth Example>
This embodiment illustrates a configuration in which, on the terminal 20 of the remittance request destination user, the remittance request message (not limiting, an example of a first display based on the first information) and the remittance reminder message (not limiting, an example of a second display different from the first display based on the remittance request) are displayed on the display unit 24 by a messaging application (not limiting, an example of an application) installed on the terminal 20.
As an example of an effect of the embodiment obtained by such a configuration, the first information and the second information can be recognized by the user of the terminal by an application installed on the terminal.

In addition, in this embodiment, the terminal 20 of the remittance request destination user displays a group talk room (not limiting, an example of a chat room) including at least the remittance request destination user (not limiting, an example of a terminal user) and the remittance master user (not limiting, an example of a first user) on the display unit 24. The display of the remittance request message and the display of the remittance reminder message indicate a configuration displayed in this group talk room.
As an example of an effect of an embodiment obtained by such a configuration, the first information and the second information can be effectively recognized by the user of the terminal by displaying them in a chat room including at least the user of the terminal and the first user.

<Fifth Modification (1)>
In the fifth embodiment, a remittance request message and a remittance reminder message are displayed in the group talk room displayed on the terminals 20 of all group users included in the group, but this is not limited to the above.
It is also possible to prevent remittance request messages and remittance reminder messages from being displayed in the group talk room displayed on the terminals 20 of some of the group users.

<Display screen>
The example shown in FIG. 5-6 is a modified example of FIG. 5-2.
On the terminal 20 of the first user (A.A.), the first user (A.A.) can view his/her own message MS11 in the talk room.
In addition, on the terminal 20 of the user (B.B.) who is the target of the remittance reminder, the message MS21 from the first user (A.A.) can be viewed in the talk room.

On the other hand, the terminal 20 of another user (C.C), who is neither the first user (A.A) nor the target of the remittance reminder, cannot view the message MS31 of the first user (A.A) in the talk room.

Thus, as an example and not a limitation, among users belonging to the same group (X), other users (C.C) who are neither the first user (A.A) who sent the money transfer reminder nor the user (B.B) who was the target of the money transfer reminder may be prevented from viewing the message regarding the money transfer reminder in the chat room.

The example shown in FIG. 5-7 is a modified example of FIG. 5-2.
On the terminal 20 of the user (B.B.) who is the target of the remittance reminder, the message MS21 from the first user (A.A.) can be viewed in the talk room.

On the other hand, the first user (A.A.) cannot see his/her own message MS11 in the talk room on the terminal 20 of the first user (A.A.).
Furthermore, the terminal 20 of another user (C.C.) who is neither the first user (A.A.) nor the target of the remittance reminder cannot view the message MS31 of the first user (A.A.) in the talk room.

In this way, as an example and not a limitation, it may be possible to prevent users belonging to the same group (X) other than the user (B.B) who is the target of the remittance reminder, including the first user (A.A), from viewing the message regarding the remittance reminder.

<Data structure>
FIG. 5-8 is a diagram showing an example of a table for explaining a method of displaying a remittance request message and a remittance reminder message in this modified example.
In this table, by way of example and not limitation, setting numbers and display flags are defined in association with each other.

The display flag is a flag that indicates whether or not remittance request messages and remittance reminder messages are displayed in the group talk room displayed on the display unit 24 of the user's device 20.

The display flags include, by way of example and not limitation, the display flag of the remittance master user (user A.A in this example), the display flag of the remittance request destination user (user B.B in this example), and the display flag of other group users (user C.C in this example).

Let me explain in detail.
Setting No. "1" specifies that the display flags of the remittance master user, the remittance request destination user, and other group users are all set to "ON."
This means that the remittance request message and the remittance reminder message are displayed in the group talk room displayed on the terminals 20 of all users in the same group, regardless of whether they are the parties to the remittance request or not.

Setting No. "2" specifies that the display flags for the remittance master user and the remittance request destination user are set to "ON", and that the display flags for other group users are set to "OFF".
This means that the remittance request message and remittance reminder message are displayed in the group talk room displayed on the terminals 20 of the remittance master user and the remittance request destination user, who are the parties to the remittance request, but the remittance request message and remittance reminder message are not displayed in the group talk room displayed on the terminals 20 of other group users who are not parties to the remittance request.

Setting No. "3" specifies that the display flags for the remittance master user and the remittance request destination user are set to "ON", and that the display flags for other group users are set to "OFF".
This means that the remittance request message and the remittance reminder message are displayed on the terminals 20 of the remittance master user and the remittance request destination user, who are the parties to the remittance request, but the remittance request message and the remittance reminder message are not displayed on the terminals 20 of other group users who are not the parties.

<Processing>
5-9 to 5-10 are flowcharts showing an example of the flow of processes executed by each device in this modified example.
This flowchart is a rewrite of the flowcharts in FIG. 5-4 to FIG. 5-5 so as to perform processing according to the above table.
Here, a case will be illustrated in which the server 10 sets the display flag based on an input to the terminal 20 of the remittance master user.

In A120, the control unit 21 of the terminal 20A transmits remittance request transmission request information, which includes information for requesting the setting of the display flag, to the server 10 via the communication I/F 22.

The control unit 11 of the server 10 sets the display flag based on the information for requesting the setting of the display flag contained in the remittance request transmission request information received from the terminal 20A (S505).

In S520, the control unit 11 of the server 10 transmits the added remittance request message via the communication I/F 14 to the terminal 20 whose display flag has been set to "ON".
In response to this, the terminal 20 whose display flag is set to “ON” displays the received remittance request message in the group talk room on the display unit 24 .

Similarly, in S550, the control unit 11 of the server 10 transmits the added remittance message/receive message via the communication I/F 14 to the terminal 20 whose display flag is set to "ON".
In response to this, the terminal 20 whose display flag is set to “ON” displays the received remittance message/receive message in the group talk room on the display unit 24 .

Similarly, in S580, the control unit 11 of the server 10 transmits the added remittance reminder message via the communication I/F 14 to the terminal 20 whose display flag is set to "ON".
In response to this, the terminal 20 whose display flag is set to “ON” displays the received remittance reminder message in the group talk room on the display unit 24 .

In the above process, the server 10 sets the display flag based on the input to the terminal 20 of the remittance master user, but the present invention is not limited to this.
Alternatively, the server 10 may or may not set the display flag based on an input to the terminal 20 of the remittance request destination user.

In the above process, a common display flag is set for both the remittance request message and the remittance reminder message, but the present invention is not limited to this.
Alternatively, the display flag may or may not be set separately for the remittance request message and the remittance reminder message.
In this case, as just one example, a display flag setting of setting No. "1" may be applied to a remittance request message, and a display flag setting of setting No. "2" or setting No. "3" may be applied to a remittance reminder message.

In this modified example, the above group talk room includes at least the remittance request destination user (not limiting, an example of a terminal user), the remittance master user (not limiting, an example of a first user), and other group users (not limiting, an example of a second user different from the first user), and the remittance reminder message is not displayed in the group talk room displayed on the terminals 20 of other group users.
As an example of the effect of this modified example obtained by such a configuration, the second information based on the remittance request can be prevented from being made known to users who are not involved in the remittance request, i.e., users who are not the parties involved.

In addition, this modified example shows a configuration in which the remittance reminder message is not displayed in the group talk room displayed on the terminal 20 of the remittance master user.
The first user is a user making a remittance request, and is aware that he/she has made a remittance request to the user of the terminal by at least the first information. Therefore, by preventing the second display based on the remittance request from being displayed in a chat room displayed on the terminal of the first user, it is possible to prevent information that is not necessary for the first user from being displayed on the terminal of the first user.

<Fifth Modification (2)>
In the fifth embodiment, a message based on remittance reminder information to be displayed in a group chat room may or may not be displayed as a message from the official account of the payment application rather than as a message from the first user.

5-11 and 5-12 are modifications of FIGS. 5-2 and 5-3.
In the examples of Figures 5-2 and 5-3, messages MS11, MS21, and MS31 sent from a first user (A.A) to a user (B.B.) who is the target of a remittance reminder are displayed as messages from the first user (A.A).

As an example and not as a limitation, on the terminal 20 of the first user (A.A), the message MS11 is displayed as the user's own message, on the terminal 20 of the user (B.B) who is the target of the remittance reminder, the message MS21 is displayed in association with an icon image of the first user (A.A), and on the terminal 20 of another user (C.C), the message MS31 is displayed in association with an icon image of the first user (A.A).
That is, a message based on the remittance reminder information was displayed as a message from the first user (A.A) who performed the operation to send the remittance reminder information.

In Figures 5-11 and 5-12, by way of example and not limitation, a message based on remittance reminder information is displayed as a message from the official account of the payment application, rather than as a message from the first user (A.A).

As shown in FIG. 5-11, by way of example and not limitation, on the terminals 20 of users A.A, B.B, and C.C, a message based on remittance reminder information from a first user (A.A) to another user (B.B) is displayed in the talk room in association with an icon image of the official account of the payment application (in this example, an image including the word "Pay")

A message MS11a is displayed on the terminal 20 of A.A, who is the first user, a message MS21a is displayed on the terminal 20 of B.B, who is the target of the remittance reminder, and a message MS31a is displayed on the terminal 20 of C.C, who is another user.
Messages MS11a, MS21a, and MS31a have the same content except for the display manner of the buttons, and each is associated with an icon image of the official account of the payment application.

By way of example and not limitation, messages MS11a, MS21a, and MS31a all include an icon with the word "Remind," but do not include the icon with the words "Send Remind" that was included in message MS11, or the icon with the words "Receive Remind" that was included in message MS21.

Also, by way of example and not limitation, messages MS11a, MS21a, and MS31a all include an icon image of a first user (A.A) and an icon image of a user (B.B) who is the subject of the remittance reminder, along with an arrow pointing from the former icon image to the latter icon image.
The icon for the word "Receive" contained in message MS11 and the icon for the word "Payment" contained in message MS21 are not included.

Also, by way of example and not limitation, other information included in messages MS11a, MS21a, and MS31a is similar to other information included in messages MS11, MS12, and MS13, respectively.
For example and not by way of limitation, message MS11a includes a non-selectable remittance button BT11a and button BT11b, message MS21a includes a selectable remittance button BT21a and button BT21b, and message MS31a includes a non-selectable remittance button BT31a and button BT31b.

When the remittance process to the first user (A.A) is completed based on the user (B.B) who is the target of the remittance reminder tapping the remittance button BT21a, as shown in FIG. 5-12, a message MS12 is displayed on the terminal 20 of the first user (A.A) as a message from the user (B.B) who has completed the remittance, and a message MS13 is displayed as a message from the first user (A.A).

Furthermore, on the terminal 20 of the user (B.B.) who has completed the remittance, a message MS22 is displayed as his/her own message, and a message MS23 is displayed as the message of the first user (A.A.).
Furthermore, on the terminal 20 of the other user (C.C.), a message MS32 is displayed as a message from the user (B.B.) who has completed the remittance, and a message MS33 is displayed as a message from the first user (A.A.).

The contents of messages MS12 and MS13, messages MS22 and MS23, and messages MS32 and MS33 are similar to the example shown in Figure 5-3.

In the example shown in FIG. 5-11 and FIG. 5-12, but without being limited thereto, a remittance reminder based on a remittance request from a first user (A.A) to B.B. is displayed as a message from the official account of the payment application, thereby reducing the impression that the remittance reminder was displayed based on an operation by the first user (A.A).

On the other hand, after the remittance process is completed, messages MS12, MS22, and MS23 notifying the user that the remittance has been made are displayed as messages from the user (B.B) who received the remittance request, and messages MS13, MS23, and MS33 notifying the user that the remittance request amount has been received are displayed as messages from the first user (A.A), thereby clarifying the relationship between users.

The example shown in FIG. 5-13 is a modified example of FIG. 5-11.
On the terminal 20 of the first user (A.A), the message MS11a from the official account can be viewed in the talk room.
In addition, on the terminal 20 of the user (B.B.) who is the target of the remittance reminder, the message MS21a from the official account can be viewed in the talk room.

On the other hand, the message MS31a from the official account cannot be viewed in the chat room on the terminal 20 of another user (C.C), who is neither the first user (A.A) nor the target of the remittance reminder.

Thus, as an example and not a limitation, among users belonging to the same group (X), other users (C.C) who are neither the first user (A.A) who sent the money transfer reminder nor the user (B.B) who was the target of the money transfer reminder may be prevented from viewing the message regarding the money transfer reminder in the chat room.

The example shown in FIG. 5-14 is a modified example of FIG. 5-11.
On the terminal 20 of the user (B.B.) who is the target of the remittance reminder, the user can view a message MS21a from the official account in the talk room.

On the other hand, the first user (A.A) cannot view the message MS11a from the official account in the talk room on the terminal 20.
Furthermore, the message MS31a from the official account cannot be viewed in the talk room on the terminal 20 of another user (C.C.) who is neither the first user (A.A.) nor the target of the remittance reminder.

In this way, as an example and not a limitation, it may be possible to prevent users belonging to the same group (X) other than the user (B.B) who is the target of the remittance reminder, including the first user (A.A), from viewing the message regarding the remittance reminder.

<Fifth Modification (3)>
In the fifth embodiment, at least one of the remittance request message and the remittance reminder message displayed in the group chat room may or may not be a message based on the mention function of the messaging application.

FIG. 5-15 is a diagram showing an example of a group talk room in this case.
By way of example and not limitation, when a message based on remittance reminder information (an example of a remittance reminder display, not by way of limitation) is displayed in a chat room, the mention function in the messaging application will automatically be activated and the notation "@username" will be highlighted with an underline.

Here, the mention function is a function of a messaging application for sending a message (content) to a specified user.
In addition, on the terminal of a user who receives a message via the mention function, a notification emphasizing that the message has been received may or may not be displayed.

As an example and not a limitation, the "user name" part of "@user name" displays the username of the user designated by the first user (A.A) as the user of the terminal 20 on which the remittance reminder display will be displayed (as an example and not a limitation, the user associated with the remittance request history that was the target of the drag operation).
This username is, by way of example and not limitation, the username included in the remittance reminder display (by way of example and not limitation, messages MS11b, MS21b, MS31b).

In the example shown in FIG. 5-15, as a message to B.B, a user designated by the mention function, a message MS11b is displayed on the terminal 20 of the first user (A.A), a message MS21b is displayed on the terminal 20 of the user (B.B) who is the target of the remittance reminder, and a message MS31b is displayed on the terminal 20 of the other user (C.C).
At the beginning of each of the messages MS11b, MS21b, and MS31b, there is written "@B.B.", which indicates that the message is addressed to B.B., based on the mention function.

In this modified example, the remittance reminder message is displayed including at least information specifying the remittance request destination user using the mention function (this is not limiting, but is an example of information indicating the user of the terminal).
As an example of the effect of the modified example obtained by such a configuration, the second display including information indicating the user of the terminal can reliably allow the user of the terminal to recognize that the display is a display designated for that user.

<Fifth Modification (4)>
The display mode of the remittance reminder message displayed in the group talk room displayed on the display unit 24 of the terminal 20 of the remittance request destination user may be made different from the display mode of the remittance reminder message displayed in the group talk room displayed on the display unit 24 of the terminal 20 of other group users excluding the remittance request destination user and the remittance master user.

In this case, as in the example shown on the display screen, not only can the content of part of the text included in the message be made different, or the display mode (selectable/non-selectable) of the button included in the message be made different, but also, as a non-limiting example, a detailed message can be displayed on the terminal 20 of the person involved, while a simplified message can be displayed on the terminal 20 of the person other than the person involved. The messages can also be displayed in different colors.

In this modified example, the display manner of the remittance reminder message differs between the display manner (not limiting, an example of a first display manner) of the remittance reminder message displayed in a group talk room displayed on the terminal 20 (not limiting, an example of a terminal) of the remittance request destination user, and the display manner (not limiting, an example of a second display manner) of the remittance reminder message displayed in a group talk room displayed on the terminal 20 (not limiting, an example of a terminal of a second user) of other group users excluding the remittance request destination user and the remittance master user.
As an example of the effect of an embodiment obtained by such a configuration, the difference between the first display mode and the second display mode can make the user of the terminal aware that he or she is a party to the remittance request, while making the second user aware that he or she is not a party to the remittance request.

<Fifth Modification (5)>
If the remittance requested user does not make a payment, some of the functionality of the messaging application may or may not be restricted.

In the example of Figure 5-16, a message MS14 is displayed on the terminal 20 of the first user (A.A.) as a message from the official account of the payment application, a message MS24 is displayed on the terminal 20 of the user (B.B.) who is the target of the remittance reminder, and a message MS34 is displayed on the terminal 20 of the other user (C.C.).
At the beginning of each of the messages MS14, MS24, and MS34, based on the mention function, there is a notation "@B.B." indicating that the message is addressed to B.B. (in this example, the user who is the target of the remittance reminder).

Messages MS14, MS24, and MS34 each display, by way of example and not limitation, the words [Payment App], information indicating the functions that are restricted in the messaging application and the conditions of the usage restrictions (in this example, the words "If no remittance is made within 24 hours, the stamp function in Messaging App will be restricted" and the words "Please remit within the deadline"), the username of the first user to whom the remittance is to be made (in this example, A.A.), the requested remittance amount (in this example, "3,000 yen"), and the remittance deadline (in this example, 2020-04-24 17:00), and a remittance button is displayed at the bottom.

The send button BT14 of message MS14 and the send button BT34 of message MS34 are both displayed in an unselected state, while the send button BT24 of message MS24 is displayed in a selected state.

<Fifth Modification (6)>
The reminder displayed on the terminal 20 of a user who has not yet completed remittance may or may not include information about users who have already completed remittance.

In the example shown in FIG. 5-17, similar to the example shown in FIG. 5-1, messages exchanged between friends in the chat room of group X are displayed on the display unit 24 of A.A's device 20.

This example shows a state in which a user C.C. of one terminal 20 has replied that he has sent money, but there has been no reply from a user B.B. of the other terminal 20.
By way of example and not limitation, when a first user, A.A, taps button BTM3, a history of A.A's past remittance requests that are targeted to multiple users (B.B and C.C) and for which payment processing has not been completed for at least one user is displayed in the chat room.

In this example, a first user (A.A) is sending remittance request information for a common event (in this example, an event with a membership fee of 3,000 yen) to multiple users (B.B and C.C). Then, based on the fact that the remittance process for the remittance request to one user (B.B) is incomplete and the remittance process for the remittance request to the other user (C.C) is completed, information about both users is displayed in area R10.

As an example and not as a limitation, area R10 displays the date and time when the remittance request information was sent, an icon with the words "Request Sent," an icon with the words "Receive" indicating that the user is in a position to receive payment from each of multiple users (A.A, B.B), and the amount (3,000 yen) to be received from each of multiple users (A.A, B.B).
Below that is displayed information indicating the number of users for whom the remittance request was made (in this example, "Member 2"), and further displayed is both information about one user (B.B) who has not yet made a remittance, and information about the other user (C.C) who has already made a remittance.

As an example and not as a limitation, a first user (A.A) sends remittance request information to another user (B.B), but the remittance processing for this remittance request is incomplete, and therefore the remittance request amount (3,000 yen in this example) is displayed in association with the icon image and user name of the other user (B.B).
Also, as an example and not by way of limitation, when a first user (A.A) sends remittance request information to another user (C.C), and the remittance process for this remittance request is completed, information indicating that the remittance has been completed (in this example, the words "Remitted") is displayed in association with the icon image and user name of the other user (C.C).

In addition, the information relating to one user (B.B.) has a white background, while the information relating to the other user (C.C.) has a black background, so that the display manner of the former information and the latter information is different, making them easy to distinguish.
When the first user (A.A.) checks the check box in area R10, each piece of information displayed in area R10 becomes selected.
By tapping area RR in this state, remittance reminder information based on the information displayed in area R10 is sent to terminal 20 of user (B.B.) who has not made a remittance.

The example shown in Figure 5-18 differs from the example shown in Figure 5-2 in that the remittance reminder display based on the remittance reminder information also includes information about the other user (C.C) who has already made a payment.

A message MS11c is displayed on the terminal 20 of the first user (A.A.), a message MS21c is displayed on the terminal 20 of the other user (B.B.), and a message MS31c is displayed on the terminal 20 of the other user (C.C.).
For each of messages MS11c, MS21c, and MS31c, information indicating the number of users who have been the target of remittance requests based on a common event (in this example, "Member 2") is displayed, and further, information about one user (B.B) who has not yet made a remittance, and information about the other user (C.C) who has already made a remittance are both displayed.

As a non-limiting example, a remittance reminder displayed on the terminal 20 of one user (B.B) who has not yet remitted money for a certain event can include information about another user (C.C) who has already remitted money for the same event, thereby encouraging the one user (B.B) to remit money.

5-19 and 5-20 are modifications of FIGS. 5-17 and 5-18.
Figures 5-19 and 5-20 differ from Figures 5-17 and 5-18 in that, by way of example and not limitation, they show the number of times that each of the multiple users (B.B., C.C.) to whom remittance request information was sent was the subject of a remittance reminder (by way of example and not limitation, the number of times a remittance reminder display targeted at that user was displayed on that user's terminal 20).

In the examples of Figures 5-19 and 5-20, icon RIC1 is displayed in association with the icon image and user name of one user (B.B) who has not made a remittance in response to a remittance request for a certain event, indicating the number of times the user has been the subject of a remittance reminder (by way of example and not of limitation, the number of times a remittance reminder message for B.B has been displayed on B.B's terminal 20; in this example, 10 times), and icon RIC2 is displayed in association with the icon image and user name of the other user (C.C) who has already made a remittance in response to a remittance request for the same event, indicating the number of times the user has been the subject of a remittance reminder (by way of example and not of limitation, the number of times a remittance reminder message for C.C has been displayed on C.C's terminal 20; in this example, 0 times).

By way of example and not limitation, such a display can encourage each user to compare the number of reminders they have received with other users and with other users, thereby making each user aware of the need to avoid being the target of money transfer reminders as much as possible.

Next, an embodiment in which remittance reminders to the remittance request destination user are not sent will be described. Not sending remittance reminders is sometimes expressed as "stopping remittance reminders."
There are two main ways to stop these remittance reminders:
There are two possible methods: the server 10 stops sending the remittance reminder information, and the terminal 20 stops displaying the remittance reminder message. Each method will be described below.

Sixth Example
The sixth embodiment is an embodiment in which the server 10 stops sending remittance reminder information to the terminal 20 of the remittance request destination user.
The contents described in the sixth embodiment are applicable to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

As a method for the server 10 to manage remittance requests, the above-mentioned two patterns (Pattern A and Pattern B) are considered as examples and are not limited thereto.
When "Pattern A" is applied, the server 10 leaves the remittance request that has already been remitted without deleting it, and stops sending remittance reminder information corresponding to the remittance request to the terminal 20 of the remittance request destination user.
When "Pattern B" is applied, the server 10 deletes the remittance request that has been completed. Since the remittance request itself is deleted, the transmission of remittance reminder information is consequently stopped.

<Processing>
6A and 6B are flow charts showing an example of the flow of processes executed by each device in this embodiment.
This flowchart is based on the process of Server Remind, which continues from FIG. 1-13 to FIG. 2-11, by way of example and not by way of limitation.

If it is determined that a remittance reminder should be sent (S260: YES), the control unit 11 of the server 10 determines whether the reminder has been stopped for the remittance request corresponding to that remittance reminder (S267). Specifically, by way of example and not limitation, the second remittance request management data 157B is referenced, and if the remittance completed flag corresponding to the corresponding remittance request management ID is set to "ON", it is determined that the reminder has been stopped.

If it is determined that the reminding has not been stopped (S267: NO), the control unit 11 of the server 10 proceeds to S270.
In this case, control is performed so that remittance reminder information is sent from the server 10 to the terminal 20B.

On the other hand, if it is determined that the reminding has been stopped (S267: YES), the control unit 11 of the server 10 proceeds to S190.
In this case, the server 10 is controlled so as not to transmit remittance reminder information to the terminal 20B.

In the above process, the remittance reminder information may be sent from the server 10 to the terminal 20B more than once. In this case, when the server 10 executes the remittance settlement process based on an input to any of the remittance reminder displays displayed on the display unit 24 of the terminal 20B in the above process, the server 10 is controlled so that no remittance reminder information is sent from there to the terminal 20.

<Effects of the Sixth Embodiment>
In this embodiment, the server 10 receives remittance request information (not limiting, an example of first information related to a payment request) by a remittance master user (not limiting, an example of a first user) from the terminal 20 of the remittance master user via the communication I/F 14. Then, the server 10 shows a configuration in which the control unit 11 performs transmission control related to control of transmitting remittance reminder information (not limiting, an example of second information based on a remittance request) based on the remittance request to the terminal 20 of the remittance request destination user based on the execution of a second remittance process (not limiting, an example of a remittance process related to remittance to the first user) based on the remittance request.
As an example of an effect of an embodiment obtained by such a configuration, by performing transmission control regarding control of transmitting second information based on a remittance request to a terminal based on execution of a remittance process for remittance to a first user based on a remittance request, it is possible to allow the user of the terminal to appropriately remit money to the first user.

In this embodiment, the remittance request information includes information on the remittance request amount, and the remittance reminder information includes information on the same amount.
As an example of the effect of the embodiment obtained by such a configuration, the amount based on the remittance request can be reliably notified to the terminal user by the first information and the second information.

In addition, this embodiment illustrates a configuration in which the server 10 controls the transmission of remittance reminder information to the terminal 20 of the remittance request destination user via the communication I/F 14 when the second remittance process is not executed, and controls the transmission of remittance reminder information to the terminal 20 of the remittance request destination user via the communication I/F 14 when the second remittance process is executed.
As an example of an effect of an embodiment obtained by such a configuration, when a remittance process is not executed, the second information can be transmitted to the terminal, whereas when a remittance process is executed, the second information can be prevented from being transmitted to the terminal.

In addition, this embodiment illustrates a configuration in which the second remittance process is executed based on input by the user of the terminal 20 on the remittance request display (not limited to, but an example of the first display based on the first information) displayed on the terminal 20 of the remittance request destination user, in response to the remittance request display.
As an example of an effect of the embodiment obtained by such a configuration, a first display based on the first information can be displayed on the terminal, and a remittance process can be easily executed based on an input by a user of the terminal on the first display. In this case, in combination with the above configuration, the server can be controlled not to transmit the second information to the terminal based on the fact that a remittance process has been executed based on an input on the first display.

Also, in this embodiment, the server 10 transmits remittance reminder information based on the remittance request (not limiting, an example of third information based on a remittance request) to the terminal 20 of the remittance request destination user via the communication I/F 14. Then, the second remittance process shows a configuration in which a remittance reminder display (not limiting, an example of third display based on third information) is displayed on the terminal 20 of the remittance request destination user, and is executed based on an input by the remittance request destination user in response to the remittance reminder display.
As an example of the effect of the embodiment obtained by such a configuration, a remittance process can be executed based on an input to the third display based on the third information. In this case, in combination with the above configuration, when a remittance process is executed based on an input to the third display, the second information can be prevented from being transmitted to the terminal.

In addition, in this embodiment, the transmission control executed by the server 10 includes control to send second remittance reminder information (not limiting, an example of fourth information based on a remittance request) to the terminal 20 of the remittance request destination user when first remittance reminder information (not limiting, an example of second information) is sent to the terminal 20 of the remittance request destination user by the communication I/F 14 of the server 10, and the second remittance processing is configured such that a first remittance reminder display (not limiting, an example of second display based on second information) is displayed on the terminal 20 of the remittance request destination user and is executed based on input by the remittance request destination user in response to the first remittance reminder display.
As an example of the effect of the embodiment obtained by such a configuration, even if second information based on a remittance request is transmitted from the server to the terminal, fourth information based on the remittance request can be transmitted from the server to the terminal separately from the second information. Also, even if the fourth information based on a remittance request is transmitted from the server to the terminal, the user of the terminal can remit money to the first user based on an input by the user of the terminal to a second display based on the second information displayed on the terminal.

In addition, this embodiment illustrates a configuration in which the second remittance process (not limiting, but an example of a remittance process) is a process regarding a remittance from a remittance request destination user (not limiting, but an example of a terminal user) to a remittance master user (not limiting, but an example of a first user).
As an example of an effect of an embodiment obtained by such a configuration, the server can realize a remittance from the user of the terminal to the first user by a remittance process.

<Sixth Modification (1)>
In the sixth embodiment, pattern B (deleting the remittance request) can also be applied.
In this case, for example and not by way of limitation, when remittance is made by the remittance settlement process, the server 10 deletes the record corresponding to the remittance request management ID from the second remittance request management data 157B, and as a result, not only the remittance request but also the remittance reminder corresponding to this remittance request is deleted.

<Sixth Modification (2)>
When pattern A (leaving remittance requests without deleting them) is applied, remittance requests stored and managed by the server 10 are not deleted. Therefore, when a request to view remittance requests is made from the terminal 20 to the server 10, information on remittance requests that have already been sent can also be viewed on the terminal 20.
Therefore, the display mode of information regarding remittance requests for which remittance has already been made may or may not be changed to a different mode from that of information regarding remittance requests for which remittance has not yet been made.

As an example and not of limitation, the control unit 11 of the server 10 transmits a page of remittance request list information (remittance request list page) to the terminal 20 based on a request from the terminal 20 .
In this case, the control unit 11 of the server 10 sets and transmits a remittance request list page to be sent to the terminal 20B based on the remittance completion flag set in association with the corresponding remittance request management ID in the second remittance request management data 157B.

Specifically, as an example and not as a limitation, a remittance request list page is set up and sent in which remittance request information and remittance reminder information whose remittance completion flag is "OFF" is displayed in the default state, while remittance request information and remittance reminder information whose remittance completion flag is "ON" is displayed in a manner that indicates that remittance has been completed (as an example and not a limitation, a grayed-out display or a display with a remittance completion mark).

FIG. 6-3 is a diagram showing an example of a remittance request list screen displayed on the display unit 24 of the terminal 20B in this embodiment, and shows a screen corresponding to FIG. 2-13.
In this example, a completion mark MK1 including the word “DONE” is displayed for each of the remittance request information shown in area R21 and the remittance reminder information shown in area R22 corresponding to this remittance request, as information indicating that the remittance has been completed.

However, the display showing that remittance has been completed is not limited to this.
As a non-limiting example, on a remittance request list screen with the layout of FIG. 6-3, areas R21 and R22 may be grayed out as shown in FIG. 6-4 to distinguish them from remittance requests and remittance reminders that have not yet been remitted.

In addition, on a remittance request list screen with a layout different from that of Figure 6-3, for example and not limitation, on a remittance request list screen displayed based on the reception date and time as shown in Figure 2-17, a completion mark MK1 may be displayed in areas R21 and R23 as shown in Figure 6-5, for example and not limitation.
Moreover, these areas may be displayed in a grayed-out manner.

<Sixth Modification (3)>
As described above, it is also possible to stop the remittance reminder by causing the terminal 20 to stop displaying the remittance reminder display.
Here, an example is given in which the terminal reminding technique is applied.

FIG. 6 is a flowchart showing an example of the flow of processes executed by each device in this modified example.
This flowchart is based on the terminal remind process of FIG. 1-13 to FIG. 1-14, by way of example and not limitation.

If it is determined that a remittance reminder should be sent (B145: YES), the control unit 21 of terminal 20B determines whether a remittance based on the received remittance request has already been executed (B455).

If it is determined that the remittance has not been executed (B455: NO), the control unit 21 of the terminal 20B transfers the process to B150.
In this case, the control unit 21 of the terminal 20B executes control to display a remittance reminder message on the display unit 24.

On the other hand, if it is determined that the remittance has been executed (B455: YES), the control unit 21 of the terminal 20B advances the process to B190.
In this case, the control unit 21 of the terminal 20B executes control so as not to display the remittance reminder display on the display unit 24.

In the above process, the remittance reminder message may be displayed more than once on the display unit 24 of the terminal 20B.
In this case, in the above process, when a remittance is executed based on an input to any of the remittance reminder displays displayed on the display unit 24 of terminal 20, the remittance reminder information will thereafter be controlled so that it is not displayed on the display unit 24 of terminal 20B.

In this modified example, the terminal 20 of the remittance request destination user receives remittance request information (not limiting, an example of first information related to a remittance request) from a remittance master user (not limiting, an example of a first user) via the communication I/F 22. The terminal 20 of the remittance request destination user then displays a remittance request display (not limiting, an example of a first display based on the first information) on the display unit 24. The terminal 20 of the remittance request destination user then displays, via the control unit 21, display control related to control for displaying a remittance reminder display based on the remittance request (not limiting, an example of a second display based on a remittance request) on the display unit 24 based on the first remittance process (not limiting, an example of a remittance process related to remittance to the first user) based on the remittance request.
As an example of the effect of an embodiment obtained by such a configuration, by executing display control related to control for displaying a second display based on a remittance request on the display unit of the terminal based on the execution of a remittance process related to the remittance to the first user based on the remittance request, it is possible to allow the user of the terminal to appropriately remit money to the first user.

In addition, this modified example shows a configuration in which the above-mentioned display control is performed to control the display of a remittance reminder display on the display unit 24 when the first remittance process is not executed, and is configured to control the display not to display the remittance reminder display on the display unit 24 when the first remittance process is not executed.
As an example of an effect of an embodiment obtained by such a configuration, it is possible to appropriately switch whether or not to display the second information based on whether or not a remittance process has been executed.

In addition, this modified example shows a configuration in which the first remittance process is executed based on a display (not limiting, an example of the first display) based on the remittance request information (not limiting, an example of the first information) being displayed on the terminal 20 of the remittance request destination user, and based on input by the remittance request destination user on that display (not limiting, an example of input by a user of the terminal on the first display).
As an example of the effect of the modified example obtained by such a configuration, a first display based on the first information can be displayed on the terminal, and a remittance process can be easily executed based on an input by a user of the terminal to the first display. In this case, in combination with the above configuration, the terminal can be controlled not to display the second display on the display unit based on the fact that a remittance process has been executed based on an input to the first display.

<Sixth Modification (4)>
In relation to the sixth modified example (3), in the server reminding method, the remittance reminder can also be stopped by the terminal 20 stopping the display of the remittance reminder. In other words, the server 10 does not stop sending the remittance reminder information, but the terminal 20 can stop displaying the remittance reminder.

6 and 7 are flowcharts showing an example of the flow of processes executed by each device in this modified example.
If it is determined in B240 that remittance reminder information has been received from the server 10 (B240: YES), the control unit 21 of the terminal 20B determines whether or not remittance based on the corresponding remittance request has been executed (B455).

If it is determined that the remittance has not been executed (B455: NO), the control unit 21 of the terminal 20B transfers the process to B250.
In this case, remittance reminder information is transmitted from the server 10, and the control unit 21 of the terminal 20B executes control to display a remittance reminder display on the display unit 24 based on the remittance reminder information.

On the other hand, if it is determined that the remittance has been executed (B455: YES), the control unit 21 of the terminal 20B advances the process to B190.
In this case, remittance reminder information is sent from the server 10, but the control unit 21 of the terminal 20B controls so that a remittance reminder display based on the remittance reminder information is not displayed on the display unit 24.

<Sixth Modification (5)>
Furthermore, it is also possible for the server 10 to stop sending remittance reminder information based on a request from the terminal 20 of the remittance request destination user.
Specifically, as an example and not a limitation, when a remittance request list is displayed on the display unit 24 of the terminal 20B of user B.B, who is a remittance request destination user, and as an example and not a limitation, a remittance reminder from user A.A is tapped, a remittance screen as shown in FIG. 6-9 is displayed.

A confirmation information display area WR1 is configured at the bottom of this remittance screen to notify the server 10 that the contents of the remittance reminder have been confirmed. In this example, the confirmation information display area WR1 displays a link including the characters "Confirmed" along with the text "[Remind] Remittance request from A.A." By tapping this link, remittance reminder confirmation information indicating that the contents of the remittance reminder have been confirmed is sent from terminal 20B to the server 10.
The server 10 stops sending the remittance reminder information based on the reception of the remittance reminder confirmation information from the terminal 20B.

Seventh Example
The seventh embodiment is an embodiment in which a remittance request display and a remittance reminder display are displayed in a chat room in the sixth embodiment.
The contents described in the seventh embodiment are applicable to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<Processing>
7A and 7B are flow charts showing an example of the flow of processes executed by each device in this embodiment.
For simplicity, the following description will be given with reference to the process shown and explained with a focus on the case where the added message is displayed in the talk room displayed on terminal 20B, and the display of the talk room on terminal 20A will be omitted.

When the remittance request transmission request information is received from the terminal 20A via the communication I/F 14, the control unit 11 of the server 10 adds the remittance request message to the talk management data (talk room) between the user A.A and the user B.B, and updates it (S610).
Then, the control unit 11 of the server 10 transmits the added remittance request message to the terminal 20B via the communication I/F 14 (S620).

The control unit 21 of the terminal 20B determines whether or not a remittance request message has been received from the server 10 via the communication I/F 22 (B610), and if it is determined that a remittance request message has been received (B610: YES), executes a request notification process (B620).
This request notification process can be realized, for example and not by way of limitation, in a manner similar to the remind notification process described above.

Then, the control unit 21 of the terminal 20B determines whether to display the talk room on the display unit 24 based on whether an input to display the talk room has been made to the input unit (B630). If it is determined that the talk room should be displayed (B630: YES), the control unit 21 causes the display unit 24 to display the talk room based on the latest talk data stored in the memory unit 28 (B640).

The control unit 11 of the server 10 determines whether or not a remittance reminder sending request information has been received from the terminal 20A via the communication I/F 14 (S650), and if it is determined that the information has been received (S650: YES), it determines whether or not the reminder has been stopped based on the remittance completion flag that has been set (S660).

If it is determined that the remittance completion flag is "OFF" and the reminder has not been stopped (S660: NO), the control unit 11 of the server 10 adds the remittance reminder message to the chat management data (chat room) between user A.A and user B.B, and updates it (S670).
Then, the control unit 11 of the server 10 transmits the added remittance reminder message to the terminal 20B via the communication I/F 14 (S680).

Then, the control unit 11 of the server 10 judges whether or not to end the process (S690), and if it is judged that the process should be continued (S690: NO), the process returns to S650. On the other hand, if it is judged that the process should be ended (S690: YES), the process ends.

The control unit 21 of the terminal 20B determines whether or not a remittance reminder message has been received from the server 10 via the communication I/F 22 (B650), and if it is determined that a remittance reminder message has been received (B650: YES), executes a reminder notification process (B660).
This reminder notification process can be performed by applying the above-mentioned method, for example and not by way of limitation.

Then, the control unit 21 of the terminal 20B determines whether to display the talk room on the display unit 24 based on whether an input to display the talk room has been made to the input unit (B670). If it is determined that the talk room should be displayed (B670: YES), the control unit 21 causes the display unit 24 to display the talk room based on the latest talk data stored in the memory unit 28 (B680).

Then, the control unit 21 of the terminal 20B judges whether or not to end the process (B690), and if it judges to continue the process (B690: NO), it returns the process to B650. On the other hand, if it judges to end the process (B690: YES), it ends the process.

<Effects of the Seventh Embodiment>
This embodiment illustrates a configuration in which a remittance request display (not limiting, an example of a first display based on the first information) on terminal 20 is displayed in a talk room (not limiting, an example of a chat room) including at least a remittance request destination user (not limiting, an example of a user of the terminal) and a remittance master user (not limiting, an example of a first user).
As an example of an effect of the embodiment obtained by such a configuration, the first information can be easily and appropriately notified to at least the user of the terminal and the first user by displaying it in a chat room.

<Seventh Modification>
As in the sixth variant example (1), when applying the above-mentioned pattern A, the information regarding remittance requests that have already been sent may or may not be displayed in a manner different from the information regarding remittance requests that have not yet been sent.

In some messaging applications, the server 10 and the terminal 20 store talk information independently of each other.
As an example and not by way of limitation, messages stored on the server 10 are automatically deleted a certain amount of time (for example and not by way of limitation, several weeks) after the message is sent to the terminal 20, but messages stored on the terminal 20 remain unless deleted by the user.

In this case, since the message history is basically not deleted but remains on the terminal 20, the user of the terminal 20 can view past remittance request messages and remittance reminder messages based on the data stored on the terminal 20.
Therefore, in this modified example, the display mode of information related to a remittance request is changed by the following method.

FIG. 7C is a diagram showing an example of a table for explaining this technique.
In this table, by way of example and not limitation, a remittance completion flag, an information type, and a message are defined in association with each other.

The remittance completed flag can be either "OFF" or "ON".

The information type is the type of the message, and by way of example and not limitation, "request" and "reminder" are defined for each of the remittance flags "OFF" and "ON".

The type of message to be displayed in the chat room of the terminal 20 is determined according to whether the corresponding remittance flag is "ON" or "OFF."

Let me explain in detail.
(1) Remittance completed flag is "OFF"
For the information type "request," a "first type remittance request message (unsent)" is defined as the message. This indicates that when the remittance completion flag is "OFF," that is, when the remittance has not been made, the remittance request message displayed in the chat room will be a first type remittance request message.

For the information type "remind," the message type is defined as "Type 1 remittance reminder message (unsent)." This indicates that when the remittance flag is "OFF," meaning that the remittance has not yet been remitted, the remittance reminder message displayed in the chat room will be a Type 1 remittance reminder message.

(2) Remittance completed flag is "ON"
For the information type "request," a "second-class remittance request message (remittance completed)" is defined as the message. This indicates that when the remittance completed flag is "ON," that is, when the remittance has been completed, the remittance request message displayed in the chat room will be the second-class remittance request message.

For the information type "remind," the message type is defined as "Type 2 remittance reminder message (remittance completed)." This indicates that when the remittance completed flag is "ON," meaning that the remittance has been completed, the remittance reminder message displayed in the chat room will be a Type 2 remittance reminder message.

In other words, when the remittance has not yet been sent, the remittance request message and remittance reminder message are displayed in the first display mode (default display mode, as an example and not a limitation), but after the remittance has been completed, the display mode of these messages is changed from the first display mode to the second display mode (as an example and not a limitation, a display mode indicating that the remittance has been sent) and displayed.

Figures 7-4 and 7-5 are flowcharts showing an example of the process flow executed by each device in this embodiment.

When the communication I/F 14 receives the remittance request transmission request information from terminal 20A, the control unit 11 of the server 10 adds the first type remittance request message as a remittance request message to the talk management data (talk room) between user A.A and user B.B, and updates it (S710).

Then, the control unit 11 of the server 10 sends the first type remittance request message and the second type remittance request message to the terminal 20B via the communication I/F 14 as a remittance request message (S720).

After B620, the control unit 21 of terminal 20B stores the received remittance request message (first type, second type) in the memory unit 28 (B725).

Thereafter, the control unit 21 of the terminal 20B determines whether to display the talk room on the display unit 24 based on whether an input for displaying the talk room has been made to the input unit (B730). If it is determined that the talk room should be displayed (B730: YES), the control unit 21 causes the display unit 24 to display the talk room based on the latest talk data (B740).
Specifically, a first type of remittance request message is displayed in the chat room as a remittance request message.

If it is determined in S660 that the reminder has not been stopped (S660: NO), the control unit 11 of the server 10 updates the chat management data (chat room) between user A.A and user B.B by adding a first type remittance reminder message as a remittance reminder message (S770).

Then, the control unit 11 of the server 10 sends a first type remittance remind message and a second type remittance remind message to the terminal 20B via the communication I/F 14 as remittance remind messages (S780).

After B660, the control unit 21 of the terminal 20B stores the received remittance reminder message (first type, second type) in the memory unit 28 (B765).

Then, the control unit 21 of the terminal 20B determines whether to display the talk room on the display unit 24 based on whether an input to display the talk room has been made to the input unit (B770). Then, if it is determined that the talk room should be displayed (B770: YES), the control unit 21 causes the display unit 24 to display the talk room based on the latest talk data (B780).

Specifically, as an example and not as a limitation, when remittance information has not yet been received from server 10 among messages in a chat room, a first type remittance request message and a first type remittance reminder message are displayed as the corresponding remittance request message and remittance reminder message.
On the other hand, if remittance information has already been received from the server 10, a second type remittance request message and a second type remittance reminder message are displayed as the corresponding remittance request message and remittance reminder message.

Eighth Example
The eighth embodiment is an embodiment in which remittance is executed without going through a remittance request or a remittance reminder.

It is also anticipated that the remittance request destination user may make a remittance to the remittance master user using an independent remittance function in the payment application, either after checking the remittance request display or the remittance reminder display, or without checking these.
In such a case, the server 10 cannot determine (specify) for which remittance request management ID the remittance reminder should be stopped.

The contents described in the eighth embodiment are applicable to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

FIG. 8-1 is a diagram showing an example of the configuration of the third remittance request management data 157C, which is another example of the remittance request management data 157 described above, stored in the storage unit 15 of the server 10. As shown in FIG.
The third remittance request management data 157C stores in association with the date and time, remittance request management ID, remittance master ID, remittance request destination ID, remittance request amount, remittance completed flag, and information type in the second remittance request management data 157B, as well as, by way of example and not limitation, a reminder stop flag.

The reminder stop flag is a flag for identifying whether or not to stop sending remittance reminder information to the remittance request destination user's terminal 20 for the corresponding remittance request management ID, and is set to "ON" for those for which sending of remittance reminder information is to be stopped.

The difference from the previous embodiment is that even if the remittance completion flag is "OFF", the reminder stop flag may be set to "ON".

FIG. 8-2 is a diagram showing an example of a table for explaining a method in which the server 10 identifies a remittance request management ID in this embodiment.
In this table, by way of example and not limitation, a setting number, a target terminal, determination information, and a determination result are defined in association with each other.

For the target terminal, it is determined that the server 10 will determine which remittance reminders to stop based on the information selected and entered on which terminal 20.

The determination information specifies information that the server 10 uses to determine which remittance reminders to stop.

The determination result specifies the result that the server 10 determines as a remittance reminder to be stopped.

Let me explain in detail.
For setting No. "S1," the target terminal is defined as "the terminal of the remittance request destination user," the judgment information is defined as "the selected remittance master user," and the judgment result is defined as "a remittance reminder from the selected remittance master user."
This allows the remittance request destination user to select one of the remittance master users by displaying a list of users (remittance master users) who have received the remittance request on a screen (a remittance screen, for example and not by way of limitation) displayed on the display unit 24 of the remittance request destination user's terminal 20. Then, based on the selection of the remittance master user, it is indicated that remittance reminders from the selected remittance master user will be stopped.

When this setting is applied, the server 10 executes the remittance by regarding a remittance from the remittance request destination user as a remittance based on a remittance request from the selected remittance master user to the remittance request destination user, and the server 10 stops remittance reminders from the remittance master user to the remittance request destination user.
Specifically, by way of example and not limitation, the server 10 sets to “ON” the reminder stop flag corresponding to the remittance request management ID of all remittance requests from the selected remittance master user to the remittance request destination user in the third remittance request management data 157C.
However, since this setting does not allow a remittance request to be uniquely identified, the remittance completion flag can be left at "OFF."

For setting No. "S2," the target terminal is "the terminal of the remittance request destination user," the determination information is "the selected remittance destination user and whether or not the remittance reminder has been stopped," and the determination result is "the remittance reminder from the selected remittance destination user."
This indicates, by way of example and not by way of limitation, that the remittance request destination user selects a remittance destination user (hereinafter referred to as the "remittance destination user") on a screen (by way of example and not by way of limitation) displayed on the display unit 24 of the remittance request destination user's terminal 20, and based on the selection to stop remittance reminders from that remittance destination user, remittance reminders from the selected remittance destination user are stopped.

When this setting is applied, the server 10 judges whether or not a remittance request exists from the selected remittance destination user to the remittance request destination user. If it is judged that a remittance request exists, the server 10 regards the remittance from the remittance request destination user as a remittance based on a remittance request from the selected remittance destination user to the remittance request destination user and executes the remittance. If it is selected to stop remittance reminders, the server 10 stops remittance reminders from the remittance destination user to the remittance request destination user.
Specifically, by way of example and not limitation, the server 10 sets to “ON” the reminder stop flag corresponding to the remittance request management ID of all remittance requests from the selected remittance destination user to the remittance request destination user in the third remittance request management data 157C.
However, even with this setting, it is not possible to uniquely identify a remittance request, so the remittance completion flag can be left at "OFF."

If the user does not select to stop the remittance reminder, the server 10 will not stop the remittance reminder. The same applies below.

For setting No. "S3," the target terminal is "the terminal of the remittance request destination user," the judgment information is "the selected remittance destination user and the entered remittance amount," and the judgment result is "a remittance reminder from the selected remittance destination user and a remittance reminder in which the entered remittance amount and the remittance request amount are the same."
This indicates, by way of example and not by way of limitation, that when a remittance destination user is selected by the remittance request destination user on a screen (a remittance screen, by way of example and not by way of limitation) displayed on the display unit 24 of the remittance request destination user's terminal 20 and the remittance amount for that remittance destination user is input, a remittance reminder from the selected remittance destination user in which the input remittance amount is the same as the remittance request amount is stopped.

When applying this setting, the server 10, by way of example and not limitation, identifies in the third remittance request management data 157C, from among the remittance request management IDs from the selected remittance destination user to the remittance request destination user, the remittance request management ID in which the remittance request amount is the same as the remittance amount entered on the remittance request destination user's terminal 20.
The server 10 then regards the remittance from the remittance request destination user as a remittance based on the remittance request of the identified remittance request management ID and executes the remittance.The server 10 then stops the remittance reminder for the remittance request of that remittance request management ID.Specifically, by way of example and not limitation, the server 10 sets the remittance completed flag corresponding to the identified remittance request management ID to "ON" in the third remittance request management data 157C, and also sets the reminder stop flag to "ON".

In addition to or instead of stopping remittance reminders where the input remittance amount is the same as the remittance request amount, remittance reminders where the input remittance amount is close to the remittance request amount (for example and not by way of limitation, remittance reminders where the difference in amount is "300 yen or less") may or may not be stopped.

In setting No. "S4," the target terminal is defined as "the terminal of the user to whom the remittance request is made," the judgment information is defined as "the selected remittance request within the group," and the judgment result is defined as "the remittance reminder corresponding to the selected remittance request within the group."
This indicates, by way of example and not by way of limitation, that when the remittance request destination user selects remittance requests to other group users in addition to a remittance request to himself/herself on a screen (by way of example and not by way of limitation, a group request list screen) displayed on the display unit 24 of the remittance request destination user's terminal 20, remittance reminders corresponding to those remittance requests are stopped.

When this setting is applied, the server 10 executes the remittance by regarding the remittance from the remittance request destination user as a remittance based on the selected remittance request in the group, and then the server 10 stops remittance reminders corresponding to the remittance request to the remittance request destination user and remittance reminders corresponding to the remittance requests to the selected other group users.
Specifically, by way of example and not limitation, the server 10 sets the remittance completion flag corresponding to the remittance request management ID of these remittance requests to “ON” in the third remittance request management data 157C, and also sets the reminder stop flag to “ON”.

In this setting, as an example and not a limitation, a remittance request destination user in a group can stop remittance reminders for himself/herself and for other group users in the same group by remitting the amount that he/she wishes to remit, in addition to the amount that other group users in the same group wish to remit.

In addition, in each of the above settings, the choice of whether or not to stop remittance reminders (selection of whether or not to stop remittance reminders) is a required element, and remittance reminders may or may not be stopped when selection of stopping remittance reminders is made.

<Display screen>
Hereinafter, as an example, a display screen example when the setting of the setting number "S2" and the setting of the setting number "S4" are applied will be described.

8-3 to 8-7 show an example of the transition of screen images when the setting of setting No. "S2" is applied.
Fig. 8-3 shows a main menu screen of the payment application displayed on the display unit 24 of the terminal 20B, which corresponds to Fig. 2-2. Here, the state in which the "Remittance" icon IC3 has been tapped is shown. In this case, as an example and not a limitation, a remittance destination user selection screen shown in Fig. 8-4 is displayed.

This destination user selection screen is a screen for selecting a destination user, and by way of example and not limitation, it has a field for searching for destination user candidates from a payment application ID, and a field for searching for destination user candidates from a phone number. In this example, the field for searching for destination user candidates from a payment application ID is selected, and the search results show multiple users, such as "A.A," "C.C," "D.D," and "E.E." In this example, the checkbox next to "A.A" has been checked, indicating that user A.A. has been selected as the destination user.

In this state, when the selection area RM3 at the bottom of the screen is tapped and the amount to be remitted is input on an amount input screen (not shown), the screen shown in FIG. 8-5 is displayed as a non-limiting example.
In this screen, "3,000 yen" is entered as the planned remittance amount, and when the remittance area RM2 at the bottom of the screen is tapped in this state, remittance reminder stop information RS1 including, by way of example and not limitation, the icon image and user name of user A. A, the text "Stop reminders from this user?", an OK button BT10, and a cancel button is displayed as a pop-up in the center of the screen, as shown in FIG. 8-6.

When the OK button BT10 included in the remittance reminder stop information RS1 is tapped in this state, remittance destination user selection information (information indicating that user A.A has been selected) and remittance reminder stop request information are sent from terminal 20B to server 10. Then, server 10 executes the remittance and issues a remittance reminder. Then, as an example and not a limitation, a remittance completion notification is displayed in a pop-up in the center of the screen, indicating that the remittance has been completed and that the remittance reminder has been stopped, as shown in FIG. 8-7.

FIG. 8-8 is a diagram showing an example of a main menu screen of the payment application displayed on the display unit 24 of the terminal 20B in this embodiment.
This main menu screen corresponds to Fig. 2-2, and here shows a state where the "Remittance" icon IC3 is tapped. In this case, by way of example and not limitation, the remittance destination user selection screen shown in Fig. 8-4 is displayed.

8-8 to 8-9 show an example of a transition of screen images when the setting of setting No. "S4" is applied. Fig. 8-8 shows an example of a group talk room displayed on the display unit 24 of the terminal 20C of user C.C.
When the remittance icon IC4 at the bottom right of the icons displayed at the bottom of the group chat room is tapped, the remittance item selection area SMR is displayed in the chat room, as described above.

This remittance item selection area SMR displays a button BTM1 for sending remittances to other users, a button BTM2 for sending remittance request information to other users, a button BTM3 for displaying a list of remittance requests, and a button BTM4 for displaying a list of group requests.

When button BTM4 is tapped, a list of group requests is displayed on the screen, for example and not for limitation. In this example, two group requests are displayed: a remittance request from user A.A to user B.B (a remittance from user B.B to user A.A) with a remittance request amount of "3,000 yen", and a remittance request from user A.A to user C.C (a remittance from user C.C to user A.A) with a remittance request amount of "3,000 yen".

When the checkboxes associated with the remittance requests for the two people are checked and the remittance area RM2 at the bottom of the screen is tapped, the remittance request selection information is sent from terminal 20C to server 10. Server 10 then executes the remittances based on the remittance requests for the two people, and stops the remittance reminders corresponding to each of them.

8-9 shows group talk rooms displayed on the display units 24 of a terminal 20A of a user A.A who is a remittance master user, a terminal 20B of a user B.B who is a remittance request destination user, and a terminal 20C of a user C.C who is also a remittance request destination user.
In the group talk room displayed on terminal 20A, a message MS71 is displayed indicating that user C.C. has sent money to user A.A. for two people, and below that, a message M72 is displayed indicating that user A.A. has received that amount.

In the group talk room displayed on terminal 20B, in response to message MS71, a message MS81 is displayed indicating that user C.C. has sent money to user A.A for two people, and in response to message MS72, a message MS82 is displayed indicating that user A.A has received the amount. In addition, a message M83 is displayed indicating that the money transfer reminder from user A.A to user B.B has been stopped.

In addition, in the group talk room displayed on terminal 20C, message MS91 is displayed in response to message MS71, indicating that user C.C. has sent money to user A.A. for two people, and message MS92 is displayed in response to message MS72, indicating that user A.A. has received the amount.

In this case, in addition to the remittance reminders from user A.A to user B.B, the remittance reminders from user A.A to user C.C are also stopped. However, since it is likely that user C.C will make a payment including that for user B.B, knowing that the remittance reminders for himself/herself will be stopped, in this example, the group talk room displayed on terminal 20C does not display a message indicating that the remittance reminders from user A.A to user C.C have been stopped.

Alternatively, a message indicating that the remittance reminder from user A.A to user C.C has been stopped may be displayed in the group talk room displayed on terminal 20C.

<Processing>
8 to 10 are flowcharts showing an example of the flow of processes executed by each device in this embodiment.
Here, the processing of terminal 20B is shown on the left and the processing of server 10 is shown on the right, with the processing of terminal 20A being omitted from the illustration.
These processes are executed by the control unit 21 of the terminal 20B and the control unit 11 of the server 10 as subroutine processes of the processes in FIGS. 6-1 and 6-2, respectively, by way of example and not limitation.

The control unit 21 of the terminal 20B determines whether or not to execute the remittance (B810). Specifically, by way of example and not limitation, the control unit 21 determines whether or not an input for executing the remittance has been made to the input unit from the remittance screen described above or the group request list screen described above, etc.

If it is determined that the remittance should be executed (B810: YES), the control unit 21 of the terminal 20B transmits remittance settlement request information including the above-mentioned determination information to the server 10 via the communication I/F 22 (B830).

The control unit 11 of the server 10 determines whether or not remittance settlement request information has been received from the terminal 20B via the communication I/F 14 (S810), and if it is determined that the information has been received (S810: YES), it determines whether or not the received remittance settlement request information includes determination information (S820).

If it is determined that the received remittance settlement request information includes the determination information (S820: YES), the control unit 11 of the server 10 executes a remittance reminder stop determination process (S830).
Specifically, by way of example and not limitation, the remittance request management ID for which remittance reminders are to be stopped is determined (identified) according to the method described in the table of FIG. 8-2.

Then, the control unit 11 of the server 10 executes the remittance settlement process (S130). Specifically, by way of example and not limitation, the remittance is made to the remittance request associated with the determined remittance request management ID. Then, flags (remittance completed flag, reminder stop flag) are set using the method described above.

After B140, the control unit 21 of the terminal 20B determines whether or not to end the process (B890), and if it determines to continue the process (B890: NO), returns the process to B810.
On the other hand, if it is determined that the process is to be ended (B890: YES), the control unit 21 of the terminal 20B ends the process.

Similarly, after S150, the control unit 11 of the server 10 determines whether or not to end the process (S890), and if it determines to continue the process (S890: NO), the process returns to S810.
On the other hand, if it is determined that the process is to be ended (S890: YES), the control unit 11 of the server 10 ends the process.

In addition, in this process, in S267 of FIG. 6-2, the control unit 11 of the server 10 determines whether or not the reminder has been stopped for the remittance request management ID corresponding to the remittance reminder information for which a transmission request has been received. Specifically, by way of example and not limitation, the third remittance request management data 157C is referenced, and if the request stop flag corresponding to that remittance request management ID is set to "ON", it is determined that the reminder has been stopped.

<Effects of the Eighth Example>
This embodiment illustrates a configuration in which the second remittance process (not limiting, but an example of a remittance process) executed by the server 10 is executed based on the selection of a remittance master user (not limiting, but an example of a first user) displayed on the display unit 24 of the terminal 20 of the remittance request destination user.
As an example of the effect of an embodiment obtained by such a configuration, when a first user displayed on the display unit of the terminal is selected, the remittance process can be executed assuming that the remittance is based on a remittance request from the first user.

In addition, this embodiment illustrates a configuration in which the second remittance process is executed based on the selection of a remittance master user (not limiting, an example of a first user) by the remittance request destination user (not limiting, an example of a user of the terminal) and the selection of remittance reminder stop (not limiting, information indicating that the second information will not be sent).
As an example of an effect of an embodiment obtained by such a configuration, the remittance process can be appropriately executed by the user of the terminal based on the selection of the first user and the selection of information indicating that the second information will not be sent.

In addition, this embodiment illustrates a configuration in which the second remittance process is executed based on a remittance master user (not limiting, an example of a first user), a remittance request amount (not limiting, an example of an amount based on a remittance request), and a planned remittance amount (not limiting, an example of an amount input by a user of the terminal).
As an example of an effect of an embodiment obtained by such a configuration, the remittance process can be appropriately executed based on the first user's selection, the amount based on the remittance request, and the amount entered by the user of the terminal.

In addition, in the above embodiment, the second remittance process is configured to be executed based on a remittance from a group user (not limiting, an example of a second user) different from the remittance request destination user (not limiting, an example of a user of the terminal) to a remittance master user (not limiting, an example of a first user).
As an example of an effect of an embodiment obtained by such a configuration, it is possible to appropriately execute a remittance process based on a remittance to a first user by a second user different from the user of the terminal that requested the remittance.

In this case, the remittance request information is sent to a group including at least the remittance request destination user (not limited to, an example of a user of the terminal), the remittance master user (not limited to, an example of a first user), and another group user (not limited to, an example of a second user), and the second remittance process can be executed based on input by the other group user to a remittance request display based on the remittance request information displayed on the terminal 20 of that group user.
As an example of an effect of an embodiment obtained by such a configuration, the remittance process can be easily and appropriately executed based on an input by the second user to the first display based on the first information displayed on the second user's terminal.

Furthermore, this embodiment illustrates a configuration in which information such as an icon image and user name of the remittance master user (not limiting, but an example of first user information) is displayed on the display unit 24 of the terminal 20, and the first remittance process is executed based on input by the remittance request destination user (not limiting, but an example of a user of the terminal) to the first user information displayed on the display unit 24.
As an example of an effect of an embodiment obtained by such a configuration, a remittance process can be executed based on input by a user of the terminal to the first user information displayed on the display unit, which is easy for the user to understand.

Furthermore, in this embodiment, the terminal 20 acquires selection information of the remittance destination user (not limited to, but information indicating that the first user has been selected) and information on the planned remittance amount (not limited to, but an example of information on the amount to be remitted to the first user) based on an input to the terminal 20. The first remittance process is configured to be executed based on the information on the remittance request amount (requested remittance amount) and the information on the planned remittance amount.
As an example of the effect of an embodiment obtained by such a configuration, and not by way of limitation, when the amount based on the remittance request and the amount to be remitted to the user are the same amount, the remittance can be made to be regarded as being based on a remittance request from the user.

Furthermore, this embodiment illustrates a configuration in which the first remittance process is executed based on an input by the remittance request destination user to the terminal 20 to select a remittance master user, or an input to stop a remittance reminder (this is not a limitation, but is an example of an input indicating that the remittance is to the first user based on a remittance request).
As an example of an effect of an embodiment obtained by such a configuration, the remittance process can be easily and appropriately executed based on an input indicating that the remittance is to the first user based on a remittance request.

<Eighth Modification>
In the eighth embodiment, the server 10 manages whether or not to stop sending remittance reminder information by the reminder stop flag in the remittance request management data 157, but the present invention is not limited to this.
By way of example and not limitation, whether or not to stop sending remittance reminder information may or may not be managed by data other than the remittance request management data.

8 to 11 are diagrams showing an example of reminding stop management data stored in the storage unit 15 of the server 10 in this modified example.
As a non-limiting example, the reminder stop management data stores the application ID of the user receiving the remittance reminder information (receiving side) vertically and the application ID of the user sending the remittance reminder information (sending side) horizontally, and stores in a matrix format whether or not the remittance reminder information has been sent from the sending side to the receiving side (sent/not sent).

By default, “Sent” is stored in all fields where the sending side and receiving side intersect, but in the remittance reminder stop determination process (S830) in Figure 8-10, if it is determined that the sending of remittance reminder information should be stopped, the field where the sending side and receiving side intersect is updated to “Not sent.”
By way of example and not limitation, if the remittance master user is user A.A and the remittance request destination user is user B.B, and it is determined that remittance reminders from user A.A to user B.B should be stopped, then the field where the sender "U001 (user A.A)" and the receiver "U002 (user B.B)" intersect is updated to "no transmission."

Ninth Example
The ninth embodiment is an embodiment in which remittance reminders are stopped in exceptional cases different from those in the above embodiments.
The contents described in the ninth embodiment are applicable to the other embodiments and the other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

The following are some cases in which you may need to stop remittance reminders:
(A) The case where the remittance based on the remittance request has not yet been made, but the user wishes to stop the remittance reminder. (B) The case where the amount corresponding to the remittance request has been paid without using the payment application, and the user wishes to stop the remittance reminder.

(A) is an example, not a limitation, where the remittance has not been sent, but the user (but may also be a user other than the user) wishes to stop the remittance reminders in order to prevent repeated remittance reminders.
There may also be cases where the remittance master user abandons the remittance request.

(B) is, by way of example and not limitation, a case in which money is paid by handing over cash, transferring money to a financial institution (such as a bank), etc. In this case, too, it is considered that the user concerned would primarily wish to stop sending money reminders.

FIG. 9-1 is a diagram showing an example of a table for explaining a method for stopping the transmission of remittance reminder information in this embodiment.
In this table, by way of example and not limitation, a setting number, a target terminal, information for determination, a determination result, and whether approval by a remittance master user is required are associated with each other.

The target terminal, judgment information, and meaning of the judgment result are the same as those in the table in Figure 8-2.

Information (approval required/approval not required) is provided to identify whether approval from the remittance master user is required to stop a remittance reminder.

Let me explain in detail.
For setting No. “T1,” the target terminal is “terminal of remittance master user,” the judgment information is “selected remittance request destination user & whether or not remittance reminder has been selected to be stopped,” the judgment result is “remittance reminder to selected remittance request destination user,” and the requirement for approval from the remittance master user is “no.”
This indicates, by way of example and not by way of limitation, that a remittance request destination user is selected by the remittance master user on a screen (by way of example and not by way of limitation, a remittance request destination user list screen) displayed on the display unit 24 of the remittance master user's terminal 20, and that remittance reminders to the selected remittance request destination user are stopped based on the selection to stop remittance reminders.
In addition, since remittance reminders can be stopped at the request of the remittance master user, the requirement for approval from the remittance master user is set to "No."

When this setting is applied, the server 10 will stop all remittance reminders from that remittance master user to the selected remittance request destination user.
Specifically, by way of example and not limitation, the server 10 sets to “ON” the reminder stop flag corresponding to the remittance request management ID of all remittance requests from that remittance master user to the selected remittance request destination user in the third remittance request management data 157C.

For setting No. "T2," the target terminal is "the terminal of the remittance master user," the determination information is "whether or not the selected remittance request and remittance reminder has been selected to be stopped," the determination result is "the remittance reminder corresponding to the selected remittance request," and "No" is defined as whether or not approval from the remittance master user is required.
This indicates, by way of example and not by way of limitation, that a remittance request is selected by the remittance master user on a screen (by way of example and not by way of limitation, a remittance request list screen) displayed on the display unit 24 of the remittance master user's terminal 20, and based on the selection to stop the remittance reminder, the remittance reminder corresponding to the selected remittance request is stopped.
In addition, since remittance reminders can be stopped at the request of the remittance master user, the requirement for approval from the remittance master user is set to "No."

When this setting is applied, the server 10 stops the remittance reminder corresponding to the selected remittance request. Specifically, by way of example and not limitation, the server 10 sets the reminder stop flag corresponding to the remittance request management ID of the selected remittance request to "ON" in the third remittance request management data 157C.

However, this setting can uniquely identify the remittance request management ID, but cannot identify whether the remittance based on the remittance request has already been executed. For this reason, the remittance completion flag is left "OFF."
Therefore, if remittance has already been completed, remittance master user's terminal 20 may transmit remittance completion information to the server 10 so that the server 10 sets the remittance completion flag to "ON."

For setting No. "T3," the target terminal is "terminal of the user to whom the remittance request is made," the determination information is "remittance master user & whether or not remittance reminder stop has been selected," the determination result is "remittance reminder from selected remittance master user," and the requirement for approval from the remittance master user is "required."
This indicates, by way of example and not by way of limitation, that a remittance master user is selected by the remittance request destination user on a screen (by way of example and not by way of limitation, a remittance master user list screen) displayed on the display unit 24 of the remittance request destination user's terminal 20, and that remittance reminders from the selected remittance master user are stopped based on the selection to stop remittance reminders.
In addition, in order to stop remittance reminders at the request of the remittance request destination user, the approval requirement of the remittance master user is set to "Required."

When this setting is applied, the server 10 executes a process (hereinafter referred to as "approval confirmation process") to confirm whether or not the suspension of remittance reminders is approved for the terminal 20 of the selected remittance master user. Specifically, the server 10 transmits information (hereinafter referred to as "approval confirmation information") for confirming whether or not the suspension of remittance reminders is approved for the terminal 20 of the selected remittance master user.
When information indicating approval (hereinafter referred to as "approval information") is received from the remittance master user's terminal 20, the server 10 stops remittance reminders from that remittance master user to the remittance request destination user. Specifically, in the third remittance request management data 157C, the server 10 sets to "ON" the reminder stop flags corresponding to the remittance request management IDs of all remittance requests from the remittance master user identified by the received application ID to that remittance request destination user.
On the other hand, if the server 10 does not receive approval information from the remittance master user terminal 20, the server 10 does not stop the remittance reminder, i.e., the reminder stop flag remains "OFF".

In setting No. "T4," the target terminal is "the terminal of the user to whom the remittance request is made," the determination information is "selected remittance request and whether or not the remittance reminder has been stopped," the determination result is "the remittance reminder corresponding to the selected remittance request," and "required" is defined as whether approval from the remittance master user is required.
This indicates, by way of example and not by way of limitation, that a remittance request is selected by the remittance request destination user on a screen (by way of example and not by way of limitation, a remittance request list screen) displayed on the display unit 24 of the terminal 20 of the remittance request destination user, and based on the selection to stop the remittance reminder, the remittance reminder corresponding to the selected remittance request is stopped.
In addition, in order to stop remittance reminders at the request of the remittance request destination user, the approval requirement of the remittance master user is set to "Required."

When this setting is applied, the server 10 stops the remittance reminder corresponding to the selected remittance request. Specifically, the server 10 sets the reminder stop flag of the remittance request management ID corresponding to the selected remittance request to "ON" in the third remittance request management data 157C.

However, this setting can uniquely identify the remittance request management ID, but cannot identify whether the remittance based on the remittance request has already been executed. For this reason, the remittance completion flag is left "OFF."
Therefore, if remittance has already been completed, remittance completion information may be sent from the remittance request destination user's terminal 20 to the server 10, so that the server 10 sets the remittance completion flag to "ON".

For setting No. "T5," the target terminal is "a terminal of a user other than the parties involved," the determination information is "whether the selected party has chosen to stop the remittance request and remittance reminder," the determination result is "the remittance reminder corresponding to the remittance request of the selected party," and "required" is defined as whether approval from the remittance master user is required.
This indicates, by way of example and not by way of limitation, that a user other than the parties to the remittance (by way of example and not by way of limitation, a user other than the remittance master user and the remittance request destination user in the same group) selects a remittance request of a party on a screen (by way of example and not by way of limitation, a group request list screen) displayed on the display unit 24 of the terminal 20 of that user and chooses to stop the remittance reminder, and based on this, the remittance reminder corresponding to the remittance request of the selected party is stopped.

This is, for example and not by way of limitation, a case where one user in a group requests that another group user (remittance request destination user) in the same group stop a remittance reminder in response to a remittance request from the remittance master user, in which a user other than the party in question acts as a witness to stop the remittance reminder of the party in question.
Since remittance reminders can be stopped at the request of users other than the parties involved, the approval requirement for the remittance master user is set to "Required."

When this setting is applied, the server 10 stops remittance reminders corresponding to the remittance request of the selected party. Specifically, the server 10 sets the reminder stop flag of the remittance request management ID corresponding to the remittance request of the selected party to "ON" in the third remittance request management data 157C.

In addition, when the setting is such that approval from the remittance master user is "required," the server 10 can perform approval confirmation processing at regular intervals, for example and not by way of limitation, once every few hours. This is to prevent repudiation by the remittance master user.

In addition, if no approval information is received from the remittance master user's terminal 20 within a set period of time (for example, several days, but not limited to this) after the first approval confirmation process is performed, the server 10 can assume that approval has been granted by the remittance master user and stop sending remittance reminders.
Conversely, if no approval information is received from the remittance master user's terminal 20 even after a set period has elapsed since the first approval confirmation process was performed, the server 10 can assume that approval has been denied by the remittance master user and can choose not to stop the remittance reminder.

<Display screen>
As an example, a display screen example when the setting of the above setting number "T2" and the setting of the setting number "T4" are applied will be described.

9-2 is a diagram showing an example of a remittance request list screen displayed on the display unit 24 of the terminal 20A of the user A.
In this example, the remittance master user is user A.A, the remittance request destination user is user B.B, and a case will be described in which user A.A stops a remittance reminder corresponding to a remittance request sent to user B.B.

This remittance request list screen displays information about the remittance request sent by user A.A to user B.B, and information about the remittance reminder corresponding to this remittance request.

In the display area for information regarding the remittance request, next to the icon image and user name of user B.B., a reminder stop icon IC10 including an image of a speaker is displayed, by way of example and not by way of limitation, for stopping the remittance reminder.
By way of example and not limitation, the reminder stop icon IC10 is displayed in a default state (a state in which remittance reminders are not stopped) in black with the image of the speaker being whited out.

When the reminder stop icon IC10 is tapped, as an example and not a limitation, a first remittance reminder stop information for stopping the remittance reminder corresponding to this remittance request is popped up in the center of the screen as shown in FIG. 9-3.
Then, when the OK button BT10 included in the first reminder stop confirmation information is tapped, remittance request selection information and first remittance reminder stop request information are transmitted from the terminal 20A to the server 10, and the remittance reminder corresponding to the selected remittance request is stopped.

Then, by way of example and not limitation, the display mode of the reminder stop icon IC10 associated with the remittance request from user A.A to user B.B changes from the mode shown in FIG. 9-2. Specifically, by way of example and not limitation, as shown in FIG. 9-4, the area of the reminder stop icon IC10 that was displayed in black other than the image of the speaker is displayed in white.
Also, based on the fact that the remittance reminder has been stopped, by way of example and not limitation, as shown in FIG. 9-4, the display area of the remittance reminder corresponding to the remittance request is displayed in a faded state.

In addition to stopping the remittance reminder, the server 10 may be notified that the money has been paid based on an input by the user to the terminal 20A.
In this case, the server 10 not only sets the reminder stop flag to "ON", but also sets the remittance completed flag to "OFF".
As a result, by way of example and not limitation, as shown in FIG. 9-5, on the remittance request list screen displayed on the display unit 24 of the terminal 20A, a completion mark MK1 including the word “DONE” is displayed for each remittance request and its corresponding remittance reminder.

9-6 is a diagram showing an example of a remittance request list screen displayed on the display unit 24 of the terminal 20A of user B.
In this example, the remittance master user is user A.A, the remittance request destination user is user B.B, and a case will be described in which user B.B requests to stop a remittance reminder corresponding to a remittance request received from user A.A.

This remittance request list screen displays information regarding the remittance request received by user B.B from user A.A, and information regarding the remittance reminder corresponding to this remittance request.
In the remittance request display area, the reminder stop icon IC10 described above is displayed next to the icon image and user name of user A.A.

When the reminder stop icon IC10 is tapped, as an example and not by way of limitation, as shown in FIG. 9-7, a second remittance reminder stop information for requesting the user A.A to stop the remittance reminder corresponding to this remittance request is popped up in the center of the screen.
Then, when the OK button BT10 included in the second reminder stop confirmation information is tapped, the remittance request selection information and the second remittance reminder stop request information are transmitted from the terminal 20B to the server 10. In this case, the server 10 transmits to the terminal 20A of the user A.
We will send you information to confirm whether or not you want to stop receiving remittance reminders.

9-8 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20A of the user A.
On the display unit 24 of the terminal 20A, in the center of the remittance request list screen, suspension approval confirmation information for confirming whether or not to approve the suspension of the remittance reminder received from the server 10 is displayed. Then, when the OK button BT10 included in the approval confirmation information is tapped, the approval information is transmitted from the terminal 20A to the server 10. Then, in the server 10, the remittance reminder corresponding to this remittance request is stopped.
As a result, a remittance request list screen such as that shown in FIG. 9-9 is displayed on the display unit 24 of the terminal 20B, by way of example and not limitation.

In the remittance request list screen of FIG. 9-9, by way of example and not limitation, the display mode of the reminder stop icon IC10 associated with a remittance request from user A.A to user B.B is changed and displayed, and the display area of the remittance reminder corresponding to this remittance request is displayed faded.

<Effects of the ninth embodiment>
This embodiment illustrates a configuration in which the control of sending remittance reminder information (not limiting, an example of second information) by the server 10 is performed based on input (not limiting, an example of first input) by the terminal 20 of a remittance master user (not limiting, an example of a first user).
As an example of an effect of an embodiment obtained by such a configuration, the transmission of the second information to the terminal of the user who is the recipient of the remittance request can be controlled according to the intention of the first user who has made the remittance request.

In addition, this embodiment shows a configuration in which the first input is an input regarding not transmitting remittance reminder information to the terminal 20 of the remittance request destination user.
As an example of the effect of an embodiment obtained by such a configuration, it is possible to control so that the second information is not sent to the terminal of the user to whom the remittance is requested, in accordance with the wishes of the first user who has made the remittance request.

In addition, this embodiment illustrates a configuration in which the above-mentioned transmission control is executed based on input (not limiting, an example of a second input) made by the remittance request destination user (not limiting, an example of a terminal user) to his/her own terminal 20.
As an example of the effect of the embodiment obtained by such a configuration, the transmission of the second information to the terminal of the user who is the remittance destination can be controlled in accordance with the intention of the user who is the remittance destination.

In addition, this embodiment shows a configuration in which the second input is an input regarding not transmitting remittance reminder information.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to perform control so that the second information is not sent to the terminal of the user who is the recipient of the remittance request, in accordance with the will of the user who is the recipient of the remittance request.

In addition, this embodiment illustrates a configuration in which the above-mentioned transmission control is executed based on the above-mentioned second input and information regarding the remittance master user's approval of not transmitting the second information (not limited to this, but an example of information regarding the first user's approval of the second input).
As an example of the effect of the embodiment obtained by such a configuration, by way of example and not by way of limitation, even if a second input is made, if the second input is not approved by the first user who made the remittance request, the second information can be transmitted to the terminal of the user who is the destination of the remittance request. Conversely, by way of example and not by way of limitation, if a second input is made, but the first user who made the remittance request approves the second input, the second information can be prevented from being transmitted to the terminal of the user who is the destination of the remittance request.

＜Other＞
In the above embodiment, the first information regarding the remittance request in the present invention is "remittance request information" and the second information based on the remittance request is "remittance reminder information", but the present invention is not limited thereto.

The combination of the first information and the second information in the present invention may be any of the following combinations.
(1) First Combination First Information: Remittance Request Information Second Information: Remittance Reminder Information This combination is the combination described in the above embodiment.

(2) Second combination: First information: remittance request information; Second information: remittance exemption information. The remittance exemption information is, by way of example and not limitation, information used by a remittance master user to notify a remittance request destination user that remittance is exempt (information used to notify the remittance request destination user that there is no need to make a remittance).
This combination is applicable in cases where a remittance master user has made a remittance request to the remittance request destination user, but wishes to inform the remittance request destination user that for some reason the remittance does not need to be completed.

(3) Third combination: First information: remittance exemption information; Second information: remittance exemption reminder information. The remittance exemption reminder information is, by way of example and not limitation, information for the remittance master user to reconfirm to the remittance request destination user that the remittance is exempt (information to emphasize that there is no need to make the remittance).
This combination is applicable when the remittance master user wishes to reaffirm the remittance request destination user after informing him/her that the remittance is exempt.

(4) Fourth combination: First information: remittance exemption information; Second information: remittance request information. This combination is applicable when a remittance master user has notified a remittance request destination user that the remittance request destination user is initially exempt from remittance, but then, for some reason, the remittance destination user is required to make the remittance and requests the remittance.

Reference Signs List 1 Communication system 10 Server 20 Terminal 30 Network

Claims (14)

A server that transmits a message to a chat room of a group including a first user of a first terminal, a second user of a second terminal, and a third user of a third terminal,
a communication unit configured to transmit first remittance request information regarding a remittance request made by the first user to the second user to the chat room of the group;
and a control unit that controls the transmission of second remittance request information to the second terminal via the communication unit based on the remittance request from the first user to the second user after the first remittance request information is sent to the chat room of the group. 2. The server of claim 1,
The control unit transmits the second remittance request information only to the second terminal. The server according to claim 1 or 2,
The control unit performs control not to transmit the second remittance request information to the first terminal. The server according to any one of claims 1 to 3,
The second remittance request information is information displayed in the chat room. 5. The server according to claim 4,
The control unit performs control to transmit the second remittance request information to the second terminal of the second user who has received the remittance request. The server according to any one of claims 1 to 5,
The second remittance request information includes information indicating that the remittance request is directed to the second user. The server according to any one of claims 1 to 6,
The first remittance request information includes information regarding the remittance requests to a plurality of users including the second user. 8. The server according to claim 7,
The second remittance request information is transmitted to a terminal of each of the plurality of users, and includes information about a user among the plurality of users who has made a remittance based on the remittance request. 9. The server according to claim 8,
The second remittance request information includes information that is displayed in different display modes for a user who has made a remittance based on the remittance request and a user who has not made a remittance based on the remittance request. The server according to any one of claims 1 to 9,
the control unit transmits a plurality of second remittance request information to the second terminal based on the remittance request from the first user to the second user;
The second remittance request information includes information regarding the number of times the second remittance request information has been sent to the second user. The server according to any one of claims 1 to 10,
The first remittance request information includes information on an amount based on the remittance request,
The second remittance request information includes information on the amount based on the remittance request. A server according to any one of claims 1 to 11,
The control unit controls the communication unit to transmit the second remittance request information to the second terminal and not to transmit the second remittance request information to the third terminal when, based on the first user's transmission of the first remittance request information regarding the remittance request to the second user and the third user, the remittance is not made by the second user but is made by the third user. 1. An information processing method of a server for transmitting a message to a chat room of a group including a first user of a first terminal, a second user of a second terminal, and a third user of a third terminal, comprising:
transmitting first remittance request information regarding a remittance request from the first user to the second user to the chat room of the group via a communication unit of the server;
The method includes controlling, by a control unit of the server, the transmission of second remittance request information to the second terminal via the communication unit based on the remittance request from the first user to the second user after the first remittance request information is sent to the chat room of the group. A program executed by a server for sending a message to a chat room of a group including a first user of a first terminal, a second user of a second terminal, and a third user of a third terminal,
transmitting first remittance request information regarding a remittance request from the first user to the second user to the chat room of the group via a communication unit of the server;
After the first remittance request information is sent to the chat room of the group, the server controls a control unit of the server to transmit second remittance request information to the second terminal via the communication unit based on the remittance request from the first user to the second user.

Images