JP2022010423A - Program, information processing method, and server - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve the convenience of remittance based on remittance requests.

SOLUTION: A program executed by a server that communicates with a terminal causes the server to transmit first information about a remittance request by a first user to the terminal by a communication unit of the server, and perform, by a control unit of the server, transmission control related to control to transmit second information based on the remittance request to the terminal based on execution of remittance processing related to remittance to the first user based on the remittance request.

SELECTED DRAWING: Figure 1-1

COPYRIGHT: (C)2022,JPO&INPIT

Description

The present disclosure relates to programs, information processing methods, servers, etc.

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

Japanese Unexamined Patent Publication No. 2002-176671

According to the first aspect of the present invention, the program executed by the server communicating with the terminal transmits the first information regarding the remittance request by the first user to the terminal by the communication unit of the server, and is based on the remittance request. Based on the execution of the remittance process related to the remittance to the first user, the server executes the transmission control related to the control of transmitting the second information based on the remittance request to the terminal by the control unit of the server.
According to the second aspect of the present invention, the information processing method of the server communicating with the terminal is based on the transmission of the first information regarding the remittance request by the first user to the terminal by the communication unit of the server and the remittance request. (1) Based on the execution of the remittance process relating to the remittance to the user, the control unit of the server performs the transmission control relating to the control of transmitting the second information based on the remittance request to the terminal.
According to the third aspect of the present invention, the server communicating with the terminal has a communication unit that transmits the first information regarding the remittance request by the first user to the terminal, and a remittance process related to the remittance to the first user based on the remittance request. It is provided with a control unit for performing transmission control regarding control for transmitting the second information based on the remittance request to the terminal based on the execution of.
According to a fourth aspect of the present invention, the server communicating with the terminal includes a processor that reads a program stored in the memory and executes processing based on the program, and the processor is a first information regarding a remittance request by a first user. Is transmitted to the terminal by the communication unit of the server, and the transmission control related to the control of transmitting the second information based on the remittance request to the terminal based on the execution of the remittance process related to the remittance to the first user based on the remittance request. Do and do what you do.
According to the fifth aspect of the present invention, the program executed by the terminal receives the first information regarding the remittance request by the first user by the communication unit of the terminal, and displays the first display based on the first information of the terminal. The control unit of the terminal controls the display related to the display by the display unit and the control to display the second display based on the remittance request on the display unit based on the execution of the remittance process related to the remittance to the first user based on the remittance request. What you do with is done by the terminal.

The figure which shows an example of the structure of the communication system in one aspect of Embodiment. The figure which shows an example of the function realized by the control part of the server which concerns on 1st Embodiment. The figure which shows an example of the information stored in the storage part of the server which concerns on 1st Embodiment. The figure which shows an example of the user registration data which concerns on 1st Embodiment. The figure which shows an example of the user management database which concerns on 1st Embodiment. The figure which shows an example of the remittance request management data which concerns on 1st Example. The figure which shows an example of the function realized by the control part of the terminal which concerns on 1st Embodiment. The figure which shows an example of the information stored in the storage part of the terminal which concerns on 1st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 1st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 1st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 1st Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 1st Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 1st Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 1st Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on the 1st modification. The figure which shows an example of the remittance request management data which concerns on 2nd Example. The figure which shows an example of the display screen of the terminal which concerns on 2nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 2nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 2nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 2nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 2nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 2nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 2nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 2nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 2nd Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 2nd Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 2nd Embodiment. The figure which shows an example of the display screen of the terminal which concerns on the 2nd modification. The figure which shows an example of the display screen of the terminal which concerns on the 2nd modification. The figure which shows an example of the display screen of the terminal which concerns on the 2nd modification. The figure which shows an example of the display screen of the terminal which concerns on the 2nd modification. The figure which shows an example of the display screen of the terminal which concerns on the 2nd modification. The figure which shows an example of the display screen of the terminal which concerns on the 2nd modification. The figure which shows an example of the timing chart which concerns on 3rd Example. The figure which shows an example of the timing chart which concerns on the 3rd modification. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 4th Embodiment. The figure which shows an example of the remittance reminder condition data which concerns on 4th Example. The figure which shows an example of the display screen of the terminal which concerns on 4th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 4th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 4th modification. The figure which shows an example of the display screen of the terminal which concerns on 5th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 5th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 5th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 5th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 5th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 5th modification. The figure which shows an example of the display screen of the terminal which concerns on 5th modification. The figure which shows an example of the table about the display method of the remittance request message and the remittance reminder message which concerns on 5th modification. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 5th modification. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 5th modification. The figure which shows an example of the display screen of the terminal which concerns on 5th modification. The figure which shows an example of the display screen of the terminal which concerns on 5th modification. The figure which shows an example of the display screen of the terminal which concerns on 5th modification. The figure which shows an example of the display screen of the terminal which concerns on 5th modification. The figure which shows an example of the display screen of the terminal which concerns on 5th modification. The figure which shows an example of the display screen of the terminal which concerns on 5th modification. The figure which shows an example of the display screen of the terminal which concerns on 5th modification. The figure which shows an example of the display screen of the terminal which concerns on 5th modification. The figure which shows an example of the display screen of the terminal which concerns on 5th modification. The figure which shows an example of the display screen of the terminal which concerns on 5th modification. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 6th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 6th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 6th modification. The figure which shows an example of the display screen of the terminal which concerns on 6th modification. The figure which shows an example of the display screen of the terminal which concerns on 6th modification. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 6th modification. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 6th modification. The figure which shows an example of the display screen of the terminal which concerns on 6th modification. The figure which shows an example of the display screen of the terminal which concerns on 6th modification. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 7th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 7th Embodiment. The figure which shows an example of the table about the display mode of the information related to the remittance request which concerns on 7th modification. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 7th modification. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 7th modification. The figure which shows an example of the remittance request management data which concerns on 8th Embodiment. The figure which shows an example of the remittance reminder determination table which concerns on 8th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 8th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 8th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 8th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 8th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 8th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 8th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 8th Embodiment. The flowchart which shows an example of the processing flow of the terminal and the server which concerns on 8th Embodiment. The figure which shows an example of the remind stop management data which concerns on the 8th modification. The figure which shows an example of the remittance reminder determination table which concerns on 9th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 9th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 9th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 9th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 9th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 9th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 9th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 9th Embodiment. The figure which shows an example of the display screen of the terminal which concerns on 9th Embodiment.

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

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

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

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

The server 10 has a function of providing a payment service and a messaging service to a terminal 20 owned by a user via a network 30. The server 10 can also be expressed as a payment management (messaging management) server, a payment service (messaging service) server, or the like.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The clock unit 29A is a built-in clock of the terminal 20, and outputs time information (timekeeping information). The clock unit 29A is configured to include, for example, a clock using a crystal oscillator and the like, without limitation. The clock unit 29A can be expressed as a time measuring unit or a time information detecting unit as an example without limitation.

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

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

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

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

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

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

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

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

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

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

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

(2) HW configuration of the server FIG. 1-1 shows an example of the HW configuration of the server 10.
The server 10 includes a control unit 11 (CPU), a storage unit 15, a communication I / F 14 (interface), an input / output unit 12, and a clock unit 19. Each component of the HW of the server 10 is connected to each other via bus B, as an example, but not by limitation. It is not essential that the HW of the server 10 includes all the components as the configuration of the HW of the server 10. As an example, but not by limitation, the HW of the server 10 may or may not be configured to remove individual components or a plurality of components.

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

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

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

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

The input / output unit 12 is realized by a device that inputs various operations to the server 10.
The input unit is realized by any or a combination of all kinds of devices capable of receiving input from the user and transmitting information related to the input to the control unit 11. The input unit is typically realized by a hardware key typified by a keyboard or the like, or a pointing device such as a mouse. The input unit may or may not include, as an example, a touch panel, a camera (operation input via a moving image), and a microphone (operation input by voice), without limitation.

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

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

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

The clock unit 19 is a built-in clock of the server 10 and outputs time information (timekeeping information). The clock unit 19 is configured to include, for example, an RTC (Real Time Clock) as a hardware clock, a system clock, or the like, without limitation. The clock unit 19 is not limited, but may be expressed as a time measuring unit or a time information detecting unit as an example.

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

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

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

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

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

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

Further, the program P of the present disclosure may or may not be provided to the server 10 and / or the terminal 20 via any transmission medium (communication network, broadcast wave, etc.) capable of transmitting the program. .. The server 10 and / or the terminal 20 is not limited to, but as an example, by executing the program P downloaded via the Internet or the like, the functions of the plurality of functional units shown in each embodiment are realized.
The same applies to other devices.

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

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

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

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

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

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

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

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

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

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

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

In the following, for convenience, the user requesting remittance will be referred to as a "remittance master user", and the user requesting remittance will be referred to as a "remittance request destination user".
The remittance master user can also be expressed as a "remittance request source user", a "remittance request main user", or the like.

Further, in the following, it will be described that various processes according to the present invention are executed by the payment application and the messaging application installed in the terminal 20. In this case, as an example, not limited to, it is possible to have the function of the messaging service as one function of the payment application, or to have the function of the payment service as one function of the messaging application.

The messaging service is configured to allow users to chat using a chat room.
The chat room is a virtual room for one or more users of the terminal 20 to communicate using a data communication line on a computer network.
In messaging services, chat rooms may be referred to as "talk rooms."

The talk room includes, as an example, not limited to, a talk room for users to talk one-on-one, and a group talk room for talking in a group including a plurality of users formed in a messaging service. ..

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

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

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

<First Example>
The first embodiment is an embodiment in which the terminal 20 of the remittance request destination user automatically displays the remittance reminder based on the received remittance request. Hereinafter, this method is referred to as "terminal reminding".
The contents described in the first embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

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

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

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

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

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

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

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

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

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

As an example, not limited to this, it may or may not be possible to assign a plurality of terminal IDs to one user ID.

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

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

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

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

The remittance request management data 157 is a database that stores data for managing information related to the remittance request in an accumulated manner, and FIG. 1-6 shows a configuration example of the first remittance request management data 157A, which is an example thereof.
The first remittance request management data 157A stores, as an example, not limited to, the date and time, the remittance request management ID, the remittance master ID, the remittance request destination ID, the remittance request amount, and the remittance completed flag. To.

At the time of day, as an example, not limited to, the date and time when the remittance request information of the corresponding remittance request is transmitted from the server 10 to the terminal 20 of the remittance request destination user is stored.

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

The application ID of the remittance master user is stored in the remittance master ID.
The application ID of the remittance request destination user is stored in the remittance request destination ID.

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

The remittance completed flag is a flag for identifying whether or not the remittance corresponding to the remittance request has been performed. Initially, it is set to "OFF", and when the remittance is completed, it is set to "ON". To.

Here, the method for managing the remittance request by the server 10 can be roughly divided into the following two patterns.
"Pattern A": The remittance request that has been remitted (the remittance flag is ON) is left without being deleted.
"Pattern B": Delete the remittance request that has been remitted (the remittance flag is ON).

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

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

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

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

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

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

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

FIG. 1-9 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment.
The remittance request display MS1 for notifying the user of the terminal 20 (the user of the payment application) that the remittance request information has been received is displayed on the display unit 24 based on the function of the payment application executed by the terminal 20. Has been done.

As an example, not a limitation, the remittance request display MS1 is a notification displayed in a push format (hereinafter referred to as "push notification"), and is referred to as "Payment App" indicating that the display is based on the function of the payment application. A message notifying you of the characters and icons, the receipt of the remittance request information, and the user name of the first user who made the remittance request (not limited, but as an example, "AA", "There is a remittance request." ) And.

Further, on the left side of the remittance request display MS1, a button BT1 for confirming detailed information regarding the remittance request is displayed.
Not limited, the remittance request display MS1 and the button BT1 indicate that the terminal 20 has received the first information (not limited, but as an example, remittance request information) regarding the remittance request by the first user (AA in this example). It is an example of the first display which is displayed based on.
When the user taps the button BT1 with the word "Open", the details of the remittance request are displayed based on the function of the payment application.

In FIG. 1-10, the user of the terminal 20 who received the remittance request information is B. An example of B is shown. That is, in FIG. 1-9, the user of the terminal 20 is B.I. As a result of tapping the button BT1, B shifts to the screen shown in FIG. 1-10.
In the center of the top of the screen, the characters "Payment App" indicating that this screen is based on the function of the payment application are displayed. On the right side, an icon image and a user name (“BB” in this example) of the user in the payment application of the terminal 20 are displayed.

Below that, the user name of the first user and a message indicating that remittance request information has been received from that user (not limited to, for example, "AA", "remittance request." ) Is displayed.
Further below, the remittance request display MS2 showing the details of the remittance request is displayed.

The remittance request display MS2 has an icon indicating that the display is based on the receipt of remittance request information (in this example, the icon with the characters "request received") and the first user (A) who made the remittance request. The amount of money specified by the icon image of A) and the remittance request information that the user (BB) of the terminal 20 should remit to the first user ("3,000 yen" in this example). ), An icon notifying that the user of the terminal 20 is in a position to make a payment (in this example, an icon with the characters "payment"), and the date and time when the terminal 20 received the remittance request information (in this example, "2020.". 04.20 21:30 "), the user name of the first user, and a message indicating that the remittance request information has been received from that user (in this example," There is a remittance request from Mr. A. "). And link information for displaying more detailed information about the remittance request (in this example, the part where the characters "> Confirm details" are displayed).

Further, the remittance request display MS2 includes a remittance button BT2 for executing a remittance process to the first user (AA) based on the function of the payment application.
Not limited to this, the remittance request display MS2 is an example of the first display displayed based on the first information regarding the remittance request by the first user (AA in this example).

On this screen, when the user (BB) of the terminal 20 taps the remittance button BT2, the remittance screen for remittance of the amount specified by the remittance request information (not limited, but as an example, the screen of FIG. 2-8). ). When the remittance area RM2 at the bottom of the screen is tapped on this remittance screen, the screen shifts to the remittance confirmation screen (not limited, but as an example, the screen of FIG. 2-9).
User B. of terminal 20. When B taps the confirmation button BT6 on the remittance confirmation screen, the amount specified by the remittance request (remittance request amount: amount indicated by the remittance request display MS2) is the user B of the terminal 20. Remittance is made from B's electronic money account to the first user (AA)'s electronic money account.

When the amount corresponding to the remittance request amount of the first user (AA) is remitted, the user (BB) of the terminal 20 is reminded to remit to the first user (AA). The remittance reminder display (an example of a second display different from the first display based on a remittance request, not a limitation) will not be displayed on the display unit 24 of the terminal 20 of the user (BB).

On the other hand, when the amount corresponding to the remittance request amount of another user (AA) is not remitted, the remittance operation described above by the user (BB) of the terminal 20 within a predetermined period is not limited, but as an example. If this is not performed, the remittance reminder display can be displayed on the display unit 24 of the terminal 20 of the user (BB).

In the example of FIG. 1-11, the display unit 24 indicates that the remittance reminding has been performed to the user of the terminal 20 (the user of the payment application) based on the function of the payment application executed by the terminal 20. The remittance reminder display MS3 to be notified is displayed.

As an example, but not a limitation, the remittance reminder display MS3 has a remittance reminder based on the function of the terminal 20 (a function of the payment application) (that is, a terminal reminder has been performed) and a remittance reminder. Remittance request display shown in FIG. 1-9 in that it includes a message notifying the user name of one user (not limited to, as an example, "AA", "(terminal remind) remittance request."). Different from MS1.

Further, on the left side of the remittance reminder display MS3, a button BT3 for confirming detailed information regarding the remittance reminder is displayed. Not limited, the remittance reminder display MS3 and the button BT3 are examples of a second display different from the first display based on the remittance request.
When the user taps the button BT3 with the word "Open", the details of the remittance reminder are displayed based on the function of the payment application.

In FIG. 1-12, the user of the terminal 20 that is the target of the remittance reminder is the user B. An example of B is shown. That is, in FIG. 1-11, the user B. As a result of tapping the button BT3, B shifts to the screen shown in FIG. 1-12.

On the screen shown in FIG. 1-12, the remittance reminder display MS4 showing the details of the remittance reminder is displayed.

As an example, not a limitation, the remittance reminder display MS4 notifies that the remittance process corresponding to the remittance request information has not been executed yet, and indicates that the notification is based on the function of the terminal 20 (the function of the payment application). The date and time when the terminal 20 received the remittance request information is displayed after the point including the icon of the character "Terminal Remind" and the message indicating that the remittance request was made by the first user (in this example, "A"). There is a remittance request from Mr. A. (2020.0420.21: 30) ”), which is different from the remittance request display MS2 shown in FIG. 1-12.
That is, in the remittance reminder display MS4, it is notified by the content or display mode of the message that the remittance reminder has been performed for the fact that the remittance process for the remittance request has not been executed yet.

Further, the remittance reminder display MS4 includes a remittance button BT4 for executing a remittance process to the first user (AA) based on the function of the payment application.
Not limited, the remittance reminder display MS4 is an example of a second display different from the first display based on the remittance request.

On this screen, when the user (BB) of the terminal 20 taps the remittance button BT4, the remittance screen for remittance of the amount specified by the remittance reminder display MS4 (not limited, but as an example, FIG. 2-8). Screen). When the remittance area RM2 at the bottom of the screen is tapped on this remittance screen, the screen shifts to the remittance confirmation screen (not limited, but as an example, the screen of FIG. 2-9).
When the user (BB) of the terminal 20 taps the confirmation button BT6 on the remittance confirmation screen, the amount specified by the remittance reminder display MS4 is transferred from the electronic money account of the user (BB) of the terminal 20. Remittance is sent to the electronic money account of one user (AA).

As described above, as an example, not limited to, the remittance remind display MS4 including the second display (remittance remittance display MS3 and button BT3, remittance button BT4) displayed on the display unit 24 by the user (BB) of the terminal 20. ), Based on the remittance request, the remittance process related to the remittance from the terminal user (BB) to the first user (AA) will be executed by the control unit 21 of the terminal 20. ..

<Processing>
1-13 to 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 are not limited to these processes.
Further, another step may be added to the process described below, or some steps may be omitted (deleted).
This is the same for each flowchart (process) described below.

In this process, in order from the left side, a process executed by the control unit 21 of the terminal 20A, a process executed by the control unit 21 of the terminal 20B, and a process executed by the control unit 11 of the server 10 are shown.
As an example, not a limitation, the user A. of the terminal 20A. Let A be the remittance master user, and the user B. of the terminal 20B. An example is given in the case where B 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 the remittance reminder display on the display unit 24.
In addition, the remittance reminder can be performed not only once but also twice or more, but for the sake of simplicity, the end determination of the process is omitted, and the process is shown as a process when the remittance reminder is performed only once. explain. The same applies when remittance reminders are performed more than once.

First, the control unit 21 of the terminal 20A is not limited to, but as an example, whether or not an input for requesting execution of a remittance request (hereinafter referred to as “remittance request execution input”) has been made to the input unit. Based on this, it is determined whether or not to request the execution of the remittance request (A110).
The remittance request execution input is not limited, but may be, as an example, an operation for requesting execution of the remittance request (hereinafter, referred to as “remittance request execution operation”).

If it is determined that the request is made (A110: YES), the control unit 21 of the terminal 20A requests (requests) the remittance request information to be transmitted to the terminal 20 (terminal 20B in this example) of the remittance request destination user. (Hereinafter referred to as "remittance request transmission request information") is transmitted to the server 10 by the communication I / F22 (A120).

Remittance request The remittance request information is not limited, but as an example, at least the user A. of his / her terminal 20A. The identification information of A (application ID as an example, not limited) and the user B. who is the remittance request destination user. B's identification information (not limited, but as an example, application ID) and remittance request amount (amount for which remittance is requested) can be included.

When the remittance request transmission request information is received from the terminal 20A by the communication I / F 14, the control unit 11 of the server 10 generates the remittance request information in which the remittance request management ID is set based on the received remittance request transmission request information. 1 Update the remittance request management data 157A. Then, the control unit 11 of the server 10 transfers the generated remittance request information to the user B. who is the user of the remittance request destination. It is transmitted to the terminal 20B of B by communication I / F14 (S110).

The remittance request information is not limited, but as an example, in addition to the remittance request management ID, information that can be identified (recognized) by the user as a remittance request (text indicating that the remittance request is not limited but as an example). , Image, etc.), information on the remittance request amount, information on the remittance master user (not limited, but as an example, the user name of the remittance master user) and the like.

The information of the remittance master user may or may not include not only the user name but also the application ID, the terminal telephone number of the remittance master user, the terminal email address, and the like.

When the remittance request information is received from the server 10 by the communication I / F 22, the control unit 21 of the terminal 20B causes the display unit 24 to display the remittance request display based on the received remittance request information (B110).
The remittance request display is for displaying some or all of the information contained in the received remittance request information, displaying information related to the received remittance request information, and realizing remittance based on the received remittance request information. Information (not limited, but as an example, operation images such as remittance buttons, remittance icons, etc.) can be included.

After that, the control unit 21 of the terminal 20B determines whether or not to execute the remittance based on the remittance request (B120). As an example, not a limitation, it is determined whether or not the remittance execution input for which the remittance request management ID is specified 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 the remittance settlement request information for requesting the remittance settlement to the server 10 by the communication I / F 22 (B130).

