Method and apparatus for remittance service

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 money transfer service, and in particular to a server providing the money transfer service and a client using the money transfer service. [Background technology]

[0002] Fintech (Financial Technology) is a compound word of finance and technology, and refers to financial services and industries based on information technology such as mobile, big data, and SNS. Various financial services that are differentiated from existing financial services have emerged using Fintech technology, such as mobile banking and app cards. As Fintech services have spread recently, online remittance services have become more popular as banking operations such as transfers and deposits can be handled directly using a computer or mobile phone without visiting a bank. Previously, in order to use online remittance services, it was necessary to use an official certificate or exchange personal information such as the recipient's name, bank name, and account number. However, recently, technologies have been developed to provide convenient online remittance services, such as simplifying the authentication process and the information required for remittance transactions. Summary of the Invention [Problem to be solved by the invention]

[0003] An object of the present invention is to provide a technique that enables money transfer between participants in an anonymous chat room without revealing each other's account information. However, the technical issues are not limited to the above-mentioned technical issues, and further technical issues may exist. [Means for solving the problem]

[0004] According to one aspect, a method of operating a server providing a remittance service includes the steps of receiving a remittance request for a second temporary profile participating in an anonymous chat room provided by the server from a remitter participating in the anonymous chat room as a first temporary profile, confirming the remittance qualification of the remitter's account based on authentication information of the remitter's account, generating remittance transaction information for remitting an amount corresponding to the remittance request to a recipient's account corresponding to the second temporary profile based on the remittance qualification of the remitter's account, and sending a remittance notification including information about the first temporary profile as remitter information to the recipient's account based on the remittance transaction information.

[0005] The step of generating the remittance transaction information may include a step of generating the remittance transaction information if the remitter's account is confirmed as being eligible for remittance, and a step of requesting the remitter to perform personal authentication to obtain remittance qualification if the remitter's account is not confirmed as being eligible for remittance.

[0006] The step of generating the remittance transaction information may include the steps of verifying eligibility of the payee account based on authentication information of the payee account, and generating the remittance transaction information further based on eligibility of the payee account.

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

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

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

[0010] The step of providing the remittance interface may include a step of separately displaying a first type of temporary profile corresponding to an account including authentication information and a second type of temporary profile corresponding to an account not including authentication information among the anonymous profiles participating in the anonymous chat room.

[0011] The step of providing the money transfer interface may include deactivating an input to select as a recipient a second type temporary profile corresponding to an account that does not include authentication information among the anonymous profiles participating in the anonymous chat room.

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

[0013] The method of operating the server may further include the steps of receiving a receipt request from the recipient's account based on the remittance advice sent to the recipient's account, verifying the recipient's account's eligibility to receive based on authentication information of the recipient's account, and processing a remittance transaction corresponding to the receipt request based on the existence or absence of the recipient's account's eligibility to receive.

[0014] The step of processing the remittance transaction may include a step of processing the remittance transaction if the recipient's account eligibility to receive is confirmed, and a step of requesting the recipient to authenticate himself / herself to obtain eligibility to receive if the recipient's account eligibility to receive is not confirmed.

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

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

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

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

[0019] The payee's account may include an account created when the payee subscribes to the remittance service.

[0020] According to one aspect, a method of operating a client for using a remittance service provided by a server includes the steps of requesting from the server remittance eligibility through an anonymous chat room in which the client is participating based on whether an account subscribed to the remittance service has been authenticated, selecting at least one of the temporary profiles participating in the anonymous chat room as a recipient, and requesting remittance to the temporary profile based on the receiving eligibility of a participant corresponding to the temporary profile selected as the recipient.

[0021] A server providing a remittance service according to one aspect includes at least one processor that receives a remittance request from a remitter participating in an anonymous chat room provided by the server as a first temporary profile to a second temporary profile participating in the anonymous chat room, verifies the remittance qualification of the remitter's account based on authentication information of the remitter's account, generates remittance transaction information for remitting an amount corresponding to the remittance request to a recipient's account corresponding to the second temporary profile based on the remittance qualification of the remitter's account, and sends a remittance notification to the recipient's account including information regarding 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 is confirmed as being eligible to remit, and may request the remitter to authenticate himself / herself to obtain remittance qualification if the remitter's account is not confirmed as being eligible to remit.

[0023] The processor may receive a receipt request from the recipient's account based on a remittance advice sent to the recipient's account, verify eligibility of the recipient's account based on authentication information for the recipient's account, and process a remittance transaction corresponding to the receipt request based on eligibility of the recipient's account.

[0024] In one aspect, a client for using a remittance service provided by a server includes at least one processor that requests eligibility to remit through an anonymous chat room in which a user is participating based on whether or not an account subscribed to the remittance service has been authenticated, selects at least one of the temporary profiles in which a user is participating in the anonymous chat room as a recipient, and requests remittance to the temporary profile based on the receiving eligibility of a participant corresponding to the temporary profile selected as the recipient.

[0025] A method for providing a remittance service in cooperation with a remittance server in a messaging server providing a messaging service according to one aspect includes the steps of receiving 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, sending the remittance request to the remittance server based on whether the remitter's account is eligible to remit, receiving remittance transaction information from the remittance server including an identifier of the second temporary profile as a recipient, and sending 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 the steps of generating a temporary profile subordinate to the anonymous chat room for each participant in the anonymous chat room, and mapping and storing an identifier of the temporary profile of each participant to an account of each participant subscribing to the messaging service.

[0027] Sending the remittance request may include sending the remittance request to the remittance server further based on eligibility of a payee account mapped to the second temporary profile.

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

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

[0030] The method for providing the remittance service may further include the step of sending a remittance advice message to the remitter's account, the remitter's account including information about the second temporary profile as recipient information.

[0031] The remittance advice message may include information about the first temporary profile as remitter information.

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

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

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

[0035] According to one aspect, a method of operating a client for using a remittance service provided in conjunction with a remittance server by a messaging server includes the steps of requesting from the messaging server a remittance qualification through an anonymous chat room in which the client is participating based on whether an account subscribed to the messaging service is authenticated, selecting at least one of temporary profiles participating in the anonymous chat room as a recipient, and requesting remittance to the temporary profile selected as the recipient.

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

[0037] A method for providing a remittance service in cooperation with a remittance server by a messaging server providing a messaging service according to one aspect includes the steps of receiving a recipient verification request from the remittance server corresponding to a request to receive a remittance through an anonymous chat room, verifying whether an account that has requested the remittance server to receive the remittance is the same user as the recipient identifier included in the receipt request based on an identifier of a temporary profile of a participant subordinate to the anonymous chat room and mapping information of the participant's account, and transmitting the verification result to the remittance server.

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

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

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

[0041] A messaging server providing a remittance service in conjunction with a remittance server according 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, transmits 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 including an identifier of the second temporary profile as a recipient, and transmits a remittance notification message to a 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 can map and store an identifier of the temporary profile for each participant to an account of the participant that subscribes to a messaging service.

[0043] The processor, in sending the remittance request, may send the remittance request to the remittance server further based on eligibility of a payee account mapped to the second temporary profile.

[0044] A client for using a remittance service provided in conjunction with a remittance server in a messaging server according to one aspect includes at least one processor that requests, based on whether an account subscribed to the messaging service has been authenticated, from the messaging server for remittance eligibility 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 a recipient, and requests remittance to the temporary profile selected as the recipient.

[0045] The processor, in requesting the remittance, may request the remittance to the temporary profile based on the receiving entitlement of a 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 according to one aspect includes at least one processor that receives from the remittance server a recipient verification request corresponding to a request to receive a remittance through an anonymous chat room, verifies whether the account that has requested the remittance server to receive the remittance is the same user as the recipient identifier included in the receipt request based on an identifier of a temporary profile of a participant subordinate to the anonymous chat room and mapping information of the participant's account, and transmits the verification result to the remittance server.

[0047] The processor may receive the receipt request from the recipient's account based on a remittance advice message sent to the recipient's account, and may send the receipt request to the remittance server based on the recipient's account's eligibility to receive. Effect of the Invention

[0048] According to the present invention, it is possible to provide a technique that enables money transfer between participants in an anonymous chat room whose account information is unknown to each other. [Brief description of the drawings]

