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

Description

The present invention relates to a program, an information processing method, and a server.

Technology is known that allows users to send and receive content via terminals and view it. Patent Document 1 discloses that a user can post a message via a social networking service (SNS), and when the message is confirmed, a process is performed to change the message from an unread state to a read state.

JP 2019-028735 A

According to a first aspect of the present invention, a program executed by a server transmits a first content input by the first user to a first terminal of the first user, on which a chat room including at least a first user and a second user is displayed, and transmitted from the first terminal, to a second terminal of the second user, and transmits a second content input by the second user to the second terminal, on which the chat room is displayed, and transmitted from the second terminal, to the first terminal, in which the server performs control to set a first setting for the chat room related to a remittance to the first user, by a control unit of the server, receives information related to the remittance from the second user to the first user based on the first setting and an input by the second user to the chat room displayed on the second terminal, by a communication unit of the server, and performs processing related to the remittance from the second user to the first user based on information related to the remittance from the second user to the first user, by the control unit.

According to a second aspect of the present invention, a server information processing method for transmitting a first content input by the first user to a first terminal of the first user on which a chat room including at least the first user and the second user is displayed and transmitted from the first terminal to a second terminal of the second user, and transmitting a second content input by the second user to the second terminal on which the chat room is displayed and transmitted from the second terminal to the first terminal, includes controlling a control unit of the server to set a first setting related to a remittance to the first user for the chat room, receiving information related to a remittance from the second user to the first user based on the first setting and an input by the second user to the chat room displayed on the second terminal, by a communication unit of the server, and performing a process related to a remittance from the second user to the first user based on information related to the remittance from the second user to the first user by the control unit.

According to a third aspect of the present invention, a server transmits a first content input by a first user to a first terminal of the first user on which a chat room including at least a first user and a second user is displayed and transmitted from the first terminal to a second terminal of the second user, and transmits a second content input by the second user to the second terminal on which the chat room is displayed and transmitted from the second terminal to the first terminal, the server comprising a control unit that controls setting a first setting for the chat room related to a remittance to the first user, and a communication unit that receives information related to a remittance from the second user to the first user based on the first setting and an input by the second user to the chat room displayed on the second terminal, and the control unit performs processing related to a remittance from the second user to the first user based on information related to a remittance from the second user to the first user.

FIG. 1 is a diagram showing a configuration of a communication system according to an embodiment of the present disclosure. FIG. 2 is a diagram showing an overview of information processing according to the first embodiment. FIG. 2 is a diagram showing an overview of information processing according to the first embodiment. FIG. 13 is a diagram showing an example of talk room information D12. FIG. 13 is a diagram showing an example of content information D13. FIG. 13 is a diagram showing an example of remittance account information D14. FIG. 15 is a diagram showing an example of remittance history information D15. FIG. 13 is a diagram showing an example of remittance account information D31. 4 is a flowchart showing a procedure of information processing according to the first embodiment. FIG. 13 is a diagram showing an example of relationship information D16. FIG. 13 shows an image T8 of a talk room in which a display regarding the setting of a predetermined relationship is displayed. FIG. 13 is a diagram showing an example of a remittance setting image T9. 10 is a flowchart showing information processing according to the second embodiment. FIG. 11 is a diagram showing an overview of information processing according to the second embodiment. FIG. 13 is a diagram showing an example of talk room information D12 according to the second embodiment. FIG. 13 is a diagram showing an example of an image T8 including content indicating completion of settings. FIG. 13 is a diagram showing an overview of information processing according to a fourth modified example. FIG. 13 is a diagram showing an example of talk room information D12 according to a fourth modified example. FIG. 13 is a diagram showing an overview of information processing according to a fifth modified example. FIG. 13 is a diagram showing an example of an image T13 including content related to a change of receipt. 13 is a flowchart showing information processing according to the third embodiment. FIG. 13 is a diagram showing an example of an approval confirmation screen T14. FIG. 17 is a diagram showing an example of personal identification information D17. FIG. 13 is a diagram showing an example of a remittance completion image T15. 13 is a flowchart showing information processing according to the fourth embodiment. FIG. 13 is a diagram showing an overview of information processing according to the fourth embodiment. FIG. 13 is a diagram showing an example of extinction condition information D18. 13 is a flowchart showing information processing according to the fifth embodiment. FIG. 13 is a diagram showing an overview of information processing according to the fifth embodiment. FIG. 19 is a diagram showing an example of first restriction information D19A. FIG. 19 is a diagram showing an example of second restriction information D19B. 20 is a flowchart showing information processing according to the sixth embodiment. FIG. 23 is a diagram showing an overview of information processing according to the sixth embodiment. FIG. 13 is a diagram showing an overview of information processing according to a seventh modified example. 23 is a flowchart showing information processing according to the seventh embodiment. FIG. 23 is a diagram showing an overview of information processing according to the seventh embodiment. FIG. 13 is a diagram showing an example of a remittance request image. FIG. 13 shows an example of a remittance request identification image T28. FIG. 23 is a diagram showing an overview of information processing according to a ninth modified example. FIG. 13 is a diagram showing an example of a remittance completion image T31. 23 is a flowchart showing information processing according to the eighth embodiment. FIG. 23 is a diagram showing an overview of information processing according to the eighth embodiment.

＜Compliance with legal matters＞

Please note that the disclosures contained herein are subject to compliance with the laws of the country in which they are implemented, including confidentiality of communications.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment for implementing an information processing method, a program, and an information processing device according to the present disclosure will be described with reference to the drawings.
<System Configuration>

Figure 1 shows the configuration of a communication system 1 according to an embodiment of the present disclosure. As disclosed in Figure 1, in the communication system 1, a server 10, user terminals 20 (user terminal 20A, user terminal 20B, user terminal 20C), and a payment server 30 are connected via a network N. The server 10 provides a service that realizes the transmission and reception of messages and other data (including, by way of example and not limitation, video data and audio data) between the multiple user terminals 20 via the network N. The server 10 also executes a remittance process between the payment server 30 via the network N. Note that the number of servers 10, user terminals 20, and payment servers 30 connected to the network N is not limited.

The network N plays a role in connecting one or more servers 10, one or more user terminals 20, and the payment server 30. In other words, the network N refers to a communication network that provides a connection path so that the user terminal 20 can send and receive data after connecting to the server 10.

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

The server 10 has a function of providing a predetermined service to the user terminal 20. The server 10 may be any information processing device capable of implementing the functions described in each embodiment. Examples of the server 10 include, but are not limited to, a server computer, a personal computer (such as, but not limited to, a desktop, laptop, tablet, etc.), a media computer platform (such as, but not limited to, a cable or satellite set-top box, digital video recorder), a handheld computer device (such as, but not limited to, a PDA, email client, etc.), or other types of computers or communication platforms. The server 10 may also be referred to as an information processing device.

The user terminal 20 (user terminal 20A, user terminal 20B, user terminal 20C) may be any information processing device (computer) that can realize the functions described in each embodiment. Examples of the user terminal 20 include, but are not limited to, smartphones, mobile phones (feature phones), personal computers (such as, but not limited to, desktops, laptops, tablets, etc.), media computer platforms (such as, but not limited to, cable and satellite set-top boxes, digital video recorders), handheld computer devices (such as, but not limited to, PDAs (personal digital assistants), email clients, etc.), wearable devices (such as glasses-type devices and watch-type devices), other types of computers, or communication platforms. The user terminal 20 may also be expressed as an information processing device.

In the following description, information about a user in a specified service that is associated with the user terminal 20 or the user of the user terminal 20 will be referred to as user information. Note that user information is information about a user that is associated with an account used by the user in a specified service. User information may include information input by the user, or may include information provided by the specified service. User information includes, by way of example and not limitation, at least one item of information among multiple items of information, such as the user's name, the user's icon image, the user's age, the user's gender, the user's address, the user's hobbies and interests, and the user's identifier. User information may include information that is different from the multiple items of information described above and that is associated with the user.

The payment server 30 has a function of providing services related to remittance according to instructions from the server 10. The payment server 30 may be any information processing device capable of implementing the functions described in each embodiment. The payment server 30 may include, but is not limited to, a server computer, a personal computer (such as, but not limited to, a desktop, laptop, tablet, etc.), a media computer platform (such as, but not limited to, a cable or satellite set-top box, digital video recorder, etc.), a handheld computer device (such as, but not limited to, a PDA, an email client, etc.), or other types of computers or communication platforms. The payment server 30 may also be referred to as an information processing device.
<Hardware (HW) configuration>

The HW configuration of each device included in the communication system 1 will be described with reference to FIG.
(1) Server hardware configuration

The server 10 comprises a control unit (CPU) 11, a memory unit 15, a communication I/F (interface) 14, an input unit 12, and an output unit 13. The components of the HW of the server 10 are connected to each other via a bus B1, by way of example and not limitation. Note that it is not essential that the HW of the server 10 includes all of the components as the configuration of the HW of the server 10. By way of example and not limitation, the HW of the server 10 may or may not be configured to allow the output unit 13 to be removed.

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

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

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

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

The input unit 12 is realized by a device that inputs various operations to the server 10. The input unit 12 is realized by any of all types of devices or a combination thereof that can receive input from a user and transmit information related to the received input to the control unit 11. The input unit 12 is typically realized by hardware keys such as a keyboard, or a pointing device such as a mouse. Note that the input unit 12 may or may not include a touch panel, a camera (operation input via video images), or a microphone (operation input by voice), as examples and without limitation. However, in the present disclosure, the input unit 12 is not limited to these.

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

The server 10 stores a program P1 and databases D11 to D15 in the storage unit 15. In the server 10, the control unit 11 executes this program P1, thereby executing the processes of each unit included in the control unit 11. In other words, the program 15a stored in the storage unit 15 causes the server 10 to realize each function executed by the control unit 11. This program P1 may or may not be expressed as a program module.
(2) User terminal hardware configuration

The user terminal 20 comprises a control unit (CPU: central processing unit) 21, a memory unit 25, a communication I/F (interface) 24, an input unit 22, and an output unit 23. The HW components of the user terminal 20 are connected to each other via a bus B2, by way of example and not limitation. It is not essential that the HW configuration of the user terminal 20 includes all of the components. By way of example and not limitation, the user terminal 20 may or may not be configured such that individual components, such as the input unit 22, the output unit 23, or multiple components, can be removed.

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

The input unit 22 includes a device for inputting various operations to the user terminal 20. The output unit 23 includes a device for outputting the results of processing performed by the user terminal 20. The input unit 22 and the output unit 23 may or may not be specified as input/output units. If specified as input/output units, the input/output unit may be integrated with the input unit 22 and the output unit 23, or may be separated into the input unit 22 and the output unit 23.

The input unit 22 is realized by any one of or a combination of all types of devices that can receive input from a user and transmit information related to the received input to the control unit 21. The input unit 22 includes, by way of example and not limitation, an operation unit 22a, a microphone 22b, and a camera 22c.
The operation unit 22a includes, by way of example and not limitation, a touch panel, a touch display, hardware keys such as a keyboard, and a pointing device such as a mouse. The microphone 22b includes, by way of example and not limitation, a device for inputting voice. The microphone 22b is used for inputting voice data. The camera 22c includes, by way of example and not limitation, a device for inputting images. The camera 22c is used for acquiring image data.

The output unit 23 is realized by any one of all types of devices or a combination thereof that can output the results of processing by the control unit 21. The output unit 23 includes, by way of example and not limitation, a display unit 23a and a speaker (audio output) 23b. The output unit 23 further includes, by way of example and not limitation, a touch panel, a touch display, a lens (for example and not limitation, 3D (three dimensions) output or hologram output), a printer, etc.

The display unit 23a is realized by any one of all types of devices or a combination thereof that can display an image according to the display data written to the frame buffer. Examples of the display unit 23a include, but are not limited to, a touch panel, a touch display, a monitor (for example, but not limited to, a liquid crystal display or an organic electroluminescence display (OELD)), a head mounted display (HDM), a projection mapping, a hologram, and a device that can display images, text information, etc. in air (which may or may not be a vacuum). Note that these display units 23a may or may not be capable of displaying display data in 3D. The speaker 23b is used to output audio data.

The input unit 22 and the output unit 23 may be specified as input/output units and configured as a touch panel, for example and not for limitation. When the input unit 22 and the output unit 23 are configured as a touch panel, the operation unit 22a and the display unit 23a may be arranged facing each other with approximately the same size and shape.

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

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

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

The user terminal 20 stores the program P1 and databases D21 to D25 in the storage unit 25. In the user terminal 20, the control unit 21 executes this program P2, thereby executing the processing of each unit included in the control unit 21. In other words, the program P2 stored in the storage unit 25 causes the user terminal 20 to realize each function executed by the control unit 21. Furthermore, this program P2 may or may not be expressed as a program module.
(3) Payment server hardware configuration

The payment server 30 comprises a control unit (CPU) 31, a memory unit 35, a communication I/F (interface) 34, an input unit 32, and an output unit 33. The components of the HW of the payment server 30 are connected to each other via a bus B3, by way of example and not limitation. It is not essential that the HW of the payment server 30 includes all of the components as the configuration of the HW of the payment server 30. By way of example and not limitation, the HW of the payment server 30 may or may not be configured to allow the output unit 33 to be removed.

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

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

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

The communication I/F 34 transmits and receives various data via the network N. The communication by the communication I/F 34 may be performed either wired or wirelessly, and any communication protocol may be used as long as the communication between the two devices is possible. The communication I/F 34 has a function of communicating with other devices, such as the user terminal 20, via the network N. The communication I/F 34 transmits various data to other devices according to instructions from the control unit 11. The communication I/F 34 also receives various data transmitted from other devices and transmits it to the control unit 31. The communication I/F 34 may also be referred to simply as a communication unit. When the communication I/F 34 is configured with a physically structured circuit, it may also be referred to as a communication circuit.

The input unit 32 is realized by a device that inputs various operations to the server 30. The input unit 32 is realized by any of all types of devices or a combination of devices that can receive input from a user and transmit information related to the received input to the control unit 31. The input unit 32 is typically realized by hardware keys such as a keyboard, or a pointing device such as a mouse. Note that the input unit 32 may or may not include a touch panel, a camera (operation input via moving images), or a microphone (operation input by voice), as examples and without limitation. However, in the present disclosure, the input unit 32 is not limited to these.

The output unit 33 includes a display unit 33a, for example and not for limitation. The display unit 33a is typically realized by a monitor (for example and not for limitation, a liquid crystal display or an OELD). The display unit 33a may or may not be a head mounted display (HDM) or the like. These display units 33a may or may not be capable of displaying display data in 3D. However, in the present disclosure, the display unit 33a is not limited to these.

The payment server 30 stores the program P3 and the database D31 in the memory unit 35. In the payment server 30, the control unit 31 executes this program P3, thereby executing the processing of each unit included in the control unit 31. In other words, the program P3 stored in the memory unit 35 causes the payment server 30 to realize each function executed by the control unit 31. This program P3 may or may not be expressed as a program module.

Each embodiment of the present disclosure will be described as being realized by the CPU of the user terminal 20 and/or the server 10 executing a program.

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

In addition, the programs of each embodiment of the present disclosure (for example, but not limited to, a software program, a computer program, or a program module) may or may not be provided in a state stored in a computer-readable storage medium. The storage medium can store the programs of each embodiment in a "non-transitory tangible medium." In addition, the programs of each embodiment may or may not be for realizing part of the functions of each embodiment of the present disclosure. Furthermore, the programs of each embodiment may or may not be what can realize the functions of each embodiment of the present disclosure in combination with a program already recorded in the storage medium, that is, a so-called difference file (difference program).

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

The servers 10, 30 and/or the user terminal 20 can realize the functions of the multiple functional units shown in each embodiment by reading a program stored in a storage medium and executing the read program.

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

Furthermore, each embodiment of the present disclosure may be realized in the form of a data signal embedded in a carrier wave in which a program is embodied by electronic transmission. At least a portion of the processing in the server 10, 30 and/or the user terminal 20 may or may not be realized by one or more computers (for example, and not by way of limitation, cloud computing consisting of one or more computers).

At least a part of the processing in the user 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 user 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 user 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 user terminal 20.

At least some or all of the processing in the payment server 30 may or may not be performed by the server 10. In this case, at least some or all of the processing of each functional unit of the control unit 31 of the payment server 30 may or may not be performed by the server 10.

Unless explicitly stated, the judgment configuration in the embodiments of the present disclosure is not essential, and a specified process may or may not be executed when the judgment condition is satisfied, or when the judgment condition is not satisfied.

The programs disclosed herein may be implemented using, for example and without limitation, scripting languages such as ActionScript and JavaScript (registered trademark), object-oriented programming languages such as Objective-C and Java (registered trademark), and markup languages such as HTML5.

