JP7778543B2 - Program, information processing method, server, system - Google Patents

Description

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

Recently, services that enable the management of electronic currency (electronic money) held by a device or a user of a device, as well as the sending and receiving of money, using applications that can be executed on devices such as smartphones, are becoming increasingly popular. For example, Patent Document 1 discloses technology for settling the purchase amount of goods.

Japanese Patent Application Laid-Open No. 2002-176671

According to a first aspect of the present invention, a program executed by a server communicating with a terminal is executed by the server to transmit first information regarding a remittance request by a first user to the terminal by a communication unit of the server, and to perform transmission control regarding control of transmitting second information based on the remittance request to the terminal by a control unit of the server based on the execution of a remittance process regarding the remittance to the first user based on the remittance request.
According to a second aspect of the present invention, an information processing method of a server communicating with a terminal includes transmitting first information related to a remittance request by a first user to the terminal by a communication unit of the server, and performing transmission control related to control of transmitting second information based on the remittance request to the terminal based on the execution of a remittance process related to a remittance to the first user based on the remittance request by a control unit of the server.
According to a third aspect of the present invention, a server communicating with a terminal includes a communication unit that transmits first information related to a remittance request by a first user to the terminal, and a control unit that performs transmission control related to control of transmitting second information based on the remittance request to the terminal based on execution of a remittance process related to remittance to the first user based on the remittance request.
According to a fourth aspect of the present invention, a server communicating with a 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: transmitting first information related to a remittance request by a first user to the terminal via a communication unit of the server; and performing transmission control related to control of transmitting second information based on the remittance request to the terminal based on the execution of a remittance process related to the remittance to the first user based on the remittance request.
According to a fifth aspect of the present invention, a program executed by the terminal receives first information regarding a remittance request by a first user by a communication unit of the terminal, displays a first display based on the first information by a display unit of the terminal, and performs display control by a control unit of the terminal regarding control of displaying a second display based on the remittance request on the display unit based on the remittance request based on execution of a remittance process for remittance to the first user based on the remittance request.

FIG. 1 is a diagram illustrating an example of the configuration of a communication system according to an embodiment. FIG. 3 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. 3 is a diagram showing an example of a user management database according to the first embodiment. FIG. 10 is a diagram showing an example of remittance request management data according to the first embodiment. FIG. 2 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 the processing flow of the terminal and the server according to the first embodiment; 6 is a flowchart showing an example of the processing flow of the terminal and 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. 10 is a diagram showing an example of remittance request management data according to the second embodiment. FIG. 10 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 10 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 10 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 10 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 10 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 10 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 10 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 10 is a diagram showing an example of a display screen of a terminal according to a second embodiment. FIG. 10 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 the processing flow of a terminal and a server according to the second embodiment; 10 is a flowchart showing an example of the processing flow of a terminal and a server according to the second embodiment; FIG. 10 is a diagram showing an example of a display screen of a terminal according to a second modified example. FIG. 10 is a diagram showing an example of a display screen of a terminal according to a second modified example. FIG. 10 is a diagram showing an example of a display screen of a terminal according to a second modified example. FIG. 10 is a diagram showing an example of a display screen of a terminal according to a second modified example. FIG. 10 is a diagram showing an example of a display screen of a terminal according to a second modified example. FIG. 10 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 timing chart according to the third embodiment. FIG. 11 is a diagram showing an example of a timing chart according to a third modified example. 13 is a flowchart showing an example of the 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 a 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 the 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 the processing flow of a terminal and a server according to the fifth embodiment. 13 is a flowchart showing an example of the 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 the processing flow of a terminal and a server according to a fifth modified example. 13 is a flowchart showing an example of the 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. 13 is a flowchart showing an example of the processing flow of a terminal and a server according to the sixth embodiment. 13 is a flowchart showing an example of the 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 the processing flow of a terminal and a server according to a sixth modified example. 13 is a flowchart showing an example of the 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. 13 is a flowchart showing an example of the processing flow of a terminal and a server according to the seventh embodiment. 13 is a flowchart showing an example of the processing flow of a terminal and a server according to the seventh embodiment. FIG. 13 is a diagram showing an example of a table relating to a display mode of information related to a remittance request according to the seventh modified example. 13 is a flowchart showing an example of the processing flow of a terminal and a server according to a seventh modified example. 13 is a flowchart showing an example of the 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 an eighth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to an 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 an eighth embodiment. 13 is a flowchart showing an example of the processing flow of a terminal and a server according to the eighth embodiment. FIG. 23 is a diagram showing an example of reminding 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 a ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to a ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to a ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to a ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to a ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to a ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to a ninth embodiment. FIG. 23 is a diagram showing an example of a display screen of a terminal according to a ninth embodiment.

<Compliance with legal matters>
It should be noted that the disclosures set forth herein are subject to compliance with the laws of the country of implementation, such as communications privacy, as required for the implementation of the disclosures.

Embodiments for implementing the programs and the like related to this disclosure 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 a device sends and receives various types of information and data via a communication I/F (via a communication unit) based on the control of a control unit (e.g., 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, for example and not by way of 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.

Terminal 20 (terminal 20A, terminal 20B, terminal 20C, etc.) may be any information processing terminal capable of implementing the functions described in each embodiment. Examples of terminal 20 include, but are not limited to, smartphones, mobile phones (feature phones), computers (including, but not limited to, desktops, laptops, tablets, etc.), media computer platforms (including, but not limited to, cable and satellite set-top boxes, digital video recorders), handheld computer devices (including, but not limited to, personal digital assistants (PDAs), email clients, etc.), wearable devices (glasses-type devices, watch-type devices, etc.), virtual reality (VR) terminals, smart speakers (voice recognition devices), or other types of computers or communication platforms. Terminal 20 may also be referred to as an information processing terminal.

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

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

One or more portions of network 30 may or may not be a wired network or a wireless network. 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 (registered trademark), satellite communications, etc., or a combination of two or more thereof. Network 30 may include one or more networks 30.

The server 10 (which is an example of a server, information processing device, or information management device, but is not limited thereto) has the function of providing a predetermined service (such as a payment service in this embodiment) to the terminal 20. The server 10 may be any information processing device capable of implementing the functions described in each embodiment. Examples of the server 10 include, but are not limited to, a server device, a computer (such as a desktop, laptop, or tablet), a media computer platform (such as a cable or satellite set-top box or digital video recorder), a handheld computer device (such as a PDA or email client), or other types of computers or communication platforms. The server 10 may also be referred to as an information processing device. If 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 each be referred to as an information processing device.

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

(1) HW Configuration of Terminal FIG. 1A shows an example of the HW configuration of the terminal 20.
The terminal 20 includes a control unit 21 (CPU: central processing unit), a storage unit 28, a communication I/F 22 (interface), an input/output unit 23, a clock unit 29A, and a position calculation information detection unit 29B. The HW components of the terminal 20 are connected to each other via a bus B, for example and not as a limitation. It is not essential that the HW configuration of the terminal 20 includes all of the components. For example and not as a limitation, the terminal 20 may or may not be configured such that individual components or multiple components are detachable.

The communication I/F 22 sends and receives various data via the network 30. Communication may be performed either wired or wirelessly, and any communication protocol may be used as long as mutual communication is possible. The communication I/F 22 has the function of communicating with various devices, such as the server 10, via the network 30. The communication I/F 22 transmits various data to various devices, such as the server 10, in accordance with 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. Furthermore, if the communication I/F 22 is configured as 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 and output units, or may not be so.

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

The output unit may be any one or a combination of any type of device capable of outputting the results of processing performed by the control unit 21. Examples of output units include, but are not limited to, touch panels, touch displays, speakers (audio output), lenses (for example, but not limited to, 3D (three dimensions) output and hologram output), printers, 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 or a combination of any type of device capable of displaying 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 (such as, but not limited to, liquid crystal displays and organic electroluminescence displays (ELDs)), head-mounted displays (HDMs), projection mapping, holograms, and devices capable of displaying 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, for example and without limitation, with a clock that uses a quartz oscillator. The clock unit 29A can also be referred to, for example and without limitation, as a timekeeping unit or a time information detection unit.

Note that 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 without limitation.

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

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 calculations 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 necessary to calculate the position of the terminal 20 using inertial navigation calculations. 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.
By way of example and not 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 a positioning ultra-wideband pulse signal 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 intervals or specific intervals 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 the calculated terminal position history data in the storage unit 28.

The control unit 21 has circuits physically structured to execute the functions realized by the code or instructions contained in the program, and is realized, for example and without limitation, by 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), or a field programmable gate array (FPGA).

The storage unit 28 has the function of storing various programs and data required for the operation of the terminal 20. The storage unit 28 includes, but is not limited to, various storage media such as a hard disk drive (HDD), a solid state drive (SSD), flash memory, random access memory (RAM), and read-only memory (ROM). Furthermore, the storage unit 28 may or may not be referred to as 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 as a limitation. Note that the HW of the server 10 does not necessarily have to include all components as a configuration of the HW of the server 10. For example and not as a 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 circuits physically structured to execute the functions realized by the code or instructions contained in the program, and is realized, for example but not limited to, 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, processor core, multiprocessor, ASIC, or FPGA, or may not be one of these. In this disclosure, the control unit 11 is not limited to these.

The storage unit 15 has the function of storing various programs and data required for the operation of the server 10. The storage unit 15 is realized by various storage media such as an HDD, SSD, or 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 referred to as memory.

The communication I/F 14 sends and receives various data via the network 30. Communication may be performed either wired or wirelessly, and any communication protocol may be used as long as mutual communication is possible. The communication I/F 14 has the function of communicating with various devices such as the terminal 20 via the network 30. The communication I/F 14 transmits various data to various devices such as the terminal 20 in accordance with 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. If the communication I/F 14 is configured as 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 accept 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, for example and without limitation, a touch panel, a camera (for operation input via moving images), or a microphone (for operation input by voice).

The output unit may be any one or a combination of any type of device capable of outputting the results of processing performed by the control unit 11. Examples of output units include, but are not limited to, touch panels, touch displays, speakers (audio output), lenses (for example, but not limited to, 3D (three dimensions) output and hologram output), printers, etc.

In the first embodiment, the input/output unit 12 includes 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 without limitation, an RTC (Real Time Clock) as a hardware clock, a system clock, etc. The clock unit 19 can also be referred to as, for example and without limitation, a timekeeping unit or a time information detection unit.

(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 not only by a CPU having a control circuit, but also 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 be realized by one or more integrated circuits, and multiple processes shown in each embodiment may or may not be realized by a single integrated circuit. LSIs are sometimes referred to as VLSIs, super LSIs, ultra LSIs, etc., depending on the level of integration. Therefore, the control unit 21 may or may not be referred to as a control circuit.
The same applies to other devices.

Furthermore, 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 on a computer-readable storage medium. The storage medium may store the program P on a "non-transitory tangible medium." Furthermore, the program P may or may not be intended to realize part of the functions of each embodiment of the present disclosure. Furthermore, the program P may or may not be a so-called differential file (differential program) that can realize the functions of each embodiment of the present disclosure in combination with a program P already recorded on a 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 thereof. The storage medium may be volatile, non-volatile, or a combination of volatile and non-volatile, as appropriate. Note that the storage medium is not limited to these examples and may be any device or medium capable of storing the program P. Furthermore, the storage medium may or may not be referred to as 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 the program P stored in the 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). For example and not by way of limitation, the server 10 and/or the terminal 20 executes the program P downloaded via the Internet or the like to realize the functions of the multiple functional units shown in each embodiment.
The same applies to other devices.

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 configured by one or more computers.
At least a part of the processing in the terminal 20 may or may not be performed by the server 10. In this case, at least a part of the processing of each functional unit of the control unit 21 of the terminal 20 may or may not be performed by the server 10.
At least a part of the processing in the server 10 may or may not be performed by the terminal 20. In this case, at least a part of the processing of each functional unit of the control unit 11 of the server 10 may or may not be performed by the terminal 20.
Unless explicitly stated otherwise, the judgment configuration in the embodiments of the present disclosure is not essential, and a predetermined process may or may not be performed when the judgment condition is met, or when the judgment condition is not met.

