Methods and apparatus for money transfer services

Abstract

To provide a method and apparatus for a remittance service.SOLUTION: An operation method of a server providing a remittance service includes the steps of: receiving, from a remitter participating in an anonymous chatroom by using a first temporary profile, a request for a remittance to a second temporary profile participating in the anonymous chatroom; verifying a remittance qualification of an account of the remitter; generating remittance transaction information for remitting the amount corresponding to the remittance request to an account of a remittee corresponding to the second temporary profile; and transmitting, to the account of the remittee, a remittance notification including information on the first temporary profile as remitter information.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The following embodiments relate to a method and apparatus for a remittance service, specifically, to a server that provides a remittance service and a client that uses the remittance service.

Background Art

[0002] Fintech (Financial Technology) refers to financial services and industries based on information technologies such as mobile, big data, and SNS as a compound word of finance and technology. Various financial services differentiated from existing financial services have emerged using fintech technology, for example, mobile banking and app cards. Recently, as fintech services have spread, banking operations such as transfers or deposits can be directly processed using a computer or mobile device without visiting a bank, and online remittance services are widely used. Conventionally, in order to use an online remittance service, a public certificate was used, or an exchange of personal information such as the name of the recipient, bank name, and account number was essential. Recently, technologies for providing convenient online remittance services have been developed, such as simplifying the authentication process or simplifying the information required for remittance transactions.

Summary of the Invention

Problems to be Solved by the Invention

[0003] An object of the present invention is to provide a technology that enables remittance between participants in an anonymous chat room who do not know each other's account information. However, the technical problems are not limited to the above-described technical problems, and further technical problems may exist.

Means for Solving the Problems

[0004] The operation method of a server providing a remittance service relating to one aspect includes the steps of: receiving a remittance request from a remitter who is participating in an anonymous chat room provided by the server as a first temporary profile, for a second temporary profile that is participating in the anonymous chat room; verifying the remittance eligibility of the remitter's account based on the authentication information of the remitter's account; generating remittance transaction information for sending the amount corresponding to the remittance request to the recipient's account corresponding to the second temporary profile, based on the remittance eligibility of the remitter's account; and sending a remittance notification to the recipient's account, based on the remittance transaction information, which includes information about the first temporary profile as remitter information.

[0005] The step of generating the remittance transaction information may include, if the remitter's account eligibility has been verified, the step of generating the remittance transaction information, and if the remitter's account eligibility has not been verified, the step of requesting the remitter to authenticate their identity to obtain remittance eligibility.

[0006] The step of generating the remittance transaction information may include a step of verifying the recipient's eligibility to receive payments based on the recipient's account authentication information, and a step of generating the remittance transaction information based on whether or not the recipient's account is eligible to receive payments.

[0007] The step of generating the remittance transaction information, further based on whether the recipient's account is eligible to receive payments, may include the steps of generating the remittance transaction information if the recipient's account is confirmed to be eligible to receive payments, and sending a remittance failure notification to the sender's account if the recipient's account is not confirmed to be eligible to receive payments.

[0008] The step of receiving the remittance request may include the steps of providing a remittance interface for the remittance request to the sender's terminal via the anonymous chat room, and receiving input for the remittance request from the sender's terminal via the remittance interface.

[0009] The input for the remittance request may include an input for selecting the second temporary profile as the recipient from among at least one temporary profile participating in the anonymous chat room, and an input for the amount to be remitted.

[0010] The step of providing the aforementioned remittance interface may include the step of distinguishing and displaying among anonymous profiles participating in the anonymous chat room a first type of temporary profile corresponding to accounts that include authentication information and a second type of temporary profile corresponding to accounts that do not include authentication information.

[0011] The step of providing the aforementioned remittance interface may include the step of deactivating the input for selecting a second type of temporary profile as the recipient, which corresponds to an account among the anonymous profiles participating in the anonymous chat room that does not contain authentication information.

[0012] The operation method of the server may further include the step of sending a remittance notification to the remitter's account, which includes information about the second temporary profile as recipient information.

[0013] The operation method of the server may further include the steps of: receiving a receipt request from the recipient's account based on a remittance notification sent to the recipient's account; verifying the recipient's eligibility to receive based on the recipient's account authentication information; and processing the remittance transaction corresponding to the receipt request based on whether the recipient's account is eligible to receive.

[0014] The step of processing the remittance transaction may include, if the recipient's account is verified as eligible to receive payments, the step of processing the remittance transaction, and if the recipient's account is not verified as eligible to receive payments, the step of requesting the recipient to authenticate their identity to obtain eligibility.

[0015] The server's operation method may further include the step of sending a receipt notification to the recipient's account, which includes information about the first temporary profile as sender information, based on the processing of the remittance transaction corresponding to the receipt request.

[0016] The server's operation method may further include the step of sending a receipt notification to the sender's account, which includes information about the second temporary profile as recipient information, based on the processing of the remittance transaction corresponding to the receipt request.

[0017] The remittance transaction information may include an identifier for the recipient corresponding to the remittance request and an identifier for the remittance transaction corresponding to the remittance request.

[0018] The remitter's account may include an account generated when the remitter subscribes to the remittance service.

[0019] The recipient's account may include an account created when the recipient subscribes to the money transfer service.

[0020] The method of operation for a client using a remittance service provided by a server relating to one aspect includes the steps of requesting the server to grant eligibility to remit through an anonymous chat room in which the client is participating, based on whether or not the account that has joined the remittance service has been authenticated; selecting at least one of the temporary profiles participating in the anonymous chat room as the recipient; and requesting a remittance to the temporary profile based on the eligibility of the participant corresponding to the temporary profile selected as the recipient.

[0021] A server providing a remittance service relating to one aspect includes at least one processor that receives a remittance request from a remitter participating as a first temporary profile in an anonymous chat room provided by the server to a second temporary profile participating in the anonymous chat room, verifies the remittance eligibility of the remitter's account based on the authentication information of the remitter's account, generates remittance transaction information to send the amount corresponding to the remittance request to the recipient's account corresponding to the second temporary profile based on the remittance eligibility of the remitter's account, and sends a remittance notification to the recipient's account, including information about the first temporary profile as remitter information, based on the remittance transaction information.

[0022] In generating the remittance transaction information, the processor may generate the remittance transaction information if the remitter's account eligibility is verified, or may request the remitter to perform identity verification to obtain remittance eligibility if the remitter's account eligibility is not verified.

[0023] The processor can receive a receipt request from the recipient's account based on a remittance notification sent to the recipient's account, verify the recipient's eligibility to receive based on the recipient's account authentication information, and process the remittance transaction corresponding to the receipt request based on whether the recipient's account is eligible to receive.

[0024] A client using a money transfer service provided by a server relating to one aspect includes at least one processor that, based on whether or not the account subscribed to the money transfer service is authenticated, requests eligibility to send money through an anonymous chat room in which the client is participating, selects at least one of the temporary profiles participating in the anonymous chat room as the recipient, and requests a transfer to the temporary profile based on the eligibility of the participant corresponding to the temporary profile selected as the recipient.

[0025] A method for providing a remittance service in conjunction with a remittance server by a messaging server that provides a messaging service related to one side includes receiving a remittance request from a remitter who participates as a first temporary profile in an anonymous chat room for a second temporary profile that is participating in the anonymous chat room; transmitting the remittance request to the remittance server based on whether the remitter's account has the remittance qualification; receiving remittance transaction information including the identifier of the second temporary profile as the recipient from the remittance server; and transmitting a remittance notification message to the recipient's account mapped to the identifier of the second temporary profile based on the remittance transaction information.

[0026] The method for providing the remittance service may further include generating a temporary profile subordinate to the anonymous chat room corresponding to each participant in the anonymous chat room, and mapping and storing the identifier of the temporary profile of each participant to the account of each participant who has joined the messaging service.

[0027] The step of transmitting the remittance request may include transmitting the remittance request to the remittance server further based on whether the recipient's account mapped to the second temporary profile has the receiving qualification.

[0028] The step of receiving the remittance request may include providing a remittance interface for the remittance request to the remitter's terminal through the anonymous chat room, and receiving an input for the remittance request from the remitter's terminal through the remittance interface.

[0029] The input for the remittance request may include an input for selecting the second temporary profile as the recipient and an input for the remittance amount among at least one temporary profile that is participating in the anonymous chat room.

[0030] The method of providing the money transfer service may further include the step of sending a money transfer notification message to the sender's account, which includes information about the second temporary profile as recipient information.

[0031] The aforementioned remittance notification message may include information regarding the first temporary profile as remitter information.

[0032] The aforementioned remittance transaction information may include a remittance transaction identifier corresponding to the remittance request and a recipient identifier corresponding to the remittance request.

[0033] The sender's account may include an account created when the sender subscribes to the messaging service.

[0034] The recipient's account may include an account created when the recipient subscribes to the messaging service.

[0035] The method of operation for a client using a remittance service provided in conjunction with a remittance server by a messaging server relating to one aspect includes the steps of requesting the messaging server to grant eligibility to remit through an anonymous chat room in which the user is participating, based on whether the account that has joined the messaging service is authenticated; selecting at least one of the temporary profiles participating in the anonymous chat room as the recipient; and requesting a remittance to the temporary profile selected as the recipient.

[0036] The step of requesting the transfer may include a step of requesting the transfer to the temporary profile based on the eligibility of the participant corresponding to the temporary profile selected as the recipient.

[0037] A method for providing a money transfer service in conjunction with a money transfer server using a messaging server that provides messaging services relating to one aspect includes the steps of: receiving a recipient verification request from the money transfer server corresponding to a request to receive a money transfer via an anonymous chat room; verifying whether the account that requested the money transfer from the money transfer server is the same user as the recipient identifier included in the request to receive the money transfer, based on the identifier of the temporary profile of a participant subordinate to the anonymous chat room and the mapping information of the participant's account; and transmitting the verification result to the money transfer server.

[0038] The method of providing the money transfer service may further include the steps of receiving the receipt request from the recipient's account based on a money transfer notification message sent to the recipient's account, and sending the receipt request to the money transfer server based on whether the recipient's account is eligible to receive.

[0039] The method for providing the money transfer service may further include the steps of receiving the processing result of the receipt request from the money transfer server, and in response to the processing result, sending a receipt notification message to the account that requested the receipt.

[0040] The method for providing the money transfer service may further include the steps of receiving the processing result of the receipt request from the money transfer server, and in response to the processing result, sending a receipt notification message to the account that requested the money transfer.

[0041] A messaging server that provides a remittance service in conjunction with a remittance server relating to one aspect includes at least one processor that receives a remittance request from a remitter participating in an anonymous chat room as a first temporary profile to a second temporary profile participating in the anonymous chat room, sends the remittance request to the remittance server based on whether the remitter's account is eligible to remit, receives remittance transaction information from the remittance server that includes the identifier of the second temporary profile as the recipient, and sends a remittance notification message to the recipient's account mapped to the identifier of the second temporary profile based on the remittance transaction information.

[0042] The processor can generate a temporary profile subordinate to the anonymous chat room for each participant in the anonymous chat room, and map the identifier of each participant's temporary profile to the account of each participant who has subscribed to the messaging service and store it.

[0043] The processor may, in sending the remittance request, send the remittance request to the remittance server based further on whether the recipient's account mapped to the second temporary profile is eligible to receive the remittance.

[0044] A client for using a remittance service provided in conjunction with a remittance server by a messaging server relating to one aspect includes at least one processor that, based on whether or not the account subscribed to the messaging service is authenticated, requests the messaging server to grant eligibility to remit through an anonymous chat room in which the client is participating, selects at least one of the temporary profiles participating in the anonymous chat room as the recipient, and requests a remittance to the temporary profile selected as the recipient.

[0045] In requesting the transfer, the processor may request the transfer to the temporary profile based on the eligibility of the participant corresponding to the temporary profile selected as the recipient.

[0046] A messaging server that provides a remittance service in conjunction with a remittance server relating to one aspect includes at least one processor that receives a recipient verification request from the remittance server corresponding to a request to receive a remittance via an anonymous chat room, verifies whether the account that requested the remittance from the remittance server to receive the remittance is the same user as the recipient identifier included in the request, based on the identifier of the temporary profile of a participant subordinate to the anonymous chat room and the mapping information of the participant's account, and transmits the verification result to the remittance server.

