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

Description

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

A technology is known that enables content to be transmitted and received between users via terminals and viewed. Patent Literature 1 discloses that a user posts a message through a SNS (Social Networking Service), and that when the message is confirmed, the message is changed from an unread state to a read state.

JP 2019-028735 A

According to the first aspect of the present invention, input by the first user to the 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 and transmitting the received first content to the second terminal of the second user, and transmitting the second content input by the second user to the second terminal on which the chat room is displayed and transmitted from the second terminal. A program executed by a server for transmission to the first terminal, wherein a control unit of the server performs control for setting a first setting regarding remittance to the first user for the chat room; A communication unit of the server receives information regarding remittance from the second user to the first user based on the first setting and the second user's input to the chat room displayed on the second terminal. and performing processing related to remittance from the second user to the first user by the control unit based on information related to remittance from the second user to the first user. .

According to the second aspect of the present invention, input by the first user to the 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 and transmitting the received first content to the second terminal of the second user, and transmitting the second content input by the second user to the second terminal on which the chat room is displayed and transmitted from the second terminal. An information processing method of a server for transmission to the first terminal, wherein a control unit of the server performs control for setting a first setting regarding remittance to the first user for the chat room; A communication unit of the server receives information regarding remittance from the second user to the first user based on the first setting and the second user's input to the chat room displayed on the second terminal. and performing processing related to remittance from the second user to the first user by the control unit based on information related to remittance from the second user to the first user.

According to the third aspect of the present invention, input by the first user to the 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 and transmitting the received first content to the second terminal of the second user, and transmitting the second content input by the second user to the second terminal on which the chat room is displayed and transmitted from the second terminal. A server for transmitting to the first terminal, the control unit performing control for setting a first setting regarding remittance to the first user for the chat room, and the first setting and the second user a communication unit configured to receive information related to remittance from the second user to the first user based on an input to the chat room displayed on the second terminal, wherein the control unit receives information from the second user; Based on the information related to the remittance to the first user, processing related to remittance from the second user to the first user is performed.

1 is a diagram showing the configuration of a communication system according to an embodiment of the present disclosure; FIG. The figure which shows the outline|summary of the information processing which concerns on 1st Embodiment. The figure which shows the outline|summary of the information processing which concerns on 1st Embodiment. The figure which shows an example of the talk room information D12. The figure which shows an example of the content information D13. The figure which shows an example of remittance account information D14. The figure which shows an example of remittance history information D15. The figure which shows an example of remittance account information D31. 4 is a flowchart showing the procedure of information processing according to the first embodiment; The figure which shows an example of the relationship information D16. FIG. 10 is a diagram showing an image T8 of a talk room in which an indication regarding setting of a predetermined relationship is displayed; The figure which shows an example of remittance setting image T9. 9 is a flowchart showing information processing according to the second embodiment; The figure which shows the outline|summary of the information processing which concerns on 2nd Embodiment. The figure which shows an example of the talk room information D12 which concerns on 2nd Embodiment. The figure which shows an example of the image T8 containing the content which shows the completion of a setting. The figure which shows the outline|summary of the information processing which concerns on a 4th modification. The figure which shows an example of the talk room information D12 based on a 4th modification. The figure which shows the outline|summary of the information processing which concerns on a 5th modification. The figure which shows an example of the image T13 containing the content regarding receipt change. 9 is a flowchart showing information processing according to the third embodiment; The figure which shows an example of the approval confirmation screen T14. The figure which shows an example of personal identification information D17. The figure which shows an example of the remittance completion image T15. 10 is a flowchart showing information processing according to the fourth embodiment; The figure which shows the outline|summary of the information processing which concerns on 4th Embodiment. The figure which shows an example of the extinction condition information D18. 14 is a flowchart showing information processing according to the fifth embodiment; The figure which shows the outline|summary of the information processing which concerns on 5th Embodiment. The figure which shows an example of the 1st restriction|limiting information D19A. The figure which shows an example of the 2nd restriction|limiting information D19B. 14 is a flowchart showing information processing according to the sixth embodiment; The figure which shows the outline|summary of the information processing which concerns on 6th Embodiment. The figure which shows the outline|summary of the information processing which concerns on a 7th modification. 14 is a flowchart showing information processing according to the seventh embodiment; The figure which shows the outline|summary of the information processing which concerns on 7th Embodiment. The figure which shows an example of a remittance request image. The figure which shows an example of remittance request identification image T28. The figure which shows the outline|summary of the information processing which concerns on a 9th modification. The figure which shows an example of the remittance completion image T31. 14 is a flowchart showing information processing according to the eighth embodiment; The figure which shows the outline|summary of the information processing which concerns on 8th Embodiment.

<Compliance with legal matters>

Note that the disclosure provided herein is subject to compliance with the legal requirements of the implementing country required for the practice of this disclosure, such as confidentiality of communications.

Embodiments for implementing an information processing method, a program, and an information processing apparatus according to the present disclosure will be described with reference to the drawings.
<System configuration>

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

The network N serves to connect one or more servers 10 , one or more user terminals 20 and a payment server 30 . That is, the network N means a communication network that provides a connection path so that the user terminal 20 can transmit 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 an IP (Internet Protocol) network. Network N can be, by way of example and not limitation, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless wireless LAN (WLAN), wide area network (WAN), wireless WAN (WWAN), metropolitan area network (MAN), part of the Internet, public switched telephone network (Public Part of Switched Telephone Network (PSTN), mobile phone network, ISDN (integrated service digital networks), wireless LAN, LTE (long term evolution), CDMA (code division multiple access), Bluetooth (registered trademark), satellite communication, etc., or a combination of two or more thereof. A network N may 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 realizing the functions described in each embodiment. Server 10 may be, by way of example and without limitation, a server computer, a personal computer (including but not limited to desktops, laptops, tablets, etc.), media computer platforms (including but not limited to cable, satellite set-top boxes, digital video recorders), handheld computing devices (eg, without limitation, PDAs, email clients, etc.), or other types of computers or communication platforms. Also, the server 10 may be expressed as an information processing device.

The user terminal 20 (user terminal 20A, user terminal 20B, user terminal 20C) may be any information processing apparatus (computer) that can implement the functions described in each embodiment. User terminals 20 may include, by way of example and not limitation, smart phones, mobile phones (feature phones), personal computers (including but not limited to desktops, laptops, tablets, etc.), media computer platforms (including but not limited to cables, satellite set-top boxes, digital video recorders), handheld computing devices (including but not limited to PDAs (personal digital assistants), email clients, etc.), wearable terminals (glass-type devices, watch-type devices, etc.), and other types of Including computers or communication platforms. Also, the user terminal 20 may be expressed as an information processing device.

In the following description, user information refers to user information associated with the user terminal 20 or the user of the user terminal 20 and associated with a predetermined service. The user information is user information associated with an account used by the user in a predetermined service. The user information may include information input by the user, or may include information provided by a predetermined service. The user information includes, for example and not limitation, at least one of a plurality of items of information including user name, user icon image, user age, user gender, user address, user hobbies and tastes, and user identifier. Contains information. The user information may include information associated with the user, which is different from the information of the plurality of items described above.

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 realizing the functions described in each embodiment. Payment server 30 may include, by way of example and without limitation, server computers, personal computers (including but not limited to desktops, laptops, tablets, etc.), media computer platforms (including but not limited to cable, satellite set-top boxes, digital video recorders), handheld computing devices (eg, without limitation, PDAs, email clients, etc.), or other types of computers or communication platforms. Also, the payment server 30 may be expressed 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 HW configuration

The server 10 includes a control unit (CPU) 11 , a storage unit 15 , a communication I/F (interface) 14 , an input unit 12 and an output unit 13 . Each component of the HW of the server 10 is interconnected via a bus B1, for example and not limitation. It should be noted that the HW of the server 10 does not have to include all components as the HW configuration of the server 10 . As an example and not a limitation, the HW of the server 10 may or may not have a configuration in which the output unit 13 can be removed.

The control unit 11 comprises, by way of example and not limitation, a data processing device that is physically structured to carry out the functions implemented by the code or instructions contained within the program. It is realized by

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

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

Communication I/F 14 transmits and receives various data via network N. FIG. Communication by the communication I/F 14 may be performed by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F 14 has a function of communicating with other devices such as the user terminal 20 via the network N. Communication I/F 14 transmits various data to other devices according to instructions from control unit 11 . The communication I/F 14 also receives various data transmitted from other devices and transmits the data to the control unit 11 . Also, the communication I/F 14 may be simply referred to as a communication unit. Moreover, when the communication I/F 14 is configured by a physically structured circuit, it may be expressed as a communication circuit.

The input unit 12 is realized by a device for inputting various operations to the server 10 . The input unit 12 is realized by any one or a combination of all types of devices that can receive input from the user and transmit information related to the received input to the control unit 11 . The input unit 12 is implemented by hardware keys typically represented by a keyboard and 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 moving images), and a microphone (operation input by voice) as examples without limitation. However, in the present disclosure, the input unit 12 is not limited to these.

The output unit 13 includes, by way of example and not limitation, a display unit 13a. The display unit 13a is typically realized by a monitor (as a non-limiting example, a liquid crystal display or an OELD). The display unit 13a may or may not be a head-mounted display (HDM). 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 the program P1 and the databases D11 to D15 in the storage unit 15. FIG. In the server 10, the control unit 11 executes the program P1, thereby executing the processing of each unit included in the control unit 11. FIG. In other words, the program 15 a stored in the storage unit 15 causes the server 10 to implement each function executed by the control unit 11 . This program P1 may or may not be expressed as a program module.
(2) HW configuration of user terminal

The user terminal 20 includes a control section (CPU: central processing unit (central processing unit)) 21 , a storage section 25 , a communication I/F (interface) 24 , an input section 22 and an output section 23 . Each component of the HW of the user terminal 20 is interconnected via a bus B2, for example and not limitation. Note that the HW configuration of the user terminal 20 does not necessarily include all the components. As an example and not a limitation, the user terminal 20 may or may not have a configuration in which individual components, such as the input unit 22 and the output unit 23, or a plurality of components can be removed. .

Communication I/F 24 transmits and receives various data via network N. FIG. Communication by the communication I/F 24 may be performed by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. Communication I/F 24 has a function of executing communication with server 10 via network N. FIG. Communication I/F 24 transmits various data to server 10 according to instructions from control unit 21 . Also, the communication I/F 24 receives various data transmitted from the server 10 and transmits the data to the control unit 21 . Moreover, communication I/F24 may be simply expressed as a communication part. Moreover, when the communication I/F 24 is composed of a physically structured circuit, it may be expressed 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 that outputs the processing result processed by the user terminal 20 . The input unit 22 and the output unit 23 may or may not be specified as input/output units. When specified as an input/output unit, the input/output unit may be the input unit 22 and the output unit 23 integrated, or may be separated into the input unit 22 and the output unit 23 .

The input unit 22 is implemented by any one or a combination of all types of devices that can receive input from the 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 hardware keys such as a touch panel, a touch display, and a keyboard, and a pointing device such as a mouse, as examples without limitation. Microphone 22b includes, by way of example and not limitation, a device for inputting sound. The microphone 22b is used for inputting voice data. Camera 22c includes, by way of example and not limitation, an image input device. The camera 22c is used for acquiring image data.

The output unit 23 is implemented by any one or a combination of all types of devices capable of outputting processing results processed 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, as non-limiting examples, a touch panel, a touch display, a lens (3D (three dimensions) output and hologram output as non-limiting examples), a printer, and the like.

The display unit 23a is realized by any one or a combination of all kinds of devices capable of displaying an image according to the display data written in the frame buffer. The display unit 23a includes, as non-limiting examples, a touch panel, a touch display, a monitor (non-limiting examples include a liquid crystal display and an OELD (organic electroluminescence display)), a head mounted display (HDM: Head Mounted Display), projection mapping, and a hologram. , including devices capable of displaying images, text information, etc. in air (which may or may not be a vacuum). 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 an input/output unit and configured as a touch panel, for example and not limitation. When the input unit 22 and the output unit 23 are configured as touch panels, the operation unit 22a and the display unit 23a may be arranged to face each other with substantially the same size and shape.

The control unit 21 comprises, by way of example and not limitation, a data processing device that is physically structured to carry out the functions implemented by the code or instructions contained within the program. It is realized by Therefore, the control unit 21 may or may not be expressed as a control circuit.

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

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

The user terminal 20 stores the program P1 and the databases D21 to D25 in the storage unit 25. FIG. In the user terminal 20, the control unit 21 executes the program P2, thereby executing processing as each unit included in the control unit 21. FIG. That is, the program P2 stored in the storage unit 25 causes the user terminal 20 to implement each function executed by the control unit 21 . Also, this program P2 may or may not be expressed as a program module.
(3) HW configuration of payment server

The payment server 30 includes a control unit (CPU) 31 , a storage unit 35 , a communication I/F (interface) 34 , an input unit 32 and an output unit 33 . Each component of the HW of payment server 30 is interconnected, by way of example and not limitation, via bus B3. It should be noted that the HW of the payment server 30 does not have to include all components as the HW configuration of the payment server 30 . As an example and not a limitation, the HW of the payment server 30 may or may not have a configuration in which the output unit 33 can be removed.

The control unit 31 comprises, by way of example and without limitation, physically structured circuitry for performing functions implemented by code or instructions contained within a program, such as a data processing device built into hardware. It is realized by

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

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

Communication I/F 34 transmits and receives various data via network N. FIG. Communication by the communication I/F 34 may be performed by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F 34 has a function of communicating with other devices such as the user terminal 20 via the network N. Communication I/F 34 transmits various data to other devices according to instructions from control unit 11 . The communication I/F 34 also receives various data transmitted from other devices and transmits the data to the control unit 31 . Also, the communication I/F 34 may be simply referred to as a communication section. Moreover, when the communication I/F 34 is configured by a physically structured circuit, it may be expressed as a communication circuit.

The input unit 32 is implemented by a device for inputting various operations to the server 30 . The input unit 32 is realized by any one or a combination of all types of devices that can receive input from the user and transmit information related to the received input to the control unit 31 . The input unit 32 is realized by hardware keys typically represented by a keyboard and 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), and a microphone (operation input by voice) as examples without limitation. However, in the present disclosure, the input unit 32 is not limited to these.

The output unit 33 includes, by way of example and not limitation, a display unit 33a. The display unit 33a is typically realized by a monitor (as a non-limiting example, a liquid crystal display or an OELD). The display unit 33a may or may not be a head-mounted display (HDM). 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 storage unit 35. FIG. In the payment server 30, the control section 31 executes the program P3, thereby executing the processing of each section included in the control section 31. FIG. In other words, the program P3 stored in the storage unit 35 causes the payment server 30 to implement 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 implemented by the user terminal 20 and/or the CPU of the server 10 executing a program.