The remittance settlement request information may include, as an example, not only a limitation, a remittance request management ID and a remittance scheduled amount.
The planned remittance amount is the amount entered as the amount to be remitted and is the amount in which the remittance has not been performed yet.

The control unit 11 of the server 10 determines whether or not the remittance settlement request information has been received from the terminal 20B by the communication I / F 14 (S120), and if it is determined that the remittance settlement request information has been received (S120: YES), the remittance settlement process is performed. Execute (S130).
Specifically, as an example, not a limitation, the user B. The amount of the planned remittance amount is subtracted from the balance of the electronic money account of B as the remittance amount and updated, and the user A. Update by adding the remittance amount to the electronic money account balance of A.
The remittance amount is the amount of remittance sent from the remittance request destination user to the remittance master user.
In addition, the remittance completed flag corresponding to the received remittance request management ID in the first remittance request management data 157A is set to "ON".
No remittance will be performed for the remittance request management ID whose remittance completed flag is "ON".

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

After that, the control unit 11 of the server 10 transmits the remittance information, which is the information related to the remittance, to the terminal 20B by the communication I / F14 (S140).
The remittance information is not limited, but includes, for example, information on a remittance completion notification for notifying that the remittance has been completed.

Further, the control unit 11 of the server 10 transmits the receipt information, which is the information regarding the receipt, to the terminal 20A by the communication I / F 14 (S150).
The receipt information is not limited, but includes, for example, information on a receipt completion notification for notifying that the receipt has been completed.

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

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

After that, the control unit 21 of the terminal 20B determines whether or not to perform remittance reminding (terminal reminding in this embodiment) in response to the above remittance request (B145). Specifically, it is determined that remittance reminding is performed when the setting is not limited to limitation but remittance reminding (terminal remittance).

Basically, when the remittance based on the remittance request is not executed in B120, the remittance reminding can be performed.
However, unlike this, remittance reminders can be made regardless of whether or not the remittance was made based on the remittance request.

Further, in this case, the remittance request information transmitted from the server 10 is received in S110, or the remittance request display is displayed on the display unit 24 in B110, and then the remittance remind is not immediately performed. As a result, remittance reminders can be performed at the timing when a certain period of time has passed.

When it is determined to perform remittance reminding (B145: YES), the control unit 11 of the server 10 creates remittance reminding 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 the remittance reminder display based on the created remittance reminder information (B150).

The content of the remittance reminder display is not limited, but as an example, other than information that the user can identify (recognize) that it is a remittance reminder (text, image, etc. indicating that it is a remittance reminder as an example, not limited). Can be similar to the remittance request display.

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

The remittance reminder display is for displaying some or all of the information contained in the received remittance reminder information, displaying information related to the received remittance reminder information, and realizing remittance based on the received remittance reminder information. It can be a concept including display of information (not limited, but as an example, an operation image such as a remittance button and a remittance icon).

Next, the control unit 21 of the terminal 20B determines whether or not an input has been made to the remittance reminder display displayed on the display unit 24 (B160).
The "input" can be an operation for an input unit (operation unit) as an example rather than a limitation, and a tap (tap operation) as an example rather than a limitation.
In addition, this input can include inputs to the various remittance reminder display MSs described above. Not limited to tapping the remittance button, but as an example, the remittance is realized by inputting that the display area of any of the above-mentioned remittance reminder display MSs is tapped. You can also do it.

If it is determined that the input has been made (B160: YES), the control unit 21 of the terminal 20B transmits the remittance settlement request information to the server 10 by the communication I / F22 based on the remittance reminder information (B130).
Also in this case, the remittance request management ID of the remittance request information received earlier and the remittance scheduled amount can be included in the remittance settlement request information as an example without limitation.

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

After that, the control unit 11 of the server 10 transmits the above-mentioned remittance information to the terminal 20B by the communication I / F 14 (S140).
Further, the control unit 11 of the server 10 transmits the above-mentioned receipt information to the terminal 20A by 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 by 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.
Further, when the receipt information is received from the server 10 by the communication I / F 22 (A140: YES), the control unit 21 of the terminal 20A causes the display unit 24 to display the received receipt information (A150). Then, the control unit 21 of the terminal 20A ends the process.

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

This first remittance process is not limited to, but as an example, a process for realizing a remittance from a terminal user to a first user, and a process related to a remittance from a terminal user to a first user in some way. Can be included. Not only the processing directly related to the remittance but also the processing indirectly related to the remittance can be included in the remittance processing executed by the terminal.

In the above processing example, the following processing is included in the first remittance processing as an example, not a limitation.
(1) Process of transmitting remittance settlement request information to server 10 by communication I / F 22 (2) Process of receiving remittance information from server 10 by communication I / F 22 (3) Displaying received remittance information on display unit 24 process

<Input related to the terminal>
In the above process, the input to the terminal or the input by the user of the terminal, such as the input for executing the remittance request and the input for the remittance reminder display, is set as the operation input to the input unit (operation unit), but the present invention is not limited to this.

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

<Effect of the first embodiment>
In this embodiment, the terminal 20 receives the remittance request information (not limited, but an example of the first information regarding the remittance request) by the remittance master user (not limited, but an example of the first user) by the communication I / F22. Then, the terminal 20 displays the remittance request display (not limited, but an example of the first display) on the display unit 24.
Further, the terminal 20 displays a remittance reminder display (not limited, but an example of a second display) different from the remittance request information based on the remittance request on the display unit 24. Then, the terminal 20 is based on the input for the remittance reminder display displayed on the display unit 24 (an example of the input for the second display, not the limitation), and the first remittance process (not the limitation, but the terminal) based on the remittance request. An example of a remittance process relating to a remittance from a user to a first user) is executed by the control unit 21.
As an example of the effect of the embodiment obtained by such a configuration, the remittance process is executed by the control unit of the terminal based on the input to the second display displayed on the display unit of the terminal, and the user of the terminal first executes the remittance process. Remittance to the user can be easily realized.

Further, in this embodiment, the remittance request display includes information on the remittance request amount based on the remittance request (not limited, but an example of information on the amount based on the remittance request), and the remittance reminder display includes information on the same amount (not limited). It is not limited, but shows a configuration that includes information on the amount of money based on the remittance request).
As an example of the effect of the embodiment obtained by such a configuration, the amount of money based on the remittance request can be surely notified to the user of the terminal by the first display and the second display.

Further, in this embodiment, the remittance request display includes information such as the user name of the remittance master user (not limited, but an example of the information of the first user), and the remittance reminder display includes information such as the same user name (not limited). The configuration including the information of the first user) is shown without limitation.
As an example of the effect of the embodiment obtained by such a configuration, the information of the user who requested the remittance can be surely notified to the user of the terminal by the first display and the second display.

Further, in this embodiment, the remittance request display (an example of the first display, not the limitation) and the remittance reminder display (an example of the second display, not the limitation) are the payment applications installed on the terminal 20 (in the limitation). However, the configuration displayed on the display unit 24 is shown by an example of an application installed on the terminal).
As an example of the effect of the embodiment obtained by such a configuration, the user of the terminal can easily recognize the first display and the second display by the application installed in the terminal.

Further, the present embodiment shows a configuration in which the first remittance process includes a process of receiving remittance information (not limited to information indicating that the remittance process based on the remittance request has been executed) by the communication I / F22. ing.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to notify the user of the terminal that the remittance process based on the remittance request has been executed.

Further, the present embodiment shows a configuration in which the first remittance processing includes a process of transmitting remittance settlement request information (not limited, but an example of information regarding a request for remittance processing based on a remittance request) by communication I / F22. ing.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to request the outside to process the remittance based on the remittance request from the first user.

<First modification (1)>
When the first remittance process is not executed (not executed) on the terminal 20 of the remittance request destination user, the display regarding the fact that the remittance is not performed based on the remittance request from the remittance master user (not limited, but the first). 4 An example of display) is displayed on the display unit 24. On the other hand, when the first remittance process is executed (when it has been executed) on the terminal 20 of the remittance request destination user, a display indicating that the remittance is performed based on the remittance request from the remittance master user (limited). Instead, an example of the fifth display) may or may not be displayed on the display unit 24.

Remittance The indication that the remittance has not been made based on the remittance request from the master user is not limited, but as an example, with texts such as "Not remitted yet", "Not remitted", or in the unsent state. Images (marks, icons, etc.) indicating that there is can be included.
Similarly, the indication that a remittance is being made based on a remittance request from the remittance master user is not limited, but as an example, texts such as "already remitted", "sent", or remitted. An image (mark, icon, etc.) indicating the state can be included.

In this modification, if the terminal 20 of the remittance request destination user does not execute the first remittance process (not limited to an example of the remittance process), the remittance based on the remittance request from the remittance master user is not performed. A display relating to this (not a limitation, but an example of a fourth display) is displayed on the display unit 24. On the other hand, when the terminal 20 of the remittance request destination user has executed the first remittance process (when it has been executed), the display regarding the fact that the remittance is performed based on the remittance request from the remittance master user (limited). However, an example of the fifth display) is shown on the display unit 24.
As an example of the effect of the modified example obtained by such a configuration, it is possible to appropriately inform the user of the terminal of the status of remittance (performed / not performed) based on the remittance request.

<First modification (2)>
In the first embodiment, the terminal 20 of the remittance request destination user can perform push notification as one of the reminder displays. This push notification can be said to be a kind of remind display and a kind of remind notification.

In addition to this push notification, as an example, not limited to this, remind notification processing based on the following control can be performed.
The control unit 21 controls the sound output unit 26 to output a predetermined sound.
The control unit 21 controls a vibrating unit (not shown) to vibrate the housing of the terminal 20.
The control unit 21 controls a light emitting unit (not shown) to emit a predetermined light.

In addition to the terminal remind execution timing, conditions for performing remind notification (hereinafter referred to as "remind notification conditions") are set, and based on the fact that the remind notification conditions are satisfied. , Remind notification processing can also be executed.

Remind notification conditions are not limited, but as an example, "The current time is the time zone when the user is likely to be sleeping (late night (until midnight the next day), early dawn (until 3:00 the next day)). Conditions such as the time zone of the day and the time zone of dawn (not included in the time zone of the next day) can be set.
By doing so, the remind notification condition is not satisfied and the remind notification process is not executed in these set time zones, so that the remind notification is not performed in the time zone when the user is likely to be sleeping. Can be.

This modification shows a configuration in which the terminal 20 of the remittance request destination user executes the remind notification process by the control unit 21 based on the set remind notification condition (not limited, but an example of the second condition). ..
As an example of the effect of the modification obtained by such a configuration, it is possible to notify the terminal user of the execution of the terminal reminder at an appropriate timing based on the set conditions.

<First modification (3)>
In the first embodiment, when the remittance based on the remittance request is executed on the terminal 20 of the remittance request destination user, the remittance is displayed on the display unit 24 as in the case of executing the remittance based on the remittance reminder as an example, not limited. You can make the remittance execute based on the input to the remittance request display.

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

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

In this modification, the terminal 20 of the remittance request destination user remittances from the remittance request destination user based on the remittance request based on the input to the remittance request display (not limited, but an example of the first display) by the remittance request destination user. The configuration is shown in which the control unit 21 executes a process for realizing the remittance to the master user (not limited to the example of the remittance process relating to the remittance from the terminal user to the first user).
As an example of the effect of the embodiment obtained by such a configuration, remittance based on the remittance request can be easily realized based on the input to the first display by the user of the terminal.

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

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

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

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

<First modification (5)>
It is assumed that some users of the terminal 20 may feel awkward and hesitate to make a remittance request or remittance remind to the remittance request destination user. As an example, not limited to the case, the remittance request destination user is a person superior to himself or the remittance request destination user is a close friend.

Therefore, it is possible that the user who requested the remittance request or the remittance reminder is not the user of the terminal 20 but the user who uses the business account.
The business account is not limited, but as an example, a user who has an official account (hereinafter referred to as "official account" and appropriately referred to as "OA: Official Account") in the service (payment service in the above example). Is.

As an example, a user with an official account can be, as an example, not a limitation, a payment service provider. In this case, the server 10 sends the remittance request information and the remittance reminder information to the terminal 20 of the remittance request destination user as the payment service provider instead of the user of the terminal 20 as the user who requested the remittance request or the remittance reminder. Can be done.

This modification shows a configuration in which the user of the remittance requester (an example of a first user, not a limitation) is a user who uses an official account (an example of a business account, not a limitation).
As an example of the effect of the modification obtained by such a configuration, it is possible to make a user who uses a business account make a remittance request on behalf of a user who wants to make a remittance request, which is convenient for the user. Can be improved.

<Second Example>
The second embodiment is an embodiment in which the remittance reminder display is performed based on the fact that the terminal 20 of the remittance request destination user receives the remittance reminder information from the server 10. Hereinafter, this method is referred to as "server reminding".
The contents described in the second embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

<Data structure>
FIG. 2-1 is a diagram showing a configuration example of the second remittance request management data 157B, which is another example of the above-mentioned remittance request management data 157 stored in the storage unit 15 of the server 10.
The second remittance request management data 157B includes the date and time, the remittance request management ID, the remittance master ID, the remittance request destination ID, the remittance request amount, and the remittance completed flag in the first remittance request management data 157A. As an example, not a limitation, information types are stored in association with each other.

The information type is information for identifying whether the type of information corresponding to the remittance request management ID is a remittance request or a remittance reminder. However, "remind" is memorized in each remittance reminder.

At the time of day, as an example, not limited, if the information type of the corresponding remittance request is "request", the date and time when the remittance request information was transmitted from the server 10 to the terminal 20 of the remittance request destination user is stored and corresponds. If the information type of the remittance request is "Remind", the date and time when the remittance remind information is transmitted from the server 10 to the terminal 20 of the remittance request destination user is stored.

In addition, for each remittance request management ID, the remittance remind information corresponding to the remittance request information identified by the remittance request management ID includes the remittance request management ID and the remittance request regardless of the number of remittance reminders. The same ID, the same amount, and the same flag are stored as the amount and the remittance completed flag.
As an example, not a limitation, the data of the record surrounded by the black frame in the figure is the data of the remittance request and the remittance reminder in the corresponding relationship.

<Display screen>
FIG. 2-2 shows an example of the information displayed on the display unit 24 when the payment application is executed on the terminal 20 of the first user (AA).
The electronic money account balance of the first user (AA) (“25,000 yen” in this example) is displayed on the display unit 24, and icons corresponding to each function that can be executed in the payment application are displayed. Is displayed.
The first user (AA) displays the remittance history related to his / her account on the display unit 24 to indicate whether or not the remittance has been made, and the user and the remittance who made the remittance when the remittance was made. You can check the amount. That is, it is possible to confirm whether or not the remittance has been performed in response to the remittance request.

As a function that can be executed by the payment application, there is a remittance request function that requests payment to a specified user, and the characters "remittance request" are displayed together with the icon IC1 including the "¥ mark" corresponding to the remittance request function. There is.
The first user (AA) selects this icon, specifies the user to be remittance requested (BB in this example), and the remittance request amount (remittance request amount) ("3,000" in this example. By inputting "yen"), the remittance request information is transmitted to the terminal 20 of the designated user (BB), and the remittance request display MS1 is displayed on the display unit 24 of the terminal 20 of the designated user. MS2 is displayed.

Then, in the terminal 20 of the first user (AA), in the payment application, the information about the user who is the target of the remittance request and the remittance request amount are managed as the remittance request history.
In the example of FIG. 2-2, the characters of "sending request list" are displayed together with the icon IC2 corresponding to the remittance request history viewing function.
By selecting this icon, the first user (AA) can individually confirm the user who has been the target of the remittance request in the past and the remittance request amount for that user.

In this example, as shown in Fig. 2-3, below the title of "Remittance Request List", the remittance processing is not completed among the remittance requests made by the first user (AA) in the past. That is, information about what can be targeted for remittance reminders is displayed individually.
In this example, the icon image and user name (BB in this example) of the user who is the target of the remittance request, and the date and time when the terminal 20 of that user received the remittance request information (2020.04 in this example). .20 21:30), the amount of the remittance request to the user (“3,000 yen” in this example), and the first user (AA) are in a position to receive the remittance request amount. An icon (in this example, the icon of the character "receive") and is displayed in association with each other in the rectangular area R1.

Further, a check box is provided in the area R1, and when the user checks the check box, each information displayed in the area R1 is selected.

In the example of FIG. 2-3, the area RR displayed as "Remind" is provided at the bottom of the screen. When the first user (AA) taps the area RR with the check box checked, the remittance reminder information based on the information displayed in the area R1 becomes the transmission target of the remittance request information. It is transmitted to the terminal 20 of the user (BB) who has been there.
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 (BB) receives the remittance reminder information, or the remittance reminder display based on the reception of the remittance reminder information at the terminal 20 of the user (BB) is displayed, FIG. As shown in -4, the remittance reminder completion display MS5 for notifying that the remittance reminder is completed is displayed on the terminal 20 of the first user (AA).
The remittance reminder completion display MS5 includes the user name (BB in this example) of the user who was the target of the remittance request.

As shown in FIG. 2-5, the remittance reminder display MS3A based on the receipt of the remittance reminder information is displayed on the terminal 20 of the user (BB) who has received the remittance reminder information.

As an example, not the limitation, the remittance reminder display MS3A is a message notifying the user name of the first user regarding the remittance reminder based on the receipt of the remittance reminder information (as an example, not the limitation, "AA", "[ Remind me] I have a remittance request. ") Includes.
In the remittance reminder display MS3 shown in FIG. 1-11, "terminal reminder" is displayed according to the remittance reminder display based on the function of the own terminal, whereas in the remittance reminder display MS3A, it is received. The difference is that "Remittance reception" is displayed depending on the remittance remind display based on the remittance remind information.

Further, on the left side of the remittance reminder display MS3A, a button BT3A for confirming detailed information regarding the remittance reminder is displayed.
Not limited, the remittance reminder display MS3A and the button BT3A are examples of a second display different from the first display based on the remittance request.
Not limited to this, the remittance reminder display MS3A and the button BT3A are examples of the second display displayed on the display unit 24 based on the fact that the terminal 20 has received the second information based on the remittance request.

When the user taps the button BT3A with the word "Open", the details of the remittance reminder are displayed based on the function of the payment application.
In FIG. 2-5, as a result of the user (BB) tapping the button BT3A, the screen shifts to the screen shown in FIG. 2-6, and the remittance reminder display MS4A showing the details of the remittance reminder is displayed.

As an example, but not limited to, the remittance reminder display MS4A notifies the icon of the characters "Remind receive" based on the receipt of the remittance reminder information and the user name of the first user based on the receipt of the remittance reminder information. Includes a message (as an example, not a limitation, "[Remind reception] A.A. has a remittance request.").

In the remittance reminder display MS4 shown in FIG. 1-12, the icon of the characters "terminal reminder" is displayed according to the remittance reminder display based on the function of the own terminal, whereas the remittance reminder display MS4A is displayed. The difference is that the icon with the characters "Remind reception" based on the receipt of remittance remind information is displayed.
Further, in the remittance reminder display MS4A of FIG. 2-6, the remittance reminder display based on the remittance reminder information is displayed before the user name (AA) of the first user. On the other hand, the remittance reminder display MS4 shown in FIG. 1-12 is different in that there is no such display.

When the user (BB) of the terminal 20 taps the link information displayed as "> Confirm details" of the remittance reminder display MS4A, the screen shifts to the screen shown in FIG. 2-7.
On the screen of Fig. 2-7, what kind of event caused the remittance request reminded by the remittance reminder display MS4A (in this example, it is the membership fee of the event held on 4/20). Will be notified. In addition, the user (BB) of the terminal 20 is in a position to make a payment (in this example, the icon of the character "payment") and the amount to be paid (in this example, "3,000 yen"). Will be notified.

On the screen of FIG. 2-7, the information about the remittance reminder is displayed together with the animal character in a larger area than the above-mentioned remittance reminder display MS4A. Below that, a region RM1 is provided.

In the area RM1, the user name (AA) of the first user and the information notifying that the remittance request and the remittance reminding have been performed by the first user (in this example, “remind reception”, “A. The message "There is a remittance request from Mr. A.") and the link information for sending the amount corresponding to the remittance request and remittance reminder to the first user (in this example, the characters "> Remittance" are displayed. The part) is displayed.

When the user (BB) of the terminal 20 taps the link information for remittance, the screen shifts to the remittance screen shown in FIG. 2-8.
On the remittance screen, the icon image and user name (AA) of the first user who is the remittance partner, the remittance amount to be remitted to the first user (“3,000 yen” in this example), and the terminal 20 An icon notifying that the user (BB) is in a position to make a payment (in this example, the icon with the characters "payment") and the remittance amount of the current terminal 20 user (BB) (this example). Then, "5,000 yen") is displayed.

Based on the fact that the remittance amount of the current terminal 20 user (BB) is larger than the remittance amount to be remitted to the first user, the terminal 20 user (BB) is the first user (A.B.). It is possible to remit the amount corresponding to the remittance request information and the remittance reminder information to A).