[0047] The processor can receive the receipt request from the recipient's account based on the remittance notification message sent to the recipient's account, and send the receipt request to the remittance server based on whether the recipient's account is eligible to receive the payment. [Effects of the Invention]

[0048] According to the present invention, it is possible to provide a technology that enables money transfers between participants in an anonymous chat room who do not know each other's account information. [Brief explanation of the drawing]

[0049] [Figure 1] This is a flowchart illustrating the operation method of a server providing a money transfer service according to one embodiment. [Figure 2A] This diagram illustrates the steps for generating remittance transaction information based on remittance eligibility and receiving eligibility according to one embodiment. [Figure 2B] This diagram illustrates the steps for generating remittance transaction information based on remittance eligibility and receiving eligibility according to one embodiment. [Figure 3A] This figure illustrates a remittance interface screen according to one embodiment. [Figure 3B] This figure illustrates a remittance interface screen according to one embodiment. [Figure 3C]This figure illustrates a remittance interface screen according to one embodiment. [Figure 3D] This figure illustrates a remittance interface screen according to one embodiment. [Figure 3E] This figure illustrates a remittance interface screen according to one embodiment. [Figure 3F] This figure illustrates a remittance interface screen according to one embodiment. [Figure 4] This is a flowchart illustrating the operation method of a server providing a money transfer service according to one embodiment. [Figure 5] This diagram illustrates the steps for processing a remittance transaction based on eligibility to receive according to one embodiment. [Figure 6] This is a flowchart illustrating the operation method of a client for using a money transfer service provided by a server according to one embodiment. [Figure 7] This is an illustrative diagram of the hardware configuration of a remittance system according to one embodiment. [Figure 8] This diagram illustrates a remittance system according to one embodiment. [Figure 9] This is an operation flowchart of a method for providing a money transfer service in conjunction with a money transfer server using a messaging server according to one embodiment. [Figure 10] This is a flowchart illustrating the operation method of a client for using a money transfer service provided in conjunction with a money transfer server by a messaging server according to one embodiment. [Figure 11] This diagram illustrates an overall scenario of a remittance process according to one embodiment. [Figure 12A] This figure shows an example of a remittance notification message according to one embodiment. [Figure 12B] This figure shows an example of a remittance notification message according to one embodiment. [Figure 13] This is an operation flowchart of a method for providing a money transfer service in conjunction with a money transfer server using a messaging server according to one embodiment. [Figure 14]This diagram illustrates an overall scenario regarding the receiving process of a money transfer service according to one embodiment. [Figure 15A] This figure shows an example of a receipt notification message according to one embodiment. [Figure 15B] This figure shows an example of a receipt notification message according to one embodiment. [Figure 16] This is an illustrative diagram of the hardware configuration of a remittance system according to one embodiment. [Modes for carrying out the invention]

[0050] The specific structural or functional descriptions of the embodiments are disclosed for illustrative purposes only and can be modified in various ways. Therefore, the embodiments are not limited to the specific disclosure, and the scope of this specification includes modifications, equivalents, or substitutions that are part of the technical idea.

[0051] Terms such as "first" or "second" may be used to describe multiple components, but such terms should be interpreted solely for the purpose of distinguishing one component from others. For example, "first component" can be named "second component," and similarly, "second component" can also be named "first component."

[0052] When it is mentioned that one component is “linked” or “connected” to another component, it should be understood that it is directly linked to or connected to the other component, but that other components may be present in between.

[0053] A singular expression includes plural expressions unless the context clearly indicates otherwise. In this disclosure, terms such as “includes” or “has” are intended to specify that the described features, figures, stages, actions, components, parts, or combinations thereof exist, and should not be understood to preemptively exclude the existence or possibility of adding one or more other features, figures, stages, actions, components, parts, or combinations thereof.

[0054] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as those commonly understood by a person of ordinary skill in the art to which this embodiment belongs. Commonly used predefined terms should be interpreted as having the meaning consistent with their meaning in the context of the relevant art, and not as ideal or overly formal unless expressly defined herein.

[0055] The embodiments will be described in detail below with reference to the attached drawings. In the description with reference to the attached drawings, the same components will be given the same reference numerals regardless of the reference numerals in the drawings, and redundant explanations for them will be omitted.

[0056] Figure 1 is a flowchart illustrating the operation method of a server providing a money transfer service according to one embodiment.

[0057] Referring to Figure 1, the operation method of a server providing a money transfer service according to one embodiment includes the steps of: receiving a money transfer request from a sender participating in an anonymous chat room as a first temporary profile to a second temporary profile participating in the anonymous chat room (Step S110); verifying the sender's account's eligibility to send money (Step S120); generating money transfer transaction information to send the amount corresponding to the money transfer request to the recipient's account corresponding to the second temporary profile (Step S130); and sending a money transfer notification to the recipient's account, including information about the first temporary profile as sender information (Step S140). More specifically, the operation described with reference to Figure 1 corresponds to the money transfer process of the money transfer service performed on the server.

[0058] According to one embodiment, the server provides a money transfer service, which generates and manages accounts for registered users and provides a service for sending and receiving a certain amount of money using these accounts. For example, the account may mean a bank account, or it may mean an online account that stores virtual electronic currency having a certain monetary value.

[0059] In one embodiment, the server generates an account corresponding to a user who has requested to join, and a client logged into the generated account can use the services provided by the server. The client includes the terminal of a user logged into the money transfer service account.

[0060] According to one embodiment, the server can generate an account based on the real name information of a user who has requested to join. For example, the server may generate a user account based on the authenticated real name information and / or the mobile phone number registered under the real name of the user who has requested to join. An account is a unit for the server to identify a user who has joined the service.

[0061] In one embodiment, the sender means a client that has requested a remittance from the server, and the recipient means a client designated by the sender as the recipient of the requested remittance. The sender's account may include an account created by the sender subscribing to the remittance service provided by the server, and the recipient's account may include an account created by the recipient subscribing to the remittance service provided by the server.

[0062] Step S110 according to one embodiment includes receiving a remittance request from a remitter who is participating in an anonymous chat room provided by the server as a first temporary profile, for a second temporary profile that is participating in the anonymous chat room.

[0063] A server according to one embodiment provides an anonymous chat room service to a client. An anonymous chat room is a chat room in which participants join via a temporary profile that is not based on a real name. As an example, the anonymous chat room service may include the open chat service provided by the applicant Kakao, specifically the other-user-based open chat service provided in the applicant's KakaoTalk application, and the anonymous chat room means a chat room (or chat room) of the open chat service provided by the applicant Kakao. The open chat service provided by Kakao is merely an example of the anonymous chat room service, and is not limited thereto, and the anonymous chat room service includes a service that provides a chat room in which participants join via a temporary profile that is not based on a real name. An anonymous chat room according to one embodiment includes the form of a 1:1 chat room or a group chat room that includes two or more users as participants.

[0064] A temporary profile according to one embodiment is a profile temporarily assigned to a user's account and may include as identification information an arbitrary name entered by the user or a name arbitrarily generated by the server, rather than the user's real name information. In other words, an anonymous chat room is a chat room that can be joined through a temporarily generated temporary profile without exposing the user's account based on their real name information. Unlike a general chat room for chatting with other users whose accounts are known, an anonymous chat room can be used as a means for users who do not share accounts with each other to chat. Participants in an anonymous chat room may be displayed as temporary profiles to other participants in the anonymous chat room and can exchange messages within the anonymous chat room using their temporary profiles.

[0065] According to one embodiment, a temporary profile may be generated in conjunction with an anonymous chat room. For example, a temporary profile may be generated to display a user in a specific anonymous chat room when the user joins that anonymous chat room, and may be deleted when the anonymous chat room ends or when the user leaves the anonymous chat room. Also, for example, a first temporary profile of a first user account generated in conjunction with a first anonymous chat room and a second temporary profile of a first user account generated in conjunction with a second anonymous chat room are considered separate temporary profiles distinct from each other.

[0066] In one embodiment, the server can generate temporary profiles corresponding to each participant in an anonymous chat room, and map and store the identifier of each participant's temporary profile to the account of each participant who has subscribed to the messaging service. The temporary profile identifier is an identifier for identifying a temporary profile and is a type of identifier distinct from the user's account. The server maps and stores the temporary profile of a user generated to participate in an anonymous chat room to the account of the user who has subscribed to the messaging service. If a user participates in multiple anonymous chat rooms, a temporary profile corresponding to each of the multiple anonymous chat rooms is generated, and the identifiers of the multiple temporary profiles are mapped and stored to the user's account. The temporary profile identifier further includes information for identifying the anonymous chat room to which the temporary profile belongs. As an example, the anonymous chat room to which a given temporary profile belongs can be identified based on the temporary profile identifier.

[0067] According to one embodiment, a remittance request includes information necessary for the remittance. For example, a remittance request may include a recipient identifier and the amount to be remitted. The recipient identifier may include an identifier for a second temporary profile that is a participant in an anonymous chat room. The second temporary profile is a temporary profile designated by the remitter as the recipient of the remittance request. According to one embodiment, a remittance request may further include a remitter identifier. The remitter identifier may include information about the client that sent the remittance request, for example, the account of the user who sent the remittance request.

[0068] According to one embodiment, the server can recognize the account of the user who sent the remittance request as the sender's account, and recognize the account mapped to the identifier of the second temporary profile included in the remittance request as the recipient's account. Since the sender's client knows its own account, the sender's account can be communicated to the server using the client's information that sent the remittance request.

[0069] According to one embodiment, a remittance request can be received via an anonymous chat room. For example, step S110 of receiving a remittance request includes providing a remittance interface for the remittance request to the sender's terminal via the anonymous chat room, and receiving input for the remittance request from the sender's terminal via the remittance interface. As an example, the input for the remittance request may include input selecting a second temporary profile as the recipient from at least one temporary profile participating in the anonymous chat room, and inputting the amount to be remitted. In other words, the server can provide a remittance interface via an anonymous chat room, and the sender can request a remittance from the server via the remittance interface and input information for the remittance request, such as the recipient and the amount to be remitted.

[0070] For example, the step of providing a remittance interface may include a step of distinguishing and displaying a first type of temporary profile, which corresponds to an anonymous profile participating in an anonymous chat room that includes authentication credentials, and a second type of temporary profile, which corresponds to an anonymous profile participating in an anonymous chat room that does not include authentication credentials. Also, for example, the step of providing a remittance interface may include a step of deactivating the input for selecting a second type of temporary profile, which corresponds to an anonymous profile participating in an anonymous chat room that does not include authentication credentials, as the recipient. The remittance interface is described below.

[0071] Step S120 according to one embodiment includes a step of verifying the eligibility of the sender's account to send money based on the authentication information of the sender's account. Eligibility to send money is the eligibility required to request a transfer through an anonymous chat room, and more specifically, the eligibility required to request a transfer by designating a temporary profile, which is not account information, as the recipient. Eligibility to send money is determined by whether or not the sender's account is authenticated, for example, if the sender's account is an authenticated account, or if the sender's account holds a certificate of authentication issued by the server, it is determined that the sender is eligible to send money.

[0072] According to one embodiment, a registered user's account can be authenticated via the server according to a predetermined method. The server stores authentication information (e.g., a certificate) obtained from the authentication of the registered user's account and determines whether any user's account is an authenticated account based on the stored authentication information. If authentication information corresponding to the sender's account is stored, the server determines that the sender's account is eligible to send money.

[0073] Step S130 according to one embodiment includes generating remittance transaction information for sending an amount corresponding to a remittance request to the recipient's account corresponding to a second temporary profile, based on the remittance eligibility of the remitter's account.

[0074] As an example, referring to Figure 2A, the step of generating remittance transaction information (for example, step S130 shown in Figure 1) includes step S210 to generate remittance transaction information if the remitter's account is verified as eligible to remit, and step S220 to request the remitter to authenticate their identity to obtain remittance eligibility if the remitter's account is not verified as eligible to remit. As an example, based on the server's authentication request 220, the remitter's account may perform authentication via the server according to a predetermined method. Since remittance eligibility is obtained when the authentication of the remitter's account is successfully performed in step S220, the server generates remittance transaction information (S210).