The information processing according to the embodiment provides a service for executing a process related to remittance (for example, not limitation, a remittance process) between user terminals 20 of a group including a plurality of users, by way of example and not limitation. The remittance process includes, for example and not limitation, a process related to remittance and a remittance request. The remittance process will be described later.

In the following description, the user of user terminal 20A is represented as user A, the user of user terminal 20B is represented as user B, and the user of user terminal 20C is represented as user C. The number of users included in one group is any number equal to or greater than two. For example, one group may be composed of user A and user B, and the number of users included in this group is two. Another group may be composed of user A, user B, and user C, and the number of users included in this group is three.

In the following description, the service provided by the information processing according to the embodiment is referred to as a messaging service. The user terminal 20 displays an image of a graphical user interface (referred to as a GUI) provided by the messaging service, as an example and not a limitation. In the following description, the GUI that allows users in a group to view content transmitted and received between terminals in a group including multiple users is referred to as a talk room. The talk room may also be referred to as a chat room. Here, the talk room is, as an example and not a limitation, a display area in which messages can be transmitted and received between participating users. In addition, the talk room may be, as an example and not a limitation, a name different from the user name registered in the server 10 can be used within the area. In addition, the talk room may be, as an example and not a limitation, a talk room in which messages can be transmitted and received even if the participating users do not have a friend relationship, a following relationship, or a followed relationship.

The above content includes, by way of example and not limitation, at least one of text, images, and audio. The text included in the content includes, by way of example and not limitation, at least one of national characters, extended characters, machine-dependent characters, numbers, symbols, graphics, and codes, all of which are represented by character codes. The text included in the content does not have to include at least one of the above characters, extended characters, machine-dependent characters, numbers, symbols, graphics, and codes, and may include other text.

The images included in the content include, by way of example and not limitation, at least one of a captured image captured by a camera, a processed image obtained by performing image processing on a captured image, a computer graphics image (by way of example and not limitation, an icon, an emoticon, an emoticon) generated using a computer, and a text image that visualizes text. The images included in the content may include a composite image obtained by combining two or more of the captured image, processed image, computer graphics image, and text image. The images included in the content may not include at least one of the captured image, processed image, computer graphics image, text image, and composite image, and may include other images. The images included in the content may be still images, videos, or images in other forms. The content including images may be represented by icons such as thumbnails in an image in a talk room, by way of example and not limitation. The user terminal 20 may display the images included in the content based on an input to an icon representing an image included in the content, by way of example and not limitation.

The sound included in the content includes, by way of example and not limitation, at least one of recorded sound recorded by a microphone, processed sound obtained by processing recorded sound, synthetic sound generated by a computer, and read-aloud sound converted from text using a computer's read-aloud function. The sound included in the content may include a combination sound obtained by combining two or more of the above recorded sound, processed sound, synthetic sound, and read-aloud sound. The sound included in the content may not include at least one of the above recorded sound, processed sound, synthetic sound, read-aloud sound, and combined sound, and may include other sounds. The sound included in the content may include at least one of sounds or voices emitted by humans or non-human living beings, sounds emitted by objects such as musical instruments or machines, sound effects, environmental sounds, noise sounds, and alarms, or may not include at least one of these sounds or voices, or may include sounds different from these sounds or voices. The content including sound may be represented by an icon or the like in the image of the talk room, by way of example and not limitation. The user terminal 20 may play back the sound included in the content based on an input to an icon representing the sound included in the content, by way of example and not limitation.

The content may be, for example and without limitation, a combination of two or more of text, image, and audio. The content may be, for example and without limitation, a content in which video and audio are played in parallel, a content in which images and text are combined and displayed, or a content in which text is displayed in sync with audio playback. The content may also be a content in which audio is played in parallel with the display of text and images. The content may be, for example and without limitation, a content in which at least one of text, image, and audio is combined with content that is different from any of text, image, and audio.

The storage unit 15 of the server 10 stores information used in the messaging service, for example and not limitation. The information includes, for example and not limitation, user information D11, talk room information D12, content information D13, remittance account information D14, and remittance history information D15. The user information D11 includes, for example and not limitation, a user ID and a password associated with each account in the messaging service. In the messaging service, the user terminal 20 transmits account information D21 to the server 10. When the server 10 receives the account information D21 transmitted by the user terminal 20, it collates the user ID and password contained in the account information D21 with the user information D11 to identify the user associated with the user terminal 20. The talk room information D12, content information D13, remittance account information D14, and remittance history information D15 will be described later.

The storage unit 25 of the user terminal 20 stores information used in the messaging service, for example and not for limitation. The information includes, for example and not for limitation, account information D21, talk room information D22, content information D23, remittance account information D24, and remittance history information D25. The talk room information D22, content information D23, remittance account information D24, and remittance history information D25 will be described later.

Account information D21 is information about an account used by a user of the user terminal 20 in the messaging service. Account information D21 is information used to authenticate a user in the messaging service. Account information D21 includes, by way of example and not limitation, a user's identification information and a password. In the following description, the user's identification information will be referred to as a user ID as appropriate. The user ID may be information registered by the user of the user terminal 20, or may be information assigned in the messaging service.

The storage unit 25 may not store either or both of the user ID and password. For example, when the user is authenticated in the messaging service, the user may operate the input/output unit 23 of the user terminal 20 to input the necessary information of the user ID and password. Furthermore, the account information D21 may include information other than the user ID and password. For example, when the user is authenticated by biometric authentication, the account information D21 may include information such as the user's fingerprint, vein pattern, and face photo as information used for biometric authentication.