Tap the remittance area RM2 at the bottom of the screen on this remittance screen to move to the remittance confirmation screen shown in FIG. 2-9.
As an example, but not limited to, the remittance confirmation screen is a screen superimposed on the remittance screen, using the icon image and user name (AA) of the first user to be the remittance partner, and the payment application. Includes the remittance amount to be remitted to one user (3,000 yen in this example) and the confirmation button BT6 with the characters "confirmation" displayed.

When the user (BB) of the terminal 20 taps the confirmation button BT6, the amount of money displayed on the remittance confirmation screen (“3,000 yen” in this example) is the user of the terminal 20 (BB). ) Is transferred to the account of the first user (AA).
When the remittance is completed, the remittance completion screen shown in FIG. 2-10 is displayed on the terminal 20 of the user (BB).
As an example, not a limitation, the remittance completion screen is a screen superimposed on the remittance screen, and the user name (AA) of the first user to be the remittance partner and a message notifying that the remittance process is completed. Is displayed.

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

The control unit 11 of the server 10 determines whether or not to perform remittance reminding (server reminding in this embodiment) for the previous remittance request (S260). Specifically, it is determined that the remittance reminding is performed when the remittance settlement request information is not received from the terminal 20A in S120 as an example, not the limitation.

In this case, the remittance remind is not performed immediately after the remittance request information is transmitted to the terminal 20 in S110, but as an example, the remittance remind is performed at the timing when a certain time has elapsed. Can be done.

When it is determined to perform remittance reminding (S260: YES), the control unit 11 of the server 10 creates remittance remind information set with the same ID as the remittance request management ID set in S110, and the second remittance request management data. Update 157B. Then, the control unit 11 of the server 10 transmits the generated remittance reminder information to the terminal 20B by the communication I / F14 together with the remittance request management ID (S270). Then, the control unit 11 of the server 10 shifts the processing to S120.

When the remittance reminder information is received from the server 10 by the communication I / F 22 (B240: YES), the control unit 21 of the terminal 20B causes the display unit 24 to display the remittance reminder display (B250). Then, the control unit 21 of the terminal 20B shifts the 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 apparatus in this embodiment.
This flowchart corresponds to the processing portion of FIG. 1-14 in the flowcharts of FIGS. 1-13 to 1-14, and the server 10 is transmitted from the remittance master user's terminal 20 (terminal 20A in this example). It is a flowchart which shows the process of transmitting the remittance reminder information to the terminal 20 (terminal 20B in this example) of the remittance request destination user based on receiving the remittance reminder transmission request information.

After A150 in FIG. 1-13, the control unit 21 of the terminal 20A is not limited to, but as an example, an input for requesting execution of remittance reminder (hereinafter referred to as “remittance reminder execution input”) is input to the input unit. It is determined whether or not the remittance reminder is requested to be executed based on whether or not the remittance is made (A260).
The remittance reminder execution input can be realized by an operation input or a sound input as an example, not limited to the same as the above-mentioned remittance request execution input.

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

The control unit 11 of the server 10 determines whether or not the remittance reminder transmission request information has been received from the terminal 20A by the communication I / F14 (S265), and if it is determined that the information has been received (S265: YES), processes in S270. To move.

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

The second remittance process is not limited to, but as an example, a process for realizing a remittance from the terminal user to the first user, and a process related to the remittance from the terminal user to the first user in some way. Can be included. Not only the processing directly related to the remittance but also the processing indirectly related to the remittance can be included in the remittance processing executed by the terminal.

In the above processing example, the following processing is included in the second remittance processing as an example, not a limitation.
(1) Remittance settlement request information is received from the terminal 20 by communication I / F14 (2) Remittance settlement processing (including processing for adjusting the balance of the electronic money account balance).
(3) Processing for transmitting remittance information / receipt information to the terminal 20 by communication I / F14

<Effect of the second embodiment>
In this embodiment, the remittance request information (not limited, but an example of the first information) regarding the remittance request by the remittance master user (not limited, but an example of the first user) is the remittance master user (not limited, not limited to the first user). Based on the input to the terminal 20 of the remittance master user by (1 example)), the remittance is transmitted to the terminal 20 of the remittance request destination user via the server 10.
On the other hand, the remittance reminder information (not limited, but an example of the second information) is transmitted by the server 10 to the terminal 20 of the remittance request destination user, and the remittance reminder display (not limited, but an example of the second display) is the remittance. Based on the remittance information, the configuration displayed on the display unit 24 of the terminal 20 of the remittance request destination user is shown.
As an example of the effect of the embodiment obtained by such a configuration, the first information can be transmitted to the terminal via the server according to the intention of the first user of the remittance request source. Further, after the second information is transmitted from the server to the terminal, the second display can be displayed on the display unit of the terminal based on the second information.

Further, in this embodiment, the server 10 sends remittance request information (not limited, but an example of the first information regarding the remittance request) regarding the remittance request by the remittance master user (not limited, but an example of the first user) to the remittance request destination. Remittance is performed by communication I / F 14 to the user's terminal 20 (not limited, but an example of the terminal). Further, the server 10 transmits the remittance reminder information (not limited, but an example of the second information based on the remittance request) based on the remittance request to the terminal 20 of the remittance request destination user by the communication I / F14. Then, the server 10 remittances the second remittance based on the input to the remittance remind display (not limited, but an example of the second display based on the second information) displayed on the display unit 24 of the terminal 20 of the remittance request destination user. A configuration is shown in which the control unit 11 executes a process (not limited to an example of a remittance process relating to a remittance from a terminal user to a first user based on a remittance request).
As an example of the effect of the modification obtained by such a configuration, the remittance process is executed by the control unit of the server based on the input to the second display displayed on the display unit of the terminal, and the user of the terminal first executes the remittance process. Remittance to the user can be easily realized.

<Second modification (1)>
The user interface of the display screen in the payment application described in the second embodiment, the functions of the payment application, and the like can be appropriately redesigned.

As an example, not a limitation, FIG. 2-13 shows a remittance request list screen displayed on the terminal 20 of the user (BB).
This remittance request list screen is not limited to, but as an example, below the title of "Remittance Request List", remittance processing is not completed among past remittance requests to the terminal user (BB). The remittance request history is displayed.

In this example, the user (BB) of the terminal 20 is the first user, A.B. Based on the fact that the remittance request information is received from A, A. The icon image and user name of A, the icon of the character "request received", the date and time when the remittance request information was received (2020.04.220 21:30), and A. An icon with the letters "Payment" indicating that you are in a position to pay to A, and A. The amount to be paid to A (3,000 yen) is displayed.

Further, the user (BB) of the terminal 20 is the first user, D.I. Based on the fact that the remittance request information is also received from D, D.D. Information about the remittance request from D is displayed. In this example, D. The date and time when the remittance request information from D was received is 2020.04.21 08:42, and D. The amount to be paid to D is "500 yen".

Among the plurality of (AA, BB) first users, A. Regarding the remittance request from A, based on the fact that after the terminal 20 receives the remittance request information, the remittance reminder information is also received, the area R22 below the area R21 (not limited to the display area related to the remittance request information). As an example of the display area related to remittance reminder information corresponding to), A. The icon image and user name of A, the icon of the characters "Remind reception", the reception date and time of the remittance remind information (2020.04.23 17:00), and A. An icon with the letters "Payment" indicating that you are in a position to pay to A, and A. The amount to be paid to A (3,000 yen) is displayed.

Since the information displayed in the area R21 and the information displayed in the area R22 are information based on the common remittance request information, A. An icon with the letters "Payment" indicating that you are in a position to pay to A, and A. The amount to be paid to A (3,000 yen) is the same.

On the other hand, unlike the area R21, an arrow indicating that the information is related to the information displayed in the area R21 is displayed in the area R22. In addition, A. in R22. The icon image of A, the user name, and the icon of the character "Remind receive" are the icons of A. in the area R21, respectively. It is displayed on the right side of the icon image of A, the user name, and the icon of the character "request received".

As an example, not limited to, the information displayed in the area 21 displayed based on the remittance request information received by the terminal 20 and the area 22 displayed based on the remittance reminder information based on the remittance request information. Due to the difference in the display position of at least a part of the information (for example, the image icon and the user name of the first user and the icon displayed above the information), the user can make a remittance request and remittance. Easy to understand the correspondence with reminders.

As an example, not a limitation, the information displayed as the remittance request history can be sorted by the operation of the user of the terminal 20.
On the screen displaying the remittance request history shown in FIG. 2-13, the sort item selection area SR is displayed as shown in FIG. 2-14 when the blank area is tapped by the user.

At the upper part of the sort item selection area SR, information for notifying that the sort is executed based on the items shown below (as an example, not a limitation, the characters "sort requests") is displayed.
Below that is a button BTS1 for performing a sort based on the date and time the remittance request information or remittance remind information was received, and the remittance amount (not limited, but as an example, remittance request information or remittance remind information). A button BTS2 for executing sorting based on the amount of money) and a button BTS3 for executing sorting based on the user name registered as a friend in the payment application or the messaging application linked with the payment application are displayed.

As an example, not a limitation, a user (one account) of one terminal 20 performs a process for adding a user (another account) of another terminal 20 as a friend from his / her own terminal 20, and the server 10 performs a process. By executing the process of adding / registering a friend (friend addition process, friend registration process), it is possible to send / receive a message between the terminals 20 registered as friends via the server 10. An account for a messaging application owned by an individual user is referred to as a "general account". The history of messages sent and received between the terminals 20 of the user who owns the general account is displayed as a talk room or the like on the display unit 24 of the terminal 20.

As an example, not limited to, when the user (BB) of the terminal 20 taps the button BTS3, as shown in FIG. 2-15, the information displayed as the remittance request history is sorted and the remittance request is made. Of the first users (AA and DD as examples, not limited), the user names of the users registered as friends (AA and DD as examples, not limited) are in alphabetical order. It is displayed based on.
In this example, in the area R21, the first user, A. The icon image of A and the user name are displayed, and in the area R22, the first user B. The icon image of B and the user name are displayed.

The example shown in FIG. 2-15 is different from the example shown in FIG. 2-14, and after sorting, both the "request received" icon and the "remind received" icon are displayed as information about the first user. None of the date and time when the remittance request information was received and the date and time when the remittance reminder information was received are displayed, and the information regarding the remittance amount is not displayed.
The screen shown in FIG. 2-15 is such that at least the first user who has made the remittance request can be grasped.

On the screen shown in FIG. 2-15, when the user (BB) of the terminal 20 taps the area R21 corresponding to the first user (AA as an example, not limited) registered as a friend, FIG. As shown in 16, detailed information about the remittance request of the selected first user (AA) is displayed.
In the area R20 at the top of the screen, information notifying that the history is related to the remittance request of the selected first user (AA) (not limited, but as an example, the characters "A.A. remittance request list"). Is displayed, and below that, a detailed history of the remittance request of the selected first user (AA) is displayed in the manner shown in FIG. 2-13.

As an example, not a limitation, each information displayed in the areas R21 and R22 of FIG. 2-13 (not a limitation, an example of a display based on remittance request information, an example of a display based on remittance reminder information) is shown in FIG. 2-16. It is displayed in the areas R21 and R22 of.
The history of remittance requests of other first users (DD) that have not been selected is not displayed.

As an example, not a limitation, when the user (BB) of the terminal 20 taps the button BTS1 on the screen of FIG. 2-14, the information displayed as the remittance request history is displayed as shown in FIG. 2-17. History of the first user (AA and DD, not limited, as an example) that was sorted and made a remittance request (an example of display based on remittance request information, not limited, display based on remittance reminder information) (Example) is displayed based on the reception date and time.

In this example, the newest history is A.I. Since the history is based on the remittance reminder information (reception date and time 2020.04.23 17:00) corresponding to the remittance request of 3,000 yen by A, A. The icon of "Remind reception" is displayed together with the icon image of A and the user name.
Next, the new history is the other first user, B. Since the history is based on the remittance request information (reception date and time 2020.04.21 08:42) corresponding to the remittance request of 500 yen by B, the second area R22 from the top includes B.I. Along with the icon image of B and the user name, the "request received" icon is displayed.
Next, the new history is A.I. Since the history is based on the remittance request information (reception date and time 2020.04.20 21:30) corresponding to the remittance request of 3,000 yen by A, the third area R23 from the top includes A. Along with the icon image of A and the user name, the "request received" icon is displayed.

The information displayed in the area R21 and the information displayed in the area R23 are both information related to a common remittance request from one of the first users (AA).
However, after receiving the remittance request information based on the first remittance request of one first user (AA), the remittance request information based on the second remittance request of the other first user (DD) is received. After that, since the remittance reminder information based on the first remittance request of one of the first users (AA) is received, the area R21 where the information corresponding to the first remittance request is displayed and the first remittance request. Information corresponding to the second remittance request is displayed in the area R22, which is an area between the area R23 and the area R23 in which the information corresponding to is displayed.

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

As an example, not a limitation, when the user (BB) of the terminal 20 taps the remittance link information displayed in the area RM1 on the screen shown in FIG. 2-7, the remittance screen of FIG. 2-8 is displayed. Before moving to, the friend registration confirmation screen shown in Fig. 2-18 is displayed.
As an example, not a limitation, the friend registration confirmation screen is a screen superimposed and displayed on the screen of FIG. 2-7, and the person who is trying to send money (not a limitation, but as an example, the user name (A) displayed on RM1. A message for the user (BB) of the terminal 20 to confirm whether the first user of A) is a registered friend (as an example, not limited to, "Is the person who requested the remittance a friend?" Please check again. Do you want to send money? ") Is displayed.

When the user (BB) of the terminal 20 taps the confirmation button BT7 on the friend registration screen, the screen shifts to the remittance screen shown in FIG. 2-8.
In this way, even if the remittance link information is tapped, a screen is displayed to confirm whether the first user who reminded the remittance is a registered friend before moving to the remittance screen. By doing so, it is possible to prevent inadvertent remittances to users who are not registered as friends.

<Second modification (2)>
Although related to the first modification (2), the terminal 20 of the remittance request destination user can execute the remittance notification process based on the receipt of the remittance remind information. This remind notification processing can be realized by any of the following methods as an example without limitation.

-Controls the display unit 24 to display the push notification based on the receipt of the remittance reminder information push-transmitted from the server 10.
The control unit 21 controls the sound output unit 26 to output a predetermined sound.
The control unit 21 controls a vibrating unit (not shown) to vibrate the housing of the terminal 20.
The control unit 21 controls a light emitting unit (not shown) to emit a predetermined light.

"Push transmission" is not limited to, but as an example, the information to be transmitted (in this example, remittance reminder information) is transmitted from the source device (server 10 in this example), or the destination. It means that what is received by the device (in this example, the terminal 20 of the remittance request destination user) is transmitted so as to be push-notified by the destination device.

In addition to receiving the remittance reminder information, the same reminder notification condition as in the first modification (2) is set, and the reminder notification process is executed based on the fact that the reminder notification condition is satisfied. It can also be.

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

<Third Example>
The third embodiment is an example relating to the method and timing of display / transmission of remittance reminder information.
The contents described in the third embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

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

In this timing chart, the horizontal axis is the time axis, and the timing at which the terminal 20 of the remittance request destination user performs the remittance request display / remittance remind display is shown. Remittance request information is indicated by a white circle, and remittance reminder information is indicated by a white diamond.

There is "auto" as a setting, which indicates a setting in which 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 performs a remittance reminder display every time the set time tm elapses after the remittance request display is performed, as an example.

In addition, unlike this, the terminal 20 of the remittance request destination user is not limited, but as an example, the remittance reminder is displayed every time the set time tm elapses after receiving the remittance request information from the server 10. It may or may not be.

<Effect of the third embodiment>
In this embodiment, the remittance request information (not limited, but an example of the first information) is input to the terminal 20 by the remittance master user (not limited, but an example of the first user) to the server. It is transmitted to the terminal 20 of the remittance request destination user via 10.
Further, the remittance reminder display (an example of the second display, not the limitation) is the time when the remittance request display (an example of the first display, not the limitation) is displayed on the display unit 24 of the terminal 20 of the remittance request destination user. Alternatively, the configuration is shown in which the remittance request information (not limited, but an example of the first information) is displayed on the display unit 24 of the remittance request destination user's terminal 20 based on the time received by the remittance request destination user's terminal 20. ing.
As an example of the effect of the embodiment obtained by such a configuration, the second display is displayed at the display unit of the terminal, or the first information is received by the terminal at an appropriate timing. The display can be displayed on the display unit of the terminal.

Further, in this embodiment, the terminal 20 of the remittance request destination user displays the first remittance reminder display (not limited, but an example of the third display) on the display unit 24. Further, the terminal 20 of the remittance request destination user displays the second remittance reminder display (not limited, but an example of the fourth display) based on the elapse of the set time after displaying the first remittance reminder display. The configuration to be displayed on 24 is shown.
As an example of the effect of the embodiment obtained by such a configuration, the fourth display can be displayed on the display unit of the terminal based on the display of the third display on the display unit of the terminal. ..

<Third variant (1)>
The method of the third embodiment can be similarly applied to the server reminding method described in the second embodiment.

FIG. 3-2 is a diagram showing an example of a timing chart for explaining the server reminder in this modification.
The way to read the figure is the same as in Fig. 3-1. The diamond corresponding to the remittance reminder information sent manually is shown in "gray", and the diamond corresponding to the remittance reminder information sent automatically is shown in "white". There is.

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

The setting B is "auto", which is a setting in which the server 10 automatically transmits the remittance reminder information to the terminal 20 of the remittance request destination user regardless of the terminal 20 of the remittance master user. Specifically, the server 10 transmits the remittance reminder information to the terminal 20 of the remittance request destination user every time the set time tun elapses after the remittance request information is transmitted to the terminal 20 of the remittance request destination user.

Setting C is "auto & manual", which is a combination of setting A and setting B. In this setting, the server 10 basically transmits the remittance reminder information according to the setting B (auto). However, if the manual remittance reminder information transmission is inserted between the automatic remittance reminder information transmissions, the automatic remittance reminder information transmission will be delayed.

Specifically, as an example, not limited, the server 10 basically transmits the remittance request information to the terminal 20 of the remittance request destination user, and every time the set time tun elapses, the remittance request destination user's terminal. Send remittance reminder information to 20. However, if the manual remittance reminder information is sent between the automatic remittance reminder information transmissions, the manual remittance reminder information transmission timing will be used instead of the automatic remittance reminder information transmission timing. Remittance reminder information is transmitted every time the set time tun elapses.

Which of the settings A to C is applied is not limited, but as an example, the information about the setting is transmitted to the server 10 based on the input to the own terminal 20 by the remittance master user, and the setting is made on the server 10. Can be done.

Not limited to this, the above settings may or may not be made on the server 10 side based on the input by the payment service operator, the administrator of the server 10, or the like.

In this modification, the remittance request information (not limited, but an example of the first information) is input to the terminal 20 by the remittance master user (not limited, but an example of the first user) to the server. It is transmitted to the terminal 20 of the remittance request destination user via 10.
Further, the remittance reminder information (not limited, but an example of the second information) is transmitted by the server 10 to the terminal 20 of the remittance request destination user, and the remittance reminder display (not limited, but an example of the second display) is the remittance. Based on the remittance information, the configuration displayed on the display unit 24 of the terminal 20 of the remittance request destination user is shown.
As an example of the effect of the embodiment obtained by such a configuration, the first information can be transmitted to the terminal via the server according to the intention of the first user of the remittance request source. Further, after the second information is transmitted from the server to the terminal, the second display can be displayed on the display unit of the terminal based on the second information.

Further, in this modification, in the above, the remittance reminder information is based on the fact that the set time has elapsed since the remittance request information was transmitted to the terminal 20 of the remittance request destination user (not limited, the first information is the terminal). 1), or the first information is transmitted to the terminal based on the time received by the terminal).
As an example of the effect of the embodiment obtained by such a configuration, the second information is sent 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. Can be sent to.

Further, in this modification, in the above, the remittance request destination user's terminal 20 is the remittance master user based on the input of the remittance master user to the terminal 20 by the remittance master user (not limited, but an example of the first user). The first remittance reminder information (not limited, but an example of the third information based on the remittance request) transmitted from the terminal 20 of the above is received by the communication I / F22. Then, the terminal 20 of the remittance request destination user displays the first remittance reminder display (not limited, but an example of the third display) on the display unit 24. In this case, as an example, not limited, the second remittance reminder information (not limited, but an example of the second information) is sent to the terminal 20 based on the lapse of the set time after the first remittance reminder information is transmitted. Shows the configuration to be sent.
As an example of the effect of the embodiment obtained by such a configuration, the second information based on the remittance request is appropriately transmitted to the terminal based on the third information based on the remittance request being transmitted to the terminal. can do.

<Third variant (2)>
Regarding the terminal reminding method (setting: auto) described in the third embodiment, the set time may be different between the display of the first remittance reminding information and the display of the second and subsequent remittance reminding information. It is possible.

Specifically, the terminal 20 of the remittance request destination user performs the first remittance remind display at the timing when the first set time has elapsed from the remittance request display or the reception of the remittance request information.
Further, the terminal 20 of the remittance request destination user performs the second remittance remind display at the timing when the second set time has elapsed from the first display.
Further, the terminal 20 of the remittance request destination user performs the third remittance remind display at the timing when the third set time has elapsed from the second display.
The same applies hereinafter.

In this case, the first set time can be set to be the longest time as an example, not limited.

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