[0049] [Figure 1] 1 is a flowchart of a method of operation of a server providing a remittance service according to one embodiment. [Figure 2A] FIG. 13 is a diagram illustrating a step of generating remittance transaction information based on remittance qualification and receiving qualification according to an embodiment. [Figure 2B] FIG. 13 is a diagram illustrating a step of generating remittance transaction information based on remittance qualification and receiving qualification according to an embodiment. [Figure 3A] FIG. 13 illustrates an example remittance interface screen according to one embodiment. [Figure 3B] FIG. 13 illustrates an example remittance interface screen according to one embodiment. [Figure 3C]FIG. 13 illustrates an example remittance interface screen according to one embodiment. [Figure 3D] FIG. 13 illustrates an example remittance interface screen according to one embodiment. [Figure 3E] FIG. 13 illustrates an example remittance interface screen according to one embodiment. [Figure 3F] FIG. 13 illustrates an example remittance interface screen according to one embodiment. [Figure 4] 1 is a flowchart of a method of operation of a server providing a remittance service according to one embodiment. [Diagram 5] FIG. 1 is a diagram illustrating the steps of processing a remittance transaction based on receiving entitlement according to one embodiment. [Figure 6] 1 is a flowchart of a method for operating a client for using a remittance service provided by a server according to an embodiment. [Figure 7] FIG. 2 is a diagram illustrating a hardware configuration of a remittance system according to an embodiment. [Figure 8] FIG. 1 illustrates a remittance system according to one embodiment. [Figure 9] 1 is a flowchart illustrating an operation of a method for providing a remittance service in cooperation with a remittance server in a messaging server according to an embodiment. [Figure 10] 1 is a flowchart of a method of operating a client for using a remittance service provided by a messaging server in conjunction with a remittance server according to an embodiment; [Figure 11] 1 is a diagram illustrating an overall scenario for a remittance process according to an embodiment; [Figure 12A] FIG. 2 illustrates an example of a remittance advice message according to one embodiment. [Figure 12B] FIG. 2 illustrates an example of a remittance advice message according to one embodiment. [Figure 13] 1 is a flowchart illustrating an operation of a method for providing a remittance service in cooperation with a remittance server in a messaging server according to an embodiment. [Figure 14]FIG. 2 illustrates an overall scenario of a receiving process of a remittance service according to an embodiment. [Figure 15A] FIG. 13 illustrates an example of a receipt acknowledgement message according to an embodiment. [Figure 15B] FIG. 13 illustrates an example of a receipt acknowledgement message according to an embodiment. [Figure 16] FIG. 2 is a diagram illustrating a hardware configuration of a remittance system according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0050] The specific structural or functional description of the embodiments is disclosed for the purpose of illustration only, and may be modified in various forms. Therefore, the embodiments are not limited to the specific disclosed forms, and the scope of the present specification includes modifications, equivalents, or alternatives within the technical spirit.

[0051] Although terms such as first or second may be used to describe multiple components, such terms should be construed only for the purpose of distinguishing one component from the other components. For example, a "first component" may be termed a "second component," and similarly, a "second component" may be termed a "first component."

[0052] When a component is referred to as being "coupled" or "connected" to another component, it should be understood that although it is directly coupled or connected to the other component, there may be other components in between.

[0053] The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, the terms "comprise" or "have" are intended to specify the presence of the described features, numbers, steps, operations, components, parts, or combinations thereof, and should be understood not to preclude the presence or additional possibility of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

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

[0055] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. In the description with reference to the accompanying drawings, the same components are given the same reference numerals regardless of the reference numerals, and redundant description thereof will be omitted.

[0056] FIG. 1 is a flow chart of a method of operation of a server providing a remittance service according to one embodiment.

[0057] 1, an operation method of a server providing a remittance service according to an embodiment includes receiving a remittance request from a remitter participating in an anonymous chat room as a first temporary profile in a second temporary profile participating in the anonymous chat room in step S110, verifying remittance qualification of the remitter's account in step S120, generating remittance transaction information for remittance of an amount corresponding to the remittance request to a recipient's account corresponding to the second temporary profile in step S130, and sending a remittance notification including information on the first temporary profile as remitter information to the recipient's account in step S140. More specifically, the operations described with reference to FIG. 1 correspond to a remittance process of the remittance service executed in the server.

[0058] The server according to an embodiment is a server that provides a remittance service, and creates and manages accounts of registered users and provides a service of sending and receiving a certain amount of money using the accounts. For example, the account may refer to a bank account or an online account that stores virtual electronic currency having a certain monetary value.

[0059] In one embodiment, the server creates an account corresponding to the user who has requested subscription, and a client logged into the created account can use the service provided by the server. The client includes a terminal of a user logged into an account of the remittance service.

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

[0061] According to one embodiment, the remitter refers to a client who has requested a remittance from the server, and the recipient refers to a client designated by the remitter to receive the requested remittance. The remitter's account may include an account created by the remitter subscribing to a remittance service provided by the server, and the recipient's account includes an account created by the recipient subscribing to a remittance service provided by the server.

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

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

[0064] According to an embodiment, the temporary profile is a profile temporarily assigned to a user's account, and may include an arbitrary name input by the user, not the user's real name information, or a name randomly generated by the server, as identification information. In other words, an anonymous chat room is a chat room that can be joined through a temporary profile that is temporarily generated without exposing an account based on the user's real name information. Unlike a general chat room for chatting with other users who know the account, an anonymous chat room can be used as a means for chatting between users who do not share accounts. Participants in an anonymous chat room may be displayed as a temporary profile to other participants in the anonymous chat room, and messages can be exchanged in the anonymous chat room using the temporary profile.

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

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

[0067] According to one embodiment, the remittance request includes information required for remittance. For example, the remittance request may include a recipient identifier and a remittance amount. The recipient identifier may include an identifier of a second temporary profile that is a participant of the 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, the 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 that sent the remittance request.

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

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

[0070] As an example, the step of providing a remittance interface may include a step of displaying a first type of temporary profile corresponding to an account including authentication information and a second type of temporary profile corresponding to an account not including authentication information among anonymous profiles participating in the anonymous chat room, in a differentiated manner. Also, as an example, the step of providing a remittance interface may include a step of deactivating an input for selecting a second type of temporary profile corresponding to an account not including authentication information among anonymous profiles participating in the anonymous chat room as a recipient. The remittance interface will be described below.

[0071] Step S120 according to one embodiment includes a step of confirming the remittance qualification of the remitter's account based on the authentication information of the remitter's account. The remitter qualification is the qualification required to request a remittance through an anonymous chat room, and more specifically, the qualification required to request a remittance by designating a temporary profile other than account information as a recipient. The remitter qualification is determined as whether the remitter's account is authenticated. For example, the remitter's account is determined to be eligible for remittance if it is an authenticated account, or if the remitter's account holds a certificate related to authentication issued by a server.

[0072] According to one embodiment, the subscriber's account can be authenticated according to a predetermined scheme via the server. The server stores authentication information (e.g., certificates) of the subscriber's account and determines whether a given user's account is an authenticated account based on the stored authentication information. If authentication information corresponding to the remitter's account is stored, the server determines that the remitter's account is eligible to remit.

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

[0074] As an example, referring to FIG. 2A, the step of generating remittance transaction information (e.g., step S130 shown in FIG. 1) includes step S210 of generating remittance transaction information if the remitter's account is confirmed as being eligible to remit, and step S220 of requesting the remitter to authenticate himself / herself to obtain remittance qualification if the remitter's account is not confirmed as being eligible to remit. As an example, based on the server's authentication request 220, the remitter's account may perform authentication according to a predetermined method via the server. If the authentication of the remitter's account is successfully performed through step S220, remittance qualification is obtained, and thus 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 transaction 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 refers to a valid period during which receipt of the remittance can be requested, and may be determined based on the time when the remittance request is generated or the time when the remittance request is received by the server.

[0076] According to an embodiment, a token for a remittance transaction may be generated in response to remittance transaction information. The token for a remittance transaction corresponds to information required for authenticating a remittance transaction. The server may obtain the recipient and the identifier of the second temporary profile designated and the recipient's account mapped thereto, and may generate a token based on the identifier of the second temporary profile of the recipient and the recipient's account. The server may generate a token corresponding to the identifier of the user's temporary profile and the user's account mapped thereto using a logic for token generation. For example, the server may generate a token based on additional information for identifying a remittance transaction, such as validity period information of receipt according to the time when a remittance request is received. The token generated based on the validity period information of receipt is also used by the server to confirm the validity period for receipt of the remittance. A method for authenticating a remittance transaction using a token will be described below. The token may be transmitted to the remittance transaction information and the recipient.

[0077] Referring again to FIG. 1, step S130 according to an embodiment includes a step of confirming the recipient's account's eligibility to receive based on the authentication information of the recipient's account, and a step of generating remittance transaction information further based on the eligibility of the recipient's account. The eligibility to receive is a qualification required to receive a remittance through an anonymous chat room, and more specifically, corresponds to a qualification required to receive a requested remittance by designating a temporary profile other than account information as the recipient. The eligibility to receive is determined as the authentication of the recipient's account, and for example, the recipient's account is determined to be eligible to receive if it is an account that has been authenticated, or if the recipient's account holds a certificate related to identity authentication issued by the server. In other words, the server can generate remittance transaction information if the remittance eligibility of the remitter's account and the eligibility of the recipient's account are both confirmed.