[0075] According to one embodiment, the remittance transaction information includes a remittance transaction identifier corresponding to the remittance request and a recipient identifier corresponding to the remittance request. The remittance transaction identifier is an identifier assigned to each remittance unit in order for the server to distinguish and recognize the remittance transaction. The recipient identifier corresponds to the recipient identifier included in the remittance request, in other words, the identifier of the second temporary profile participating in the anonymous chat room. As an example, the remittance transaction information may further include information regarding the validity period of the remittance transaction. The information regarding the validity period of the remittance transaction means the validity period during which the receipt of the remittance can be requested, and may be determined based on the time the remittance request was made or the time the remittance request was received by the server.

[0076] According to one embodiment, a token for a remittance transaction may be generated in response to the remittance transaction information. The token for the remittance transaction is the information necessary to authenticate the remittance transaction. The server can obtain the recipient's account mapped to the identifier of the second temporary profile designated as the recipient, and can therefore generate a token based on the recipient's second temporary profile identifier and the recipient's account. The server can generate a token corresponding to the user's temporary profile identifier and the user's account mapped thereto using a token generation logic. As an example, the server may further generate a token based on additional information to identify the remittance transaction, such as the validity period of receipt information based on the time the remittance request was received. A token further generated based on the validity period of receipt information can also be used by the server to verify the validity period of receipt of the remittance. A method for authenticating a remittance transaction using a token is described below. The token can be transmitted to the remittance transaction information and the recipient.

[0077] Referring again to Figure 1, step S130 according to one embodiment includes the step of verifying the recipient's eligibility to receive based on the recipient's account authentication information, and the step of generating remittance transaction information based on whether the recipient's account is eligible to receive. Eligibility to receive is the qualification required to receive a remittance made through an anonymous chat room, and more specifically, the qualification required to receive a remittance requested by designating a temporary profile, which is not account information, as the recipient. Eligibility to receive is determined by whether the recipient's account is authenticated, for example, if the recipient's account is an authenticated account, or if the recipient's account holds a certificate of identity verification issued by the server, then the recipient is eligible to receive. In other words, the server can generate remittance transaction information once both the sender's account eligibility to send and the recipient's account eligibility to receive have been verified.

[0078] As an example, referring to Figure 2B, the server receives a recipient selection input from the remitter whose remitter eligibility has been verified (S230) and verifies the eligibility of the selected recipient (S240). As an example, since the recipient selection input is received (S230) in step S110, the remitter eligibility verification 120 of the remitter's account may be performed after the recipient selection input is received (S230). The step of generating remittance transaction information, further based on whether the recipient's account is eligible to receive, includes step S250 to generate remittance transaction information if the recipient's account is eligible to receive, and step S260 to send a remittance failure notification to the remitter's account if the recipient's account is not eligible to receive. Step S250 to generate remittance transaction information is performed when both remitter eligibility and recipient eligibility have been verified.

[0079] Step S240, according to one embodiment, is a step to verify the eligibility of a recipient account to an account corresponding to a temporary profile designated as a recipient by the sender, and is performed in response to the recipient selection input 230 received from the sender. If the recipient account's eligibility has not been verified, the server does not request identity verification for eligibility verification from the recipient who has not entered a request for the remittance transaction, and instead provides the sender with a remittance failure notification.

[0080] According to one embodiment, the server may generate remittance transaction information without verifying eligibility to receive, and eligibility verification may be performed when a receipt request is received from the recipient.

[0081] In one embodiment, unlike the one shown in Figure 2B, the server can first verify whether a participant in the anonymous chat room is eligible to receive the payment before the recipient selection input is received (S230). The server provides the sender with participants who have been confirmed to be eligible to receive the payment as recipients, and inputs for selecting ineligible participants as recipients are not activated. This will be explained below.

[0082] Step S140 according to one embodiment includes sending a remittance notification to the recipient's account, which includes information about the first temporary profile as sender information, based on the remittance transaction information generated in step S130. For example, the remittance notification sent to the recipient may be sent in the form of a message and a push notification. The server retrieves the recipient's account corresponding to the temporary profile identifier included as the recipient identifier in the remittance transaction information and sends the remittance notification to the recipient's account. As described above, the server stores mapping information between the temporary profile identifiers subordinate to the anonymous chat room and the user accounts to which the temporary profiles have been assigned. Based on the mapping information, the server retrieves the recipient's account corresponding to the temporary profile identifier included as the recipient identifier in the remittance transaction information. The server can communicate the remittance transaction identifier and the token for the remittance transaction included in the remittance transaction information to the recipient via the remittance notification message.

[0083] According to one embodiment, a remittance notification sent to the recipient's account includes information to notify the recipient that a certain amount of money has been sent by the sender. The remittance notification sent to the recipient may include information about the first temporary profile as sender information. Based on the mapping information, the server obtains the identifier of the sender's first temporary profile that belongs to the anonymous chat room mapped to the sender's account corresponding to the remittance request. The anonymous chat room is an anonymous chat room in which the sender and recipient participate, and in which the remittance request by the sender originated. Since participant accounts are not exposed in the anonymous chat room, the sender's account is not exposed in the remittance notification, and it may include information about the first temporary profile of the anonymous chat room. The temporary profile information includes the name or alias set in the temporary profile, regardless of the user's real name.

[0084] According to one embodiment, a remittance notification sent to a recipient may include a receipt request function. For example, a remittance notification sent to a recipient may include an interface object for receipt requests. The recipient requests receipt of the remittance based on the received remittance notification, and the receipt process is initiated by the recipient's receipt request. The receipt process is described below.

[0085] The operation method of the server according to one embodiment may further include the step of sending a remittance notification to the sender's account, which includes information about the second temporary profile as recipient information. The server may also send a remittance notification to the sender's account based on the remittance transaction information. For example, the remittance notification sent to the sender is sent in the form of a message and a push notification. For example, the remittance notification sent to the sender includes information to notify the recipient that a certain amount of money has been transferred. The recipient information is displayed in the information about the second temporary profile. For example, the remittance notification may include information about the anonymous chat room where the remittance request originated. The anonymous chat room information includes the names set in the anonymous chat room in which the recipient and the sender participate.

[0086] In one embodiment, the transmission of a remittance is distinguished from the completion of receipt, and receipt is completed when the recipient requests receipt of the transmitted remittance and the receipt process is completed.

[0087] Figures 3A to 3D illustrate the remittance interface screen according to one embodiment.

[0088] Referring to Figure 3A, a send button 301 is provided that connects to the send interface via a menu tap 302 included in the anonymous chat room interface. The anonymous chat room interface shown in Figure 3A can be switched to the send interface shown in Figure 3B by selecting the send button 301.

[0089] Referring to Figure 3B, the remittance interface displays a list of temporary profiles participating in an anonymous chat room and includes a picker for selecting a temporary profile participating in an anonymous chat room as the recipient. The remittance interface receives input to select at least one temporary profile from among the temporary profiles participating in an anonymous chat room, and the selected temporary profile 311 is designated as the recipient of the remittance.

[0090] According to one embodiment, the server displays anonymous profiles participating in an anonymous chat room, distinguishing between a first type of temporary profile corresponding to accounts with authentication information and a second type of temporary profile corresponding to accounts without authentication information. Accounts with authentication information are accounts whose identity has been verified via the server, while accounts without authentication information are accounts whose identity has not been verified via the server. In other words, the first type of temporary profile corresponds to the temporary profile of an account whose eligibility to receive has been confirmed, and the second type of temporary profile corresponds to the temporary profile of an account whose eligibility to receive has not been confirmed.

[0091] As an example, referring to Figure 3C, among the temporary profiles participating in the anonymous chat room, temporary profiles of type 1, 323 and 322, are displayed with marks 321 and 324 added to indicate that they are verified profiles whose eligibility has been confirmed.

[0092] As an example, referring to Figure 3D, temporary profiles participating in an anonymous chat room are displayed in lists 331 and 332, which are categorized according to whether or not they are eligible to receive. The server deactivates the input for selecting a second type temporary profile as a recipient. For example, by providing a picker 333 for selection input only in list 331 of first type temporary profiles whose eligibility has been confirmed, and not providing a picker for selection input in list 332 of second type temporary profiles, the server deactivates the input for selecting a second type temporary profile as a recipient.

[0093] The remittance interface for recipient selection shown in Figures 3B to 3D is switched to the remittance interface for remittance amount input shown in Figure 3F through the input for selecting the recipient. Referring to Figure 3F, the remittance interface includes an input window 341 for entering the remittance amount.

[0094] Referring to Figure 3E, a send button 341 is provided that connects to the send interface via a temporary profile view. The interface of the temporary profile view shown in Figure 3E is switched to the send interface for entering the send amount shown in Figure 3F through the input of selecting the send button 341. When connecting to the send interface via the send button 341 included in the temporary profile view, the temporary profile is selected as the recipient, and the interface is switched to the send interface for entering the send amount shown in Figure 3F without any further process of selecting the recipient. For example, the send button 341 provided via the temporary profile view shown in Figure 3E may or may not be exposed depending on whether the account corresponding to the temporary profile is eligible to receive the payment. Specifically, if the account corresponding to the temporary profile is not confirmed to be eligible to receive the payment, the send button 341 for the payment request is not exposed.

[0095] Figure 4 is a flowchart illustrating the operation method of a server providing a money transfer service according to one embodiment.

[0096] Referring to Figure 4, the operation method of a server providing a remittance service according to one embodiment includes the steps of receiving a receipt request from the recipient's account S410, verifying the recipient's eligibility to receive the receipt in the recipient's account S420, and processing the remittance transaction corresponding to the receipt request S430. For example, steps S410 to S430 may be performed after step S140 shown in Figure 1.

[0097] Step S410 according to one embodiment includes receiving a receipt request from the recipient's account based on a remittance notification sent to the recipient's account. The recipient requests the server to accept the remittance via the remittance notification. The receipt request includes remittance transaction information and a token for the remittance transaction contained in the remittance notification. For example, the receipt request includes a remittance transaction identifier corresponding to the remittance request, a token for the remittance transaction corresponding to the remittance request, and a recipient identifier corresponding to the remittance request.

[0098] Step S420 according to one embodiment includes a step of verifying the recipient's eligibility to receive based on the recipient's account authentication information. Eligibility is determined by whether the recipient's account is authenticated, for example, if the recipient's account is an authenticated account, or if the recipient's account holds an authentication certificate issued by the server, then the recipient is eligible to receive. As described above, the verification of eligibility to receive may be carried out separately in the receiving process from the sending process, and may be omitted in the receiving process if eligibility verification is performed in the sending process.

[0099] Step S420 according to one embodiment may further include a step of verifying the remittance transaction based on a token for the remittance transaction. The token for the remittance transaction may be included in the receipt request. The server obtains an account mapped to the recipient identifier included in the receipt request based on the mapping information. The server can verify the remittance transaction by generating a token based on the recipient identifier and the obtained account, and comparing whether the generated token is identical to the token included in the receipt request.

[0100] Step S420 according to one embodiment may further include a step of verifying the remittance transaction based on the validity period for receiving the remittance. As described above, the token is generated based on the information of the validity period for receiving, and the server verifies whether the remittance transaction is valid by checking the validity period for receiving in the process of verifying the remittance transaction based on the token. Alternatively, as described above, the remittance transaction information may further include information regarding the validity period of the remittance transaction, and the server can verify whether the remittance transaction is valid by checking the validity period of the remittance transaction information included in the receiving request.

[0101] Step S430 according to one embodiment includes processing a remittance transaction in response to a receipt request, based on whether the recipient's account is eligible to receive. Processing a remittance transaction means processing a remittance and receipt, which involves sending the remittance amount from the remitter's account to the recipient's account based on the remittance transaction information.

[0102] As an example, referring to Figure 5, the step of processing a remittance transaction (for example, step S430 shown in Figure 4) includes step S510, which processes the remittance transaction if the recipient's account is verified as eligible to receive, and step S520, which requests the recipient to authenticate themselves to obtain eligibility if the recipient's account is not verified as eligible to receive. As an example, based on the server's authentication request 520, the recipient's account may authenticate itself via the server according to a predetermined method. Step S520 grants eligibility to receive if the recipient's account is successfully authenticated, and the server processes the remittance transaction (S510).