If the time is different, the set time can be shortened each time the remittance reminder is displayed, not as a limitation.
Specifically, as an example, not limited, the first set time is "24 hours", the second set time is "18 hours", the third set time is "12 hours", and so on. be able to.
By doing so, the display time interval (display time interval) related to the remittance request becomes shorter in stages, so that the user at the remittance request destination recognizes that the remittance has not been performed yet, and the remittance is performed quickly. Can be alerted as follows.

Contrary to the above, the first set time may or may not be the shortest.

Further, these contents can be similarly applied to the time interval (transmission time interval) of transmission of the remittance reminder information in the server reminder described in FIG. 3-2.

Further, in the setting C (auto & manual) of FIG. 3-2, when the manual remittance reminder information transmission is sandwiched between the automatic remittance reminder information transmission by the server 10, the automatic remittance reminder information transmission is performed. Instead of delaying, the automatic remittance reminder information transmission may or may not be skipped.

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

In this embodiment, a case where the terminal reminding method described in the first embodiment is applied and the terminal 20 of the remittance request destination user determines the success or failure of the remittance reminding condition and performs the terminal reminding will be described.

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

After B140 in FIG. 1-13, the control unit 21 of the terminal 20B determines whether or not the remittance reminder condition is satisfied (B450). Then, if it is determined that the condition is satisfied (B450: YES), the control unit 21 of the terminal 20B shifts the processing to the B150.

FIG. 4-2 is a diagram showing an example of remittance reminder condition data in which the remittance reminder condition in this embodiment is defined.
The remittance reminder condition data is defined by associating a category with a remittance reminder condition as an example, not a limitation.

Categories include, but are not limited to, categories based on different concepts such as "time," "balance," "deposit (remittance)," and "other."

The remittance reminder condition is not limited, but includes, as an example, a condition No. indicating the condition number and the content of the remittance reminder condition of the condition No.

A specific example will be described.
(1) Category "Time"
Regarding the condition No. "PA-1", "the time has become the set time" is defined as the content of the remittance reminder condition. As the set time, an arbitrary time every day (not limited to midnight or 12:00 noon as an example) can be set.
This condition is a condition for notifying the user that the remittance has not been performed yet by displaying the remittance reminder display on the display unit 24 at the timing when the current time becomes the set time every day.

In this case, the control unit 21 of the terminal 20 determines whether or not the time measured by the clock unit 29A has reached the set time, and if it determines that the time has reached the set time, the remittance reminder display is displayed on the display unit 24. Can be done.

Regarding the condition No. "PA-2", "the timing of the remittance & the time is included in the first set time zone" is stipulated as the content of the remittance reminder condition. Any set time zone can be set every day in the first set time zone.
This condition is that when it is time to remind the terminal, if the current time is included in the set time zone, the remittance reminder display is displayed on the display unit 24 so that the remittance has not been performed yet. It is a condition to inform.

As an example, not limited, the time zone when the user is likely to browse the terminal 20, as an example, not limited, from 9 pm to midnight when the user often returns home and spends free time A time zone such as a time zone can be set as the first set time zone.

The timing of the terminal reminding when this condition is applied is not limited, and the timing described in the third embodiment (FIG. 3-1) can be applied as an example.
In this case, the control unit 21 of the terminal 20 determines whether or not it is time to remind the terminal. Then, when it is the timing to remind the terminal, it is determined whether or not the time measured by the clock unit 29A is included in the first set time zone, and when it is determined that the time is included, the remittance remind display is displayed. It can be displayed on the unit 24.

Regarding the condition No. "PA-3", "the timing of the remittance & the time is not included in the second set time zone" is stipulated as the content of the remittance reminder condition. As the second set time zone, an arbitrary set time zone can be set every day.
This condition is that when it is time to remind the terminal, if the current time is not included in the set time zone, the remittance reminder display is displayed on the display unit 24 so that the remittance has not been performed yet. It is a condition to inform the user.

As an example, not limited, a time zone when the user is unlikely to browse the terminal 20, a time zone late at night (until midnight the next day), when the user is likely to be sleeping, as an example, not limited, before dawn (until midnight the next day) A time zone such as a time zone (until 3:00 the next day) and a time zone at dawn (from 3:00 the next day) can be set as the second set time zone.

As for the timing of the terminal reminding when this condition is applied, the timing described in the third embodiment (FIG. 3-1) can be applied as an example without limitation.
In this case, the control unit 21 of the terminal 20 determines whether or not it is time to remind the terminal. Then, when it is the timing to remind the terminal, it is determined whether or not the time measured by the clock unit 29A is included in the second set time zone, and when it is determined that the time is not included, the remittance remind display is displayed on the display unit 24. Can be displayed in.

Regarding the condition No. "PA-4", "the date has been set" is stipulated as the content of the remittance reminder condition. In this case, any date (not limited, but as an example, "15th of every month" or "25th of every month") can be set as the date.
This condition is a condition for notifying the user that the remittance has not been performed yet by displaying the remittance reminder display on the display unit 24 at the timing when the current date becomes the set date.

As an example, not limited, a date on which the remittance request destination user can afford money can be set, and as an example, not limited, a date on which salary is paid (salary date) can be set.

In this case, the control unit 21 of the terminal 20 determines whether or not the current date is the set date based on the timekeeping information of the clock unit 29A, and if it is determined that the current date has been set, the remittance reminder display is displayed. It can be displayed on 24.

(2) Category "Balance"
Regarding the condition No. "PB-1", "the electronic commerce account balance is equal to or greater than the set amount" is stipulated as the content of the remittance reminder condition. Any amount (not limited, but "30,000 yen" as an example) can be set as the set amount.
This condition is a condition for notifying the user that the remittance has not been performed yet by displaying the remittance reminder display on the display unit 24 at the timing when the account balance of the electronic money exceeds the set amount.

As an example, not a limitation, it is possible to set an amount that is at least twice the maximum amount of the remittance request amount for the remittance request destination user, or a somewhat large amount such as 30,000 yen or more as the set amount. can.

In this case, as an example, not limited to, the control unit 21 of the terminal 20 inquires about the electronic money account balance of the user of the terminal 20 by the communication I / F22. When the terminal 20 inquires about the electronic commerce account balance by the communication I / F 14, the control unit 11 of the server 10 transmits the information of the user's electronic commerce account balance to the terminal 20 by the communication I / F 14.
Then, the control unit 21 of the terminal 20 determines whether or not the electronic commerce account balance is equal to or greater than the set amount based on the received electronic commerce account balance information, and if it is determined that the electronic commerce account balance is equal to or greater than the set amount, the remittance reminder display is displayed. It can be displayed on the unit 24.

Regarding the condition No. "PB-2", "the balance of possession is equal to or greater than the set amount" is stipulated as the content of the remittance reminder condition. Any amount (not limited, but "30,000 yen" as an example) can be set as the set amount.
This condition is intended to inform the user that the remittance has not been performed yet by displaying the remittance reminder display on the display unit 24 at the timing when the balance of possession input to the terminal 20 by the user exceeds the set amount. It is a condition.

In this case, the control unit 21 of the terminal 20 causes the display unit 24 to input the possession balance by displaying a screen prompting the user to input the possession balance. Then, it is possible to determine whether or not the input balance of possession is equal to or greater than the set amount, and if it is determined that the balance of possession is equal to or greater than the set amount, the remittance reminder display can be displayed on the display unit 24. ..

(3) Category "Deposit (remittance)"
Regarding the condition No. "PC-1", "payment by borrowing a loan" is stipulated as the content of the remittance reminder condition.
This condition is not limited, but as an example, a loan service by the user, and not limited, as an example, a service provided by a business operator of a loan service, and the user is provided with an application related to physical money or electronic money such as a loan application. By using a service that allows you to borrow a loan and displaying a remittance reminder display on the display unit 24 when the money is deposited in the account balance of a bank or electronic money, the user is notified that the remittance has not been performed yet. It is a condition of purpose.

The loan service operator may be, for example, the same operator as the payment application operator or the messaging service operator described above, or may be a different operator.
If it is a different business operator, the loan service business operator cooperates with the payment application business operator or the messaging service business operator, and sends information about the loan amount of the user of the terminal 20 to the server 10, etc. It can be provided to payment application operators and messaging application operators.

As an example, not limited, the remittance request destination is made by depositing (remittance) from the loan service provider to the bank of the user who requested the remittance (net bank as an example, not limited) or the account balance of the electronic money of the payment application. When the user has an economic margin, it can be defined as the content of the remittance reminder condition.

In this case, the control unit 21 of the terminal 20 determines whether or not the loan has been made by borrowing the loan, based on the information (including the notification) transmitted from the server 10 as an example, not the limitation. Then, when it is determined that the remittance has been made, the remittance reminder display can be displayed on the display unit 24.

Regarding the condition No. "PC-2", "payment by purchasing the exhibited product" is stipulated as the content of the remittance reminder condition.
This condition is not a limitation but an example, and the user is a flea market service, and not a limitation but an example, a service provided by a flea market service operator, which is referred to as a flea market application (hereinafter referred to as "flea market application"). ), Etc., using a service that allows you to list and purchase products, display the remittance remind display on the display unit 24 when the listed product is purchased and the money is deposited in the electronic money account balance. This is a condition to inform the user that the remittance has not been performed yet.

As an example, not limited to, remittance reminders when the remittance request destination user has an economic margin by depositing (remittance) from the frima application to the electronic money account balance of the payment application of the remittance request destination user. It can be defined as the content of the condition.

In this case, the control unit 21 of the terminal 20 determines whether or not the product exhibited by the flea market application has been purchased and paid for based on the information (including the notification) transmitted from the server 10. Then, when it is determined that the remittance has been made, the remittance reminder display can be displayed on the display unit 24.

(3) Category "Other"
Regarding the condition No. "PD-1", "the exhibited product has been purchased (unpaid)" is stipulated as the content of the remittance reminder condition.
This condition is not limited, but as an example, by displaying the remittance reminder display on the display unit 24 at the timing when the product exhibited by the user through the flea market application or the like is purchased (the timing when the remittance is not deposited in the electronic money account balance). , It is a condition to inform the user that the remittance has not been performed yet.

As an example, not limited, when the product sold by the remittance request destination user is purchased by the flea market application, etc., the electronic money account balance of the remittance request destination user is purchased as an example, not limited. Although it has not been deposited from the flea market application, it can be expected to be deposited. Therefore, the case where the remittance request destination user can be expected to have an economical margin can be defined as the content of the remittance reminder condition.

In this case, the control unit 21 of the terminal 20 determines whether or not the product exhibited by the flea market application has been purchased based on the information (including the notification) transmitted from the server 10, and determines that the product has been purchased. The remittance reminder display can be displayed on the display unit 24.

Regarding the condition No. "PD-2", "Job-seeking application is in progress" is stipulated as the content of the remittance reminder condition.
This condition is a predetermined timing of the period during which the user is seeking a job in a service such as a job search service (job search application) (the job search application is not limited, but as an example, the timing of entry into a company or a job offer notification from the company. It is a condition for notifying the user that the remittance has not been performed yet by displaying the remittance reminder display on the display unit 24 at (timing, etc.).

As an example, not limited, when the remittance request destination user is seeking a job in a job search service, etc., as an example, not limited, if the remittance request destination user seeks a job, there is a possibility that wages will be earned after working. Since it is a case where it is possible to expect an economic margin for the remittance request destination user, it can be defined as the content of the remittance reminder condition.

In this case, the control unit 21 of the terminal 20 determines whether or not the job-seeking application is being executed on its own terminal 20, and if it is determined that the application is being executed, the remittance reminder display is displayed on the display unit 24. Can be done.

Regarding the condition No. "PD-3", "purchase of goods by flea market application" is stipulated as the content of the remittance reminder condition.
This condition is a condition for notifying the user that the remittance has not been performed yet by displaying the remittance remind display on the display unit 24 at the timing when the user purchases the exhibited product in the service such as the flea market application. Is.

As an example, not limited, when the remittance request destination user purchases the product by flea market application etc., as an example, not limited, when the remittance request destination user purchases the product, the remittance request destination user can afford economically. If it can be recognized, it can be defined as the content of the remittance reminder condition.

In this case, the control unit 21 of the terminal 20 determines whether or not the product exhibited by the flea market application has been purchased based on the information (including the notification) transmitted from the server 10, and determines that the product has been purchased. In this case, the remittance reminder display can be displayed on the display unit 24.

The above remittance reminder condition is not limited, but as an example, is set by the remittance request destination user's terminal 20 based on the input to the own terminal 20 by the remittance request destination user, and the storage unit 28 of the remittance request destination user's terminal 20. Can be remembered in.

Not limited to this, but as an example, the above remittance reminder condition may be set by the remittance master user's terminal 20 based on the input to the own terminal 20 by the remittance master user. , You don't have to do that. In this case, as an example, not limited, the remittance reminder condition set by the remittance master user's terminal 20 is transmitted / notified to the remittance request destination user's terminal 20 via the server 10, and the remittance request destination user's terminal 20 is notified. It can be stored in the storage unit 28 of the terminal 20.

Further, when the terminal 20 of the remittance request destination user determines the success or failure of the above remittance reminder condition, the success or failure of one condition may be determined, or the success or failure of two or more conditions may be determined. You may. That is, the determination may be made by combining two or more conditions.

<Display screen>
FIG. 4-3 shows, as an example, not limited to, a user (BB) who has received remittance request information but has not yet completed remittance, makes a transaction using the above-mentioned flea market application, and the user ( An example is shown in which a deposit is made in the account of BB) according to the sales amount.

The terminal 20 of the user (BB) receives a message MS25 indicating that the transaction by the payment application is completed from the official account of the payment application.
As an example, not a limitation, this message MS25 contains the characters "transaction completed" indicating that the transaction has been completed, the sales amount due to the transaction ("1,600 yen" in this example), and the user (BB). ) Is in a position to receive the sales amount, and includes an icon of the character "receipt" and the date and time when the transaction is completed (2020.0423 20:59 in this example).

When this message MS25 is displayed, it is highly possible that at least an amount corresponding to the sales amount remains in the electronic money account of the user (BB).

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

The content of the message MS26 is the same as the content of the remittance reminder display MS4A described above, except that the icon image of the official account is included instead of the icon image of the first user (AA).

As an example, the terminal 20 receives the message MS 26 immediately after receiving the message MS 25. Therefore, it can be said that there is a high possibility that the user (BB) confirms the message MS26 in a state where at least an amount corresponding to the sales amount remains in the electronic money account of the user (BB).
As an example, but not a limitation, the display of this message MS26 can prompt the user (BB) to make a remittance immediately after the deposit is made in the account.

<Effect of Fourth Example>
In this embodiment, the remittance reminder display (an example of the second display, not the limitation) is displayed on the terminal 20 of the remittance request destination user based on the remittance reminder condition (an example of the first condition, not the limitation). The configuration is shown.
As an example of the effect of the embodiment obtained by such a configuration, the second display based on the remittance request can be appropriately displayed on the display unit of the terminal based on the set first condition.

Further, in this embodiment, the remittance reminder condition shows a configuration including a condition such as a time, a time zone, a date, and an elapsed time (an example of a condition relating to time, not a limitation).
As an example of the effect of the embodiment obtained by such a configuration, the second display based on the remittance request can be appropriately displayed on the display unit of the terminal based on the condition regarding time.

Further, in this embodiment, the remittance reminder condition shows a configuration including a time or a time condition set by the terminal 20 (not limited, but an example of the terminal) of the remittance request destination user.
As an example of the effect of the embodiment obtained by such a configuration, the second display based on the remittance request is displayed on the display unit of the terminal at an appropriate timing according to the intention of the user of the remittance request destination. Can be done.

Further, in this embodiment, the remittance reminder condition shows a configuration including a time or a time condition set by the remittance master user terminal 20 (not limited to, but an example of the terminal of the first user).
As an example of the effect of the embodiment obtained by such a configuration, the second display based on the remittance request is displayed on the display unit of the terminal at an appropriate timing according to the intention of the first user of the remittance request source. can do.

Further, in this embodiment, the remittance reminder condition shows a configuration including a condition relating to the balance such as the electronic money account balance and the possession balance of the remittance request destination user (not limited, but an example of the balance associated with the terminal user). ing.
As an example of the effect of the embodiment obtained by such a configuration, the second display based on the remittance request is displayed on the display unit of the terminal at an appropriate timing according to the balance of the user who receives the remittance request. can do.

Further, in this embodiment, the remittance reminder condition shows a configuration including a condition relating to payment (remittance) to the remittance request destination user.
As an example of the effect of the embodiment obtained by such a configuration, the second display based on the remittance request can be displayed on the display unit of the terminal based on the conditions for remittance to the user of the terminal.

Further, the present embodiment shows a configuration in which the above-mentioned condition regarding the payment (remittance) to the remittance request destination user includes the payment (remittance) by the remittance request destination user borrowing a loan.
As an example of the effect of the embodiment obtained by such a configuration, the second display based on the remittance request is displayed at the timing when the terminal user borrows a loan and there is a high possibility that the terminal user has a margin of money. It can be displayed on the display unit of the terminal.

Further, in this embodiment, the condition regarding the payment (remittance) to the above-mentioned remittance request destination user is that the product purchased by the remittance request destination user has been purchased, and the purchaser of the product pays the remittance request destination user (remittance). It shows the configuration including remittance).
As an example of the effect of the embodiment obtained by such a configuration, it is highly possible that the product exhibited by the terminal user is purchased and paid (remittance) by the purchaser, and the terminal user has a margin of money. Then, the second display based on the remittance request can be displayed on the display unit of the terminal.

Further, in this embodiment, the remittance request condition shows a configuration including a condition relating to the purchase of the product exhibited by the remittance request destination user.
As an example of the effect of the embodiment obtained by such a configuration, the remittance request is made based on the fact that the product exhibited by the terminal user is expected to have a margin in the money of the terminal user. The second display based on this can be displayed on the display unit of the terminal.

<Fourth variant (1)>
It is also possible to apply the server reminding method described in the second embodiment so that the server 10 determines the success or failure of the remittance reminding condition and performs the server reminding.

In this case, basically, the same conditions as the remittance reminder conditions illustrated in the table of FIG. 4-2 can be applied. However, in this modification, the determination subject of the remittance reminder condition is not the terminal 20 but the server 10.

The condition of 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, the timing of reminding when the condition No. “PA-2” or the condition “PA-3” is applied is not limited, but is described in the third modification (1) (FIG. 3-2) as an example. Server reminder timing can be applied.

The condition of the category "balance" is the information of the electronic money account balance of the user of the terminal 20 stored and managed by the control unit 11 of the server 10 in the storage unit 15, or input by the terminal 20 and transmitted to the server 10. It can be determined based on the information on the balance of possession.

The condition of the category "payment (remittance)" is that the information of the electronic money account balance of the user of the terminal 20 stored and managed in the storage unit 15 by the control unit 11 of the server 10 is updated by the remittance settlement process. It can be determined based on the above.

Regarding the conditions of the category "Other", the condition of the condition No. "PD-1" is that if the flea market service is provided as one of the payment services, the control unit 11 of the server 10 uses the flea market service to terminal. It can be determined by detecting that the product exhibited by 20 users has been purchased.
If the business operator that provides the flea market service is different from the business operator that provides the payment service, the control unit 11 of the server 10 sells the user of the terminal 20 from a device such as a server of the business operator that provides the flea market service. It is possible to make a determination by configuring so that information indicating that the product has been purchased can be acquired.

The condition of the condition No. "PD-2" is that if the job-seeking service is provided as one of the payment services, the control unit 11 of the server 10 searches for the job-seeking information by the user of the terminal 20 using the job-seeking service. It can be determined by detecting that it is doing.
If the business operator that provides the job-seeking service is different from the business operator that provides the payment service, the control unit 11 of the server 10 causes the user of the terminal 20 to seek a job from a device such as a server of the business operator that provides the job-seeking service. Judgment can be made by configuring so that information indicating that the service is being used can be acquired.

The condition of the condition No. "PD-3" is that if the flea market service is provided as one of the payment services, the control unit 11 of the server 10 uses the flea market service to display the exhibited product at the terminal 20. It can be determined by detecting that the user has purchased the product.
If the business operator that provides the frima service is different from the business operator that provides the payment service, the control unit 11 of the server 10 selects the product exhibited from the device such as the server of the business operator that provides the frima service. The determination can be made by configuring the terminal 20 so that the user can acquire the information indicating that the purchase has been made.

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

After S150 in FIG. 1-13, the control unit 11 of the server 10 determines whether or not the remittance reminder condition is satisfied (S460). Then, if it is determined that it is satisfied (S460: YES), the control unit 11 of the server 10 shifts the processing to S270.

When the remittance remind information is received from the server 10 by the communication I / F 22, the control unit 21 of the terminal 20B executes the process on the B250.

In this modification, based on the success or failure of the remittance reminder condition (an example of the first condition, not the limitation), the terminal 20 of the remittance request destination user uses the remittance reminder information (the second information based on the remittance request, not the limitation). (Example) is received by communication I / F22. The remittance reminder display shows a configuration displayed on the display unit 24 of the terminal 20 of the remittance request destination user based on the reception of the remittance reminder information.
As an example of the effect of the embodiment obtained by such a configuration, the terminal can receive and display the second information based on the remittance request based on the first condition. Further, since it is not necessary for the terminal side to determine the success or failure of the first condition, the processing load of the terminal can be reduced.