Note that the control unit 21 of the user terminal 20 and/or the control unit 11 of the server 10 is not only a CPU having a control circuit, but also an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)) or the like. Each process may or may not be implemented by a logic circuit (hardware) or a dedicated circuit. Also, these circuits may be realized by one or more integrated circuits, and the plurality of processes shown in each embodiment may or may not be realized by one integrated circuit. LSIs are also called VLSIs, super LSIs, ultra LSIs, etc., depending on the degree of integration. 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 program of each embodiment of the present disclosure (as a non-limiting example, a software program, a computer program, or a program module) may be provided in a state stored in a computer-readable storage medium, It does not have to be. The storage medium can store the program of each embodiment in a "non-temporary tangible medium". Also, the program of each embodiment may or may not be for realizing part of the functions of each embodiment of the present disclosure. Furthermore, the function of each embodiment of the present disclosure may or may not be achieved by combining with a program already recorded in a storage medium, a so-called difference file (difference program).

The storage medium may be one or more semiconductor-based or other integrated circuits (ICs) (such as, without limitation, field programmable gate arrays (FPGAs) or application specific ICs (ASICs)), hard Disk drive (HDD), hybrid hard drive (HHD), optical disk, optical disk drive (ODD), magneto-optical disk, magneto-optical drive, floppy diskette, floppy disk drive (FDD), magnetic tape, solid state It may include a drive (SSD), RAM drive, secure digital card, drive, or any other suitable storage medium, or any suitable combination of two or more thereof. Storage media may, where appropriate, be volatile, nonvolatile, or a combination of volatile and nonvolatile. Note that the storage medium is not limited to these examples, and any device or medium that can store the program P may be used. Also, the storage medium may or may not be expressed as memory.

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

In addition, the program of the present disclosure may or may not be provided to the servers 10 and 30 and/or the user terminal 20 via any transmission medium (communication network, broadcast wave, etc.) capable of transmitting the program. good too. The servers 10 and 30 and/or the user terminal 20 implement the functions of the plurality of functional units shown in each embodiment by executing a program P downloaded via the Internet or the like, for example and not limitation.

Embodiments of the present disclosure may also be implemented in the form of a data signal embedded in a carrier wave in which the program is embodied by electronic transmission. At least part of the processing in the servers 10, 30 and/or the user terminal 20 may be realized by one or more computers (for example, not limitation, cloud computing configured by one or more computers), It doesn't have to be.

At least part of the processing in the user terminal 20 may or may not be performed by the server 10 . In this case, the server 10 may or may not perform at least part of the processing of the functional units of the control unit 21 of the user terminal 20 .

At least part of the processing in the server 10 may or may not be performed by the user terminal 20 . In this case, the user terminal 20 may or may not perform at least part of the processing of the functional units of the control unit 11 of the server 10 .

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

Unless explicitly mentioned, the configuration of determination in the embodiments of the present disclosure is not essential, and predetermined processing is performed when the determination condition is satisfied, or predetermined processing is performed when the determination condition is not satisfied. may or may not.

It should be noted that the programs of the present disclosure are not limited to examples, but include script languages such as ActionScript and JavaScript (registered trademark), object-oriented programming languages such as Objective-C and Java (registered trademark), markup languages such as HTML5, and the like. implemented using

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

In the following description, the user of the user terminal 20A is referred to as user A, the user of the user terminal 20B is referred to as user B, and the user of the user terminal 20C is referred to 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 consist of user A and user B, and the number of users included in this group is two. Another group may consist of User A, User B and User C, and the number of users included in this group is three.

Also, in the following description, a service provided by the information processing according to the embodiment will be referred to as a messaging service as appropriate. User terminal 20 displays, by way of example and not limitation, an image of a graphical user interface (hereinafter referred to as GUI) provided by the messaging service. In the following description, a GUI that allows users included in a group to view content transmitted and received between terminals of a group including a plurality of users will be referred to as a talk room as appropriate. Also, the talk room may be called a chat room. Here, a talk room is, by way of example and not limitation, a display area in which messages can be sent and received between participating users. In addition, for example and not limitation, the talk room may be one in which a name different from the user name registered in the server 10 can be used within its area. Also, by way of example and not limitation, a chat room may allow messages to be sent and received without a friendship, following, or followed relationship between participating users.

The content includes, by way of example and not limitation, at least one of text, images, and audio. The text included in the content includes, as a non-limiting example, at least one of national characters represented by character codes, extended characters, machine-dependent characters, numerals, symbols, graphics, and symbols. The text included in the content may not include at least one of the characters, extended characters, machine-dependent characters, numerals, symbols, graphics, and symbols, and may include other text.

Examples of images included in the content include, but are not limited to, captured images captured by a camera, processed images obtained by subjecting captured images to image processing, and computer graphics images generated using a computer (as examples, not limited to , icons, pictograms, emoticons), and at least one of text images that are images of text. An image included in the content may include a synthesized image obtained by synthesizing two or more of various images such as the captured image, the processed image, the computer graphics image, and the text image. Images included in the content may not include at least one of the captured image, the processed image, the computer graphics image, the text image, and the synthesized image, and may include other images. The images included in the content may be still images, moving images, or images in other forms. Content that includes images may be represented by icons, such as thumbnails, in the chat room images, for example and not by way of limitation. By way of example and not limitation, the user terminal 20 may display images included in content based on input to icons representing images included in the content.

Sounds included in the content include, but are not limited to, recorded sounds recorded with a microphone, processed sounds processed by recording sounds, synthesized sounds generated using a computer, and computer read-aloud functions. includes at least one read-aloud speech converted from text using The sound contained in the content may include a combined sound obtained by combining two or more of the above recorded sounds, processed sounds, synthesized sounds, and read-out sounds. The voice included in the content may not include at least one of the recorded voice, processed voice, synthesized voice, reading voice, and combined voice, and may include other voices. The audio included in the content may include at least one of sounds or voices emitted by humans or living things other than humans, sounds emitted by objects such as musical instruments or machines, sound effects, environmental sounds, noise sounds, and alarms, At least one of these sounds or voices may not be included, or a voice different from these sounds or voices may be included. Content that includes audio may be represented, for example and not by way of limitation, in an image of the talk room, such as by an icon. As an example and not a limitation, the user terminal 20 may reproduce the audio included in the content based on an input to an icon representing the audio included in the content.

The content may be, by way of example and not limitation, content that combines two or more of text, images, and audio. Content may be, by way of example and not limitation, content in which video and audio are played in parallel, content in which images and text are displayed in combination, and text is displayed in sync with audio playback. It may be content that The content may also be content in which audio is played in parallel with the display of text and images. The content may be, by way of example and not limitation, content that combines at least one of text, images and audio with content that is different from any of the text, images and audio.

The storage unit 15 of the server 10 stores, by way of example and not limitation, information used in messaging services. The information includes, by way of example and not limitation, user information D11, talk room information D12, content information D13, remittance account information D14, and remittance history information D15. User information D11 includes, by way of example and not limitation, user IDs and passwords associated with each account in the messaging service. In the messaging service, the user terminal 20 transmits account information D21 to the server 10. FIG. When the server 10 receives the account information D21 transmitted by the user terminal 20, the server 10 collates the user ID and password included 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, the content information D13, the remittance account information D14, and the remittance history information D15 will be described later.

The storage unit 25 of the user terminal 20 stores, by way of example and not limitation, information used in messaging services. The information includes, by way of example and not 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, the content information D23, the remittance account information D24, and the remittance history information D25 will be described later.

The account information D21 is account information used by the user of the user terminal 20 in the messaging service. The account information D21 is information used for user authentication in the messaging service. Account information D21 includes, by way of example and not limitation, user identification information and a password. User identification information will be referred to as a user ID as appropriate in the following description. The user ID may be information registered by the user of the user terminal 20 or information given in the messaging service.

Note that the storage unit 25 may not store one or both of the user ID and password. For example, the user may operate the input/output unit 23 of the user terminal 20 to input necessary information out of the user ID and password when the user is authenticated in the messaging service. Also, the account information D21 may include information different from the user ID and password. For example, when user authentication is performed by biometric authentication, the account information D21 may include information such as the user's fingerprint, vein pattern, and facial photograph as information used for biometric authentication.

In addition, the storage unit 25 does not need to store at least part of the information used for the messaging service (for example, without limitation, the chat room information D22, the content information D23, the remittance account information D24, and the remittance history information D25). For example, at least part of the information used for the messaging service may be stored in a storage unit external to the user terminal 20 (as an example and not a limitation, the storage unit 15 of the server 10). The information used for the service may be obtained via the network N from a storage unit external to the user terminal 20 as an example and not a limitation.
<First embodiment>

FIG. 2 is a diagram showing information processing according to the first embodiment. An outline of this embodiment will be described. By way of example and not limitation, the server 10 may transfer content input by a user at the user terminal 20 of a certain user in which a talk room in which a plurality of users participates is displayed and transmitted from the user terminal 20 to another user's user. Send to terminal 20 . In addition, as an example and not a limitation, the server 10 sends content input by another user to the user terminal 20 of another user on which the talk room is displayed and transmitted from the user terminal 20 to the user terminal 20 of a certain user. Send. In this embodiment, as an example and not a limitation, in a talk room, remittance is performed from the user terminal 20 of a certain user to the user terminal 20 of another user. In the present embodiment, the user terminal 20 of another user requests the server 10 to process remittance via the communication unit (communication I/F 24 as an example, not limitation). Server 10 performs the remittance process based on the remittance process request, by way of example and not limitation.

The outline of the remittance process will be described below. The remittance process is a process of remittance from a user's remittance account to another user's remittance account in the chat room. Here, the remittance in the remittance process means, as an example and not a limitation, sending and receiving information regarding payment means using information communication technology. Here, the payment means using information communication technology is not limited to, but includes electronic value, electronic money, and the like. Electronic value and electronic money include, by way of example and not limitation, information indicating money, electronic money, points, and the like. Hereinafter, information on payment means using information communication technology will be referred to as "value". Specifically, the user terminal 20 displays in the display area 28 a remittance setting image T4 for setting remittance details shown in FIG. Then, in FIG. 2B(e), the user terminal 20 receives an input from a certain user to the input unit 22 to specify the remittance account and the remittance amount used for remittance. As an example and not a limitation, the user terminal 20 transmits a remittance processing request including information regarding remittance to the server 10 when the remittance content is confirmed. Server 10 identifies, by way of example and not limitation, the remittance account included in the information regarding the remittance. Server 10 transmits, by way of example and not limitation, information regarding the remittance to payment server 30 corresponding to the identified remittance account. Payment server 30, by way of example and not limitation, completes a transfer from one user to another user by updating transfer account information D31.

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

Next, the present embodiment will be described in detail with reference to FIGS. 2 to 4 as appropriate, and the contents described in the present embodiment can be applied to other embodiments as appropriate. In this embodiment, the same reference numerals are assigned to the same configurations as in the above-described embodiment, and the description thereof will be omitted or simplified. 2A and 2B, it is assumed that user A, user B, and user C constitute a talk room.

First, each image related to the talk room in this embodiment will be described. Symbol TL in FIG. 2A(a) is an image showing a list of talk rooms. As an example and not a limitation, the user terminal 20 displays an image TL of a list of talk rooms associated with the own terminal or the user of the own terminal in the display area 28 . Note that the user terminal 20 may display in the display area 28 an image TL of a list of talk rooms that are not associated with the user of the terminal or its own terminal, 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", "Athletic meet", and "I love baseball" are icons with names of talk rooms. An icon is, by way of example and not limitation, an image displayed in display area 28 . As a non-limiting example, the user terminal 20 determines that a talk room with the name "Coffee party" has been selected when an input is made to the input unit 22 for the icon "Coffee party". When there is an input in the input unit 22 with respect to the icon of "Coffee party" displayed in the display area 28, the user terminal 20 determines that the talk room with the name "Coffee party" has been selected. As shown in (b), the image T1 of the talk room with the name "coffee party" is displayed in the display area 28. FIG.

Here, each user can create a talk room, by way of example and not limitation. When each user creates a talk room, by way of example and not limitation, one or more users are selected, and a talk room including the users selected by the user is created by the server 10 . As an example and not a limitation, a talk room may be created without each user selecting one or more users. Note that the process of creating a talk room is not limited to being executed by the server 10 , and may be executed by the user terminal 20 or by the user terminal 20 and the server 10 . A device different from the user terminal 20 and the server 10 may execute the process of generating the talk room.

In the following description, it is assumed that user A has created a talk room "Coffee party" in this embodiment. It is also assumed that user B and user C are participating in the talk room "Coffee party". Hereinafter, User A may be referred to as "manager", and User B and User C may be referred to as "participants". Here, the manager is, as an example and not a limitation, a user selected from the users who created the talk room and the users participating in the talk room. As an example and not as a limitation, the administrator may also be referred to as a "master". A participant is, for example and not limitation, a user who is different from the manager and who participates in the generated talk room. As an example and not a limitation, the user terminal 20 of the participant determines that the icon is selected when there is an input in the input unit 22 with respect to the icon with the name of the talk room, and A participant may join the talk room by sending a request to the server 10 to join the chat room. In addition, as an example and not a limitation, when a predetermined URL is input to the input unit 22, the participant's user terminal 20 determines that the URL has been selected, and determines that the URL is associated with the talk room. An image may be displayed in the display area 28 and the participant may participate in the talk room. Also, as an example and not limitation, the participant's user terminal 20 may allow the participant to participate in the talk room based on the 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. The name of the talk room is set to the name entered by the administrator, by way of example and not limitation. The name of the talk room may be, for example and not limitation, a name automatically given in the messaging service, or may be represented by identification information of the talk room.

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

In the image T2 of the talk room shown in FIG. 2A(c), the symbol Tb is an icon (a remittance setting icon as an example, not a limitation) for making settings related to remittance. The remittance setting icon Tb includes, as a non-limiting example, a plurality of icons (as a non-limiting example, "remittance setting", "remittance", "receipt setting", "receipt cancellation", "receipt change", "destruction condition"). , “report”, “refund”, “remittance request”, and “withdrawal”). The user terminal 20 displays an image corresponding to the icon in the display area 28 when a predetermined icon included in the remittance setting icon Tb is input to the input unit 22 . Note that the remittance setting icon Tb shown in FIG. 2A(c) is an example, and is not limited to this.

Also, in image T7 of the talk room in FIG. 2B(h), content Q2 and content Q3 are transmitted from a terminal (here, user terminal 20B or user terminal 20C) different from its own terminal (here, user terminal 20A). content. In the following description, a terminal different from the own terminal will be referred to as another terminal as appropriate. 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, content Q2 and content Q3 in image T7 of the chat room in FIG. It is arranged on the side opposite to the content Q1 in the horizontal direction of T7. 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 layout of the content Q1 in FIG. In comparison, they are arranged at different positions in the second direction.

In addition, as a non-limiting example, the user terminal 20 sets each content transmitted from another terminal and information related to the user of the user terminal 20 that transmitted this content, and arranges them in the image of the talk room. . The information about the user includes, by way of example and not limitation, at least one of an indication of the user's icon, the user's name, the user ID, and the user's nickname. In images T4 and T7 of the talk room in FIGS. 2B(e) and 2B(h), symbols Ua1, Ub1, and Uc1 are icons of user A, user B, and user C, respectively. Also, in images T4 and T7 of the talk room, symbols Ua2, Ub2, and Uc2 are the user names of user A, user B, and user C, respectively.