[0103] One embodiment of the server operation method further includes step S530, which sends a receipt notification to the recipient's account and / or the sender's account.

[0104] According to one embodiment, the server's operation method may include the step of sending a receipt notification to the recipient's account, based on the processing of the remittance transaction corresponding to the receipt request, the receipt notification containing information about the first temporary profile as sender information. For example, the receipt notification sent to the recipient may be sent in the form of a message and a push notification. According to one embodiment, the receipt notification sent to the recipient's account may include information to notify that the receipt of the remittance from the sender has been completed. The receipt notification sent to the recipient may include information about the first temporary profile as sender information. Similar to the remittance notification, the receipt notification may not expose the sender's account and may include information about the first temporary profile corresponding to the sender's account. For example, the receipt notification may include information about the anonymous chat room where the remittance request originated. The anonymous chat room information may include the name set in the anonymous chat room in which the recipient and the sender participate.

[0105] According to one embodiment, the server operation method includes the step of sending a receipt notification to the sender's account, based on the processing of the remittance transaction corresponding to the receipt request, the receipt notification containing information about the second temporary profile as recipient information. For example, the receipt notification sent to the sender may be sent in the form of a message and a push notification. According to one embodiment, the receipt notification sent to the sender's account includes information to notify that the recipient has completed receiving the remittance. The receipt notification sent to the sender may include information about the second temporary profile as recipient information. Similar to the remittance notification, the receipt notification does not expose the recipient's account and includes information about the second temporary profile corresponding to the recipient's account. For example, the receipt notification may include information about the anonymous chat room where the remittance request originated. The anonymous chat room information may include the name set in the anonymous chat room in which the recipient and the sender participate.

[0106] Figure 6 is a flowchart illustrating the operation method of a client using a money transfer service provided by a server according to one embodiment.

[0107] Referring to Figure 6, the operation method of a client for using a money transfer service provided by a server according to one embodiment includes the steps of: requesting the server to grant eligibility to send money through the anonymous chat room in which the user is participating, based on whether or not the account that has joined the money transfer service has been authenticated; selecting at least one of the temporary profiles participating in the anonymous chat room as the recipient, in step S620; and requesting a transfer to the temporary profile based on the eligibility of the participant corresponding to the temporary profile selected as the recipient, in step S630. More specifically, the operation described with reference to Figure 6 corresponds to the money transfer process executed by the client corresponding to the sender.

[0108] Step S610 according to one embodiment includes a step of requesting the server to grant eligibility to send money if the account subscribed to the client's money transfer service is not authenticated. As described above, eligibility to send money is the eligibility required to request a transfer through an anonymous chat room, and eligibility to send money is determined based on whether or not authentication has been performed. Step S610 according to one embodiment includes a step of requesting the server to authenticate in order to obtain eligibility to send money. For example, a client can obtain eligibility to send money by performing identity authentication provided by the server and registering authentication information with the server, or by performing an authentication procedure to obtain a certificate issued by the server. Based on the obtained eligibility to send money, the client can carry out the money transfer process through an anonymous chat room.

[0109] Step S620 according to one embodiment includes selecting at least one temporary profile of a client whose eligibility to send money from the server has been verified in step S610 and who is currently participating in an anonymous chat room, as the recipient.

[0110] Step S630 according to one embodiment is a step of requesting the server to make a transfer, specifying an anonymous profile identifier, which is not another user's account, as the recipient. In other words, a client whose eligibility to make a transfer has been verified can request a transfer from a party whose account information is unknown.

[0111] According to one embodiment, a remittance request can be sent to the server based on the recipient's eligibility. The recipient's eligibility is determined based on whether the account mapped to the temporary profile selected as the recipient on the server is authenticated. If the recipient's eligibility is confirmed, the remittance request is sent to the server.

[0112] In one embodiment, a step of verifying the eligibility of anonymous chat room participants to receive is performed prior to step S620, which is the step of selecting a recipient. Temporary profiles corresponding to participants whose eligibility has been verified are displayed in the list of temporary profiles that can be selected as recipients, while temporary profiles corresponding to participants whose eligibility has not been verified are restricted from being selected as recipients.

[0113] According to one embodiment, unlike step S630, the remittance request may be sent to the server without verifying the recipient's eligibility, and the recipient's eligibility is determined when the recipient requests to receive the remittance.

[0114] Figure 7 is an illustrative diagram of the hardware configuration of a remittance system according to one embodiment.

[0115] Referring to Figure 7, a remittance system according to one embodiment includes a server 720 and a client 710 connected via a network 730.

[0116] In one embodiment, the client 710 may be a mobile terminal implemented by a computer device. For example, the client 710 can communicate with the server 720 and / or other electronic devices via the network 730 using a wireless or wired communication method.

[0117] A server 720 according to one embodiment can be implemented as a computer device or a group of computer devices that communicate with a client 710 and / or other servers via a network 730 to provide commands, code, files, content, services, etc. The communication method is not limited thereto and may include a network 730, and may include a communication method that utilizes a communication network (e.g., a mobile communication network, wired internet, wireless internet, broadcast network), or a short-range wireless communication method between devices. For example, the network 730 may include one or more arbitrary networks such as a PAN (personal area network), LAN (local area network), CAN (campus area network), MAN (metropolitan area network), WAN (wide area network), BBN (broadband network), or the Internet.

[0118] In one embodiment, the server 720 can provide files for application installation to a client 710 connected via the network 730. In this case, the client 710 installs an application (for example, a money transfer service application with chat functionality or a chat service application with money transfer functionality) using the files provided by the server 720. The client 710 also connects to the server 720 in accordance with the control of its operating system (OS) and at least one program (for example, a browser or an installed application), and is provided with services and content offered by the server 720. For example, when the client 710 sends a service request message to the server 720 via the network 730 in accordance with the control of the application, the server 720 sends a code corresponding to the service request message to the client 710, and the client 710 can provide content to the user by configuring and displaying a screen based on the code in accordance with the control of the application.

[0119] According to one embodiment, the client 710 and server 720 include memory 711, 721, processors 713, 723, communication modules 715, 725, and input / output interfaces 717, 727.

[0120] In one embodiment, processors 713 and 723 perform at least one of the operations described above with reference to Figures 1 to 6. For example, processor 713 can perform at least one operation for the client 710 to use the money transfer service provided by the server, as described above with reference to Figure 6, and processor 723 can perform at least one operation for the provision of the money transfer service executed by the server 720, as described above with reference to Figures 1 to 5. Processors 713 and 723 can be configured to process computer program instructions by performing basic arithmetic, logic, and input / output operations. Instructions can be provided to processors 713 and 723 by memory 711 and 721 or by communication modules 715 and 725.

[0121] The memories 711 and 721 may be volatile or non-volatile memory as computer-readable recording media. In one embodiment, the memories 711 and 721 store the information for the money transfer service described above, with reference to Figures 1 to 6. As an example, memory 721 stores accounts and account authentication information generated in response to a subscribed user, and also stores mapping information between the identifier of a temporary profile subordinate to an anonymous chat room and the account of a user to whom the temporary profile has been assigned.

[0122] In one embodiment, the memory 711 may include a money transfer service application with chat functionality, or code for a chat service application with money transfer functionality, which is installed and driven on the client 710 by a file provided by the server 720 via the network 730.

[0123] According to one embodiment, the memory 721 can store a program that embodies the operation of the server for providing the aforementioned money transfer service, as shown in Figures 1 to 6.

[0124] According to one embodiment, communication modules 715 and 725 provide functions for server 720 and client 710 to communicate with each other via network 730, and also provide functions for communicating with other electronic devices or other servers.

[0125] For example, a request generated by the processor 713 of the client 710 in accordance with a program code relating to a money transfer service application with chat functionality, or a money transfer service application with chat functionality, stored in a recording device such as memory 711, may be sent to the server 720 via the network 730 under the control of the communication module 715.

[0126] For example, control signals, instructions, content, files, etc., provided in response to the control of the processor 723 of the server 720 may be received by the client 710 via the communication module 715 of the client 710 through the communication module 715, via the communication module 725 and the network 730.

[0127] The input / output interfaces 717, 727 may also be means for interface with the input / output device 719. For example, the input device may include a device such as a keyboard or mouse, and the output device may include a device such as a display for displaying the application's communication session. In a different example, the input / output interface 717 may be means for interface with a device that combines input and output functions into one, such as a touchscreen. In a more specific example, the processor 713 of the client 710 processes instructions for a computer program loaded into memory 711, and a service screen or content consisting of data provided by the server 720 is displayed on the display via the input / output interface 717. Input received from the user through the input / output device 719 can be provided via the input / output interface 717 in a form that can be processed by the processor 713 of the client 710.

[0128] According to one embodiment, the client 710 and server 720 may include other components not shown in Figure 7. For example, the client 710 may be implemented including at least some of the input / output devices 719 described above, or it may further include other components such as a transceiver, a GPS (Global Positioning System) module, a camera, various sensors, a database, etc.

[0129] Figure 8 shows a remittance system according to one embodiment.

[0130] Referring to Figure 8, a remittance system according to one embodiment includes a messaging server 810, a remittance server 820, and a client 830. The messaging server 810 and the remittance server 820 include devices that work in conjunction with each other to provide remittance services. The client 830 includes a terminal for a user of the remittance service provided by the messaging server 810 and the remittance server 820.

[0131] A messaging server 810 according to one embodiment is a server that provides messaging services, and can send and receive messages between users who have subscribed to the services provided by the messaging server 810, and can also send notification messages to subscribed users. The messaging server 810 may provide messaging services based on instant messages sent and received via messenger applications installed on the terminals of subscribed users, or it may provide messaging services based on SMS (short message service) provided by a mobile communications carrier.

[0132] According to one embodiment, the messaging server 810 generates an account corresponding to a user who has requested to join, and a client 830 logged into the generated account can use the services provided by the messaging server 810. The messaging server 810 can generate an account based on the real name information of the user who has requested to join. For example, the messaging server 810 can generate a user's account based on the authenticated real name information and / or the mobile phone number registered under the real name of the user who has requested to join. An account corresponds to a unit for identifying a user who has joined the messaging service at the messaging server 810. As an example, messages are transmitted to the account of the user designated as the recipient at the messaging server 810, and a list of chat rooms that the user participates in and messages sent and received in the chat rooms are stored corresponding to the user's account. A client 830 can set its own account and other users' accounts as friends, and can send and receive messages with other users' accounts set as friends via the messaging server 810.

[0133] According to one embodiment, the messaging server 810 may provide messaging services not only to users who have subscribed to the messaging service, but also to users who have subscribed to other services linked to the messaging server 810. The client 830 can log in with an account for another service linked to the messaging server 810 and use the services provided by the messaging server 810.

[0134] According to one embodiment, the messaging server 810 provides an anonymous chat room service.

[0135] In one embodiment, the remittance server 820 is a server that provides remittance services in conjunction with the messaging server 810, and can create and manage accounts for registered users, and provide services for sending and receiving a certain amount of money using those accounts. For example, the remittance server 820 may include a bank's online banking server, or an online banking server that provides remittance services via an application.

[0136] According to one embodiment, the remittance server 820 generates an account corresponding to a user who has requested to join, and the client 830 logged into the generated account can use the services provided by the remittance server 810. According to one embodiment, the account corresponding to the messaging server 810 and the account corresponding to the remittance server 820 for the same user are linked to each other. For example, the messaging server 810 can identify the account corresponding to the messaging server 810 from the account corresponding to the remittance server 820, and the remittance server 820 can identify the account corresponding to the remittance server 820 from the account corresponding to the messaging server 810.

[0137] According to one embodiment, the messaging server 810 can provide a money transfer service in conjunction with the money transfer server 820. For example, the messaging server 810 can provide a function that allows users who have subscribed to the messaging service to request money transfers from other users' accounts via a messaging application or chat room interface, and to request receipt of the amount transferred from other users' accounts. The money transfer server 820 can identify the sender who requested the money transfer from the messaging server 810 and the recipient of the requested transfer, and can process the money transfer transaction between the sender's account and the recipient's account provided by the money transfer server 820. The messaging server 810 can transmit a message regarding the money transfer transaction processed by the money transfer server 820 to the user's account. In other words, the messaging server 810 can provide a money transfer service in conjunction with the money transfer server 830 to a client 830 logged into an generated account.