<Fourth variant (2)>
In the fourth modification (1), the remittance reminder condition determined by the control unit 11 of the server 10 may include "the remittance reminder transmission request information has been received from the terminal of the remittance master user". It does not have to be.
The processing in this case can be realized by combining the processing of FIG. 2-12 and the processing of FIG. 4-5.

<Fifth Example>
The fifth embodiment is an embodiment in which the above-mentioned remittance request display and remittance reminder display are displayed in a chat room available by the chat service.
The contents described in the fifth embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

In this embodiment, the chat service is a messaging service (not limited to the instant messaging service: IMS), and a remittance request display and a remittance remind display are performed by a messaging application installed on the terminal 20.
In addition, as a chat room when applying a message service (messaging application), a talk room will be illustrated below.

<Display screen>
In the example below, A. who is both a user of the messaging application and a user of the payment application. A and B. B and C.I. It is assumed that C belongs to group X and is registered as a friend.

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

In this example, C.I. Although C responded that the remittance was sent, B. was a user of the other terminal 20. It shows that there is no response from B.
A. When A taps the remittance icon at the lower right of the icons displayed at the bottom of the talk room, the remittance item selection area SMR is displayed on the talk room.

At the top of the remittance item selection area SMR, information that informs that processing based on the function related to remittance is executed by operating the button shown below (as an example, not limited to the word "remittance menu") ) Is displayed.
Below that, a button BTM1 for remittance to another user, a button BTM2 for transmitting remittance request information to another user, and a button BTM3 for displaying the remittance request history are displayed.

As an example, not a limitation, the first user, A. When A taps the button BTM3, A. The history of A's past remittance requests for which the remittance process has not been completed is displayed on the talk room.

In this example, the first user (AA) is the user of the terminal 20. Although the remittance request information has been transmitted to B, the remittance process for this remittance request has not been completed. The icon image and user name of B, the icon of the characters "send request", the transmission date and time of the remittance request information (2020.04.220 21:30), and B. An icon with the letters "Receive" indicating that you are in a position to receive payment from B, and B. The amount of money (3,000 yen) to be received from B is displayed.

Further, in this example, the area RR displayed as "Remind" is provided at the lower part of the screen. By setting the check box of the area R21 to be checked by the first user (AA), each information displayed in the area R21 is selected.
By tapping the area RR in this state, the remittance reminder information based on the information displayed in the area R1 is transmitted to the terminal 20 of the user (BB) to whom the remittance request information is transmitted. To.

FIG. 5-2 shows, as an example, not a limitation, a message displayed on the terminal 20 of the first user (AA) belonging to the group X, and a user (BB) who is the target of the remittance reminding by the first user. The relationship between the message displayed on the terminal 20 of the user (CC) and the message displayed on the terminal 20 of the user (CC) who was not the target of the remittance by the first user is shown.

The terminal 20 of the first user (AA) has a B.I. The message MS11 is displayed as a message transmitted by oneself (AA) based on the fact that the remittance reminder information is transmitted to the terminal 20 of B.

As an example, but not exclusively, message MS11 has an icon with the words "Send Remittance" to indicate that it has sent remittance remind information to users in the group, and indicates that the message is based on the functionality of the payment application [ Payment App], the user name of the user in the group who received the remittance reminder information (in this example, the character "Remittance request to BB"), and the amount requested for remittance by the remittance reminder information (book) In the example, it includes (¥ 3,000) and an icon with the word "receive" indicating that you (AA) are in a position to receive payment.

As an example, not a limitation, a remittance button BT11a including the characters "remittance" and a button BT11b including the characters "decline" are displayed at the bottom of the message MS11.
Here, even if the first user (AA) taps the remittance button BT11a, since the remittance destination for this message MS11 is himself (AA), the remittance screen is displayed. No migration and no remittance processing is performed.
Therefore, the remittance button BT11a is displayed in a non-selectable mode because the remittance process is not executed according to the operation.

Further, even if the first user (AA) taps the button BT11b, since the remittance destination for this message MS11 is himself (AA), he / she can contact other users. , No message will be sent to the effect that the remittance has been declined.
Therefore, the button BT11b is displayed in a non-selectable mode because the message is not transmitted in response to the operation.

Remittance reminding information received B. On the terminal 20 of B, the message MS21 is displayed as a message of the first user (AA) based on the fact that the remittance reminder information is transmitted from the first user (AA).

As an example, but not limited to, the message MS21 has an icon with the words "Remind Receive" to indicate that it has received remittance remind information from users in the group, and [Payment Appp] to indicate that the message is based on the functionality of the payment application. ], The user name of the user (yourself) in the group who received the remittance reminder information (in this example, the character "Remittance request to BB"), and the amount requested for remittance by the remittance reminder information. (In this example, ¥ 3,000) and an icon with the characters "payment" indicating that you (BB) are in a position to make payments are included.

As an example, not a limitation, a remittance button BT21a including the characters "remittance" and a button BT21b including the characters "decline" are displayed at the bottom of the message MS21.
When the user (BB) of the terminal 20 taps the remittance button BT21a, the screen shifts to the remittance screen described above, and the remittance process can be executed.

That is, since the remittance destination for this message MS21 is the first user (AA) whose image icon and user name are displayed corresponding to the message MS21, the remittance button 21a can be operated. B. From B's account A. An amount equivalent to the remittance request amount (3,000 yen in this example) is remitted to A's account.
Therefore, since the remittance button BT21a is executed according to the operation, the remittance button BT11a is displayed in a selectable manner different from the remittance button BT11a described above and the remittance button 31a described later.

Further, when the user (BB) of the terminal 20 taps the button BT21b, a message to the effect that the remittance is refused is sent to the first user (AA) associated with the message MS21.
Therefore, since the button BT21b is transmitted in response to the operation, the button BT21b is displayed in a selectable manner different from the button BT11b described above and the button 31b described later.

The terminal 20 of another user (CC) who is neither the first user (AA) nor the user (BB) who is the target of the remittance reminder is the first user A. A is B. The message MS31 is displayed as the message transmitted by the first (AA) based on the transmission of the remittance reminder information to B.

As an example, not a limitation, remittance reminder information is transmitted from one user different from oneself (A.A., which is the first user) to the other user (BB) different from oneself to the message MS31. An icon with the word "Remind" to indicate that, the word [Payment App] to indicate that the message is based on the function of the payment application, and the user name of the user in the group who received the remittance reminder information (in this example). , "Request for remittance to BB"), the amount requested for remittance by the remittance remind information (3,000 yen in this example), the icon image of the first user (AA) and the remittance remind. The icon image of the user (BB) who received the information is included.

From the icon image of the first user (AA), an arrow pointing to the icon image of the user (BB) who received the remittance reminder information is displayed. As a result, the other user (CC) has received remittance reminder information from one user (AA) different from himself / herself to the other user (BB) different from himself / herself. Can be recognized.

Further, as an example, not limited to, the message MS31 includes both the icon of the character "reminder transmission" included in the message MS11 and the icon of the character "remind reception" included in the message MS21. Not. This makes it possible to recognize that the remittance reminder regarding the message MS31 is not from oneself to another user, nor from another user to oneself.

As an example, not a limitation, at the bottom of the message MS31, a remittance button BT31a including the characters "remittance" and a button BT31b containing the characters "decline" are both displayed in a non-selectable manner.

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

As an example, not a limitation, the message MS12 contains the characters [Payment App], a user name of the first user, a remittance request amount to the first user, and a message indicating that the payment of the remittance request amount has been completed. (In this example, the text "I sent 3,000 yen to Mr. A.") is included.

Further, the message MS13 is displayed as a message of oneself (AA) who is the first user.
As an example, not a limitation, the message MS13 contains the characters [Payment App], the user name of the user who was the target of the remittance reminder, and a message indicating that the remittance request amount was received from that user (in this example, "Remittance received", "Remittance received from BB"), the remittance request amount (3,000 yen in this example), and the position where you (AA) received the remittance request amount. Includes an icon with the letters "Receive" to indicate that it is.

On the other hand, a message is sent to the terminal 20 of the user (BB) who is the target of the remittance reminder and has paid the amount specified by the remittance reminder information as his (BB) message. MS22 is displayed.
As an example, not a limitation, the content of the message MS 22 is similar to the content of the message MS 12.

Further, the message MS23 is displayed as the message of the first user (AA). The message MS23 includes a "payment" character icon indicating that the person (BB) has paid the remittance request amount, and does not include a "receipt" character icon. It is different from MS13.

Further, a user who has paid the amount specified by the remittance reminder information to the terminal 20 of another user (CC) who is neither the first user (AA) nor the target of the remittance reminder. The message MS32 is displayed as the message of (BB).
As an example, not a limitation, the content of the message MS 32 is similar to the content of the message MS 12.

Further, the message MS33 is displayed as the message of the first user (AA). The message MS33 does not include either the "receive" character icon or the "pay" character icon, but instead has an icon image of the first user (AA) and a target for remittance reminders. It differs from the messages MS13 and MS23 in that it includes the icon image of the user (BB) who has become.

An arrow is displayed from the icon image of the first user (AA) different from oneself (CC) to the icon image of the user (BB) different from oneself (CC). .. As a result, the other user (CC) has received remittance reminder information from one user (AA) different from himself / herself to the other user (BB) different from himself / herself. Can be recognized.

<Processing>
5-4 to 5-5 are flowcharts showing an example of the flow of processing executed by each apparatus in this embodiment.
These flowcharts are flowcharts in which the flowcharts of FIGS. 1-13 to 1-14 are rewritten so that the remittance request information and the remittance reminder information are displayed in the talk room.

When the remittance request transmission request information is received from the terminal 20A by the communication I / F 14, the control unit 11 of the server 10 sends the remittance request message to the user A. A and user B. B and user C. It is added and updated to the group talk management data (group talk room) of the group members including at least C (S510).

In this example, a group talk room including three users is illustrated, but instead of this, the user A. A and user B. It may or may not be a talk room that includes two people with B. That is, it may be a talk room that includes at least two parties to the remittance (the remittance master user and the remittance request destination user).

After that, the control unit 11 of the server 10 transmits the added remittance request message to the terminal 20A, the terminal 20B, and the terminal 20C by the communication I / F14 (S520).
In response to this, the terminal 20A, the terminal 20B, and the terminal 20C display the received remittance request message in the group talk room by their respective control units 21 (A520, B520, C520).

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

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

After that, the control unit 11 of the server 10 transmits the added remittance message or the remittance message to the terminal 20A, the terminal 20B, and the terminal 20C by the communication I / F14 (S550).
In response to this, the terminal 20A, the terminal 20B, and the terminal 20C display the received remittance message or the remittance message in the group talk room by their respective control units 21 (A550, B550, C550).

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

After that, the control unit 11 of the server 10 transmits the added remittance reminder message to the terminal 20A, the terminal 20B, and the terminal 20C by the communication I / F14 (S580).
In response to this, the terminal 20A, the terminal 20B, and the terminal 20C display the received remittance remind message in the group talk room by their respective control units 21 (A580, B580, C580).

The control unit 21 of the terminal 20B determines whether or not there is an input for the remittance reminder message displayed in the group talk room (B590), and if it is determined that there is an input, the process is transferred to the B130.

<Effect of the fifth embodiment>
In this embodiment, the remittance request message is displayed (not limited, but an example of the first display based on the first information) and the remittance reminder message is displayed (not limited, but for the remittance request) on the terminal 20 of the remittance request destination user. Based on this, the second display (an example of the second display different from the first display) indicates a configuration to be displayed on the display unit 24 by a messaging application (not a limitation, but an example of the application) installed in the terminal 20.
As an example of the effect of the embodiment obtained by such a configuration, the user of the terminal can be made to recognize the first information and the second information by the application installed in the terminal.

Further, in this embodiment, the terminal 20 of the remittance request destination user includes at least a remittance request destination user (an example of a terminal user, not a limitation) and a remittance master user (an example of a first user, not a limitation). The group talk room including the group talk room (not limited, but an example of a chat room) is displayed 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 the effect of the embodiment obtained by such a configuration, the first information and the second information are effectively displayed to the terminal user by displaying the terminal user and the first user in a chat room including at least the first user. Can be recognized by.

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

<Display screen>
The example shown in FIG. 5-6 is a modification of FIG. 5-2.
On the terminal 20 of the first user (AA), the message MS11 of oneself (AA) can be viewed on the talk room.
Further, on the terminal 20 of the user (BB) who is the target of the remittance reminder, the message MS21 of the first user (AA) can be seen on the talk room.

On the other hand, in the terminal 20 of another user (CC) who is neither the first user (AA) nor the target of the remittance reminder, the terminal 20 of the first user (AA) is on the talk room. I cannot see the message MS31.

As described above, as an example, not limited, among the users belonging to the same group (X), the user (BB) who is the target of the remittance reminder, not the first user (AA) who performed the remittance reminder. Other users (CC) who are not may not be able to see the message about the remittance reminder on the talk room.

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

On the other hand, on the terminal 20 of the first user (AA), the message MS11 of oneself (AA) cannot be seen on the talk room.
Further, even on the terminal 20 of another user (CC) who is neither the first user (AA) nor the target of the remittance reminder, the message of the first user (AA) is displayed on the talk room. I can't see MS31.

As described above, as an example, not limited to users, among users belonging to the same group (X), users other than the user (BB) who is the target of the remittance reminder include the first user (AA). You may not be able to see the message about the remittance reminder.

<Data structure>
FIG. 5-8 is a diagram showing an example of a table for explaining a method of displaying a remittance request message and a remittance remind message in this modification.
In this table, as an example, not a limitation, a setting No. and a display flag are defined in association with each other.

The display flag is a flag indicating whether or not to display a remittance request message or a remittance remind message in the group talk room displayed on the display unit 24 of the user's terminal 20.

The display flags are not limited, but as an example, the display flag of the remittance master user (user A.A. in this example), the display flag of the remittance request destination user (user BB in this example), and other group users. (In this example, user CC) is included.

This will be described in detail.
The setting No. "1" stipulates that the display flags of the remittance master user, the remittance request destination user, and other group users are all set to "ON".
This means that the remittance request message / remittance remind message is displayed in the group talk room displayed on the terminals 20 of all users included in the same group regardless of whether or not they are the parties to the remittance request. ..

The setting No. "2" stipulates that the display flag is set to "ON" for the remittance master user and the remittance request destination user, and the display flag is set to "OFF" for the other group users.
This causes the group talk room displayed on the terminals 20 of the remittance master user and the remittance request destination user who are the parties to the remittance request to display the remittance request message and the remittance remind message, but the terminals of other group users who are not the parties. It means that the remittance request message / remittance remind message is not displayed in the group talk room displayed in 20.

The setting No. "3" stipulates that the display flag is set to "ON" for the remittance master user and the remittance request destination user, and the display flag is set to "OFF" for the other group users.
This causes the terminal 20 of the remittance master user and the remittance request destination user who are the parties to the remittance request to display the remittance request message and the remittance remind message, but the remittance request message is displayed on the terminals 20 of other group users who are not the parties.・ It means that the remittance reminder message is not displayed.

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

In A120, the control unit 21 of the terminal 20A transmits the remittance request transmission request information including the information for requesting the setting of the display flag to the server 10 by the communication I / F22.

The control unit 11 of the server 10 sets the display flag based on the information for 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 to the terminal 20 whose display flag is set to "ON" by the communication I / F14.
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 of the display unit 24.

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

Similarly, in S580, the control unit 11 of the server 10 transmits the added remittance reminder message to the terminal 20 whose display flag is set to "ON" by the communication I / F14.
In response to this, the terminal 20 whose display flag is set to "ON" displays the received remittance remind message in the group talk room of 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.
Instead of this, the server 10 may or may not set the display flag based on the input to the terminal 20 of the remittance request destination user.

Further, in the above process, it is decided to set a common display flag for both the remittance request message and the remittance reminder message, but the present invention is not limited to this.
Alternatively, the remittance request message and the remittance reminder message may or may not be individually set with display flags.
In this case, as an example, the setting of the display flag of setting No. "1" is applied to the remittance request message, and the display flag of setting No. "2" or setting No. "3" is set for the remittance remind message. It may be applied.

In this modification, the above group talk room includes a remittance request destination user (an example of a terminal user, not a limitation), a remittance master user (an example of a first user, not a limitation), and another group user (an example of a first user, not a limitation). Not limited to, but at least an example of a second user different from the first user), and the remittance remind message display indicates a configuration that is not displayed in the group talk room displayed on the terminal 20 of another group user. There is.
As an example of the effect of the modification obtained by such a configuration, it is possible to prevent a user who is not related to the remittance request, that is, a user who is not a party, from knowing the second information based on the remittance request.

Further, this modification shows a configuration in which the remittance remind message display is not displayed in the group talk room displayed on the terminal 20 of the remittance master user.
The first user is the user who makes the remittance request, and is aware that he / she has made the remittance request to the user of the terminal by at least the first information. Therefore, by preventing the second display based on the remittance request from being displayed in the chat room displayed on the terminal of the first user, information unnecessary for the first user is displayed on the terminal of the first user. It can be prevented.

<Fifth variant (2)>
The message based on the remittance reminder information displayed in the group talk room in the fifth embodiment may or may not be displayed as the message of the official account of the payment application instead of the message of the first user. good.

5-11 and 5-12 are modifications of FIGS. 5-2 and 5-3.
In the examples of FIGS. 5-2 and 5-3, the messages MS11, MS21, and MS31 from the first user (AA) to the user (BB) who was the target of the remittance reminder are the first user (A), respectively. It was displayed as the message of A).

As an example, not a limitation, the message MS11 is displayed as a message on the terminal 20 of the first user (AA), and the message MS21 is displayed on the terminal 20 of the user (BB) who is the target of the remittance reminder. It is displayed in association with the icon image of the first user (AA), and the message MS31 is also displayed in association with the icon image of the first user (AA) on the terminal 20 of another user (CC). ..
That is, the message based on the remittance reminder information was displayed as the message of the first user (AA) who performed the operation for transmitting the remittance reminder information.

In FIGS. 5-11 and 5-12, as an example, but not limited, the message based on the remittance reminder information is displayed as the message of the official account of the payment application, not as the message of the first user (AA). ..

As shown in FIG. 5-11, as an example rather than a limitation, A. A, B. B, and C.I. On the terminal 20 of any user of C, a message based on remittance reminder information from the first user (AA) to another user (BB) is displayed on the talk room as an icon image of the official account of the payment application. (In this example, the image including the characters "Pay") is displayed in association with it.

The first user, A. The message MS11a is displayed on the terminal 20 of A, and the user who is the target of the remittance reminder is B.I. The message MS21a is displayed on the terminal 20 of B, and the other user, C.I. The message MS31a is displayed on the terminal 20 of C.
The messages MS11a, MS21a, and MS31a have the same contents except for the display mode of the button, and all of them are associated with the icon image of the official account of the payment application.

As an example, but not limited to, the messages MS11a, MS21a, and MS31a all include the icon of the character "Remind", and are included in the icon of the character "Remind transmission" included in the message MS11 and in the message MS21. The icon of the word "Remind Receive" was not included.

Further, as an example, not limited to, the messages MS11a, MS21a, and MS31a are all the former together with the icon image of the first user (AA) and the icon image of the user (BB) who is the target of the remittance reminding. It contains an arrow from the icon image of the to the latter icon image.
The icon of the character "receive" included in the message MS11 and the icon of the character "payment" included in the message MS21 are not included.

Also, as an example, but not limited to, the other information contained in the messages MS11a, MS21a, and MS31a is similar to the other information contained in the messages MS11, MS12, and MS13, respectively.
As an example, but not limited to, the message MS11a includes a remittance button BT11a and a button BT11b in a non-selectable mode. Further, the message MS21a includes a remittance button BT21a and a button BT21b in selectable modes. Further, the message MS31a includes a remittance button BT31a and a button BT31b in a non-selectable mode.

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

Further, the message MS22 is displayed as a message of the user (BB) who has completed the remittance, and the message MS23 is displayed as a message of the first user (AA).
Further, on the terminal 20 of another user (CC), the message MS32 is displayed as a message of the user (BB) who has completed the remittance, and the message MS33 is displayed as a message of the first user (AA). Will be done.

The contents of the messages MS12 and MS13, the messages MS22 and MS23, and the messages MS32 and MS33 are the same as those shown in FIG. 5-3.

Not limited, but according to the examples shown in FIGS. 5-11 and 5-12, from the first user (AA) to B.I. The remittance reminder display based on the remittance request to B is displayed as a message of the official account of the payment application, so that the impression that the remittance reminder display is displayed based on the operation of the first user (AA) is softened. Can be done.

On the other hand, after the remittance process is completed, the messages MS12, MS22, and MS23 notifying that the remittance has been performed are displayed as messages of the user (BB) who received the remittance request, and the remittance request amount is received. By displaying the messages MS13, MS23, and MS33 notifying that as a message of the first user (AA), the relationship between the users is clarified.