In the image T7 of the talk room in FIG. 2B(h), the symbol Ub1 is the icon of the user of the other terminal (here, the user terminal 20B) that transmitted the content. The user terminal 20A arranges the content Q2 and the icon Ub1 of the user of the user terminal 20B that transmitted the content Q2 (here, user B) in the talk room image T7 so as to have a predetermined positional relationship. It should be noted that, as an example and not a limitation, the user terminal 20 is capable of transmitting and receiving content including messages regardless of whether remittance processing is executed. Further, the information about the user may not include at least one of the user icon, user name, user ID, and user nickname. It may contain information different from the display. The user terminal 20 does not have to include the information about the user in the image of the talk room.

As an example and not a limitation, the user terminal 20 arranges the content in each talk room in the first direction in order of the time of transmission, and displays an image of each talk room in the display area 28 . For example, in image T7 of the chat room shown in FIG. 2B(h), content Q2 is content transmitted after content Q1, content Q3 is content transmitted after content Q2. It is arranged below the content Q1 in the vertical direction of the image T7.

An outline of each device constituting the communication system 1 will be described below. First, an outline of the operation of the server 10 will be described. When receiving a remittance processing request from the user terminal 20, the server 10 stores the remittance processing request in the storage unit 15 as an example and not as a limitation. As an example and not a limitation, the server 10 collates the user IDs of the remittance source and remittee included in the remittance processing request with the talk room information D12 to identify the remittance source and remittee users in the talk room. By way of example and not limitation, the server 10 matches the remittance account included in the remittance process request with the remittance account information D14 to identify the remittance account for the remittance. By way of example and not limitation, the server 10 identifies the remittance amount included in the remittance process request. By way of example and not limitation, the server 10 transmits remittance information to the payment server 30 to update the value corresponding to the "remittance account ID" based on the specified 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 remittance source and the remittance destination as the destination as a result of processing related to remittance in the payment server 30, and content indicating that the remittance is completed. to transmit (eg, distribute) The server 10 updates the remittance history information D15 when transmitting the content. When receiving the content transmitted by the server 10 , the user terminal 20 transmits a reception notification to the server 10 as an example and not as a limitation. When the server 10 receives the notification of reception transmitted by the user terminal 20, as an example and not limitation, the server 10 may delete the content associated with the notification of reception from the content information D13.

Next, an example of talk room information D12, an example of content information D13, an example of remittance account information D14, and an example of remittance history information D15, which are referred to in the operation of server 10, will be described. FIG. 3A is a diagram showing an example of the talk room information D12. The chat room information D12 includes, by way of example and not limitation, [chat room ID], [name], [user ID], [creator ID], [remittance recipient ID], [sender ID], and [content list ] items. [Talk room ID] is an item containing identification information of the talk room. The chat room ID is provided in the messaging service, by way of example and not limitation, when the user creates the chat room.

[Name] is an item indicating the name of the talk room as an example and not as a limitation. [Name] is associated with [Talk Room ID]. For example, the [name] of the talk room whose [talk room ID] is [tr01] is [coffee party]. Also, the [name] of the talk room whose [talk room ID] is [tr02] is [tea party]. Also, the [name] of the talk room whose [talk room ID] is [tr03] is [athletic meet].

[User ID] is an item indicating identification information of a user included in a group corresponding to each talk room, as an example and not a limitation. [User ID] is associated with [Talk room ID]. For example, the users included in the group corresponding to the talk room whose [chat room ID] is "tr01" are user A, user B, and user C, and the [user ID] corresponding to "tr01" is the user It contains A's user ID, user B's user ID, and user C's user ID. Likewise, users A, B, and C are included in the groups corresponding to the talk rooms whose [talk room ID] are "tr02" and "tr03".

[Creator ID] is an item indicating the identification information of the user who created each talk room, as an example and not as a limitation. [Generator ID] is associated with [Talk room ID]. For example, the user A is the user who created the talk room with the [chat room ID] of "tr01", and the [creator ID] corresponding to "tr01" includes the user A's user ID. Further, for example, the user A is also the user who created the talk rooms "tr02"] and "tr03".

[Remittance Recipient ID] is, by way of example and not limitation, an item indicating identification information of a user (remittance recipient as an example, not limitation) who can receive money transfer in each chat room. [Remittance recipient ID] is associated with [Talk room ID]. For example, in a chat room whose [chat room ID] is "tr01", the user who can receive remittance is user A, and the [remittance recipient ID] corresponding to "tr01" includes user A's user ID. . That is, the talk room "tr01" is set so that only user A can receive remittance. Also, for example, in a talk room with a [chat room ID] of "tr02", the user who can receive money is user B, and the [remittance recipient ID] corresponding to "tr02" is user B's user ID. including. Also, for example, in a talk room with a [chat room ID] of "tr03", the user who can receive remittance is user A, and the [remittance recipient ID] corresponding to "tr03" is user A's user ID. including. By way of example and not limitation, the server 10 may automatically set the [Remittance Recipient ID] to the manager's user ID when the chat room is created, or based on information set by the manager. , or may be set based on information set by the participant at arbitrary timing.

[Sender ID] is an item indicating, as an example and not a limitation, identification information of a user who can send money in each chat room (as an example, not a limitation, a sender). [Sender ID] is associated with [Talk Room ID]. For example, in a chat room whose [chat room ID] is "tr01", users who can send money are user B and user C, and the [sender ID] corresponding to "tr01" is the user ID of user B and user C. including. That is, the chat room with "tr01" is set so that only users B and C can send money to user A. Also, for example, in the talk room with [chat room ID] of "tr02", remittance is possible. The valid users are user A and user C, and the [sender ID] corresponding to "tr02" includes the user IDs of user A and user C. Also, for example, in a talk room with a [chat room ID] of "tr03", only user B can send money, and the [sender ID] corresponding to "tr03" is user B's user ID. include. As an example and not a limitation, the server 10 may automatically set the user ID set in [Sender ID] to the user ID of the participant when the user participates in the talk room, It may be set based on information set by the manager at arbitrary timing, or may be set based on information set by the participant at arbitrary timing. As an example and not a limitation, the talk room information D12 may not include the [sender ID] item. In this case, the server 10 may automatically set the user ID of the participant who participated in the talk room in [sender ID] as an example and not as a limitation.

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

FIG. 3B is a diagram showing an example of the content information D13. FIG. 3B is part of the content information D13 and corresponds to "list 1" in FIG. 3A. The content information D13 includes, by way of example and not limitation, items of [content ID], [transmitting user ID], and [content].

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

[Transmitting user ID] is an item indicating the user ID corresponding to the user terminal 20 that transmitted each content, as an example and not as a limitation. [Sending User ID] is associated with [Content ID]. For example, the user corresponding to the user terminal 20 that sent the content with the [content ID] of "tr01c01" is user A, and the [transmitting user ID] corresponding to "tr01c01" includes user A's user ID. The user corresponding to the user terminal 20 that transmitted the content with the [content ID] of "tr01c02" is user B, and the [transmitting user ID] corresponding to "tr01c02" includes user B's user ID.

[Content] is an item that indicates, by way of example and not limitation, content submitted by the user. [Content] is associated with [Content ID]. If the content contains text, [content] stores the text data of the content. For example, the content Q1 shown in FIG. 2B is the text "1,000 yen per person." data is stored. Content Q2 and content Q3 shown in FIG. 2(f) are the text "Remittance completed." The text data representing "Remittance has been sent" is stored. When the content includes an image, [content] stores image data, a link to the image data, or the address of the storage section where the image data is stored. The image data may include, by way of example and not limitation, still image data or moving image data. The image data may or may not include, by way of example and not limitation, data representing stamps, stickers, emojis, and emoticons. When the content includes audio, [Content] stores audio data, a link to the audio data, or the address of the storage section in which the audio data is stored.

FIG. 3C is a diagram showing an example of remittance account information D14. Remittance account information D14 includes, by way of example and not limitation, items of [user ID] and [remittance account ID]. [User ID] is an item indicating user identification information, by way of example and not limitation.

[Remittance Account ID] is an item indicating 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 remittance account A, remittance account B, and remittance account C Contains an ID.

FIG. 3D is a diagram showing an example of remittance history information D15. The remittance history information D15 includes, by way of example and not limitation, items of [chat room ID], [date and time], [remittance recipient ID], [sender ID], [remittance amount], and [remittance account]. [Chat Room ID], [Remittance Recipient ID], and [Sender ID] are the same as those described with reference to FIG. 3A, for example and not limitation, and descriptions thereof will be omitted. [Date and time] is an item indicating the date and time when the talk room ID was assigned. [Transfer Amount] is an item showing information indicating the amount of value transferred by the user. [Transfer amount] is associated with [Talk room ID]. That is, in the talk room tr01 of FIG. 3D, the value of "1,000" is transferred from the user B to the user A at "10:00 on January 1, 2020". A value of '1,000' is transferred from user C to user A at '00 minutes'.

Next, an overview of the operation of the user terminal 20 will be described. The user terminal 20 refers to the talk room information D22 and the content information D23 shown in FIG. As an example and not a limitation, the user terminal 20 receives input from the user to the input unit 22, refers to the chat room information D22 and the remittance account information D24, and refers to remittance sources, remittance destinations, remittance amounts, and remittance accounts. A remittance processing request including information is sent to the server 10 . User terminal 20 receives remittance history information from server 10 by way of example and not limitation. The user terminal 20 stores the received remittance history information in the storage unit 25 as an example and not as a limitation. As an example and not a limitation, the user terminal 20 may refer to the remittance history information D25 and display in the display area 28 an image of a talk room including content indicating that the remittance process has been completed.

Next, an example of talk room information D22, an example of content information D23, an example of remittance account information D24, and an example of remittance history information D25, which are referred to in the operation of user terminal 20, will be described. Note that the user terminal 20 does not have to store the remittance account information D24 and the remittance history information D25 in the storage unit 25 as an example and not as a limitation.

The talk room information D<b>22 is, by way of example and not limitation, information about a talk room associated with the user of the user terminal 20 . Since the items included in the talk room information D22 are the same as those in the talk room information D12, description thereof will be omitted.

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

The remittance account information D<b>24 is, by way of example and not limitation, information about a remittance account associated with the user of the user terminal 20 . Since the items included in the remittance account information D24 are the same as those in the remittance account information D14, description thereof will be omitted.

The remittance history information D<b>25 is information about remittance in the talk room associated with the user of the user terminal 20 as an example and not limitation. Since the items included in the remittance history information D25 are the same as those in the remittance history information D15, description thereof will be omitted.

Next, an outline of the operation of the payment server 30 will be described. When the payment server 30 receives the remittance information from the server 10, the payment server 30 stores the remittance information in the storage unit 35 as an example and not as a limitation. By way of example and not limitation, payment server 30 identifies the source and destination remittance account IDs included in the remittance information. As an example and not a limitation, the payment server 30 refers to the remittance account information D31 to determine the value corresponding to the remittance amount from the value corresponding to the remittance account ID of the remittance source and the value corresponding to the remittance account ID of the remittee. (for example, but not by way of limitation, processing related to remittances). The payment server 30, by way of example and not limitation, sends a notification to the server 10 regarding the outcome of the transaction regarding the transfer.

Next, an example of the remittance account information D31 referred to in the operation of the payment server 30 will be described. The remittance account information D<b>31 is, by way of example and not limitation, information about a remittance account associated with the user of the user terminal 20 . FIG. 4 is a diagram showing an example of remittance account information D31. The remittance account information D31 includes, by way of example and not limitation, items of [user ID], [remittance account ID], and [value]. The [user ID] and [remittance account ID] are the same as the [user ID] and [remittance account ID] of the remittance account information D14, so description thereof will be omitted. [Value] is an item that indicates, by way of example and not limitation, an amount of value. [Value] is associated with [Remittance Account ID].

Next, settings related to remittance for each user in the server 10 will be described. As an example and not a limitation, when a talk room is created by a manager, the server 10 associates the manager's user ID with the talk room ID as shown in the talk room information D12 of FIG. ] and [Producer ID]. When receiving a participation request from a participant, the server 10 registers the user ID of the participant in the [user ID] item in association with the talk room ID, as in the talk room information D12. Then, the server 10 makes settings related to remittance as an example and not as a limitation. The settings for remittances are, by way of example and not limitation, setting the user IDs of the manager and participants in the items of [Remittance Recipient ID] or [Sender ID]. By way of example and not limitation, the server 10 may set the remittance settings based on information about predetermined settings, or may set the remittance settings based on information about settings defined by an administrator or a participant. May be set.

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 flow chart showing the procedure of information processing according to the first embodiment. Here, FIG. 5 shows, as an example and not a limitation, a procedure from when a manager creates a chat room to when a participant completes remittance to the manager. Hereinafter, as an example and not limitation, user A is the administrator, user B and user C are participants, and a talk room in which user A, user B, and user C participate is called a "coffee party."

First, in step S<b>111 , the user terminal 20</b>A generates a creation request for the talk room A to the server 10 based on the input from the user A to the input unit 22 . In step 112, the user terminal 20A transmits a creation request to the server 10 via the communication I/F24. 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, user ID, and creator ID in the talk room information D12 based on the creation request (see FIG. 3A). As an example and not a limitation, when a 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 the talk room information D12 (see FIG. 3A) in the storage unit 25 as an example and not a limitation. As an example and not a limitation, the user terminal 20A reads the talk room information D22 and generates the image TL of the 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. FIG. Then, when there is an input in the input unit 22 with respect to the icon of the talk room "Coffee party", the user terminal 20A determines that the talk room "Coffee party" has been selected, and determines that the talk room "Coffee party" has been selected. An image is displayed on the display area 28 .

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