[0078] As an example, referring to FIG. 2B, the server receives a recipient selection input from the sender whose remittance qualification has been confirmed (S230), and confirms the recipient's eligibility to receive (S240). As an example, in step S110 of receiving a remittance request, the recipient selection input is received (S230), so the remittance qualification confirmation 120 of the remittance account may be performed after the recipient selection input is received (S230). The step of generating remittance transaction information based further on the presence or absence of the recipient's account eligibility includes step S250 of generating remittance transaction information if the recipient's account eligibility has been confirmed, and step S260 of sending a remittance failure notification to the remittance account if the recipient's account eligibility has not been confirmed. The step S250 of generating remittance transaction information is performed when the remittance qualification and the recipient eligibility are all confirmed.

[0079] In one embodiment, step S240 of confirming the recipient's account eligibility is a step of confirming the recipient's eligibility of the account corresponding to the temporary profile designated by the remitter as the recipient, and is executed in response to the recipient's selection input 230 received from the remitter. Here, if the recipient's account eligibility has not been confirmed, the server does not request the recipient, who has not input a request for a remittance transaction to the server, to authenticate himself / herself to confirm eligibility, and provides the sender with a remittance failure notice.

[0080] According to one embodiment, the server may generate the remittance transaction information without checking eligibility, which may be performed when a receipt request is received from the payee.

[0081] According to one embodiment, unlike that shown in Fig. 2B, the server may first check whether the anonymous chat room participants are eligible to receive money before the recipient selection input is received (S230). The server provides the sender with participants who are confirmed to be eligible to receive money as recipients to select, and does not activate the input to select participants who are not eligible to receive money as recipients, as will be described below.

[0082] Step S140 according to an embodiment includes a step of sending a remittance notice including information on the first temporary profile as remitter information to a recipient's account based on the remittance transaction information generated in step S130. As an example, the remittance notice sent to the recipient may be sent in the form of a message and a push notification. The server obtains a recipient's account corresponding to an identifier of the temporary profile included as a recipient identifier in the remittance transaction information, and sends the remittance notice to the recipient's account. As described above, the server stores mapping information between an identifier of a temporary profile subordinate to an anonymous chat room and an account of a user to which the temporary profile is assigned. The server obtains a recipient's account corresponding to an identifier of the temporary profile included as a recipient identifier in the remittance transaction information based on the mapping information. The server may transmit the remittance transaction identifier and a token for the remittance transaction included in the remittance transaction information to the recipient via a remittance notice message.

[0083] According to an embodiment, the remittance notice sent to the recipient's account includes information for notifying that a certain amount of money has been remitted from the remitter. The remittance notice sent to the recipient may include information about the first temporary profile as remitter information. The server obtains an identifier of the first temporary profile of the remitter subordinate to the anonymous chat room mapped to the remitter's account corresponding to the remittance request based on the mapping information. The anonymous chat room is an anonymous chat room in which the remitter and the recipient participate and in which the remittance request by the remitter occurs. In the anonymous chat room, the accounts between the participants are not exposed, so the remitter's account is not exposed in the remittance notice, and information about the first temporary profile of the anonymous chat room may be included. The information about the temporary profile includes a name or alias set in the temporary profile regardless of the user's real name.

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

[0085] The operating method of the server according to an embodiment may further include a step of sending a remittance notice including information on the second temporary profile as recipient information to the remitter's account. The server may also send the remittance notice to the remitter's account based on the remittance transaction information. For example, the remittance notice sent to the remitter is sent in the form of a message and a push notification. For example, the remittance notice sent to the remitter includes information for notifying the recipient that a certain amount of remittance has been delivered. The information on the recipient is displayed in the information on the second temporary profile. For example, the remittance notice may include information on an anonymous chat room in which a remittance request has occurred. The information on the anonymous chat room includes names set in anonymous chat rooms in which the recipient and the remitter participate.

[0086] According to one embodiment, the transmission of a remittance is distinct from receipt completion, and receipt is completed when the recipient requests receipt for the transmitted remittance and the receipt process is completed.

[0087] 3A-3D are diagrams illustrating an example remittance interface screen according to one embodiment.

[0088] Referring to Figure 3A, an anonymous chat room interface includes a send money button 301 that is connected to a send money interface via a menu bar 302. The anonymous chat room interface shown in Figure 3A can be switched to the send money interface shown in Figure 3B through an input of selecting the send money button 301.

[0089] 3B, the money transfer interface displays a list of the casual profiles participating in the anonymous chat room and includes a picker for selecting a casual profile participating in the anonymous chat room as a recipient. An input is received via the money transfer interface selecting at least one casual profile from the casual profiles participating in the anonymous chat room, and the selected casual profile 311 is designated as a recipient of the money transfer.

[0090] According to one embodiment, the server displays a first type of temporary profile corresponding to an account including authentication information and a second type of temporary profile corresponding to an account not including authentication information among anonymous profiles participating in an anonymous chat room. The accounts including authentication information are accounts that have been authenticated through the server, and the accounts not including authentication information are accounts that have not been authenticated through the server. In other words, the first type of temporary profile corresponds to a temporary profile of an account whose eligibility to receive has been confirmed, and the second type of temporary profile corresponds to a temporary profile of an account whose eligibility to receive has not been confirmed.

[0091] As an example, referring to FIG. 3C, among the temporary profiles participating in an anonymous chat room, the first type of temporary profile 323, 322 is displayed with marks 321, 324 to indicate that it is an authenticated profile whose eligibility to receive has been confirmed.

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

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

[0094] Referring to FIG. 3E, a remittance button 341 connected to a remittance interface is provided through the temporary profile view. The interface of the temporary profile view shown in FIG. 3E is switched to a remittance interface for inputting a remittance amount shown in FIG. 3F through an input for selecting the remittance button 341. When the remittance interface is connected through the remittance button 341 included in the temporary profile view, the corresponding temporary profile is selected as a recipient, so that the interface is switched to a remittance interface for inputting a remittance amount shown in FIG. 3F without a separate process for selecting a recipient. As an example, the remittance button 341 provided through the temporary profile view shown in FIG. 3E may be exposed or not exposed depending on whether or not the account corresponding to the corresponding temporary profile has a receiving eligibility. Specifically, if the receiving eligibility of the account corresponding to the temporary profile has not been confirmed, the remittance button 341 for a remittance request is not exposed.

[0095] FIG. 4 is a flow chart of a method of operation of a server providing a remittance service according to one embodiment.

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

[0097] Step S410 according to one embodiment includes receiving a receipt request from the payee's account based on the remittance advice sent to the payee's account. The payee requests the server to receive the remittance via the remittance advice. The receipt request includes the remittance transaction information included in the remittance advice and a token for the remittance transaction. 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 payee identifier corresponding to the remittance request.

[0098] Step S420 according to one embodiment includes a step of confirming eligibility of the payee's account based on authentication information of the payee's account. Eligibility is determined based on whether the payee's account is authenticated, for example, the payee's account is determined to be eligible if it is an authenticated account, or the payee's account is determined to be eligible if it holds a certificate related to authentication issued by a server. As described above, confirmation of eligibility may be performed in the receiving process separately from the remittance process, or may be omitted in the receiving process if confirmation of eligibility is performed in the remittance process.

[0099] Step S420 according to an embodiment may further include 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 payee identifier included in the receipt request based on the mapping information. The server may generate a token based on the payee identifier and the obtained account, and verify the remittance transaction by comparing whether the generated token is the same as the token included in the receipt request.

[0100] Step S420 according to an 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 further based on the information on the validity period of receiving, and the server verifies whether the remittance transaction is valid by checking the validity period of 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 on the validity period of the remittance transaction, and the server may verify whether the remittance transaction is valid by checking the validity period of the remittance transaction information included in the receiving request.

[0101] In one embodiment, step S430 includes processing a remittance transaction corresponding to the receipt request based on whether the recipient's account is eligible to receive. Processing a remittance transaction means processing the remittance and receipt of a remittance amount from the remitter's account to the recipient's account based on remittance transaction information.

[0102] For example, referring to Fig. 5, the step of processing the remittance transaction (e.g., step S430 shown in Fig. 4) includes step S510 of processing the remittance transaction if the recipient's account is confirmed as eligible to receive, and step S520 of requesting the recipient to authenticate to obtain the recipient's eligibility to receive if the recipient's account is not confirmed as eligible to receive. For example, based on the server's authentication request 520, the recipient's account may perform authentication according to a predetermined method via the server. If the recipient's account is successfully authenticated according to step S520, the recipient's eligibility to receive is obtained, and the server processes the remittance transaction (S510).

[0103] The method of operating the server according to an embodiment further includes a step S530 of sending an acknowledgement to the payee account and / or the sender account.