The example shown in FIG. 5-13 is a modification of FIG. 5-11.
On the terminal 20 of the first user (AA), the message MS11a of the official account can be viewed on the talk room.
Further, on the terminal 20 of the user (BB) who is the target of the remittance reminder, the message MS21a of the official account can be viewed on the talk room.

On the other hand, on the terminal 20 of another user (CC) who is neither the first user (AA) nor the target of the remittance reminder, the message MS31a of the official account can be viewed on the talk room. Can not.

As described above, as an example, not limited, among the users belonging to the same group (X), the user (BB) who is the target of the remittance reminder, not the first user (AA) who performed the remittance reminder. Other users (CC) who are not may not be able to see the message about the remittance reminder on the talk room.

The example shown in FIG. 5-14 is a modification of FIG. 5-11.
On the terminal 20 of the user (BB) who is the target of the remittance reminder, the message MS21a of the official account can be viewed on the talk room.

On the other hand, on the terminal 20 of the first user (AA), the message MS11a of the official account cannot be seen on the talk room.
Further, even the terminal 20 of another user (CC) who is neither the first user (AA) nor the target of the remittance reminder cannot see the message MS31a of the official account on the talk room.

As described above, as an example, not limited to users, among users belonging to the same group (X), users other than the user (BB) who is the target of the remittance reminder include the first user (AA). You may not be able to see the message about the remittance reminder.

<Fifth variant (3)>
At least one of the remittance request message and the remittance remind message displayed in the group talk room in the fifth embodiment 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.
As an example, not a limitation, when a message based on remittance remind information (an example of a remittance remind display, not a limitation) is displayed in the talk room, the mention function in the messaging application automatically works, and the underlined "@username" Notation is emphasized.

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 the terminal of the user who receives the message by the mention function may or may not display the notification emphasizing that the message has been received.

As an example, not a limitation, the user specified as the user of the terminal 20 to display the remittance reminder display by the first user (AA) in the "user name" part of the "@username" (as an example, not a limitation). , The user name associated with the remittance request history that was the target of the drag operation) is displayed.
This user name is not a limitation but an example, and is a user name included in a remittance reminder display (not a limitation but an example, messages MS11b, MS21b, MS31b).

In the example shown in FIG. 5-15, the user designated by the mention function is B.I. As a message to B, the message MS11b is displayed on the terminal 20 of the first user (AA), and the message MS21b is displayed on the terminal 20 of the user (BB) who is the target of the remittance reminder. The message MS31b is displayed on the terminal 20 of the other user (CC).
At the beginning of each of the messages MS11b, MS21b, and MS31b, the message is B.I. The notation "@ BB" is used to indicate that the message is for B.

This modification shows a configuration in which the display of the remittance reminder message includes at least information that specifies a remittance request destination user by using the mention function (not limited, but an example of information indicating a terminal user).
As an example of the effect of the modification obtained by such a configuration, the second display including the information indicating the user of the terminal ensures that the user of the terminal recognizes that the display is the display that specifies himself / herself. Can be done.

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

In this case, as in the example shown on the display screen, only a part of the text included in the message is different, or the display mode (selectable mode / non-selectable mode) of the button included in the message is different. However, as an example, the terminal 20 of the party may be displayed with a detailed message, while the terminal 20 other than the party may be displayed with a simplified message. The message may be displayed in a different color.

In this modification, the remittance reminder message is displayed in a display mode (not limited, but not limited) of the remittance reminder message displayed in the group talk room displayed on the terminal 20 (not limited, but an example of the terminal) of the remittance request destination user. It is displayed in the group talk room displayed on the terminal 20 (not limited, but an example of the terminal of the second user) of other group users excluding the remittance request destination user and the remittance master user. The display mode is different from the display mode of the remittance reminder message (not limited, but an example of the second display mode).
As an example of the effect of the embodiment obtained by such a configuration, the difference in the display mode between the first display mode and the second display mode indicates to the terminal user that he / she is the party to the remittance request. The second user can be made aware that he / she is not the party to the remittance request.

<Fifth variant (5)>
Some features of the messaging application may or may not be restricted if the user making the remittance request does not make the payment.

In the example of FIG. 5-16, the message MS14 is displayed on the terminal 20 of the first user (AA) as the message of the official account of the payment application, and the user (BB) who is the target of the remittance reminder. The message MS24 is displayed on the terminal 20 of the above, and the message MS34 is displayed on the terminal 20 of the other user (CC).
At the beginning of each of the messages MS14, MS24, and MS34, the message is B.I. The notation "@ BB" is used to indicate that the message is for B (in this example, the user who is the target of the remittance reminder).

The messages MS14, MS24, and MS34 are not limited, but as an example, the characters [Payment App] and information indicating the functions and usage restriction conditions restricted in the messaging application (in this example, "24 hours"). If there is no remittance within the time limit, the stamp function in the Messaging App will be restricted. ”And“ Please remit within the deadline. ”) And the user of the first user who will be the remittance destination. The name (AA in this example), the remittance request amount ("3,000 yen" in this example), and the remittance deadline (2020-04-24 17:00 in this example) are displayed, and the remittance button is displayed at the bottom. Is displayed.

Both the remittance button BT14 of the message MS14 and the remittance button BT34 of the message MS34 are displayed in the non-selective mode, and the remittance button BT24 of the message MS24 is displayed in the selected mode.

<Fifth variant (6)>
The reminder display displayed on the terminal 20 of the user whose remittance has not been completed may or may not include information about the user whose remittance has already been completed.

In the example shown in FIG. 5-17, A. On the display unit 24 of the terminal 20 of A, messages exchanged between friends are displayed in the talk room of group X.

In this example, C.I. Although C responded that the remittance was sent, B. was a user of the other terminal 20. It shows that there is no response from B.
As an example, not a limitation, the first user, A. When A taps the button BTM3, A. A history of past remittance requests for multiple users (BB and CC) for which payment processing has not been completed for at least one user is available on the talk room. Is displayed in.

In this example, the first user (AA) sends remittance request information about a common event (in this example, an event with a membership fee of 3,000 yen) to a plurality of users (BB and CC). is doing. Then, based on the fact that the remittance process related to the remittance request to one user (BB) is incomplete and the remittance process related to the remittance request to the other user (CC) is completed, the remittance process is related to both users. The information is displayed in the area R10.

As an example, not a limitation, the area R10 indicates the transmission date and time of the remittance request information, the icon of the character "request transmission", and the position of receiving payment from each of a plurality of users (AA, BB). The icon of the character "receive" and the amount of money (3,000 yen) to be received from each of the plurality of users (AA, BB) are displayed.
Below that, information indicating the number of users who have been requested to remittance (“Member 2” in this example) is displayed, and further, information about one user (BB) who has not yet made the remittance. , Both information about the other user (CC) who has already sent money is displayed.

As an example, not a limitation, based on the fact that the first user (AA) has sent the remittance request information to one user (BB), but the remittance process for this remittance request has not been completed. The remittance request amount (3,000 yen in this example) is displayed in association with the icon image and the user name of one user (BB).
Further, as an example, not limited to, the first user (AA) sends the remittance request information to the other user (CC), and the remittance process for this remittance request is completed. Based on this, information indicating that the remittance has been completed (in this example, the characters "remittance completed") is displayed in association with the icon image and the user name of the other user (CC).

Further, the background of the information about one user (BB) is white, the background of the information about the other user (CC) is black, and the display mode differs between the former information and the latter information. It is easy to distinguish.
By setting the check box of the area R10 to be checked by the first user (AA), each information displayed in the area R10 is selected.
By tapping the area RR in this state, the remittance reminder information based on the information displayed in the area R10 is transmitted to the terminal 20 of the user (BB) who is not performing the remittance.

The example shown in FIG. 5-18 is different from the example shown in FIG. 5-2 in that the remittance reminder display based on the remittance reminder information also includes information about the other user (CC) who has already paid. It's different.

The message MS11c is displayed on the terminal 20 of the first user (AA), the message MS21c is displayed on the terminal 20 of one user (BB), and the terminal 20 of the other user (CC) is displayed. Message MS31c is displayed.
For all of the messages MS11c, MS21c, and MS31c, information indicating the number of users who have been the target of the remittance request based on the common event (“member 2” in this example) is displayed, and further, the remittance has not been performed yet. Both information about one user (BB) and information about the other user (CC) who has already sent money is displayed.

As an example, not a limitation, the other user (CC) who has already sent money for the same event to the remittance reminder display displayed on the terminal 20 of one user (BB) who has not yet sent money for a certain event. ) Can be included to encourage one user (BB) to remit.

5-19 and 5-20 are modifications of FIGS. 5-17 and 5-18.
With respect to FIGS. 5-19 and 5-20, as an example, not limited to, a plurality of users (BB, CC) to whom the remittance request information is transmitted are subject to remittance reminders, respectively. It differs from FIGS. 5-17 and 5-18 in that the number of times (as an example, not a limitation, the number of times the remittance reminder display for the user is displayed on the user's terminal 20) is shown.

In the examples of FIGS. 5-19 and 5-20, the number of times a remittance reminder is applied in association with the icon image and user name of one user (BB) who has not made a remittance in response to a remittance request for an event. The icon RIC1 indicating (as an example, not a limitation, the number of times the remittance reminder display for BB is displayed on the terminal 20 of BB, 10 times in this example) is displayed, and the same event is displayed. The number of times the remittance was reminded (not limited, but as an example, remittance targeting CC) in association with the icon image and user name of the other user (CC) who has already sent the remittance in response to the remittance request. The icon RIC2 indicating the number of times the reminder display is displayed on the terminal 20 of CC, which is 0 times in this example) is shown.

As an example, but not a limitation, such a display allows each user to compare the number of reminders with their other users and the number of reminders between other users, so it is subject to remittance reminders as much as possible. It is possible to make each user aware of this.

Next, an example of preventing the remittance reminding to the remittance request destination user will be described. Preventing remittance reminders is sometimes referred to as "stopping remittance reminders."
The methods for achieving this suspension of remittance reminders can be broadly divided into:
-The server 10 stops the transmission of the remittance reminder information.-The terminal 20 stops the display of the remittance reminder display. Hereinafter, each method will be described.

<Sixth Example>
The sixth embodiment is an embodiment in which the server 10 stops the transmission of the 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 the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

As a method for the server 10 to manage the remittance request, the above-mentioned two patterns (pattern A and pattern B) can be considered as an example without limitation.
When "Pattern A" is applied, the server 10 leaves the remittance request that has already been remitted without deleting it, and stops the transmission of the remittance reminder information corresponding to the remittance request to the terminal 20 of the remittance request destination user. do.
When applying "Pattern B", the server 10 deletes the remittance request that has already been remitted. Since the remittance request itself is deleted, as a result, the remittance reminder information transmission is stopped.

<Processing>
6-1 to 6-2 are flowcharts showing an example of the flow of processing executed by each device in this embodiment.
This flowchart is not limited, but is, as an example, a flowchart based on the server reminder processing following FIGS. 1-13 to 2-11.

If it is determined that the remittance reminder is to be performed (S260: YES), the control unit 11 of the server 10 determines whether or not the remittance request corresponding to the remittance reminder is stopped (S267). Specifically, as an example, not limited, the remittance is stopped when the second remittance request management data 157B is referred to and the remittance completed flag corresponding to the corresponding remittance request management ID is set to "ON". It is determined that it is.

If it is determined that the reminder has not been stopped (S267: NO), the control unit 11 of the server 10 shifts the processing to S270.
In this case, the server 10 is controlled to transmit the remittance reminder information to the terminal 20B.

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

In the above process, the remittance reminder information may be transmitted from the server 10 to the terminal 20B more than once. In this case, in the above process, when the remittance settlement process is executed by the server 10 based on the input for any of the remittance reminder displays displayed on the display unit 24 of the terminal 20B, the server 10 is subsequently transferred to the terminal 20. On the other hand, it will be controlled so that the remittance reminder information is not transmitted.

<Effect of the sixth embodiment>
In this embodiment, the server 10 remittance request information (an example of the first information regarding a payment request, not a limitation) by a remittance master user (an example of a first user, not a limitation) by a communication I / F14. Receive from the terminal 20 of. Then, the server 10 remittance information (not limited, but remittance) based on the remittance request based on the execution of the second remittance process (not limited, but an example of the remittance process related to the remittance to the first user) based on the remittance request. An example of a second information based on a request) is shown in a configuration in which the control unit 11 performs transmission control relating to control of transmitting the remittance request destination user to the terminal 20.
As an example of the effect of the embodiment obtained by such a configuration, transmission relating to control for transmitting the second information based on the remittance request to the terminal based on the execution of the remittance processing relating to the remittance to the first user based on the remittance request. By controlling the remittance to the first user, the user of the terminal can appropriately perform the remittance.

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

Further, in this embodiment, when the second remittance process is not executed, the server 10 controls to transmit the remittance reminder information to the terminal 20 of the remittance request destination user by the communication I / F14, and the second remittance process is executed. If this is the case, a configuration is shown in which control is performed so that the remittance reminder information is not transmitted to the terminal 20 of the remittance request destination user by the communication I / F14.
As an example of the effect of the embodiment obtained by such a configuration, if the remittance process is not executed, the second information is transmitted to the terminal, while if the remittance process is executed, the second information is transmitted. It can be prevented from being sent to the terminal.

Further, in this embodiment, in the second remittance process, the remittance request display (not limited, but an example of the first display based on the first information) is displayed on the terminal 20 of the remittance request destination user, and the user of the terminal 20 displays the remittance request display. It shows a configuration that is executed based on the input to the remittance request display.
As an example of the effect of the embodiment obtained by such a configuration, the first display based on the first information is displayed on the terminal, and the remittance process is easily executed based on the input to the first display by the user of the terminal. Can be done. Further, in this case, coupled with the above configuration, the server can be controlled not to transmit the second information to the terminal based on the fact that the remittance process is executed based on the input for the first display.

Further, in this embodiment, the server 10 transmits the remittance reminder information based on the remittance request (not limited, but an example of the third information based on the remittance request) to the terminal 20 of the remittance request destination user by the communication I / F14. .. Then, in the second remittance process, the remittance reminder display (not limited, but an example of the third display based on the third information) is displayed on the terminal 20 of the remittance request destination user, and the remittance request destination user inputs the remittance reminder display. Shows the configuration to be executed based on.
As an example of the effect of the embodiment obtained by such a configuration, the remittance process can be executed based on the input to the third display based on the third information. Further, in this case, in combination with the above configuration, when the remittance process is executed based on the input for the third display, the second information can be prevented from being transmitted to the terminal.

Further, in this embodiment, in the transmission control executed by the server 10, the first remittance reminder information (not limited, but an example of the second information) is transmitted to the terminal 20 of the remittance request destination user by the communication I / F 14 of the server 10. If so, the second remittance process includes the control of transmitting the second remittance reminder information (not limited, but an example of the fourth information based on the remittance request) to the terminal 20 of the remittance request destination user, and the second remittance process displays the first remittance reminder. (An example of a second display based on the second information, not a limitation) is displayed on the terminal 20 of the remittance request destination user, and the configuration is shown to be executed based on the input to the first remittance reminder display by the remittance request destination user. There is.
As an example of the effect of the embodiment obtained by such a configuration, even when the second information based on the remittance request is transmitted from the server to the terminal, the fourth information based on the remittance request is separated from the second information. Information can be sent from the server to the terminal. Further, even when the fourth information based on the remittance request is transmitted from the server to the terminal, the first user is based on the input by the terminal user to the second display based on the second information displayed on the terminal. It is possible to have the user of the terminal perform the remittance to.

Further, in this embodiment, the second remittance process (an example of the remittance process, not the limitation) is performed from the remittance request destination user (an example of the terminal user, not the limitation) to the remittance master user (not the limitation, the first user). An example) shows a configuration that is a process related to remittance to.
As an example of the effect of the embodiment obtained by such a configuration, the server can realize the remittance from the user of the terminal to the first user by the remittance process.

<Sixth variant (1)>
In the sixth embodiment, pattern B (delete the remittance request) can be applied.
In this case, the server 10 deletes the record corresponding to the remittance request management ID in the second remittance request management data 157B when the remittance is performed by the remittance settlement process, for example, without limitation. As a result, not only the remittance request but also the remittance reminder corresponding to this remittance request is deleted.

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