Next, in step S131, the user terminal 20B displays the chat room list image TL as shown in FIG. display. The user terminal 20B determines that the talk room "Coffee party" is selected when there is an input in the input unit 22 for the "Coffee party" icon in the list. As an example and not a limitation, the user terminal 20B generates a participation request for requesting the server 10 to participate in the talk room "Coffee Party" when it is determined that "Coffee Party" has been selected. Then, in step S132, the user terminal 20B transmits a participation request to the talk room "Coffee party" to the server 10 via the communication I/F 24. FIG. 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 the user B in the talk room information D12 based on the participation request (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 receives the content information D13 from the server 10, and the content as shown in FIG. An image T1 including Q1 may be displayed in the display area 28. FIG.

Note that before step S131, the server 10 transmits a participation request to the user terminals 20 (here, the user terminals 20B and 20C) to participate in the talk room, for example and not limitation. good too. In this case, as a non-limiting example, when receiving a participation request from the server 10, the user terminal 20 may cause the display area 28 to display an image including a message text requesting participation in the talk room "Coffee Party". Then, an image T4 as shown in FIG.

Next, in step S133, the server 10 transmits the talk room information D12 in which the user ID of the participant is registered (here, participation information) to the user terminal 20A as an example and not a limitation. The user terminal 20A stores the participation information in the storage unit 25 as an example and not as a limitation.

Next, in step S141, the user terminal 20A causes the display area 28 to display an image T2 of the talk room including the content Q1 as shown in FIG. As a non-limiting example, the user terminal 20A determines that the icon PL has been selected when there is an input to the input unit 22 for the icon PL in the display area 28, and determines that the icon PL is selected as shown in FIG. 2A(c). A selection image T2 including a remittance setting icon Tb is displayed in the display area . Then, as an example and not a limitation, the user terminal 20A determines that "remittance setting" is selected when there is an input in the input unit 22 for the icon "remittance setting" in FIG. 2A(c). As an example and not a limitation, the user terminal 20A refers to the talk room information D22 and causes the display area 28 to display a remittance setting image T3 shown in FIG. 2A(d). The remittance setting image T3 includes, by way of example and not limitation, a remittance recipient setting portion T3a, a remitter setting portion T3b, and a setting determination portion T3c. As a non-limiting example, the remittance recipient setting unit T3a sets a user to be a remittance recipient by displaying the name of the user whose user ID is associated with the talk room "Coffee Party" based on the talk room information D22. It is an area for As an example and not a limitation, the remitter setting unit T3b displays the name of the user whose user ID is associated with the talk room "Coffee party" based on the talk room information D22, in order to set the user who will be the remitter. is the area of Here, the remittance recipient setting unit T3a and the remitter setting unit T3b, as an example and not a limitation, when there is an input in the input unit 22, in a predetermined display format (as an example, not a limitation, a pull-down) The user's name may be displayed. The remittance recipient setting section T3a and the remitter setting section T3b may be, for example and not limitation, a text box or the like that accepts input of the user's name. As a non-limiting example, the setting confirming unit T3c, when there is an input in the input unit 22, information (as a non-limiting example, first setting information). Then, in step S142, the user terminal 20A transmits the first setting information to the server 10. FIG. In the above description, the first setting information is generated by the manager (here, user A) who generated the talk room, but the present invention is not limited to this. As an example and not a limitation, the first setting information may be generated by a participant in the generated talk room (here, user B or user C). Also, the server 10 has been described as setting the first setting in step S141, but the present invention is not limited to this. By way of example and not limitation, the server 10 may set the first settings automatically or based on setting information generated by the administrator when receiving the creation request from the user terminal 20A in step S121, The first setting may be set automatically or based on the setting information generated by the manager when the participation request is received from the user terminal 20 in step S131, and the timing at which the first setting is set is not limited. .

Here, setting contents of the first setting will 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. As an example and not a limitation, "setting" may mean that the user ID of at least one of the manager or the participant is given authority, power, responsibility, or the like regarding remittance.

First, if the first setting is automatically set by the server 10, the server 10, by way of example and not limitation, sets the user ID of the manager when the chat room is created by the manager [remittance recipient ID]. , and the participant's user ID may be registered in [sender ID] when a participation request is received from the participant. In this case, the manager's user ID is registered in [remittance recipient ID], and the participant's user ID is registered in [sender ID], such that the chat room ID in FIG. 3A is "tr01". As a result, remittance from the participants to the manager in the talk room becomes possible. In other words, in this case, the first setting is a setting in which the user participating in the talk room cannot transfer money to the participant.

Next, when the first setting is set by the user, the user IDs registered in [remittance recipient ID] and [sender ID] are set arbitrarily. Specifically, the server 10 registers the user ID of one of the participants in the [remittance recipient ID], such as the chat room ID of FIG. The user IDs of the administrator and other participants may be registered in [Sender ID]. As a result, remittance can be made from the manager and other participants to one of the participants in the talk room. As a non-limiting example, the manager's user ID is registered in the [remittance recipient ID], and the specific participant among the participants is registered in the [sender ID], such as the chat room ID of FIG. 3A being "tr03". may be registered. As a result, it becomes possible for only specific participants in the talk room to send money to the manager.

Next, in step S151, the server 10 registers the user ID in the [remittance recipient ID] and [sender ID] of the talk room information D12 based on the first setting information as an example and not limitation.

Next, in step S161, the user terminal 20B causes the display area 28 to display an image T4 of the talk room including the content Q1 as shown in FIG. 2B(e), for example and not limitation. As a non-limiting example, the user terminal 20B determines that the icon PL in the display area 28 is selected when there is an input in the input unit 22, and sets the remittance setting shown in FIG. 2B(f). A selection image T5 including the icon Tb is displayed in the display area . As an example and not a limitation, when the user terminal 20B receives an input in the input unit 22 for the icon "remittance" in FIG. 2B(f) in the display area 28, the icon "remittance ” is selected. The user terminal 20B then refers to the talk room information D22 and the remittance account information D24 to display the remittance registration image T6 shown in FIG. Remittance registration image T6 includes, by way of example and not limitation, remittance destination T61, remittance account setting portion T62, remittance available amount T63, remittance amount input portion T64, and remittance confirmation portion T65. The remittance destination T61 is an area for displaying the remittance destination specified by referring to the talk room information D22 as an example and not a limitation. As a non-limiting example, the remittance account setting unit T62 sets a remittance account corresponding to a remittance account ID that can be used in a predetermined display format (as an example, not a limitation, pull-down) when there is an input in the input unit 22. This is an area for displaying the name of the account. Note that the remittance account setting unit T62 may be, for example and not limitation, a text box or the like that accepts and displays the name of the remittance account input by the user. The remittable amount T63 is, by way of 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 an area for displaying the input remittance amount when there is an input in the input section 22, as an example and not a limitation. As a non-limiting example, the remittance confirmation unit T65 confirms the above-described remittance-related information (as a non-limiting example, remittance information) when there is an input in the input unit 22 . Then, in step S162, the user terminal 20B transmits to the server 10 a remittance processing request including remittance information. Here, the remittance processing request is, as an example and not a limitation, information for requesting the server 10 to perform remittance processing by user B, who sends remittance, to user A, who receives remittance. As an example and not a limitation, steps S161 and S162 are similarly executed in the user terminal 20C.

Next, in step S<b>171 , the server 10 stores the remittance processing request in the storage unit 15 . As an example and not a limitation, the server 10 collates the user ID of user B with the user ID of [sender ID] of the talk room information D12 based on the remittance processing request. As a non-limiting example, if the user ID of user B and the user ID of [remitter ID] match as a result of collation, the control unit 11 proceeds to remittance processing. As an example and not a limitation, the control unit 11 identifies the user IDs of the remittance source and the remittance destination, the remittance account, and the remittance amount based on the remittance information. Server 10 sends, by way of example and not limitation, a remittance advice to payment server 30 that includes information regarding the source and destination user IDs, the remittance account, and the remittance amount. 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 remittance source to the value of the remittance account corresponding to the user ID of the remittee. The payment server 30, by way of example and not limitation, transmits information to the server 10 regarding the outcome of the transaction regarding the money transfer. This completes the remittance process.

Next, in step S172, the server 10 transmits to the user terminal 20 a remittance completion notification including information regarding the remittance amount. Based on the remittance completion notification, the user terminal 20A, as an example and not as a limitation, remits content Q2 and content Q3 (as an example, not as a limitation) indicating remittance completion as shown in FIG. 2B(h). ) is displayed. As an example and not a limitation, the user terminal 20B and the user terminal 20C similarly display images including the content Q2 and the content Q3. Thereby, the user of the talk room can confirm the remittance status in the talk room.
<First modification>

Information processing according to the first modification will be described with reference to FIG. FIG. 6 is a diagram showing an example of the relationship information D16. The information processing according to the first modification is a form in which the manager and participants of the chat room can execute remittance to other users in the chat room even if they do not have a predetermined relationship in the messaging service. . Here, "predetermined relationship" refers, by way of example and not limitation, to a mutually recognizable relationship between users in a messaging service. For example, the predetermined relationship is a friend relationship, a followed relationship, a following relationship, and the like. In addition, the server 10 may have relationship information D16 indicating the above relationship between users, as an example and not a limitation. The relationship information D16 includes, by way of example and not limitation, at least one of the items [user ID], [friend relationship], [follow 1], and [follow 2]. The relationship information D16 may further include items that indicate mutually recognizable relationships between users.

[friend relationship] is an item indicating a user ID having a friend relationship with a certain user. [Friendship] is associated with [User ID]. "Friendship" refers, by way of example and not limitation, to a relationship in a messaging service that has mutually identifiable information. Specifically, as an example and not as a limitation, the telephone number corresponding to the user terminal 20A of a certain user (here, user A) and the user terminal 20B of another user (here, user B) is the user B's contact number. If they are registered first, user A and user B are "friends". Also, as an example and not a limitation, if a messaging account corresponding to user B is registered in user A's user terminal 20A, user A and user B are in a "friend relationship." Also, as an example and not a limitation, if a phone number corresponding to user A's user terminal 20A is registered in user B's user terminal 20B as user A's contact address, user B and user A have a "friend relationship". is. Also, as an example and not a limitation, if a messaging account corresponding to user A is registered in user B's user terminal 20B, user B and user A are in a "friend relationship." Further, as an example and not a limitation, when a messaging account corresponding to user B's user terminal 20B registered in user A's user terminal 20A is also registered in user C's user terminal 20C, user A and user C is "friendship". For example, in FIG. 6, it is the relationship between user A and user C who have user D as a common friend.

[Follow 1] is an item indicating the user ID of a user who is followed by a certain user. [Follow 1] is associated with [User ID]. "Followed relationship" means, as an example and not a limitation, an account containing content provided by the user terminal 20 of another user (here, user B) in a messaging service, a certain user (here, user B) A) refers to the relationship between user A and user B registered in the user terminal 20 of A). In this case, the relationship between user A and user B is that user B is followed by user A. Specifically, as an example and not a limitation, the user terminal 20A of the user A uses the account registration section (as an example and not a limitation, "Follow") displayed in the display area 28 in the content on the messaging service for the user B. ), when there is an input in the input unit 22, the information on account registration is transmitted to the server 10. FIG. The server 10 registers the relationship that the user A is followed by the user B by updating the relationship information D16 based on the information regarding account registration.

[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]. "Following relationship" means that, as an example and not a limitation, in a messaging service, the user terminal 20 of another user (here, user B) provides the user terminal 20 of a certain user (here, user A). Refers to the relationship between User B and User A who have registered an account containing content. In this case, the relationship between user B and user A is that user B follows user A. Specifically, as an example and not a limitation, the user terminal 20B of the user B uses the account registration section (as an example and not a limitation, "Follow") displayed in the display area 28 in the content on the messaging service for the user A. ), when there is an input in the input unit 22, the information on account registration is transmitted to the server 10. FIG. The server 10 registers the relationship that the user B follows the user A by updating the relationship information D16 based on the information regarding account registration.
<Second modification>

Information processing according to the second modification will be described with reference to FIG. FIG. 7 is a diagram showing an image T8 of a talk room in which an indication regarding setting of a predetermined relationship is displayed. The information processing according to the second modified example sets at least one of a friend relationship, a followed relationship, and a following relationship in the image of the chat room as shown in FIG. 7 as an example and not a limitation. It is a form including a display for (here, "add friend"). When an input is made to the input unit 22 with respect to the “add friend” icon T81, the control unit 21 determines that “add friend” has been selected, and displays an image for setting a friend relationship in the display area 28. to display. By way of example and not limitation, so are the indications for setting followed relationships and the indications for setting following relationships. As an example and not a limitation, as shown in FIG. 7, a display for setting at least one of a friend relationship, a followed relationship, and a following relationship (here, " Friend addition") may not be included. By excluding the display regarding the setting of a predetermined relationship, it is possible to eliminate the establishment of a friend relationship, a followed relationship, and a following relationship between users in the chat room.
<Third modification>

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

According to this embodiment, the server 10 transmits to the user terminal 20B content transmitted by user A's input to the input unit 22 of the user terminal 20A, and user B's input to the input unit 22 of the user terminal 20B. to the user terminal 20A. The control unit 11 sets settings related to remittances to user A (settings for receiving remittances, settings for remittances, etc.) for the talk room. The server 10 provides information (remittee, remittance source, remittance destination, remittance source, Remittance amount, remittance account, etc.). The control unit 11 executes processing related to remittance (remittance processing) based on the information related to remittance.

As a result, according to the information processing of the present embodiment, as an example and not a limitation, when executing remittance processing, there is no need for the server 10 to determine remittance-related settings for each user. can improve. In addition, users using the talk room can make remittance within the talk room, thereby improving user convenience.

According to the present embodiment, the settings related to remittance set by the control unit 11 include settings related to user A being the administrator of the talk room (person who created the talk room, etc.). As a result, according to the information processing of the present embodiment, as an example and not as a limitation, settings related to remittance are set for the administrator. can reduce the amount. Moreover, since the amount of information transmitted from the user terminal 20 to the server 10 can be reduced, the processing speed of the server 10 can be improved.

According to the present embodiment, the control unit 11 sets settings related to remittance based on the creation of the talk room by the user A. FIG. As a result, according to the information processing of the present embodiment, as a non-limiting example, when the chat room is created, settings related to remittance are set. Since the amount can be reduced, the processing speed of the server 10 can be improved.

According to the present embodiment, the setting related to remittance set by the control unit 11 enables remittance to the user A based on input to the input unit 22 of the user terminal 20 by the user who participates in the talk room. including settings related to As a result, according to the information processing of the present embodiment, as an example and not as a limitation, it is possible to set a user who can send money in the talk room, thereby improving the convenience of the talk room.

According to the present embodiment, the settings related to remittance set by the control unit 11 include settings related to prohibiting remittance from users participating in the talk room to user B who is a participant. As a result, according to the information processing of this embodiment, as an example and not as a limitation, by setting so that remittance can be made only to a specific user, the processing for specifying the remittance destination in the server 10 can be reduced. Therefore, the processing speed of the server 10 can be improved. In addition, since rules regarding remittance can be determined in the talk room, abuse of the talk room by the user can be prevented.

According to this embodiment, the server 10 stores the relationship between the user A and a user different from the user A in the storage unit 15 . User A and user B do not have at least one of 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 the present embodiment, as a non-limiting example, the users participating in the chat room can participate in the chat room even if there is no specific relationship between them. can be reduced, the processing speed of the server 10 can be improved. Moreover, since the user can participate in the talk room without considering the relationship with other users, the convenience of the talk room can be improved.

According to the present embodiment, the server 10 does not include display regarding setting of friend relationships, followed relationships, and following relationships in the image of the chat room. As a result, according to the present embodiment, as an example and not a limitation, a user participating in a talk room is not allowed to establish a predetermined relationship with another user, so the amount of processing and processing items in the server 10 can be reduced. Therefore, the processing speed of the server 10 can be improved.
=== Second Embodiment ===