The programs disclosed herein may be implemented using, but are not limited to, 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 also be implemented by a system that does not include a server, such as the following system, by way of example and not limitation.
A system (distributed system) in which the terminal 20 has the function of a server. This can be realized by using, for example and not by way of limitation, blockchain (chain) technology.
A system in which terminals 20 communicate wirelessly with each other. This can be realized, for example and without limitation, by communicating in a P2P (peer-to-peer) manner using short-range wireless communication technology such as Bluetooth.

Furthermore, below, the expression "through a communication I/F" will be used where appropriate. This indicates, by way of example and not limitation, that the device sends and receives various information and data via the communication I/F (via the communication unit) based on the control of a control unit (processor, etc.).

<Overview>
In recent years, applications (application software) related to network services, such as applications for making payments using electronic currency (payment applications), applications for making settlements using electronic currency (settlement applications), applications for sending/receiving money using electronic currency (remittance applications), and applications that combine some or all of the functions of these applications, have become 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 a terminal 20 managed by the various applications described above, or by a user of the terminal 20.

Electronic currency may or may not be expressed as "electronic money" or "digital currency (digital currency)."
Furthermore, as "electronic currency (electronic money)" or "digital currency (digital money)", legal tender or virtual currency may be used.
Furthermore, "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 generally be used, and by way of example and not limitation, the balance in the electronic money account of a user of terminal 20 will be referred to as the "electronic money account balance."

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

In the following, the term "remittance reminder" refers to reminding, recalling, or reconfirming the contents of a remittance request to the other user, and information related to this remittance reminder is referred to as "remittance reminder information."
Reminding someone to remit money may be expressed as "reminding someone to remit money" or "reminding someone to remit money."
In addition, being reminded to remit may be expressed as "being reminded to remit" or "a remittance reminder is made."

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 expressed as the "remittance requesting user" or "remittance requesting main user."

Furthermore, in the following description, it is assumed that various processes according to the present invention are performed by a payment application or messaging application installed on terminal 20. In this case, by way of example and not limitation, a payment application may have a messaging service function as one of its functions, or a messaging application may have a payment service function as one of its functions.

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 a data communication line 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 for one-on-one user chats, as well as group chat rooms for chatting among a group of multiple users formed in a messaging service.

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

There is also a view that messaging services (MS) (including IMS) are 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 input made to a display based on the remittance reminder information displayed on the remittance request destination user's terminal 20 (hereinafter referred to as the "remittance reminder display").

First Example
In the first embodiment, the terminal 20 of the remittance request recipient 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 reminding."
The contents described in the first embodiment can be applied to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<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, a payment application management processing unit 111 that performs processing to provide various payment services using 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, but is not limited to this.

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 that 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, but not limited to, a user name, an application ID, a terminal phone number, and other registration information are stored in association with each other.

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

The application ID is information used to identify a payment application account, or the account itself.
This application ID is preferably a value that is unique for 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 about the terminal or information about the user of the terminal.

The terminal phone number is the phone number of the terminal 20 of the user with this username; 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 (by way of example and not limitation, IMEI (International Mobile Equipment Identity)), 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, for an application that allows only one account to be registered per terminal 20, as an example and not a limitation, "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 device IDs to one user ID.

The user management database 155 is a database that cumulatively stores data for managing information about the terminals 20 that use the payment application or their users. Figure 1-5 shows an example of the configuration of the first user management database 155A.

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