As an example, not a limitation, the control unit 11 of the server 10 transmits a remittance request list information page (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 sends a remittance request list page to the terminal 20B based on the remittance completed flag set in association with the corresponding remittance request management ID in the second remittance request management data 157B. And send.

Specifically, as an example, not limited, the remittance request information and the remittance reminder information in which the remittance completed flag is "OFF" are displayed by default, while the remittance request information and the remittance request information in which the remittance completed flag is "ON" are displayed. Regarding the remittance reminder information, the remittance request list page is set and sent with the display changed to the display mode indicating that the remittance has been completed (not limited, but as an example, a grayout display or a display with a remittance completed 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, the characters "DONE" are used as information indicating that the remittance has been completed for each of the remittance request information shown in the area R21 and the remittance reminder information shown in the area R22 in response to the remittance request. The completion mark MK1 including the completion mark MK1 is displayed.

The display indicating that the remittance has been completed is not limited to this.
As an example, not a limitation, on the remittance request list screen of the layout shown in FIG. 6-3, as shown in FIG. It may be distinguished from reminders.

Further, in the remittance request list screen different from the layout of FIG. 6-3, as an example instead of the limitation, in the remittance request list screen displayed based on the reception date and time as shown in FIG. 2-17, the remittance request list screen is not limited but as an example. As shown in FIG. 6-5, the completion mark MK1 may be displayed in the area R21 and the area R23.
Further, these areas may be grayed out.

<Sixth variant (3)>
As described above, it is also possible to stop the remittance reminder by the terminal 20 stopping the display of the remittance reminder display.
Here, the case of applying the terminal reminding method is illustrated.

FIG. 6-6 is a flowchart showing an example of the flow of processing executed by each device in this modification.
This flowchart is not limited, but is, as an example, a flowchart based on the processing of the terminal reminder of FIGS. 1-13 to 1-14.

If it is determined that the remittance is to be reminded (B145: YES), the control unit 21 of the terminal 20B determines whether or not the remittance based on the received 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 shifts the process to B150.
In this case, the control unit 21 of the terminal 20B executes control to display the remittance reminder display on the display unit 24.

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

In the above process, the remittance reminder display may be displayed twice or more on the display unit 24 of the terminal 20B.
In this case, in the above process, when the remittance is executed based on the input for any of the remittance reminder displays displayed on the display unit 24 of the terminal 20, the remittance reminder information is subsequently transmitted to the display unit 24 of the terminal 20B. It will be controlled so that it is not displayed in.

In this modification, the terminal 20 of the remittance request destination user communicates the remittance request information (not limited, but an example of the first information regarding the remittance request) by the remittance master user (not limited, but an example of the first user). Received by F22. Then, the terminal 20 of the remittance request destination user displays the remittance request display (not limited, but an example of the first display based on the first information) on the display unit 24. Then, the terminal 20 of the remittance request destination user displays the remittance reminding based on the remittance request based on the execution of the first remittance process (not limited to the example of the remittance process related to the remittance to the first user) based on the remittance request. The configuration is shown in which the control unit 21 performs display control relating to the control of displaying (an example of a second display based on a remittance request) on the display unit 24 without limitation.
As an example of the effect of the embodiment obtained by such a configuration, the second display based on the remittance request is displayed on the display unit of the terminal based on the execution of the remittance process related to the remittance to the first user based on the remittance request. By executing the display control related to the control, the remittance to the first user can be appropriately performed by the user of the terminal.

Further, in this modification, the above display control controls to display the remittance reminder display on the display unit 24 when the first remittance process is not executed, and displays the remittance reminder display when the first remittance process is not executed. A configuration is shown in which control that is not displayed on the unit 24 is performed.
As an example of the effect of the 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 the remittance process is executed.

Further, in this modification, in the first remittance processing, the display (not limited, but an example of the first display) based on the remittance request information (not limited, but an example of the first information) is displayed on the terminal 20 of the remittance request destination user. It shows a configuration that is displayed and executed based on the input to the display by the remittance request destination user (not limited, but an example of the input to the first display by the terminal user).
As an example of the effect of the modification obtained by such a configuration, the first display based on the first information is displayed on the terminal, and the remittance process is easily executed based on the input to the first display by the user of the terminal. Can be done. Further, in this case, coupled 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 is executed based on the input for the first display.

<Sixth variant (4)>
Although related to the sixth modification (3), regarding the server reminder method, it is also possible to stop the remittance reminder by stopping the display of the remittance reminder display by the terminal 20. That is, the server 10 does not stop the transmission of the remittance reminder information, but the terminal 20 can stop the display of the remittance reminder display.

FIG. 6-7 is a flowchart showing an example of the flow of processing executed by each device in this modification.
If it is determined in B240 that the remittance remind information has been received from the server 10 (B240: YES), the control unit 21 of the terminal 20B determines whether or not the 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 shifts the process to B250.
In this case, the remittance reminder information is transmitted from the server 10, and the control unit 21 of the terminal 20B executes control to display the remittance reminder display based on the remittance reminder information on the display unit 24.

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

<Sixth variant (5)>
Further, it is also possible to make the server 10 stop the transmission of the remittance reminder information based on the request from the terminal 20 of the remittance request destination user.
Specifically, as shown in FIG. 6-8, as an example, not a limitation, the user B. who is the remittance request destination user. With the remittance request list displayed on the display unit 24 of the terminal 20B of B, the user A. When you tap the remittance reminder from A, the remittance screen as shown in FIG. 6-9 is displayed.

At the bottom of the remittance screen, a confirmation information display area WR1 is configured to notify the server 10 that the content of the remittance reminder has been confirmed. In this example, in the confirmation information display area WR1, a link including the characters "confirmed" is displayed together with the text "[Remind] A.A. remittance request". Then, by tapping this link, the remittance reminder confirmation information indicating that the content of the remittance reminder has been confirmed is transmitted from the terminal 20B to the server 10.
The server 10 stops the transmission of the remittance reminder information based on the reception of the remittance reminder confirmation information from the terminal 20B.

<7th Example>
The seventh embodiment is an embodiment in which the remittance request display and the 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 the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

<Processing>
7-1 to 7-2 are flowcharts showing an example of the flow of processing executed by each device in this embodiment.
Here, for the sake of simplicity, the process will be illustrated and described as a process focusing on the case where the added message is displayed in the talk room displayed on the terminal 20B, and the display of the talk room on the terminal 20A will be omitted.

When the remittance request transmission request information is received from the terminal 20A by the communication I / F 14, the control unit 11 of the server 10 sends the remittance request message to the user A. A and user B. It is added to and updated in the talk management data (talk room) with B (S610).
Then, the control unit 11 of the server 10 transmits the added remittance request message to the terminal 20B by the communication I / F14 (S620).

The control unit 21 of the terminal 20B determines whether or not the remittance request message has been received from the server 10 by the communication I / F 22 (B610), and if it is determined that the remittance request message has been received (B610: YES), executes the request notification process. (B620).
This request notification process is not limited, but can be realized by the same method as the above-mentioned remind notification process as an example.

After that, the control unit 21 of the terminal 20B determines whether or not to display the talk room on the display unit 24 based on whether or not an input for displaying the talk room is made to the input unit (B630). .. Then, if it is determined to be displayed (B630: YES), the talk room is displayed on the display unit 24 based on the latest talk data stored in the storage unit 28 (B640).

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

If the remittance completed flag is "OFF" and it is determined that the remittance has not been stopped (S660: NO), the control unit 11 of the server 10 sends the remittance remind message to the user A. A and user B. It is added to and updated in the talk management data (talk room) with B (S670).
Then, the control unit 11 of the server 10 transmits the added remittance reminder message to the terminal 20B by the communication I / F 14 (S680).

After that, the control unit 11 of the server 10 determines whether or not to end the processing (S690), and if it is determined to continue the processing (S690: NO), returns the processing to S650. On the other hand, if it is determined to end the process (S690: YES), the process ends.

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

After that, the control unit 21 of the terminal 20B determines whether or not to display the talk room on the display unit 24 based on whether or not an input for displaying the talk room is made to the input unit (B670). .. Then, if it is determined to be displayed (B670: YES), the talk room is displayed on the display unit 24 based on the latest talk data stored in the storage unit 28 (B680).

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

<Effect of the 7th Example>
In this embodiment, the remittance request display (not limited, but an example of the first display based on the first information) on the terminal 20 is the remittance request destination user (not limited, but an example of the terminal user) and the remittance master user (limited). Instead, it shows a configuration that is displayed in a talk room (not a limitation, but an example of a chat room) including at least an example of a first user).
As an example of the effect of the embodiment obtained by such a configuration, the first information can be easily and appropriately notified to at least the terminal user and the first user by the display in the chat room.

<7th modification>
Similar to the sixth modification (1), when the above-mentioned pattern A is applied, the information regarding the remittance request that has been remitted may be changed to a display mode different from the information regarding the remittance request that has not been remitted. It may or may not be.

Depending on the messaging application, the server 10 and the terminal 20 may store the talk information independently.
As an example, not a limitation, the message stored on the server 10 is automatically deleted after a certain period of time (not a limitation, for example, several weeks) has passed since the message was sent to the terminal 20, but the message is automatically deleted on the terminal 20. The saved message is like remaining untouched unless the user deletes it.

In this case, since the message history is basically not deleted on the terminal 20, the user of the terminal 20 can view the past remittance request message and the remittance remind message based on the data stored in the terminal 20. It becomes.
Therefore, in this modification, the display mode of the information related to the remittance request is changed by the following method.

FIG. 7-3 is a diagram showing an example of a table for explaining this method.
In this table, as an example, not a limitation, a remittance completed flag, an information type, and a message are defined in association with each other.

The remittance completed flag includes "OFF" and "ON".

The information type is the type of the message, and is not limited, but as an example, "request" and "remind" are defined for each of the remittance flag "OFF" and "ON".

In the message, the type of the message to be displayed in the talk room of the terminal 20 is defined according to the corresponding remittance flag "ON" / "OFF".

This will be described in detail.
(1) Remittance completed flag "OFF"
In the information type "request", "type 1 remittance request message (unremitted)" is defined as a message. This indicates that the remittance request message displayed in the talk room is the first-class remittance request message when the remittance completed flag is "OFF", that is, when the remittance has not been performed.

In the information type "Remind", "Type 1 remittance remittance message (unremitted)" is defined as a message. This indicates that when the remittance completed flag is "OFF", that is, when the remittance has not been remitted, the remittance remind message displayed in the talk room is the first-class remittance remind message.

(2) Remittance completed flag "ON"
In the information type "request", "type 2 remittance request message (remittance completed)" is defined as a message. This indicates that when the remittance completed flag is "ON", that is, when the remittance has been completed, the remittance request message displayed in the talk room is the second type remittance request message.

In the information type "Remind", "Type 2 remittance remittance message (remittance completed)" is defined as a message. This indicates that when the remittance completed flag is "ON", that is, when the remittance has been completed, the remittance remind message displayed in the talk room is the second type remittance remind message.

That is, in the unremitted state, the remittance request message and the remittance remind message are displayed in the first display mode (not limited, but as an example, the default display mode), but after the remittance is completed, these messages are displayed. Is changed from the first display mode to the second display mode (not limited to, as an example, a display mode indicating that remittance has been completed).

7-4 to 7-5 are flowcharts showing an example of the flow of processing executed by each apparatus in this embodiment.

Upon receiving the remittance request transmission request information from the terminal 20A by the communication I / F 14, the control unit 11 of the server 10 sends the first-class remittance request message as the remittance request message to the user A. A and user B. It is added to and updated in the talk management data (talk room) with B (S710).

After that, the control unit 11 of the server 10 transmits the first-class remittance request message and the second-class remittance request message to the terminal 20B by the communication I / F14 as the remittance request message (S720).

After B620, the control unit 21 of the terminal 20B stores the received remittance request message (type 1 and type 2) in the storage unit 28 (B725).

After that, the control unit 21 of the terminal 20B determines whether or not to display the talk room on the display unit 24 based on whether or not an input for displaying the talk room is made to the input unit (B730). .. Then, if it is determined to be displayed (B730: YES), the talk room is displayed on the display unit 24 based on the latest talk data (B740).
Specifically, as a remittance request message, a first-class remittance request message is displayed in the talk room.

If it is determined in S660 that the remittance has not been stopped (S660: NO), the control unit 11 of the server 10 sends the first-class remittance remind message as the remittance remind message to the user A. A and user B. It is added to and updated in the talk management data (talk room) with B (S770).

After that, the control unit 11 of the server 10 transmits, as the remittance reminder message, the first-class remittance reminder message and the second-class remittance reminder message to the terminal 20B by the communication I / F14 (S780).

After B660, the control unit 21 of the terminal 20B stores the received remittance reminder messages (types 1 and 2) in the storage unit 28 (B765).

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

Specifically, as an example, not limited, if the remittance information has not been received from the server 10 among the messages in the talk room, the first type remittance request is used as the corresponding remittance request message / remittance remind message. Message ・ Display a first-class remittance reminder message.
On the other hand, when the remittance information has been received from the server 10, the second type remittance request message and the second type remittance remind message are displayed as the corresponding remittance request message / remittance remind message.

<Eighth Example>
The eighth embodiment is an embodiment relating to the case where the remittance is executed without going through the remittance request or the remittance reminder.

In some cases, the remittance request destination user confirms the remittance request display and the remittance remind display, or without confirming these, using the independent remittance function in the payment application to transfer the remittance to the remittance master user. is assumed.
In such a case, the server 10 cannot determine (specify) which remittance request management ID should stop the remittance reminder.

The contents described in the eighth embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

FIG. 8-1 is a diagram showing a configuration example of the third remittance request management data 157C, which is another example of the above-mentioned remittance request management data 157 stored in the storage unit 15 of the server 10.
The third remittance request management data 157C includes the date and time, the remittance request management ID, the remittance master ID, the remittance request destination ID, the remittance request amount, the remittance flag, and the information in the second remittance request management data 157B. In addition to the type, the remind stop flag is associated and stored as an example, not a limitation.

The remittance stop flag is a flag for identifying whether or not to stop the transmission of the remittance remind information to the terminal 20 of the remittance request destination user for the corresponding remittance request management ID, and stops the transmission of the remittance remind information. For things, "ON" is set.

The difference from the above-described embodiment is that the remittance stop flag may be set to "ON" even if the remittance completed flag is "OFF".

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

The target terminal defines whether the server 10 determines the remittance reminder to be stopped based on the information selected and input by which terminal 20.

The determination information defines information for the server 10 to determine the remittance reminder to be stopped.

The determination result defines the result that the server 10 determines as a remittance reminder to stop.

This will be described in detail.
In the setting No. "S1", the "terminal of the remittance request destination user" is set as the target terminal, the "selected remittance master user" is set as the judgment information, and the "remittance remind from the selected remittance master user" is set as the judgment result. Are defined respectively.
This is a user (remittance master user) who receives a remittance request as an example, not a limitation, on the screen displayed on the display unit 24 of the terminal 20 of the remittance request destination user (not limited but as an example, a remittance screen). Select one of the remittance master users by displaying a list of. Then, it is shown that the remittance reminder from the selected remittance master user is stopped based on the selection of the remittance master user.

When this setting is applied, the server 10 regards the remittance from the remittance request destination user as the remittance based on the remittance request from the selected remittance master user to the remittance request destination user, and executes the remittance. Then, the server 10 stops the remittance reminding from the remittance master user to the remittance request destination user.
Specifically, the server 10 corresponds to the remittance request management ID of all the remittance requests from the selected remittance master user to the remittance request destination user in the third remittance request management data 157C, as an example, not limited to. Set the reminder stop flag to "ON".
However, with this setting, the remittance request cannot be uniquely specified, so the remittance completed flag can be left as "OFF".

In the setting No. "S2", "the terminal of the remittance request destination user" is set as the target terminal, "selected remittance destination user & remittance reminder stop selection" is set as the judgment information, and "selected remittance is selected" as the judgment result. "Remittance reminders from destination users" are defined respectively.
This is not a limitation, but as an example, on the screen displayed on the display unit 24 of the terminal 20 of the remittance request destination user (as an example, not the limitation, the remittance screen), the remittance destination user (hereinafter,, the user of the remittance destination) by the remittance request destination user. Remittance reminders from the selected remittance user are stopped based on the selection of "Remittance destination user") and the selection to stop the remittance reminders from that remittance destination user. Shows.

When applying this setting, the server 10 determines whether or not there is a remittance request from the selected remittance destination user to the remittance request destination user. Then, if it is determined that it exists, the remittance from the remittance request destination user is regarded as the remittance based on the remittance request from the selected remittance destination user to the remittance request destination user, and the remittance is executed. Then, when it is selected to stop the remittance reminder, the server 10 stops the remittance reminder from the remittance destination user to the remittance request destination user.
Specifically, the server 10 corresponds to, as an example, not limited to, the remittance request management ID of all the remittance requests from the selected remittance destination user to the remittance request destination user in the third remittance request management data 157C. Set the reminder stop flag to "ON".
However, even with this setting, the remittance request cannot be uniquely specified, so the remittance completed flag can be left as "OFF".

If it is not selected to stop the remittance reminder, the server 10 does not stop the remittance reminder. The same applies hereinafter.

In the setting No. "S3", "the terminal of the remittance request destination user" is set as the target terminal, "selected remittance destination user & input remittance amount" is set as the judgment information, and "selected remittance destination" is set as the judgment result. Remittance reminders from users & remittance reminders with the same remittance amount entered and remittance request amount are defined respectively.
This is not a limitation, but as an example, the remittance destination user is selected by the remittance request destination user on the screen displayed on the display unit 24 of the terminal 20 of the remittance request destination user (as an example, not the limitation, the remittance screen). Indicates that the remittance reminder from the selected remittance user based on the remittance amount entered for that remittance user, with the same remittance amount entered and the remittance request amount, will be stopped. ing.

When this setting is applied, the server 10 is not limited to, but as an example, in the third remittance request management data 157C, the remittance request amount is selected from the remittance request management IDs from the selected remittance destination user to the remittance request destination user. , The remittance request management ID, which is the same as the remittance amount input on the terminal 20 of the remittance request destination user, is specified.
Then, the server 10 regards the remittance from the remittance request destination user as the remittance based on the remittance request of the specified remittance request management ID, and executes the remittance. Then, the server 10 stops the remittance reminder for the remittance request of the remittance request management ID. Specifically, the server 10 is not limited to, but as an example, in the third remittance request management data 157C, the remittance completed flag corresponding to the specified remittance request management ID is set to "ON", and the remind stop flag is also "ON". Set to "ON".

Note that instead of stopping the remittance reminder that the entered remittance amount and the remittance request amount are the same, or in addition to this, the remittance reminder that the entered remittance amount and the remittance request amount are close to each other (as an example, not limited) Remittance reminders whose difference is "300 yen or less" may or may not be stopped.

In the setting No. "S4", the "terminal of the remittance request destination user" is set as the target terminal, the "selected remittance request in the group" is set as the judgment information, and the "selected remittance request in the group" is set as the judgment result. Corresponding remittance reminders are set for each.
This is not a limitation, but as an example, on the screen displayed on the display unit 24 of the terminal 20 of the remittance request destination user (as an example, not a limitation, the group request list screen), the remittance request destination user makes a remittance request to himself / herself. In addition, it indicates that when remittance requests to other group users are selected together, the remittance reminders corresponding to those remittance requests will be stopped.

When this setting is applied, the server 10 regards the remittance from the remittance request destination user as the remittance based on the selected remittance request in the group and executes the remittance. Then, the server 10 stops the remittance reminder corresponding to the remittance request to the remittance request destination user and the remittance reminder corresponding to the remittance request to the other selected group users.
Specifically, the server 10 is not limited, but as an example, in the third remittance request management data 157C, the remittance completed flag corresponding to the remittance request management ID of these remittance requests is set to "ON" and the remittance is stopped. The flag is also set to "ON".

In this setting, as an example, not limited to, one remittance requesting user in a group can remit the amount that he / she should remit, as well as the amount that other group users in the same group should remit. By doing so, it is possible to stop the remittance reminding to oneself and the remittance reminding to other group users included in the same group.

In each of the above settings, the selection of whether to stop the remittance reminder (whether or not the remittance reminder is selected or not) is an essential element, and when it is selected to stop the remittance reminder, the remittance reminder is stopped. It may or may not be done.

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

8-3 to 8-7 show an example of the transition of the screen diagram when the setting of the setting No. “S2” is applied.
FIG. 8-3 is a main menu screen of the payment application displayed on the display unit 24 of the terminal 20B, and is a screen corresponding to FIG. 2-2. And here, the state where the icon IC3 of "remittance" is tapped is shown. In this case, the remittance destination user selection screen shown in FIG. 8-4 is displayed as an example, not a limitation.

This remittance destination user selection screen is a screen for selecting a remittance destination user. There is a column. Then, in this example, a field for searching for candidates for the remittance destination user is selected from the payment application ID, and the search results are "AA", "CC", "DD", and "EE". A state in which a plurality of users such as "" is displayed is shown. Then, in this example, the check box next to "AA" is checked, so that the user A. The state in which A is selected as the remittance destination user is shown.

In this state, the selection area RM3 at the bottom of the screen is tapped, and after the remittance schedule amount is input on the amount input screen (not shown), the screen shown in FIG. 8-5 is displayed as an example, not limited.
On this screen, "3,000 yen" is entered as the remittance scheduled amount, and by tapping the remittance area RM2 at the bottom of the screen in this state, as shown in FIG. 8-6, as remittance remind stop information. As an example, not a limitation, User A. The remittance reminder stop information RS1 including the icon image and user name of A, the text "Do you want to stop the reminder from this user?", The OK button BT10, and the cancel button is popped up in the center of the screen. To.

When the OK button BT10 included in the remittance reminder stop information RS1 is tapped in this state, the remittance destination user selection information (information indicating that user AA has been selected) and the remittance reminder stop request information are displayed on the terminal. It is transmitted from 20B to the server 10. Then, the remittance is executed by the server 10, and the remittance is reminded. Then, as an example, not limited to, as shown in FIG. 8-7, a remittance completion notification including the fact that the remittance has been completed and the remittance reminding has been stopped is popped up in the center of the screen.

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

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

In this remittance item selection area SMR, in addition to the button BTM1 for sending remittance to another user, the button BTM2 for sending remittance request information to other users, and the button BTM3 for displaying the remittance request list. The button BTM4 for displaying the group request list is displayed.

When the button BTM4 is tapped, a list of group requests is displayed on the screen as an example, not a limitation. In this example, as a group request, the user A. who sets the remittance request amount to "3,000 yen". From A to user B. Remittance request to B (remittance from user BB to user A.A) and user A. with the remittance request amount as "3,000 yen". From A to user C. A remittance request for two people, a remittance request to C (a remittance from user CC to user AA), is displayed.

The check boxes associated with each of the above two remittance requests are checked, and the remittance area RM2 at the bottom of the screen is tapped to send the remittance request selection information from the terminal 20C to the server 10. .. Then, the server 10 executes the remittance based on the above two remittance requests, and stops the remittance reminders corresponding to each.

FIG. 8-9 shows the user A. who is the remittance master user. Terminal 20A of A and user B. who is a remittance request destination user. The terminal 20B of B and the user C. who is also the remittance request destination user. The group talk room displayed on each display unit 24 with the terminal 20C of C is shown.
In the group talk room displayed on the terminal 20A, the user C.I. From C to user A. A message MS71 indicating that two people have been remitted to A is displayed, and below that, the amount is displayed by the user A. A message M72 indicating that A has received is displayed.

In the group talk room displayed on the terminal 20B, the user C.I. From C to user A. Corresponding to the message MS81 and the message MS72 indicating that the remittance for two people was sent to A, the amount of money was set by the user A. In addition to the message MS82 indicating that A has received, the user A. From A to user B. A message M83 indicating that the remittance reminder to B has been stopped is displayed.

Further, in the group talk room displayed on the terminal 20C, the user C.I. From C to user A. Corresponding to the message MS91 and the message MS72 indicating that the remittance for two people has been sent to A, the amount of money is set to the user A. The message MS92 indicating that A has received is displayed.

In this case, User A. From A to user B. In addition to remittance reminders to B, User A. From A to user C. Remittance reminders to C will also be stopped. However, knowing that the remittance reminder to himself will be stopped, User C. C is user B. In this example, the group talk room displayed on the terminal 20C is the user A. From A to user C. The message indicating that the remittance reminder to C has been stopped is not displayed.

In addition, unlike this, in the group talk room displayed on the terminal 20C, the user A. From A to user C. A message indicating that the remittance reminder to C has been stopped may be displayed.

<Processing>
FIG. 8-10 is a flowchart showing an example of the flow of processing executed by each device in this embodiment.
Here, the processing of the terminal 20B is shown on the left side, the processing of the server 10 is shown on the right side, and the processing of the terminal 20A is not shown.
These processes are not limited, but as an example, are processes executed by the control unit 21 of the terminal 20B and the control unit 11 of the server 10 as the processing of the subroutines of the processes of FIGS. 6-1 to 6-2, respectively.

The control unit 21 of the terminal 20B determines whether or not to execute the remittance (B810). Specifically, as an example, not limited, it is determined whether or not an input for executing remittance has been made to the input unit from the above-mentioned remittance screen, the above-mentioned group request list screen, or the like.

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

The control unit 11 of the server 10 determines whether or not the remittance settlement request information has been received from the terminal 20B by the communication I / F 14 (S810), and if it is determined that the remittance settlement request information has been received (S810: YES), the received remittance settlement. It is determined whether or not the request information includes the 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 the remittance reminder stop determination process (S830).
Specifically, as an example, not a limitation, the remittance request management ID for stopping the remittance reminder is determined (specified) according to the method described in the table of FIG. 8-2.

After that, the control unit 11 of the server 10 executes the remittance settlement process (S130). Specifically, as an example, the remittance is performed for the remittance request associated with the determined remittance request management ID. Then, the flag (remittance completed flag, remind stop flag) is set by the above-mentioned method.