An 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 talk room can set settings to receive remittances from other users. Hereinafter, as an example and not as a limitation, a setting for receiving money transfer in the talk room will be referred to as "remittance receipt setting". In addition, as a non-limiting example, in the present embodiment, a setting that allows remittance in a chat room (a non-limiting example, a remittance setting) is set so that a user who has set a remittance receipt setting can transfer the remittance setting to another user. can be set. In the following description, as an example and not as a limitation, it is assumed that the administrator who has the remittance receipt settings sets the remittance receipt settings for the participants. In this embodiment, the manager's user terminal 20, as an example and not a limitation, designates one of the participants to provide information on the setting of remittance receipt settings (receipt setting information as an example and not a limitation) or remittance At least one of the information regarding the setting of the settings (as an example and not by way of limitation, the remittance setting information) is sent to the server 10 . Based on this information, the server 10 sets at least one of remittance receipt setting and remittance setting to the user ID of any of the participants. Note that the content described in this embodiment can be applied to other embodiments as appropriate.

This embodiment will be described in detail with reference to FIGS. 9 to 12. FIG. 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 the talk room information D12. FIG. 12 is a diagram showing an example of an image T8 including content indicating completion of setting. In this embodiment, the same reference numerals are given to the same configurations as in the above-described embodiment, and the description thereof will be omitted or simplified. Note that FIG. 9 is a flowchart on the premise that the procedures from S111 to S141 in FIG. 2 have been completed. That is, it is assumed that the remittance receipt setting is set to the user ID of the manager (here, user A). A procedure for user A to set remittance receipt settings for user B's user ID via user terminal 20A will be described below.

First, in step S211, the user terminal 20A, as a non-limiting example, selects the icon PL when there is an input to the input unit 22 for the icon PL in the display area 28 shown in FIG. 2A(b). After determination, a selection image T6 including a remittance setting icon Tb as shown in FIG. 10A is displayed in the display area . Then, as an example and not as a limitation, the control unit 21 determines that the “receiving setting” is selected when the input unit 22 receives an input for the icon “receiving setting”. Then, as an example, not limitation, the control unit 21 refers to the talk room information D22 and causes the display area 28 to display the reception setting image T7 in FIG. 10B. The receipt setting image T7 in FIG. 10(b) includes, by way of example and not limitation, a remittance recipient setting portion T71 displaying the name of the user corresponding to the user ID associated with the talk room, and a setting confirming portion T72. . As a non-limiting example, the remittance recipient setting unit T71 may display the name of the user in a predetermined display format (as a non-limiting example, pull-down) when there is an input in the input unit 22. . The remittance beneficiary setting section T71 may be, for example and not limitation, a text box or the like that accepts input of the user's name. In addition, the remittance recipient setting section T71 may include, as an example and not a limitation, check boxes displayed corresponding to the respective names of a plurality of users. Here, for the user terminal 20A, as an example and not as a limitation, it is assumed that "user B" is set in the remittance recipient setting section T71. Then, as an example and not a limitation, the control unit 21 confirms the reception setting information when there is an input in the input unit 22 to the setting confirming portion T72 displayed in the display area 28 . Then, in step S212, the user terminal 20A transmits to the server 10 a reception setting request including the reception setting information.

Next, in step S<b>221 , the server 10 stores the reception setting request in the storage unit 15 . As an example and not a limitation, the server 10 collates the user ID of user A with the user ID of [remittance recipient ID] of the talk room information D12 shown in FIG. 3A based on the reception setting request. That is, as an example and not a limitation, the control unit 11 confirms that a reception setting request has been transmitted from the user terminal 20 of the user for whom the remittance reception setting is set. As a non-limiting example, if the user ID of user A matches the user ID of the [remittance recipient ID] as a result of collation, the control unit 11 updates the talk room information D12 (as a non-limiting example, receipt setting processing). Specifically, as an example and not a limitation, the control unit 11 compares the chat room information D12 shown in FIG. Register your user ID.

Next, in step S231, the server 10 transmits to each user terminal 20 a setting completion notification including the updated talk room information D12. Based on the setting completion notification, the user terminal 20A displays an image T8 including content Q4 indicating completion of setting as shown in FIG. As an example and not a limitation, the user terminal 20B and the user terminal 20C similarly display an image including the content Q4. Note that the server 10 may or may not transmit the setting completion notification to each user terminal 20 as an example and not as a limitation. Further, 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 receipt setting. In this case, the user terminal 20 that has received the setting completion notification may cause the display area 28 to display an image including a message indicating the setting completion.

In the above description, the control unit 11 registers the user B's user ID in the [remittance recipient ID] (receipt change processing) as in the chat room information D12 shown in FIG. Not limited. As a non-limiting example, the control unit 11 may set the user ID of the user B in addition to the user ID of the user A for whom the remittance receipt setting is set in the [remittance recipient ID]. . In this case, user A's user ID and user B's user ID are registered in [remittance recipient ID]. In this case, as an example and not a limitation, the user terminal 20A displays an image containing content indicating completion of setting (as an example, not a limitation, a new remittance receipt setting has been set for user B) based on the setting completion notification. It may or may not be displayed.

Also, in the above description, it was explained that the manager, who has the settings for receiving money transfer, sets the settings for receiving money transfer for the participants, but the present invention is not limited to this. As an example and not a limitation, the control unit 11 may execute such that the participant who has the remittance receipt setting sets the remittance receipt setting to another participant.
<Fourth modification>

Information processing according to the fourth modification will be described with reference to FIGS. 13 and 14 . FIG. 13 is a diagram showing an overview of information processing according to the fourth modification. FIG. 14 is a diagram showing an example of talk room information D12 according to the fourth modification. The information processing according to the fourth modification is a form in which a user participating in a talk room executes processing for canceling the remittance receipt setting of a user who has set the remittance receipt setting. Here, "to cancel the remittance receipt setting" means to delete the user ID from the [remittance recipient ID] in the talk room information D12 in the server 10, as an example and not a limitation. It means to make it impossible to do so. In the following, it is assumed that the remittance receipt setting is set to the user ID of the manager (here, user A), and user A cancels the remittance receipt setting set for himself via the user terminal 20A. Describe the procedure.

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

Next, the server 10 stores the receipt cancellation request in the storage unit 15 . As an example and not a limitation, the server 10 collates the user ID of user A with the user ID of [remittance recipient ID] in the talk room information D12 based on the receipt cancellation request. That is, as an example and not a limitation, the control unit 11 confirms that a receipt cancellation request has been transmitted from the user terminal 20 of the user for whom the remittance receipt setting is set. As a non-limiting example, if the user ID of user A matches the user ID of the [remittance recipient ID] as a result of collation, the control unit 11 updates the talk room information D12 (as a non-limiting example, receipt cancellation processing). Specifically, as an example and not a limitation, the control unit 11 compares the chat room information D12 shown in FIG. Deleted.

In the above description, the administrator cancels the remittance receipt setting, but the present invention is not limited to this. By way of example and not limitation, processing may be performed such that the participant cancels the remittance receipt setting. In this case, the server 10 cancels the remittance reception setting of the given user based on the reception cancellation request received from the participant's user terminal 20, as an example and not a limitation.

Next, the server 10 transmits to each user terminal 20 a release completion notification including the updated talk room information D2. Based on the cancellation completion notification, the user terminal 20A causes the display area 28 to display an image containing content indicating the completion of cancellation (as a non-limiting example, a message "The remittance receipt setting has been canceled from user A"). As an example and not a limitation, the user terminal 20B and the user terminal 20C similarly display an image including the above content.
<Fifth Modification>

Information processing according to the fifth modification will be described with reference to FIGS. 15 and 16 . FIG. 15 is a diagram showing an overview of information processing according to the fifth modification. FIG. 16 is a diagram showing an example of an image T13 containing content related to change receipt. The information processing according to the second modification is a process in which a certain user who has set a remittance receipt setting in a chat room changes his own remittance receipt setting to another user (as an example, not a limitation, a receipt change process). It is a form that executes Then, as an example and not limitation, the server 10 executes a process (value transfer process as an example, not a limitation) to transfer the value corresponding to the amount of remittance received by a certain user from one user to another user. . In the following, a procedure will be described in which user A, who has set a remittance receipt setting, causes user B to change his own remittance receipt setting via the user terminal 20A.

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

Next, the server 10 stores the setting change request in the storage unit 15 . As an example and not a limitation, the server 10 collates the user ID of user A who is the source of the change with the user ID of [remittance recipient ID] of the talk room information D12 based on the setting change request. As a non-limiting example, if the user ID of user A matches the user ID of the [remittance recipient ID] as a result of collation, the control unit 11 executes reception change processing to update the talk room information D12.

Next, the control unit 11 refers to the remittance history information D15 shown in FIG. 3D as an example and not a limitation, and refers to information related to the remittance associated with the user ID of the user A until the receipt change process is completed. identify. Specifically, as an example and not as 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 "1,000" for the user ID (here, user B) who sent money at 10:00, and "1,000" for the user ID (here, user C) who sent money at 11:00 on January 1, 2020. 000”. Then, the control unit 11 refers to the remittance account information D14, and applies the value indicating the specified remittance total to the value corresponding to the remittance account associated with the user ID set as the change destination. Therefore, value transfer processing is executed to update the remittance account information D31 of the payment server 30 corresponding to the remittance account.

Server 10 then receives updated remittance account information D31 from payment server 30, by way of example and not limitation. The server 10 transmits a setting change notification including the remittance account information D31 to the user terminal 20 by way of example and not limitation. Based on the setting change notification, the user terminal 20A sends content Q5 indicating completion of the setting change as shown in FIG. The display area 28 displays an image T13 including the content Q6 indicating the details of the remittance (as an example, not limitation, 2,000 yen was remitted to the user B). As an example and not a limitation, the user terminal 20B and the user terminal 20C similarly cause an image including the content Q5 and the content Q6 to be displayed in the display area 28 .

In the above description, when the receipt change process is completed, the value associated with the user ID of user A until the receipt change process is completed is applied to the value associated with the change destination user B. Although it has been described as executing transfer processing, it is not limited to this. As an example and not a limitation, the control unit 11 applies only the value corresponding to the remittance process to user A executed after the completion of the receipt change process to the value associated with the change destination user B. , a value transfer process that updates the remittance account information D31 of the payment server 30 may be executed.
=== Effect ===

According to this embodiment, the server 10 sets settings related to remittance to other users different from the user A based on the input by the user A to the input unit 22 of the user terminal 20A. As a result, according to the information processing of the present embodiment, as an example and not as a limitation, only a specific user (here, user A) is authorized to set settings related to remittance, so that information related to chat room management can be obtained. Since the processing can be reduced, the processing speed of the server 10 can be improved. In addition, since user A can set settings related to remittance to other users as necessary, the convenience of the talk room can be improved.

According to the present embodiment, the server 10 cancels the remittance settings set for the user A based on the input by the user A to the input unit 22 of the user terminal 20A. As a result, according to the information processing of the present embodiment, as a non-limiting example, only a specific user (here, user A) is given the authority to cancel the settings related to remittance, thereby Since the amount of information processing can be reduced, the processing speed of the server 10 can be improved. In addition, since the user A can cancel the settings related to remittance as necessary, it is possible to prevent unnecessary remittances, thereby improving the security of the talk room.

According to this embodiment, when the server 10 sets the settings related to remittance to another user different from user A, the amount already remitted from user B to user A is transferred from user A to the other user. Execute the remittance process. As a result, according to the information processing of the present embodiment, for example and not limitation, remittance from user A to another user can be performed without requiring a procedure for remittance from user A to another user at user terminal 20A. Since it is executed, the information processing amount of the user terminal 20 can be reduced, and accordingly, the information processing amount of the server 10 can also be reduced. In addition, since it is possible to reduce the number of procedures for user A to transfer money to other users, the convenience of the talk room can be improved.
=== Third Embodiment ===

An outline of this embodiment will be described. 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 the talk room, and if the participant satisfies a predetermined condition, the participant's request is accepted. It is a form of approving participation in the talk room. In the following description, as an example and not a limitation, it is assumed that the server 10 approves the participation of the participants (here, user B and user C) in the talk room. Note that the content described in this embodiment can be applied to other embodiments as appropriate.

This embodiment will be described in detail with reference to FIG. FIG. 17 is a flowchart showing information processing according to the third embodiment. In this embodiment, the same reference numerals are assigned to the same configurations as in the above-described embodiment, and the description thereof will be omitted or simplified. FIG. 17 is a flowchart on the premise that the procedures from S111 to S132 in FIG. 2 have been completed.

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

Next, in step S351, the user terminal 20B causes the display area 28 to display an approval confirmation screen T14 shown in FIG. 18 as an example and not a limitation. Approval confirmation image T14 includes, by way of example and not limitation, a user name input field T141 for receiving input of the user name of user B requesting participation in the talk room, and an approval request execution part T142. As a non-limiting example, the control unit 21 controls the user name input field T141 (as a non-limiting example, a text box) displayed in the display area 28, when there is an input in the input unit 22, The text data is displayed in the user name input field T141. Then, as an example, not a limitation, the control unit 21, when there is an input in the input unit 22, to the approval request execution unit T142 displayed in the display area 28, information related to approval (as an example, not a limitation, approval request information). Then, in step S352, the user terminal 20B transmits to the server 10 an approval request including the approval request information.

Next, at step 361 , the server 10 stores the approval request in the storage section 15 . Then, the server 10 collates the user name included in the approval request information with the “user name” of the personal identification information D17 shown in FIG. 19 (as an example, not as a limitation, approval processing).

Here, the personal identification information D17 will be explained. Personal identification information D17 is generated by an identity verification procedure, by way of example and not limitation. The personal identification procedure is, for example and not limitation, a procedure for registering the user's personal information in the server 10 before the user makes a remittance processing request. Specifically, as an example and not a limitation, the server 10 transmits an input request image to the user terminal 20 . The input request image is, by way of example and not limitation, an image for inputting bank account information or driver's license information (which may include an image or the like). The user terminal 20 receives an input to the input unit 22 in response to the input request image, registers information corresponding to each item in FIG. 19 as an example and not a limitation, and generates personal identification information D17. The user terminal 20 transmits the personal identification information D17 to the server 10 by way of example and not limitation. FIG. 19 is a diagram showing an example of personal identification information D17. Personal identification information D17 includes, by way of example and not limitation, [user ID], [user name], [password], [real name], [date of birth], [address], [phone number], and [email address] including the items of [User ID] is, by way of example and not limitation, identification information of a user included in a group corresponding to each talk room. [User Name] is, by way of example and not limitation, the name used in the messaging service that is associated with [User ID] and is 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 full name of the user associated with User ID. [Date of Birth] is, by way of example and not limitation, the date of birth of the user associated with the [User ID]. [Address] is, by way of example and not limitation, the address of the user associated with [User ID]. [Phone Number] is, by way of example and not limitation, the user's mobile or landline number, etc., associated with the [User ID]. [Email Address] is, by way of example and not limitation, the email address of the user associated with [User ID].