In addition, the memory unit 25 may not store at least a portion of the information used for the messaging service (for example and not limitation, talk room information D22, content information D23, remittance account information D24, and remittance history information D25. For example, at least a portion of the information used for the messaging service may be stored in a memory unit external to the user terminal 20 (for example and not limitation, the memory unit 15 of the server 10). The user terminal 20 may obtain the information used for the messaging service from a memory unit external to the user terminal 20 via the network N, for example and not limitation.
First Embodiment

FIG. 2 is a diagram showing information processing according to the first embodiment. An overview of this embodiment will be described. As an example and not a limitation, the server 10 transmits content input by a user and transmitted from a user terminal 20 of a certain user, in which a talk room in which multiple users participate is displayed, to a user terminal 20 of another user. Also, as an example and not a limitation, the server 10 transmits content input by another user to a user terminal 20 of another user, in which a talk room is displayed, to a user terminal 20 of a certain user. As an example and not a limitation, this embodiment is a form in which a user terminal 20 of a certain user performs a remittance to a user terminal 20 of another user in a talk room. In this embodiment, the user terminal 20 of the other user requests a remittance process to the server 10 via a communication unit (as an example and not a limitation, the communication I/F 24). The server 10 performs a remittance process based on the remittance process request, as an example and not a limitation.

The following is an overview of the remittance process. The remittance process is a process of remittance from a remittance account of a user to a remittance account of another user in a chat room. Here, remittance in the remittance process refers to, by way of example and not limitation, sending and receiving information about a payment means utilizing information and communication technology. Here, the payment means utilizing information and communication technology are, by way of example and not limitation, electronic value, electronic currency, etc. Electronic value and electronic currency include, by way of example and not limitation, information indicating gold, electronic money, points, etc. Hereinafter, information about a payment means utilizing information and communication technology is referred to as "value". Specifically, the user terminal 20 displays, by way of example and not limitation, a remittance setting image T4 for setting remittance contents shown in FIG. 2B(e) in the display area 28. Then, in FIG. 2B(e), the user terminal 20 accepts input from a certain user to the input unit 22 and specifies the remittance account and remittance amount used for remittance. When the remittance details are confirmed, the user terminal 20 sends a remittance processing request including information about the remittance to the server 10, for example and not by way of limitation. The server 10 identifies, for example and not by way of limitation, a remittance account included in the information about the remittance. The server 10 sends, for example and not by way of limitation, the information about the remittance to the payment server 30 corresponding to the identified remittance account. The payment server 30 completes the remittance from one user to another user by updating, for example and not by way of limitation, the remittance account information D31.

When the remittance process is completed, the user terminal 20 displays an image T7 of a talk room including content Q2 and content Q3 indicating the completion of the remittance process, as shown in FIG. 2B (h).
Specifically, content Q1 is a text that says "1000 yen per person," and content Q2 and content Q3 are text that says "1000 yen has been remitted." Note that the server 10 may or may not automatically transmit content Q2 and content Q3 to the user terminal 20 upon completion of the remittance process.

Next, this embodiment will be described in detail with reference to Figures 2 to 4 as appropriate. The contents described in this embodiment can be applied to each of the other embodiments as appropriate. In this embodiment, the same components as those in the above-mentioned embodiments will be denoted by the same reference numerals as appropriate, and their description will be omitted or simplified. In Figures 2A and 2B, the talk room is composed of user A, user B, and user C.

First, each image related to the talk room in this embodiment will be described. The symbol TL in FIG. 2A(a) is an image showing a list of talk rooms. The user terminal 20 displays an image TL of a list of talk rooms associated with the user terminal or the user of the user terminal in the display area 28, as an example and not a limitation. Note that the user terminal 20 may display an image TL of a list of talk rooms not associated with the terminal or the user of the user terminal in the display area 28, as an example and not a limitation. In the image TL of the list of talk rooms in FIG. 2A(a), "Coffee Party", "Tea Party", "Sports Day", and "Baseball Lover" are icons with the names of talk rooms. An icon is an image displayed in the display area 28, as an example and not a limitation. As an example and not a limitation, the user terminal 20 determines that a talk room named "Coffee Party" has been selected when an input is made to the input unit 22 for the "Coffee Party" icon. When an input is made to the input unit 22 for the "Coffee Party" icon displayed in the display area 28, the user terminal 20 determines that a talk room named "Coffee Party" has been selected, and displays an image T1 of the talk room named "Coffee Party" in the display area 28, as shown in FIG. 2A (b).

Here, each user can generate a talk room, by way of example and not limitation. When generating a talk room, each user selects, by way of example and not limitation, one or more users, and a talk room including the users selected by the user is generated by the server 10. Note that, by way of example and not limitation, a talk room may be generated without each user selecting one or more users. Note that the process of generating a talk room is not limited to being executed by the server 10, and may be executed by the user terminal 20, or may be executed by the user terminal 20 and the server 10. The process of generating a talk room may be executed by a device other than the user terminal 20 and the server 10.

In the following description, it is assumed that user A has generated the talk room "Coffee Party" in this embodiment. It is also assumed that user B and user C have participated in the talk room "Coffee Party". In the following, user A may be referred to as the "administrator", and user B and user C may be referred to as the "participants". Here, the administrator is, for example and not limited to, a user selected from the user who generated the talk room and the users who have participated in the talk room. It is also possible for the administrator to be referred to as the "master" for example and not limited to. It is also possible for the participant to be a user other than the administrator who has participated in the generated talk room. It is also possible for the participant's user terminal 20 to, for example and not limited to, determine that an icon with the name of the talk room has been selected when an input is made to the input unit 22, and to transmit a request to the server 10 to participate in the talk room, thereby allowing the participant to participate in the talk room. Also, as a non-limiting example, when a specific URL is input to the input unit 22, the participant's user terminal 20 may determine that the URL has been selected, display an image of the talk room associated with the URL in the display area 28, and allow the participant to participate in the talk room. Also, as a non-limiting example, the participant's user terminal 20 may allow the participant to participate in the talk room based on a participation request received from the user terminal 20 of the user who created the talk room.

In the image T1 of the talk room shown in FIG. 2A(b), the symbol Ta is the name of the talk room. As an example and not a limitation, the name of the talk room is set to a name entered by the administrator. As an example and not a limitation, the name of the talk room may be a name automatically assigned in a messaging service, or may be represented by the identification information of the talk room, etc.

In the talk room image T1 shown in FIG. 2(b), content Q1 is, by way of example and not limitation, content input by user A to the input unit 22 of user terminal 20A. Here, by way of example and not limitation, user terminal 20 displays the content input to the input unit 22 of its own terminal in a first direction relative to the talk room image T1. By way of example and not limitation, the first direction is the vertical direction relative to the talk room image T1, and a second direction intersecting with the first direction is the horizontal direction relative to the talk room image T1. For example, content Q1 in the talk room image T1 in FIG. 2(b) is content input by its own terminal (here, user terminal 20A), and is positioned to one side in the horizontal direction of the talk room image T1 and aligned vertically.

In the chat room image T2 shown in FIG. 2A(c), the symbol Tb is an icon for setting remittances (the remittance settings icon is an example and not a limitation) The remittance settings icon Tb includes, by way of example and not a limitation, a number of icons (icons indicating "remittance settings", "remittance", "receiving settings", "cancel receiving", "change receiving", "termination conditions", "report", "refund", "remittance request", and "cancel membership"). When an input is made to the input unit 22 for a specific icon included in the remittance settings icon Tb, the user terminal 20 displays an image corresponding to the icon in the display area 28. Note that the remittance settings icon Tb shown in FIG. 2A(c) is an example and is not limited to this.

In addition, in the image T7 of the talk room in FIG. 2B(h), the content Q2 and the content Q3 are contents transmitted from a terminal (here, the user terminal 20B or the user terminal 20C) different from the own terminal (here, the user terminal 20A). In the following description, the terminal different from the own terminal is appropriately referred to as the other terminal. As an example and not a limitation, the user terminal 20 displays the content transmitted from the other terminal at a position different from the content transmitted from the own terminal in the second direction. As an example and not a limitation, the content Q2 and the content Q3 in the image T7 of the talk room in FIG. 2B(h) are contents transmitted from the other terminal (here, the user terminal 20B or the user terminal 20C), and are arranged on the opposite side to the content Q1 in the horizontal direction of the image T7 of the talk room. Note that the image T4 of the talk room in FIG. 2B(e) is an image displayed in the display area 28 of the user terminal 20B, and the arrangement of the content Q1 in FIG. 2B(e) is arranged in a different position in the second direction compared to the content Q1 in FIG. 2A(b).

Furthermore, the user terminal 20, by way of example and not limitation, places each piece of content transmitted from another terminal and information about the user of the user terminal 20 that transmitted the content in a pair within the image of the talk room. The information about the user includes, by way of example and not limitation, at least one of an icon of the user, a name of the user, a user ID, and an indication of the user's nickname. In the talk room images T4 and T7 of Figures 2B(e) and 2B(h), the symbols Ua1, Ub1, and Uc1 are the icons of user A, user B, and user C, respectively. In the talk room images T4 and T7, the symbols Ua2, Ub2, and Uc2 are the usernames of user A, user B, and user C, respectively.

In the talk room image T7 in FIG. 2B(h), the symbol Ub1 is the icon of the user of the other terminal (here, user terminal 20B) who sent the content. The user terminal 20A arranges the content Q2 and the icon Ub1 of the user of the user terminal 20B who sent the content Q2 (here, user B) in the talk room image T7 so as to have a predetermined positional relationship. Note that, as an example and not a limitation, the user terminal 20 is assumed to be able to send and receive content including messages, etc., regardless of whether or not a remittance process is executed. In addition, the information about the user does not need to include at least one of the user's icon, user's name, user ID, and user's nickname, and may include information different from the display of the user's icon, user's name, user ID, and user's nickname. The user terminal 20 does not need to include the information about the user in the talk room image.

As a non-limiting example, the user terminal 20 displays images of each talk room in the display area 28, arranging the contents in each talk room in the order of the time they were sent in the first direction.
For example, in the talk room image T7 shown in Figure 2B (h), content Q2 is content sent after content Q1, and content Q3 is content sent after content Q2, and is positioned vertically below content Q1 in the talk room image T7.

The following describes an overview of each device constituting the communication system 1. First, an overview of the operation of the server 10 will be described. When the server 10 receives a remittance processing request from the user terminal 20, the server 10 stores the remittance processing request in the memory unit 15, for example and not limitation. The server 10, for example and not limitation, matches the remittance source and remittance destination user IDs included in the remittance processing request with the talk room information D12 to identify the remittance source and remittance destination users in the talk room. The server 10, for example and not limitation, matches the remittance account included in the remittance processing request with the remittance account information D14 to identify the remittance account for remittance. The server 10, for example and not limitation, identifies the remittance amount included in the remittance processing request. The server 10, for example and not limitation, transmits remittance information to the payment server 30 to update the value corresponding to the "remittance account ID" based on the identified remittance account and remittance amount. As a non-limiting example, the server 10 sets the user terminal 20 corresponding to the user IDs of the sender and recipient as the destination as a result of processing related to the remittance in the payment server 30, and transmits (e.g., distributes) content indicating that the remittance has been completed. When transmitting the content, the server 10 updates the remittance history information D15. When the user terminal 20 receives the content transmitted by the server 10, it transmits a receipt notification to the server 10, as a non-limiting example. When the server 10 receives the receipt notification transmitted by the user terminal 20, it may, as a non-limiting example, delete the content associated with the receipt notification from the content information D13.

Next, examples of talk room information D12, content information D13, remittance account information D14, and remittance history information D15, which are referenced in the operation of the server 10, will be described. FIG. 3A is a diagram showing an example of talk room information D12. Talk room information D12 includes, by way of example and not limitation, the following items: [Talk room ID], [Name], [User ID], [Creator ID], [Remittance recipient ID], [Remitter ID], and [Content list]. [Talk room ID] is an item that includes identification information of the talk room. By way of example and not limitation, the talk room ID is assigned in the messaging service when a user creates a talk room.

[Name] is an item that indicates the name of the talk room, by way of example and not limitation. [Name] is associated with [Talk Room ID]. For example, the [Name] of a talk room whose [Talk Room ID] is [tr01] is [Coffee Party]. The [Name] of a talk room whose [Talk Room ID] is [tr02] is [Tea Party]. The [Name] of a talk room whose [Talk Room ID] is [tr03] is [Sports Day].

[User ID] is an item that indicates, by way of example and not limitation, the identification information of users included in a group corresponding to each talk room. [User ID] is associated with [Talk Room ID]. For example, the users included in a group corresponding to a talk room with [Talk Room ID] "tr01" are user A, user B, and user C, and the [User ID] corresponding to "tr01" includes the user ID of user A, the user ID of user B, and the user ID of user C. Similarly, the users included in groups corresponding to talk rooms with [Talk Room ID] "tr02" and "tr03" are also user A, user B, and user C.

[Creator ID] is an item that indicates, by way of example and not by way of limitation, the identification information of a user who has created each talk room. [Creator ID] is associated with [Talk Room ID].
For example, the user who created the talk room with [talk room ID] "tr01" is user A, and the [creator ID] corresponding to "tr01" includes the user A's user ID.
Similarly, the user who created the talk rooms "tr02" and "tr03" is also User A.

[Money transfer recipient ID] is an item that indicates, by way of example and not limitation, the identification information of a user (a money transfer recipient, by way of example and not limitation) who can receive money transfers in each chat room. [Money transfer recipient ID] is associated with [Talk room ID]. For example, in a chat room with a [Talk room ID] of "tr01", the user who can receive money transfers is user A, and the [Money transfer recipient ID] corresponding to "tr01" includes the user ID of user A. That is, in the chat room with a [Talk room ID] of "tr01", only user A is set to be able to receive money transfers. Also, for example, in a chat room with a [Talk room ID] of "tr02", the user who can receive money transfers is user B, and the [Money transfer recipient ID] corresponding to "tr02" includes the user ID of user B. Also, for example, in a chat room with a [Talk room ID] of "tr03", the user who can receive money transfers is user A, and the [Money transfer recipient ID] corresponding to "tr03" includes the user ID of user A. For example, and not by way of limitation, the server 10 may automatically set the administrator's user ID to the [Remittance Recipient ID] when the chat room is created, may set it based on information set by the administrator, or may set it based on information set by the participants at any time.

[Remitter ID] is an item indicating, by way of example and not limitation, the identification information of a user (a remitter, by way of example and not limitation) who can send money in each talk room. [Remitter ID] is associated with [Talk Room ID]. For example, in a talk room with [Talk Room ID] "tr01", users who can send money are user B and user C, and the [Remitter ID] corresponding to "tr01" includes the user IDs of user B and user C. That is, the talk room with "tr01" is set so that only user B and user C can send money to user A. Also, for example, in a talk room with [Talk Room ID] "tr02", users who can send money are user A and user C, and the [Remitter ID] corresponding to "tr02" includes the user IDs of user A and user C. Also, for example, in a talk room with [Talk Room ID] "tr03", only user B can send money, and the [Remitter ID] corresponding to "tr03" includes the user ID of user B. As a non-limiting example, the server 10 may automatically set the user ID to be set as [Sender ID] to the user ID of a participant when a user joins a talk room, may set it based on information set by an administrator at any timing, or may set it based on information set by a participant at any timing.
As an example and not a limitation, the talk room information D12 may not include the [Remitter ID] item. In this case, as an example and not a limitation, the server 10 may automatically set the user ID of a participant who has joined the talk room to the [Remitter ID].

[Content List] is an item that indicates, by way of example and not limitation, information showing a list of content contained in each talk room. [Content List] is associated with [Talk Room ID]. For example, the content contained in a talk room with [Talk Room ID] "tr01" is represented by "List 1," which is part of content information D13.

Figure 3B is a diagram showing an example of content information D13. Figure 3B is a part of content information D13 and corresponds to "List 1" in Figure 3A. Content information D13 includes, by way of example and not limitation, the items [Content ID], [Sender User ID], and [Content].

[Content ID] is an item that indicates the identification information of each content. The identification information of the content is assigned by the messaging service when the user terminal 20 sends the content, for example and not limitation. Here, the content with [Content ID] "tr01c01" corresponds to the content Q1 in the talk room image T1 in FIG. 2A (b). Similarly, the content with [Content ID] "tr01c02" corresponds to the content Q2, and the content with [Content ID] "tr01c03" corresponds to the content Q3.

[Sender User ID] is an item that indicates, by way of example and not limitation, the user ID corresponding to the user terminal 20 that transmitted each piece of content. [Sender User ID] is associated with [Content ID]. For example, for a piece of content with a [Content ID] of "tr01c01", the user corresponding to the transmitted user terminal 20 is user A, and the [Sender User ID] corresponding to "tr01c01" includes the user ID of user A. For a piece of content with a [Content ID] of "tr01c02", the user corresponding to the transmitted user terminal 20 is user B, and the [Sender User ID] corresponding to "tr01c02" includes the user ID of user B.

[Content] is an item indicating the content sent by the user, for example and not for limitation. [Content] is associated with [Content ID]. When the content includes text, the text data of the content is stored in [Content]. For example, the content Q1 shown in FIG. 2B is a text of "1,000 yen per person," and the text data representing "1,000 yen per person" is stored in [Content] corresponding to "tr01c01." Furthermore, the content Q2 and the content Q3 shown in FIG. 2F are a text of "Remittance completed," and the text data representing "1,000 yen has been remitted" is stored in [Content] corresponding to "tr01c02" and "tr01c03." Furthermore, when the content includes an image, the image data, a link to the image data, or an address of a storage unit in which the image data is stored is stored in [Content]. The image data may include, for example and not for limitation, still image data or video data. The image data may include, for example and not for limitation, data representing a stamp, a sticker, an emoticon, and an emoticon, or may not include such data.
If the content includes audio, the audio data, a link to the audio data, or the address of a storage unit in which the audio data is stored is stored in [Content].

Figure 3C is a diagram showing an example of remittance account information D14. Remittance account information D14 includes, by way of example and not limitation, the fields for [User ID] and [Remittance Account ID]. [User ID] is, by way of example and not limitation, an item indicating the user's identification information.

[Remittance Account ID] is an item that indicates the identification information of each remittance account, by way of example and not limitation. [Remittance Account ID] is associated with [User ID]. For example, the remittance accounts that can be used by a user whose [User ID] is "User A" are Remittance Account A, Remittance Account B, and Remittance Account C, and includes the remittance account IDs of Remittance Account A, Remittance Account B, and Remittance Account C.

3D is a diagram showing an example of remittance history information D15. Remittance history information D15 includes the following items, by way of example and not limitation: [Chat Room ID], [Date and Time], [Remittance Recipient ID], [Remittance Sender ID], [Remittance Amount], and [Remittance Account]. [Chat Room ID], [Remittance Recipient ID], and [Remittance Sender ID] are similar to those described in FIG. 3A by way of example and not limitation, and therefore description thereof will be omitted. [Date and Time] is an item indicating the date and time when the chat room ID was assigned. [Remittance Amount] is an item indicating information indicating the amount of value remitted by the user.
[Remittance amount] is associated with [Chat room ID]. That is, in the chat room tr01 in Fig. 3D, a value of "1,000" is transferred from user B to user A at "10:00 on Jan. 1, 2020," and a value of "1,000" is transferred from user C to user A at "11:00 on Jan. 1, 2020."

Next, an overview of the operation of the user terminal 20 will be described. By way of example and not limitation, the user terminal 20 refers to the talk room information D22 and the content information D23 shown in FIG. 1 to display an image of a talk room in the display area 28. By way of example and not limitation, the user terminal 20 accepts an input by a user to the input unit 22, and by way of example and not limitation, transmits a remittance process request to the server 10, including information on the remittance source, remittance destination, remittance amount, and remittance account, by way of example and not limitation, the user terminal 20 receives remittance history information from the server 10. By way of example and not limitation, the user terminal 20 stores the received remittance history information in the storage unit 25. By way of example and not limitation, the user terminal 20 may display an image of a talk room including content indicating that the remittance process has been completed in the display area 28, by way of example and not limitation, by way of example and not limitation, the remittance history information D25.

Next, examples of talk room information D22, content information D23, remittance account information D24, and remittance history information D25 that are referenced in the operation of the user terminal 20 will be described. Note that, by way of example and not limitation, the user terminal 20 may not store the remittance account information D24 and remittance history information D25 in the storage unit 25.

The talk room information D22 is, by way of example and not limitation, information about a talk room associated with a user of the user terminal 20. The items included in the talk room information D22 are similar to those in the talk room information D12, and therefore a description thereof will be omitted.

The content information D23 is, by way of example and not limitation, information about the content in a talk room associated with the user of the user terminal 20. The items included in the content information D23 are the same as those in the content information D13, and therefore a description thereof will be omitted.

The remittance account information D24 is, by way of example and not limitation, information about a remittance account associated with a user of the user terminal 20. The items included in the remittance account information D24 are similar to those in the remittance account information D14, and therefore a description thereof will be omitted.

The remittance history information D25 is, by way of example and not limitation, information regarding remittances in a chat room associated with the user of the user terminal 20. The items included in the remittance history information D25 are the same as those in the remittance history information D15, and therefore a description thereof will be omitted.

Next, an overview of the operation of the payment server 30 will be described. When the payment server 30 receives remittance information from the server 10, by way of example and not limitation, the payment server 30 stores the remittance information in the memory unit 35. By way of example and not limitation, the payment server 30 identifies the remittance account IDs of the remitter and the remittance destination contained in the remittance information. By way of example and not limitation, the payment server 30 refers to the remittance account information D31 and transfers a value corresponding to the remittance amount from the value corresponding to the remittance account ID of the remitter to the value corresponding to the remittance account ID of the remittance destination (by way of example and not limitation, a process related to remittance). By way of example and not limitation, the payment server 30 sends a notification regarding the result of the process related to remittance to the server 10.

Next, an example of remittance account information D31 that is referenced in the operation of the payment server 30 will be described. The remittance account information D31 is information about a remittance account associated with a user of the user terminal 20, by way of example and not limitation. FIG. 4 is a diagram showing an example of remittance account information D31. The remittance account information D31 includes the items [User ID], [Remittance Account ID], and [Value], by way of example and not limitation. The [User ID] and [Remittance Account ID] are similar to the [User ID] and [Remittance Account ID] of the remittance account information D14, and therefore their description will be omitted. [Value] is an item that indicates the amount of value, by way of example and not limitation. [Value] is associated with the [Remittance Account ID].

Next, the settings for money transfer to each user in the server 10 will be described. When a talk room is generated by an administrator, the server 10 registers the user ID of the administrator in the [User ID] and [Producer ID] fields in association with the talk room ID, as in the talk room information D12 of FIG. 3A. When a participation request is received from a participant, the server 10 registers the user ID of the participant in the [User ID] field in association with the talk room ID, as in the talk room information D12. Then, the server 10 performs settings for money transfer, as in an example and not a limitation. The settings for money transfer, as an example and not a limitation, are to set the user IDs of the administrator and the participants in the [Remittance Recipient ID] or [Remittance Sender ID] fields. As an example and not a limitation, the server 10 may set settings for money transfer based on information regarding a predetermined setting, or may set settings for money transfer based on information regarding a setting determined by the administrator or the participant.

Next, the procedure of information processing according to the first embodiment will be described with reference to Figs. 2 to 5 as appropriate. Fig. 5 is a flowchart showing the procedure of information processing according to the first embodiment. Here, Fig. 5 shows, as an example and not a limitation, the procedure from when the administrator creates a talk room to when the participants complete remittances to the administrator. Hereinafter, as an example and not a limitation, the administrator is User A, the participants are User B and User C, and the talk room in which User A, User B, and User C participate is called a "coffee meeting."

First, in step S111, the user terminal 20A generates a creation request for a talk room A to the server 10 based on an input by the user A to the input unit 22. In step 112, the user terminal 20A transmits the creation request to the server 10 via the communication I/F 24. The server 10 receives the creation request from the user terminal 20A via the communication I/F 14.

Next, in step S121, the server 10 registers the talk room ID, the user ID, and the creator ID in the talk room information D12 based on the creation request (see FIG. 3A). By way of example and not limitation, when the talk room is registered in the talk room information D12, the server 10 transmits the talk room information D12 to the user terminal 20A.

Next, the user terminal 20A stores talk room information D12 (see FIG. 3A ) in the storage unit 25. The user terminal 20A reads out talk room information D22 and generates an image TL of a list of talk rooms. The control unit 21 of the user terminal 20A controls the display unit 23a to display the image TL in the display area 28.
Then, when there is input into the input unit 22 for the icon of the talk room "Coffee Meeting", the user terminal 20A determines that the talk room "Coffee Meeting" has been selected, and displays an image of the talk room "Coffee Meeting" in the display area 28.

Next, in step S122, the server 10 may, by way of example and not limitation, send a join request to the user terminal 20 to join the talk room "Coffee Party."

Next, in step S131, the user terminal 20B, as an example and not a limitation, displays an image TL of a list of talk rooms as shown in FIG. 2A in the display area 28 when the application of the messaging service is started. When an input is made to the input unit 22 for the icon of "coffee meeting" in the list, the user terminal 20B determines that the talk room "coffee meeting" has been selected. When it is determined that "coffee meeting" has been selected, as an example and not a limitation, the user terminal 20B generates a participation request to request the server 10 to participate in the talk room "coffee meeting". Then, in step S132, the user terminal 20B transmits a participation request to the server 10 for the talk room "coffee meeting" via the communication I/F 24. As an example and not a limitation, steps S131 and S132 are similarly executed in the user terminal 20C. The server 10 stores the participation request in the storage unit 15. As an example and not a limitation, the server 10 registers the user ID of user B in the talk room information D12 based on the participation request (see FIG. 3A). As a non-limiting example, when the user ID of user B is registered in the talk room information D12 on the server 10, the user terminal 20B may receive the content information D13 from the server 10 and display an image T1 including the content Q1 as shown in FIG. 2(b) in the display area 28.

Before step S131, the server 10 may, by way of example and not limitation, send a participation request to the user terminal 20 (here, user terminal 20B and user terminal 20C) to participate in the talk room. In this case, by way of example and not limitation, when the user terminal 20 receives the participation request from the server 10, the user terminal 20 may display in the display area 28 an image including message text requesting participation in the talk room "Coffee Party", or may display in the display area 28 an image T4 as shown in FIG. 2(e) which indicates a state in which the user has joined the talk room.

Next, in step S133, the server 10 transmits, by way of example and not limitation, talk room information D12 (here, participation information) in which the user IDs of the participants are registered, to the user terminal 20A. By way of example and not limitation, the user terminal 20A stores the participation information in the storage unit 25.

Next, in step S141, the user terminal 20A displays in the display area 28 a talk room image T2 including the content Q1 as shown in FIG. 2A(b), for example and not for limitation. When an input is made to the input unit 22 for the icon PL in the display area 28, the user terminal 20A determines that the icon PL has been selected, and displays in the display area 28 a selection image T2 including a remittance setting icon Tb as shown in FIG. 2A(c). Then, when an input is made to the input unit 22 for the icon "remittance setting" in FIG. 2A(c), the user terminal 20A determines that "remittance setting" has been selected. Then, by way of example and not for limitation, the user terminal 20A refers to the talk room information D22 and displays in the display area 28 a remittance setting image T3 as shown in FIG. 2A(d). The remittance setting image T3 includes, by way of example and not for limitation, a remittance recipient setting section T3a, a remittance sender setting section T3b, and a setting confirmation section T3c. The remittance recipient setting unit T3a is an area for setting a user who will be a remittance recipient, which displays, as an example and not a limitation, the name of a user whose user ID is associated with the talk room "Coffee Party" based on the talk room information D22. The remittance sender setting unit T3b is an area for setting a user who will be a remittance sender, which displays, as an example and not a limitation, the name of a user whose user ID is associated with the talk room "Coffee Party" based on the talk room information D22. Here, the remittance recipient setting unit T3a and the remittance sender setting unit T3b may, as an example and not a limitation, display the user's name in a predetermined display format (as an example and not a limitation, a pull-down) when an input is made to the input unit 22. The remittance recipient setting unit T3a and the remittance sender setting unit T3b may, as an example and not a limitation, be a text box that accepts input of a user's name. For example and not limitation, when an input is made to the input unit 22, the setting confirmation unit T3c confirms information (for example and not limitation, the first setting information) related to the above-mentioned setting related to the remittance (for example and not limitation, the first setting). Then, in step S142, the user terminal 20A transmits the first setting information to the server 10. Note that, in the above description, the first setting information is generated by the administrator (here, user A) who generated the talk room, but this is not limited to this. For example and not limitation, the first setting information may be generated by a participant (here, user B or user C) of the generated talk room. Also, in the description, the server 10 sets the first setting in step S141, but this is not limited to this. For example and not limitation, the server 10 may set the first setting automatically or based on the setting information generated by the administrator when receiving a creation request from the user terminal 20A in step S121, or may set the first setting automatically or based on the setting information generated by the administrator when receiving a participation request from the user terminal 20 in step S131, and the timing at which the first setting is set is not limited.

The contents of the first setting will now be described. The first setting may be, by way of example and not limitation, automatically set by the server 10, or may be set by the user as described above. "Setting" may mean, by way of example and not limitation, that authority, power, or responsibility regarding remittance is granted to at least one of the user IDs of the administrator or participant.

First, when the first setting is automatically set by the server 10, the server 10 may, by way of example and not limitation, register the administrator's user ID in [Money Transfer Recipient ID] when the administrator creates a talk room, and may register the participant's user ID in [Money Transfer ID] when a participation request is received from a participant. In this case, as in the talk room ID in FIG. 3A being "tr01", the administrator's user ID is registered in [Money Transfer Recipient ID], and the participant's user ID is registered in [Money Transfer ID]. This makes it possible for participants to transfer money to the administrator in the talk room. In other words, in this case, the first setting is a setting that does not allow users participating in the talk room to transfer money to participants.

Next, when the first setting is set by a user, the user IDs registered in [Money Transfer Recipient ID] and [Money Sender ID] are set arbitrarily. Specifically, as a non-limiting example, the server 10 may register a user ID of one of the participants in [Money Transfer Recipient ID], and register user IDs of the administrator and other participants in [Money Sender ID], as in the talk room ID in FIG. 3A being "tr02". This allows money to be transferred from the administrator and other participants to one of the participants in the talk room. As a non-limiting example, the server 10 may register a user ID of the administrator in [Money Transfer Recipient ID], and register user IDs of a specific participant among the participants in [Money Sender ID], as in the talk room ID in FIG. 3A being "tr03". This allows money to be transferred to the administrator only from a specific participant in the talk room.

Next, in step S151, the server 10 registers the user ID in the [Remittance Recipient ID] and [Remittance Sender ID] fields of the talk room information D12 based on the first setting information, for example and not by way of limitation.

Next, in step S161, the user terminal 20B displays, as an example and not a limitation, an image T4 of a talk room including content Q1 as shown in FIG. 2B(e) in the display area 28. When an input is made to the input unit 22 for an icon PL in the display area 28, the user terminal 20B determines that the icon PL has been selected, and displays a selection image T5 including a remittance setting icon Tb shown in FIG. 2B(f) in the display area 28. When an input is made to the input unit 22 for the icon "Remittance" in FIG. 2B(f) in the display area 28, the user terminal 20B determines that the icon "Remittance" in FIG. 2B(f) has been selected, and displays, as an example and not a limitation, a remittance registration image T6 shown in FIG. 2B(g) in the display area 28 with reference to the talk room information D22 and the remittance account information D24. The remittance registration image T6 includes, for example and not limitation, a remittance destination T61, a remittance account setting section T62, a remittable amount T63, a remittance amount input section T64, and a remittance confirmation section T65. The remittance destination T61 is, for example and not limitation, an area that displays a remittance destination specified by referring to the talk room information D22. The remittance account setting section T62 is, for example and not limitation, an area that displays the name of a remittance account corresponding to a usable remittance account ID in a predetermined display format (for example and not limitation, a pull-down) when an input is made to the input section 22. Note that, for example and not limitation, the remittance account setting section T62 may be a text box that accepts and displays an input of the name of a remittance account by a user. The remittable amount T63 is, for example and not limitation, an area that displays the remaining amount of value that can be remitted in the selected remittance account. The remittance amount input section T64 is, for example and not limitation, an area that displays the input remittance amount when an input is made to the input section 22. When an input is made to the input unit 22, the remittance confirmation unit T65, by way of example and not by way of limitation, confirms the information relating to the remittance (by way of example and not by way of limitation, the remittance information). Then, in step S162, the user terminal 20B transmits a remittance processing request including the remittance information to the server 10. Here, the remittance processing request is, by way of example and not by way of limitation, information by which the remittance sender user B requests the server 10 to perform processing to send remittance to the remittance recipient user A. By way of example and not by way of limitation, steps S161 and S162 are similarly executed in the user terminal 20C.

Next, in step S171, the server 10 stores the remittance processing request in the memory unit 15. The server 10, as an example and not a limitation, compares the user ID of user B with the user ID of [remitter ID] in the talk room information D12 based on the remittance processing request. As an example and not a limitation, the control unit 11 transitions to the remittance processing when the user ID of user B matches the user ID of [remitter ID] as a result of the comparison. As an example and not a limitation, the control unit 11 identifies the user IDs of the remitter and the remitter, the remittance account, and the remittance amount based on the remittance information. As an example and not a limitation, the server 10 transmits a remittance notification including information on the user IDs of the remitter and the remitter, the remittance account, and the remittance amount to the payment server 30. The payment server 30 transfers the value corresponding to the remittance amount from the value of the remittance account corresponding to the user ID of the remitter to the value of the remittance account corresponding to the user ID of the remitter. The payment server 30 sends information regarding the result of the remittance process to the server 10, for example and not by way of limitation. This completes the remittance process.

Next, in step S172, the server 10 transmits a remittance completion notification including information regarding the remittance amount to the user terminal 20. Based on the remittance completion notification, the user terminal 20A, by way of example and not limitation, displays an image T7 including content Q2 and content Q3 (by way of example and not limitation, 1,000 yen has been remitted) indicating the completion of remittance as shown in FIG. 2B(h). By way of example and not limitation, the user terminals 20B and 20C also similarly display images including content Q2 and content Q3. This allows the users of the talk room to check the status of remittance in the talk room.
<First Modification>

With reference to FIG. 6, the information processing according to the first modified example will be described. FIG. 6 is a diagram showing an example of the relationship information D16. The information processing according to the first modified example is a form in which the administrator and participants of the chat room can send money to other users in the chat room even if they do not have a specific relationship in the messaging service. Here, the "specific relationship" refers to a relationship that can be recognized between users in the messaging service, by way of example and not by way of limitation. For example, the specific relationship is a friend relationship, a followed relationship, a following relationship, etc. In addition, the server 10 may have relationship information D16 indicating the above relationship between each user, by way of example and not by way of limitation. The relationship information D16 includes at least one of the items [User ID], [Friend Relationship], [Follow 1], and [Follow 2], by way of example and not by way of limitation. The relationship information D16 may further include an item indicating a relationship that can be recognized between users.

[Friendship] is an item that indicates a user ID that has a friendship with a certain user. [Friendship] is associated with [User ID]. A "friendship" refers to, by way of example and not limitation, a relationship in which two users have information that can identify each other in a messaging service. Specifically, by way of example and not limitation, when a telephone number corresponding to a user terminal 20B of another user (here, user B) is registered as a contact point for user B in a user terminal 20A of a certain user (here, user A), user A and user B are in a "friendship". Also, by way of example and not limitation, when a messaging account corresponding to user B is registered in user terminal 20A of user A, user A and user B are in a "friendship". Also, by way of example and not limitation, when a telephone number corresponding to user A's user terminal 20A is registered as a contact point for user A in user terminal 20B of user B, user B and user A are in a "friendship". Also, as a non-limiting example, if a messaging account corresponding to user A is registered in user terminal 20B of user B, user B and user A are in a "friend relationship." Also, as a non-limiting example, if a messaging account corresponding to user B's user terminal 20B registered in user terminal 20A of user A is also registered in user terminal 20C of user C, user A and user C are in a "friend relationship." For example, this is the relationship between user A and user C in FIG. 6, who have user D as a mutual friend.

[Follow 1] is an item indicating the user ID of a user who has a relationship of being followed by a certain user. [Follow 1] is associated with [User ID]. The "following relationship" refers to, by way of example and not limitation, a relationship between a user A and a user B in which the user terminal 20 of a certain user (here, user A) registers an account including content provided by the user terminal 20 of another user (here, user B) in a messaging service. In this case, the relationship between user A and user B is a relationship in which user B is followed by user A. Specifically, by way of example and not limitation, when an input is made to the input unit 22 of the user terminal 20A of user A in the content on the messaging service related to user B, the user terminal 20A of user A transmits information regarding the registration of the account to the server 10. The server 10 registers the relationship in which user A is followed by user B by updating the relationship information D16 based on the information regarding the registration of the account.

[Follow 2] is an item indicating the user ID of a user who has a relationship of following a certain user. [Follow 2] is associated with [User ID]. The "following relationship" refers to, as a non-limiting example, a relationship between a user B and a user A in which the user terminal 20 of another user (here, user B) has registered an account including content provided by the user terminal 20 of a certain user (here, user A) in a messaging service. In this case, the relationship between user B and user A is a relationship in which user B follows user A. Specifically, as a non-limiting example, the user terminal 20B of user B transmits information regarding the registration of the account to the server 10 when an input is made to the input unit 22 for the account registration unit (as a non-limiting example, "follow") displayed in the display area 28 in the content on the messaging service related to user A. The server 10 registers the relationship in which user B follows user A by updating the relationship information D16 based on the information regarding the registration of the account.
<Second Modification>

With reference to FIG. 7, the information processing according to the second modification will be described. FIG. 7 is a diagram showing an image T8 of a talk room on which a display related to the setting of a predetermined relationship is displayed. The information processing according to the second modification is, as shown in FIG. 7, a form including a display for setting at least one of a friend relationship, a followed relationship, and a following relationship (here, "add friend") in the image of the talk room. When an input is made to the input unit 22 for the "add friend" icon T81, the control unit 21 determines that "add friend" is selected, and displays an image for setting a friend relationship in the display area 28. As an example and not a limitation, the same is true for the display for setting a followed relationship and the display for setting a following relationship. Note that, as an example and not a limitation, as shown in FIG. 7, the image of the talk room may not include a display for setting at least one of a friend relationship, a followed relationship, and a following relationship (here, "add friend"). By eliminating the display related to the setting of a predetermined relationship, it is possible to prevent a friend relationship, a followed relationship, and a following relationship from being established between users in the talk room.
<Third Modification>

The information processing according to the third modified example will be described with reference to FIG. 8. FIG. 8 is a diagram showing an example of a remittance setting image T9. The information processing according to the third modified example is, as an example and not a limitation, a form in which the remittance destination T61 of the remittance registration image T6 of FIG. 2(g) is displayed as a selectable remittance destination. When an input is made to the input unit 22 for the icon of the remittance destination T91 (here, ▼), the user terminal 20 determines that the icon of the remittance destination T91 has been selected. As an example and not a limitation, when it is determined that the icon of the remittance destination T91 has been selected, the control unit 21 displays a list showing candidates of the remittance destination in the display area 28 as shown in FIG. 8. As an example and not a limitation, the control unit 21 may display a list of candidates of the remittance destination by arranging user names corresponding to the user IDs associated with the talk room IDs with reference to the talk room information D22.
===Effect===

According to this embodiment, the server 10 transmits content sent by user A through input to the input unit 22 of the user terminal 20A to the user terminal 20B, and transmits content sent by user B through input to the input unit 22 of the user terminal 20B to the user terminal 20A. The control unit 11 sets settings for the talk room related to money transfers to user A (settings for receiving money transfers, settings for sending money, etc.). The server 10 receives from the user terminal 20B information related to money transfers from user B to user A (remittance destination, remittance source, remittance amount, remittance account, etc.) based on the settings for money transfers and input by user B to the input unit 22 of the user terminal 20B for the talk room. The control unit 11 executes processing related to money transfers (remittance processing) based on the information related to money transfers.

As a result, according to the information processing of this embodiment, by way of example and not limitation, when executing a remittance process, the server 10 does not need to determine the remittance settings for each user, thereby improving the processing speed of the server 10. In addition, for users who use talk rooms, remittances can be made within the talk room, improving user convenience.

According to this embodiment, the settings related to remittances set by the control unit 11 include settings related to user A being the administrator of the talk room (such as the person who created the talk room). As a result, according to the information processing of this embodiment, by way of example and not limitation, settings related to remittances are set for the administrator, so that the number of settings related to remittances by user A can be reduced, thereby reducing the amount of processing by the user terminal 20. In addition, the amount of information sent from the user terminal 20 to the server 10 can be reduced, thereby improving the processing speed of the server 10.

According to this embodiment, the control unit 11 sets the settings related to remittance based on the creation of a talk room by user A. As a result, according to the information processing of this embodiment, by way of example and not limitation, the settings related to remittance are set when a talk room is created, so that the amount of communication between the server 10 and the user terminal 20 regarding the settings related to remittance can be reduced, thereby improving the processing speed of the server 10.

According to this embodiment, the settings related to money transfer set by the control unit 11 include settings related to enabling money transfer to user A based on input to the input unit 22 of the user terminal 20 by a user participating in the talk room. As a result, according to the information processing of this embodiment, by way of example and not limitation, it is possible to set users who can transfer money in a talk room, thereby improving the convenience of the talk room.

According to this embodiment, the settings regarding money transfers set by the control unit 11 include a setting regarding the inability to transfer money from a user participating in a chat room to user B, who is also a participant. As a result, according to the information processing of this embodiment, by way of example and not limitation, by setting money transfers to be possible only to specific users, the processing for identifying the transfer destination in the server 10 can be reduced, thereby improving the processing speed of the server 10. In addition, since rules regarding money transfers can be determined in the chat room, it is possible to prevent users from misusing the chat room.

According to this embodiment, the server 10 stores in the storage unit 15 the relationship between user A and a user other than user A. User A and user B do not have at least one of the following relationships: a friend relationship, a relationship in which user A is followed by user B, and a relationship in which user A follows user B. As a result, according to this embodiment, by way of example and not limitation, a talk room can be joined even if there is no specific relationship between the users who participate in the talk room, and therefore the processing required for approval by the server 10 can be reduced, thereby improving the processing speed of the server 10. In addition, the convenience of the talk room can be improved because a user can participate in the talk room without considering relationships with other users.

According to this embodiment, the server 10 does not include any indication regarding settings of friend relationships, followed relationships, and following relationships in the image of the talk room. As a result, according to this embodiment, by way of example and not limitation, a user participating in a talk room is not allowed to build a specific relationship with other users, so that the amount of processing and processing items in the server 10 can be reduced, and the processing speed of the server 10 can be improved.
Second Embodiment

The outline of this embodiment will be described. In this embodiment, as an example and not a limitation, a user who can receive remittances in a chat room can set a setting for receiving remittances for other users. In the following, as an example and not a limitation, a setting for receiving remittances in a chat room is referred to as a "remittance receipt setting". In addition, this embodiment may include, as an example and not a limitation, a setting for sending remittances in a chat room (remittance setting, as an example and not a limitation), a setting for receiving remittances can be set for other users by a user who has a remittance receipt setting. In the following, as an example and not a limitation, an administrator who has a remittance receipt setting will set a remittance receipt setting for a participant. In this embodiment, as an example and not a limitation, the administrator's user terminal 20 designates one of the participants and transmits at least one of information on the setting of the remittance receipt setting (receive setting information, as an example and not a limitation) or information on the setting of the remittance setting (remittance setting information, as an example and not a limitation) to the server 10. Based on this information, the server 10 sets at least one of the remittance receipt setting or remittance setting for the user ID of one of the participants. Note that the contents described in this embodiment can be appropriately applied to each of the other embodiments.

This embodiment will be described in detail with reference to Figs. 9 to 12. Fig. 9 is a flowchart showing information processing according to the second embodiment. Fig. 10 is a diagram showing an overview of information processing according to the second embodiment. Fig. 11 is a diagram showing an example of talk room information D12. Fig. 12 is a diagram showing an example of an image T8 including content indicating completion of settings. In this embodiment, the same components as those in the above-mentioned embodiment are appropriately denoted with the same reference numerals and their description will be omitted or simplified. Note that Fig. 9 is a flowchart assuming that the steps S111 to S141 in Fig. 2 have been completed. In other words, it is assumed that the remittance receipt setting is set for the user ID of the administrator (here, user A). The procedure for user A to set the remittance receipt setting for user B's user ID via user terminal 20A will be described below.

First, in step S211, when an input is made to the input unit 22 for the icon PL in the display area 28 shown in FIG. 2A(b), the user terminal 20A determines that the icon PL has been selected, and displays a selection image T6 including a remittance setting icon Tb as shown in FIG. 10(a) in the display area 28. Then, when an input is made to the input unit 22 for the icon "receive setting", the control unit 21 determines that "receive setting" has been selected. Then, by way of example and not of limitation, the control unit 21 refers to the talk room information D22 and displays a receive setting image T7 in FIG. 10(b) in the display area 28. The receive setting image T7 in FIG. 10(b) includes, by way of example and not of limitation, a remittance recipient setting unit T71 that displays the name of a user corresponding to a user ID associated with the talk room, and a setting confirmation unit T72. The remittance recipient setting unit T71 may, for example and not limitation, display the user's name in a predetermined display format (for example and not limitation, a pull-down) when an input is made to the input unit 22. The remittance recipient setting unit T71 may, for example and not limitation, be a text box that accepts input of the user's name. Furthermore, the remittance recipient setting unit T71 may, for example and not limitation, include check boxes that are displayed corresponding to each of a plurality of user's names. Here, for example and not limitation, it is assumed that "User B" is set in the remittance recipient setting unit T71 of the user terminal 20A.
Then, by way of example and not limitation, the control unit 21 confirms the receipt setting information in the setting confirmation unit T72 displayed in the display area 28 when there is an input to the input unit 22. Then, in step S212, the user terminal 20A transmits a receipt setting request including the receipt setting information to the server 10.

Next, in step S221, the server 10 stores the receipt setting request in the storage unit 15. Based on the receipt setting request, the server 10, as an example and not a limitation, compares the user ID of user A with the user ID of [Remittance Recipient ID] in the talk room information D12 shown in FIG. 3A. That is, as an example and not a limitation, the control unit 11 confirms that the receipt setting request has been sent from the user terminal 20 of the user for whom the remittance receipt setting has been set. As an example and not a limitation, the control unit 11 updates the talk room information D12 (as an example and not a limitation, the receipt setting process) when the user ID of user A matches the user ID of [Remittance Recipient ID] as a result of the comparison. Specifically, as an example and not a limitation, the control unit 11 compares the talk room information D12 shown in FIG. 3A and registers the user ID of user B in [Remittance Recipient ID] as in the talk room information D12 shown in FIG. 11.

Next, in step S231, the server 10 transmits a setting completion notification including the updated talk room information D12 to each user terminal 20. Based on the setting completion notification, the user terminal 20A displays an image T8 including content Q4 (as an example and not a limitation, the remittance receiving setting has been set for user B) indicating the setting completion as shown in FIG. 12. As an example and not a limitation, the user terminal 20B and the user terminal 20C also display an image including content Q4. Note that, as an example and not a limitation, the server 10 may or may not not transmit the setting completion notification to each user terminal 20. Also, as an example and not a limitation, the server 10 may transmit the setting completion notification only to the user terminal 20 of the user who has set the remittance receiving setting. In this case, the user terminal 20 that has received the setting completion notification may display an image including a message indicating the setting completion in the display area 28.

In the above, the control unit 11 has been described as registering the user ID of user B in [Remittance Recipient ID] (receiving change process) as in the talk room information D12 shown in FIG. 11, but this is not limiting. As a non-limiting example, the control unit 11 may execute the process to set the user ID of user B in [Remittance Recipient ID] in addition to the user ID of user A for whom remittance receiving settings have been set. In this case, the user IDs of user A and user B are registered in [Remittance Recipient ID]. In this case, as a non-limiting example, the user terminal 20A may, or may not, display an image including content indicating the completion of settings (as a non-limiting example, a new remittance receiving setting has been set for user B) based on the setting completion notification.

In the above description, the administrator who has been set with remittance receipt settings sets remittance receipt settings for the participants, but this is not limiting. For example and not limiting, the control unit 11 may execute a process in which a participant who has been set with remittance receipt settings sets remittance receipt settings for other participants.
<Fourth Modification>

The information processing according to the fourth modified example will be described with reference to Figs. 13 and 14. Fig. 13 is a diagram showing an overview of the information processing according to the fourth modified example. Fig. 14 is a diagram showing an example of the talk room information D12 according to the fourth modified example. The information processing according to the fourth modified example is a form in which a user participating in a talk room executes a process of canceling the remittance receipt setting of a user for whom the remittance receipt setting has been set. Here, "canceling the remittance receipt setting" refers to, by way of example and not by way of limitation, deleting the user ID from [remittance recipient ID] in the talk room information D12 in the server 10, i.e., making the user unable to receive remittances. In the following, it is assumed that the remittance receipt setting is set to the user ID of the administrator (here, user A), and a procedure will be described in which user A cancels the remittance receipt setting set for himself/herself via the user terminal 20A.

First, when an input is made to the input unit 22 for the icon PL in the display area 28 shown in Fig. 2A(b), the user terminal 20A determines that the icon PL has been selected, and displays a selection image T9 including a remittance setting icon Tb as shown in Fig. 13(a) in the display area 28. Then, when an input is made to the input unit 22 for the icon "cancel receipt", the control unit 21 determines that "cancel receipt" has been selected.
Then, the control unit 21, by way of example and not limitation, refers to the talk room information D22 and causes the display area 28 to display the receipt cancellation image T10 of FIG. 13(b). The receipt cancellation image T10 includes, by way of example and not limitation, a remittance recipient cancellation section T101 that displays the name of a user for whom a remittance receipt setting is set in the talk room, and a cancellation confirmation section T102. By way of example and not limitation, the remittance recipient cancellation section T101 may display the name of the user in a predetermined display format (by way of example and not limitation, a pull-down) when an input is made to the input section 22. By way of example and not limitation, the remittance recipient cancellation section T101 may be a text box or the like that accepts input of the name of the user. In addition, by way of example and not limitation, the remittance recipient setting section T101 may include check boxes that are displayed so as to correspond to the names of each of a plurality of users. Here, by way of example and not limitation, it is assumed that "user A" is set in the remittance recipient cancellation section T101 of the user terminal 20A. Then, as an example and not a limitation, the control unit 21 causes the cancellation confirmation unit T102 to confirm the receipt cancellation information when there is an input to the input unit 22. Then, the user terminal 20A transmits a receipt cancellation request including the receipt cancellation information to the server 10.

Next, the server 10 stores the receipt cancellation request in the storage unit 15. Based on the receipt cancellation request, the server 10, by way of example and not limitation, compares the user ID of user A with the user ID of the [remittance recipient ID] in the talk room information D12. That is, by way of example and not limitation, the control unit 11 confirms that the receipt cancellation request was sent from the user terminal 20 of a user for whom remittance receipt settings are set. By way of example and not limitation, the control unit 11 updates the talk room information D12 when the user ID of user A matches the user ID of the [remittance recipient ID] as a result of the comparison (by way of example and not limitation, a receipt cancellation process). Specifically, by way of example and not limitation, the control unit 11 compares the talk room information D12 shown in FIG. 3A and deletes user A from the [remittance recipient ID] as in the talk room information D12 shown in FIG. 14.

In the above, it has been described that the remittance receipt setting is cancelled by the administrator, but this is not limited to this. As a non-limiting example, processing may be executed so that the remittance receipt setting is cancelled by a participant. In this case, as a non-limiting example, the server 10 cancels the remittance receipt setting of a specific user based on a receipt cancellation request received from the participant's user terminal 20.

Next, the server 10 transmits a cancellation completion notification including the updated talk room information D2 to each user terminal 20. Based on the cancellation completion notification, the user terminal 20A displays an image including content indicating cancellation completion (as a non-limiting example, a message saying "Settings for receiving remittances from user A have been cancelled") in the display area 28. As a non-limiting example, the user terminal 20B and the user terminal 20C also similarly display an image including the above content.
<Fifth Modification>

The information processing according to the fifth modified example will be described with reference to Fig. 15 and Fig. 16. Fig. 15 is a diagram showing an overview of the information processing according to the fifth modified example. Fig. 16 is a diagram showing an example of an image T13 including content related to receipt change. The information processing according to the second modified example is a form in which a user who has a remittance receipt setting set in a chat room executes a process (a receipt change process, by way of example and not limitation) to have another user change his/her remittance receipt setting.
Then, the server 10 executes a process (value transfer process) for transferring a value corresponding to an amount of remittance received by a certain user from one user to another user, by way of example and not by way of limitation. The following describes a procedure in which user A, who has remittance receipt settings set, changes his/her remittance receipt settings to user B via user terminal 20A.

First, when an input is made to the input unit 22 for the icon PL of the display area 28 shown in FIG. 2A(b), the user terminal 20 of the recipient user determines that the icon PL has been selected, and displays a selection image T11 including a remittance setting icon Tb as shown in FIG. 15(a) in the display area 28. Then, when an input is made to the input unit 22 for the icon "change receipt", the control unit 21 determines that "change receipt" has been selected. Then, by way of example and not limitation, the control unit 21 refers to the talk room information D22 and displays the receipt change image T12 of FIG. 15(b) in the display area 28. The receipt change image T12 includes, by way of example and not limitation, a change source setting section T121 indicating the source of the change to the remittance receipt setting, a change destination setting section T122 indicating the destination of the change to the remittance receipt setting, and a change completion section T123 for confirming the setting change. The control unit 21, by way of example and not of limitation, refers to the talk room information D22 and causes the change source setting unit T121 to display an icon with the name of the user to whom the remittance receipt setting is set. The control unit 21, by way of example and not of limitation, refers to the talk room information D22 and causes the change destination selection unit T122 to selectably display an icon with the name of the user to whom the remittance receipt setting is to be changed. By way of example and not of limitation, the change destination setting unit T122 may display the name of the user in a predetermined display format (by way of example and not of limitation, a pull-down) when an input is made to the input unit 2 ... be a text box or the like that accepts input of the name of the user. Here, by way of example and not of limitation, it is assumed that "user B" is set in the change destination setting unit T122 of the user terminal 20A. Then, by way of example and not of limitation, the control unit 21 confirms the setting change information for the change completion unit T123 when an input is made to the input unit 22. Then, the user terminal 20A transmits a setting change request including the setting change information to the server 10.

Next, the server 10 stores the setting change request in the memory unit 15. Based on the setting change request, the server 10 compares, by way of example and not by way of limitation, the user ID of the user A who is making the change with the user ID of the [remittance recipient ID] in the talk room information D12. As a non-limiting example, if the comparison results in a match between the user ID of user A and the user ID of the [remittance recipient ID], the control unit 11 executes a receipt change process to update the talk room information D12.

Next, the control unit 11 refers to the remittance history information D15 as shown in FIG. 3D as an example and not a limitation, and identifies information related to remittances associated with the user ID of user A until the receipt change process is completed. Specifically, as an example and not a limitation, when the receipt change process is completed at 11:01 on January 1, 2020, the control unit 11 refers to the remittance history information D15 and identifies "1,000" of the user ID (here, user B) who remitted at 10:00 on January 1, 2020 and "1,000" of the user ID (here, user C) who remitted at 11:00 on January 1, 2020. Then, the control unit 11 refers to the remittance account information D14, and executes a value transfer process that updates the remittance account information D31 of the payment server 30 corresponding to the remittance account associated with the user ID set as the change destination in order to allocate the value indicating the identified total remittance to the value corresponding to the remittance account.

Next, the server 10 receives the updated remittance account information D31 from the payment server 30, for example and not limitation. The server 10 transmits a setting change notification including the remittance account information D31 to the user terminal 20, for example and not limitation. Based on the setting change notification, the user terminal 20A displays an image T13 in the display area 28, including a content Q5 indicating the completion of the setting change (for example and not limitation, the remittance receiving setting has been changed from user A to user B) and a content Q6 indicating the content of the remittance related to the transfer process (for example and not limitation, 2,000 yen has been remitted to user B), as shown in FIG. 16. For example and not limitation, the user terminals 20B and 20C also display images including the content Q5 and the content Q6 in the display area 28 in the same manner.

In the above, it has been described that when the receipt change process is completed, a value transfer process is executed to allocate the value associated with the user ID of user A until the receipt change process is completed to the value associated with the changed user B, but this is not limited to this. As a non-limiting example, the control unit 11 may execute a value transfer process that updates the remittance account information D31 of the payment server 30 so that only the value corresponding to the remittance process to user A executed after the receipt change process is completed is allocated to the value associated with the changed user B.
===Effect===

According to this embodiment, the server 10 sets settings related to remittances to other users other than user A based on input by user A to the input unit 22 of the user terminal 20A. As a result, according to the information processing of this embodiment, by way of example and not limitation, by granting authority to set settings related to remittances only to a specific user (here, user A), it is possible to reduce information processing related to management of the talk room, thereby improving the processing speed of the server 10. In addition, since user A can set settings related to remittances to other users as necessary, it is possible to improve the convenience of the talk room.

According to this embodiment, the server 10 cancels the settings related to remittances set for user A based on an input by user A to the input unit 22 of the user terminal 20A. As a result, according to the information processing of this embodiment, by way of example and not limitation, the authority to cancel the settings related to remittances can be granted only to a specific user (here, user A), thereby reducing information processing related to talk room management, and improving the processing speed of the server 10. In addition, because user A can cancel the settings related to remittances as necessary, unnecessary remittances can be prevented, thereby improving the security of the talk room.

According to this embodiment, when the server 10 sets settings related to money transfer to another user different from user A, the server 10 executes a process of transferring the amount of money already transferred from user B to user A from user A to the other user. As a result, according to the information processing of this embodiment, by way of example and not limitation, a transfer of money from user A to another user is executed without requiring a procedure related to a transfer of money from user A to the other user in the user terminal 20A, so that the amount of information processing of the user terminal 20 can be reduced, and therefore the amount of information processing of the server 10 can also be reduced. Furthermore, since the procedure related to a transfer of money from user A to another user can be reduced, the convenience of the talk room can be improved.
Third Embodiment

The following describes an overview of this embodiment. In this embodiment, as an example and not a limitation, the server 10 receives a participation request from the user terminal 20 of a participant who wishes to participate in a talk room, and approves the participant's participation in the talk room if the participant meets certain conditions. In the following, as an example and not a limitation, the server 10 is described as approving the participation of participants (here, user B and user C) in the talk room. Note that the contents described in this embodiment can be applied to the other embodiments as appropriate.

This embodiment will be described in detail with reference to FIG. 17. FIG. 17 is a flowchart showing information processing according to the third embodiment. In this embodiment, the same components as those in the above-described embodiment are appropriately designated by the same reference numerals, and their description will be omitted or simplified. Note that FIG. 17 is a flowchart that assumes that the steps from S111 to S132 in FIG. 2 have been completed.

First, in step S341, the server 10 accepts the participation request, and stores the participation request in the memory unit 15, as an example and not a limitation. The server 10 generates an approval confirmation image T14, as an example and not a limitation. Next, in step 342, the server 10 transmits the approval confirmation image T14 shown in FIG. 18, as an example and not a limitation, to the user terminal 20B that sent the participation request.

Next, in step S351, the user terminal 20B displays the approval confirmation screen T14 shown in FIG. 18 in the display area 28, as an example and not a limitation. The approval confirmation screen T14 includes, as an example and not a limitation, a user name input field T141 that accepts input of the user name of user B requesting to join the talk room, and an approval request execution unit T142. As an example and not a limitation, when there is input in the input unit 22 for the user name input field T141 (a text box, as an example and not a limitation) displayed in the display area 28, the control unit 21 displays the input text data in the user name input field T141. Then, as an example and not a limitation, when there is input in the input unit 22 for the approval request execution unit T142 displayed in the display area 28, the control unit 21 confirms information regarding approval (approval request information, as an example and not a limitation). Then, in step S352, the user terminal 20B transmits an approval request including the approval request information to the server 10.

Next, in step 361, the server 10 stores the approval request in the memory unit 15. The server 10 then compares the user name included in the approval request information with the "user name" of the personal identification information D17 shown in FIG. 19 (approval process, as an example and not a limitation).

Here, the personal identification information D17 will be described. The personal identification information D17 is created by a personal identification procedure, for example and not limitation. The personal identification procedure is, for example and not limitation, a procedure in which the server 10 registers the user's personal information before the user makes a remittance processing request. Specifically, for example and not limitation, the server 10 transmits an input request image to the user terminal 20. The input request image is, for example and not limitation, an image in which information about a bank account or information about a driver's license (which may include an image, etc.) is input. The user terminal 20 accepts input to the input unit 22 for the input request image, and, for example and not limitation, registers information corresponding to each item in FIG. 19 to generate the personal identification information D17. The user terminal 20 transmits the personal identification information D17 to the server 10, for example and not limitation. FIG. 19 is a diagram showing an example of the personal identification information D17. The personal identification information D17 includes, for example and not limitation, the items [User ID], [User name], [Password], [Real name], [Date of birth], [Address], [Telephone number], and [Email address]. [User ID] is, by way of example and not limitation, identification information of a user included in a group corresponding to each chat room. [User name] is, by way of example and not limitation, a name used in a messaging service that is associated with [User ID] and set by the user. [Password] is, by way of example and not limitation, associated with [User ID] and is a combination of letters, symbols, and numbers. [Real name] is, by way of example and not limitation, the user's name that is associated with [User ID]. [Date of birth] is, by way of example and not limitation, the user's date of birth that is associated with [User ID]. [Address] is, by way of example and not limitation, the user's address that is associated with [User ID]. [Phone number] is, by way of example and not limitation, the user's mobile phone number, landline phone number, or the like that is associated with [User ID]. [Email address] is, by way of example and not limitation, the user's email address that is associated with [User ID].

Next, in step 362, as an example and not a limitation, if the user name included in the approval request information matches the "user name" of the [user name] associated with the user ID of user B, the server 10 registers the user ID of user B in [user ID] of the talk room information D12 (see FIG. 3A). As an example and not a limitation, when the user ID of user B is registered in the talk room information D12 in the server 10, the user terminal 20B may receive content information D13 from the server 10 and display an image T1 including content Q1 as shown in FIG. 2A (b) in the display area 28. As an example and not a limitation, steps S341 to S361 are similarly executed for the user terminal 20C.

In the above description, the approval confirmation image T14 has been described as having a user name input field 141, but is not limited thereto. As a non-limiting example, the approval confirmation image T14 may be an image including an input field for inputting at least one of a user ID, a password, a real name, a date of birth, an address, a telephone number, and an email address, instead of the user name input field T141. That is, in the present embodiment, as a non-limiting example, the server 10 receives from the user information that can identify an individual in a messaging service, and approves the user's participation in the talk room if the information satisfies a predetermined condition.
<Sixth Modification>

The information processing according to the sixth modified example will be described with reference to FIG. 20. FIG. 20 is a diagram showing an example of a remittance completion image T15. The information processing according to the sixth modified example is a form in which, when the remittance process is completed in the server 10, the server 10 transmits information capable of uniquely identifying the user who sent the remittance to the user who received the remittance. In the following description, the user who received the remittance will be referred to as user A, and the user who sent the remittance will be referred to as user B.

First, when the remittance process is completed in the server 10, the server 10, by way of example and not limitation, refers to the personal identification information D17 generated by the identity verification procedure described above to identify the "real name" associated with user B. The server 10 transmits a remittance completion image T15 including the "real name" of user B to the user terminal 20A, by way of example and not limitation. The user terminal 20A displays the remittance completion image T15 shown in FIG. 20 in the display area 28. The remittance completion image T15 is an image including, by way of example and not limitation, a user display section T151 in which the real name of user B is displayed, a remittance amount display section T152 in which the remittance amount is displayed, and a confirmation completion section T153.
As an example, and not as a limitation, when an input is made to the input unit 22 for the icon of the confirmation completion section T153, the user terminal 20A determines that the confirmation completion section T153 has been selected and erases the remittance completion screen T15 from the display area 28.

For example and not for limitation, the server 10 may create a remittance completion image T151 that further includes a nickname used when joining the talk room. Also, for example and not for limitation, the server 10 may refer to the personal identification information D17 to identify an email address associated with the user ID of the user A who received the remittance, and send a transmission completion notification including the content to that email address.
===Effect===

According to this embodiment, the server 10 receives information regarding approval to allow user B to participate in the talk room from the user terminal 20B of user B. The server 10 executes a process to allow user B to participate in the talk room based on the information regarding approval. As a result, according to the information processing of this embodiment, by way of example and not limitation, the server 10 can ensure the safety of the talk room and improve security by making user participation in the talk room approval-based.

According to this embodiment, when the server 10 performs processing related to a remittance from user B to user A, it transmits name information in the identity verification procedure of user B and information related to the completion of the remittance from user B to user A to the user terminal 20A of user A. As a result, according to the information processing of this embodiment, by way of example and not limitation, the user terminal 20A of user A who receives the remittance can receive the real name of the remitter and a notification indicating that the remittance has been completed, thereby improving user convenience and improving the security of remittances in talk rooms.
===Fourth Embodiment===

The following describes an overview of this embodiment. In this embodiment, by way of example and not limitation, the server 10 deletes "talk room IDs" that satisfy a predetermined condition from the [talk room ID] in the talk room information D12. Here, the predetermined condition is, by way of example and not limitation, that a predetermined amount of time has passed since the date and time the talk room was created, that a preset date and time has passed, that the administrator has left the talk room, etc.

This embodiment will be described in detail with reference to Figs. 21 and 22. Fig. 21 is a flowchart showing information processing according to the fourth embodiment. Fig. 22 is a diagram showing an overview of information processing according to the fourth embodiment. In this embodiment, the same components as those in the above-mentioned embodiment are appropriately denoted with the same reference numerals, and the description thereof will be omitted or simplified. Note that Fig. 21 is a flowchart assuming that the procedures from S111 to S151 in Fig. 2 have been completed. In the following, as an example and not a limitation, an administrator (here, user A) who has set the remittance receiving setting will set a predetermined condition for deleting the talk room. Note that, as an example and not a limitation, a participant can also set a predetermined condition. Also, as an example and not a limitation, the server 10 may automatically delete the talk room a predetermined time (e.g., 24 hours) after the talk room is created. Also, as an example and not a limitation, the user (operator) of the server 10 may arbitrarily set the timing for deleting the talk room. Also, the contents described in this embodiment can be appropriately applied to each of the other embodiments.

First, in step S451, when an input is made to the input unit 22 for the icon PL in the display area 28 shown in FIG. 2A(b), the user terminal 20A determines that the icon PL has been selected, and displays a selection image T16 including a remittance setting icon Tb shown in FIG. 22(a) in the display area 28. Then, when an input is made to the input unit 22 for the icon "disappearance condition", the control unit 21 determines that "disappearance condition" has been selected. Then, by way of example and not of limitation, the control unit 21 refers to the disappearance information D12 and displays the disappearance condition image T17 in FIG. 22(b) in the display area 28. The disappearance condition image T17 includes, by way of example and not of limitation, a disappearance item setting unit T171 that selectively displays the items of the disappearance condition, a disappearance date setting unit T172 for setting the disappearance date, a disappearance time setting unit T173 for setting the disappearance time, and a condition completion unit T174. As a non-limiting example, when an input is made to the input unit 22, the control unit 21 displays the extinction item setting unit T171 displayed in the display area 28 so that "time" or "user" can be selected. Then, as a non-limiting example, when an input is made to the input unit 22 for the extinction date setting unit T172 displayed in the display area 28, the control unit 21 displays the input text data in the extinction date setting unit T172. Then, as a non-limiting example, when an input is made to the input unit 22 for the extinction time setting unit T173 displayed in the display area 28, the control unit 21 displays the input text data in the extinction time setting unit T173. Note that, as a non-limiting example, the extinction date setting unit T172 and the extinction time setting unit T173 may display the date or time in a predetermined display format (as a non-limiting example, a pull-down) when an input is made to the input unit 22. The extinction date setting unit T172 and the extinction time setting unit T173 may be, as a non-limiting example, a text box that accepts input of a date or time. Then, as a non-limiting example, when an input is made to the input unit 22 for the condition completion unit T174 displayed in the display area 28, the control unit 21 confirms information regarding the disappearance condition (as a non-limiting example, disappearance condition information). Then, in step S452, the user terminal 20A transmits the disappearance condition information to the server 10.

Next, in step 461, the server 10 stores the extinction condition information in the storage unit 15. The storage unit 15 stores the extinction condition information as the extinction condition information D18 shown in FIG. 23. FIG. 23 is a diagram showing an example of the extinction condition information D18. The extinction condition information D18 includes items of [talk room ID], [creation date and time], and [extinction condition], as an example and not a limitation. [Talk room ID] is identification information of each talk room, as an example and not a limitation. [Creation date and time] is the date and time when the talk room was created, which is associated with the [talk room ID], as an example and not a limitation. [Extinction condition] is the extinction condition included in the extinction condition information, which is associated with the [talk room ID], as an example and not a limitation. Specifically, as an example and not a limitation, the talk room "tr01" is set to extinguish at "January 5, 2020, 10:00". As a non-limiting example, the chat room "tr02" is set to disappear "20 hours after" "January 2, 2020, 10:00." As a non-limiting example, the chat room "tr03" is set to disappear when user A, the administrator, leaves the chat room.

Next, in step 471, the control unit 11 of the server 10 determines whether the disappearance condition is satisfied in each talk room. In step 481, the control unit 11 executes a disappearance process when it is determined that the disappearance condition is satisfied, for example and not by way of limitation. The disappearance process is a process of deleting the talk room ID from the talk room information D12, for example and not by way of limitation. Next, in step 482, the server 10 transmits the talk room information D12 to the user terminal 20, for example and not by way of limitation. Then, in the user terminal 20, when an image TL of a list of talk rooms is displayed in the display area 28, an icon of the talk room (here, "Coffee Party") from which the talk room ID has been deleted may be displayed in the image TL. In this case, for example and not by way of limitation, a message indicating that the talk room cannot be used, such as "Closed", may be displayed together with the icon "Coffee Party". Furthermore, in the user terminal 20, for example and not by way of limitation, when an input is made to the input unit 22 for the icon "Coffee Party", the user terminal 20 determines that "Coffee Party" has been selected. Then, the user terminal 20, by way of example and not limitation, refers to the talk room information D22 and determines that there is no talk room ID corresponding to “Coffee Party.” The control unit 21, by way of example and not limitation, may generate a message indicating that the talk room “Coffee Party” is unavailable and display the message in the display area 28.
===Effect===

According to the present embodiment, the server 10 deletes a talk room when a set period of time has elapsed or based on a set time. As a result, according to the information processing of the present embodiment, by way of example and not limitation, it is possible to reduce the amount of information processing at the user end 20. Furthermore, according to the information processing of the present embodiment, by way of example and not limitation, it is possible to eliminate the operational burden of a user in deleting a talk room, thereby improving user convenience.
Fifth Embodiment

The outline of this embodiment will be described. In this embodiment, by way of example and not limitation, the server 10 is capable of allowing users participating in a chat room to report other users. In other words, the server 10 is configured to change settings related to money transfers by a participant in a chat room reporting the money transfer recipient to the server 10 based on information related to the money transfer recipient. Here, the settings related to money transfer may be, by way of example and not limitation, a setting to temporarily prohibit money transfers in a chat room, a setting to permanently prohibit money transfers in a chat room, a setting to temporarily prohibit money transfers in a message service, a setting to permanently prohibit money transfers in a message service, and the like, in addition to setting the user IDs of the administrator and participants described above in the [Money Transfer Recipient ID] or [Money Transfer Sender ID] fields. Hereinafter, by way of example and not limitation, information related to a report is referred to as "report information", the money transfer recipient is User A, and the participant who transmits report information about User A to the server 10 is User B. The contents described in this embodiment may be appropriately applied to each of the other embodiments.

This embodiment will be described in detail with reference to Figs. 24 and 25. Fig. 24 is a flowchart showing information processing according to the fifth embodiment. Fig. 25 is a diagram showing an overview of information processing according to the fifth embodiment. In this embodiment, the same components as those in the above-mentioned embodiments are appropriately denoted with the same reference numerals, and their description will be omitted or simplified. Note that Fig. 24 is a flowchart assuming that the procedures from S111 to S151 in Fig. 2 have been completed. Below, a procedure for user B to report user A's actions in a talk room via user terminal 20B will be described.

First, in step S551, when an input is made to the input unit 22 for the icon PL in the display area 28 shown in FIG. 2A(c), the user terminal 20B determines that the icon PL has been selected, and displays a selection image T18 including a remittance setting icon Tb as shown in FIG. 25(a) in the display area 28. Then, when an input is made to the input unit 22 for the icon "report", the control unit 21 determines that "report" has been selected. Then, by way of example and not limitation, the control unit 21 refers to the talk room information D22 and displays a report setting image T19 in FIG. 25(b) in the display area 28. The report setting image T19 in FIG. 25(b) includes, by way of example and not limitation, a target person display section T191, a report reason display section T192, and a report confirmation section T193. The target display section T191 displays, by way of example and not limitation, the name of the user corresponding to the user ID set in [remittance recipient ID]. For example and not limitation, the target display unit T191 may display the names of multiple users in a predetermined display format (for example and not limitation, a pull-down menu) when multiple remittance recipients are set in a chat room. Furthermore, for example and not limitation, the control unit 21 may display check boxes or the like corresponding to each user in the display area 28 so that two or more of the names of the multiple users can be selected when multiple remittance recipients are set in a chat room. For example and not limitation, the report reason display unit T192 may display the report reason in a predetermined display format (for example and not limitation, a pull-down menu) when an input is made to the input unit 22 in response to the report reason display unit T192. For example and not limitation, the report reason display unit T192 may be a text box or the like that accepts input of the contents of the report. For example and not limitation, when the control unit 21 determines that an icon in the report reason display unit T192 has been selected, the control unit 21 displays a list showing candidates for the report reason in the display area 28 as shown in FIG. 25(b). Then, when an input is made to the input unit 22 for a predetermined icon displayed in the list, the control unit 21 determines that the icon (here, illegal act) has been selected. Then, as a non-limiting example, the control unit 21 confirms the notification information in the notification confirmation unit T193 displayed in the display area 28 when there is an input to the input unit 22. Then, in step S552, the user terminal 20A sends a receipt setting request including the receipt setting information to the server 10.

Next, in step S561, the server 10 stores the report information in the storage unit 15. The server 10, as an example and not a limitation, collates the user ID of user B with the user ID of [user ID] of the talk room information D12 shown in FIG. 3A based on the report information. That is, the control unit 11, as an example and not a limitation, confirms that the report information has been sent from the user terminal 20 of the user participating in the talk room. The server 10, as an example and not a limitation, executes a restriction setting process. The restriction setting process, as an example and not a limitation, is a process of setting a restriction on the user ID of the target of the report (here, user A) based on the report information. In addition, the restriction setting process may be, as an example and not a limitation, a process of setting a restriction on the user ID of user A by determining whether or not a predetermined condition is satisfied. Here, the predetermined condition, as an example and not a limitation, is that the number of times the report has been made exceeds a predetermined threshold, that the content sent by the target of the report is determined to be fraudulent based on the result of character analysis, and the like. The server 10, as an example and not a limitation, imposes a restriction on the user ID of user A as in the first restriction information D19A shown in FIG. 26. In addition, as a non-limiting example, the server 10 may impose restrictions on user IDs for each talk room ID.
Furthermore, as a non-limiting example, the server 10 may impose a restriction on user A so that user A cannot receive remittances in the talk room by deleting the user ID of user A from the [Remittance Recipient ID] field in the talk room information D12. Furthermore, as a non-limiting example, the server 10 may cause user A to leave the talk room by deleting the user ID of user A from the talk room information D12. In this case, as a non-limiting example, the server 10 may refer to the remittance history information D15 and execute the above-described value transfer process so that the remittance setter (here, user A) refunds money to users who have previously remitted money to the remittance setter.

Next, in step S562, the server 10 transmits a setting completion notification including the first restriction information D19A to each user terminal 20. By way of example and not limitation, each user terminal 20 displays an image including content related to restrictions (e.g., "Restrictions have been set for user A") based on the setting completion notification.

In the above, the settings related to remittance are set for the remittance recipient. However, as an example and not a limitation, the server 10 may set the settings related to remittance for users (remitters) who can remit based on the report information. The restriction setting process in S561 in this case will be described below. As an example and not a limitation, the server 10 sets restrictions on the user IDs of the participants in the talk room (users B and C in this case) based on the report information. In this case, as an example and not a limitation, the target display unit T191 displays the name of the user corresponding to the user ID set in [User ID]. That is, as an example and not a limitation, the target display unit T191 may display all users participating in the talk room. The report reason display unit T192 and the report confirmation unit T193 are the same as those described above, and therefore will not be described. Then, as an example and not a limitation, the server 10 imposes a restriction on the user IDs of the reported users (users B and C in this case) that prohibits (makes impossible) remittance, as shown in the second restriction information D19B shown in FIG. 27. In addition, as a non-limiting example, the server 10 may restrict the reported user from sending money by deleting the user ID of the reported user from the [Remitter ID] in the talk room information D12.

In addition, in the above description, a setting related to money transfer is set for the money transfer recipient or the money transfer sender (here, a setting for temporarily prohibiting money transfer in a chat room or the like), but this is not limited thereto. For example and not limitation, the server 10 may restrict the reported money transfer recipient or the money transfer sender to at least temporarily suspend the use of the user ID used in the messaging service. In this case, for example and not limitation, the server 10 restricts all actions of the restricted user using the messaging service, such as receiving and sending money transfers, and sending and receiving content.
===Effect===

According to this embodiment, the server 10 receives notification information about user A (administrator) from user B, and changes the settings related to remittances to user A to predetermined settings based on the information about user A (administrator). As a result, according to the information processing of this embodiment, by way of example and not limitation, the server 10 can change the settings related to remittances in the talk room based on information acquired from the user's user terminal 20, thereby improving the security of the talk room.

According to this embodiment, the server 10 may receive report information from user B about user A (the administrator), and change the settings to prohibit remittances to user A based on the information about user A (the administrator). As a result, according to the information processing of this embodiment, by way of example and not limitation, the settings can be changed based on information acquired from the user's user terminal 20 so that user A cannot receive remittances in the talk room, thereby preventing user A from committing fraudulent acts in the talk room and improving the security of the talk room.

According to this embodiment, the server 10 may receive report information about user A (the administrator) from user B, and may at least temporarily suspend the use of user A's account based on the information about user A (the administrator). As a result, according to the information processing of this embodiment, by way of example and not limitation, it is possible to suspend an action related to remittance by user A in the talk room based on information acquired from the user's user terminal 20, thereby preventing user A from engaging in fraudulent activities in the talk room, thereby improving the security of the talk room.
Sixth Embodiment

The outline of this embodiment will be described. In this embodiment, by way of example and not limitation, the server 10 is capable of allowing a user who has received a remittance to refund the remittance to the user who sent the remittance. In other words, by way of example and not limitation, the administrator who has received the remittance (such as a remittance recipient, by way of example and not limitation) can refund the participant who sent the remittance to the administrator. Hereinafter, the process of making a refund in the server 10 will be referred to as a "refund process." Here, the refund process is, by way of example and not limitation, a process of updating the information of the payment server 30 corresponding to the remittance account so as to transfer the value corresponding to the refund amount from the value corresponding to the remittance account ID of the refund source to the value corresponding to the remittance account ID of the refund destination. The contents described in this embodiment can be applied to each of the other embodiments as appropriate.

This embodiment will be described in detail with reference to Figs. 28 and 29. Fig. 28 is a flowchart showing information processing according to the sixth embodiment. Fig. 29 is a diagram showing an overview of information processing according to the sixth embodiment. In this embodiment, the same components as those in the above-mentioned embodiments are appropriately denoted with the same reference numerals, and their description will be omitted or simplified. Note that Fig. 28 is a flowchart assuming that the steps S111 to S151 in Fig. 2 have been completed. In the following, as an example and not a limitation, a description will be given assuming that the user giving the refund in a chat room is User A, and the users receiving the refund are User B and User C.

First, in step S651, when an input is made to the input unit 22 for the icon PL in the display area 28 shown in FIG. 2A(c), the user terminal 20A determines that the icon PL has been selected, and displays a selection image T20 including a remittance setting icon Tb as shown in FIG. 29(a) in the display area 28. Then, when an input is made to the input unit 22 for the icon "refund", the control unit 21 determines that "refund" has been selected. Then, as an example and not a limitation, the control unit 21 extracts a remittance history of remittances made before the current time by referring to the remittance history information D15. As an example and not a limitation, the control unit 21 displays a refund setting image T21 of FIG. 29(b) in the display area 28 based on the extracted remittance history. The refund setting image T21 includes, as an example and not a limitation, a refund condition display section T211 and a refund completion section T212. The refund condition display unit T211 displays the name of the user corresponding to the user ID set in the [Remitter ID]. Also, as a non-limiting example, the names of only users who have remitted money before the current time may be displayed based on the extracted remittance history. As a non-limiting example, the refund condition display unit T211 may display the names of the multiple users in a predetermined display format (as a non-limiting example, a pull-down) when there are multiple users who have remitted money before the current time. Also, as a non-limiting example, the control unit 21 may display check boxes corresponding to each user in the display area 28 so that two or more of the names of the multiple users can be selected when there are multiple users who have remitted money before the current time. In this way, by displaying the user who is to make a refund among the multiple users in a selectable manner, the user who is to make a refund (here, user A) can make a refund to some users (here, user B or user C). Also, as a non-limiting example, the refund condition display unit T211 includes an input area for the refund amount corresponding to the refund destination. As a non-limiting example, the input area for the refund amount may be a text box for accepting input of the refund amount. As a non-limiting example, when an input is made to the input unit 22 for the refund completion unit T212, the control unit 11 confirms the information regarding the refund (as a non-limiting example, the refund information). Then, in step S552, the user terminal 20A transmits a refund request including the refund information to the server 10.

Next, in step S661, the server 10 stores the refund request in the memory unit 15. The server 10, by way of example and not limitation, compares the user ID of user A with the user ID of the [remittance recipient ID] in the talk room information D12 based on the refund request. That is, by way of example and not limitation, the control unit 11 confirms that the refund request has been sent from the user terminal 20 of the remittance recipient. By way of example and not limitation, the control unit 11 executes the refund process if, as a result of the comparison, the user ID of user A matches the user ID of the [remittance recipient ID].
In the refund process, as an example and not a limitation, the control unit 11 first identifies the user ID of the refund source (here, user A) and the user ID of the refund destination (here, user B and user C) based on the refund information. Next, as an example and not a limitation, the control unit 11 identifies the remittance account used in the remittance process based on the remittance history information D15. Note that, as an example and not a limitation, information regarding the remittance account used in the remittance process may be included in the refund information. The control unit 11 executes a process of updating the remittance account information D31 of the payment server 30 corresponding to the remittance account (here, remittance account A) so as to transfer a value indicating the refund amount from the value corresponding to the remittance account of the refund source user ID (here, user A) to the value corresponding to the remittance account of the refund destination user ID (here, user B and user C).

Next, in step S662, the server 10 transmits a refund completion notification including information regarding the result of the refund to the user terminal 20. Based on the refund completion notification, the user terminal 20 displays an image including content indicating the completion of the refund (as an example and not a limitation, that user A has refunded 1,000 yen to user B and user C) in the display area 28. As an example and not a limitation, the user terminal 20B and the user terminal 20C also display an image including the content in the display area 28 in the same manner.
<Seventh Modification>

The information processing according to the seventh modified example will be described with reference to FIG. 30. FIG. 30 is a diagram showing an overview of the information processing according to the seventh modified example. The information processing according to the seventh modified example is, by way of example and not limitation, a form in which a remittance recipient refunds money to a remittance sender based on votes by users who wish to receive a refund. Note that the seventh modified example is premised on the completion of the procedures from S111 to S151 in FIG. 2. Below, by way of example and not limitation, the remittance senders are user B and user C, the remittance recipient is user A, and a procedure in which user A refunds money to user B and user C based on the voting results of user B and user C will be described.

First, when an input is made to the input unit 22 for the icon PL of the display area 28 shown in FIG. 2A(c), the user terminal 20B determines that the icon PL has been selected, and displays a selection image T22 including a remittance setting icon Tb as shown in FIG. 30(a) in the display area 28. Then, when an input is made to the input unit 22 for the icon "refund vote", the control unit 21 determines that "refund vote" has been selected. Then, as an example and not a limitation, the control unit 21 refers to the remittance history information D15 to extract remittance history of remittances made before the current time. As an example and not a limitation, the control unit 21 displays a refund vote image T23 of FIG. 30(b) in the display area 28 based on the extracted remittance history. The refund vote image T23 includes, as an example and not a limitation, a refunder display section T231, a refund amount display section T232, and a voting completion section T233. The refunder display unit T231 displays the name of the user corresponding to the user ID set in the [Remittance Recipient ID], for example and not limitation. In addition, when there are multiple user IDs set in the [Remittance Recipient ID], the refunder display unit T231 may display the names of the multiple users in a predetermined display format (as an example and not limitation, a pull-down). In addition, when there are multiple user IDs set in the [Remittance Recipient ID], the control unit 21 may display check boxes corresponding to the multiple users in the display area 28 so that two or more of the multiple user names can be selected, for example and not limitation. The refund amount display unit T232 may be, for example and not limitation, a text box that accepts input of the refund amount. In the case where there is an input in the input unit 22, the voting completion unit T213, for example and not limitation, confirms the information on the vote (as an example and not limitation, the voting information). Then, the user terminal 20B, 20C transmits a voting request including the voting information to the server 10.

Next, the server 10 stores the voting request in the storage unit 15. The server 10, for example and not limitation, compares the user IDs of user B and user C with the user ID of [User ID] in the talk room information D12 shown in FIG. 3A based on the voting information. That is, for example and not limitation, the control unit 11 confirms that the voting information has been sent from the user terminal 20 of the user participating in the talk room. The server 10, for example and not limitation, executes the voting refund process based on the voting information. The voting refund process is a process for making the refunder refund the user who sent the voting request by determining whether or not a predetermined condition is satisfied based on the voting information. Here, for example and not limitation, the predetermined condition is, for example and not limitation, that the total number of pieces of information indicating the refunder exceeds a predetermined threshold, that the total number of pieces of information indicating the refunder exceeds a predetermined ratio to the number of users participating in the talk room, etc., based on the information on the refunder included in the voting information. When the control unit 11 determines that the predetermined condition is satisfied, for example and not limitation, it executes the above-mentioned value transfer process to make the refunder refund the voter.

Next, the server 10 transmits, by way of example and not limitation, a refund completion notification including information regarding the result of executing the value transfer process to each user terminal 20. Based on the refund completion notification, the user terminal 20 displays, by way of example and not limitation, an image including content related to the refund (e.g., "User A has refunded 1,000 yen to users B and C due to voting").
===Effect===

According to this embodiment, the server 10 receives refund information regarding refunding the amount transferred from user B (participant) to user A (administrator) to user A, and executes processing regarding transferring the amount transferred from user A to user B based on the refund information. As a result, according to the information processing of this embodiment, by way of example and not limitation, the server 10 can refund the transferred amount to the user who transferred the money, and therefore, since transfer procedures associated with a user's erroneous transfer or a change in the transfer recipient can be quickly executed, it is possible to improve user convenience and improve the security of the chat room.
Seventh Embodiment

An overview of this embodiment will be described. This embodiment is an example, not a limitation, in which a remittance recipient can make a remittance request to a remittance sender on the server 10, and can display whether or not the user has made a remittance in response to the remittance request. In the following, as an example, not a limitation, the remittance recipient is User A, the remittance senders are User B and User C, and User A requests User B and User C to remit money. The contents described in this embodiment can be applied to the other embodiments as appropriate.

This embodiment will be described in detail with reference to Figs. 31 to 33. Fig. 31 is a flowchart showing information processing according to the seventh embodiment. Fig. 32 is a diagram showing an overview of information processing according to the seventh embodiment. Fig. 33 is a diagram showing an example of a remittance request image. In this embodiment, the same components as those in the above-mentioned embodiment are appropriately denoted with the same reference numerals and their description will be omitted or simplified. Note that Fig. 31 is a flowchart assuming that the steps S111 to S151 in Fig. 2 have been completed. Below, the procedure for a remittance recipient (here, user A) to request a remittance from a remittance sender (here, users B and C) will be described.

First, in step S751, when an input is made to the input unit 22 for the icon PL in the display area 28 shown in FIG. 2A(c), the user terminal 20A determines that the icon PL has been selected, and displays a selection image T24 including a remittance setting icon Tb as shown in FIG. 32(a) in the display area 28. Then, when an input is made to the input unit 22 for the icon "remittance request", the control unit 21 determines that "remittance request" has been selected. Then, by way of example and not limitation, the control unit 21 refers to the talk room information D12 and the remittance history information D15 and displays a remittance request image T25 in FIG. 32(b) in the display area 28. The remittance request image T25 includes, by way of example and not limitation, a remittance request destination selection section T251 and a remittance request completion section T252. The remittance request destination display section T251 displays, by way of example and not limitation, the name of the user corresponding to the user ID set in [remittance sender ID]. Also, as a non-limiting example, the names of only users who have not remitted money may be displayed based on the remittance history information D15. As a non-limiting example, the remittance request destination display unit T251 may display the names of multiple users in a predetermined display format (as a non-limiting example, a pull-down) when there are multiple remitters. Also, as a non-limiting example, the control unit 21 may display check boxes corresponding to each user in the display area 28 so that two or more of the names of the multiple users can be selected when there are multiple remitters. In this way, by displaying the user who requests remittance among the multiple users in a selectable manner, the user who requests remittance (here, user A) can request some users (here, user B or user C) to remit money. As a non-limiting example, when there is an input to the input unit 22 for the remittance request completion unit T252, the control unit 11 confirms the information on the remittance request (as a non-limiting example, remittance request information). Then, in step S752, the user terminal 20A transmits a remittance request request including the remittance request information to the server 10.

Next, in step S761, the server 10 stores the remittance request request in the storage unit 15. The server 10, for example and not limitation, compares the user ID of user A with the user ID of [remittance recipient ID] in the talk room information D12 based on the remittance request request. That is, for example and not limitation, the control unit 11 confirms that the remittance request request has been sent from the user terminal 20 of the remittance recipient. For example and not limitation, the control unit 11 executes a request display process when the user ID of user A matches the user ID of [remittance recipient ID] as a result of the comparison. In the request display process, for example and not limitation, the control unit 11 first identifies a user to whom a remittance is to be requested based on the remittance request information. Next, the control unit 11 generates a remittance list T261 shown in FIG. 33(a) that can determine whether the identified user has remitted or not remitted based on the remittance history information D10. As an example and not a limitation, the control unit 11 generates a remittance request image T26 that includes a remittance list T261. Note that, as an example and not a limitation, the control unit 11 may generate the remittance list T241 so that it includes an indication that makes it possible to distinguish at least one of users who have remitted money or users who have not remitted money.

Next, in step 762, the server 10 transmits, by way of example and not limitation, a remittance request image T26 including a remittance list T241 to the user terminal 20. Next, the user terminal 20 displays the remittance request image T26 shown in FIG. 33(a) in the display area 28. Note that, by way of example and not limitation, the server 10 may transmit the remittance request image T26 only to the user terminal 20 of the remittance recipient (here, user A). In this case, only the user terminal 20A displays the remittance request image T26 shown in FIG. 33(a) in the display area 28. The remittance request image T26 includes, by way of example and not limitation, a remittance list T261 and content Q8 related to user A's remittance request. In FIG. 33(a), as an example and not a limitation, since users B and C have not yet remitted money to user A, the "Remitted" column in the remittance list T261 is shown blank, and the "Unremitted" column shows the indication "B" for user B and the indication "C" for user C.

Next, as an example and not a limitation, when user B completes remittance to user A in steps 771 to 781, in step 791, the server 10 generates a remittance request image T27 including a remittance list T271 shown in FIG. 33(b) that allows identification of user B who has completed remittance, and a content Q9 indicating that user B has completed remittance in response to user A's remittance request. Note that, as an example and not a limitation, the control unit 11 may transition to remittance processing when user B inputs into the input unit 22 of the user terminal 20B content Q8 including a URL and an icon Q81 for causing the server 10 to execute remittance processing. In this case, as an example and not a limitation, when remittance processing is completed, the control unit 11 generates a remittance request image T27 including a content Q9 indicating that remittance has been made in response to user A's remittance request (as an example and not a limitation, "Remittance has been made in response to the remittance request from user A").

Next, in step 792, the server 10 transmits the remittance request image T27 to the user terminal 20, for example and not limitation. Note that, for example and not limitation, the server 10 may transmit the remittance request image T27 only to the user terminal 20 of the remittance recipient (here, user A). Also, for example and not limitation, the server 10 may generate the remittance request image T27 including the remittance list T271 that displays only the status related to the remittance of the remittance user, and transmit the remittance request image T27 to the user terminal 20 of the remittance user. In this case, for example and not limitation, when transmitting the remittance request image T27 to the user terminal 20 of the remittance user B, the server 10 generates the remittance request image T27 by displaying the indication "B" indicating user B in the "Remitted" column of the remittance list T271 in FIG. 33(b) and leaving the "Unremitted" column blank. Next, the user terminal 20 displays in the display area 28 a remittance request image T27 shown in FIG. 33(b), for example and not for limitation.
<Eighth Modification>

The information processing according to the eighth modified example will be described with reference to FIG. 34. FIG. 34 is a diagram showing an example of a remittance request identification image T28. The information processing according to the eighth modified example is, by way of example and not limitation, a form in which an indication of a user in a chat room is highlighted depending on the status of unsent or completed remittance. Note that the eighth modified example is premised on the completion of the steps up to S781 in FIG. 31. Hereinafter, by way of example and not limitation, the remittance recipient is User A, the remittance senders are User B and User C, the user who has completed remittance is User B, and the user who has not yet completed remittance is User C. The contents described in this embodiment can be applied to the other embodiments as appropriate.

The server 10 generates a remittance request image T28 by applying highlighting T282 shown in FIG. 34 to the icon Uc1 of user C, which allows the user C who has not yet remitted money to be identified. Note that, as a non-limiting example, the server 10 may generate a remittance list image T28 by applying highlighting T282 to the icon Ub1 of user B, which allows the user B who has already remitted money to be identified. Also, as a non-limiting example, the server 10 may generate a remittance request image T28 by applying highlighting T282 to the user's username (here, reference symbols Ub2 and Uc2) or content. Here, the highlighting T282 is, as a non-limiting example, a blinking or lit display that surrounds the icon Uc1 of user C. Also, as a non-limiting example, the highlighting T282 may be, as a non-limiting example, a blinking or lit display that surrounds the username Uc2 of user C. Furthermore, the highlighting T282 may be, for example and not for limitation, a flashing or lit display surrounding user C's content Q10, or a display in which the color scheme of content Q10 is different from that of content Q9. Note that, for example and not for limitation, FIG. 34 shows the remittance list T281 included, but the remittance list T261 may or may not be included in the remittance request image T28.

Next, the server 10, by way of example and not limitation, transmits a remittance request image T28 to the user terminal 20. Note that, by way of example and not limitation, the server 10 may transmit the remittance request image T28 only to the user terminal 20 of the remittance recipient (here, user A). Next, the user terminal 20, by way of example and not limitation, displays the remittance request image T28 shown in FIG. 34 in the display area 28.
<Ninth Modification>

With reference to FIG. 35, the information processing according to the ninth modified example will be described. FIG. 35 is a diagram showing an outline of the information processing according to the ninth modified example. The information processing according to the ninth modified example is, by way of example and not of limitation, a form in which the server 10 rejects a request to leave a talk room by a user who has not yet remitted money. Here, "withdrawal" means, by way of example and not of limitation, that the relationship between the talk room ID and the user ID in the talk room information D12 is released in the server 10. That is, when "withdrawal" is executed, the user terminal 20 of the withdrawn user cannot display the content of the talk room in the display area 28, cannot remit money to other users, and cannot receive money from other users. In the following, in the ninth modified example, it is assumed that the procedure up to S762 in FIG. 31 has been completed. Also, by way of example and not of limitation, it is assumed that the remittance recipient is user A, the remittance senders are user B and user C, user B is a user who has remitted money, user C is a user who has not yet remitted money, and the user terminal 20C of user C has sent a withdrawal request to the server 10. The contents described in this embodiment can be applied to other embodiments as appropriate.

First, when an input is made to the input unit 22 for the icon PL in the display area 28 shown in FIG. 2A(c), the user terminal 20C determines that the icon PL has been selected, and displays a selection image T26 including a remittance setting icon Tb as shown in FIG. 35(a) in the display area 28. Then, when an input is made to the input unit 22 for the icon "withdrawal", the control unit 21 determines that "withdrawal" has been selected. For example and not limitation, the user terminal 20C transmits information related to withdrawal (for example and not limitation, withdrawal information) to the server 10. Next, for example and not limitation, the server 10 stores the withdrawal information in the storage unit 15. For example and not limitation, the server 10 refers to the remittance history information D15 and determines whether or not the user C has not remitted money based on the withdrawal information. For example and not limitation, if it is determined that the user C has not remitted money, the server 10 generates a withdrawal refusal image T30 including a refusal comment image T301 indicating that withdrawal is not possible. The server 10 transmits, by way of example and not limitation, a withdrawal refusal image T30 to the user terminal 20C. Next, the user terminal 20C displays, by way of example and not limitation, the withdrawal refusal image T30 shown in Fig. 35(b) in the display area 28. Note that the server 10 is not limited to generating the withdrawal refusal image T30 as described above, and, by way of example and not limitation, the user terminal 20C may generate the withdrawal refusal image T30 based on the remittance history information D25 and display the withdrawal refusal image T30 in the display area 28.
<Tenth Modification>

The information processing according to the tenth modified example will be described with reference to FIG. 36. FIG. 36 is a diagram showing an example of a remittance request image T31. The information processing according to the tenth modified example is a form in which, after the receipt change processing in the second embodiment, when a remittance request is made from a user whose remittance receipt settings have been changed (here, user B) to a user who has not yet remitted money (here, user C), a remittance is executed to the user whose settings have been changed. Hereinafter, it is assumed that the user terminal 20A of the user who changed the remittance receipt settings (here, user A) makes a remittance request to the user terminal 20C of user C, and then the user terminal 20B of the user whose remittance receipt settings have been changed (here, user B) makes a remittance request to the user terminal 20C of user C.

The server 10 transmits a remittance request image T31 to the user terminal 20C, for example and not limitation. Next, the user terminal 20C displays the remittance request image T31 shown in FIG. 36 in the display area 28. Here, the remittance request image T26 includes, for example and not limitation, a content Q8 related to a remittance request from user A and a content Q10 related to a remittance request from user B. The content Q8 includes, for example and not limitation, a URL and an icon Q81 for causing the server 10 to execute a remittance process, and the user terminal C includes, for example and not limitation, a URL and an icon Q101 for causing the server 10 to execute a remittance process. The user terminal 20C may determine, for example and not limitation, that the icon Q81 has been selected when an input is made to the input unit 22 for the icon Q81, and transmit a remittance process request (including, for example and not limitation, information related to the remittance destination, remittance source, remittance amount, remittance account, etc.) to the server 10. In this case, the server 11, by way of example and not limitation, refers to the talk room information D12 and executes a remittance process to remit money to the remittance recipient (here, user B) after the remittance receipt setting has been changed. Also, by way of example and not limitation, when an input is made to the input unit 22 for the icon Q101, the user terminal 20C may determine that the icon Q101 has been selected and send a remittance process request (including, by way of example and not limitation, information on the remittance destination, remittance source, remittance amount, remittance account, etc.) to the server 10. Even in this case, the server 11, by way of example and not limitation, refers to the talk room information D12 and executes a remittance process to remit money to the remittance recipient (here, user B) after the remittance receipt setting has been changed. That is, when an input is made to the input unit 22 for a display related to a remittance request displayed in the talk room after the remittance receipt setting has been changed, a remittance process is executed to remit money to the remittance recipient after the remittance receipt setting has been changed.
===Effect===

According to this embodiment, when user B remits money in response to a transmission request sent from user A to user B, the server 10 includes information in the chat room indicating that the remittance has been made in response to the remittance request. As a result, according to the information processing of this embodiment, by way of example and not limitation, the server 10 can display in the chat room users who have remitted money to the user, thereby improving the convenience of users with regard to remittances.

According to this embodiment, when user B has not sent money in response to a transmission request sent from user A to user B, the server 10 includes information in the chat room indicating that the user has not sent money in response to the remittance request. As a result, according to the information processing of this embodiment, by way of example and not limitation, users who have not sent money to the user can be displayed in the chat room, thereby improving the convenience of users in sending money.

According to this embodiment, the server 10 displays information indicating that user B has sent money in response to a transmission request sent from user A to user B, and information indicating that user B has not sent money, only in the talk room displayed in the display area 28 of user A's user terminal 20A. As a result, according to the information processing of this embodiment, as an example and not a limitation, information indicating users who have sent money and users who have not sent money is displayed only in the talk room displayed in the display area 28 of user A's user terminal 20A, who is the administrator, so that the amount of information processing by the server 10 can be reduced. Also, as an example and not a limitation, the server 10 can provide a talk room that does not cause discomfort to users who have not sent money.

In this embodiment, the input by user B to the input unit 22 for the talk room displayed in the display area 28 of the user terminal 20B is an input to a display related to a remittance request from user A to user B displayed in the talk room. The server 10 receives information related to the remittance from user B to user C based on the input by user B to the input unit 22 for the display related to the remittance request displayed in the talk room displayed in the display area 28 of the user terminal 20B, which is transmitted from the user terminal 20C of user C to the user terminal 20B, and the setting related to the remittance to another user different from user A executed by user A. The server 10 executes a process related to the remittance from user B to user C based on the information related to the remittance from user B to user C. As a result, according to the information processing of this embodiment, by way of example and not limitation, a remittance request can be executed even if the remittance recipient is changed, thereby improving the convenience of the user.
Eighth Embodiment

An overview of this embodiment will be described. This embodiment is, by way of example and not limitation, a form in which images (e.g., photos, etc.) posted in a chat room by a specific user on the server 10 can be purchased by other users. In this embodiment, the server 10 receives photo data from the user terminal 20 of the specific user, and transmits the received photo data to each user terminal 20 at a low resolution. In the following, by way of example and not limitation, the remittance recipient is User A, the user who uploads the photo data to the server 10 is User B, and the user who purchases the photo data is User C. The contents described in this embodiment can be applied to the other embodiments as appropriate.

This embodiment will be described in detail with reference to Figs. 37 and 38. Fig. 37 is a flowchart showing information processing according to the eighth embodiment. Fig. 38 is a diagram showing an overview of information processing according to the eighth embodiment. In this embodiment, the same components as those in the above-mentioned embodiment are appropriately denoted with the same reference numerals and their description will be omitted or simplified. Note that Fig. 37 is a flowchart assuming that the procedures from S111 to S151 in Fig. 2 have been completed. Below, a procedure will be described in which a user (here, user C) who purchases photo data uploaded by a specific user (here, user B) remits money to a money transfer recipient (here, user A).

First, in step S861, the user terminal 20B generates photo data of the first resolution based on an input by the user B to the input unit 22, as an example and not a limitation. Next, in step S862, the user terminal 20B transmits the photo data of the first resolution to the server 10, as an example and not a limitation.

Next, in step S871, the server 10 stores the photo data of the first resolution in the storage unit 15, as an example and not a limitation. The server 10 generates photo data of a second resolution indicating a resolution lower than the first resolution based on the photo data of the first resolution, as an example and not a limitation. The server 10 generates a photo posting image T31 including the photo data of the second resolution shown in FIG. 38(a), as an example and not a limitation (here, a posting process). Next, in step S872, the server 10 transmits the photo posting image T31 to the user terminal 20, as an example and not a limitation.

Next, in step S881, the user terminal 20C displays in the display area 28 a photo posting image T32 as shown in FIG. 38(a), for example and not limitation. When an input is made to the input unit 22 for an icon of the purchase transition section T321 included in the photo posting image T32, the user terminal 20C determines that the purchase transition section T321 has been selected, and displays the photo purchase image T33 in the display area 28. The photo purchase image T33 includes, for example and not limitation, a photo selection section T331, an amount display section T332, a remittance destination T333, a remittance account setting section T334, and a purchase confirmation section T335. The photo selection section T331 is, for example and not limitation, an area in which photo data of the second resolution is selectably posted. The photo selection section T331 includes, for example and not limitation, a selection display icon T3311. For example and not limitation, when an input is made to the input unit 22 for the selection display icon T3311, the control unit 11 determines that the selection display icon T3311 has been selected and changes the status of the selection display icon T3311 (for example, by adding a number and changing the color). The amount display unit T332 is an area in which the purchase amount of the photo data is displayed, for example and not limitation. The control unit 11 calculates the purchase amount of the photo data corresponding to the selected selection display icon T3311, and displays the purchase amount in the amount display unit T332. The remittance destination T333 is an area in which the remittance destination specified by referring to the talk room information D22 is displayed, for example and not limitation. The remittance account setting unit T334 is an area in which the name of the remittance account corresponding to the available remittance account ID is displayed in a predetermined display format (for example and not limitation, a pull-down) when an input is made to the input unit 22. For example, but not limited to, when an input is made to the input unit 22 for the purchase confirmation unit T335, the control unit 11 confirms information regarding the photo data to be purchased and the purchase price (for example, but not limited to, purchase information). Then, in step S882, the user terminal 20C transmits a purchase request including the purchase information to the server 10.

Next, in step S891, the server 10 stores the purchase request in the storage unit 15. The server 10, for example and not limitation, compares the user ID of user C with the user ID of [user ID] in the talk room information D12 based on the purchase request. That is, the control unit 11, for example and not limitation, confirms that the purchase request has been sent from the user terminal 20 of the user participating in the talk room. As an example and not limitation, the control unit 11 transitions to a remittance process when the user ID of user C matches the user ID of [user ID] as a result of the comparison. The server 10, for example and not limitation, executes a remittance process based on the purchase information. As an example and not limitation, the control unit 11 identifies the user IDs of the remittance source and remittance destination, the remittance account, and the purchase amount (remittance amount) based on the purchase information. The server 10, for example and not limitation, transmits a remittance notification including information on the user IDs of the remittance source and remittance destination, the remittance account, and the purchase amount to the payment server 30. The payment server 30 transfers the value corresponding to the purchase amount from the value of the remittance account corresponding to the user ID of the remitter to the value of the remittance account corresponding to the user ID of the remitter. By way of example and not limitation, the payment server 30 transmits information regarding the results of the remittance processing to the server 10. This completes the remittance processing. Next, in S892, the server 10 acquires the first resolution photo data from the storage unit 15 based on the purchase information. Then, the control unit 11 transmits the first resolution photo data to the user terminal 20 of user C. Next, in S893, the server 10 transmits a remittance completion notice including information regarding the purchase amount to the user terminal 20. By way of example and not limitation, the user terminal 20A displays an image including content indicating the completion of the remittance (by way of example and not limitation, 2,000 yen has been remitted for the photo purchase price) based on the remittance completion notice.

In the above, the server 10 may, for example and not for limitation, transmit an image of the talk room so that content sent and received by users participating in the talk room is not displayed to the user device 20 of the user who uploads photo data to the server 10. Specifically, for example and not for limitation, the server 10 refers to the content information D13 to identify content corresponding to users other than user B, excludes the identified content, and generates a photo posting image T32 to be transmitted to the user terminal 20 of user B.
===Effect===

According to this embodiment, the server 10 can post low-resolution photo data in a chat room and provide high-resolution photos to the user in response to the user's purchase request. As a result, according to the information processing of this embodiment, by way of example and not limitation, the server 10 can compress the volume of data sent and received in order to post low-resolution photo data, thereby improving processing speed. In addition, the user can purchase photos in the chat room, improving user convenience.

B1, B2, B3... bus, N... network, 1... communication system, 10... server, 20... user terminal, 30... payment server, 11, 21, 31... control unit, 12, 22, 32... input unit, 13, 23, 33... output unit, 14, 24, 34... communication I/F, 15, 25, 35... memory unit.

Claims (12)

A program executed by a server that provides a chat room in which users can send and receive content,
receiving, by a communication unit of the server, remittance information regarding a remittance from a first user included in the chat room to a second user included in the chat room, based on an input by the first user to the chat room displayed on a first terminal of the first user;
The server executes a process related to the remittance from the first user to the second user based on the reception of the remittance information,
When information to leave the chat room is received from the first terminal before the first user makes a remittance in response to a remittance request, the server executes the following: sending information to the first terminal via the communication unit indicating that the first user cannot leave the chat room. The program according to claim 1,
The remittance information is transmitted based on a remittance request from the second user to the first user. The program according to claim 1 or 2,
The server controls a control unit of the server to set a first setting for the chat room, the first setting being related to a setting that enables remittance to the second user. The program according to claim 3,
The first setting is set based on creation of the chat room by the second user. The program according to claim 3 or 4,
The first settings include settings related to enabling transfer of money to the second user based on input into the chat room by users included in the chat room. The program according to any one of claims 3 to 5,
The first setting includes a setting regarding not allowing users in the chat room to transfer money to the first user. The program according to any one of claims 1 to 6,
The server executes, by the control unit, a second setting related to a remittance to a third user different from the second user, based on a first input by the second user to the chat room displayed on the second terminal of the second user;
The third user is included in the chat room. The program according to any one of claims 3 to 6,
receiving information about the second user from the first user by the communication unit;
The server executes control by the control unit to change the first setting regarding remittance to the second user to a third setting based on information regarding the second user. The program according to claim 8,
The third setting includes a setting related to disabling remittance to the second user. The program according to any one of claims 1 to 9,
receiving information about the second user from the first user by the communication unit;
The server executes control by the control unit to at least temporarily suspend the account of the second user based on information about the second user. An information processing method for a server that provides a chat room in which users can send and receive content, comprising the steps of:
receiving, by a communication unit of the server, remittance information regarding a remittance from a first user included in the chat room to a second user included in the chat room, based on an input by the first user to the chat room displayed on a first terminal of the first user;
and performing a process for remittance from the first user to the second user by a control unit of the server based on the reception of the remittance information;
The method includes, when information to leave the chat room is received from the first terminal before the first user makes a remittance in response to a remittance request, transmitting information to the first terminal via the communication unit indicating that the first user cannot leave the chat room. A server that provides a chat room in which users can send and receive content,
a communication unit that receives remittance information regarding a remittance from a first user included in the chat room to a second user included in the chat room based on an input by the first user to the chat room displayed on a first terminal of the first user;
a control unit that performs processing related to the remittance from the first user to the second user based on the reception of the remittance information,
When information to leave the chat room is received from the first terminal before the first user makes a remittance in response to a remittance request, the server executes the following: sending information to the first terminal via the communication unit indicating that the first user cannot leave the chat room.