[0138] According to one embodiment, the messaging server 810 can, in conjunction with the remittance server 820, provide a remittance service that allows users to designate other participants in an anonymous chat room whose account information is unknown as recipients and request remittances. The following describes a method by which the messaging server 810 provides a remittance service between participants in an anonymous chat room in conjunction with the remittance server 820, and the operation method of the client 830 for using the remittance service between participants in an anonymous chat room provided by the messaging server 810 in conjunction with the remittance server 820.

[0139] Figure 9 is an operation flowchart of a method for providing a remittance service in conjunction with a remittance server using a messaging server according to one embodiment.

[0140] Referring to Figure 9, a method for providing a money transfer service in conjunction with a money transfer server using a messaging server that provides a messaging service according to one embodiment includes the steps of: receiving a money transfer request from a sender participating in an anonymous chat room as a first temporary profile to a second temporary profile that is participating in the anonymous chat room (Step S910); sending the money transfer request to the money transfer server based on whether the sender's account is eligible to send money (Step S920); receiving money transfer transaction information from the money transfer server that includes the identifier of the second temporary profile as the recipient (Step S930); and sending a money transfer notification message to the recipient's account mapped to the identifier of the second temporary profile based on the money transfer transaction information (Step S940). More specifically, the operations described with reference to Figure 9 correspond to a money transfer process executed by the messaging server, and as an example, the messaging server that is the entity executing the operations described with reference to Figure 9 corresponds to the messaging server 810 shown in Figure 8.

[0141] According to one embodiment, the sender's account may include an account generated when the sender subscribes to a messaging service, and the recipient's account may include an account generated when the recipient subscribes to a messaging service.

[0142] In one embodiment, the sender means a client that has requested a remittance from the messaging server, and the recipient means a client designated by the sender as the recipient of the requested remittance. The client includes a terminal logged into an account of a user who has subscribed to the services provided by the messaging server. The client can log into an account created by the messaging server upon subscription and use the remittance service provided by the messaging server in conjunction with the remittance server. As an example, the sender and recipient correspond to client 830 shown in Figure 8.

[0143] Step S910 according to one embodiment is the step of receiving a remittance request from a remitter who is participating in the anonymous chat room as a first temporary profile, to a second temporary profile that is participating in the anonymous chat room. As described above, the anonymous chat room is a chat room in which a participant is joined as a temporary profile, and a participant in the anonymous chat room is displayed as a temporary profile to other participants in the anonymous chat room, and can exchange messages within the anonymous chat room using the temporary profile.

[0144] A method for providing a money transfer service according to one embodiment further includes the steps of generating a temporary profile corresponding to each participant in an anonymous chat room and subordinate to the anonymous chat room, and mapping and storing the identifier of each participant's temporary profile to the account of each participant who has subscribed to the messaging service. The messaging server maps and stores the temporary profile of a user generated to join the anonymous chat room to the account of the user who has subscribed to the messaging service.

[0145] According to one embodiment, the messaging server recognizes the account of the user who sent the remittance request as the sender's account, and recognizes the account mapped to the identifier of the second temporary profile included in the remittance request as the recipient's account. Since the sender's client knows its own account, it can transmit the sender's account to the messaging server in the client's information that sent the remittance request.

[0146] According to one embodiment, the remittance request is received via an anonymous chat room.

[0147] For example, the money transfer interface may be provided to the user's terminal through an input that selects a money transfer button included in the menu tab of the anonymous chat room interface, or it may be provided to the user's terminal through an input that selects a money transfer button included in the temporary profile interface of an anonymous chat room participant. The money transfer interface is described below.

[0148] Step S920 according to one embodiment includes determining whether the account of the sender who sent the remittance request is eligible to remit, and if it is determined that the account is eligible, sending the remittance request to the remittance server. Remittance eligibility is determined by whether or not the sender's account is authenticated. For example, the sender's account is deemed eligible if it is an authenticated account, or if the sender's account holds a certificate of identity authentication issued by the messaging server or an authentication server linked to the messaging server. The authentication server is a server linked to the messaging server that performs authentication operations for remittance eligibility. This will be explained below.

[0149] According to one embodiment, step S920, which sends a remittance request, includes sending a remittance request to the remittance server, further based on whether the recipient's account mapped to the second temporary profile is eligible to receive. Eligibility is the qualification required to receive a remittance through an anonymous chat room, and more specifically, the qualification required to receive a remittance requested by designating a temporary profile, which is not account information, as the recipient. Eligibility is determined by whether the recipient's account is authenticated, for example, if the recipient's account is an authenticated account, or if the recipient's account holds a certificate of identity verification issued by the messaging server or an authentication server linked to the messaging server. If the messaging server has confirmed the remittance qualification of the sender's account and the eligibility of the recipient's account, it sends a remittance request to the remittance server.

[0150] According to one embodiment, the remittance process may verify the eligibility to remit, but it may not need to verify the eligibility to receive. Verification of eligibility to receive may be performed in the receiving process, which is executed when a receiving request is received from the recipient. The receiving process is described below.

[0151] For example, verification of eligibility to send and / or receive funds may be performed by the messaging server's authentication module. The authentication module is a module that authenticates the user accounts of the sender and / or recipient and determines whether the user accounts are authenticated. For example, the authentication module may authenticate the user accounts according to a predetermined method. Alternatively, for example, it may generate and store authentication information (e.g., a certificate) based on the authentication and provide it to the user's account, and then verify whether the user's account is an authenticated account based on the stored authentication information. The messaging server determines whether the sender's account is an account that is eligible to send funds based on the authentication results of the authentication module. For example, the authentication module may be a separate authentication server that works in conjunction with the messaging server.

[0152] According to one embodiment, a remittance request sent to the remittance server includes information necessary for the remittance received from the remitter. As described above, the remittance request includes a recipient identifier, a remittance amount, and a remitter identifier. The remitter identifier corresponds to the account of the remitter who sent the remittance request. The recipient identifier corresponds to the identifier of the second temporary profile designated as the recipient by the remitter, and the remittance amount corresponds to the amount entered by the remitter.

[0153] According to one embodiment, the remittance server can identify the account corresponding to the remitter's messaging server based on the account corresponding to the remitter's messaging server included in the remittance request. The remittance server may perform authentication on the identified account corresponding to the remitter's messaging server, in addition to the authentication procedure performed on the messaging server.

[0154] According to one embodiment, a remittance request may be sent directly from the remitter to the remittance server without going through a messaging server. For example, the remitter may request remittance eligibility from the messaging server and send a remittance request to the remittance server based on the eligibility obtained. Alternatively, for example, it may not be necessary to request remittance eligibility obtained from the messaging server to send a remittance request to the remittance server; the remittance server may determine remittance eligibility through authentication of the remitter's account and request the messaging server to verify the remittance eligibility of the remitter's account.

[0155] Step S930 according to one embodiment includes receiving remittance transaction information generated by the remittance server. The remittance server, having received the remittance request in step S920, generates remittance transaction information based on the received remittance request. The remittance server can generate remittance transaction information after performing the necessary procedures for performing the remittance transaction on the remittance server, such as a separate authentication procedure. If, as a result of performing the necessary procedures for performing the remittance transaction on the remittance server, it is determined that it is not appropriate to generate a remittance transaction, such as when the authentication of the remitter fails or when there are insufficient funds in the remitter's account for the remittance, the remittance server notifies the messaging server that it cannot perform the remittance transaction. This notification that it cannot perform the remittance transaction may be transmitted to the remitter and / or recipient via the messaging server.

[0156] According to one embodiment, the remittance transaction information includes a remittance transaction identifier corresponding to the remittance request and a recipient identifier corresponding to the remittance request. The remittance transaction identifier is an identifier assigned to each remittance transaction unit in order for the remittance server to distinguish and recognize the remittance transaction. As an example, the remittance transaction information may further include information regarding the validity period of the remittance transaction. The information regarding the validity period of the remittance transaction means the validity period during which the receipt of the remittance can be requested, and may be determined based on the time the remittance request was made or the time the remittance request was received by the messaging server or the remittance server. The information regarding the validity period of the remittance transaction may be generated by the messaging server and sent to the remittance server, or it may be generated by the remittance server.

[0157] According to one embodiment, in step S930, the remittance transaction information may be received along with a token for the remittance transaction. The token is data generated by the messaging server based on the recipient's temporary profile identifier and the recipient's account, and is information necessary to authenticate the remittance transaction. The messaging server can obtain the recipient and the recipient's account mapped to the identifier of the second temporary profile specified by the recipient, and can therefore generate a token based on the recipient's second temporary profile identifier and the recipient's account. The messaging server can generate a token corresponding to the user's temporary profile identifier and the user's account mapped thereto using a token generation logic. As an example, the messaging server may further generate a token based on additional information to identify the remittance transaction, such as the validity period of receipt information based on the time the remittance request was received. A token further generated based on the validity period of receipt information may also be used by the messaging server to verify the validity period of receipt of the remittance. A method for authenticating a remittance transaction using a token is described below. The token can be transmitted to the remittance server along with the remittance request in step S920, when the messaging server sends a remittance request to the remittance server, and can be transmitted to the recipient via the messaging server along with the remittance transaction information generated by the remittance server.

[0158] Step S940 according to one embodiment may include the step of obtaining the recipient's account corresponding to the temporary profile identifier included as the recipient identifier in the remittance transaction information, and sending a remittance notification message or remittance notification to the recipient's account. As described above, the messaging server stores mapping information between the temporary profile identifiers subordinate to the anonymous chat room and the user accounts to which the temporary profiles have been assigned. Based on the mapping information, the messaging server obtains the recipient's account corresponding to the temporary profile identifier included as the recipient identifier in the remittance transaction information. The messaging server can transmit the remittance transaction identifier and the token for the remittance transaction included in the remittance transaction information to the recipient via a remittance notification message.

[0159] According to one embodiment, the remittance notification message sent to the recipient may include a message notifying the recipient that the remittance has been made. For example, the remittance notification message sent to the recipient may include a message notifying the recipient that a certain amount of money has been remitted by the remitter. The remittance notification message sent to the recipient may include information about the first temporary profile as remitter information.

[0160] According to one embodiment, the remittance notification message sent to the recipient may include a receipt request function. For example, the remittance notification message sent to the recipient may include an interface object for receipt requests. The recipient requests receipt of the remittance based on the received remittance notification message, and the receipt process is initiated by the recipient's receipt request. The receipt process is described below.

[0161] A method for providing a remittance service according to one embodiment may further include the step of sending a remittance notification message to the remitter's account, which includes information about the second temporary profile as recipient information. The messaging server may also send a remittance notification message to the remitter's account based on the remittance transaction information received from the remittance server. The remittance notification message sent to the remitter includes a message notifying the recipient that the remittance has been delivered. The delivery of the remittance is distinguished from completion of receipt, and receipt may be completed when the recipient requests receipt of the delivered remittance and the receipt process is completed. For example, the remittance notification message sent to the remitter may include content notifying the recipient that a certain amount of money has been delivered, and the recipient information may be displayed as information about the second temporary profile.

[0162] A specific example of a remittance notification message sent to the recipient and the remitter according to one embodiment is described below.

[0163] Figure 10 is a flowchart illustrating the operation method of a client for using a remittance service provided in conjunction with a remittance server by a messaging server according to one embodiment.

[0164] Referring to Figure 10, the operation method of a client for using a money transfer service provided in conjunction with a money transfer server by a messaging server according to one embodiment includes the steps of: requesting the messaging server to grant eligibility to send money through the anonymous chat room in which the user is participating, based on whether or not the account that has joined the messaging service has been authenticated; selecting at least one of the temporary profiles participating in the anonymous chat room as the recipient; and requesting a transfer to the temporary profile selected as the recipient, in step S1030. More specifically, the operation described with reference to Figure 10 corresponds to a money transfer process executed by a client corresponding to the sender, and as an example, the client that is the entity executing the operation described with reference to Figure 10 corresponds to client 830 shown in Figure 8.