Remittance history data is data that stores information about the history of remittances from users of this application ID to users of other application IDs (remittance history information).

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 (receive 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.
The first remittance request management data 157A stores, by way of example and not limitation, the date and time, remittance request management ID, remittance master ID, remittance request destination ID, remittance request amount, and remittance completion flag in association with each other.

The date and time stored is, by way of example and not limitation, 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 recipient user.

The remittance request management ID stores an ID that is uniquely assigned 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 recipient user in 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 made. It is initially set to "OFF" and is set to "ON" once the remittance is completed.

Here, the method by which the server 10 manages remittance requests can be broadly divided into the following two patterns.
"Pattern A": Remittance requests that have been remitted (remittance completed flag ON) are left as they are 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 payment application processing, 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 positioned opposite the display, thereby forming a touchscreen. When an element such as an icon, button, item, or input area is displayed on the display, and a user operates a part of the touch panel that faces the area where the element is displayed, a program associated with that element or a subroutine of that program is executed.

In the following, tapping (tapping operation) will be exemplified as an example of a user operation, but is not limited thereto.
A tap (tap operation) is, by way of example and not limitation, an action in which a user lightly taps 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 techniques of the present disclosure. In the display screen transitions illustrated below, some of the 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 (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 words "Payment App" and an icon indicating that the display is based on the functionality of a payment application, and a message (by way of example and not limitation, "A.A.", "You have a remittance request") notifying that the remittance request information has been received and the username of the first user who made the remittance request.

Also, on the left side of the remittance request display MS1, a button BT1 is displayed for confirming detailed information about the remittance request.
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 (for example, and not by way of 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.

Figure 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 Figure 1-9, B.B., the user of the terminal 20, taps button BT1, resulting in a transition to the screen shown in Figure 1-10.
The words "Payment App" are displayed at the top center 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 the user name (in this example, "B.B.") of the user in the payment application of this terminal 20.

Also, below that, 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.") are displayed.
Further below, a remittance request display MS2 showing the details of the remittance request is displayed.

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 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 the 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 username of the first user, a message indicating that remittance request information has been received from that user (in this example, "You have received a remittance request from A.A."), and link information for displaying more detailed information about the remittance request (in this example, the portion displaying the text ">View 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 being limiting, 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 terminal 20 taps remittance button BT2 on this screen, the screen transitions to a remittance screen (the screen in FIG. 2-8, for example and not by way of limitation) for remitting the amount specified in the remittance request information. When the user (B.B.) taps remittance area RM2 at the bottom of this remittance screen, the screen transitions to a remittance confirmation screen (the screen in FIG. 2-9, for example and not by way of limitation).
When user B.B of terminal 20 taps confirmation button BT6 on the remittance confirmation screen, the amount specified in the remittance request (remittance request amount: the amount shown in 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 the 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) urging 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 user's (B.B.) terminal 20.

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, a remittance reminder message can be displayed on the display unit 24 of the terminal 20 of that user (B.B).

In the example of Figure 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 Figure 1-9 in that it includes a message (by way of example and not limitation, "A.A.", "You have a (terminal reminder) remittance request.") notifying the user that a remittance reminder has been generated based on the functionality of the terminal 20 (i.e., that a terminal reminder has been generated) and the username of the first user associated with the remittance reminder.

Additionally, a button BT3 for checking detailed information about 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 and is 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.

Figure 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. In other words, in Figure 1-11, user B.B. taps button BT3, resulting in the screen shown in Figure 1-12.

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

By way of example and not limitation, the remittance reminder display MS4 differs from the remittance request display MS2 shown in Figure 1-12 in that it notifies the user that the remittance process corresponding to the remittance request information has not yet been executed, 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 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 format of the message notifies the user that a remittance reminder has been issued because the remittance process for the remittance request has not yet been carried out.

Furthermore, the remittance reminder display MS4 includes a remittance button BT4 for executing a remittance process for 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 terminal 20 taps remittance button BT4 on this screen, the screen transitions to a remittance screen (the screen in FIG. 2-8, for example and not by way of limitation) for remitting the amount specified in the remittance reminder display MS4. When the user (B.B.) taps remittance area RM2 at the bottom of this remittance screen, the screen transitions to a remittance confirmation screen (the screen in FIG. 2-9, for example and not by way of 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 transferred from the electronic money account of the user (B.B) of terminal 20 to the electronic money account of the first user (A.A).

In this way, by way of example and not limitation, based on input by the user (B.B) of terminal 20 to the second display (remittance reminder display MS3 and button BT3, remittance reminder display MS4 including remittance button BT4) displayed on display unit 24, remittance processing for remittance from the user (B.B) of the terminal to the first user (A.A) based on a remittance request is executed by control unit 21 of terminal 20.

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

The processes described below are merely examples of processes for realizing the method of the present disclosure, and the present disclosure is not limited to these processes.
Furthermore, other steps may be added to the processing described below, or some steps may be omitted (deleted).
This also applies to each flowchart (process) 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.
By way of example and not 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 on the display unit 24.
In addition, the remittance reminder can be sent two or more times, but for simplicity, the process of determining whether the process is complete will be omitted and the illustrations and explanations will be given for the case where the remittance reminder is sent only once. The same applies to the case where the remittance reminder is sent two or more times.

First, the control unit 21 of the terminal 20A determines whether to request the execution of a remittance request based on whether an input to request the execution of a remittance request (hereinafter referred to as "remittance request execution input") has been made to the input unit, by way of example and not limitation (A110).
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 sends 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 send the remittance request information (A120).

The remittance request transmission request information may include, by way of example and not limitation, at least the identification information of user A.A. of user terminal 20A (by way of example and not limitation, the application ID), the identification information of user B.B., the remittance request destination user (by way of example and not limitation, the application ID), and the remittance request amount (the 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, for example and without limitation, a remittance request management ID, information that allows the user to identify (recognize) that it is a remittance request (for example and without limitation, text, images, etc. indicating that it is a remittance request), information on the remittance request amount, and information on the remittance master user (for example and without limitation, the username of the remittance master user).

In addition, the information about the remittance master user is not limited to the user name, and may or may not include information such as the application ID, the remittance master user's terminal phone 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 remittance based on the received remittance request information (for example, but not limited to, operational images such as remittance buttons and remittance icons).

Thereafter, the control unit 21 of the terminal 20B determines whether or not to execute the remittance based on the remittance request (B120). For example and not by way of limitation, it determines 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 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 it has been received (S120: YES), executes the remittance settlement process (S130).
Specifically, by way of example and not limitation, the amount of the planned remittance is subtracted from the balance of user B.B's electronic money account as the remittance amount, and the amount of the remittance is added to the balance of user A.A's electronic money account to update the balance.
The remittance amount is the amount remitted from the remittance request destination user to the remittance master user.
In addition, 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 is set to "ON", no further remittances will be made.

In addition, in the remittance settlement process, if the balance in the electronic money account is insufficient (if the amount to be remitted exceeds the balance in the electronic money account), the remittance will not be carried out.
In this case, the control unit 11 of the server 10 transmits information to the terminal 20B prompting the terminal 20B to charge the balance of the electronic money account. Then, based on the information requesting charging received from the terminal 20B, the electronic money account balance may be charged and then the remittance may or may not be carried out.

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

Furthermore, the control unit 11 of the server 10 transmits the receipt information, which is information relating 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 displays the received remittance information on the display unit 24 (B140).

Then, the control unit 21 of terminal 20B determines whether 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, the control unit 21 determines to issue a remittance reminder.

Basically, if the 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, rather than sending a 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, for example and not by way of limitation, after a certain period of time has elapsed.

If it is determined that a remittance reminder should be sent (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 may be the same as that of the remittance request display, except for, for example and without limitation, information that allows the user to identify (recognize) that it is a remittance reminder (for example and without limitation, text, images, etc. indicating that it is a remittance reminder).

The content of the remittance request display and 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).
"Input" can be, for example, but not limited to, an operation on an input unit (operation unit), and for example, but not limited to, 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 for example, and without limitation, a tap on the display area of any of the various remittance reminder displays MS described above can be used as input to realize a remittance.

If it is determined that 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 settlement request information may include the remittance request management ID and the planned remittance amount of the previously received remittance request information.

The control unit 11 of the server 10 determines whether or not remittance settlement request information has been received from terminal 20B via the communication I/F 14 (S120), and if it determines that it 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 displays the received remittance information on the display unit 24 (B140). Then, the control unit 21 of the terminal 20B ends the process.
Furthermore, when the communication I/F 22 receives the receipt information from the server 10 (A140: YES), the control unit 21 of the terminal 20A displays the received receipt information 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 control unit 21 of the terminal 20 (for example, but not limited to, the terminal 20 of the user to whom the remittance request is made) includes a remittance processing (hereinafter, the remittance processing executed by this terminal will be 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. The remittance process performed by the terminal may include not only a process directly related to the remittance, but also a process indirectly related to the remittance.

In the above example process, the first remittance process includes, by way of example and not limitation, 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 inputs to execute a remittance request or inputs to display a remittance reminder, are considered to be operation inputs to the input unit (operation unit), but this is not limiting.

As an example and not as a limitation, instead of or in addition to operation 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.
This is also 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 (a non-limiting example of first information related to a remittance request) from a remittance master user (a non-limiting example of a first user) via the communication I/F 22. Then, the terminal 20 displays a remittance request display (a non-limiting 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) that is 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 (not limiting, an example of an input to the second display) displayed on the display unit 24.
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 input to the second display displayed on the display unit of the terminal, making it possible to easily transfer remittances 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 limited to, 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 limited to, but an example of information on the amount based on the remittance request).
As an example of the effect of this embodiment, the amount based on the remittance request can be reliably notified to the terminal user by the first and second displays.

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 this embodiment obtained by such a configuration, the information of the user who has requested the remittance can be reliably notified to the terminal user 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 the first display) and the remittance reminder display (not limiting, an example of the 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 this embodiment obtained by such a configuration, the user of the terminal can easily recognize the first display and the second display by using 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 (including, but 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 this embodiment obtained by such a configuration, it is possible to notify 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, but an example of information regarding a request for remittance processing based on a remittance request) via the communication I/F 22.
As an example of the effect of this 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 Example (1)>
If the first remittance process has not been executed (has not been 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, if the first remittance process has been executed (has been 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 has been made may or may not be displayed on the display unit 24.

The indication that a transfer has not been made 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 that the transfer has not been made.
Similarly, the indication 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 transfer has been completed.

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

<First Modification Example (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 a type of reminder display or a type of reminder notification.

In addition to this push notification, reminder notification processing can also be performed based on the following control, for example and not by way of limitation.
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 amount of light.

In addition to when it is time to execute a device reminder, you can also 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, conditions such as "the current time is not included in the time period when the user is likely to be asleep (late at night (until midnight the next day), early morning (until 3:00 the next day), or 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 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 the reminder notification process using the control unit 21 based on the set reminder notification conditions (not limited to, but an example of the second conditions).
As an example of the effect of this modified example obtained by such a configuration, it is possible to notify the user of the terminal at an appropriate timing that a terminal reminder will be executed based on the set conditions.

<First Modification Example (3)>
In the first embodiment, when executing a remittance based on a remittance request on the terminal 20 of the remittance request recipient 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 processing 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 and 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 can 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 proceeds to B130.

This modified example shows a configuration in which the terminal 20 of the remittance request destination user executes, via the control unit 21, a process (not limited to, but 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 limited to, but an example of a first display).
As an example of the effect of this embodiment obtained by such a configuration, remittance based on a remittance request can be easily realized based on an input by the terminal user on the first display.

<First Modification Example (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 that sells products (including providing services) or a business that operates a money lending business, and other businesses (stores) that are expected to request money from the user of terminal 20 through a remittance request.

In this case, in the above embodiment, these businesses obtain an account for the payment service (payment application). They can then use this account to 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 recipient user).

The account acquired by the business (store) may be a general 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 the 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 of stores can be made users (first users) who can make remittance requests to the user of the terminal.

<First Modification Example (5)>
It is conceivable 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 senior or a close friend of the user.

Therefore, the user who requests a remittance request or a remittance reminder may not be the user of the terminal 20, but may be a user who uses a business account.
A business account is, by way of example and not limitation, a user who has an official account (hereinafter referred to as an "official account" and, where appropriate, as an "OA: Official Account") for the service (in the above example, a payment service).

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

This modified example shows a configuration in which the user requesting remittance (an example of a first user, not limited to this) is a user who uses an official account (an example of a business account, not limited to this).
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 upon 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 can be applied to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<Data structure>
FIG. 2A is a diagram showing an example of the structure 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, information type is also stored in association with the first remittance request management data 157B, for example and not by way of limitation.

The information type is information used to identify 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, if the information type of the corresponding remittance request is "request," the date and time that the remittance request information was sent from the server 10 to the terminal 20 of the remittance request recipient user is stored; if the information type of the corresponding remittance request is "remind," the date and time that the remittance reminder information was sent from the server 10 to the terminal 20 of the remittance request recipient user is stored.

Furthermore, 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 the 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 the data for the corresponding remittance requests and remittance reminders.

<Display screen>
FIG. 2B shows an example of information displayed on the display unit 24 when a payment application is running on the terminal 20 of the first user (AA).
The display unit 24 displays the balance of the first user's (A.A.) electronic money account (in this example, "25,000 yen"), as well as icons corresponding to each function that can be executed in the payment application.
The first user (A.A.) can check whether a remittance has been made, and if so, the user who made the remittance and the remitted 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 accordance with a remittance request.

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

Then, in the terminal 20 of the first user (A.A.), information about the user who is the target 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 the users who have been the target of previous remittance requests and the remittance amounts requested for those users.

In this example, as shown in Figure 2-3, below the title "Remittance Request List," 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.
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 the user's terminal 20 received the remittance request information (in this example, 2020.04.20 21:30), the remittance amount requested for 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 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 has check boxes, and when the user checks the check boxes, each piece of information displayed in area R1 is selected.

In the example of Figure 2-3, an area RR displaying "Remind" is provided at the bottom of the screen. When the first user (A.A) taps area RR with the checkbox checked, remittance reminder information based on the information displayed in area R1 is sent 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 the remittance reminder information, or when 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 Figure 2-4, a remittance reminder completion display MS5 is displayed on the terminal 20 of the first user (A.A) to notify that the remittance reminder has been completed.
The remittance reminder completion message MS5 includes the username of the user who requested the remittance (B.B. in this example).

As shown in Figure 2-5, 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.

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.", "[Reminder received] Remittance request.") informing the first user of the username of the remittance reminder based on receiving the remittance reminder information.
The remittance reminder display MS3 shown in Figure 1-11 displays "Terminal Reminder" because it is a remittance reminder display based on the functions of the own terminal, whereas the remittance reminder display MS3A displays "Reminder Received" because it is a remittance reminder display based on received remittance reminder information.

Also, on the left side of the remittance reminder display MS3A, a button BT3A for checking detailed information regarding the remittance reminder is displayed.
Without limitation, the remittance reminder display MS3A and 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 button BT3A are an example of a second display that is displayed on the display unit 24 when the terminal 20 receives 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 changes 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 words "Reminder Received" based on the receipt of the remittance reminder information, and a message notifying the first user of the username based on the receipt of the remittance reminder information (by way of example and not limitation, "[Reminder Received] A remittance request has been received from A.A.").

The remittance reminder display MS4 shown in Figure 1-12 displays an icon with the words "Terminal Remind" because the remittance reminder display is based on the functions of the device itself, whereas the remittance reminder display MS4A displays an icon with the words "Remind Received" because the remittance reminder information has been received.
Another difference is that in the remittance reminder display MS4A in Figure 2-6, the word [Received reminder] is displayed before the first user's username (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 the link information displayed as ">Check details" on the remittance reminder display MS4A, the screen moves to the screen shown in FIG. 2-7.
The screen in Figure 2-7 notifies the user of the terminal 20 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). The user is also notified that they are the one making the payment (in this example, an icon with the word "Payment") and the amount to be paid (in this example, "3,000 yen").

On the screen in Figure 2-7, information about remittance reminders is displayed in an area larger than the remittance reminder display MS4A described above, along with an animal character. 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 remitting the amount corresponding to the remittance request and remittance reminder to the first user (in this example, the part displaying the words ">Remit money").

When the user (B.B.) of the terminal 20 taps the remittance link information, the screen changes to the remittance screen shown in FIG. 2-8.
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 (B.B.) of terminal 20 is in the position to make the payment (in this example, an icon with the word "payment"), and the amount that the user (B.B.) of terminal 20 can currently 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 remittance amount to be sent to the first user, the user (B.B) of terminal 20 is now able to send the amount corresponding to the remittance request information and remittance reminder information to the first user (A.A).

When the remittance area RM2 at the bottom of this 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 username (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, the 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 that is 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 by 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 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 terminal 20A in S120, it determines to issue a remittance reminder.

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

If it is determined that a remittance reminder should be sent (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 sends the created remittance reminder information, together with the remittance request management ID, to 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 terminal 20B displays a remittance reminder message on the display unit 24 (B250). The control unit 21 of terminal 20B then transfers processing 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 process in 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 to request the execution of a remittance reminder (A260) based on 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, for example and not by way of limitation.
The remittance reminder execution input can be realized by, for example and not by way of limitation, operation input or sound input, similar to the remittance request execution input described above.

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

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

<Remittance process executed by the 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 (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. The remittance process performed by the terminal may include not only a process directly related to the remittance, but also a process indirectly related to the remittance.

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).
(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 (an example of first information, not limiting) regarding a remittance request by a remittance master user (an example of a first user, 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 a first user, not limiting) to the remittance master user's terminal 20.
On the other hand, the 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 the remittance reminder display (an example of second display, not limiting) is configured to be 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 an effect obtained by this configuration, first information can be transmitted to the terminal via the server in accordance with the intention of the first user who has requested the remittance, and 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.

Furthermore, 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 the remittance request) to the terminal 20 of the remittance request destination user via the communication I/F 14. The server 10 then executes, via the control unit 11, a second remittance process (not limiting, an example of remittance process related to a remittance from the user of the terminal to the first user based on the remittance request) 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 this modified example obtained by such a configuration, the remittance process can be executed by the control unit of the server based on input to the second display displayed on the display unit of the terminal, making it possible to easily transfer remittances 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 needed.

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.).
As an example, but not by way of limitation, this remittance request list screen displays, below the title "Remittance Request List," a remittance request history for 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 A.A.'s icon image and user name, 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 owed 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 the remittance request information from D.D. was received is 2020.04.21 08:42, and the amount owed to D.D. is "500 yen."

With regard to 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. Therefore, in area R22 below area R21 (which is not a limitation and is an example of a display area for the remittance reminder information corresponding to the display area for the remittance request information), an icon image and user name of A.A., an icon with the text "Reminder Received," the date and time the remittance reminder information was received (2020.04.23 17:00), an icon with the text "Payment" indicating that A.A. is in a position to make a payment, and the amount owed 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 "Payment" icon, indicating that the payment is being made to A.A., and the amount owed to A.A. (3,000 yen) are the same.

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

By way of example and not limitation, the display positions of at least some of the information (by way of example and not limitation, the image icon and username of the first user and the icon displayed above them) differ 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 that 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 can be sorted by the user of the terminal 20 .
When the user taps 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 informing users 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 enabling messages to be sent and received between the registered friends via the server 10. A messaging application account owned by an individual user is referred to as a "general account." A history of messages sent and received between the 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 a non-limiting example, 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 a non-limiting example) who are registered as friends of the first user (A.A. and D.D.) who made the remittance request are displayed in alphabetical order.
In this example, the icon image and user name of the first user A.A. are displayed in region R21, and the icon image and user name of the 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 about the remittance amount is displayed.
The screen shown in FIG. 2-15 allows the user to at least identify the first user who has made the remittance request.

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 as 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 that the history is related to the remittance request of the selected first user (A.A.) (for example, but not limited to, the words "List of remittance requests from A.A."), and below that, detailed history related to the remittance request of the selected first user (A.A.) is displayed in the manner shown in Figure 2-13.

As an example and not as a limitation, the information displayed in areas R21 and R22 of Figure 2-13 (which are not limited to examples of display based on remittance request information and examples of display based on remittance reminder information) is displayed in areas R21 and R22 of Figure 2-16.
Note that the history of remittance requests from other first users (DD) who have not been selected is not displayed.

As a non-limiting example, 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 (non-limiting examples of a display based on remittance request information, examples of a display based on remittance reminder information) of the first user (A.A. and D.D., as examples, not limited to) who made the remittance request is displayed based on the date and time of receipt.

In this example, the most recent history is based on remittance reminder information (received on April 23, 2020 at 17:00) corresponding to a remittance request of 3,000 yen from the first user A.A., and therefore, the top region R21 displays a "Receive Reminder" icon along with A.A.'s icon image and user name.
The next most recent history entry is based on remittance request information (received at 08:42 on April 21, 2020) corresponding to a remittance request of 500 yen from another first user, B.B., and therefore, in the second region R22 from the top, an icon image and user name of B.B. and a "request received" icon are displayed.
Since the next most recent history entry is based on remittance request information (received on April 20, 2020 at 21:30) corresponding to a remittance request of 3,000 yen from the first user A.A., the third region R23 from the top displays a "request received" icon along with A.A.'s icon image and user name.

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), the remittance request information based on the second remittance request of the other first user (D.D) is received, and then the remittance reminder information based on the first remittance request of one first user (A.A) is received. Therefore, the information corresponding to the second remittance request is displayed in area R22, which is the area between area R21 where information corresponding to the first remittance request is displayed and area R23 where information corresponding to the first remittance request is displayed.

As an example, and not by way of 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, allowing the user to confirm whether the first user who made the remittance request or remittance reminder is a user registered as a friend in the payment application or a messaging application linked to the payment application.

As an example, but not by way of limitation, on the screen shown in Figure 2-7, when a user (B.B) of terminal 20 taps the link information for remittance displayed in area RM1, the friend registration confirmation screen of Figure 2-18 is displayed before transitioning to the remittance screen of Figure 2-8.
By way of example and not limitation, the friend registration confirmation screen is a screen superimposed on the screen of Figure 2-7, and displays a message (by way of example and not limitation, "Please check again whether the person who requested the money transfer is a friend. Do you want to transfer the money?") to allow the user (B.B) of terminal 20 to confirm whether the person to whom the money is being transferred (by way of example and not 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 the remittance screen shown in FIG. 2-8.
In this way, even if the link information for money transfer is tapped, a screen is displayed before transitioning to the money transfer screen, prompting the user to confirm whether the first user who sent the money transfer reminder is a user registered as a friend, thereby preventing the user from inadvertently transferring money to a user who is not registered as a friend.

<Second Modification Example (2)>
In relation to the first modified example (2), the terminal 20 of the remittance request destination user 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:

- Based on 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 amount of light.

By way of example and not limitation, "push transmission" means transmitting information to be sent (in this example, remittance reminder information) 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, reminder notification conditions similar to those in the first variant (2) can be set, and the reminder notification process can be executed when the reminder notification conditions are met.

In this modification, 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 performed 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 the effect of this 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 relates to the method and timing of displaying and transmitting remittance reminder information.
The contents described in the third embodiment can be applied to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

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 when the terminal reminding method 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 at which the remittance request display and remittance reminder display are displayed on the remittance request recipient user's terminal 20. Remittance request information is indicated by a white circle, and remittance reminder information is indicated by a white diamond.

The setting is "auto", which indicates that the terminal 20 of the remittance request destination user automatically displays the remittance reminder information.
In this setting, the terminal 20 of the remittance request destination user displays a remittance reminder message every time the set time tm has elapsed since the remittance request message was displayed, but this is 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.

<Effects of the Third Embodiment>
In this embodiment, the 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, 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. The terminal 20 of the remittance request destination user also displays a second remittance reminder display (not limiting, an example of a fourth display) on the display unit 24 based on the elapse of a set time since the display of the first remittance reminder display.
As an example of the effect of this 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 Example (1)>
The technique of the third embodiment can also be applied to the server remind 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", and 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 sends remittance reminder information to the remittance request destination user's terminal 20 based on a remittance reminder execution input made on the remittance master user's terminal 20. Specifically, the server 10 sends remittance reminder information to the remittance request destination user's terminal 20 based on receiving remittance reminder transmission request information from the remittance master user's terminal 20.

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

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 transmissions, the automatic remittance reminder information transmission will be delayed.

Specifically, by way of example and not limitation, the server 10 basically sends remittance reminder information to the terminal 20 of the remittance request destination user every time the set time tn has elapsed since the remittance request information was sent to the terminal 20 of the remittance request destination user. However, if manual remittance reminder information is sent between automatic remittance reminder information transmissions, the server 10 will send the remittance reminder information every time the set time tn has elapsed since the latest manual remittance reminder information was sent, instead of the latest automatic remittance reminder information.

Which of Settings A to C is applied can be determined, for example and without limitation, by sending information about the setting 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, this is not limited to this, and 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 server 10, etc.

In this variant, remittance request information (an example of first information, not limiting) is sent 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, the 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 the remittance reminder display (an example of 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 an effect obtained by this configuration, first information can be transmitted to the terminal via the server in accordance with the intention of the first user who has requested the remittance, and 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 fact that a set time has elapsed since the remittance request information was sent to the terminal 20 of the remittance request recipient 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, the second information can be transmitted 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.

Furthermore, in this modified example, the terminal 20 of the remittance request destination user receives, via the communication I/F 22, first remittance reminder information (a non-limiting example of third information based on a remittance request) transmitted from the terminal 20 of the remittance master user based on input by the remittance master user (a non-limiting example of a first user) to the terminal 20 of the remittance master user. The terminal 20 of the remittance request destination user then displays a first remittance reminder display (a non-limiting example of a third display) on the display unit 24. In this case, as a non-limiting example, a configuration is shown in which second remittance reminder information (a non-limiting example of second information) is transmitted to the terminal 20 based on the elapse 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, the second information based on the remittance request can be appropriately sent to the terminal based on the third information based on the remittance request being sent to the terminal.

<Third Modification (2)>
Regarding the terminal reminding 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 second and subsequent remittance reminder information.

Specifically, by way of example and not limitation, the terminal 20 of the remittance request recipient user displays the remittance request or displays the first remittance reminder when a first set time has elapsed since receiving the remittance request information.
Furthermore, the terminal 20 of the remittance request destination user displays the remittance reminder for the second time when a second set time has elapsed since the first display.
Furthermore, the terminal 20 of the remittance request destination user displays the remittance reminder for the third time 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 may 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, etc.) can be shorter than "24 hours." In this case, the other set times can all be the same or different.

When different times are used, the set time may be shortened each time a remittance reminder is displayed, by way of example and not limitation.
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", and so on.
By doing this, the time interval (display time interval) for displaying the remittance request gradually becomes shorter, making the remittance request recipient user aware that the remittance has not yet been made and alerting them to make the remittance quickly.

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

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

Furthermore, in setting C (auto & manual) in Figure 3-2, if manual transmission of remittance reminder information is sandwiched between automatic transmissions of remittance reminder information by the server 10, the automatic transmission of the remittance reminder information may or may not be skipped rather than delaying the automatic transmission of the remittance reminder information.

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

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

FIG. 4A 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 FIG. 1-14 in the flowcharts of FIGS. 1-13 and 1-14.

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

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

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

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

A specific example will be given.
(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 notify 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 determines 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 falls within 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 for the terminal reminder is reached.

By way of example and not limitation, the first set time period can be set to a time period when a user is likely to view the terminal 20, such as, for example and not limitation, a time period from 9 p.m. to midnight, when users are likely to have free time after returning home.

When this condition is applied, the timing of the terminal reminder may be, by way of example and not limitation, the timing described in the third embodiment (FIG. 3A).
In this case, the control unit 21 of the terminal 20 determines whether it is time to perform a terminal reminder. If it is time to perform a terminal reminder, the control unit 21 determines whether the time measured by the clock unit 29A is within the first set time period, and if it is determined that it is within the first set time period, the control unit 21 can display a remittance reminder message on the display unit 24.

For condition No. "PA-3," the remittance reminder condition is set as "the time for the reminder has arrived and the time is not included in the second set time period." The second set time period can be set to any time period you like 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 be viewing the terminal 20, such as late at night (until midnight the next day) when the user is likely to be asleep, before dawn (until 3 the next day), or at dawn (from 3 the next day).

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

For condition No. "PA-4," the remittance reminder condition is set as "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," but is not limited to this).
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.

By way of example and not limitation, you can set the date when the user to whom you are requesting money has extra money, or by way of example and not limitation, the date when their 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 as "the balance of the electronic money account is equal to or greater than a set amount." The set amount can be set to any amount (for example, "30,000 yen," but this is not a limitation).
This condition is intended to notify 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 certain large amount, such as more than twice the maximum remittance request amount for the remittance request recipient 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 about the balance of the electronic money account of the user of the terminal 20 via the communication I/F 22. When the inquiry about the electronic money account balance is received from the terminal 20 via the communication I/F 14, the control unit 11 of the server 10 transmits information about the balance of the electronic money account of the user to the terminal 20 via the communication I/F 14.
Then, the control unit 21 of the terminal 20 determines whether the electronic money account balance has reached or exceeded a set amount based on the received information on the electronic money account balance, and if it determines that the electronic money account balance has reached or exceeded a set amount, it can cause the display unit 24 to display a remittance reminder message.

For condition No. "PB-2," the remittance reminder condition is set as "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" but is not limited to this).
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 balance entered by the user into the terminal 20 becomes equal to or greater than the set amount.

In this case, the control unit 21 of the terminal 20 prompts the user to enter their balance by, for example, displaying a screen on the display unit 24 that prompts the user to enter their balance. The control unit 21 then determines whether the entered 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 display a remittance reminder message on the display unit 24.

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

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

As a non-limiting example, a remittance reminder condition could be set as a situation in which the remittance request recipient user has financial leeway due to a loan service provider depositing (transferring) funds into the balance of the remittance request recipient user's bank (for example, 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 a deposit has been made by borrowing a loan based on information (including notifications) sent from the server 10. If it determines that a deposit has been made, the control unit 21 can display a remittance reminder message on the display unit 24.

For condition No. "PC-2," the remittance reminder condition is set as "receive payment when the exhibited item is purchased."
This condition is intended, by way of example and not limitation, to inform the user that a remittance has not yet been made by displaying a remittance reminder on the display unit 24 when a user uses a flea market service, by way of example and not 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.

As a non-limiting example, a remittance reminder condition could be defined as a situation in which the remittance request recipient user has financial leeway due to a deposit (remittance) from a flea market application being made into the balance of the electronic money account of the payment application of the remittance request recipient user.

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

(3) Category "Other"
For condition No. "PD-1," the remittance reminder condition is set as "the exhibited item has been purchased (payment not yet made)."
This condition is not intended to be limiting, but rather is an example, and 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 when an item that the user has listed for sale using a flea market application or the like is purchased (at the time when the money has not yet been deposited into the electronic money account balance).

By way of example and not limitation, if a product that the remittance request recipient user has listed via a flea market application or the like is purchased, it is possible to expect that the purchase of the listed product will result in the remittance request recipient user's electronic money account balance being credited, even though it has not yet been credited via the flea market application. Therefore, the remittance reminder conditions can be set to include cases in which the remittance request recipient user is expected to have financial leeway.

In this case, the control unit 21 of the terminal 20 can determine whether or not an item 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 determines that the item has been purchased, can cause a remittance reminder to be displayed on the display unit 24.

For condition No. "PD-2," the remittance reminder condition is set as "currently seeking 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 when 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 the user applies to a company or when the user receives a job offer from the company).

By way of example and not limitation, if the remittance request recipient user is looking for work in a job search service, etc., this can be determined as a remittance reminder condition, since the remittance request recipient user is looking for work and is likely to receive wages after working, which can be expected to result in financial leeway for the remittance request recipient user.

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

For condition No. "PD-3," the remittance reminder condition is set as "purchase of product 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.

By way of example and not limitation, the following conditions can be defined as conditions for a remittance reminder: when the remittance request recipient user purchases an item through a flea market application, etc.; or when the remittance request recipient user is recognized as having financial means.

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

The above remittance reminder conditions may 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.

As a non-limiting example, the remittance master user's terminal 20 may or may not set the above remittance reminder conditions 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 sent 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.

Furthermore, 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 based on a combination of two or more conditions.

<Display screen>
Figure 4-3 shows, by way of example and not 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 the user's (B.B.) account is credited 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 word "Received" 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 user (B.B.) has at least the amount equivalent to the sales amount remaining in their electronic money account.

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

The content of message MS26 is the same as 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 by way of limitation, terminal 20 receives message MS26 immediately after receiving message MS25. Therefore, it can be said that user (B.B.) is likely to check message MS26 when there is at least an amount equivalent to the sales amount remaining in his/her 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 made to his/her account.

<Effects of the Fourth Embodiment>
In this embodiment, the remittance reminder display (not limiting, but 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, but an example of the first conditions).
As an example of the effect of this 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 reminding conditions include conditions such as time, time period, date, and elapsed time (these are not limited to these, but are examples of conditions related to time).
As an example of the effect of this 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 time-related conditions.

In addition, in this embodiment, the remittance reminding condition includes a time or period 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 to whom the remittance request is made.

In addition, this embodiment shows a configuration in which the remittance reminding condition includes a time or period condition set by the remittance master user's terminal 20 (not limited to, but an example of the first user's terminal).
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 regarding the balance of the remittance request recipient user's electronic money account balance, possession balance, etc. (not limited to, but 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 this 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 relating to remittance to the user of the terminal.

In addition, this embodiment shows a configuration in which the conditions for depositing (remittance) to the remittance request destination user include that the remittance request destination user deposits (remittances) by 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 terminal user is likely to have 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 a 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 an item put up for sale by the user of the terminal is purchased and the purchaser makes a deposit (remittance), and the user of the terminal has some extra money.

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, which makes it likely that the terminal user will have some extra money.

<Fourth Modification Example (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, the same conditions as the remittance reminder conditions exemplified in the table in Figure 4-2 can basically be applied. However, in this modified example, the remittance reminder conditions are determined by the server 10, not the terminal 20.

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, when applying condition No. "PA-2" or condition "PA-3", the timing of the reminder can be, by way of example and not limitation, the timing of the server reminder described in the third variant example (1) (Figure 3-2).

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

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

Regarding the conditions in the category "Other," the 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 be able to obtain information indicating that the product listed 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 the 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 the user of the terminal 20 is searching for job search information using the job search service.
Furthermore, if the business providing the job search service is different from the business providing the payment service, the determination can be made by configuring the control unit 11 of the server 10 to be able to obtain information indicating that the user of the terminal 20 is using the job search service from a device such as a server of the business providing the job search service.

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 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 be able to obtain information indicating that the user of the terminal 20 has purchased the item being put up for sale from a device such as the server of the business providing the flea market service.

FIG. 4-5 is a flowchart showing an example of the flow of processing executed by each device in this modified example.
This flowchart is a rewrite of the processing portion of FIG. 4-1.

After S150 in FIG. 1-13, the control unit 11 of the server 10 determines whether the remittance reminder conditions are met (S460). If it is determined that the conditions are 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 modification, based on whether the remittance reminder condition (not limited to, but an example of the first condition) is met, the terminal 20 of the remittance request destination user receives remittance reminder information (not limited to, but an example of the second information based on the 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 this configuration, the terminal can receive and display the second information based on the remittance request in accordance with the first condition. Furthermore, since the terminal does not need to determine whether the first condition is met, the processing load on the terminal can be reduced.

<Fourth Modification Example (2)>
In the fourth variant (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. 4-5.

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

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 illustrated using 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 chat 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. sends a message to B.B. and C.C. requesting that they 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 situation in which C.C., a user of one terminal 20, has replied that he has sent money, but B.B., a user of the other terminal 20, has not replied.
A. When 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 appears in the chat room.

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

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 have not yet been completed is displayed in the chat room.

In this example, the first user (A.A.) 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. Therefore, area R1 displays B.B.'s icon image and username, an icon with the words "Request Sent," the date and time the remittance request information was sent (2020.04.20 21:30), an icon with the word "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).

In this example, an area RR is provided at the bottom of the screen that displays "Remind." When the first user (A.A.) checks the checkbox in area R21, each piece of information displayed in area R21 is selected.
When area RR is tapped in this state, remittance reminder information based on the information displayed in area R1 is sent to the terminal 20 of the 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 the message displayed on the terminal 20 of a first user (A.A) belonging to group X, the message displayed on the terminal 20 of a user (B.B) who is the target of a remittance reminder from the first user, and the 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 limitation, message MS11 includes a "Sent Reminder" icon indicating that remittance reminder information has been sent to users in the group, the text [Payment App] indicating that the message is based on the functionality of a payment application, the username of the user in the group who received the remittance reminder information (in this example, the text "Request remittance to B.B."), the amount requested to be remitted in the remittance reminder information (in this example, 3,000 yen), and a "Receive" icon 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 recipient 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 because 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.), no message indicating that the remittance has been declined will be sent to other users.
Therefore, the button BT11b is displayed in an unselectable state because no message is sent in response to the operation.

On B.B's terminal 20, which received the remittance reminder information, a message MS21 is displayed as a message from the first user (A.A.) based on the remittance reminder information sent by the first user (A.A.).

By way of example and not limitation, message MS21 may include 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 username of the user (yourself) in the group who received the remittance reminder (in this example, the text "Request to remit money 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 changes to the remittance screen described above, and 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 in association with the message MS21, and therefore, by operating the remittance button 21a, an amount equivalent to the requested remittance amount (3,000 yen in this example) is remitted from B.B.'s account to A.A.'s account.
Therefore, the remittance button BT21a is displayed in a selectable manner different from the remittance button BT11a described above and the remittance button 31a described later, since the remittance process is executed in response to the operation of the remittance button BT21a.

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 an operation, it is displayed in a selectable manner different from the button BT11b described above and the button 31b described below.

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, 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 limitation, message MS31 includes an icon with the word "Remind" indicating that a remittance reminder has been sent from a different user (first user A.A.) to another different user (B.B.), the words [Payment App] indicating that the message is based on a payment application function, the username of the user in the group who received the remittance reminder (in this example, the words "Remittance request to B.B."), the amount requested to be remitted in 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 another different user (B.B).

Furthermore, by way of example and not limitation, message MS31 does not include the "Send reminder" icon included in message MS11, nor the "Receive reminder" 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 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, an example in which a user (B.B.) who has received the remittance reminder information pays the requested remittance 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 Figure 5-3.

By way of example and not limitation, message MS12 includes the words [Payment App], the username 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 by way of limitation, message MS13 includes the words [Payment App], the username of the user who is the subject of the remittance reminder, a message indicating that the remittance amount has been received from that user (in this example, "Remittance received" or "Remittance received from B.B."), the remittance amount (in this example, 3,000 yen), and an icon with the word "Received" indicating that you (A.A.) are the one who has received the remittance 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 paid 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 differs from message MS13 in that it includes an icon with the word "Pay" (indicating that B.B.) is the one who paid the requested remittance amount, but does not include an icon with the word "Receive" (indicating that B.B.) is the one who paid the requested remittance amount.

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 for the word "receipt" or the word "payment," but instead includes an icon image of the first user (A.A.) and an icon image of the user (B.B.) who is the target of the remittance reminder.

Note that an arrow is displayed pointing from the icon image of a 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 one user (A.A.) different from the user (C.C.) to another user (B.B.).

<Processing>
5-4 and 5-5 are flowcharts showing an example of the flow of processing executed by each device in this embodiment.
These flowcharts are rewritten versions of the flowcharts in 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 server 10 adds the remittance request message to and updates the group talk management data (group talk room) of group members that includes at least user A.A., user B.B., and user C.C. (S510).

In this example, a group chat room including three users is shown, but it may alternatively include two users, user A.A. and user B.B. In other words, it is sufficient for the chat room to include at least the two parties involved in the remittance (the remittance master user and the remittance request recipient 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, the terminals 20A, 20B, and 20C 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 terminal 20B determines whether there has been input in response to the remittance request message displayed in the group chat 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 receipt message to the 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 (S550).
In response to this, the control units 21 of the terminals 20A, 20B, and 20C respectively display the received remittance message or receipt message in the group talk room (A550, B550, C550).

After S550, when remittance reminder transmission request information is received from terminal 20A via communication I/F 14, 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 remind message to each of the terminals 20A, 20B, and 20C via the communication I/F 14 (S580).
In response to this, the terminals 20A, 20B, and 20C each cause the control units 21 to display the received remittance remind message in the group talk room (A580, B580, C580).

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

<Effects of the Fifth Embodiment>
In this embodiment, on the terminal 20 of the remittance request recipient 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 the effect of this 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 this embodiment, the terminal 20 of the remittance request destination user displays a group talk room (not limiting, but an example of a chat room) including at least the remittance request destination user (not limiting, but an example of a terminal user) and the remittance master user (not limiting, but 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 the 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 that includes at least the user of the terminal and the first user.

<Fifth Modification Example (1)>
In the fifth embodiment, a remittance request message or a remittance reminder message is displayed in the group talk room displayed on the terminals 20 of all group users included in the group, but the present invention is not limited to this.
It is also possible to prevent remittance request messages and remittance reminder messages from being displayed in the group chat 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 device 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 from the first user (A.A.) in the chat room.

As an example and not a limitation, among users belonging to the same group (X), other users (C.C) who are not 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.

As an example and not a limitation, 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), may be prevented from viewing the message regarding the remittance reminder.

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

The display flag indicates whether or not remittance request messages and remittance reminder messages should be displayed in the group chat 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 for the remittance master user, the remittance request destination user, and other group users are all set to "ON."
This means that a remittance request message and a remittance reminder message are displayed in the group chat 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 the display flags for other group users are set to "OFF".
This means that the remittance request message and remittance reminder message will be displayed in the group chat room displayed on the terminals 20 of the remittance master user and the remittance request recipient user, who are the parties to the remittance request, but the remittance request message and remittance reminder message will not be displayed in the group chat room displayed on the terminals 20 of other group users who are not the parties.

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

<Processing>
5-9 and 5-10 are flowcharts showing an example of the flow of processing executed by each device in this modified example.
This flowchart is a rewrite of the flowcharts in FIGS. 5-4 to 5-5 so that processing is performed in accordance with the above table.
Here, an example will be given in which the server 10 sets the display flag based on input to the terminal 20 of the remittance master user.

At A120, the control unit 21 of terminal 20A sends remittance request transmission request information, including 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 requesting the setting of the display flag included 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 is 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 remind 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 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, a display flag may or may not be set separately for the remittance request message and the remittance reminder message.
In this case, as an example only, the display flag setting of setting No. "1" may be applied to remittance request messages, and the display flag setting of setting No. "2" or setting No. "3" may be applied to remittance reminder messages.

In this modified example, the above group chat room includes at least the remittance request destination user (not limited to, but an example of a terminal user), the remittance master user (not limited to, but an example of a first user), and other group users (not limited to, but an example of a second user different from the first user), and the remittance reminder message is not displayed in the group chat 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 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 the user making the remittance request, and is aware that he or she has made a remittance request to the user of the terminal through at least the first information. Therefore, by preventing the second display based on the remittance request from being displayed in the 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 Example (2)>
In the fifth embodiment, the message based on the remittance reminder information displayed in the 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 by 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.), respectively.

As an example, and not by way of limitation, on the terminal 20 of the first user (A.A), 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, 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), 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 devices 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 chat 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 another user, C.C.
Messages MS11a, MS21a, and MS31a have the same content except for the display format of the buttons, and are all associated with icon images of the official accounts 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 target 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 "Pay" 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 non-selectable remittance buttons BT11a and BT11b, message MS21a includes selectable remittance buttons BT21a and BT21b, and message MS31a includes non-selectable remittance buttons BT31a and 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 Figure 5-12, message MS12 is displayed on the first user's (A.A.) terminal 20 as a message from the user (B.B.) who has completed the remittance, and 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 a message from 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 the same as those in the example shown in Figure 5-3.

In the examples shown in Figures 5-11 and 5-12, but without limitation, 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 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 that the requested remittance 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 device 20 of another user (C.C.) who is neither the first user (A.A.) nor the target of the remittance reminder cannot view the official account message MS31a in the chat room.

As an example and not a limitation, among users belonging to the same group (X), other users (C.C) who are not 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 message MS21a from the official account can be viewed in the chat 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 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 MS31a from the official account in the talk room.

As an example and not a limitation, 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), may be prevented from viewing the message regarding the remittance reminder.

<Fifth Modification Example (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 (a non-limiting example of a remittance reminder display) is displayed in a chat room, the mention function in the messaging application will automatically be activated and the underlined notation "@username" will be displayed.

Here, the mention function is a function of a messaging application for sending a message (content) to a specified user.
It should be noted that a notice emphasizing the receipt of the message may or may not be displayed on the terminal of the user who receives the message via the mention function.

As an example, and not as 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 as 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, a message MS11b is displayed on the terminal 20 of the first user (A.A.) as a message to B.B., who is a user designated by the mention function, 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, the notation "@B.B" is written, based on the mention function, to indicate that the message is addressed to B.B.

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 a limitation, but is an example of information indicating the terminal user).
As an example of the effect of this 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 that specifies the user.

<Fifth Modification Example (4)>
The display format of the remittance reminder message displayed in the group chat room displayed on the display unit 24 of the terminal 20 of the remittance request destination user may be different from the display format of the remittance reminder message displayed in the group chat 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 some of the text included in the message be changed, or the display mode (selectable/non-selectable) of the buttons included in the message be changed, but also, as a non-limiting example, a detailed message can be displayed on the device 20 of the person involved, while a simplified message can be displayed on the device 20 of the person other than the person involved. Messages can also be displayed in different colors, for example.

In this modified example, the display of the remittance reminder message is configured in such a way that it is displayed in a group chat room displayed on the terminal 20 (not limited to the remittance request destination user, but an example of a terminal) (not limited to the first display mode) and in a group chat room displayed on the terminal 20 (not limited to the remittance request destination user, but an example of a terminal of a second user) of other group users excluding the remittance request destination user and the remittance master user (not limited to the second display mode).
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 allows the user of the terminal to recognize that he or she is a party to the remittance request, while allowing the second user to recognize that he or she is not a party to the remittance request.

<Fifth Modification Example (5)>
If the remittance request recipient 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, as a message from the official account of the payment application, message MS14 is displayed on the terminal 20 of the first user (A.A), message MS24 is displayed on the terminal 20 of the user (B.B) who is the target of the remittance reminder, and message MS34 is displayed on the terminal 20 of the other user (C.C).
At the beginning of each of messages MS14, MS24, and MS34, there is an indication "@B.B.", which indicates that the message is addressed to B.B. (in this example, the user who is the target of the remittance reminder) based on the mention function.

Messages MS14, MS24, and MS34 each display, by way of example and not limitation, the words [Payment App], information indicating the restricted functions in the messaging application and the conditions for 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 "Please make the remittance 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 remit button BT14 for message MS14 and the remit button BT34 for message MS34 are both displayed in an unselected state, while the remit button BT24 for message MS24 is displayed in a selected state.

<Fifth Modification Example (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 Figure 5-17, similar to the example shown in Figure 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 situation in which C.C., a user of one terminal 20, has replied that he has sent money, but B.B., a user of the other terminal 20, has not replied.
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, which are intended for multiple users (B.B. and C.C.) and for which payment processing has not yet 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 to multiple users (B.B. and C.C.) regarding a common event (in this example, an event with a membership fee of 3,000 yen). Based on the fact that the remittance process for the remittance request for one user (B.B.) is incomplete and the remittance process for the remittance request for the other user (C.C.) is complete, information about both users is displayed in area R10.

As a non-limiting example, area R10 displays the date and time 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, information indicating the number of users to whom the remittance request was made (in this example, "Member 2") is displayed, and furthermore, information about one user (B.B.) who has not yet remitted money, and information about the other user (C.C.) who has already remitted money are displayed.

As an example, and not by way of limitation, a first user (A.A.) sends remittance request information to another user (B.B.), but the remittance processing for this remittance request has not been completed, and therefore the remittance request amount (3,000 yen in this example) is displayed in association with the icon image and username 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 username of the other user (C.C.).

Furthermore, 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, and the display format of the former information and the latter information is different, making them easier to distinguish.
When the first user (A.A.) checks the checkbox in area R10, each piece of information displayed in area R10 is selected.
When area RR is tapped in this state, remittance reminder information based on the information displayed in area R10 is sent to the terminal 20 of the 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 another 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 remitted money and information about the other user (C.C.) who has already remitted money 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 be displayed with information about another user (C.C.) who has already remitted money for the same event, thereby encouraging the other 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 each of the multiple users (B.B., C.C.) to whom remittance request information was sent was the target 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 username of one user (B.B.) who has not yet 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 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 username 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 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 will encourage each user to compare the number of reminders they have received with other users, and with the number of reminders they have received from 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 roughly two ways to stop this remittance reminder:
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 explained 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 can be applied to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

As a method for the server 10 to manage remittance requests, the above-mentioned two patterns (pattern A and pattern B) can be considered as examples, but are not limited to these.
When "Pattern A" is applied, the server 10 leaves the remittance request that has been remitted intact, and stops sending remittance reminder information corresponding to the remittance request to the terminal 20 of the remittance request recipient 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 flowcharts showing an example of the flow of processing 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 limitation.

If it is determined that a remittance reminder should be sent (S260: YES), the control unit 11 of the server 10 determines whether reminders have been suspended 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 completion flag corresponding to the corresponding remittance request management ID is set to "ON," it is determined that reminders have been suspended.

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, the server 10 is controlled to send remittance reminder information 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 that remittance reminder information is not sent to the terminal 20B.

In the above process, remittance reminder information may be sent from server 10 to terminal 20B more than once. In this case, if the server 10 executes the remittance settlement process based on an input in response to one of the remittance reminder displays displayed on the display unit 24 of terminal 20B, control will be exercised so that no further remittance reminder information will be sent from server 10 to 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, 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, performs transmission control via the control unit 11 to control transmission of 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.
As an example of the effect of an embodiment obtained by such a configuration, by performing transmission control regarding control of sending second information based on a remittance request to a terminal based on execution of a remittance process related to remittance to a first user based on a remittance request, it is possible to allow the user of the terminal to properly remit remittance 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 this 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 shows a configuration in which the server 10 controls to send 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 not to send the 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 sent to the terminal, while when a remittance process is executed, the second information can be prevented from being sent to the terminal.

In addition, this embodiment shows 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 an 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 input by the 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 input on the first display.

Furthermore, in this embodiment, the server 10 transmits remittance reminder information based on the remittance request (not limiting, an example of third information based on the 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 the 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 this 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 limited to, an example of second information) to the terminal 20 of the remittance request destination user when first remittance reminder information (not limited to, an example of second information) is sent by the communication I/F 14 of the server 10 to the terminal 20 of the remittance request destination user, and the second remittance processing is configured to display a first remittance reminder display (not limited to, an example of second display based on second information) on the terminal 20 of the remittance request destination user and be executed based on input by the remittance request destination user in response to the first remittance reminder display.
As an example of an effect of an embodiment obtained by such a configuration, even when 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 when 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 shows a configuration in which the second remittance process (not limited to, but an example of a remittance process) is a process related to remittance from a remittance request destination user (not limited to, but an example of a terminal user) to a remittance master user (not limited to, but an example of a first user).
As an example of an effect of the embodiment obtained by such a configuration, the server can realize remittance from the user of the terminal to the first user by the 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 a remittance is made through 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, thereby deleting not only the remittance request but also the remittance reminder corresponding to this remittance request.

<Sixth Modification (2)>
When pattern A (retaining 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 about remittance requests that have already been sent can also be viewed on the terminal 20.
Therefore, the information relating to remittance requests that have already been remitted may or may not be displayed in a different manner from the information relating to remittance requests that have not yet been remitted.

As an example and not by way 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, by way of example and not limitation, a remittance request list page is set up and sent in which remittance request information and remittance reminder information for which the remittance completion flag is "OFF" is displayed in the default state, while for remittance request information and remittance reminder information for which the remittance completion flag is "ON", the display is changed to a display style indicating that the remittance has been completed (by way of example and not 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 containing 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 indicating that remittance has been completed is not limited to this.
As a non-limiting example, on the remittance request list screen with the layout of Figure 6-3, areas R21 and R22 may be grayed out as shown in Figure 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 date and time of receipt 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.
These areas may also be displayed in gray.

<Sixth Modification (3)>
As described above, the remittance reminder can also be stopped by the terminal 20 stopping the display of 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 processing executed by each device in this modified example.
This flowchart is based on the terminal remind process of FIGS. 1-13 to 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 controls the display unit 24 to display a remittance reminder message.

On the other hand, if it is determined that the remittance has been executed (B455: YES), the control unit 21 of the terminal 20B proceeds to B190.
In this case, the control unit 21 of the terminal 20B executes control so that the remittance reminder message is not displayed 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 20B, the remittance reminder information will be controlled so that it is not displayed on the display unit 24 of terminal 20B thereafter.

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 uses the control unit 21 to perform display control related to control of 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 remittance request, based on the execution of a first remittance process (not limiting, an example of a remittance process related to remittance to the first user).
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 properly remit money to the first user.

In addition, this modified example shows a configuration in which the above-mentioned display control controls to display a remittance reminder display on the display unit 24 when the first remittance process is not executed, and controls to not display the remittance reminder display on the display unit 24 when the first remittance process is not executed.
As an example of the effect of this 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 an input by the remittance request destination user to the display (not limiting, an example of the first display) based on the remittance request information (not limiting, an example of the first information) displayed on the terminal 20 of the remittance request destination user, and based on an input by the remittance request destination user to the display (not limiting, an example of an input by the terminal user to the first display).
As an example of the effect of this modified example obtained by such a configuration, a first display based on the first information is displayed on the terminal, and the remittance process can be easily executed based on input by the terminal user on 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 the remittance process has been executed based on input on 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 processing 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 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 proceeds to B190.
In this case, remittance reminder information is sent from the server 10, but the control unit 21 of the terminal 20B controls the display unit 24 not to display a remittance reminder display based on the remittance reminder information.

<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 by way of limitation, when a remittance request list is displayed on the display unit 24 of the terminal 20B of user B.B, who is the remittance request destination user, and as an example and not by way of limitation, tapping on a remittance reminder from user A.A, a remittance screen such as that 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 the text "[Remind] Remittance request from A.A." along with a link containing the words "Confirmed." 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 the chat room in the sixth embodiment.
The contents described in the seventh embodiment can be applied to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<Processing>
7A and 7B are flowcharts showing an example of the flow of processing executed by each device in this embodiment.
For the sake of simplicity, the process will be illustrated and explained focusing 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 terminal 20A via communication I/F 14, control unit 11 of server 10 adds the remittance request message to the chat management data (chat room) between user A.A and user B.B, thereby updating the data (S610).
Then, the control unit 11 of the server 10 sends 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 determines 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 displays the talk room on the display unit 24 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 remittance reminder transmission request information has been received from the terminal 20A via the communication I/F 14 (S650), and if it determines that it has been received (S650: YES), it determines whether or not the reminder has been stopped based on the set remittance completion flag (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 remind message to the terminal 20B via the communication I/F 14 (S680).

Then, the control unit 11 of the server 10 determines whether to end the processing (S690), and if it determines to continue the processing (S690: NO), it returns to S650. On the other hand, if it determines to end the processing (S690: YES), it ends the processing.

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 determines that a remittance reminder message has been received (B650: YES), executes a reminder notification process (B660).
For this reminder notification process, the above-mentioned method can be applied, 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 to display the talk room (B670: YES), the control unit 21 displays the talk room on the display unit 24 based on the latest talk data stored in the memory unit 28 (B680).

The control unit 21 of terminal 20B then determines whether to terminate the processing (B690), and if it determines to continue the processing (B690: NO), it returns to B650. On the other hand, if it determines to terminate the processing (B690: YES), it terminates the processing.

<Effects of the Seventh Embodiment>
This embodiment shows a configuration in which the remittance request display (not limited to, an example of the first display based on the first information) on the terminal 20 is displayed in a talk room (not limited to, an example of a chat room) that includes at least the remittance request destination user (not limited to, an example of a terminal user) and the remittance master user (not limited to, an example of the 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 the chat room.

<Seventh Modification>
As in the sixth variant example (1), when applying the aforementioned pattern A, the information regarding remittance requests that have already been sent may or may not be displayed in a different manner 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.
For example, but not by way of limitation, messages stored on the server 10 are automatically deleted after a certain period of time (for example, but not by way of limitation, several weeks) has passed since the message was sent to the terminal 20, but messages stored on the terminal 20 remain unless deleted by the user.

In this case, the message history is basically left on the terminal 20 and not deleted, so the user of the terminal 20 can also 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 completion flag can be either "OFF" or "ON".

The information type is the type of the message; by way of example and not limitation, "Request" and "Reminder" are defined for the remittance flags "OFF" and "ON," respectively.

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

Let me explain in detail.
(1) Remittance completed flag "OFF"
For the information type "Request," the message type is defined as "Type 1 Remittance Request Message (Unsent)." This indicates that if the remittance flag is "OFF," meaning that the remittance has not yet been sent, the remittance request message displayed in the chat room will be a Type 1 remittance request message.

For the information type "Reminder," the message type defined is "Type 1 remittance reminder message (unsent)." This means that if the remittance flag is "OFF," meaning the remittance has not yet been sent, the remittance reminder message displayed in the chat room will be a Type 1 remittance reminder message.

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

For the information type "Reminder," the message defined is "Type 2 Remittance Reminder Message (Remittance Completed)." This indicates that if the remittance complete 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 (the 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).

Figures 7-4 and 7-5 are flowcharts showing an example of the processing 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 server 10 adds a Type 1 remittance request message as a remittance request message to the chat management data (chat room) between user A.A and user B.B, and updates it (S710).

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

After B620, the control unit 21 of terminal 20B stores the received remittance request message (Type 1, Type 2) 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 to display the talk room has been made to the input unit (B730). If it is determined to display the talk room (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-class 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 adds a Type 1 remittance reminder message as a remittance reminder message to the chat management data (chat room) between user A.A. and user B.B., and updates the data (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 (S780).

After B660, the control unit 21 of terminal 20B stores the received remittance reminder messages (Type 1 and Type 2) 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). If it is determined that the talk room should be displayed (B770: YES), the control unit 21 displays the talk room on the display unit 24 based on the latest talk data (B780).

Specifically, as an example and not by way of limitation, if a message in a chat room indicates that remittance information has not yet been received from server 10, a Type 1 remittance request message and a Type 1 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-class remittance request message and a second-class 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 recipient user may use an independent remittance function in the payment application to remit money to the remittance master user, either after checking the remittance request display or 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 can be applied to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

FIG. 8-1 is a diagram showing an example of the structure 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 the date and time, remittance request management ID, remittance master ID, remittance request destination ID, remittance request amount, remittance completion 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 that identifies 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 that stop sending remittance reminder information.

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

FIG. 8B 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, as an example and not a limitation, a setting number, a target terminal, determination information, and a determination result are defined in association with each other.

The target terminal determines which terminal 20 the server 10 will use to determine which remittance reminders to stop based on the information selected and entered on that terminal 20.

The determination information defines 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.
Setting No. "S1" defines the "terminal of the user to whom the remittance request is made" as the target terminal, the "selected remittance master user" as the judgment information, and the "remittance reminder from the selected remittance master user" as the judgment result.
This is done by, for example and not by way of limitation, displaying a list of users (remittance master users) who have received remittance requests on a screen (for example and not by way of limitation, a remittance screen) displayed on the display unit 24 of the remittance request destination user's terminal 20, and allowing the user to select one of the remittance master users. Then, based on the selection of a 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 the 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 then 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 "OFF."

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

When this setting is applied, the server 10 determines whether a remittance request exists from the selected remittance destination user to the remittance request destination user. If it determines that a remittance request exists, the server 10 executes the remittance, regarding 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. 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 the remittance request, so the remittance completion flag can remain "OFF."

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

Setting No. "S3" defines the target terminal as "terminal of the remittance request destination user," the judgment information as "selected remittance destination user & input remittance amount," and the judgment result as "remittance reminder from selected remittance destination user & remittance reminder where the input remittance amount is the same as the remittance request amount."
This indicates, by way of example and not 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 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, remittance reminders from the selected remittance destination user in which the input remittance amount is the same as the remittance request amount are stopped.

When this setting is applied, 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 whose remittance request amount is the same as the remittance amount entered on the remittance request destination user's terminal 20.
The server 10 then executes the remittance, regarding the remittance from the remittance request destination user as a remittance based on the remittance request of the identified remittance request management ID. The server 10 then stops remittance reminders for the remittance request of that remittance request management ID. Specifically, by way of example and not limitation, the server 10 sets the remittance completion 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, but not limited to, remittance reminders where the difference in amount is "300 yen or less") may or may not be stopped.

Setting No. "S4" defines the "terminal of the user to whom the remittance request is made" as the target terminal, the "selected remittance request within the group" as the judgment information, and the "remittance reminder corresponding to the selected remittance request within the group" as the judgment result.
This indicates, by way of example and not limitation, that when a remittance request destination user selects a remittance request for themselves as well as a remittance request for another group user on a screen (by way of example and not 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 within the group, and then stops remittance reminders corresponding to the remittance request to the remittance request destination user and to the remittance requests to the other selected 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, by way of example and not limitation, a remittance request recipient user in a group can stop remittance reminders for themselves and other group users in the same group by remitting the amount they themselves should remit as well as the amount that other group users in the same group should remit.

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 if selection of stopping remittance reminders is made, remittance reminders may or may not be stopped.

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

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

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

In this state, 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), after which the screen shown in FIG. 8-5 is displayed, by way of example and not limitation.
On 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 pops up in the center of the screen, as shown in FIG. 8-6. The remittance reminder stop information includes, by way of example and not limitation, the icon image and username of user A. A, the text "Do you want to stop reminders from this user?", an OK button BT10, and a cancel button.

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. Server 10 then executes the remittance and issues a remittance reminder. Then, as an example and not a limitation, a remittance completion notification indicating that the remittance has been completed and that the remittance reminder has been stopped is displayed as a pop-up in the center of the screen, 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 Figure 2-2, and here shows the state where the "Remittance" icon IC3 has been tapped. In this case, by way of example and not limitation, the remittance destination user selection screen shown in Figure 8-4 is displayed.

8-8 to 8-9 show an example of the transition of the screen when the setting No. "S4" is applied. FIG. 8-8 shows an example of the 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 on 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, by way of example and not limitation. In this example, two group requests are displayed: a money transfer request from user A.A to user B.B (a transfer from user B.B to user A.A) with a transfer request amount of 3,000 yen, and a money transfer request from user A.A to user C.C (a transfer from user C.C to user A.A) with a transfer request amount of 3,000 yen.

By checking the checkboxes associated with each of the remittance requests for the two users above and tapping the remittance area RM2 at the bottom of the screen, 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 users above, and stops the corresponding remittance reminders.

8-9 shows group talk rooms displayed on the display units 24 of terminal 20A of user A.A, who is the remittance master user, terminal 20B of user B.B, who is the remittance request destination user, and terminal 20C of user C.C, who is also the 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 the money.

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

In addition, the group talk room displayed on terminal 20C displays message MS91 in response to message MS71, indicating that user C.C. has sent money to user A.A. for two people, and message MS92 in response to message MS72, indicating that user A.A. has received that 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 user C.C is likely to make payments including for user B.B, knowing that the remittance reminders for himself/herself will be stopped, in this example, the group chat 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 chat room displayed on terminal 20C.

<Processing>
8 to 10 are flowcharts showing an example of the flow of processing executed by each device in this embodiment.
Here, the processing of terminal 20B is shown on the left side, and the processing of server 10 is shown on the right side, and the processing of terminal 20A is not shown.
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 of FIGS. 6A and 6B, respectively, by way of example and not limitation.

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

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

The control unit 11 of the server 10 determines whether remittance settlement request information has been received from terminal 20B via the communication I/F 14 (S810), and if it determines that it has been received (S810: YES), it determines whether 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 the remittance reminder is 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 for 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 processing (B890), and if it determines to continue the processing (B890: NO), returns the processing 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.

Furthermore, in this process, at S267 in FIG. 6-2, the control unit 11 of the server 10 determines whether reminders have been suspended 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 control unit 11 refers to the third remittance request management data 157C, and determines that reminders have been suspended if the request suspension flag corresponding to that remittance request management ID is set to "ON."

<Effects of the Eighth Example>
This embodiment shows a configuration in which the second remittance process (not limited to, but an example of a remittance process) executed by the server 10 is executed based on the selection of the remittance master user (not limited to, but an example of the 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 that first user.

In addition, this embodiment shows a configuration in which the second remittance process is executed based on the selection of a remittance master user (not limiting, but an example of a first user) by the remittance request destination user (not limiting, but an example of a terminal user) and the selection of remittance reminder stop (not limiting, but 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 shows a configuration in which the second remittance process is executed based on the remittance master user (not limiting, an example of the first user), the remittance request amount (not limiting, an example of the amount based on the remittance request), and the planned remittance amount (not limiting, an example of the amount input by the terminal user).
As an example of an effect of an embodiment obtained by such a configuration, the remittance process can be executed appropriately based on the first user's selection, the amount based on the remittance request, and the amount entered by the terminal user.

In addition, this embodiment shows a configuration in which the second remittance process is executed based on a remittance to a remittance master user (not limited to, but an example of a first user) by a group user (not limited to, but an example of a second user) different from the remittance request destination user (not limited to, but an example of a terminal user).
As an example of an effect of an embodiment obtained by such a configuration, the remittance process can be executed appropriately based on a remittance to a first user by a second user who is 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 (an example of a terminal user, but not limited to), the remittance master user (an example of a first user, but not limited to), and another group user (an example of a second user, but not limited to), 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 input by the second user to the first display based on the first information displayed on the second user's terminal.

In addition, this embodiment shows a configuration in which information such as an icon image and user name of the remittance master user (an example of first user information, not limited to this) 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 (an example of a user of the terminal, not limited to this) to the first user information displayed on the display unit 24.
As an example of the effect of an embodiment obtained by such a configuration, the remittance process can be executed based on input by the user of the terminal to the first user information displayed on the display unit, which is an easy-to-understand display for the user.

In addition, in this embodiment, the terminal 20 acquires selection information of the remittance destination user (not limited to, information indicating that the first user has been selected) and information on the planned remittance amount (not limited to, an example of information on the amount to be remitted to the first user) based on 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, but by way of example and not 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 carried out as if it were based on a remittance request from the user.

In addition, this embodiment shows 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 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 remind stop flag in the remittance request management data 157, but the present invention is not limited to this.
For example, and not by way of 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 examples of reminding stop management data stored in the storage unit 15 of the server 10 in this modified example.
As an example, but not limited to, 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 whether or not the remittance reminder information has been sent from the sending side to the receiving side (sent/not sent) in a matrix format.

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, for those that have been determined to stop sending remittance reminder information, the fields where the sending side and receiving side intersect are 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, the field where the sender "U001 (User A.A)" and the receiver "U002 (User B.B)" intersect is updated to "No Sent."

<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 can be applied to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

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

(A) is an example, not a limitation, where the remittance has not yet been sent, but the user of the party concerned (although it may also be a user other than the party concerned) wishes to stop the remittance reminder 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 where money is paid by handing over cash, transferring money from a financial institution (bank, etc.). In this case, too, it is likely that the user involved will primarily want to stop the remittance reminder.

FIG. 9A 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 device, judgment information, and judgment results are the same as those in the table in Figure 8-2.

The information (approval required/approval not required) used to identify whether approval from the remittance master user is required to stop remittance reminders is specified for whether approval from the remittance master user is required.

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 whether or not approval from the remittance master user is required is "no."
This indicates, by way of example and not limitation, that a remittance request destination user is selected by the remittance master user on a screen (by way of example and not 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 stops all remittance reminders from the 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 the 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 "terminal of remittance master user," the judgment information is "whether or not the selected remittance request and remittance reminder has been selected to be stopped," the judgment result is "the remittance reminder corresponding to the selected remittance request," and whether or not approval from the remittance master user is required is "No."
This indicates, by way of example and not limitation, that a remittance request is selected by the remittance master user on a screen (by way of example and not limitation, a remittance request list screen) displayed on the display unit 24 of the remittance master user's terminal 20, and that the remittance reminder corresponding to the selected remittance request is stopped based on the user's selection to stop the remittance reminder.
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 remittance reminders 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 it cannot identify whether the remittance based on the remittance request has already been executed. Therefore, the remittance completion flag remains "OFF."
Therefore, if remittance has been completed, the remittance master user's terminal 20 may transmit remittance completion information to the server 10, so that the server 10 may set 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 judgment information is "remittance master user & whether remittance reminder stop is selected," the judgment result is "remittance reminder from selected remittance master user," and whether approval from the remittance master user is required is "required."
This indicates, by way of example and not limitation, that a remittance master user is selected by the remittance request destination user on a screen (by way of example and not 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 user's selection to stop remittance reminders.
In addition, since the remittance reminder can be stopped at the request of the remittance requesting 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 selected remittance master user's terminal 20 approves the suspension of remittance reminders. Specifically, the server 10 transmits information (hereinafter referred to as "approval confirmation information") to the selected remittance master user's terminal 20 to confirm whether or not the selected remittance master user approves the suspension of remittance reminders.
When the server 10 receives information indicating approval (hereinafter referred to as "approval information") 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 terminal 20 of the remittance master user, 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 "terminal of the user to whom the remittance request is made," the judgment information is "selected remittance request & whether or not the remittance reminder has been selected to be stopped," the judgment result is "remittance reminder corresponding to the selected remittance request," and whether approval from the remittance master user is required is "required."
This indicates, by way of example and not limitation, that a remittance request is selected by the remittance request recipient user on a screen (by way of example and not limitation, a remittance request list screen) displayed on the display unit 24 of the terminal 20 of the remittance request recipient user, and that the remittance reminder corresponding to the selected remittance request is stopped based on the user's selection to stop the remittance reminder.
In addition, since the remittance reminder can be stopped at the request of the remittance requesting user, the approval requirement of the remittance master user is set to "Required."

When this setting is applied, the server 10 stops remittance reminders corresponding to the selected remittance request. Specifically, the server 10 sets the reminder stop flag for 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 it cannot identify whether the remittance based on the remittance request has already been executed. Therefore, the remittance completion flag remains "OFF."
Therefore, if the remittance has already been made, the remittance request destination user's terminal 20 may transmit remittance completion information to the server 10, so that the server 10 may set 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 "a remittance reminder corresponding to the remittance request of the selected party," and whether approval from the remittance master user is required is "required."
This indicates, by way of example and not limitation, that a user other than the parties to the remittance (by way of example and not 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 limitation, a group request list screen) displayed on the display unit 24 of the terminal 20 of that user, and based on that user choosing to stop the remittance reminder, the remittance reminder corresponding to the remittance request of the selected party is stopped.

For example, and not by way of limitation, a case in which one user in a group requests that another group user (recipient user) in the same group (recipient user) stop sending a remittance reminder in response to a remittance request from the remittance master user may be considered a method in which a user other than the parties in question acts as a witness to stop the remittance reminder of the parties in question.
Since remittance reminders can be stopped at the request of users other than the parties involved, the requirement for approval from 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 for 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 requires approval from the remittance master user, the server 10 can perform approval confirmation processing periodically, for example, but not limited to, 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 (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 the remittance reminder.
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 not stop the remittance reminder.

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

9B is a diagram showing an example of a remittance request list screen displayed on the display unit 24 of the terminal 20A of 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, as well as information about the remittance reminder corresponding to this remittance request.

In the display area for information about the remittance request, next to the icon image and user name of user B.B., a reminder stop icon IC10 including, by way of example and not limitation, an image of a speaker is displayed 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 a speaker being white.

When the reminder stop icon IC10 is tapped, as an example and not by way of limitation, 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 sent from the terminal 20A to the server 10, and the remittance reminder corresponding to the selected remittance request is stopped.

As a result, 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 except for the image of the speaker is now displayed in white.
Furthermore, based on the fact that the remittance reminder has been stopped, the display area of the remittance reminder corresponding to the remittance request is displayed in a faded color, as shown in FIG. 9-4, by way of example and not limitation.

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 remind stop flag to "ON", but also sets the remittance completion flag to "OFF".
As a result, as an example and not by way of limitation, as shown in Figure 9-5, on the remittance request list screen displayed on the display unit 24 of terminal 20A, a completion mark MK1 containing 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 about the remittance request that User B.B. has received from User A.A., and information about 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, second remittance reminder stop information for requesting User A.A. to stop the remittance reminders 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 the following 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.A. in this case.
On the display unit 24 of the terminal 20A, in the center of the remittance request list screen, stop 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 sent 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.

On the remittance request list screen in Figure 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 the display area for the remittance reminder corresponding to this remittance request is faded.

<Effects of the ninth embodiment>
This embodiment shows a configuration in which the control of sending remittance reminder information (not limiting, but an example of second information) by the server 10 is performed based on input (not limiting, but an example of first input) by the terminal 20 of the remittance master user (not limiting, but an example of first user).
As an example of the effect of this embodiment obtained by such a configuration, transmission of the second information to the terminal of the user to whom the remittance request is made can be controlled in accordance with 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 this 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 request is made, in accordance with the wishes of the first user who made the remittance request.

In addition, this embodiment shows a configuration in which the above-mentioned transmission control is executed based on input (not limited to, but an example of a second input) made by the remittance request destination user (not limited to, but an example of a terminal user) to his/her own terminal 20.
As an example of the effect of this embodiment obtained by such a configuration, transmission of the second information to the terminal of the user who is the remittance request destination can be controlled in accordance with the intention of the user who is the remittance request 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 this 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 who is the recipient of the remittance request, in accordance with the wishes of the user who is the recipient of the remittance request.

In addition, this embodiment shows 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 not to send the second information (not limited to, but an example of information regarding the first user's approval of the second input).
As an example of an effect of an embodiment obtained by such a configuration, by way of example and not limitation, even if a second input is made, if the first user who is the remittance requester does not approve the second input, the second information can be transmitted to the terminal of the user who is the remittance destination. Conversely, by way of example and not limitation, even if a second input is made, if the first user who is the remittance requester approves the second input, the second information can be prevented from being transmitted to the terminal of the user who is the remittance destination.

<Others>
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 to these.

The combination of the first information and the second information in the present invention can 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 user that remittance does not need to be made).
This combination is applicable when a remittance master user has initially made a remittance request to a remittance request destination user, but wishes to inform the remittance request destination user that, for some reason, the remittance does not need to be carried out.

(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 that allows 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 reiterate the remittance request destination user after notifying him/her that he/she is exempt from remittance.

(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 they are initially exempt from remittance, but for some reason, they are required to remit the remittance and request the remittance.

1 Communication system 10 Server 20 Terminal 30 Network

Claims (10)

A program executed by a server that controls information to be displayed in a chat room including a first user, a second user, and a third user,
a control unit of the server controls to display first information regarding a remittance request from the first user to the second user and the third user on a terminal of the second user and a terminal of the third user;
If the second user does not make a remittance based on the remittance request and the third user makes a remittance based on the remittance request, the server controls the control unit to display second information based on the remittance request in the chat room on the terminal of the second user who did not make the remittance, and not display it in the chat room on the terminal of the third user who made the remittance. A program executed by a server that controls information to be displayed in a chat room including a first user, a second user, and a third user,
a control unit of the server controls to display first information regarding a remittance request from the first user to the second user and the third user on a terminal of the second user and a terminal of the third user;
If the second user does not make a remittance based on the remittance request and the third user makes a remittance based on the remittance request, the server controls the control unit to display second information regarding the fact that the remittance based on the remittance request was not made in a first manner in the chat room on the terminal of the second user who did not make the remittance, and to display the second information in a second manner different from the first manner in the chat room on the terminal of the third user who made the remittance. 3. The program according to claim 2,
performing a process of remitting the amount based on the remittance request to the first user by the control unit based on the input of the first information;
The server executes, by the control unit, a process of remitting the amount based on the remittance request to the first user based on the input for the second information of the first aspect. The program according to any one of claims 1 to 3,
The second information includes information for displaying a sender different from the sender of the remittance request. 1. An information processing method for a server that controls information to be displayed in a chat room including a first user, a second user, and a third user, comprising:
a control unit of the server controls to display first information regarding a remittance request from the first user to the second user and the third user on a terminal of the second user and a terminal of the third user;
When the second user does not make a remittance based on the remittance request and the third user makes a remittance based on the remittance request, the control unit controls so that second information based on the remittance request is displayed in the chat room on the terminal of the second user who did not make the remittance and is not displayed in the chat room on the terminal of the third user who made the remittance. 1. An information processing method for a server that controls information to be displayed in a chat room including a first user, a second user, and a third user, comprising:
a control unit of the server controls to display first information regarding a remittance request from the first user to the second user and the third user on a terminal of the second user and a terminal of the third user;
When the second user does not make a remittance based on the remittance request and the third user makes a remittance based on the remittance request, the control unit controls to display second information regarding the fact that the remittance based on the remittance request was not made in a first manner in the chat room on the terminal of the second user who did not make the remittance, and to display second information in a second manner different from the first manner in the chat room on the terminal of the third user who made the remittance. A server that controls information to be displayed in a chat room including a first user, a second user, and a third user,
Controlling displaying first information regarding a remittance request from the first user to the second user and the third user on a terminal of the second user and a terminal of the third user;
The device is provided with a control unit that performs control such that, when the second user does not make a remittance based on the remittance request and the third user makes a remittance based on the remittance request, second information based on the remittance request is displayed in the chat room on the terminal of the second user who did not make the remittance, and is not displayed in the chat room on the terminal of the third user who made the remittance. A server that controls information to be displayed in a chat room including a first user, a second user, and a third user,
Controlling displaying first information regarding a remittance request from the first user to the second user and the third user on a terminal of the second user and a terminal of the third user;
and a control unit that performs control such that, when the second user does not make a remittance based on the remittance request and the third user makes a remittance based on the remittance request, second information regarding the fact that the remittance based on the remittance request was not made is displayed in a first manner in the chat room on the terminal of the second user who did not make the remittance, and is displayed in a second manner different from the first manner in the chat room on the terminal of the third user who made the remittance. An information processing method for a system including a server that controls information to be displayed in a chat room including a first user, a second user, and a third user, and a terminal of each user that communicates with the server,
Displaying first information regarding a remittance request from the first user to the second user and the third user on a terminal of the second user and a terminal of the third user;
If the second user does not make a remittance based on the remittance request and the third user makes a remittance based on the remittance request, second information based on the remittance request is displayed in the chat room on the terminal of the second user who did not make the remittance, and is not displayed in the chat room on the terminal of the third user who made the remittance. An information processing method for a system including a server that controls information to be displayed in a chat room including a first user, a second user, and a third user, and a terminal of each user that communicates with the server,
Displaying first information regarding a remittance request from a first user to a second user and a third user on a terminal of the second user and a terminal of the third user;
If the second user does not make the remittance based on the remittance request and the third user makes the remittance based on the remittance request, second information regarding the fact that the remittance based on the remittance request was not made is displayed in a first manner in the chat room on the terminal of the second user who did not make the remittance, and is displayed in a second manner different from the first manner in the chat room on the terminal of the third user who made the remittance.