[0104] According to an embodiment, the method of operating the server may include a step of sending a receipt notification including information on the first temporary profile as remitter information to the recipient's account based on processing of a remittance transaction corresponding to the receipt request. As an example, the receipt notification sent to the recipient may be sent in the form of a message and a push notification. According to an embodiment, the receipt notification sent to the recipient's account may include information for notifying that receipt of the remittance of the remittance by the remitter has been completed. The receipt notification sent to the recipient may include information on the first temporary profile as remitter information. Like the remittance notification, the receipt notification may also not expose the remitter's account and may include information on the first temporary profile corresponding to the remitter's account. As an example, the receipt notification may include information on an anonymous chat room in which the remittance request occurred. The information on the anonymous chat room may include a name set in an anonymous chat room in which the recipient and the remitter participate.

[0105] According to one embodiment, the method of operating the server includes a step of sending a receipt notification including information on the second temporary profile as recipient information to the remitter's account based on processing of a remittance transaction corresponding to the receipt request. As an example, the receipt notification sent to the remitter may be sent in the form of a message and a push notification. According to one embodiment, the receipt notification sent to the remitter's account includes information for notifying that the recipient's receipt of the remittance is completed. The receipt notification sent to the remitter may include information on the second temporary profile as recipient information. Like the remittance notification, the receipt notification also does not expose the recipient's account, but includes information on the second temporary profile corresponding to the recipient's account. As an example, the receipt notification may include information on an anonymous chat room in which the remittance request occurred. The information on the anonymous chat room may include names set in anonymous chat rooms in which the recipient and the remitter participate.

[0106] FIG. 6 is a flowchart of an operation method of a client for using a remittance service provided by a server according to an embodiment.

[0107] 6, an operation method of a client for using a remittance service provided by a server according to an embodiment includes step S610 of requesting a server for remittance qualification through an anonymous chat room in which the client is participating based on whether an account subscribed to the remittance service is authenticated, step S620 of selecting at least one of the temporary profiles in which the client is participating as a recipient, and step S630 of requesting remittance to the temporary profile based on the receiving qualification of a participant corresponding to the temporary profile selected as the recipient. More specifically, the operation described with reference to FIG. 6 corresponds to a remittance process executed by a client corresponding to a remitter.

[0108] Step S610 according to an embodiment includes a step of requesting a remittance qualification from the server if the account of the client subscribing to the remittance service has not been authenticated. As described above, the remittance qualification is a qualification required to request a remittance through the anonymous chat room, and the remittance qualification is determined based on the presence or absence of authentication. Step S610 according to an embodiment includes a step of requesting authentication for obtaining the remittance qualification from the server. For example, the client can obtain the remittance qualification by performing a personal authentication provided by the server to register authentication information in the server or by performing an authentication procedure to obtain a certificate issued by the server. The client can perform a remittance process through the anonymous chat room based on the obtained remittance qualification.

[0109] Step S620 according to one embodiment includes selecting, as a recipient, at least one of the temporary profiles participating in the anonymous chat room of the client whose remittance qualification has been confirmed by the server in step S610.

[0110] In one embodiment, step S630 is a step of requesting the server to send money to a recipient that is an anonymous profile identifier that is not another user's account. In other words, a client who has been confirmed as eligible to send money can request a transfer to a party whose account information is unknown.

[0111] According to one embodiment, the remittance request can be sent to the server based on the recipient's eligibility, which is determined based on the authentication of an account mapped to the temporary profile selected for the recipient at the server. If the recipient's eligibility is confirmed, the remittance request is sent to the server.

[0112] According to one embodiment, a step of verifying eligibility of anonymous chat room participants may be performed prior to selecting them as recipients S620, where temporary profiles corresponding to participants whose eligibility has been verified are displayed among the temporary profiles available for selection as recipients, and 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 checking the recipient's eligibility, which is determined when the recipient requests receipt for the remittance.

[0114] FIG. 7 is a diagram illustrating a hardware configuration of a remittance system according to an embodiment.

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

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

[0117] The server 720 according to an embodiment may be realized as a computer device or multiple computer devices that communicate with the client 710 and / or other servers via a network 730 to provide instructions, code, files, content, services, and the like. The communication method is not limited thereto and may include the network 730, and may include a communication method utilizing a communication network (e.g., a mobile communication network, a wired Internet, a wireless Internet, a broadcasting network), and a short-range wireless communication method between devices. For example, the network 730 may include any one or more of a personal area network (PAN), a local area network (LAN), a campus area network (CAN), a metropolitan area network (MAN), a wide area network (WAN), a broadband network (BBN), the Internet, and the like.

[0118] According to an embodiment, the server 720 can provide a file for installing an application to the client 710 connected via the network 730. In this case, the client 710 installs an application (e.g., a remittance service application with a chat function or a chat service application with a remittance function) using the file provided by the server 720. In addition, the client 710 connects to the server 720 under the control of an operating system (OS) and at least one program (e.g., a browser or an installed application) included in the client 710, and the server 720 provides services and content. For example, when the client 710 transmits a service request message to the server 720 via the network 730 under the control of an application, the server 720 transmits 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 under the control of the application.

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

[0120] The processors 713, 723 according to an embodiment perform at least one of the operations described above with reference to Figures 1 to 6. For example, the processor 713 may perform at least one operation for using the remittance service provided by the server to the client 710 described above with reference to Figure 6, and the processor 723 may perform at least one operation for providing the remittance service executed by the server 720 described above with reference to Figures 1 to 5. The processors 713, 723 may be configured to process computer program instructions by performing basic arithmetic, logic, and input / output operations. The instructions may be provided to the processors 713, 723 by the memory 711, 721 or the communication modules 715, 725.

[0121] The memories 711 and 721 may be volatile or non-volatile memories as computer readable recording media. The memories 711 and 721 according to an embodiment store information for the remittance service described above with reference to Figs. 1 to 6. As an example, the memory 721 stores accounts and account authentication information generated corresponding to subscribed users, and stores identifiers of temporary profiles subordinate to anonymous chat rooms and mapping information of accounts of users to which the temporary profiles are assigned.

[0122] In one embodiment, memory 711 may include code for a money transfer service app with chat functionality or a chat service app with money transfer functionality that is installed on and driven by a file provided by server 720 over network 730.

[0123] The memory 721 according to an embodiment may store a program that embodies the operation of the server for providing the remittance service described above with reference to FIGS.

[0124] In one embodiment, communication modules 715, 725 provide functionality for the server 720 and client 710 to communicate with each other, and with other electronic devices or other servers over a network 730.

[0125] As an example, a request generated by the processor 713 of the client 710 in response to program code relating to a money transfer service app with chat functionality or a chat service app with money transfer functionality stored in a storage device such as the memory 711 may be transmitted to the server 720 via the network 730 in response to control of the communication module 715.

[0126] As an example, control signals, instructions, content, files, etc. provided in response to 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 via the communication module 725 and the network 730.

[0127] The input / output interfaces 717 and 727 may be means for interfacing with the input / output device 719. For example, the input device may include a device such as a keyboard or a mouse, and the output device may include a device such as a display for displaying a communication session of an application. As a different example, the input / output interface 717 may be means for interfacing with a device in which functions for input and output are integrated into one, such as a touch screen. As a more specific example, the processor 713 of the client 710 processes instructions of a computer program loaded in the memory 711, and a service screen or content configured using data provided by the server 720 is displayed on the display via the input / output interface 717. An input received from a user through the input / output device 719 may be provided in a form processable by the processor 713 of the client 710 via the input / output interface 717.

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

[0129] FIG. 8 is a diagram illustrating a remittance system according to an embodiment.

[0130] 8, the remittance system according to an 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 cooperate with each other to provide a remittance service. The client 830 includes a terminal of a user of the remittance service provided by the messaging server 810 and the remittance server 820.

[0131] The messaging server 810 according to an embodiment is a server that provides a messaging service, and may provide a messaging service for transmitting and receiving messages between users who have subscribed to the service provided by the messaging server 810, or for transmitting notification messages to the subscribed users. The messaging server 810 may provide a messaging service based on instant messages transmitted and received via a messenger application installed in a terminal of a subscribed user, or may provide a messaging service based on a short message service (SMS) provided by a mobile communication operator.

[0132] According to an embodiment, the messaging server 810 generates an account corresponding to the user who has requested to join, and the 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 real name information of the user who has requested to join. For example, the messaging server 810 can generate an account for the user based on authenticated real name information of the user who has requested to join and / or a mobile phone number under the real name of the user who has requested to join. The account corresponds to a unit for identifying a user who has subscribed to the messaging service in the messaging server 810. For example, the messaging server 810 delivers a message to the account of the user designated as the recipient, and stores a list of chat rooms in which the user participates and messages sent and received in the chat rooms corresponding to the user's account. The client 830 can set a friend relationship between its own account and another user's account, and can send and receive messages to and from the account of the other user set as a friend relationship through 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 different services linked with the messaging server 810. The client 830 may log in with an account of another service linked with the messaging server 810 and use the services provided by the messaging server 810.

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