[0165] Step S1010 according to one embodiment includes a step of requesting the messaging server to grant eligibility to send money if the account subscribed to the client's messaging service is not authenticated. As described above, grant eligibility is the eligibility required to request a transfer through an anonymous chat room, and grant eligibility is determined based on whether or not authentication has been performed. Step S1010 according to one embodiment includes a step of requesting the messaging server to authenticate in order to obtain grant eligibility to send money. For example, a client can obtain grant eligibility to send money by performing identity authentication provided by the messaging server and registering authentication information with the messaging server, or by performing an authentication procedure to obtain a certificate issued by the messaging server or an authentication server linked to the messaging server. Based on the obtained grant eligibility to send money, the client can carry out the transfer process through an anonymous chat room.

[0166] Step S1020 according to one embodiment includes selecting at least one temporary profile as the recipient, which is a client whose eligibility to send money has been verified by the messaging server in step S1010 and is currently participating in an anonymous chat room.

[0167] Step S1030 according to one embodiment is a step of requesting a messaging server or a money transfer server to send money, specifying an anonymous profile identifier, which is not another user's account, as the recipient. In other words, a client whose eligibility to send money has been verified requests money from a recipient whose account information is unknown. For example, the money transfer request may be transmitted to the money transfer server via the messaging server, or it may be transmitted to the money transfer server immediately.

[0168] Step S1030 according to one embodiment includes a step of requesting a transfer to a selected temporary profile based on the eligibility of the participant corresponding to the temporary profile. The transfer request is sent based on the recipient's eligibility. The recipient's eligibility is determined based on whether the account mapped to the temporary profile selected as the recipient by the messaging server is authenticated. If the recipient's eligibility is confirmed, the transfer request can be sent to the transfer server or messaging server.

[0169] In one embodiment, a step may be performed prior to step S1020, in which the recipient is selected, to verify the eligibility of the anonymous chat room participants. Temporary profiles corresponding to participants whose eligibility has been verified are displayed in the list of temporary profiles that can be selected as recipients, while temporary profiles corresponding to participants whose eligibility has not been verified are restricted from being selected as recipients.

[0170] According to one embodiment, unlike step S1030, the remittance request may be sent without verifying the recipient's eligibility to receive the remittance, and the recipient's eligibility to receive the remittance is determined when the recipient requests to receive the remittance.

[0171] Figure 11 illustrates an overall scenario of a remittance process according to one embodiment.

[0172] Referring to Figure 11, the sender is the client that requested the remittance, and the recipient is the client designated by the sender to receive the remittance. For example, the sender and recipient correspond to client 830 shown in Figure 8, the messaging server corresponds to messaging server 810 shown in Figure 8, and the remittance server corresponds to remittance server 820 shown in Figure 8.

[0173] Referring to Figure 11, the sender requests a payment from the messaging server (S1103), and the payment request includes the payment amount and the identifier of the temporary profile of another user participating in the anonymous chat room. The sender may also request eligibility to send the payment from the messaging server in advance of the payment request (S1103) (S1101), and in response to the eligibility request, the messaging server authenticates the sender's account and generates authentication information (S1102).

[0174] For example, a messaging server may respond to a remittance request by verifying the sender's eligibility to remit and / or the recipient's eligibility to receive (S1104). For example, the messaging server may verify only the sender's eligibility to remit and not the recipient's eligibility during the remittance process.

[0175] As described above, the authentication operation for verifying eligibility to send and receive funds may be performed by the authentication module of the messaging server or by an authentication server linked to the messaging server. When the authentication operation is performed by an authentication server linked to the messaging server, the eligibility request for sending funds (S1101) is sent to the authentication server, and the authentication server generates authentication information for sending funds (S1102). The eligibility request for sending funds (S1101) may be transmitted to the authentication server via the messaging server or directly to the authentication server. In addition, the authentication server may perform a verification of eligibility to send funds and / or receive funds (S1104) based on the eligibility request for sending funds (S1103), and the verified result may be transmitted to the messaging server.

[0176] For example, if the messaging server's eligibility to send a payment is verified, it transmits a payment request to the payment server (S1105). The payment request includes the account of the sender who sent the payment request, the identifier of the temporary profile corresponding to the recipient specified by the sender, and the amount to be sent. As described above, when transmitting the payment request to the payment server (S1105), the messaging server may also transmit a token relating to the payment transaction.

[0177] As an example, a remittance server that receives a remittance request from a messaging server generates remittance transaction information based on the remittance request (S1107). As described above, the remittance transaction information corresponding to the remittance request includes a recipient identifier and a remittance transaction identifier. The recipient identifier includes the identifier of the recipient's temporary profile included in the remittance request. As an example, a remittance server that receives a remittance request from a messaging server may perform a remitter authentication procedure separately from the remitter eligibility verification procedure at the messaging server to authenticate the remitter (S1106), and if the remitter is authenticated, generate remittance transaction information (S1107).

[0178] For example, the remittance transaction information generated by the remittance server is transmitted to the messaging server along with the token corresponding to the remittance transaction information (S1108). Based on the remittance transaction information, the messaging server can retrieve the recipient's account mapped to the temporary profile identifier included as the recipient identifier in the remittance transaction information (S1109).

[0179] As an example, the messaging server sends a remittance notification message to the acquired recipient account (S1110). The remittance notification message includes remittance transaction information and a token for the remittance transaction. As an example, the messaging server may also send a remittance notification message to the sender's account to notify them that the remittance has been delivered to the recipient (S1111).

[0180] Figures 12A and 12B show examples of remittance notification messages according to one embodiment.

[0181] Referring to Figure 12A, the remittance notification message 1210 is sent to the recipient's account via a chat room. For example, the chat room to which the remittance notification message 1210 is sent is a chat room between the recipient's account and an account related to the remittance server, and the chat room with the account related to the remittance server is a type of chat room for transmitting informational messages generated with the account related to the remittance server as the sender. Also, for example, the chat room to which the remittance notification message 1210 is sent may be a 1:1 anonymous chat room between the sender and the recipient. If the remittance request occurs in an anonymous chat room that includes participants other than the recipient and the sender, a 1:1 anonymous chat room including the recipient and the sender is created, and the remittance notification message 1210 may be sent and received via the created 1:1 anonymous chat room. The temporary profiles of the recipient and sender in the newly created 1:1 anonymous chat room may be the same as the temporary profiles in the anonymous chat room where the remittance request occurred. Alternatively, if the remittance request occurs in a 1:1 anonymous chat room involving both the recipient and the remitter, the remittance notification message 1210 may be sent and received through that anonymous chat room.

[0182] According to one embodiment, the remittance notification message 1210 may include content that notifies the recipient that a certain amount of money has been sent by the remitter. For example, the remitter information included in the remittance notification message 1210 may include the name (e.g., "Kaka") set in the temporary profile subordinate to the anonymous chat room where the remittance request originated. As described above, the name set in the temporary profile may be an arbitrarily set name or alias corresponding to the temporary profile which is not real name information included in the remitter's account. Also, for example, the remittance notification message 1210 may include information about the anonymous chat room where the remittance request originated. The information about the anonymous chat room may include the name (e.g., "AAA") set in the anonymous chat room in which the recipient and the remitter participate.

[0183] According to one embodiment, the remittance notification message 1210 includes an interface object 1211 for a receipt request. The recipient can send a receipt request to the remittance server or messaging server by selecting the interface object 1211 included in the remittance notification message 1210. The interface object 1211 corresponds to an object that includes the function of sending a receipt request to the messaging server or remittance server, which includes a remittance transaction identifier and a token for the remittance transaction corresponding to the remittance request, via a selection input.

[0184] Referring to Figure 12B, the remittance notification message 1220 is sent to the remitter's account via a chat room. For example, the chat room to which the remittance notification message 1220 is sent is a chat room between the remitter's account and an account related to the remittance server, and the chat room with the account related to the remittance server is a type of chat room for transmitting informational messages generated with the account related to the remittance server as the sender. As mentioned above, the chat room to which the remittance notification message 1220 is sent may also be a 1:1 anonymous chat room between the remitter and the recipient.

[0185] According to one embodiment, the remittance notification message 1220 includes content that notifies the recipient that a certain amount of money has been sent. For example, the recipient information included in the remittance notification message 1220 may include the name (e.g., "Melody") set in a temporary profile subordinate to the anonymous chat room where the recipient's remittance request originated. As described above, the name set in the temporary profile corresponds to a temporary profile that is not real name information included in the recipient's account, and is an arbitrarily set name or alias.

[0186] According to one embodiment, the remittance notification message 1220 includes an interface object 1221 for providing detailed information about the remittance request. The remitter can request a page displaying detailed information about the remittance request from the messaging server or the remittance server by selecting the interface object 1221 included in the remittance notification message 1220.

[0187] Figure 13 is an operation flowchart of a method for providing a remittance service in conjunction with a remittance server using a messaging server according to one embodiment.

[0188] Referring to Figure 13, a method for providing a money transfer service in conjunction with a money transfer server using a messaging server that provides a messaging service according to one embodiment includes the steps of: receiving a recipient verification request from the money transfer server corresponding to a request to receive a money transfer via an anonymous chat room; verifying from the money transfer server whether the account that requested the money transfer to be received is the same user as the recipient identifier included in the receipt request; and sending the verification result to the money transfer server in the steps of:

[0189] Step S1310 according to one embodiment includes receiving a verification request from the remittance server to determine whether the recipient identifier included in the receipt request corresponds to the account that requested the receipt. The recipient identifier included in the receipt request is the recipient identifier included in the remittance transaction information and corresponds to the temporary profile identifier specified by the remitter at the time of the remittance request. Since the remittance server does not store mapping information between the account that requested the receipt and the temporary profile identifier corresponding to the recipient identifier, it cannot verify whether the account that requested the receipt and the temporary profile identifier corresponding to the recipient identifier are the same user, and may request verification from the messaging server.

[0190] According to one embodiment, the recipient requests receipt from a messaging server or remittance server via a remittance notification message. The receipt request includes remittance transaction information and a token for the remittance transaction included in the remittance notification message. For example, the receipt request includes a remittance transaction identifier corresponding to the remittance request, a recipient identifier corresponding to the remittance request, and a token for the remittance transaction corresponding to the remittance request. For example, referring to Figure 12A, a remittance notification message sent to a recipient account may include an interface object 1211 for the receipt request, requesting receipt of the remittance from the messaging server or remittance server as input to select the interface object 1211. When the interface object selection input is received, a receipt request including the remittance transaction information included in the remittance notification message may be sent to the remittance server or messaging server.

[0191] According to one embodiment, a receipt request sent to the remittance server may also be sent from the recipient to the remittance server via a messaging server, or from the recipient to the remittance server. If sent via a messaging server, the messaging server can verify the eligibility of the recipient who sent the receipt request and can transmit the receipt request to the remittance server based on the eligibility. In other words, the method of providing a remittance service may further include the steps of receiving a receipt request from the recipient's account based on a remittance notification message sent to the recipient's account, and transmitting the receipt request to the remittance server based on whether the recipient's account is eligible to receive.

[0192] Step S1320 according to one embodiment includes verifying whether the account that requested the remittance server to receive the remittance is the same user as the recipient identifier included in the remittance request, based on the mapping information between the temporary profile identifier of the participant subordinate to the anonymous chat room and the participant's account. As described above, the messaging server can map and store the temporary profile identifier of the participant subordinate to the anonymous chat room and the user's account. The messaging server can verify the recipient by retrieving the account mapped to the recipient identifier based on the mapping information between the temporary profile identifier and the account, and by determining whether the retrieved account and the account that received the remittance request are the same user.

[0193] Step S1320 according to one embodiment further includes the step of verifying a remittance transaction based on a token for the remittance transaction. The token for the remittance transaction may be included in a receipt request sent to the remittance server, or it may be transmitted from the remittance server to the messaging server. The messaging server obtains an account mapped to a recipient identifier included in the receipt request based on mapping information. The messaging server can verify the remittance transaction by generating a token based on the recipient identifier and the obtained account, and comparing whether the generated token is identical to the token received from the remittance server.