Next, in step 362, the server 10, as a non-limiting example, compares the user name included in the authorization request information with the "user name" of [user name] associated with the user ID of user B as a result of matching. match, the user ID of user B is registered 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 receives the content information D13 from the server 10, and receives the content as shown in FIG. 2A(b). An image T1 including Q1 may be displayed in the display area 28. FIG. 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 the user name input field 141, but the present invention is not limited to this. As an example and not a limitation, the approval confirmation image T14 is an image including an input field for inputting at least one of a user ID, password, real name, date of birth, address, telephone number, and email address instead of the user name input field T141. may be That is, in the present embodiment, the server 10 receives personally identifiable information from the user in the messaging service, and, if the information satisfies a predetermined condition, allows the user to participate in the chat room, as an example and not a limitation. approve.
<Sixth modification>

Information processing according to the sixth modification will be described with reference to FIG. FIG. 20 is a diagram showing an example of a remittance completion image T15. The information processing according to the sixth modification is such that when the remittance process is completed in the server 10, the server 10 transmits to the user who received the remittance information that can uniquely identify the user who made the remittance. be. Hereinafter, the user who received the remittance will be referred to as user A, and the user who made the remittance will be referred to as user B.

First, when the remittance process is completed in the server 10, the server 10 identifies the "real name" associated with the user B by referring to the personal identification information D17 generated by the identity verification procedure described above, for example and not limitation. do. The server 10 transmits a remittance completion image T15 including User B's "real name" to the user terminal 20A as an example and not a limitation. The user terminal 20A causes the display area 28 to display a remittance completion image T15 shown in FIG. The remittance completion image T15 is an image including, for example and not limitation, a user display portion T151 displaying the real name of User B, a remittance amount display portion T152 displaying the remittance amount, and a confirmation completion portion T153. . As a non-limiting example, the user terminal 20A determines that the confirmation completion section T153 has been selected when there is an input in the input section 22 for the icon of the confirmation completion section T153, and the remittance completion screen T15 is displayed in the display area. 28 is erased.

As an example and not a limitation, the server 10 may create a remittance completion image T151 that further includes a nickname to be used when participating in the talk room. In addition, as an example and not a limitation, the server 10 refers to the personal identification information D17 to identify the e-mail address associated with the user ID of the user A who received the remittance, and sends the transmission completion notification including the content to that e-mail address. You can send it to your email address.
=== Effect ===

According to the present embodiment, the server 10 receives information regarding approval of user B's participation in the talk room from the user terminal 20B. The server 10 performs processing for allowing user B to participate in the talk room based on the information regarding approval. As a result, according to the information processing of the present embodiment, as an example and not a limitation, the server 10 can ensure the safety of the talk room and improve the security by making the participation of the user in the talk room an approval system. .

According to the present embodiment, when the server 10 performs processing related to remittance from user B to user A, the server 10 includes name information in the identification procedure for user B and information related to completion of remittance from user B to user A. is transmitted to user A's user terminal 20A. As a result, according to the information processing of the present embodiment, as a non-limiting example, the user terminal 20A of the user A who received the remittance can receive the real name of the remitter and the notification indicating that the remittance has been completed. It can improve the convenience of the payment, and improve the safety of remittance in the talk room.
=== Fourth Embodiment ===

An outline of this embodiment will be described. In this embodiment, as an example and not a limitation, the server 10 deletes the "talk room ID" that satisfies a predetermined condition from the "talk room ID" of the talk room information D12. Here, the predetermined conditions are, for example, not limitation, that a predetermined time has passed since the date and time when the chat room was created, that a preset date and time has passed, and that the administrator has withdrawn from the chat room. and so on.

This embodiment will be described in detail with reference to FIGS. 21 and 22. FIG. 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 reference numerals are given to the same configurations as in the above-described embodiment, and the description thereof will be omitted or simplified. Note that FIG. 21 is a flowchart on the premise that the procedures from S111 to S151 in FIG. 2 have been completed. In the following description, as an example and not as a limitation, it is assumed that the manager (here, user A) for whom the remittance receipt setting is set sets a predetermined condition for deleting the talk room. As an example and not as a limitation, it is also possible for a participant to set a predetermined condition. Also, by way of example and not limitation, the server 10 may cause the talk room to be automatically deleted after a predetermined amount of time (eg, 24 hours) after the talk room was created. Also, as an example and not a limitation, the user (operator) of the server 10 may arbitrarily set the timing of deleting the talk room. Also, the content described in this embodiment can be applied to other embodiments as appropriate.

First, in step S451, the user terminal 20A, as a non-limiting example, selects the icon PL when there is an input to the input unit 22 for the icon PL in the display area 28 shown in FIG. 2A(b). The selection image T16 including the remittance setting icon Tb shown in FIG. 22(a) is displayed in the display area 28. Then, as an example, not limitation, the control unit 21 determines that the “disappearance condition” is selected when the input unit 22 receives an input for the icon “disappearance condition”. Then, as an example and not a limitation, the control unit 21 refers to the disappearance information D12 and causes the display area 28 to display the disappearance condition image T17 of FIG. 22(b). The disappearance condition image T17 includes, by way of example and not limitation, a disappearance item setting portion T171 for selectively displaying the item of the disappearance condition, a disappearance date setting portion T172 for setting the disappearance date, and a disappearance time. It includes an extinction time setting part T173 for and a condition completion part T174. As a non-limiting example, the control section 21 displays a disappearing item setting section T171 displayed in the display area 28 so that when there is an input in the input section 22, either "time" or "user" can be selected. do. As an example and not a limitation, when an input is made to the annihilation date setting portion T172 displayed in the display area 28, the control portion 21 sets the input text data to the annihilation date setting portion T172. to display. Then, as an example and not a limitation, when there is an input in the input unit 22 for the extinction time setting section T173 displayed in the display area 28, the control section 21 sets the input text data to the extinction time setting section T173. to display. Note that the annihilation date setting section T172 and the annihilation time setting section T173, as an example and not as a limitation, when there is an input in the input section 22, the date or You can display the time. The expiration date setting section T172 and the expiration time setting section T173 may be text boxes or the like for receiving input of date and time, for example and not limitation. Then, as an example and not a limitation, when there is an input in the input unit 22 to the condition completion part T174 displayed in the display area 28, the control unit 21 provides information about the disappearance condition (as an example, not a limitation, disappearance condition information). Then, in step S452, the user terminal 20A transmits the extinction condition information to the server 10. FIG.

Next, at step 461 , the server 10 stores the extinction condition information in the storage section 15 . The storage unit 15 stores the extinction condition information as extinction condition information D18 shown in FIG. FIG. 23 is a diagram showing an example of the extinction condition information D18. The extinction condition information D18 includes, by way of example and not limitation, items of [chat room ID], [date and time of creation], and [destruction condition]. [Talk Room ID] is, by way of example and not limitation, identification information for each talk room. [Creation Date] is, by way of example and not limitation, the date and time the talk room was created, which is associated with the [Talk Room ID]. [Disappearance condition] is, as an example and not a limitation, a disappearance condition included in the disappearance condition information associated with the [talk room ID]. Specifically, as an example and not a limitation, the talk room “tr01” is set to disappear at “10:00 on January 5, 2020”. As an example and not a limitation, the talk room “tr02” is set to disappear “20 hours later” from “10:00 on January 2, 2020”. As an example and not as a limitation, the talk room "tr03" is set such that the talk room disappears when user A, who is the administrator, withdraws from the talk room.

Next, at step 471, the control unit 11 of the server 10 determines whether or not the extinction condition is satisfied in each talk room. In step 481, the control unit 11 executes the extinction process when determining that the extinction condition is satisfied as an example and not a limitation. Deletion processing is, for example and not limitation, processing for deleting the talk room ID from the talk room information D12. Next, at step 482, the server 10 transmits talk room information D12 to the user terminal 20, by way of example and not limitation. Then, when the image TL of the list of talk rooms is displayed in the display area 28 on the user terminal 20, the icon of the talk room (here, "coffee party") whose talk room ID has been deleted is displayed on the image TL. may be displayed. In this case, as a non-limiting example, a message indicating that the service is not available, such as "Closed", may be displayed together with the icon "Coffee party". Furthermore, as an example and not as a limitation, the user terminal 20 determines that "Coffee party" has been selected when there is an input in the input unit 22 for the "Coffee party" icon. The user terminal 20 then refers to the talk room information D22 as a non-limiting example and determines that there is no talk room ID corresponding to "coffee party". As an example and not a limitation, the control unit 21 may generate a message indicating that the “Coffee party” talk room is not available, and cause the display area 28 to display the message.
=== Effect ===

According to this embodiment, the server 10 deletes the talk room based on the elapse of the set period or the set time. As a result, according to the information processing of the present embodiment, the amount of information processing at the user terminal 20 can be reduced as an example and not as a limitation. In addition, according to the information processing of the present embodiment, as an example and not as a limitation, it is possible to eliminate the burden of operations related to deleting a talk room by the user, thereby improving convenience for the user.
=== Fifth Embodiment ===

An outline of this embodiment will be described. This embodiment is an example, not a limitation, in which the server 10 allows a user participating in a talk room to report on another user. In other words, the participant of the chat room informs the server 10 about the remittance recipient based on the information about the remittance recipient, and the server 10 changes the remittance setting of the remittance recipient. Here, the settings related to remittance include, as an example and not limitation, setting the user IDs of the manager and participants described above in the items of [Remittance Recipient ID] or [Sender ID], Settings that temporarily prohibit money transfers in chat rooms, settings that permanently prohibit money transfers in chat rooms, settings that temporarily prohibit money transfers in message services, and money transfers in message services may be a setting such as a setting that permanently prohibits the Hereinafter, as a non-limiting example, the information about the report is referred to as "report information", the remittance recipient is User A, and the participant who transmits the report information about User A to the server 10 is User B. The content described in this embodiment can be applied to other embodiments as appropriate.

This embodiment will be described in detail with reference to FIGS. 24 and 25. FIG. 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 reference numerals are given to the same configurations as in the above-described embodiment, and the description thereof will be omitted or simplified. Note that FIG. 24 is a flowchart on the premise that the procedures from S111 to S151 in FIG. 2 have been completed. A procedure for user B to report user A's actions in the talk room via user terminal 20B will be described below.

First, in step S551, the user terminal 20B, as a non-limiting example, selects the icon PL when the input unit 22 receives an input for the icon PL in the display area 28 shown in FIG. 2A(c). After determination, a selection image T18 including a remittance setting icon Tb as shown in FIG. 25A is displayed in the display area . As a non-limiting example, the control unit 21 determines that "report" is selected when the input unit 22 receives an input for the icon "report". 25(b) is displayed in the display area 28 by referring to the talk room information D22 as an example and not as a limitation. The report setting image T19 in FIG. 25(b) includes, as an example and not limitation, a target person display portion T191, a report reason display portion T192, and a report determination portion T193. The target display section T191 displays the name of the user corresponding to the user ID set in [Remittance Recipient ID] as an example and not as a limitation. As an example and not a limitation, the target display section T191 displays the names of a plurality of users in a predetermined display format (as an example, not as a limitation, pull-down) when a plurality of remittance recipients are set in the talk room. good too. In addition, as an example and not as a limitation, when a plurality of remittance recipients are set in a talk room, the control unit 21 selects two or more of the names of a plurality of users by selecting check boxes corresponding to each user. etc. may be displayed in the display area 28 . As a non-limiting example, the reporting reason display section T192 may display the reporting reason in a predetermined display format (as a non-limiting example, pull-down) when there is an input in the input section 22. The report reason display part T192 may be a text box or the like for receiving the input of the content of the report as an example and not as a limitation. As an example and not a limitation, when it is determined that the icon of the reporting reason display section T192 has been selected, the control section 21 displays a list showing candidates for reporting reasons in the display area 28 as shown in FIG. 25(b). do. Then, when there is an input in 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 an example and not as a limitation, when there is an input in the input section 22, the control section 21 confirms the report information with respect to the report confirmation section T193 displayed in the display area 28. FIG. Then, in step S552, the user terminal 20A transmits to the server 10 a reception setting request including reception setting information.

Next, in step S561, the server 10 stores the report information in the storage unit 15. FIG. As an example and not a limitation, the server 10 collates the user ID of user B with the user ID of [user ID] in the talk room information D12 shown in FIG. 3A based on the report information. That is, as an example and not a limitation, the control unit 11 confirms that the report information has been transmitted from the user terminal 20 of the user participating in the talk room. The server 10 performs limit setting processing as an example and not as a limitation. The restriction setting process is, as an example, not a limitation, a process of setting restrictions on the user ID of the person to be notified (here, user A) based on the notification information. Further, the restriction setting process may be a process of setting a restriction on the user ID of the user A by determining whether or not a predetermined condition is satisfied, as an example rather than a limitation. Here, the predetermined conditions are, for example, not limitation, that the number of reports 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, etc. is. As an example and not a limitation, the server 10 imposes restrictions on the user ID of user A, such as first restriction information D19A shown in FIG. Note that the server 10 may limit the user ID for each talk room ID as an example, not as a limitation. In addition, as an example and not a limitation, the server 10 deletes the user ID of user A from the item of [remittance recipient ID] in the talk room information D12, thereby preventing user A from receiving remittances in the talk room. Restrictions may be given. Further, as an example and not a limitation, the server 10 may cause user A to withdraw from the talk room by deleting the user ID of user A from the talk room information D12. In this case, the server 10 refers to the remittance history information D15 as a non-limiting example, and refers to the user who sent money to the remittance setter (here, user A) in the past. You may perform the value transfer process mentioned above like this.

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

In the above description, the settings related to the remittance are set for the remittance recipient, but as an example and not as a limitation, the server 10, based on the report information, sets the remittance-enabled user (sender) You can also set up settings for remittances. The limit setting process in S561 in this case will be described below. As an example and not as a limitation, the server 10 sets restrictions on the user IDs of the participants in the talk room (here, user B and user C) based on the report information. In this case, the target display section T191 displays the name of the user corresponding to the user ID set in [User ID] as an example and not as a limitation. That is, the target display section T191 may display all users participating in the talk room as an example and not as a limitation. The report reason display section T192 and the report confirmation section T193 are the same as those described above, so descriptions thereof will be omitted. Then, as an example and not a limitation, the server 10 instructs the user IDs of the notified users (here, user B and user C) to make the remittance, as in the second restriction information D19B shown in FIG. Giving restrictions to prohibit (disable). As an example and not a limitation, the server 10 restricts the reported user from remittance by deleting the reported user's user ID from the [remitter ID] of the chat room information D12. You may

In addition, in the above, we decided to set the settings related to money transfers (here, settings such as temporarily prohibiting money transfers and money transfers in the chat room) for the money transfer recipient or the sender. Not limited. By way of example and not limitation, the server 10 may restrict the notified money transfer recipient or sender to at least temporarily suspend the user ID used in the messaging service. In this case, by way of example and not limitation, the server 10 restricts all actions of the restricted user using the messaging service, such as receiving money, sending money, and sending and receiving content.
=== Effect ===

According to the present embodiment, the server 10 receives notification information about user A (administrator) from user B, and based on the information about user A (administrator), sets the settings for remittance to user A as predetermined. change to As a result, according to the information processing of the present embodiment, as an example and not a limitation, the server 10 can change settings related to remittance in the chat room based on information acquired from the user terminal 20 of the user. It can improve safety.