After B140, the control unit 21 of the terminal 20B determines whether or not to end the processing (B890), and if it is determined to continue the processing (B890: NO), returns the processing to B810.
On the other hand, if it is determined to end the process (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 processing (S890), and if it is determined to continue the processing (S890: NO), returns the processing to S810.
On the other hand, if it is determined to end the process (S890: YES), the control unit 11 of the server 10 ends the process.

Further, in this process, in S267 of FIG. 6-2, the control unit 11 of the server 10 determines whether or not the remittance request management ID corresponding to the remittance remind information received the transmission request has been reminded. .. Specifically, as an example, not limited, when the third remittance request management data 157C is referred to and the request stop flag corresponding to the remittance request management ID is set to "ON", the reminding is stopped. It is determined that there is.

<Effect of the eighth embodiment>
In this embodiment, the second remittance process (not limited, but an example of remittance process) executed by the server 10 is a remittance master user (not limited, but an example) displayed on the display unit 24 of the terminal 20 of the remittance request destination user. An example of a first user) shows a configuration executed based on the selection.
As an example of the effect of the embodiment obtained by such a configuration, based on the fact that the first user displayed on the display unit of the terminal is selected, it is regarded as a remittance based on the remittance request from the first user. The remittance process can be executed.

Further, in this embodiment, in the second remittance process, the remittance request destination user (not limited, but an example of a terminal user) selects a remittance master user (not limited, but an example of a first user) and remittance reminders. It shows a configuration to be executed based on the selection of stop (not limited, but information indicating that the second information is not transmitted).
As an example of the effect of the embodiment obtained by such a configuration, the remittance process is appropriate based on the selection of the first user and the selection of information indicating that the second information is not transmitted by the user of the terminal. Can be run on.

Further, in this embodiment, in the second remittance processing, the remittance master user (not limited, but an example of the first user), the remittance request amount (not limited, an example of the amount based on the remittance request), and the planned remittance amount. (Not limited, but an example of the amount of money entered by the user of the terminal) and the configuration to be executed is shown.
As an example of the effect of the embodiment obtained by such a configuration, the remittance process is appropriately executed based on the selection of the first user, the amount based on the remittance request, and the amount input by the user of the terminal. Can be done.

Further, in the above embodiment, in the above, the second remittance process is a remittance master by a group user (an example of a second user, not a limitation) different from the remittance request destination user (an example of a terminal user, not a limitation). It shows a configuration executed based on a remittance to a user (not a limitation, but an example of a first user).
As an example of the effect of the embodiment obtained by such a configuration, the remittance process is appropriately executed based on the remittance to the first user by the second user different from the user of the terminal requested to remit. be able to.

In this case, the remittance request information includes the remittance request destination user (not limited, but an example of a terminal user), the remittance master user (not limited, an example of a first user), and other group users (not limited, but an example of a first user). It is transmitted to a group including at least (an example of a second user), and the second remittance process is for a remittance request display based on the remittance request information displayed on the terminal 20 of the group user by another group user. It can also be executed based on the input.
As an example of the effect of the embodiment obtained by such a configuration, the remittance process is simple and appropriate based on the input by the second user to the first display based on the first information displayed on the terminal of the second user. Can be executed.

Further, in this embodiment, information such as an icon image of a remittance master user and a user name (not limited, but an example of first user information) is displayed on the display unit 24 of the terminal 20, and the first remittance process is a remittance request. It shows a configuration executed based on the input to the first user information displayed on the display unit 24 by the destination user (not limited, but an example of a terminal user).
As an example of the effect of the embodiment obtained by such a configuration, the remittance process is executed based on the input for the display that is easy for the user, that is, the input for the first user information displayed on the display unit by the user of the terminal. Can be done.

Further, in this embodiment, the terminal 20 uses the input to the terminal 20 to select the remittance destination user (not limited to the information indicating that the first user has been selected) and the information on the planned remittance amount (information indicating that the first user has been selected). It is not a limitation, but an example of the amount information to be remitted to the first user) and is acquired. The first remittance process shows a configuration to be executed based on the information of the remittance request amount (remittance request amount) and the information of the remittance scheduled amount.
As an example of the effect of the embodiment obtained by such a configuration, when the amount based on the remittance request and the amount to be remitted to the user are the same amount, the remittance request from the user is not limited. It can be regarded as a remittance based on the above, and the remittance can be made.

Further, in this embodiment, the first remittance process is an input for selecting a remittance master user for the terminal 20 by the remittance request destination user and an input for stopping the remittance reminder (not limited, but based on the remittance request). An example of an input indicating that the remittance is to the first user) is shown.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to easily and appropriately execute the remittance process based on the input indicating that the remittance is to the first user based on the remittance request. can.

<8th modification>
In the eighth embodiment, whether or not the server 10 stops the transmission of the remittance reminder information is managed by the reminder stop flag of the remittance request management data 157, but the present invention is not limited to this.
As an example, but not a limitation, it may or may not be possible to manage whether or not to stop the transmission of remittance reminder information by data different from the remittance request management data.

FIG. 8-11 is a diagram showing an example of remind stop management data stored in the storage unit 15 of the server 10 in this modification.
The remittance stop management data is not limited, but as an example, the application ID of the user who receives the remittance remind information vertically (reception side) and the application of the user who sends the remittance remind information horizontally (sender). Each ID is stored, and whether or not the remittance reminder information is transmitted from the transmitting side to the receiving side (with / without transmission) is stored in a matrix format.

By default, "with transmission" is stored in all fields where the transmitting side and the receiving side intersect, but when the remittance reminder information transmission is stopped in the remittance reminder stop determination process (S830) of FIG. 8-10. For the determined items, the column where the transmitting side and the receiving side intersect is updated to "No transmission".
As an example, but not a limitation, the remittance master user is referred to as User A. Let A be the user B. the remittance request destination user. Let B be the user A. From A to user B. When it is determined to stop the remittance reminding to B, the column where the transmitting side "U001 (user A.A)" and the receiving side "U002 (user BB)" intersect is updated to "no transmission". Will be done.

<9th Example>
The ninth embodiment is an embodiment in which the remittance reminder is stopped in an exceptional case different from the above-mentioned embodiment.
The contents described in the ninth embodiment can be applied to any of the other embodiments and the other modifications.
Further, the same components as those already mentioned are designated by the same reference numerals, and the description thereof will be omitted again.

The following cases can be considered as cases where it becomes necessary to stop remittance reminders.
(A) Remittance based on the remittance request has not been made yet, but it is desired to stop the remittance reminder (B) The amount corresponding to the remittance request is paid without using the payment application, etc. Cases where you want to stop remittance reminders

(A) is not a limitation, but as an example, it is in a state of unremittance, but in order to prevent remittance reminders, it is mainly a user of the party (however, it may be a user other than the party). This is the case when it is desired to stop the remittance reminder.
There may also be cases where the remittance master user abandons the remittance request.

(B) is not a limitation, but is, for example, a case where money is paid by handing cash, fund transfer of a financial institution (bank, etc.), or the like. In this case as well, it is considered desirable to stop the remittance reminding mainly by the users of the parties concerned.

FIG. 9-1 is a diagram showing an example of a table for explaining a method for stopping the transmission of remittance reminder information in this embodiment.
In this table, as an example, not limited to the setting No., the target terminal, the determination information, the determination result, and the approval necessity of the remittance master user are defined in association with each other.

The meanings of the target terminal, the determination information, and the determination result are the same as those in the table of FIG. 8-2.

The remittance master user's approval requirement includes information (approval required / approval not required) for identifying whether or not approval by the remittance master user is required to stop the remittance reminder.

This will be described in detail.
In the setting No. "T1", "the terminal of the remittance master user" is set as the target terminal, and "the selected remittance request destination user & whether or not the remittance reminder is stopped or not selected" is set as the judgment result. "Remittance reminding to the request destination user" is defined as "No" as the approval requirement of the remittance master user.
This is not limited, but as an example, on the screen displayed on the display unit 24 of the terminal 20 of the remittance master user (as an example, not limited, the remittance request destination user list screen), the remittance request destination user selects the remittance request destination user. It indicates that the remittance reminder to the selected remittance request destination user will be stopped based on the fact that the remittance reminder is selected to be stopped.
In addition, in order to stop the remittance reminding at the request of the remittance master user, "No" is set as the approval requirement of the remittance master user.

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, the server 10 corresponds to, as an example, not limited to, the remittance request management ID of all the remittance requests from the remittance master user to the selected remittance request destination user in the third remittance request management data 157C. Set the reminder stop flag to "ON".

In the setting No. "T2", "the terminal of the remittance master user" is set as the target terminal, and "whether or not the selected remittance request & remittance reminder stop is selected" is set as the judgment result "as the selected remittance request". "Corresponding remittance reminders" are defined as "No" as the approval requirement of the remittance master user.
This is not a limitation, but as an example, the remittance request is selected by the remittance master user on the screen displayed on the display unit 24 of the terminal 20 of the remittance master user (as an example, not the limitation, the remittance request list screen), and the remittance reminds. Indicates that the remittance reminder corresponding to the selected remittance request will be suspended based on the choice to suspend.
In addition, in order to stop the remittance reminding at the request of the remittance master user, "No" is set as the approval requirement of the remittance master user.

When applying this setting, the server 10 stops the remittance reminder corresponding to the selected remittance request. Specifically, the server 10 sets, as an example, not limited to, the remittance stop flag corresponding to the remittance request management ID of the selected remittance request in the third remittance request management data 157C to "ON".

However, in this setting, although the remittance request management ID can be uniquely specified, it is not possible to specify whether or not the remittance based on the remittance request has been executed. Therefore, the remittance completed flag remains "OFF".
Therefore, if the remittance has been completed, the remittance completed flag may be set to "ON" by the server 10 by transmitting the remittance completed information from the terminal 20 of the remittance master user to the server 10.

In the setting No. "T3", "the terminal of the remittance request destination user" is set as the target terminal, "whether or not the remittance master user & remittance remind stop is selected" as the judgment information, and "from the selected remittance master user" as the judgment result. "Remittance reminders" are defined as "required" as the approval or disapproval of the remittance master user.
This is not limited, but as an example, on the screen displayed on the display unit 24 of the terminal 20 of the remittance request destination user (as an example, not limited, the remittance master user list screen), the remittance master user selects by the remittance request destination user. Indicates that the remittance reminder from the selected remittance master user will be stopped based on the choice to stop the remittance reminder.
In addition, in order to stop the remittance reminding at the request of the remittance request destination user, "required" is defined as the approval requirement of the remittance master user.

When this setting is applied, the server 10 confirms whether or not to approve the stop of the remittance reminder for the terminal 20 of the selected remittance master user (hereinafter referred to as "approval confirmation process"). To execute. Specifically, the server 10 transmits information for confirming whether or not to approve the suspension of the remittance reminder (hereinafter referred to as "approval confirmation information") to the terminal 20 of the selected remittance master user. do.
Upon receiving the information indicating approval (hereinafter referred to as "approval information") from the terminal 20 of the remittance master user, the server 10 stops the remittance reminding from the remittance master user to the remittance request destination user. Specifically, in the third remittance request management data 157C, a remittance stop flag corresponding to the remittance request management ID of all remittance requests from the remittance master user identified by the received application ID to the remittance request destination user is set. Set to "ON".
On the other hand, if the approval information is not received from the terminal 20 of the remittance master user, the server 10 does not stop the remittance reminder. That is, the reminder stop flag is left as "OFF".

In the setting No. "T4", "the terminal of the remittance request destination user" is set as the target terminal, and "selected remittance request & remittance reminder stop selection" is set as the judgment result. The "corresponding remittance reminder" is defined as "required" as the approval requirement of the remittance master user.
This is not a limitation, but as an example, the remittance request is selected by the remittance request destination user on the screen displayed on the display unit 24 of the terminal 20 of the remittance request destination user (as an example, not the limitation, the remittance request list screen). Indicates that the remittance reminder corresponding to the selected remittance request will be suspended based on the choice to suspend the remittance reminder.
In addition, in order to stop the remittance reminding at the request of the remittance request destination user, "required" is defined as the approval requirement of the remittance master user.

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

However, in this setting, although the remittance request management ID can be uniquely specified, it is not possible to specify whether or not the remittance based on the remittance request has been executed. Therefore, the remittance completed flag remains "OFF".
Therefore, if the remittance has been completed, the remittance completed flag may be set to "ON" by the server 10 by transmitting the remittance completed information from the terminal 20 of the remittance request destination user to the server 10. ..

In the setting No. "T5", "terminal of a user other than the party" is selected as the target terminal, and "whether or not the selected party's remittance request & remittance reminder stop selection is selected" is selected as the determination result. "Remittance reminders corresponding to the remittance requests of the parties" are defined as "required" as the approval or disapproval of the remittance master user.
This is displayed on the display unit 24 of the terminal 20 of a user other than the party to the remittance (as an example, not a limitation, a user other than the remittance master user and the remittance request destination user included in the same group) as an example, not the limitation. On the screen (as an example, not a limitation, the group request list screen), the remittance request of the selected party is based on the user selecting the remittance request of the party and choosing to stop the remittance reminder. Indicates that the corresponding remittance reminder will be suspended.

This is not a limitation, but as an example, one user in a group stops remittance reminders corresponding to a remittance request from a remittance master user to another group user (remittance request destination user) in the same group. Is the case. It can also be said that a user other than the party becomes a witness and stops the remittance reminding of the party.
In order to stop the remittance reminding at the request of a user other than the parties concerned, "required" is stipulated as to whether or not the remittance master user needs to be approved.

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

In the setting where the approval of the remittance master user is "required", the server 10 can perform the approval confirmation process at a regular timing such as once every several hours, for example, without limitation. This is to prevent omission of denial by the remittance master user.

If the approval information is not received from the remittance master user's terminal 20 even after the set period (not limited to, for example, several days) has elapsed since the first approval confirmation process was executed, the server 10 uses the remittance master. You can also consider it approved by the user and stop the remittance reminders.
On the contrary, if the approval information is not received from the terminal 20 of the remittance master user even after the set period has elapsed since the first approval confirmation process is executed, the server 10 considers that the remittance master user has rejected the remittance. You can also prevent the reminder from stopping.

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

FIG. 9-2 shows User A. It is a figure which shows an example of the remittance request list screen displayed on the display part 24 of the terminal 20A of A.
In this example, the remittance master user is the user A. Let A be the user B. the remittance request destination user. As B, user A. A is user B. The case of stopping the remittance reminder corresponding to the remittance request sent to B will be described.

On this remittance request list screen, the user A. A is user B. Information about the remittance request sent to B and information about the remittance reminder corresponding to this remittance request are displayed.

In the display area of information regarding the remittance request, the user B. Next to the icon image of B and the user name, a reminder stop icon IC10 including a speaker image is displayed as an example, but not a limitation, for stopping the remittance reminder.
The reminder stop icon IC10 is not limited, but as an example, in the default state (the state in which the remittance reminder is not stopped), the image portion of the speaker is displayed in black with white.

When the remittance stop icon IC10 is tapped, the first remittance reminder stop information for stopping the remittance reminder corresponding to this remittance request pops up in the center of the screen, as shown in FIG. Is displayed.
Then, when the OK button BT10 included in the first remittance stop confirmation information is tapped, the remittance request selection information and the first remittance remittance stop request information are transmitted from the terminal 20A to the server 10 and selected. Remittance reminders corresponding to remittance requests are suspended.

Then, as an example, not limited to the user A. From A to user B. The display mode of the remind stop icon IC10 associated with the remittance request to B changes from the mode shown in FIG. 9-2. Specifically, as an example, not limited to, as shown in FIG. 9-4, the area displayed in black other than the image portion of the speaker of the remind stop icon IC10 is also displayed in white.
Further, based on the fact that the remittance reminder has been stopped, the display area of the remittance reminder corresponding to the above remittance request is discolored and displayed as an example, not limited to, as shown in FIG. 9-4.

Not only the remittance reminder may be stopped, but also the server 10 may be notified that the money has been paid based on the 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 completed flag to "OFF".
As a result, as shown in FIG. 9-5, as shown in FIG. 9-5, on the remittance request list screen displayed on the display unit 24 of the terminal 20A, for each of the remittance request and the corresponding remittance reminder, "DONE" is displayed. The completion mark MK1 including characters is displayed.

FIG. 9-6 shows the user B. It is a figure which shows an example of the remittance request list screen displayed on the display part 24 of the terminal 20A of B.
In this example, the remittance master user is the user A. Let A be the user B. the remittance request destination user. As B, user B. B is the user A. The case of requesting to stop the remittance reminder corresponding to the remittance request received from A will be described.

On this remittance request list screen, user B. B is user A. Information about the remittance request received from A and information about the remittance reminder corresponding to this remittance request are displayed.
In the remittance request display area, User A. Next to the icon image of A and the user name, the above-mentioned reminder stop icon IC10 is displayed.

When the remittance stop icon IC10 is tapped, as shown in FIG. 9-7, as an example, not limited to, the user A. The second remittance reminder stop information for requesting A is displayed in a pop-up in the center of the screen.
Then, when the OK button BT10 included in the second remittance stop confirmation information is tapped, the remittance request selection information and the second remittance remind stop request information are transmitted from the terminal 20B to the server 10. In this case, the server 10 is the user A. For terminal 20A of A
Send information to confirm whether you approve the suspension of remittance reminders.

In this case, FIG. 9-8 shows the user A. It is a figure which shows an example of the screen displayed on the display part 24 of the terminal 20A of A.
On the display unit 24 of the terminal 20A, suspension approval confirmation information for confirming whether or not to approve the suspension of the remittance reminder received from the server 10 is displayed in the central portion of the remittance request list screen. Then, when the OK button BT10 included in the approval confirmation information is tapped, the approval information is transmitted from the terminal 20A to the server 10. Then, on the server 10, the remittance reminder corresponding to this remittance request is stopped.
As a result, the remittance request list screen as shown in FIG. 9-9 is displayed on the display unit 24 of the terminal 20B as an example without limitation.

In the remittance request list screen of FIG. 9-9, the user A. From A to user B. The display mode of the remittance stop icon IC10 associated with the remittance request to B is changed and displayed, and the display area of the remittance reminder corresponding to the remittance request is discolored and displayed.

<Effect of 9th Example>
In this embodiment, the transmission control of the remittance reminder information (not limited, but an example of the second information) by the server 10 is input by the terminal 20 of the remittance master user (not limited, but an example of the first user) (not limited). , An example of the first input) is shown.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to control the transmission of the second information to the terminal of the user of the remittance request destination according to the intention of the first user of the remittance request source.

Further, in this embodiment, the first input described above shows a configuration in which the remittance reminder information is not transmitted to the terminal 20 of the remittance request destination user.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to control so that the second information is not transmitted to the terminal of the user of the remittance request destination according to the intention of the first user of the remittance request source. can.

Further, in this embodiment, the transmission control described above is based on an input to the terminal 20 (an example of a second input, not a limitation) by a remittance request destination user (an example of a terminal user, not a limitation). Shows the configuration to be executed.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to control the transmission of the second information to the terminal of the user of the remittance request destination according to the intention of the user of the remittance request destination.

Further, in this embodiment, the above-mentioned second input shows a configuration in which the remittance reminder information is not transmitted.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to control not to transmit the second information to the terminal of the user of the remittance request destination according to the intention of the user of the remittance request destination. ..

Further, in this embodiment, in the above transmission control, the above-mentioned second input and the information regarding the approval that the remittance master user does not transmit the second information (not limited to the second input by the first user). It shows the configuration to be executed based on (an example) of information on approval).
As an example of the effect of the embodiment obtained by such a configuration, not only as an example but as an example, even if there is a second input, if there is no approval for the second input by the first user of the remittance requesting source, The second information can be transmitted to the terminal of the user of the remittance request destination. On the contrary, as an example, not limited to this, if there is a second input and the first user of the remittance request source approves the second input, the terminal of the user of the remittance request destination is used. The second information can be prevented from being transmitted.

<Others>
In the above embodiment, the first information regarding the remittance request in the present invention is referred to as “remittance request information”, and the second information based on the remittance request is referred to as “remittance reminder information”, but the present invention is not limited thereto.

The combination of the first information and the second information in the present invention can be any combination 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 not limited, but as an example, the remittance master user exempts the remittance request destination user. Information for notifying (information for notifying that remittance does not need to be performed).
This combination can be applied when the remittance master user has once made a remittance request to the remittance request destination user, but wants to inform the remittance request destination user that it is not necessary to perform the remittance for some reason. be.

(3) Third combination-First information: Remittance exemption information-Second information: Remittance exemption remind information Remittance exemption remind information is not limited, but as an example, the remittance master user exempts remittance from the user to whom the remittance is requested. Information to reconfirm what to do (information to remind you that you do not need to send money).
This combination is applicable when the remittance master user notifies the remittance request destination user that the remittance is exempted and then wants to remind it.

(4) Fourth combination-First information: Remittance exemption information-Second information: Remittance request information In this combination, the remittance master user once notified the remittance request destination user that the remittance is exempted. , For some reason, it is necessary to have the remittance made, and it is applicable when requesting the remittance.

1 Communication system 10 Servers 20 Terminals 30 Networks

Claims (1)

A program executed by a server that communicates with a terminal
Sending the first information about the remittance request by the first user to the terminal by the communication unit of the server, and
Based on the execution of the remittance process related to the remittance to the first user based on the remittance request, the control unit of the server performs the transmission control related to the control of transmitting the second information based on the remittance request to the terminal. Is executed by the server.

Images