[0194] Step S1320 according to one embodiment may further include a step of verifying the remittance transaction based on the validity period for receiving the remittance. As described above, the token is generated based further on the information of the validity period for receiving, and the messaging server can verify whether the remittance transaction is valid by checking the validity period for receiving in the process of verifying the remittance transaction based on the token.

[0195] In one embodiment, step S1330 includes providing the recipient verification result of step S1320 to the remittance server. In step S1330, the result sent to the remittance server may include whether or not the account that requested receipt is the recipient included in the remittance transaction information of the receipt request, and does not provide the remittance server with mapping information between temporary profile identifiers and accounts.

[0196] According to one embodiment, the remittance server can process a receipt request based on the verification result. Processing a receipt request means processing a remittance transaction that sends the remittance amount from the remitter's account to the recipient's account. For example, the remittance transaction information may further include information about the validity period for receipt of the remittance, and the remittance server can decide whether or not to process the remittance transaction based on the validity period for receipt included in the remittance transaction information. The remittance request can be processed if the receipt is requested within the validity period for receipt included in the remittance transaction information. On the other hand, if the validity period has expired, it is determined to be an invalid remittance transaction, and the receipt request cannot be processed. If the receipt request has not been processed, the remittance server can be notified that the remittance transaction has not been processed, and the messaging server can notify the recipient and / or remitter's accounts in the form of a message that the remittance transaction has not been processed. The remittance server can send the result of processing the receipt request to the messaging server, and the messaging server can send a receipt notification message to the recipient and / or remitter's accounts. The receipt notification message includes a message notifying that the receipt of the remittance has been completed.

[0197] As an example, a method for providing a remittance service according to one embodiment may further include the steps of receiving the processing result of a receipt request from a remittance server and responding to the processing result by sending a receipt notification message to the account that requested the receipt.

[0198] Furthermore, as an example, a method for providing a remittance service according to one embodiment may further include the steps of receiving the processing result of a receipt request from a remittance server and, in response to the processing result, sending a receipt notification message to the account that requested the remittance.

[0199] Figure 14 illustrates an overall scenario of the receiving process for a money transfer service according to one embodiment.

[0200] Referring to Figure 14, the sender is the client that requested the transfer, and the recipient is the client designated by the sender to receive the transfer. The sender and recipient correspond to client 830 shown in Figure 8, the messaging server corresponds to messaging server 810 shown in Figure 8, and the transfer server corresponds to transfer server 820. As an example, the receiving process shown in Figure 14 is a process that is executed after the transfer process shown in Figure 11.

[0201] Referring to Figure 14, the recipient requests receipt from the messaging server via a remittance notification message (S1401). The receipt request includes the remittance transaction information contained in the remittance notification message.

[0202] As an example, the messaging server responds to a received receipt request by verifying the recipient's eligibility (S1402). As described above, the verification of the recipient's eligibility may be performed in response to a remittance request received from the remitter in the remittance process. The verification of eligibility may also be performed separately in the receiving process from the remittance process, and may be omitted in the receiving process if eligibility verification has been performed in the remittance process.

[0203] For example, if the messaging server's eligibility to receive is confirmed, it transmits a request to the remittance server (S1403). The request may include the recipient's account that sent the request, the recipient identifier and remittance transaction identifier included in the remittance transaction information, and may further include a token for the remittance transaction.

[0204] Figure 14 illustrates an example where a receipt request is transmitted to the remittance server via a messaging server; however, the receipt request may also be sent directly to the remittance server without going through a messaging server.

[0205] For example, when a remittance server receives a receipt request from a messaging server, it requests the messaging server to verify the recipient to determine whether the recipient identifier included in the receipt request and the account that requested the receipt belong to the same user (S1405). Alternatively, when a remittance server receives a receipt request from a messaging server, it may perform a recipient authentication procedure separately from the recipient eligibility verification procedure at the messaging server to authenticate the recipient (S1404), and if the recipient is authenticated, it may request recipient verification from the messaging server (S1405).

[0206] For example, the messaging server can verify the recipient by obtaining the account mapped to the temporary profile identifier, which is the recipient identifier included in the receipt request, and determining whether the obtained account and the account that requested the receipt are the same user. If the verification result shows that the users are the same, the server can send a verification result indicating that the recipient is valid to the remittance server (S1406). If the users are not the same, the server can send a verification result indicating that the recipient is invalid.

[0207] For example, if the remittance server receives a verification result that the recipient is valid, it can process the receipt request (S1407) and send the processing result of the receipt request to the messaging server (S1408).

[0208] For example, upon receiving the processing result of the receipt request (S1408), the messaging server sends a receipt notification message to the recipient's account and / or the sender's account (S1409, S1410).

[0209] Figures 15A and 15B show examples of receipt notification messages according to one embodiment.

[0210] Referring to Figure 15A, the receipt notification message 1510 is sent to the recipient's account via a chat room. For example, the chat room to which the receipt notification message 1510 is sent is a chat room between the recipient's account and an account related to the remittance server, and the chat room with the account related to the remittance server is a type of chat room for transmitting informational messages generated with the account related to the remittance server as the sender. As mentioned above, the chat room to which the receipt notification message 1510 is sent may also be a 1:1 anonymous chat room between the sender and the recipient.

[0211] According to one embodiment, the receipt notification message 1510 includes content that notifies the recipient that a certain amount of money sent by the sender has been received. For example, the sender information included in the receipt notification message 1510 includes the name (e.g., "Kaka") set in a temporary profile subordinate to the anonymous chat room where the sender's remittance request originated. As described above, the name set in the temporary profile corresponds to a name or alias arbitrarily set in a temporary profile that is not real name information included in the sender's account.

[0212] According to one embodiment, the recipient information included in the receipt notification message 1510 may be displayed in the recipient's account as real name information (e.g., "Hong Gil-dong") or in a temporary profile, depending on the type of chat room to which the receipt notification message 1510 is sent. For example, if the receipt notification message 1510 is sent via a chat room with an account related to the remittance server, the recipient information included in the receipt notification message 1510 includes the recipient's account as real name information (e.g., "Hong Gil-dong"). Since there is no need to display the recipient's account in a temporary profile in a receipt notification message sent to the recipient's account, the recipient information is displayed in the recipient's account information. On the other hand, if the receipt notification message 1510 is sent via a 1:1 anonymous chat room between the remitter and the recipient, the recipient information included in the receipt notification message 1510 is shown in the recipient's temporary profile in order to prevent the recipient's real name information from being exposed to the other party.

[0213] Furthermore, as an example, the receipt notification message 1510 may include information about the anonymous chat room where the remittance request originated. The information about the anonymous chat room may include the name set for the anonymous chat room in which the recipient and sender participate (for example, "AAA").

[0214] According to one embodiment, the receipt notification message 1510 includes an interface object 1511 for providing detailed information about the remittance transaction. The recipient can request a page displaying detailed information about the remittance transaction from the messaging server or the remittance server by selecting the interface object 1511 included in the receipt notification message 1510.

[0215] Referring to Figure 15B, the receipt notification message 1520 is sent to the sender's account via a chat room. For example, the chat room to which the receipt notification message 1520 is sent corresponds to a chat room between the sender's account and an account related to the remittance server, and the chat room with the account related to the remittance server corresponds to a type of chat room for transmitting informational messages generated with the remittance server account as the sender. As mentioned above, the chat room to which the receipt notification message 1510 is sent may also be a 1:1 anonymous chat room between the sender and the recipient.

[0216] According to one embodiment, the receipt notification message 1520 includes content that notifies the recipient that a certain amount of money sent by the sender has been received. For example, the recipient information included in the receipt notification message 1520 may include the name (e.g., "Melody") set in a temporary profile subordinate to the anonymous chat room where the sender's transfer request originated. As described above, the name set in the temporary profile may be a name or alias arbitrarily set in response to a temporary profile that is not real name information included in the recipient's account.

[0217] According to one embodiment, the sender's information included in the receipt notification message 1520 may be displayed in the sender's account's real name information (e.g., "Kim Kaka") or in a temporary profile, depending on the type of chat room to which the receipt notification message 1520 is sent. For example, when the receipt notification message 1520 is sent via a chat room with an account related to the remittance server, the sender's information included in the receipt notification message 1520 includes the sender's account's real name information (e.g., "Kim Kaka"). Since there is no need to display the sender's account in a temporary profile in a receipt notification message sent to the sender's account, the sender's information is displayed in the sender's account information. On the other hand, when the receipt notification message 1520 is sent via a 1:1 anonymous chat room between the sender and the recipient, the sender's information included in the receipt notification message 1520 is displayed in the sender's temporary profile in order to avoid exposing the sender's real name information to the recipient.

[0218] Furthermore, as an example, the receipt notification message 1510 may include information about the anonymous chat room where the remittance request originated. The information about the anonymous chat room may include the name set for the anonymous chat room in which the recipient and sender participate (for example, "AAA").

[0219] According to one embodiment, the receipt notification message 1520 includes an interface object 1521 for providing detailed information about the remittance transaction. The remitter can request a page displaying detailed information about the remittance transaction from the messaging server or the remittance server by selecting the interface object 1521 included in the receipt notification message 1510.

[0220] Figure 16 is an illustrative diagram of the hardware configuration of a remittance system according to one embodiment.

[0221] Referring to Figure 16, a remittance system according to one embodiment includes a messaging server 810, a remittance server 820, and a client 830 connected via a network 1610. For example, the remittance system shown in Figure 16 corresponds to the remittance system shown in Figure 8, and the messaging server 810, remittance server 820, and client 830 correspond to the messaging server 810, remittance server 820, and client 830 shown in Figure 8, respectively. For example, although not shown in Figure 16, the remittance system may further include an authentication server, which may perform authentication operations for verifying remittance and receipt eligibility in conjunction with the messaging server 810.

[0222] In one embodiment, the client 830 may be a mobile terminal embodied in a computer device. For example, the client 830 can communicate with the messaging server 810, the remittance server 820, and / or other electronic devices via the network 1610 using wireless or wired communication methods.

[0223] In one embodiment, the messaging server 810 and the remittance server 820 may be implemented as a computer device or multiple computer devices that communicate with a client 830 and / or other servers via the network 1610 to provide instructions, code, files, content, services, etc. The communication method is not limited and may include the network 1610, a communication method that utilizes a communication network (e.g., a mobile communication network, wired internet, wireless internet, broadcast network), or a short-range wireless communication method between devices. For example, the network 1610 may include one or more arbitrary networks such as a PAN (personal area network), LAN (local area network), CAN (campus area network), MAN (metropolitan area network), WAN (wide area network), BBN (broadband network), or the Internet.

[0224] In one embodiment, the messaging server 810 can provide a client 830 connected via the network 1610 with files for application installation. In this case, the client 830 installs an application (e.g., an instant messaging app) using the files provided by the messaging server 810. Furthermore, depending on the control of the operating system (OS) and at least one program (e.g., a browser or an installed application) included in the client 830, the client may connect to the messaging server 810 and receive services and content provided by the messaging server 810. For example, if the client 830 sends a service request message to the messaging server 810 via the network 1610 in response to application control, the messaging server 810 sends a code corresponding to the service request message to the client 830, and the client 830 can provide content to the user by configuring and displaying a screen based on the code in response to application control.

[0225] According to one embodiment, the client 830 and messaging server 810 include memory 1611, 1621, processor 1613, 1623, communication modules 1615, 1625, and input / output interfaces 1617, 1627.

[0226] In one embodiment, processors 1613 and 1623 can perform at least one of the operations described above via Figures 8 to 15B. For example, processor 1613 may perform at least one operation of a client 830 for using a remittance service provided in conjunction with a remittance server 820 by the messaging server 810 as described above, with reference to Figures 10 and 11, and processor 1623 may perform at least one operation performed by the messaging server 810 that provides remittance services in conjunction with the remittance server 820 as described above, with reference to Figures 9, 11, 13, and 14. Processors 1613 and 1623 can be configured to process computer program instructions by performing basic arithmetic, logic, and input / output operations. Instructions are provided to processors 1613 and 1623 by memory 1611 and 1621 or by communication modules 1615 and 1625.