[0135] The remittance server 820 according to an embodiment is a server that provides a remittance service in conjunction with the messaging server 810, and can provide a service of creating and managing accounts of registered users and sending and receiving a certain amount of money using the accounts. For example, the remittance server 820 may include an online banking server of a bank, or an online banking server that provides a remittance service via an application.

[0136] According to one embodiment, the remittance server 820 creates an account corresponding to a user who has requested subscription, and a client 830 logged into the created account can use 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 of 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 an embodiment, the messaging server 810 may provide a remittance service in cooperation with the remittance server 820. As an example, the messaging server 810 may provide a user who has subscribed to the messaging service with a function of requesting remittance to another user's account and requesting receipt of the remitted amount from the other user's account via a messaging application or chat room interface. The remittance server 820 may identify a remitter who has requested remittance to the messaging server 810 and a recipient of the requested remittance, and process a remittance transaction between the remitter's account and the recipient's account provided by the remittance server 820. The messaging server 810 may deliver a message regarding the remittance transaction processed by the remittance server 820 to the user's account. In other words, the messaging server 810 may provide a remittance service in cooperation with the remittance server 830 to a client 830 logged into a created account.

[0138] According to one embodiment, the messaging server 810 can provide a remittance service in which a participant in an anonymous chat room, whose account information is unknown, can be designated as a recipient and requested to remit money in cooperation with the remittance server 820. Hereinafter, a method for providing a remittance service between participants in an anonymous chat room in cooperation with the remittance server 820 in the messaging server 810 and a method for operating a client 830 for using the remittance service between participants in an anonymous chat room provided by the messaging server 810 in cooperation with the remittance server 820 will be described.

[0139] FIG. 9 is a flowchart illustrating a method for providing a remittance service in cooperation with a remittance server in a messaging server according to an embodiment.

[0140] 9, a method for providing a remittance service in cooperation with a remittance server by a messaging server providing a messaging service according to an embodiment includes receiving a remittance request from a remittance sender participating in an anonymous chat room as a first temporary profile to a second temporary profile participating in the anonymous chat room S910, sending the remittance request to the remittance server based on whether the remittance sender's account has remittance qualification S920, receiving remittance transaction information including an identifier of the second temporary profile as a recipient from the remittance server S930, and sending a remittance notification message to the recipient's account mapped to the identifier of the second temporary profile based on the remittance transaction information S940. More specifically, the operations described with reference to FIG. 9 correspond to a remittance process performed by the messaging server, and as an example, the messaging server that performs the operations described with reference to FIG. 9 corresponds to the messaging server 810 shown in FIG. 8.

[0141] According to one embodiment, the sender's account may include an account created by the sender subscribing to a messaging service, and the recipient's account includes an account created by the recipient subscribing to a messaging service.

[0142] According to one embodiment, a remitter refers to a client who has requested a remittance to a messaging server, and a recipient refers to a client designated by the remitter to receive the requested remittance. A client includes a terminal logged into an account of a user who has subscribed to a service provided by the messaging server. A client can log into an account created in the messaging server by subscribing and use the remittance service provided by the messaging server in conjunction with the remittance server. As an example, the remitter and recipient correspond to the client 830 shown in FIG. 8.

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

[0144] The method for providing a remittance service according to an embodiment further includes the steps of generating a temporary profile corresponding to each participant in the anonymous chat room and subordinate to the anonymous chat room, and mapping and storing an identifier of the temporary profile of each participant to an account of each participant who has subscribed to a messaging service. The messaging server maps and stores the temporary profile of a user generated to participate in 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 remitter'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 remitter's client knows its own account, the messaging server can convey the remitter's account to the information of the client who sent the remittance request.

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

[0147] For example, the remittance interface may be provided to the user's terminal through an input of selecting a remittance button included in a menu of an interface of an anonymous chat room, or may be provided to the user's terminal through an input of selecting a remittance button included in a temporary profile interface of a participant of the anonymous chat room. The remittance interface will be described below.

[0148] Step S920 according to one embodiment includes a step of determining whether the remitter's account that has sent the remittance request is qualified to remit, and if it is determined that the remitter is qualified to remit, sending the remittance request to the remittance server. Remittance qualification is determined as whether the remitter's account has been authenticated, and for example, the remitter is determined to be qualified to remit if the remitter's account is an authenticated account, or if the remitter's account holds a certificate related to personal authentication issued by a messaging server or an authentication server linked to the messaging server. The authentication server is linked to the messaging server and corresponds to a server that performs authentication operations for remittance qualification. This will be described below.

[0149] According to an embodiment, the step S920 of sending the remittance request includes a step of sending the remittance request to the remittance server further based on the presence or absence of the receiving qualification of the recipient's account mapped to the second temporary profile. The receiving qualification is the qualification required to receive a remittance through an anonymous chat room, and more specifically, corresponds to the qualification required to receive a requested remittance by designating a temporary profile other than the account information as the recipient. The receiving qualification is determined based on the presence or absence of authentication of the recipient's account, and for example, the recipient's account is determined to be eligible to receive if it is an account that has been authenticated, or if the recipient's account holds a certificate related to the authentication issued by the messaging server or an authentication server linked to the messaging server. If the remittance qualification of the remitter's account and the receiving qualification of the recipient's account are both confirmed, the messaging server sends the remittance request to the remittance server.

[0150] According to one embodiment, the sending process checks eligibility to send but not to receive, and the checking of eligibility may be performed in the receiving process, which is executed when a receive request is received from the payee, as described below.

[0151] For example, the confirmation of remittance eligibility and / or receipt eligibility may be performed by an authentication module of the messaging server. The authentication module is a module that performs an operation of authenticating the account of a user corresponding to the remitter and / or the recipient and determining whether the user's account is authenticated. For example, the authentication module may perform the authentication of the user's account according to a predetermined method. In addition, for example, the authentication module may perform an operation of generating authentication information (e.g., a certificate) according to the authentication, storing it, and providing it to the user's account, and determining whether the user's account is an authenticated account based on the stored authentication information. The messaging server determines whether the remitter's account is an account that is eligible for remittance based on the result of the authentication module's authentication of the remitter's account. For example, the authentication module may be a separate authentication server that is linked to the messaging server.

[0152] According to one embodiment, the remittance request sent to the remittance server includes information required for 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 may identify an account corresponding to the remitter's remittance server based on an account corresponding to the remitter's messaging server included in the remittance request, and the remittance server may perform authentication of the remittance server separately from the authentication procedure performed in the messaging server for the identified account corresponding to the remitter's remittance server.

[0154] According to one embodiment, the remittance request may be sent directly from the remitter to the remittance server without going through the messaging server. As an example, the remitter may send the remittance request to the remittance server based on the remittance qualification obtained by requesting the remittance qualification from the messaging server. Also, as an example, the remittance qualification obtained from the messaging server may not be required to send the remittance request to the remittance server, and the remittance server may determine the remittance qualification through authentication of the remitter's account, and the remittance server may request the messaging server to confirm the remittance qualification of the remitter's account.

[0155] Step S930 according to one embodiment includes a step of receiving remittance transaction information generated by the remittance server. The remittance server that has received the remittance request in step S920 generates remittance transaction information based on the received remittance request. The remittance server may generate the remittance transaction information after performing a procedure required for performing the remittance transaction at the remittance server, such as a separate authentication procedure. If it is determined that the remittance transaction is not appropriate to generate as a result of performing the procedure required for performing the remittance transaction at the remittance server, such as when the authentication of the remitter fails or the remitter's account does not have enough balance for remittance, the remittance server notifies the messaging server that the remittance transaction cannot be performed. The notification that the remittance transaction cannot be performed may be transmitted to the remitter and / or the 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 that is 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 a validity period during which receipt of the remittance can be requested, and may be determined based on the time when the remittance request is generated or the time when the remittance request is 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 transmitted to the remittance server, or may be generated by the remittance server.

[0157] According to an embodiment, in step S930, the remittance transaction information may be received together with a token for the remittance transaction. The token is data generated in the messaging server based on the identifier of the temporary profile of the recipient and the account of the recipient, and is information necessary for authenticating the remittance transaction. The messaging server may obtain the identifier of the second temporary profile designated as the recipient and the account of the recipient mapped thereto, and may generate a token based on the identifier of the second temporary profile of the recipient and the account of the recipient. The messaging server may generate a token corresponding to the identifier of the temporary profile of the user and the account of the user mapped thereto using a logic for token generation. For example, the messaging server may generate the token based on additional information for identifying the remittance transaction, such as validity period information of receipt according to the time when the remittance request is received. The token generated based on the validity period information of receipt may also be used to confirm the validity period of the receipt of the remittance in the messaging server. A method for authenticating a remittance transaction using the token will be described below. The token may be transmitted to the remittance server together with the remittance request in step S920, in which the messaging server sends the remittance request to the remittance server, and transmitted to the recipient via the messaging server together with the remittance transaction information generated at the remittance server.