According to this embodiment, the server 10 receives report information about user A (administrator) from user B, and based on the information about user A (administrator), the You can change the settings. As a result, according to the information processing of the present embodiment, as an example and not as a limitation, the setting is changed so that the user A cannot receive remittance in the chat room based on the information acquired from the user's user terminal 20. Therefore, it is possible to prevent the user A from committing fraudulent acts in the talk room, thereby improving the safety of the talk room.

According to this embodiment, the server 10 receives report information about user A (administrator) from user B, and based on the information about user A (administrator), suspends user A's account at least temporarily. You may As a result, according to the information processing of the present embodiment, as an example and not a limitation, it is possible to stop the action related to remittance by user A in the chat room based on the information acquired from the user terminal 20 of the user. Since it is possible to prevent A from committing fraudulent acts, the safety of the talk room is improved.
===Sixth Embodiment===

An outline of this embodiment will be described. In this embodiment, as an example and not as a limitation, in the server 10, the user who received the remittance can refund the remittance to the user who sent the remittance. In other words, by way of example and not limitation, the custodian (as an example, but not limitation, a remittance recipient, etc.) that received the money transfer can refund the participant who sent the money to the custodian. Hereinafter, the refund processing in the server 10 will be referred to as "refund processing". Here, as a non-limiting example, the refund process transfers the value corresponding to the refund amount from the value corresponding to the refund source remittance account ID to the value corresponding to the refund destination remittance account ID. This is the process of updating the information of the payment server 30 corresponding to the account. The content described in this embodiment can be applied to other embodiments as appropriate.

This embodiment will be described in detail with reference to FIGS. 28 and 29. FIG. 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 reference numerals are given to the same configurations as in the above-described embodiment, and the description thereof will be omitted or simplified. Note that FIG. 28 is a flowchart on the premise that the procedures from S111 to S151 in FIG. 2 have been completed. Hereinafter, as an example and not as a limitation, it is assumed that user A is the user who refunds, and user B and user C are the users who receive the refund in the talk room.

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

Next, in step S661, the server 10 stores the refund request in the storage unit 15. FIG. As an example and not a limitation, the server 10 collates the user ID of user A with the user ID of [remittance recipient ID] of the talk room information D12 based on the refund request. That is, as an example and not as a limitation, the control unit 11 confirms that a refund request has been sent from the remittance recipient's user terminal 20 . As a non-limiting example, if the user ID of user A matches the user ID of the [remittance recipient ID] as a result of collation, the control unit 11 executes refund processing. As a non-limiting example of the refund processing, first, based on the refund information, the control unit 11 determines the refund source user ID (here, user A) and the refund destination user ID (here, user B and user C) is specified. Next, the control unit 11 identifies the remittance account used in the remittance process based on the remittance history information D15 as an example and not a limitation. It should be noted that information regarding the remittance account used in the remittance process may be included in the refund information as an example and not as a limitation. The control unit 11 converts 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), A process of updating the remittance account information D31 of the payment server 30 corresponding to the remittance account (here, remittance account A) is executed so as to transfer the value indicating the refund amount.

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

Information processing according to the seventh modification will be described with reference to FIG. FIG. 30 is a diagram showing an overview of information processing according to the seventh modification. The information processing according to the seventh modification is, as an example and not a limitation, a form in which the remittance recipient remits money to the remitter based on the votes of the users who desire the refund. Note that in the seventh modification, it is assumed that the procedures from S111 to S151 in FIG. 2 have been completed. Hereinafter, by way of example and not limitation, the remitter is user B and user C, the remittance recipient is user A, and the refund is made from user A to user B and user C based on the results of voting by user B and user C. Describe the procedure.

First, as a non-limiting example, the user terminal 20B determines that the icon PL is selected when there is an input in the input unit 22 for the icon PL in the display area 28 shown in FIG. 2A(c), A selection image T22 including a remittance setting icon Tb as shown in FIG. 30(a) is displayed in the display area . Then, as an example and not as a limitation, the control unit 21 determines that the “refund vote” is selected when there is an input in the input unit 22 for the icon “refund vote”. Then, as an example and not a limitation, the control unit 21 refers to the remittance history information D15 and extracts remittance histories made before the current time. As an example and not a limitation, the control unit 21 causes the display area 28 to display the refund vote image T23 of FIG. 30(b) based on the extracted remittance history. The refund vote image T23 includes, by way of example and not limitation, a refunder display portion T231, a refund amount display portion T232, and a voting completion portion T233. The refunder display section T231 displays the name of the user corresponding to the user ID set in [Remittance Recipient ID] as an example and not a limitation. In addition, as an example and not as a limitation, the refunder display section T231 displays a plurality of users' name may be displayed. In addition, as an example and not as a limitation, if there are multiple user IDs set in the [remittance recipient ID], the control unit 21 can select two or more user names from among multiple user names, corresponding to each user. You may display the check box etc. which carry out in the display area 28. FIG. The refund amount display section T232 may be, for example and not limitation, a text box or the like that accepts input of the refund amount. As an example and not as a limitation, the voting completion section T213 determines the above-mentioned information regarding voting (as an example, not as a limitation, voting information) when there is an input to the input section 22 in response thereto. The user terminals 20B and 20C then transmit voting requests including voting information to the server 10 .

The server 10 then stores the voting request in the storage unit 15 . By way of example and not limitation, the server 10 matches the user IDs of users B and C with the user IDs of [user ID] in the talk room information D12 shown in FIG. 3A based on the voting information. That is, as an example and not a limitation, the control unit 11 confirms that voting information has been transmitted from the user terminals 20 of the users participating in the talk room. By way of example and not limitation, the server 10 performs vote refund processing based on the vote information. As an example and not a limitation, the vote refund process is a process of refunding the refund to the user who sent the vote request by determining whether or not a predetermined condition is satisfied based on the vote information. Here, the predetermined condition is, as an example and not a limitation, based on the information about the refunder included in the voting information, the total number of pieces of information indicating the refunder exceeds a predetermined threshold, and the information indicating the refunder number exceeds a predetermined ratio with respect to the number of users participating in the talk room. As an example and not as a limitation, if the control unit 11 determines that a predetermined condition is satisfied, the control unit 11 executes the above-described value transfer processing so that the refunder refunds the money to the voter.

Next, the server 10 transmits to each user terminal 20 a refund completion notification including information regarding the result of executing the value transfer process, as an example and not a limitation. As an example and not a limitation, the user terminal 20 displays an image containing content related to the refund (for example, "1,000 yen has been refunded from User A to User B and User C by voting") based on the refund completion notification. display.
=== Effect ===

According to this embodiment, the server 10 receives refund information about refunding to user A the amount remitted from user B (participant) to user A (administrator), and based on the refund information, Execute processing related to remittance of the amount remitted from user A to user B. As a result, according to the information processing of the present embodiment, for example and not limitation, the server 10 can refund the remitted amount to the user who sent the remittance. Since the remittance procedure associated with the transaction can be executed quickly, the user's convenience can be improved, and the safety of the talk room can be improved.
=== Seventh Embodiment ===

An outline of this embodiment will be described. In this embodiment, as an example and not a limitation, the server 10 can execute a remittance request from the remittance recipient to the remitter, and display whether or not the user has executed the remittance in response to the remittance request. It is a form in which it is possible to In the following, as an example and not a limitation, the remittance recipient is user A, the remitter is user B and user C, and user A requests user B and user C for remittance. The content described in this embodiment can be applied to other embodiments as appropriate.

This embodiment will be described in detail with reference to FIGS. 31 to 33. FIG. 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 reference numerals are given to the same configurations as in the above-described embodiment, and the description thereof will be omitted or simplified. Note that FIG. 31 is a flowchart on the premise that the procedures from S111 to S151 in FIG. 2 have been completed. A procedure for a remittance recipient (here, user A) to request a remittance to senders (here, users B and C) will be described below.

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

Next, in step S<b>761 , the server 10 stores the remittance request request in the storage unit 15 . As an example and not a limitation, the server 10 collates 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. In other words, the control unit 11 confirms that a remittance request request has been transmitted from the remittance recipient's user terminal 20 as an example and not as a limitation. As a non-limiting example, if the user ID of user A matches the user ID of the [remittance recipient ID] as a result of collation, the control unit 11 executes the request display process. In the request display process, as an example and not a limitation, first, the control unit 11 specifies a user for whom a remittance is requested based on the remittance request information. Next, as a non-limiting example, based on the remittance history information D10, the control unit 11 generates a remittance list T261 shown in FIG. 33(a) that can determine whether the specified user has remitted or not remitted. . As an example and not a limitation, the control unit 11 generates a remittance request image T26 including a remittance list T261. Note that the control unit 11 may generate the remittance list T241 so as to include, as an example and not a limitation, at least a display capable of identifying at least one of users who have completed remittance and users who have not performed remittance.

Next, at step 762 , the server 10 transmits to the user terminal 20 a remittance request image T<b>26 including the remittance list T<b>241 as an example and not limitation. Next, the user terminal 20 causes the display area 28 to display a remittance request image T26 shown in FIG. 33(a). Note that the server 10 may transmit the remittance request image T26 only to the user terminal 20 of the remittance recipient (here, user A) as an example and not a limitation. In this case, only the user terminal 20A causes the display area 28 to display the remittance request image T26 shown in FIG. 33(a). The remittance request image T26 includes, by way of example and not limitation, a remittance list T261 and content Q8 relating to User A's remittance request. In FIG. 33(a), as a non-limiting example, user B and user C have not yet remitted money to user A. Therefore, the "remitted" column of the remittance list T261 is shown blank, indicating "unremitted". An indication “B” indicating user B and an indication “C” indicating user C are displayed in the columns.

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 determines user B who has completed remittance. A remittance request image T27 including a remittance list T271 shown in b) and content Q9 indicating that user B has completed remittance in response to user A's remittance request is generated. As an example and not a limitation, the control unit 11 detects that the user B has input the content Q8 including the URL and the icon Q81 for causing the server 10 to execute the remittance process in the input unit 22 of the user terminal 20B. In that case, you may proceed to remittance processing. In this case, as a non-limiting example, when the remittance process is completed, the control unit 11 displays the content Q9 indicating that the remittance has been made in response to the user A's remittance request. remittance) is generated.

Next, in step 792 , the server 10 transmits a remittance request image T<b>27 to the user terminal 20 by way of example and not limitation. Note that the server 10 may transmit the remittance request image T27 only to the user terminal 20 of the remittance recipient (here, user A) as an example and not a limitation. In addition, as an example and not limitation, the server 10 generates a remittance request image T27 including a remittance list T271 displaying only the remittance status of the user who made the remittance, and sends the remittance request to the user terminal 20 of the user who made the remittance. Image T27 may be transmitted. In this case, as an example and not a limitation, when the server 10 transmits the remittance request image T27 to the user terminal 20 of the remittance user B, the remittance list T271 in FIG. The display "B" shown is displayed, the "non-remittance" column is left blank, and a remittance request image T27 is generated. Next, the user terminal 20 causes the display area 28 to display a remittance request image T27 shown in FIG. 33(b) as an example, not limitation.
<Eighth modification>

Information processing according to the eighth modification 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 modification is, as an example and not a limitation, in the form of emphasizing the display indicating the user in the talk room according to the status of non-remittance or remittance. In addition, in the eighth modified example, it is assumed that the procedures up to S781 in FIG. 31 have been completed. Hereinafter, as a non-limiting example, the remittance recipient is User A, the remitter is User B and User C, the user who has already sent money is User B, and the user who has not yet sent money is User C. The content described in this embodiment can be applied to other embodiments as appropriate.

As an example and not a limitation, the server 10 generates a remittance request image T28 by attaching a highlighting T282 shown in FIG. As an example and not a limitation, the server 10 may generate the remittance list image T28 by attaching a highlighting T282 that enables identification of the remitted user B to the user B's icon Ub1. Also, as an example and not a limitation, the server 10 may generate the remittance request image T28 by adding the highlighting T282 to the user name of the user (here, the code Ub2 or the code Uc2) or the content. Here, the highlighting T282 is, for example and not limitation, a blinking display or a lit display surrounding the user C's icon Uc1. In addition, the highlighting T282 may be a flashing display or a lighting display surrounding the user name Uc2 of the user C, for example and not limitation. Furthermore, the highlighting T282 may be, for example and not limitation, a blinking display or lighting display surrounding the content Q10 of the user C, or a display in which the color scheme of the content Q10 is different from that of the content Q9. In FIG. 34, as an example and not a limitation, the remittance list T281 is displayed to be included, but the remittance list T261 may or may not be included in the remittance request image T28.

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

Information processing according to the ninth modification will be described with reference to FIG. 35 . FIG. 35 is a diagram showing an overview of information processing according to the ninth modification. The information processing according to the ninth modification is, as an example and not a limitation, a mode in which the server 10 rejects a withdrawal request from a talk room by a user who has not yet remitted money. Here, "withdrawal" means that the server 10 cancels the relationship between the talk room ID and the user ID in the talk room information D12, as an example and not a limitation. 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 send money to other users, and cannot send money from other users. will not be able to receive Hereinafter, in the ninth modification, it is assumed that the procedures up to S762 in FIG. 31 have been completed. Also, as a non-limiting example, the remittance recipient is user A, the remitter is user B and user C, user B is a user who has already sent money, user C is a user who has not yet sent money, and user C is a user of user C. It is assumed that the terminal 20C has transmitted a withdrawal request to the server 10. FIG. The content described in this embodiment can be applied to other embodiments as appropriate.

First, as a non-limiting example, the user terminal 20C determines that the icon PL is selected when there is an input in the input unit 22 for the icon PL in the display area 28 shown in FIG. 2A(c), A selection image T26 including a remittance setting icon Tb as shown in FIG. 35(a) is displayed in the display area . As an example and not a limitation, the control unit 21 determines that "withdrawal" is selected when there is an input in the input unit 22 for the icon "withdrawal". The user terminal 20C, as a non-limiting example, transmits to the server 10 information about withdrawal (as a non-limiting example, withdrawal information). Next, the server 10 stores withdrawal information in the storage unit 15 as an example and not as a limitation. As an example and not a limitation, the server 10 refers to the remittance history information D15 and determines whether user C has not remitted money based on the withdrawal information. As an example and not a limitation, when it is determined that user C has not yet 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 a withdrawal refusal image T30 to the user terminal 20C as an example and not as a limitation. Next, the user terminal 20C causes the display area 28 to display a withdrawal denial image T30 shown in FIG. 35(b) as an example and not a limitation. As described above, the server 10 is not limited to generating the withdrawal refusal image T30, and the user terminal 20C generates the withdrawal refusal image T30 based on the remittance history information D25 as an example, not as a limitation. A rejection image T30 may be displayed in the display area 28. FIG.
<Tenth Modification>