[0227] The memories 1611 and 1621 may be volatile or non-volatile memory as a recording medium readable by a computer. In one embodiment, the memories 1611 and 1621 store information related to the money transfer service described above, as shown in Figures 8 to 15B. For example, memory 1621 can store accounts and account authentication information generated in response to a subscribed user, and can store mapping information between identifiers of temporary profiles subordinate to anonymous chat rooms and accounts of users to which temporary profiles have been assigned.

[0228] In one embodiment, memory 1611 contains code for an instant messaging application that is installed on and driven by a file provided by the messaging server 810 via the network 1610.

[0229] In one embodiment, the memory 1621 stores a program that embodies the operations for providing a remittance service, which are executed in the messaging server 810 and the remittance server 820 as described above, as shown in Figures 8 to 15B.

[0230] One embodiment of the communication modules 1615 and 1625 provides functions for a client 830, a messaging server 810, and a remittance server 820 to communicate with each other via a network 1610, and can also provide functions for communicating with other electronic devices or other servers.

[0231] For example, a request generated by program code relating to an instant messaging application stored in a recording device such as memory 1611 by the processor 1613 of the client 830 may be sent to the messaging server 810 via the network 1610 in accordance with the control of the communication module 1615.

[0232] For example, control signals, instructions, content, files, etc., provided in response to the control of the processor 1623 of the messaging server 810 may be received by the client 830 via the communication module 1615 of the client 830 through the communication module 1625 and the network 1610, or received by the remittance server 820.

[0233] The input / output interfaces 1617 and 1627 may also be means for interfacing with the input / output device 1619. For example, the input device may include a device such as a keyboard or mouse, and the output device may include a device such as a display for displaying the application's communication session. In a different example, the input / output interface 1617 may be means for interfacing with a device that combines input and output functions into one, such as a touchscreen. In a more specific example, the processor 1613 of the client 830 processes instructions for a computer program loaded into memory 1611, and a service screen or content consisting of data provided by the messaging server 810 is displayed on the display via the input / output interface 1617. Input received from the user through the input / output device 1619 may be provided via the input / output interface 1617 in a form that can be processed by the processor 1613 of the client 830.

[0234] According to one embodiment, the client 830 and the messaging server 810 may include other components not shown in Figure 16. For example, the client 830 may be implemented to include at least some of the input / output devices 1619 described above, or it may further include other components such as a transceiver, a GPS (Global Positioning System) module, a camera, various sensors, a database, etc.

[0235] The embodiments described above are embodied in hardware components, software components, or combinations of hardware and software components. For example, the devices and components described in these embodiments are embodied using one or more general-purpose or special-purpose computers, such as a processor, controller, ALU (arithmetic logic unit), digital signal processor, microcomputer, FPA (field programmable array), PLU (programmable logic unit), microprocessor, or different devices that execute and respond to instructions. The processing device executes an operating system (OS) and one or more software applications that run on the OS. The processing device also accesses, stores, manipulates, processes, and generates data in response to the execution of the software. For convenience of understanding, the processing device may sometimes be described as being used as a single unit, but a person with ordinary skill in the art will understand that the processing device includes multiple processing elements and / or multiple types of processing elements. For example, the processing device includes multiple processors or one processor and one controller. Other processing configurations are also possible, such as a parallel processor.

[0236] Software includes computer programs, code, instructions, or a combination of one or more of these, which can configure a processing unit to operate as desired, or instruct the processing unit independently or in combination. Software and / or data can be permanently or temporarily embodied in any type of machine, component, physical device, virtual device, computer storage medium or device, or transmitted signal wave, for interpretation by a processing unit or for providing instructions or data to a processing unit. Software can be distributed across a network of computer systems and stored and executed in a distributed manner. Software and data can be stored on a recording medium readable by one or more computers.

[0237] The method according to this embodiment is embodied in the form of program instructions that are implemented via various computer means and recorded on a computer-readable recording medium. The recording medium includes program instructions, data files, data structures, etc., individually or in combination. The recording medium and program instructions may be specifically designed and configured for the purposes of the present invention, or they may be known and usable by those skilled in the art who have technology in the field of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tapes, optical recording media such as CD-ROMs and DVDs, magneto-optical media such as floppy disks, and hardware devices specifically configured to store and execute program instructions, such as ROMs, RAMs, and flash memory. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code executed by a computer using an interpreter or the like.

[0238] The hardware device described above may be configured to operate as one or more software modules to perform the operations shown in the present invention, and vice versa.

[0239] As described above, although embodiments have been illustrated with limited drawings, a person with ordinary skill in the art can apply various technical modifications and variations based on the above description. For example, the described technique may be performed in a different order than described, and / or the described system, structure, apparatus, circuit, and other components may be combined or assembled in a different manner than described, or replaced or substituted by other components or equivalents, and still achieve the desired results.

[0240] Therefore, other embodiments, other embodiments, and claims equivalent to those described below also fall within the scope of the claims.

Claims

1. A method for operating a terminal that uses a messaging service, The steps include displaying a remittance interface linked to the messaging service, The steps include: displaying information about the temporary profile of the recipient of the remittance via the aforementioned remittance interface; The steps include sending a remittance request to the server to the recipient corresponding to the displayed temporary profile, The steps include: displaying the result information of the aforementioned remittance request, Includes, The recipient's account information mapped to the temporary profile is generated when the recipient subscribes to the messaging service and is not displayed in the remittance interface. The method wherein the recipient's temporary profile is one of one or more temporary profiles generated in accordance with the recipient's account information for the purpose of using at least a portion of the messaging service.

2. The aforementioned server, A messaging server that provides the aforementioned messaging service, A remittance server that provides remittance services in conjunction with the messaging server, The method according to claim 1, comprising at least one of the following.

3. The step of displaying the aforementioned remittance interface is: The steps include selecting the recipient via a chat room joined using a temporary profile, The steps include: displaying the remittance interface for a remittance request to the selected recipient; The method according to claim 1, including the method described in claim 1.

4. The step of displaying the aforementioned remittance interface is: Steps to display a temporary profile view of another user account, The steps include displaying the remittance interface via the temporary profile view of the other user account, Includes, The method according to claim 1, wherein the recipient is determined to be the temporary profile of the other user account.

5. The step of displaying the remittance interface linked to the temporary profile view of the other user account is: If the eligibility of the other user account is confirmed, the step of displaying the remittance interface via the temporary profile view of the other user account, If the eligibility of the other user account mentioned above has not been verified, the step of restricting the transfer function based on the transfer interface, The method according to claim 4, including the method described in claim 4.

6. The method according to claim 1, wherein the step of displaying the remittance interface includes the step of separately displaying information for a first type of temporary profile corresponding to an account whose eligibility to receive has been verified via the remittance interface, and information for a second type of temporary profile corresponding to an account whose eligibility to receive has not been verified.

7. The method according to claim 1, wherein the step of displaying the remittance interface includes the step of displaying the remittance interface that allows input to select a first type temporary profile corresponding to an account whose eligibility to receive has been verified as the recipient.

8. The method according to claim 1, further comprising the step of transmitting authentication information for obtaining eligibility to send money to the server for an account corresponding to the terminal.

9. The method according to claim 1, wherein the result information of the remittance request includes at least one of the following: information relating to the temporary profile of the remitter who initiated the remittance request and information relating to the temporary profile of the recipient.

10. The method according to claim 1, wherein the step of displaying the result information of the remittance request includes the step of displaying a remittance failure notice if the recipient's account is not verified as eligible to receive the remittance and the remittance fails.

11. A method for operating a terminal that uses a messaging service, The steps include receiving user input for a remittance request to a recipient using a temporary profile, The steps include generating a signal for the remittance request, which includes the recipient's temporary profile information, The steps include outputting the result information of the aforementioned remittance request, Includes, The aforementioned result information is, The recipient information includes the information of the temporary profile, but does not include the recipient's account information mapped to the temporary profile. The recipient's account information is generated when the recipient subscribes to the messaging service. The method wherein the recipient's temporary profile is one of one or more temporary profiles generated in accordance with the recipient's account information for the purpose of using at least a portion of the messaging service.

12. The method according to claim 11, wherein the remittance transaction corresponding to the remittance request is processed by a remittance server linked to the messaging service.

13. The method according to claim 12, wherein the messaging server providing the messaging service transmits the recipient's account information mapped to the temporary profile to the remittance server.

14. The method according to claim 11, wherein the step of receiving user input includes receiving the user input for the remittance request via the interface of a chat room in which the recipient participates as the temporary profile.

15. The method according to claim 14, wherein the step of outputting the result information of the remittance request includes the step of displaying a message containing the result information of the remittance request in the chat room.

16. The method according to claim 11, wherein the step of receiving user input includes receiving the user input for the remittance request via the recipient's temporary profile view.

17. The method according to claim 11, wherein the result information of the remittance request further includes information relating to the temporary profile of the remitter who initiated the remittance request.

18. A method for providing a money transfer service on a server that provides a messaging service, The steps include identifying account information mapped to a second temporary profile of the recipient of the remittance included in the aforementioned remittance request, The steps include obtaining the result information of the remittance request based on the identified account information, The steps include: transmitting the aforementioned result information to the remitter's terminal corresponding to the remittance request; Includes, The aforementioned result information is, The recipient information includes the information of the second temporary profile, but does not include the recipient's account information mapped to the second temporary profile. The recipient's account information is generated when the recipient subscribes to the messaging service. The method wherein the second temporary profile is one of one or more temporary profiles generated in accordance with the recipient's account information for the use of at least a portion of the messaging service.

19. The method of claim 18, further comprising the step of receiving a remittance request from the remitter participating in the anonymous chat room for the second temporary profile participating in the anonymous chat room.

20. The method according to claim 19, wherein the remitter participates in the anonymous chat room using the first temporary profile.

21. The method according to claim 18, wherein the recipient's terminal displays a first temporary profile corresponding to the sender, and does not display the sender's account information mapped to the first temporary profile.

22. The method of claim 18, further comprising the step of receiving a remittance request from the remitter for the second temporary profile via the second temporary profile view provided to the remitter's terminal.

23. The method of claim 18, further comprising the step of sending the remittance request to a remittance server linked to the server based on the account information mapped to the second temporary profile.

24. A computer program stored on a computer-readable medium, which, in combination with hardware, causes to perform the method according to any one of claims 1 to 23.

25. A device that uses a messaging service, One or more processors, Memory for storing instructions, Includes, When the instruction is executed by one or more processors, the terminal will: The steps include: displaying a remittance interface linked to the messaging service; The steps include: displaying information about the temporary profile of the recipient of the remittance via the aforementioned remittance interface; The steps include sending a remittance request to the server for the recipient corresponding to the displayed temporary profile, The step of displaying the result information of the aforementioned remittance request, Execute, The recipient's account information mapped to the temporary profile is not displayed in the remittance interface. The recipient's account information is generated when the recipient subscribes to the messaging service. The recipient's temporary profile is one of one or more temporary profiles generated in accordance with the recipient's account information for the purpose of using at least a portion of the messaging service, on a device.

26. A device that uses a messaging service, One or more processors, Memory for storing instructions, Includes, When the instruction is executed by one or more processors, the terminal will: The steps include receiving user input for a remittance request to a recipient using a temporary profile, A step in which a signal for the remittance request is generated, including the information of the recipient's temporary profile, The steps include: outputting the result information of the aforementioned remittance request, Includes, The aforementioned result information includes the information of the temporary profile as the recipient's information, but does not include the recipient's account information mapped to the temporary profile. The recipient's account information is generated when the recipient subscribes to the messaging service. The recipient's temporary profile is one of one or more temporary profiles generated in accordance with the recipient's account information for the purpose of using at least a portion of the messaging service, on a device.

27. 。 It is a server, One or more processors, Memory for storing instructions, Includes, When the instruction is executed by one or more processors, the server will: The steps include providing account information mapped to the second temporary profile of the recipient of the remittance included in the remittance request, The steps include obtaining result information of the remittance request based on the identified account information, The result information is transmitted to the remitter's terminal corresponding to the remittance request, Includes, The aforementioned result information includes the information of the second temporary profile as the recipient's information, but does not include the recipient's account information mapped to the second temporary profile. The recipient's account information is generated when the recipient subscribes to the messaging service. The recipient's temporary profile is one of one or more temporary profiles generated in accordance with the recipient's account information for the purpose of using at least a portion of the messaging service, on the server.

Images