[0158] Step S940 according to an embodiment may include a step of acquiring a payee account corresponding to an identifier of a temporary profile included as a payee identifier in the remittance transaction information, and sending a remittance advice message or a remittance advice to the payee account. As described above, the messaging server stores mapping information between an identifier of a temporary profile subordinate to an anonymous chat room and an account of a user to which the temporary profile is assigned. The messaging server acquires a payee account corresponding to an identifier of a temporary profile included as a payee identifier in the remittance transaction information based on the mapping information. The messaging server may transmit the remittance transaction identifier and a token for the remittance transaction included in the remittance transaction information to the payee via the remittance advice message.

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

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

[0161] The method for providing a remittance service according to an embodiment may further include a step of sending a remittance notification message including information on the second temporary profile as recipient information to the remitter's account. 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 classified as receipt completion, 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 remittance has been delivered, and the information on the recipient may be displayed as information on the second temporary profile.

[0162] Specific examples of remittance advice messages sent to the payee and sender according to one embodiment are described below.

[0163] FIG. 10 is a flowchart of a method of operating a client for using a remittance service provided by a messaging server in conjunction with a remittance server according to an embodiment.

[0164] 10, a method of operating a client for using a remittance service provided by a messaging server in conjunction with a remittance server according to an embodiment includes step S1010 of requesting a messaging server for remittance qualification through an anonymous chat room in which the client is participating, based on whether an account subscribed to the messaging service is authenticated, step S1020 of selecting at least one of temporary profiles in the anonymous chat room as a recipient, and step S1030 of requesting remittance to the temporary profile selected as the recipient. More specifically, the operations described with reference to FIG. 10 correspond to a remittance process performed by a client corresponding to a remitter, and as an example, a client performing the operations described with reference to FIG. 10 corresponds to the client 830 shown in FIG. 8.

[0165] Step S1010 according to an embodiment includes a step of requesting a remittance qualification from the messaging server if the account of the client subscribing to the messaging service is not authenticated. As described above, the remittance qualification is a qualification required to request a remittance through an anonymous chat room, and the remittance qualification is determined based on the presence or absence of authentication. Step S1010 according to an embodiment includes a step of requesting authentication for obtaining the remittance qualification from the messaging server. For example, the client can obtain the remittance qualification by performing a personal authentication provided by the messaging server to register authentication information in 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. The client can perform a remittance process through the anonymous chat room based on the obtained remittance qualification.

[0166] Step S1020 according to one embodiment includes selecting, as a recipient, at least one of the temporary profiles participating in the anonymous chat room of the client whose sending qualification has been confirmed by the messaging server in step S1010.

[0167] Step S1030 according to one embodiment is a step of requesting a messaging server or a remittance server to send money to a recipient that is an anonymous profile identifier that is not another user's account. In other words, a client whose remittance qualification has been confirmed requests a remittance to a party whose account information is unknown. As an example, the remittance request may be transmitted to the remittance server via a messaging server or may be transmitted to the remittance server immediately.

[0168] Step S1030 according to one embodiment includes requesting a remittance to the selected temporary profile based on the recipient's entitlement corresponding to the temporary profile. The remittance request is sent based on the recipient's entitlement, which is determined based on the authenticity of the account mapped to the selected temporary profile at the messaging server as the recipient. If the recipient's entitlement is confirmed, the remittance request can be sent to the remittance server or the messaging server.

[0169] According to one embodiment, the step of selecting as a recipient S1020 may be preceded by a step of verifying eligibility of anonymous chat room participants, where temporary profiles corresponding to participants whose eligibility has been verified are displayed among the temporary profiles available for selection as recipients, and 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, a remittance request may be sent without checking the recipient's eligibility, and the recipient's eligibility is determined when the recipient requests receipt of the remittance.

[0171] FIG. 11 illustrates an overall scenario for 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. As an example, the sender and recipient correspond to the client 830 shown in Figure 8, the messaging server corresponds to the messaging server 810 shown in Figure 8, and the remittance server corresponds to the remittance server 820 shown in Figure 8.

[0173] 11, a remitter requests a messaging server to remit money (S1103), and the remittance request includes the remittance amount and an identifier of a temporary profile of another user participating in an anonymous chat room. The remitter may request remittance qualifications from the messaging server (S1101) before the remittance request (S1103), and in response to the remittance qualification request, the messaging server performs authentication on the remitter's account and generates authentication information (S1102).

[0174] As an example, the messaging server may respond to a money transfer request by verifying the sender's eligibility to send money and / or the recipient's eligibility to receive money (S1104). As an example, the messaging server may not verify the recipient's eligibility during the money transfer process, but may verify only the sender's eligibility to send money.

[0175] As described above, the authentication operation for confirming remittance qualification and receipt qualification may be performed in an authentication module of the messaging server or an authentication server interoperating with the messaging server. When the authentication operation is performed in an authentication server interoperating with the messaging server, a remittance qualification request (S1101) is sent to the authentication server, and the authentication server generates authentication information for remittance (S1102). The remittance qualification request (S1101) may be transmitted to the authentication server via the messaging server or directly to the authentication server. Also, the authentication server may perform remittance qualification and / or receipt qualification confirmation (S1104) based on the remittance request (S1103), and the confirmed result may be transmitted to the messaging server.

[0176] For example, if the messaging server confirms the remittance qualification, it transmits a remittance request to the remittance server (S1105). The remittance request includes the remitter's account that sent the remittance request, the identifier of a temporary profile corresponding to the recipient designated by the remitter, and the remittance amount. As described above, when transmitting the remittance request to the remittance server (S1105), a token related to the remittance transaction may be transmitted to the messaging server together.

[0177] As an example, the remittance server that receives a remittance request from the 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 an identifier of the recipient's temporary profile included in the remittance request. As an example, the remittance server that receives a remittance request from the messaging server may perform a remittance authentication procedure in the messaging server separately from the remittance qualification confirmation procedure to authenticate the remitter (S1106), and if the remitter is authenticated, generate remittance transaction information (S1107).

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

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

[0180] 12A and 12B are diagrams illustrating an example of a remittance advice message according to one embodiment.

[0181] Referring to FIG. 12A, the remittance notification message 1210 is sent to the payee's account through a chat room. As an example, the chat room to which the remittance notification message 1210 is sent corresponds to a chat room of the payee'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 an informative message generated with the account related to the remittance server as the sender. Also, as an example, the chat room to which the remittance notification message 1210 is sent may be a 1:1 anonymous chat room of the remitter and the payee. If a remittance request occurs in an anonymous chat room including participants other than the payee and the remitter, a 1:1 anonymous chat room including the payee and the remitter is generated, and the remittance notification message 1210 may be transmitted and received through the generated 1:1 anonymous chat room. The temporary profiles of the payee and the remitter in the newly generated 1:1 anonymous chat room may be the same as the temporary profiles of the anonymous chat room in which the remittance request occurs. Alternatively, if the remittance request occurs in a 1:1 anonymous chat room including the recipient and the remitter, the remittance notification message 1210 may be sent or received via the corresponding anonymous chat room.

[0182] According to an embodiment, the remittance notification message 1210 may include a content notifying that a certain amount of money has been remitted from the remitter. As an example, the remitter information included in the remittance notification message 1210 may include a name (e.g., "Kaka") set in a temporary profile subordinate to the anonymous chat room in which the remitter's remittance request occurred. As described above, the name set in the temporary profile may be a name or alias set arbitrarily corresponding to the temporary profile that is not the real name information included in the remitter's account. Also, as an example, the remittance notification message 1210 may include information of the anonymous chat room in which the remittance request occurred. The information of the anonymous chat room may include a 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 interfacing object 1211 for a receipt request. The recipient can send a receipt request to a remittance server or a messaging server by selecting the interfacing object 1211 included in the remittance notification message 1210. The interfacing object 1211 corresponds to an object that includes a function of sending a receipt request including a remittance transaction identifier corresponding to the remittance request and a token for the remittance transaction to the messaging server or the remittance server by selection input.

[0184] Referring to Figure 12B, the remittance notification message 1220 is sent to the remitter's account through a chat room. As an example, the chat room to which the remittance notification message 1220 is sent corresponds to 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 corresponds to a chat room of a type for transmitting an informative message generated with the account related to the remittance server as the sender. As described above, the chat room to which the remittance notification message 1220 is sent may be a 1:1 anonymous chat room between the remitter and the recipient.

[0185] According to one embodiment, the remittance notification message 1220 includes a content notifying the recipient that a certain amount of money has been remitted. As an example, the recipient information included in the remittance notification message 1220 may include a name (e.g., "Melody") set in a temporary profile subordinate to the anonymous chat room in which the recipient's remittance request occurred. 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 corresponds to an arbitrarily set name or alias.