Information processing according to the tenth modification will be described with reference to FIG. 36 . FIG. 36 is a diagram showing an example of a remittance request image T31. In the information processing according to the tenth modification, after the receipt change processing in the second embodiment, a user whose remittance receipt setting has been changed (here, user B) to a user who has not yet remitted money (here, user C) In this form, when a remittance request is made to the remittance request, the remittance is executed to the user whose settings have been changed. Hereinafter, the user terminal 20A of the user who has changed the settings for receiving remittance (here, user A) issues a remittance request to the user terminal 20C of user C, and then the user whose settings for receiving remittance have been changed (here, user It is assumed that user B's user terminal 20B requests user C's user terminal 20C for remittance.

The server 10 transmits a remittance request image T31 to the user terminal 20C as an example and not a limitation. Next, the user terminal 20C causes the display area 28 to display a remittance request image T31 shown in FIG. Here, the remittance request image T26 includes, by way of example and not limitation, content Q8 related to user A's remittance request and content Q10 related to user B's remittance request. The content Q8 includes, by way of example and not limitation, the URL and icon Q81 for the user terminal C to cause the server 10 to execute the remittance process, by way of example and not limitation. Also, the content Q10 includes, as an example and not a limitation, a URL and an icon Q101 for causing the server 10 to execute remittance processing. As a non-limiting example, if there is an input in the input unit 22 for the icon Q81, the user terminal 20C determines that the icon Q81 has been selected, and requests the server 10 for remittance processing (as a non-limiting example, (including information about where to send money, where to send money, amount to send money, account for money transfer, etc.). In this case, the server 11 refers to the talk room information D12 as a non-limiting example, and performs the remittance process so that the remittance is made to the remittance recipient (here, user B) after the remittance receipt setting is changed. Run. Further, as an example and not a limitation, the user terminal 20C determines that the icon Q101 has been selected when there is an input to the input unit 22 for the icon Q101, and requests the server 10 to process remittance (example, not a limitation). , including information about the remittance destination, remittance source, remittance amount, remittance account, etc.). In this case as well, the server 11 refers to the talk room information D12 as an example and not a limitation, so that the remittance will be made to the remittance recipient (here, user B) after changing the remittance reception settings. Execute the process. That is, after the remittance reception setting is changed, if there is an input in the input unit 22 in response to the remittance request displayed in the talk room, the remittance is sent to the remittance recipient after the remittance reception setting is changed. remittance processing is executed.
=== Effect ===

According to this embodiment, the server 10, when the user B makes a remittance in response to the transmission request sent from the user A to the user B, sends information indicating that the remittance has been made in response to the remittance request. include. As a result, according to the information processing of the present embodiment, as an example and not a limitation, the server 10 can display the user who has sent money to the user in the talk room, thereby improving the user's convenience regarding money transfer. .

According to this embodiment, if the user B has not sent money in response to the transmission request sent from the user A to the user B, the server 10 informs the chat room that the payment has not been made in response to the remittance request. Include information that indicates As a result, according to the information processing of the present embodiment, as a non-limiting example, a user who has not remitted money to the user can be displayed in the talk room, so that the user's convenience regarding remittance can be improved.

According to this embodiment, the server 10 sends to the chat room, in response to the transmission request sent from user A to user B, information indicating that user B has made remittance and information indicating that remittance has not been made. , is displayed only in the talk room displayed in the display area 28 of the user A's user terminal 20A. As a result, according to the information processing of the present embodiment, as a non-limiting example, only the talk room displayed in the display area 28 of the user terminal 20A of the user A, who is the administrator, is the user who sent money and the user who did not send money. Since information that the user can understand is displayed, the amount of information processing of the server 10 can be reduced. Also, by way of example and not limitation, the server 10 can provide a talk room that does not offend users who have not sent money.

In this embodiment, the input to the input unit 22 by the user B for the talk room displayed in the display area 28 of the user terminal 20B is an input for the display regarding the remittance request from the user A to the user B displayed in the talk room. is. Then, the server 10 transmits to the input unit 22 by the user B the display regarding 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 the user C to the user terminal 20B. and the settings made by user A regarding remittances to other users different from user A. The server 10 executes processing related to the remittance from the user B to the user C based on the information related to the remittance from the user B to the user C. As a result, according to the information processing of the present embodiment, as an example and not as a limitation, a remittance request can be executed even if the remittance recipient is changed, thereby improving convenience for the user.
=== Eighth Embodiment ===

An outline of this embodiment will be described. In this embodiment, as an example and not a limitation, the server 10 allows other users to purchase images (for example, photographs) posted by a predetermined user in a talk room. In this embodiment, the server 10 receives photographic data from the user terminal 20 of a predetermined user, and transmits the received photographic data to each user terminal 20 at a low resolution. Hereinafter, as an 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 content described in this embodiment can be applied to other embodiments as appropriate.

This embodiment will be described in detail with reference to FIGS. 37 and 38. FIG. 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 reference numerals are given to the same configurations as in the above-described embodiment, and the description thereof will be omitted or simplified. Note that FIG. 37 is a flowchart on the premise that the procedures from S111 to S151 in FIG. 2 have been completed. A procedure for a user (here, user C) who purchases photo data uploaded by a predetermined user (here, user B) to remit money to a remittance recipient (here, user A) will be described below.

First, in step S861, the user terminal 20B generates photo data of the first resolution based on the input to the input unit 22 by the user B, 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 S<b>871 , the server 10 stores the photo data of the first resolution in the storage unit 15 as an example and not a limitation. By way of example and not limitation, the server 10 generates second resolution photo data representing a lower resolution than the first resolution based on the first resolution photo data. The server 10 generates a photograph publication image T31 including photograph data of the second resolution shown in FIG. 38(a) as an example and not limitation (here, publication processing). Next, in step S<b>872 , the server 10 transmits the photograph posted image T<b>31 to the user terminal 20 as an example and not a limitation.

Next, in step S881, the user terminal 20C causes the display area 28 to display a photograph posted image T32 as shown in FIG. 38(a) as an example and not a limitation. As a non-limiting example, the user terminal 20C determines that the purchase transition section T321 has been selected when there is an input in the input section 22 for the icon of the purchase transition section T321 included in the photo posting image T32, A photo purchase image T33 is displayed in the display area 28. FIG. The photo purchase image T33 includes, by way of example and not limitation, a photo selection portion T331, an amount display portion T332, a remittance destination T333, a remittance account setting portion T334, and a purchase confirmation portion T335. The photo selection portion T331 is, for example and not limitation, a region in which photo data of the second resolution is displayed in a selectable manner. The photo selection portion T331 includes, by way of example and not limitation, a selection display icon T3311. As a non-limiting example, when the input unit 22 receives an input 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, assign numbers to change colors). The amount display part T332 is an area in which the purchase amount of the photo data is displayed as an example and not as a limitation. As an example and not a limitation, the control unit 11 calculates the purchase price of the photo data corresponding to the selected selection display icon T3311 and displays the purchase price on the price display unit T332. The remittance destination T333 is an area for displaying the remittance destination specified by referring to the talk room information D22 as an example and not limitation. As an example and not a limitation, the remittance account setting unit T334 sets a remittance account corresponding to a remittance account ID that can be used in a predetermined display format (as an example, not as a limitation, pull-down) when there is an input in the input unit 22. This is an area for displaying the name of the account. As an example and not as a limitation, the control unit 11 confirms information regarding the photo data to be purchased and the purchase price (purchase information as an example, not as a limitation) when there is an input in the input unit 22 to the purchase confirmation unit T335. . Then, in step S882, the user terminal 20C transmits a purchase request including purchase information to the server 10. FIG.

Next, in step S891, the server 10 stores the purchase request in the storage unit 15. FIG. As an example and not a limitation, the server 10 collates 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, as an example and not a limitation, the control unit 11 confirms that a purchase request has been sent from the user terminal 20 of the user participating in the talk room. As a non-limiting example, when the user ID of user C matches the user ID of [user ID] as a result of collation, the control unit 11 proceeds to remittance processing. Server 10 performs the remittance process based on the purchase information, by way of example and not limitation. As an example and not a limitation, the control unit 11 identifies the user IDs of the remittance source and the remittance destination, the remittance account, and the purchase amount (remittance amount) based on the purchase information. Server 10 sends, by way of example and not limitation, a remittance advice to payment server 30 that includes information regarding source and destination user IDs, remittance accounts, and purchase amounts. 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 remittance source to the value of the remittance account corresponding to the user ID of the remittee. The payment server 30, by way of example and not limitation, transmits information to the server 10 regarding the outcome of the transaction regarding the money transfer. This completes the remittance process. Next, in S892, the server 10 acquires photo data of the first resolution from the storage unit 15 based on the purchase information. Then, the control unit 11 transmits the photo data of the first resolution to the user terminal 20 of the user C. FIG. Next, in S893, the server 10 transmits to the user terminal 20 a remittance completion notification including information on the purchase amount. Based on the remittance completion notification, the user terminal 20A displays an image containing content indicating completion of remittance (as an example, not limitation, 2,000 yen for the photo purchase price has been remitted).

In the above description, as an example and not a limitation, the server 10 is configured to prevent content sent and received by users participating in the talk room from being displayed on the user device 20 of the user who uploads photo data to the server 10. You may send an image of the talk room. Specifically, as an example and not a limitation, the server 10 refers to the content information D13 to identify content corresponding to a user other than the user B, excludes the identified content, 20 to generate a photographed image T32.
=== Effect ===

According to this embodiment, the server 10 can post low-resolution photo data in the talk 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 the present embodiment, as an example and not a limitation, the server 10 can compress the amount of data to be transmitted and received in order to post low-resolution photo data, thereby improving the processing speed. In addition, since the user can purchase photos in the talk room, user convenience can be improved.

B1, B2, B3... bus, N... network, 1... communication system, 10... server, 20... user terminal, 30... payment server, 11, 21, 31... - Control part, 12,22,32... Input part, 13,23,33... Output part, 14,24,34... Communication I/F, 15,25,35... Storage part.

Claims (24)

sending first content input by the first user to the 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 the second user; to the second terminal of the server, and transmits to the first terminal the second content input by the second user to the second terminal where the chat room is displayed and transmitted from the second terminal A program that
a control unit of the server to set, for the chat room, a first setting relating to a setting enabling remittance to the first user included in the chat room ;
A communication unit of the server receives information regarding remittance from the second user to the first user based on the first setting and the second user's input to the chat room displayed on the second terminal. and
The server executes a process related to remittance from the second user to the first user by the control unit based on the information related to remittance from the second user to the first user. The program according to claim 1,
The first setting includes setting regarding that the first user is an administrator of the chat room. The program according to claim 1 or claim 2,
The first setting is set based on creation of the chat room by the first user. The program according to any one of claims 1 to 3,
The first settings include settings related to enabling users included in the chat room to send money to the first user based on inputs to the chat room. The program according to any one of claims 1 to 4,
The first setting includes a setting regarding the inability to transfer money from users included in the chat room to the second user. The program according to any one of claims 1 to 5,
Storing a relationship between the first user and a user different from the first user by a storage unit of the server is performed by the server,
The first user and the second user do not have the relationship. The program according to claim 6,
The relationship is at least one of a friendship relationship between the first user and the different user, a relationship in which the first user is followed by the different user, and a relationship in which the first user follows the different user. including one. The program according to claim 7,
The chat room does not include an indication of the friend relationships, the followed relationships, and the following relationships settings. The program according to any one of claims 1 to 8,
Based on a first input by the first user to the chat room displayed on the first terminal, a second setting regarding remittance to a third user different from the first user is performed by the control unit of the server. is performed by said server,
The third user is included in the chat room. The program according to claim 9,
Control by the control unit of the server to cancel the first setting set for the first user based on a second input by the first user to the chat room displayed on the first terminal Doing is performed by the server. A program according to claim 10,
Based on the second input, the control unit may perform a process of transferring at least the amount transferred from the second user to the first user from the first user to the third user. performed by the server; The program according to claim 9,
the second user's input to the chat room displayed on the second terminal is an input to display regarding a first remittance request from the first user to the second user, displayed in the chat room;
input by the second user in response to the display regarding the second remittance request transmitted from the third terminal of the third user different from the second user to the second terminal and displayed in the chat room of the second terminal; and receiving, by the communication unit, information regarding remittance from the second user to the third user based on the second setting;
The server executes a process related to the remittance from the second user to the third user by the control unit based on the information related to the remittance from the second user to the third user. The program according to any one of claims 1 to 12,
Receiving by the communication unit from the second terminal information regarding approval to include the second user in the chat room;
The server performs a process of including the second user in the chat room by the control unit based on the information about the approval. The program according to any one of claims 1 to 13,
Based on the processing related to the remittance from the second user to the first user, name information based on identification of the second user and information related to the completion of remittance from the second user to the first user Transmitting by the communication unit to the first terminal is performed by the server. The program according to any one of claims 1 to 14,
Based on the elapse of a set period of time or based on a set time, the server performs control to delete the chat room by the control unit. The program according to any one of claims 1 to 14,
receiving information about the first user from the second user by the communication unit;
Based on the information about the first user, the server performs control by the control unit to change the first setting regarding remittance to the first user to a third setting. 17. The program according to claim 16,
The third setting includes a setting related to disabling remittance to the first user. The program according to any one of claims 1 to 15,
receiving information about the first user from the second user by the communication unit;
The server performs control by the control unit to at least temporarily suspend the use of the first user's account based on the information about the first user. The program according to any one of claims 1 to 18,
Receiving, by the communication unit, refund information relating to refunding the amount transferred from the second user to the first user to the first user;
Based on the refund information, the server executes a process related to remittance of the amount of money from the first user to the second user by the control unit. The program according to any one of claims 1 to 19,
The chat room includes information indicating that remittance has been made in response to the remittance request sent from the first user to the second user when the second user remits money. 21. The program according to claim 20,
The chat room includes information indicating that, if the second user has not remitted money in response to the remittance request, remittance has not been performed in response to the remittance request. 22. A program according to claim 21,
Information indicating that remittance has been made in response to the remittance request or information indicating that remittance has not been made in response to the remittance request is displayed only in the chat room displayed on the first terminal of the first user. be. sending first content input by the first user to the 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 the second user; information of a server that transmits to the first terminal the second content that is input by the second user to the second terminal on which the chat room is displayed and that is transmitted from the second terminal A processing method comprising:
a control unit of the server to set, for the chat room, a first setting relating to a setting enabling remittance to the first user included in the chat room ;
A communication unit of the server receives information regarding remittance from the second user to the first user based on the first setting and the second user's input to the chat room displayed on the second terminal. and
performing a process related to remittance from the second user to the first user by the control unit based on information related to remittance from the second user to the first user. sending first content input by the first user to the 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 the second user; and transmits to the first terminal the second content input by the second user to the second terminal on which the chat room is displayed and transmitted from the second terminal. hand,
a control unit configured to set, for the chat room, a first setting relating to a setting enabling remittance to the first user included in the chat room ;
a communication unit that receives information about remittance from the second user to the first user based on the first setting and the second user's input to the chat room displayed on the second terminal;
The control unit performs processing related to remittance from the second user to the first user based on information related to remittance from the second user to the first user.

Images