[0186] According to one embodiment, the remittance advice message 1220 includes an interfacing object 1221 for providing detailed information about the remittance request. The remitter can select the interfacing object 1221 included in the remittance advice message 1220 to request a page from the messaging server or remittance server that displays detailed information about the remittance request.

[0187] FIG. 13 is a flowchart illustrating a method for providing a remittance service in cooperation with a remittance server in a messaging server according to an embodiment.

[0188] 13, a method for providing a remittance service in cooperation with a remittance server by a messaging server providing a messaging service according to an embodiment includes receiving a recipient verification request corresponding to a remittance receipt request through an anonymous chat room from the remittance server in step S1310, verifying whether the account requesting the remittance server to receive the remittance is the same user as the recipient identifier included in the receipt request in step S1320, and transmitting the verification result to the remittance server in step S1330. More specifically, the operations described with reference to FIG. 13 correspond to a receiving process performed in the messaging server, and as an example, the messaging server that performs the operations described with reference to FIG. 13 corresponds to the messaging server 810 shown in FIG. 8.

[0189] Step S1310 according to one embodiment includes receiving a verification request from the remittance server as to whether the payee identifier included in the receipt request corresponds to the account that requested receipt. The payee identifier included in the receipt request is the payee identifier included in the remittance transaction information, and corresponds to the identifier of the temporary profile designated by the remitter when requesting remittance. Since the remittance server does not store mapping information of the account that requested receipt and the identifier of the temporary profile corresponding to the payee identifier, the remittance server cannot verify whether the account that requested receipt and the identifier of the temporary profile corresponding to the payee identifier belong to the same user, and may request verification from the messaging server.

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

[0191] According to one embodiment, the receipt request sent to the remittance server may be sent from the payee to the remittance server via a messaging server, or from the payee to the remittance server. If sent via a messaging server, the messaging server may check the receiving eligibility of the payee who sent the receipt request, and may transmit the receipt request to the remittance server based on the receiving eligibility. In other words, the method for providing a remittance service may further include a step of receiving a receipt request from the payee's account based on the remittance notification message sent to the payee's account, and a step of sending the receipt request to the remittance server based on the receiving eligibility of the payee's account.

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

[0193] Step S1320 according to an embodiment further includes 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 sent to the remittance server, or may be transferred from the remittance server to the messaging server. The messaging server obtains an account mapped to the payee identifier included in the receipt request based on the mapping information. The messaging server can generate a token based on the payee identifier and the obtained account, and verify the remittance transaction by comparing whether the generated token is the same as the token received from the remittance server.

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

[0195] Step S1330 according to one embodiment includes providing the beneficiary verification result of step S1320 to the remittance server. In step S1330, the result sent to the remittance server may include a result of whether the account requesting receipt is the beneficiary included in the remittance transaction information of the receipt request, and does not provide the remittance server with the temporary profile identifier and the account mapping information.

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

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

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

[0199] FIG. 14 is a diagram illustrating an overall scenario regarding the receiving process of a remittance service according to an embodiment.

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

[0201] 14, the payee requests receipt from the messaging server via a remittance advice message (S1401). The receipt request includes the remittance transaction information included in the remittance advice message.

[0202] As an example, the messaging server verifies the recipient's eligibility to receive (S1402) in response to the received receipt request. As described above, the confirmation of the recipient's eligibility to receive may be performed in response to the remittance request received from the remitter in the remittance process. The confirmation of eligibility to receive may be performed in the receiving process separately from the remittance process, or may be omitted in the receiving process if the confirmation of eligibility to receive is performed in the remittance process.

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

[0204] Although FIG. 14 illustrates an example in which the receipt request is communicated to the remittance server via a messaging server, the receipt request may be sent directly to the remittance server without passing through the messaging server.

[0205] As an example, the remittance server receiving a receipt request from the messaging server requests the messaging server to verify the recipient to determine whether the recipient identifier included in the receipt request is the same as the account that requested the receipt (S1405). As an example, the remittance server receiving a receipt request from the messaging server may perform a recipient authentication procedure in the messaging server separately from the receipt eligibility confirmation procedure to authenticate the recipient (S1404), and if the recipient is authenticated, may request the messaging server to verify the recipient (S1405).

[0206] For example, the messaging server can verify the recipient by acquiring an account mapped to the temporary profile identifier, which is the recipient identifier included in the receipt request, and determining whether the acquired account and the account that requested the receipt are the same user. If the verification result indicates that they are the same user, the verification result that the recipient is valid can be transmitted to the remittance server, and if the verification result indicates that they are not the same user, the verification result that the recipient is invalid can be transmitted to the remittance server (S1406).

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

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

[0209] 15A and 15B are diagrams illustrating an example of an acknowledgment message according to one embodiment.

[0210] Referring to Fig. 15A, the receipt acknowledgement message 1510 is sent to the payee's account through a chat room. As an example, the chat room to which the receipt acknowledgement message 1510 is sent corresponds to a chat room between the payee's account and an account related to the remittance server, and the chat room with the account related to the remittance server is a chat room of a type for transmitting an informative message generated with the account related to the remittance server as the sender. As described above, the chat room to which the receipt acknowledgement message 1510 is sent may be a 1:1 anonymous chat room between the remitter and the payee.

[0211] According to one embodiment, the receipt acknowledgement message 1510 includes a content notifying the recipient that a certain amount of money remitted from the remitter has been received. As an example, the remitter information included in the receipt acknowledgement message 1510 includes a name (e.g., "Kaka") set in a temporary profile subordinate to the anonymous chat room in which the remitter's remittance request occurred. As described above, the name set in the temporary profile corresponds to a name or alias arbitrarily set in response to the temporary profile, which is not the real name information included in the remitter's account.

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

[0213] Also, as an example, the receipt acknowledgement message 1510 may include information about the anonymous chat room in which the remittance request occurred. The anonymous chat room information may include a name (e.g., “AAA”) set for the anonymous chat room in which the recipient and remitter participate.

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

[0215] Referring to Fig. 15B, the receipt acknowledgement message 1520 is sent to the remitter's account through a chat room. As an example, the chat room to which the receipt acknowledgement message 1520 is sent corresponds to 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 corresponds to a chat room of a type for transmitting an informative message generated with the account related to the remittance server as the sender. As described above, the chat room to which the receipt acknowledgement message 1510 is sent may be a 1:1 anonymous chat room between the remitter and the recipient.

[0216] According to one embodiment, the receipt acknowledgement message 1520 includes a content notifying that a certain amount of money remitted from the remitter has been received by the recipient. As an example, the recipient information included in the receipt acknowledgement message 1520 may include a name (e.g., "Melody") set in a temporary profile subordinate to the anonymous chat room in which the remitter's remittance request occurred. As described above, the name set in the temporary profile may be a name or alias arbitrarily set in correspondence with the temporary profile that is not the real name information included in the recipient's account.

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

[0218] Also, as an example, the receipt acknowledgement message 1510 may include information about the anonymous chat room in which the remittance request occurred. The anonymous chat room information may include a name (e.g., "AAA") set for the anonymous chat room in which the recipient and the remitter participate.

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

[0220] FIG. 16 is a diagram illustrating a hardware configuration of a remittance system according to an embodiment.

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

[0222] The client 830 according to an embodiment may be a mobile terminal embodied in a computer device. For example, the client 830 may communicate with the messaging server 810, the remittance server 820, and / or other electronic devices through the network 1610 using a wireless or wired communication method.

[0223] The messaging server 810 and the remittance server 820 according to an embodiment may be implemented as a computer device or multiple computer devices that communicate with the 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 and may include a communication method utilizing a communication network (e.g., a mobile communication network, a wired Internet, a wireless Internet, a broadcasting network), a short-range wireless communication method between devices. For example, the network 1610 may include any one or more of a personal area network (PAN), a local area network (LAN), a campus area network (CAN), a metropolitan area network (MAN), a wide area network (WAN), a broadband network (BBN), the Internet, etc.

[0224] According to an embodiment, the messaging server 810 can provide a file for installing an application to the client 830 connected via the network 1610. In this case, the client 830 installs an application (e.g., an instant messaging application) using a file provided by the messaging server 810. In addition, the client 830 can connect to the messaging server 810 and receive services and content provided by the messaging server 810 according to the control of an operating system (OS) and at least one program (e.g., a browser or an installed application) included in the client 830. For example, when the client 830 transmits a service request message to the messaging server 810 via the network 1610 according to the control of an application, the messaging server 810 transmits a code corresponding to the service request message to the client 830, and the client 830 can provide the content to the user by configuring and displaying a screen according to the code according to the control of the application.

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

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

[0227] The memories 1611 and 1621 may be volatile or non-volatile memories as computer readable recording media. The memories 1611 and 1621 according to an embodiment store information related to the remittance service described above with reference to Figs. 8 to 15B. As an example, the memory 1621 may store an account and authentication information of the account created corresponding to a subscribing user, and may store an identifier of a temporary profile subordinate to an anonymous chat room and mapping information of the account of the user to whom the temporary profile is assigned.

[0228] Memory 1611 according to one embodiment includes code for an instant messaging app that is installed on client 830 and driven by files provided by messaging server 810 over network 1610 .

[0229] The memory 1621 according to an embodiment stores a program that embodies an operation for providing a remittance service executed by the messaging server 810 and the remittance server 820 as described above with reference to FIGS. 8 to 15B.

[0230] In one embodiment, the communication modules 1615, 1625 provide functionality for the client 830, messaging server 810 and remittance server 820 to communicate with each other over the network 1610, and may provide functionality for communication with other electronic devices or other servers.

[0231] As an example, a request generated by the processor 1613 of the client 830 using program code related to an instant messaging app stored in a storage device such as memory 1611 may be transmitted to the messaging server 810 via the network 1610 under the control of the communication module 1615.

[0232] As an 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 via the communication module 1625 and the network 1610, or by the remittance server 820.

[0233] The input / output interfaces 1617 and 1627 may be means for interfacing with the input / output device 1619. For example, the input device includes a device such as a keyboard or a mouse, and the output device includes a device such as a display for displaying a communication session of an application. As a different example, the input / output interface 1617 may be means for interfacing with a device in which functions for input and output are integrated into one, such as a touch screen. As a more specific example, the processor 1613 of the client 830 processes instructions of a computer program loaded in the memory 1611, and a service screen or content configured using data provided by the messaging server 810 is displayed on the display via the input / output interface 1617. An input received from a user through the input / output device 1619 may be provided in a form processable by the processor 1613 of the client 830 via the input / output interface 1617.

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

[0235] The embodiments described above may be implemented using hardware components, software components, or a combination of hardware and software components. For example, the devices and components described herein may be implemented using one or more general-purpose or special-purpose computers, such as a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA), a programmable logic unit (PLU), a microprocessor, or other 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 operating system. The processing device also accesses, stores, manipulates, processes, and generates data in response to the execution of the software. For ease of understanding, the processing device may be described as being one in which only one processing device is used, but one skilled in the art will appreciate that the processing device may include multiple processing elements and / or multiple types of processing elements. For example, the processing device may include multiple processors or one processor and one controller. Other processing configurations, such as parallel processors, are also possible.

[0236] The software may include computer programs, codes, instructions, or any combination of one or more thereof, capable of configuring or instructing a processing device to operate as desired, either independently or in combination. The software and / or data may be embodied in any type of machine, component, physical device, virtual device, computer storage medium or device, or transmitted signal wave, either permanently or temporarily, to be interpreted by the processing device or to provide instructions or data to the processing device. The software may be distributed across computer systems coupled to a network, and may be stored and executed in a distributed manner. The software and data may be stored on one or more computer readable recording media.

[0237] The method according to the present invention may be embodied in the form of program instructions to be executed by various computer means and recorded on a computer-readable recording medium. The recording medium may include program instructions, data files, data structures, and the like, alone or in combination. The recording medium and the program instructions may be specially designed and constructed for the purposes of the present invention, or may be well known and available to those skilled in the art 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 floptical disks, and hardware devices specially configured to store and execute program instructions, such as ROMs, RAMs, flash memories, and the like. Examples of program instructions include not only machine language code, such as that generated by a compiler, but also high-level language code executed by a computer using an interpreter, etc.

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

[0239] Although the embodiments have been described above with reference to limited drawings, those skilled in the art may apply various technical modifications and variations based on the above description. For example, the described techniques may be performed in a different order than described, and / or the components of the described systems, structures, devices, circuits, etc. may be combined or combined in a different form than described, and may be replaced or substituted with other components or equivalents to achieve appropriate results.

[0240] Accordingly, other implementations, embodiments, and equivalents of the claims are intended to be within the scope of the following claims.

Claims

1. A method of operating a terminal that uses a messaging service, comprising: displaying a remittance interface in conjunction with the messaging service; displaying information regarding a temporary profile of the recipient via the remittance interface; sending to a server a remittance request for a payee corresponding to the displayed temporary profile; displaying result information of the remittance request; Including, The method, wherein the payee's account information mapped to the temporary profile is not displayed in the remittance interface.

2. The server, a messaging server providing said messaging service; a remittance server that provides a remittance service in conjunction with the messaging server; The method of claim 1 , comprising at least one of:

3. The step of displaying the remittance interface includes: selecting said recipient via a chat room participating in a temporary profile; displaying the remittance interface for a remittance request to the selected recipient; The method of claim 1 , comprising:

4. The step of displaying the remittance interface includes: displaying a temporary profile view of another user's account; displaying the remittance interface via a temporary profile view of the other user account; Including, The method of claim 1 , wherein the recipient is determined to be a temporary profile of the other user account.

5. displaying the remittance interface linked with a temporary profile view of the other user account; if the receiving eligibility of the other user account is confirmed, displaying the remittance interface via a temporary profile view of the other user account; restricting a remittance function based on the remittance interface if the receiving eligibility of the other user account is not confirmed; The method of claim 4 , comprising:

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

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

8. The method of claim 1 , further comprising the step of: sending authentication information to the server for obtaining a transfer entitlement for an account corresponding to the terminal.

9. The method of claim 1 , wherein the result information of the remittance request includes at least one of information about a temporary profile of a remitter who is the originator of the remittance request and information about a temporary profile of the recipient.

10. 2. The method of claim 1, wherein displaying the result information of the remittance request comprises displaying a remittance failure notice if the recipient's account is not eligible and the remittance fails.

11. A method of operating a terminal that uses a messaging service, comprising: receiving user input for a transfer request to a payee utilizing a temporary profile; generating a signal for said remittance request including information of said temporary profile of said recipient; outputting result information of the remittance request; Including, The result information is The method includes information about the recipient in the temporary profile and does not include account information for the recipient mapped to the temporary profile.

12. The method of claim 11 , wherein a remittance transaction corresponding to the remittance request is processed at a remittance server associated with the messaging service.

13. The method of claim 12, wherein the payee's account information mapped to the temporary profile is transmitted from a messaging server providing the messaging service to the remittance server.

14. 12. The method of claim 11, wherein receiving the user input comprises receiving the user input for the money transfer request via an interface of a chat room in which the recipient participates as the temporary profile.

15. 15. The method of claim 14, wherein outputting the result information of the remittance request comprises displaying a message in the chat room including the result information of the remittance request.

16. The method of claim 11 , wherein receiving the user input comprises receiving the user input for the remittance request via the temporary profile view of the payee.

17. The method of claim 11 , wherein the result information of the remittance request further comprises information regarding a temporary profile of the remitter who is the originator of the remittance request.

18. 1. A method for providing a money transfer service in a server providing a messaging service, comprising: identifying account information mapped to a second temporary profile of the payee included in the remittance request; obtaining result information of the remittance request based on the identified account information; sending the result information to a remitter's terminal corresponding to the remittance request; Including, The result information is The information about the recipient includes information about the second temporary profile, but does not include account information about the recipient mapped to the second temporary profile.

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

20. 20. The method of claim 19, wherein the sender joins the anonymous chat room using the first temporary profile.

21. 20. The method of claim 18, further comprising displaying a first temporary profile corresponding to the sender on the recipient's terminal, and not displaying the sender's account information mapped to the first temporary profile.

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

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

24. A computer program stored on a computer readable medium for causing, in combination with hardware, to carry out the method according to any one of claims 1 to 23.

25. A terminal that uses a messaging service, one or more processors; A memory for storing instructions; Including, The instructions, when executed by the one or more processors, cause the terminal to: displaying a remittance interface linked to the messaging service; displaying information regarding the recipient's temporary profile via the remittance interface; sending a remittance request to a server for a payee corresponding to the displayed temporary profile; displaying a result of the remittance request; Run The payee's account information mapped to the temporary profile is not displayed in the remittance interface.

26. A terminal that uses a messaging service, one or more processors; A memory for storing instructions; Including, The instructions, when executed by the one or more processors, cause the terminal to: receiving a user input for a transfer request to a payee utilizing a temporary profile; a signal for the remittance request is generated, the signal including information of the temporary profile of the payee; outputting result information of the remittance request; Including, The result information includes information of the temporary profile as information of the recipient, but does not include account information of the recipient mapped to the temporary profile.

27. A server, one or more processors; A memory for storing instructions; Including, The instructions, when executed by the one or more processors, cause the server to: providing account information mapped to a second temporary profile of the recipient included in the remittance request; obtaining result information of the remittance request based on the identified account information; sending the result information to the remitter's terminal corresponding to the remittance request; Including, The result information includes information of the second temporary profile as information of the recipient, but does not include account information of the recipient mapped to the second temporary profile.

Images