Method for verifying sender or recipient and electronic device for doing so

Abstract

It is an object of the present invention to provide a method for verifying a sender or recipient of a payment and an electronic device for doing so. A method for verifying a beneficiary of an electronic device is provided. The method for verifying a beneficiary may include the steps of: identifying information on the transfer of virtual assets, including a full name data of an originator, a date of birth data of the originator, and a receiving virtual asset address; identifying a hash value set of the originator's name generated based on the originator's name data and a hash value set of the originator's date of birth generated based on the originator's date of birth data; sending a verification request message including the hash value set of the originator's name, the hash value set of the originator's date of birth, and the receiving virtual asset address to a beneficiary server; and receiving a response message including verification result information regarding whether the originator and the beneficiary match based on the verification request message, from the beneficiary server, and the completion of the transfer of the virtual assets from the originator's remittance virtual asset address to the receiving virtual asset address may be determined based on the verification result information.

Description

[Technical field]

[0001] The present specification relates to a method and electronic device for verifying a sender or recipient in transferring virtual assets. [Background technology]

[0002] With the development of blockchain technology, virtual assets such as Bitcoin are recognized as assets without borders, and the number of places where they can be used (e.g., offline stores, online stores, etc.) is increasing. Virtual assets can be exchanged for real assets, and their value can fluctuate from time to time. In addition, the types of virtual assets are becoming more diverse, and the number of virtual asset businesses that act as agents and manage virtual asset transactions is increasing.

[0003] In this regard, reference may be made to prior art documents such as Korean Patent Publication No. 10-2022-0025634. Summary of the Invention [Problem to be solved by the invention]

[0004] The embodiments disclosed herein aim to provide a method and an electronic device for verifying a sender or a recipient, and more specifically, to provide a method and an electronic device for verifying a sender or a recipient when transferring virtual assets, while complying with information disclosure requirements when transferring virtual assets and technically protecting personal information.

[0005] The technical problem to be solved by the present embodiment is not limited to the above-mentioned technical problem, and other technical problems can be inferred from the following embodiments. [Means for solving the problem]

[0006] According to one aspect of the present specification, there is provided a method for verifying a beneficiary, the method including: identifying information regarding a transfer of virtual assets, including a full name data of a remitter, a date of birth data of the remitter, and a recipient virtual asset address; identifying a hash value set of the remitter's name generated based on the remitter's name data and a hash value set of the remitter's date of birth generated based on the remitter's date of birth data; sending a verification request message including the hash value set of the remitter's name, the hash value set of the remitter's date of birth, and the recipient virtual asset address to a beneficiary server; and receiving a response message including verification result information regarding whether the remitter and the recipient match based on the verification request message, and determining whether to transfer the virtual assets from the remitter's remittance virtual asset address to the recipient virtual asset address based on the verification result information.

[0007] In addition, in one embodiment of the present specification, a recipient verification method may be provided, in which the verification request message further includes at least one of: a value indicating a type of the object to be verified; a value indicating a type of the virtual asset; an auxiliary virtual asset address related to the type of virtual asset; or a hash salt value associated with at least one of a hash value set of the remitter's name or a hash value set of the remitter's date of birth.

[0008] In addition, in one embodiment of the present specification, a recipient verification method may be provided, in which the verification result information includes at least one of the following: information indicating that an address matching the receiving virtual asset address or the auxiliary virtual asset address is not confirmed among the virtual asset addresses related to the receiving server; information regarding a mismatch between a hash value set of the sender's name and a hash value set of the recipient's name generated based on the recipient's name data corresponding to the receiving virtual asset address, or information regarding a mismatch between a hash value set of the sender's date of birth and a hash value set of the recipient's date of birth generated based on the recipient's date of birth data; or information indicating that the recipient is verified to match the sender.

[0009] In addition, in one embodiment of the present specification, a recipient verification method can be provided, in which if the response message includes information indicating that the recipient is verified to match the sender, it is determined that the transfer of the virtual assets will be performed, and if the response message includes one of information indicating that an address matching the receiving virtual asset address or the auxiliary virtual asset address is not confirmed among the virtual asset addresses related to the receiving server, information regarding a mismatch between a hash value set of the sender's name and a hash value set of the recipient's name generated based on the recipient's name data corresponding to the receiving virtual asset address, or information regarding a mismatch between a hash value set of the sender's date of birth and a hash value set of the recipient's date of birth generated based on the recipient's date of birth data, the transfer of the virtual assets is determined to be blocked.

[0010] In one embodiment of the present specification, a method for verifying a recipient may be provided, wherein the step of identifying a set of hash values ​​of the sender's name and the set of hash values ​​of the sender's date of birth includes removing spaces from the sender's name data.

[0011] In addition, in one embodiment of the present specification, a method for verifying a recipient may be provided, in which the step of identifying the hash value set of the remitter's name and the hash value set of the remitter's date of birth includes a step of converting the letter case of characters included in the remitter's name data to a set case.

[0012] In addition, in one embodiment of the present specification, a method for verifying a recipient may be provided, in which the hash value set of the remitter's name includes at least one of: a first hash value generated based on the remitter's name information consisting of a single entry in the order of first name and last name; a second hash value generated based on the remitter's name information consisting of a single entry in the order of the last name and the first name; or a third hash value generated based on the remitter's name information consisting of multiple entries including the last name, the first name, and at least one middle name.

[0013] In addition, in one embodiment of the present specification, a recipient verification method may be provided, in which the verification result information includes information regarding a mismatch between the remitter's name hash value set and the recipient's name hash value set when any one of the hash values ​​included in the recipient's name hash value set generated based on the recipient's name data corresponding to the receiving virtual asset address does not match any one of the first hash value, the second hash value, or the third hash value.

[0014] In addition, in one embodiment of the present specification, a recipient verification method may be provided, in which the recipient name hash value set generated based on the recipient name data corresponding to the receiving virtual asset address includes at least one of: a fourth hash value generated based on recipient name information composed of a single entry of first name and last name order; a fifth hash value generated based on recipient name information composed of the last name and a single entry of the first name order; or a sixth hash value generated based on recipient name information composed of multiple entries including the last name, the first name, and at least one middle name.

[0015] In addition, in one embodiment of the present specification, a recipient verification method may be provided, in which the verification result information includes information regarding a mismatch between the hash value set of the remitter's name and the hash value set of the recipient's name when any one of the hash values ​​included in the hash value set of the remitter's name does not match any one of the fourth hash value, the fifth hash value, or the sixth hash value.

[0016] Also, in one embodiment of the present specification, a recipient verification method can be provided in which the receiving virtual asset address is verified to see if there is an address in the receiving server's database that matches the receiving virtual asset address, regardless of whether at least one character included in the receiving virtual asset address is lowercase or uppercase.

[0017] In addition, in one embodiment of the present specification, a recipient verification method can be provided in which the receiving virtual asset address is verified by removing a set prefix included in the receiving virtual asset address and checking whether there is an address in the receiving server's database that matches the receiving virtual asset address.

[0018] Another aspect of the present specification may provide a remitter verification method, including the steps of: identifying a transferred virtual asset and a receiving virtual asset address; identifying a recipient's name data and the recipient's date of birth data corresponding to the receiving virtual asset address; identifying a hash value set of the recipient's name generated based on the recipient's name data and a hash value set of the recipient's date of birth generated based on the recipient's date of birth data; sending a verification request message including the hash value set of the recipient's name, the hash value set of the recipient's date of birth, and the receiving virtual asset address to a remittance (ordering) server; and receiving a response message from the remittance server including verification result information regarding whether the recipient and the remitter match based on the verification request message.

[0019] In addition, in one embodiment of the present specification, a method for verifying a remitter may be provided, in which the verification request message further includes at least one of a transaction identification value corresponding to the transfer of the virtual asset; a value indicating the type of the object to be verified; a value indicating the type of the virtual asset; an auxiliary virtual asset address related to the type of virtual asset; or a hash salt value associated with at least one of a hash value set of the recipient's name or a hash value set of the recipient's date of birth.

[0020] In one embodiment of the present specification, a remitter verification method may be provided, in which the verification result information includes at least one of the following: information indicating that a value matching the transaction identification value is not confirmed among the transaction identification values ​​related to the remittance server; information indicating that an address matching the receiving virtual asset address or the auxiliary virtual asset address is not confirmed among the virtual asset addresses related to the remittance server; information regarding a mismatch between a hash value set of the recipient's name and a hash value set of the remitter's name generated based on the receiving virtual asset address or the remitter's name data corresponding to the transaction identification value, or information regarding a mismatch between a hash value set of the recipient's date of birth and a hash value set of the remitter's date of birth generated based on the remitter's date of birth data; or information indicating that the remitter is verified to match the recipient.

[0021] In addition, in one embodiment of the present specification, a remitter verification method may be provided, further comprising a step of reflecting the virtual assets in the balance of the receiving virtual asset address at set time intervals based on the transaction identification value if the verification result information includes information indicating that the remitter is verified to match the recipient.

[0022] In addition, in one embodiment of the present specification, a remitter verification method may be provided in which the transaction identification value is checked to see if there is a value in the remittance server's database that matches the transaction identification value, regardless of whether at least one character included in the transaction identification value is lowercase or uppercase.

[0023] In addition, in one embodiment of the present specification, a remitter verification method can be provided in which, when the type of the transaction identification value includes an identifier type and a hash value type, a transaction identification value of the hash value type is used to check whether there is a value matching the transaction identification value in the remittance server's database.

[0024] In one embodiment of the present specification, a remitter verification method may be provided in which the transaction identification value includes a leading zero value and a check is made to see if there is a value in the remittance server's database that matches the transaction identification value.

[0025] Another aspect of the present specification may provide an electronic device including one or more processors; and a memory storing one or more instructions executed by the one or more processors, the one or more processors being configured to execute the one or more instructions to identify information regarding a transfer of virtual assets, including a full name data of a remitter, a date of birth data of the remitter, and a recipient virtual asset address, identify a hash value set of the remitter's name generated based on the remitter's name data and a hash value set of the remitter's date of birth generated based on the remitter's date of birth data, transmit a verification request message including the hash value set of the remitter's name, the hash value set of the remitter's date of birth, and the recipient virtual asset address to a beneficiary server, and receive a response message including verification result information performed based on the verification request message from the beneficiary server, and determine whether to transfer the virtual assets from the remitter's remittance virtual asset address to the recipient virtual asset address based on the verification result information.

[0026] Another aspect of the present specification may provide an electronic device including one or more processors; and a memory storing one or more instructions executed by the one or more processors, the one or more processors being configured to execute the one or more instructions to identify a transferred virtual asset and a receiving virtual asset address, identify a recipient's name data and a recipient's date of birth data corresponding to the receiving virtual asset address, identify a set of hash values ​​of the recipient's name generated based on the recipient's name data and a set of hash values ​​of the recipient's date of birth generated based on the recipient's date of birth data, send a verification request message including the set of hash values ​​of the recipient's name, the set of hash values ​​of the recipient's date of birth, and the receiving virtual asset address to a remittance (ordering) server, and receive a response message including verification result information performed based on the verification request message from the remittance server.

[0027] Yet another aspect of the present disclosure may provide a computer-readable recording medium having a program recorded thereon for implementing a method performed by an electronic device.

[0028] Further details of the embodiments are included in the detailed description and the drawings. Effect of the Invention

[0029] In accordance with the proposed embodiments, one or more of the following advantages may be expected.

[0030] According to the embodiments of the present specification, when transferring virtual assets, it is possible to effectively verify the sender or recipient while complying with the information disclosure requirements when transferring virtual assets and technically protecting personal information.

[0031] In addition, according to embodiments of the present specification, in the process of verifying a sender or recipient, unintended discrepancies that may occur in the absence of standard naming rules that can reflect the local naming practices of each country can be technically prevented.

[0032] Additionally, embodiments of the present disclosure may provide a technical shield against unintended discrepancies that may arise in the absence of standard names for values ​​or symbols that indicate types of virtual assets during the process of verifying a sender or recipient.

[0033] The effects of the present invention are not limited to the effects described above, and other effects not mentioned herein will be clearly understood by those skilled in the art from the description of the claims. [Brief description of the drawings]

[0034] [Figure 1] 1 illustrates a system according to one embodiment. [Figure 2a] 1 is a diagram illustrating a process in which an electronic device verifies a payee or sender according to an embodiment. [Figure 2b] 1 is a diagram illustrating a process in which an electronic device verifies a payee or sender according to an embodiment. [Figure 3a] 1 is a diagram illustrating a process by which an electronic device verifies a payee or sender according to one embodiment. [Figure 3b] 1 is a diagram illustrating a process by which an electronic device verifies a payee or sender according to one embodiment. [Figure 4a] 1 is a diagram illustrating a process in which an electronic device verifies a payee or sender according to one embodiment. [Figure 4b] 1 is a diagram illustrating a process in which an electronic device verifies a payee or sender according to one embodiment. [Figure 5a] 1 illustrates an example of a verification request message according to one embodiment. [Figure 5b] 1 illustrates an example of a verification request message according to one embodiment. [Figure 6] 13 illustrates an example of a response message according to one embodiment. [Figure 7a]11 is a diagram illustrating a process in which a virtual asset business server checks whether a hash value of a name matches according to an embodiment. [Figure 7b] 11 is a diagram illustrating a process in which a virtual asset business server checks whether a hash value of a name matches according to an embodiment. [Figure 7c] 11 is a diagram illustrating a process in which a virtual asset business server checks whether a hash value of a name matches according to an embodiment. [Figure 7d] 11 is a diagram illustrating a process in which a virtual asset business server checks whether a hash value of a name matches according to an embodiment. [Figure 7e] 11 is a diagram illustrating a process in which a virtual asset business server checks whether a hash value of a name matches according to an embodiment. [Figure 7f] 11 is a diagram illustrating a process in which a virtual asset business server checks whether a hash value of a name matches according to an embodiment. [Figure 7g] 11 is a diagram illustrating a process in which a virtual asset business server checks whether a hash value of a name matches according to an embodiment. [Figure 7h] 11 is a diagram illustrating a process in which a virtual asset business server checks whether a hash value of a name matches according to an embodiment. [Figure 8] 4 is a diagram illustrating a process in which an electronic device verifies a recipient according to an embodiment. [Figure 9] 1 is a diagram illustrating a process in which an electronic device verifies a remitter according to an embodiment. [Figure 10] 4 is a diagram illustrating a process in which an electronic device verifies a recipient according to an embodiment. [Figure 11] 1 is a diagram illustrating a process in which an electronic device verifies a remitter according to an embodiment. [Figure 12] 1 shows a flow chart of a method for beneficiary verification of an electronic device according to one embodiment. [Figure 13]2 illustrates a flow chart of a method for verifying an originator of an electronic device according to an embodiment. [Figure 14] FIG. 1 shows a block diagram of an electronic device according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0035] The terms used in the embodiments are currently widely used and common terms as much as possible while taking into consideration the functions in the present disclosure, but these may change depending on the intentions or precedents of the engineers engaged in the field, the emergence of new technologies, etc. In addition, in certain cases, the applicant may arbitrarily select terms, and in such cases, the meanings of the terms will be described in detail in the relevant description. Therefore, the terms used in this specification must be defined based on the meanings of the terms and the contents of this specification as a whole, rather than simply the names of the terms.

[0036] Throughout the specification, when a part "comprises" a certain element, this does not mean to exclude other elements, but means that it may further include other elements, unless specifically stated to the contrary.

[0037] Throughout this specification, the phrase "at least one of a, b, and c" can encompass "a alone," "b alone," "c alone," "a and b," "a and c," "b and c," or "all of a, b, and c."

[0038] The "terminal" referred to below may be realized as a computer or a portable terminal that can connect to a server or other terminals through a network. Here, the computer may be, for example, a notebook computer, a desktop computer, or a laptop computer equipped with a web browser, and the portable terminal may be, for example, a wireless communication device that ensures portability and mobility, and may include communication-based terminals such as IMT (international mobile telecommunication), CDMA (code division multiple access), W-CDMA (W-code division multiple access), and LTE (long term evolution), as well as all kinds of handheld-based wireless communication devices such as smartphones and tablet PCs.

[0039] Hereinafter, the embodiments disclosed herein will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily carry out the embodiments disclosed herein. However, the invention disclosed herein may be embodied in several different forms and is not limited to the embodiments described herein.

[0040] In this specification, a virtual asset refers to an electronic voucher or any right related thereto that has economic value and can be traded or transferred electronically. However, a virtual asset may be referred to as a digital asset, digital currency, virtual currency, cryptocurrency, etc., and is not limited to the above.

[0041] In this specification, a virtual asset service provider (VASP) means an entity that engages in any one of the following activities with respect to virtual assets:

[0042] 1) The act of selling or buying virtual assets.

[0043] 2) Exchanging virtual assets for other virtual assets.

[0044] 3) Acts of transferring virtual assets as specified by Presidential Decree.

[0045] 4) The act of storing or managing virtual assets.

[0046] 5) Acts of mediating, facilitating or acting on behalf of others in carrying out the activities under 1) and 2).

[0047] 6) Any other acts specified by Presidential Decree as having a high possibility of being used for money laundering and public extortion fundraising activities with respect to virtual assets.

[0048] However, the business activities that a virtual asset business operator may undertake with respect to virtual assets are not limited to those described above.

[0049] In this specification, the virtual asset address refers to a unique identification number electronically generated for managing the transmission record and storage details of the virtual asset. However, the virtual asset address may be referred to as a wallet address, an electronic wallet address, or a virtual asset wallet address, and is not limited to the above.

[0050] In this specification, the auxiliary virtual asset address is a unique identification number for distinguishing a user's account, and its existence may differ depending on the type of virtual asset. That is, the auxiliary virtual asset address may be used to distinguish different virtual asset types for the same user's account. For example, depending on the type of virtual asset owned by the user, there may be one or more auxiliary virtual asset addresses corresponding to one account of the user. However, the auxiliary virtual asset address may be referred to as a secondary address, destination tag, tag, memo, message, or the like, and is not limited to the above.

[0051] Hereinafter, the embodiments of the present specification will be described in detail with reference to the drawings.

[0052] FIG. 1 illustrates a system according to one embodiment.

[0053] Referring to Fig. 1, the system may include at least one of an electronic device 100, a receiving virtual asset business server 120, a remittance virtual asset business server 140, a user terminal 160, and a network 180. Meanwhile, the system illustrated in Fig. 1 illustrates only components related to the present embodiment. Therefore, it can be understood by a person having ordinary skill in the art of the present embodiment that other general components may be further included in addition to the components illustrated in Fig. 1.

[0054] The electronic device 100 may act as an intermediary in verifying a remitter who transfers virtual assets or a recipient who receives virtual assets. For example, the electronic device 100 may send a verification request message including a hash value of a full name, a hash value of a date of birth (DOB), and a receiving virtual asset address to the receiving virtual asset business server 120 or the remittance virtual asset business server 140. Alternatively, the electronic device 100 may receive a response message including verification result information performed based on the verification request message from the receiving virtual asset business server 120 or the remittance virtual asset business server 140, and transmit the response message to the remittance virtual asset business server 140 or the receiving virtual asset business server 120.

[0055] Meanwhile, the electronic device 100 may include at least one of an enclave server existing inside the virtual asset business or an API (application programming interface) server existing outside the virtual asset business. Alternatively, the electronic device 100 may include, but is not limited to, an integrated server existing inside the virtual asset business. Alternatively, the electronic device 100 may be embodied as one entity combined with any one of the receiving virtual asset business server 120 or the sending virtual asset business server 140.

[0056] The beneficiary virtual asset business server 120 is a server that exists within the beneficiary virtual asset business and can provide users with services related to the sale, purchase, or transfer of virtual assets. For example, with respect to a virtual asset transfer service, the beneficiary virtual asset business server 120 can send a verification request for the remitter to the electronic device 100 or send a verification result for the beneficiary to the electronic device 100.

[0057] The remittance virtual asset business server 140 is a server that exists within a remittance virtual asset business and can provide users with services related to the sale, purchase, or transfer of virtual assets. For example, with respect to a virtual asset transfer service, the remittance virtual asset business server 140 can send a verification request for the recipient to the electronic device 100 or send a verification result for the remitter to the electronic device 100.

[0058] However, the receiving virtual asset business server 120 may represent a server or entity that exists separately outside the receiving virtual asset business, and the remittance virtual asset business server 140 may represent a server or entity that exists separately outside the remittance virtual asset business.

[0059] The user terminal 160 is a terminal used by each user, and the user can use his / her user terminal 160 to access the receiving virtual asset business operator or the services provided by the receiving virtual asset business operator through the network 180. For example, the user can sell, buy, or transfer virtual assets using an application installed on his / her user terminal 160.

[0060] The electronic device 100, the receiving virtual asset business server 120, the remittance virtual asset business server 140, and the user terminal 160 can communicate with each other within the network 180. The network 180 is a comprehensive data communication network that allows the constituent entities of each network shown in FIG. 1 to communicate smoothly with each other, including a local area network (LAN), a wide area network (WAN), a value added network (VAN), a mobile radio communication network, a satellite communication network, and combinations thereof, and can include wired Internet, wireless Internet, and mobile wireless communication networks. Wireless communication can be, for example, wireless LAN (Wi-Fi), Bluetooth, Bluetooth Low Energy (BLE), ZigBee, Wi-Fi direct (WFD), ultra wideband (UWB), infrared data association (IrDA), near field communication (NFC), etc., but is not limited thereto.

[0061] 2a-2b are diagrams illustrating a process in which an electronic device 100 verifies a payee or sender according to an embodiment.

[0062] According to one embodiment, a user can transfer virtual assets in his / her wallet managed by a remittance virtual asset business operator to his / her wallet managed by a receiving virtual asset business operator using the user terminal 160. That is, the account of the remittance virtual asset business operator that transfers the virtual assets (e.g., the remitter's account) and the account of the receiving virtual asset business operator that receives the virtual assets (e.g., the recipient's account) may correspond to the same person.

[0063] FIG. 2a illustrates a process in which the electronic device 100 verifies a beneficiary according to an embodiment. In this case, the electronic device 100 may refer to a server present within a remittance virtual asset business. For example, the electronic device 100 may be embodied within the remittance virtual asset business as one entity physically combined with the remittance virtual asset business server 140, in which case the electronic device 100 and the remittance virtual asset business server 140 may be understood to be functionally and logically separate. As another example, the electronic device 100 and the remittance virtual asset business server 140 may be embodied as entities present within the remittance virtual asset business that are functionally and logically separate as well as physically separate.

[0064] In step S200, the electronic device 100 may receive information regarding the transfer of virtual assets from the remittance virtual asset business server 140 according to an embodiment. For example, the remittance virtual asset business server 140 may receive at least a part of a value indicating the type of virtual assets that the user wishes to transfer, information on the receiving virtual asset business, or a receiving virtual asset address from the user terminal 160. Thereafter, the remittance virtual asset business server 140 may transmit at least a part of a value indicating the type of virtual assets, information on the receiving virtual asset business, the receiving virtual asset address, the remitter's name data, or the remitter's date of birth data to the electronic device 100. At this time, the remittance virtual asset business server 140 may also transmit a secondary virtual asset address to the electronic device 100 according to the type of virtual assets.

[0065] In step S205, the electronic device 100 may identify a hash value of the remitter's name and a hash value of the remitter's birth date according to an embodiment. For example, the electronic device 100 may generate a hash value of the remitter's name and a hash value of the remitter's birth date by hashing each of the remitter's name data and the remitter's birth date data received from the remittance virtual asset business server 140. In this case, the electronic device 100 may use the KECCAK-256 hash algorithm as a hash function or hash algorithm, but the hash algorithm used is not limited to the above.

[0066] On the other hand, when the electronic device 100 identifies the hash value of the remitter's name and the hash value of the remitter's date of birth, it can be understood as confirming the hash value of the remitter's name and the hash value of the remitter's date of birth, or obtaining the hash value of the remitter's name and the hash value of the remitter's date of birth.

[0067] According to an embodiment, the electronic device 100 may hash the remitter's name data to generate a hash value set of the remitter's name including one or more hash values ​​of the remitter's name. For example, the electronic device 100 may hash the remitter's name information configured as a single entry in the order of first name and last name to generate a hash value, or may hash the remitter's name information configured as a single entry in the order of last name and first name to generate a hash value. Alternatively, the electronic device 100 may hash the remitter's name in Korean to generate a hash value, or may hash the remitter's name in English to generate a hash value. This will be described in detail with reference to FIGS. 7a to 7d.

[0068] In step S210, the electronic device 100 may transmit a verification request message to the receiving virtual asset business server 120 according to an embodiment. For example, the electronic device 100 may transmit a verification request message to the receiving virtual asset business server 120, including at least a part of an identification value of the verification request message, a value indicating the type of the verification target, a value indicating the type of the virtual asset, information on the remittance virtual asset business operator, a receiving virtual asset address, a hash value of the remitter's name, a hash value of the remitter's date of birth, or a hash salt value. In this case, the electronic device 100 may also transmit an auxiliary virtual asset address to the receiving virtual asset business server 120 according to the type of virtual asset. Specific contents of the values ​​included in the verification request message will be described in detail with reference to FIG. 5A to FIG. 5B.

[0069] In step S215, the receiving virtual asset business server 120 may verify whether the remitter and the recipient are the same according to an embodiment. For example, the receiving virtual asset business server 120 may identify the recipient's name data and the recipient's date of birth data corresponding to the receiving virtual asset address, and generate a hash value of the recipient's name and a hash value of the recipient's date of birth by hashing the recipient's name data and the recipient's date of birth data, respectively. Thereafter, the receiving virtual asset business server 120 may check whether the hash value of the remitter's name received from the electronic device 100 is the same as the hash value of the recipient's name, and whether the hash value of the remitter's date of birth received from the electronic device 100 is the same as the hash value of the recipient's date of birth.

[0070] According to an embodiment, the receiving virtual asset business server 120 may check whether there is an address that matches the receiving virtual asset address or the auxiliary virtual asset address. For example, the receiving virtual asset business server 120 may check whether there is an address in the database that matches the receiving virtual asset address received from the electronic device 100. Alternatively, if the receiving virtual asset business server 120 also receives the auxiliary virtual asset address from the electronic device 100, the receiving virtual asset business server 120 may check whether there are addresses in the database that match the receiving virtual asset address and the auxiliary virtual asset address.

[0071] According to one embodiment, the receiving virtual asset business server 120 can check whether there is an address that matches the receiving virtual asset address or the auxiliary virtual asset address, regardless of whether at least one character included in the receiving virtual asset address or the auxiliary virtual asset address is in lowercase or uppercase. This can provide a technical effect of preventing unintended mismatches that may occur due to case discrimination.

[0072] According to one embodiment, the receiving virtual asset business server 120 can remove a set prefix included in the receiving virtual asset address and check whether there is an address that matches the receiving virtual asset address. For example, the receiving virtual asset business server 120 can remove a prefix such as bitcoin cash or ecash included in the receiving virtual asset address and check whether there is an address that matches the receiving virtual asset address. This can provide a technical effect of preventing unintended inconsistencies that may occur between a virtual asset business that removes a prefix and stores it according to the policy of the virtual asset business and a virtual asset business that stores it with the prefix.

[0073] According to one embodiment, the receiving virtual asset business server 120 can identify the recipient's name data and the recipient's date of birth data. For example, if it is confirmed that an address matching the receiving virtual asset address received from the electronic device 100 exists in the database, the receiving virtual asset business server 120 can identify the recipient's name data and the recipient's date of birth data corresponding to the receiving virtual asset address.

[0074] According to an embodiment, the receiving virtual asset business server 120 may check whether the hash value of one or more names of the remitter matches the hash value of one or more names of the recipient. For example, the receiving virtual asset business server 120 may receive a hash value of one remitter's name from the electronic device 100 and check whether the hash value of one remitter's name matches the hash value of one recipient's name. Alternatively, the receiving virtual asset business server 120 may receive a hash value set of remitter's names including one or more hash values ​​of remitter's names from the electronic device 100 and check whether the hash value of one recipient's name matches any one of the hash values ​​of one or more names of the remitter. The receiving virtual asset business server 120 may receive a hash value of one remitter's name from the electronic device 100 and check whether the hash value of one remitter's name matches any one of the hash values ​​of one or more names of the recipient. This will be described in detail with reference to FIG. 7a to FIG. 7d.

[0075] According to one embodiment, the method of verifying the payee may be based on a hash value of information other than the date of birth. For example, the electronic device 100 may identify a hash value of the remitter's mobile phone number generated based on the remitter's mobile phone number data, and the receiving virtual asset business server 120 may check whether or not the hash value of the payee's mobile phone number matches. However, the type of information that may be used to verify the payee is not limited to the above.

[0076] According to an embodiment, the receiving virtual asset business server 120 can verify whether the sender and the recipient match regardless of the type of virtual asset. For example, the value indicating the type of virtual asset included in the verification request message may be LUNA2, and the type of virtual asset held by the receiving virtual asset business server 120 may be LUNA, and there may be no value matching LUNA2. In this case, the receiving virtual asset business server 120 can verify whether the sender and the recipient match without checking whether there is a value matching the value indicating the type of virtual asset. This can provide a technical effect of preventing unintended mismatches that may occur due to the absence of a standard name for the value or symbol indicating the type of virtual asset.

[0077] In step S220, the electronic device 100 may receive a response message including information on the result of the verification performed based on the verification request message from the receiving virtual asset business server 120 according to an embodiment. For example, the electronic device 100 may receive a response message including at least some of the following information from the receiving virtual asset business server 120: information indicating that an address matching the receiving virtual asset address or the auxiliary virtual asset address is not confirmed, information on a mismatch between the hash value of the remitter's name and the hash value of the recipient's name, information on a mismatch between the hash value of the remitter's date of birth and the hash value of the recipient's date of birth, or information indicating that the recipient is verified to match the remitter. This will be described in detail with reference to FIG. 6.

[0078] In step S225, according to an embodiment, the electronic device 100 may send a response message to the remittance virtual asset business server 140. For example, the electronic device 100 may send the response message received from the receiving virtual asset business server 120 to the remittance virtual asset business server 140.

[0079] In step S230, the remittance virtual asset business server 140 may transfer the virtual assets to the receiving virtual asset address based on the verification result information included in the received response message. For example, if the response message received from the electronic device 100 includes information indicating that the recipient is verified to match the remitter, the remittance virtual asset business server 140 may transfer the virtual assets to the receiving virtual asset address based on the information received from the user terminal 160. Alternatively, if the response message received from the electronic device 100 includes information other than information indicating that the recipient is verified to match the remitter (e.g., information indicating that an address matching the receiving virtual asset address or the auxiliary virtual asset address is not confirmed, information regarding a mismatch between the hash value of the remitter's name and the hash value of the recipient's name, or information regarding a mismatch between the hash value of the remitter's date of birth and the hash value of the recipient's date of birth), the remittance virtual asset business server 140 may not transfer the virtual assets to the receiving virtual asset address.

[0080] FIG. 2b illustrates a process in which the electronic device 100 verifies a remitter (originator) according to an embodiment. In this case, the electronic device 100 may refer to a server existing within a receiving virtual asset business. For example, the electronic device 100 may be embodied within the receiving virtual asset business as one entity physically combined with the receiving virtual asset business server 120, in which case the electronic device 100 and the receiving virtual asset business server 120 may be understood to be functionally and logically separate. As another example, the electronic device 100 and the receiving virtual asset business server 120 may be embodied as entities that exist within the receiving virtual asset business but are not only functionally and logically separate but also physically separate. In the description of FIG. 2b, the contents that overlap with the description of FIG. 2a will be briefly described or omitted.

[0081] In step S250, the receiving virtual asset business server 120 may identify the virtual assets transferred to the receiving virtual asset address according to an embodiment. For example, the receiving virtual asset business server 120 may identify the virtual assets or deposit transferred to the receiving virtual asset address by the remittance virtual asset business server 140. However, the receiving virtual asset business server 120 may not reflect the transferred virtual assets in the current status of the payee's balance that the payee can check through the payee's account before the remitter's verification is completed.

[0082] In step S255, according to an embodiment, the electronic device 100 may receive information regarding the transfer of virtual assets from the receiving virtual asset business server 120. For example, the electronic device 100 may receive at least a part of a value indicating the type of virtual assets, information regarding the receiving virtual asset business, a receiving virtual asset address, a recipient's name data, or a recipient's date of birth data from the electronic receiving virtual asset business server 120. In this case, the receiving virtual asset business server 120 may also transmit a secondary virtual asset address to the electronic device 100 according to the type of virtual assets.

[0083] In step S260, the electronic device 100 may identify a hash value of the recipient's name and a hash value of the recipient's birth date according to an embodiment. For example, the electronic device 100 may hash the recipient's name data and the recipient's birth date data received from the receiving virtual asset business server 120 to generate a hash value of the recipient's name and a hash value of the recipient's birth date.

[0084] According to an embodiment, the electronic device 100 may hash the recipient's name data to generate a hash value set of the recipient's name including one or more hash values ​​of the recipient's name. For example, the electronic device 100 may hash the recipient's name information configured in a single entry in the order of first name and last name to generate a hash value, or may hash the recipient's name information configured in a single entry in the order of last name and first name to generate a hash value. Alternatively, the electronic device 100 may hash the recipient's name in Korean to generate a hash value, or may hash the recipient's name in English to generate a hash value. This will be described in detail with reference to FIGS. 7a to 7d.

[0085] In step S265, the electronic device 100 may transmit a verification request message to the remittance virtual asset business server 140 according to an embodiment. For example, the electronic device 100 may transmit a verification request message to the remittance virtual asset business server 140, including at least a part of the identification value of the verification request message, a value indicating the type of the verification target, a value indicating the type of the virtual asset, information on the receiving virtual asset business, the receiving virtual asset address, the hash value of the recipient's name, the hash value of the recipient's birth date, the hash salt value, or a transaction identification value corresponding to the transfer of the virtual asset. In this case, the electronic device 100 may also transmit the auxiliary virtual asset address to the remittance virtual asset business server 140 according to the type of the virtual asset. Specific contents of the values ​​included in the verification request message will be described in detail with reference to FIG. 5A to FIG. 5B.

[0086] In step S270, the remittance virtual asset business server 140 may verify whether the recipient and the remitter match according to an embodiment. For example, the remittance virtual asset business server 140 may identify the remitter's name data and the remitter's date of birth data corresponding to the receiving virtual asset address or the transaction identification value, and generate a hash value of the remitter's name and a hash value of the remitter's date of birth by hashing the remitter's name data and the remitter's date of birth data, respectively. Thereafter, the remittance virtual asset business server 140 may check whether the hash value of the recipient's name received from the electronic device 100 matches the hash value of the remitter's name and whether the hash value of the recipient's date of birth received from the electronic device 100 matches the hash value of the remitter's date of birth.

[0087] According to an embodiment, the remittance virtual asset business server 140 may check whether there is a value that matches the transaction identification value. For example, the remittance virtual asset business server 140 may check whether there is a value in the database that matches the transaction identification value received from the electronic device 100.

[0088] According to one embodiment, the remittance virtual asset business server 140 can check whether there is a value that matches the transaction identification value regardless of whether at least one character included in the transaction identification value is lowercase or uppercase. This can provide a technical effect of preventing unintended mismatches that may occur due to case discrimination.

[0089] According to an embodiment, when the type of the transaction identification value includes an identifier type and a hash value type, the remittance virtual asset business server 140 may check whether there is a value that matches the transaction identification value using the transaction identification value of the hash value type. For example, when the transaction identification value of the identifier type and the transaction identification value of the hash value type are different, the remittance virtual asset business server 140 may check whether there is a value that matches the transaction identification value using the transaction identification value of the hash value type. This can provide a technical effect of preventing unintended inconsistencies that may occur between a virtual asset business requesting verification and a virtual asset business performing verification.

[0090] According to an embodiment, the remittance virtual asset business server 140 may check whether there is a value that matches the transaction identification value using a transaction identification value including a leading zero value. For example, if the transaction identification value is 0.0.15852-1648154322-083000000, the remittance virtual asset business server 140 may check whether there is a value that matches the transaction identification value using a transaction identification value including 83000000. This provides a technical effect of preventing unintended inconsistencies that may occur between a virtual asset business that removes leading zero values ​​and stores the virtual asset according to the policy of the virtual asset business and a virtual asset business that includes leading zero values ​​and stores the virtual asset.

[0091] According to one embodiment, the remittance virtual asset business server 140 may check whether there is an address that matches the receiving virtual asset address or the auxiliary virtual asset address. For example, the remittance virtual asset business server 140 may check whether there is an address in the database that matches the receiving virtual asset address received from the electronic device 100. Alternatively, if the remittance virtual asset business server 140 also receives the auxiliary virtual asset address from the electronic device 100, the remittance virtual asset business server 140 may check whether there are addresses in the database that match the receiving virtual asset address and the auxiliary virtual asset address.

[0092] According to one embodiment, the remittance virtual asset business server 140 can identify the sender's name data and the sender's date of birth data. For example, if it is confirmed that a value matching the transaction identification value and an address matching the receiving virtual asset address received from the electronic device 100 exist in the database, the remittance virtual asset business server 140 can identify the sender's name data and the sender's date of birth data corresponding to the transaction identification value or the receiving virtual asset address.

[0093] According to an embodiment, the remittance virtual asset business server 140 may check whether the hash value of one or more names of the recipient matches the hash value of one or more names of the remitter. For example, the remittance virtual asset business server 140 may receive a hash value of one recipient's name from the electronic device 100 and check whether the hash value of one recipient's name matches the hash value of one remitter's name. Alternatively, the remittance virtual asset business server 140 may receive a hash value set of recipient's names including one or more hash values ​​of recipient's names from the electronic device 100 and check whether the hash value of one remitter's name matches any one of the hash values ​​of one or more names of the recipient. The remittance virtual asset business server 140 may receive a hash value of one recipient's name from the electronic device 100 and check whether the hash value of one recipient's name matches any one of the hash values ​​of one or more names of the remitter. This will be described in detail with reference to FIG. 7a to FIG. 7d.

[0094] According to one embodiment, the method for verifying the remitter may be based on a hash value of information other than the date of birth. For example, the electronic device 100 may identify a hash value of the recipient's mobile phone number generated based on the recipient's mobile phone number data, and the remittance virtual asset business server 140 may check whether the hash value matches the hash value of the remitter's mobile phone number. However, the type of information that may be used to verify the remitter is not limited to the above.

[0095] According to one embodiment, the remittance virtual asset business server 140 can verify whether the recipient and the remitter match regardless of the type of virtual asset. For example, the value indicating the type of virtual asset included in the verification request message may be LUNA, and the type of virtual asset held by the remittance virtual asset business server 140 may be LUNA2, etc., and there may be no value matching LUNA. In this case, the remittance virtual asset business server 140 can verify whether the recipient and the remitter match without checking whether there is a value matching the value indicating the type of virtual asset. This can provide a technical effect of preventing unintended mismatches that may occur due to the absence of a standard name for the value or symbol indicating the type of virtual asset.

[0096] Meanwhile, in one embodiment, the remittance virtual asset business server 140 may identify the remitter's name data and the remitter's date of birth data using the remittance virtual asset address, rather than the transaction identification value or the receiving virtual asset address. For example, in step S250, the receiving virtual asset business server 120 may identify the remitted virtual asset and then identify the remittance virtual asset address. In step S255, the receiving virtual asset business server 120 may transmit information regarding the transfer of virtual assets, including the remittance virtual asset address, to the electronic device 100, and in step S265, the electronic device 100 may transmit a verification request message including the remittance virtual asset address to the remittance virtual asset business server 140. The remittance virtual asset business server 140 may identify the remitter's name data and the remitter's date of birth data corresponding to the received remittance virtual asset address.

[0097] In step S275, the electronic device 100 may receive a response message including verification result information performed based on the verification request message according to an embodiment from the remittance virtual asset business server 140. For example, the electronic device 100 may receive a response message including at least some of the following information from the remittance virtual asset business server 140: information indicating that a value matching the transaction identification value is not confirmed, information indicating that an address matching the receiving virtual asset address or the auxiliary virtual asset address is not confirmed, information regarding a mismatch between the hash value of the recipient's name and the hash value of the remitter's name, information regarding a mismatch between the hash value of the recipient's birth date and the hash value of the remitter's birth date, or information indicating that the remitter is verified to match the recipient. This will be described in detail with reference to FIG. 6.

[0098] In step S280, the electronic device 100 may transmit a response message to the receiving virtual asset business server 120 according to an embodiment. For example, the electronic device 100 may transmit the response message received from the remittance virtual asset business server 140 to the receiving virtual asset business server 120.

[0099] In step S285, the receiving virtual asset business server 120 may reflect the virtual assets transferred to the payee's virtual asset address in the balance of the receiving virtual asset address based on the verification result information included in the response message according to an embodiment. For example, if the response message received from the electronic device 100 includes information indicating that the remitter is verified to match the payee, the receiving virtual asset business server 120 may reflect the transferred virtual assets in the balance of the receiving virtual asset address at set time intervals or each time the response message is received. Alternatively, if the response message received from the electronic device 100 includes information other than information indicating that the sender has been verified to match the recipient (e.g., at least some of the following information: information indicating that a value matching the transaction identification value has not been confirmed, information indicating that an address matching the sending virtual asset address or the auxiliary virtual asset address has not been confirmed, information regarding a mismatch between the hash value of the sender's name and the hash value of the recipient's name, or information regarding a mismatch between the hash value of the sender's date of birth and the hash value of the recipient's date of birth), the receiving virtual asset business server 120 may not reflect the transferred virtual assets in the balance of the receiving virtual asset address.

[0100] 3a-3b are diagrams illustrating a process in which the electronic device 100 verifies a payee or remitter according to an embodiment. In the description of FIG. 3a-3b, the contents that overlap with the description of FIG. 2a-2b will be briefly described or omitted.

[0101] According to one embodiment, a user can transfer virtual assets in his / her wallet managed by a remittance virtual asset business operator to his / her wallet managed by a receiving virtual asset business operator using the user terminal 160. That is, the account of the remittance virtual asset business operator that transfers the virtual assets (e.g., the remitter's account) and the account of the receiving virtual asset business operator that receives the virtual assets (e.g., the recipient's account) can correspond to the same person.

[0102] 3A illustrates a process in which the electronic device 100 verifies a recipient according to an embodiment. In this case, the enclave server 102 may communicate with the API server 104 as a server existing inside the remittance virtual asset business, and the API server 104 may act as a message mediator as a server existing outside the remittance virtual asset business. Meanwhile, the electronic device 100 may represent the enclave server 102 or the API server 104.

[0103] In step S300, the enclave server 102 may receive information regarding the transfer of virtual assets from the remittance virtual asset business server 140 according to an embodiment. For example, the remittance virtual asset business server 140 may receive at least a part of a value indicating the type of virtual assets that the user wishes to transfer, information on the receiving virtual asset business, or a receiving virtual asset address from the user terminal 160. Thereafter, the remittance virtual asset business server 140 may transmit at least a part of a value indicating the type of virtual assets, information on the receiving virtual asset business, the receiving virtual asset address, the remitter's name data, or the remitter's date of birth data to the enclave server 102. At this time, the remittance virtual asset business server 140 may also transmit a sub-virtual asset address to the enclave server 102 according to the type of virtual assets.

[0104] In step S305, the enclave server 102 may identify a hash value of the remitter's name and a hash value of the remitter's date of birth according to an embodiment. For example, the enclave server 102 may hash the remitter's name data and the remitter's date of birth data received from the remittance virtual asset business server 140 to generate a hash value of the remitter's name and a hash value of the remitter's date of birth.

[0105] In step S310, the enclave server 102 may transmit a request for verification of the recipient and related information to the API server 104 according to an embodiment. For example, the enclave server 102 may transmit at least a part of a value indicating the type of the object to be verified, a value indicating the type of the virtual asset, information on the recipient virtual asset business operator, a recipient virtual asset address, a hash value of the remitter's name, a hash value of the remitter's date of birth, or a hash salt value to the API server 104. In this case, the enclave server 102 may also transmit an auxiliary virtual asset address to the API server 104 according to the type of the virtual asset.

[0106] In step S315, the API server 104 may transmit a verification request message to the receiving virtual asset business server 120 according to an embodiment. For example, the API server 104 may transmit a verification request message to the receiving virtual asset business server 120, including at least a part of an API access key, an identification value of the verification request message, a value indicating the type of the verification target, a value indicating the type of the virtual asset, information on the remittance virtual asset business operator, a receiving virtual asset address, a hash value of the remitter's name, a hash value of the remitter's date of birth, or a hash salt value. In this case, the API server 104 may also transmit a sub-virtual asset address to the receiving virtual asset business server 120 according to the type of virtual asset. Specific contents of the values ​​included in the verification request message will be described in detail with reference to FIG. 5A to FIG. 5B.

[0107] In step S320, the receiving virtual asset business server 120 may verify whether the remitter and the recipient are the same according to an embodiment. For example, the receiving virtual asset business server 120 may identify the recipient's name data and the recipient's date of birth data corresponding to the receiving virtual asset address, and generate a hash value of the recipient's name and a hash value of the recipient's date of birth by hashing the recipient's name data and the recipient's date of birth data, respectively. Thereafter, the receiving virtual asset business server 120 may check whether the hash value of the remitter's name received from the API server 104 matches the hash value of the recipient's name and whether the hash value of the remitter's date of birth received from the API server 104 matches the hash value of the recipient's date of birth. A more detailed operation of the receiving virtual asset business server 120 verifying whether the remitter and the recipient are the same will be omitted since it overlaps with the contents described in step S215 of FIG. 2.

[0108] In step S325, the API server 104 may receive a response message including information on the result of the verification performed based on the verification request message from the receiving virtual asset business server 120 according to an embodiment. For example, the API server 104 may receive a response message including at least some of the following information from the receiving virtual asset business server 120: information indicating that an address matching the receiving virtual asset address or the auxiliary virtual asset address is not confirmed, information on a mismatch between the hash value of the remitter's name and the hash value of the recipient's name, information on a mismatch between the hash value of the remitter's date of birth and the hash value of the recipient's date of birth, or information indicating that the recipient is verified to match the remitter. This will be described in detail with reference to FIG. 6.

[0109] In step S330, the API server 104 may send a response message to the enclave server 102 according to an embodiment. For example, the API server 104 may send the response message received from the recipient virtual asset business server 120 to the enclave server 102.

[0110] In step S335, the enclave server 102 may send a response message to the remittance virtual asset business server 140 according to an embodiment. For example, the enclave server 102 may send the response message received from the API server 104 to the remittance virtual asset business server 140.

[0111] In step S340, the remittance virtual asset business server 140 may transfer the virtual assets to the receiving virtual asset address based on the verification result information included in the received response message. For example, if the response message received from the enclave server 102 includes information indicating that the recipient is verified to match the remitter, the remittance virtual asset business server 140 may transfer the virtual assets to the receiving virtual asset address based on the information received from the user terminal 160. Alternatively, if the response message received from the enclave server 102 includes information other than information indicating that the recipient is verified to match the remitter, the remittance virtual asset business server 140 may not transfer the virtual assets to the receiving virtual asset address.

[0112] 3B illustrates a process in which the electronic device 100 verifies a remitter according to an embodiment. In this case, the enclave server 106 may communicate with the API server 108 as a server existing inside the receiving virtual asset business, and the API server 108 may act as a message mediator as a server existing outside the receiving virtual asset business. Meanwhile, the electronic device 100 may represent the enclave server 106 or the API server 108.

[0113] In step S350, the receiving virtual asset business server 120 may identify the virtual assets transferred to the receiving virtual asset address according to an embodiment. For example, the receiving virtual asset business server 120 may identify the virtual assets or deposits transferred to the receiving virtual asset address by the remittance virtual asset business server 140.

[0114] In step S355, the enclave server 106 may receive information regarding the transfer of virtual assets from the receiving virtual asset business server 120 according to an embodiment. For example, the enclave server 106 may receive at least a part of a value indicating the type of virtual assets, information regarding the receiving virtual asset business, a receiving virtual asset address, a recipient's name data, or a recipient's date of birth data from the electronic receiving virtual asset business server 120. In this case, the receiving virtual asset business server 120 may also transmit a secondary virtual asset address to the enclave server 106 according to the type of virtual assets.

[0115] In step S360, the enclave server 106 may identify a hash value of the recipient's name and a hash value of the recipient's date of birth according to an embodiment. For example, the enclave server 106 may hash the recipient's name data and the recipient's date of birth data received from the receiving virtual asset business server 120 to generate a hash value of the recipient's name and a hash value of the recipient's date of birth.

[0116] In step S365, the enclave server 106 may send the sender's verification request and related information to the API server 108 according to an embodiment. For example, the enclave server 106 may send at least a part of the following to the API server 108: a value indicating the type of the verification target, a value indicating the type of the virtual asset, information on the recipient virtual asset business operator, the address of the recipient virtual asset, a hash value of the recipient's name, a hash value of the recipient's date of birth, a hash salt value, or a transaction identification value corresponding to the transfer of the virtual asset. In this case, the enclave server 106 may also send the auxiliary virtual asset address to the API server 108 according to the type of the virtual asset.

[0117] In step S370, the API server 108 may transmit a verification request message to the remittance virtual asset business server 140 according to an embodiment. For example, the electronic device 100 may transmit a verification request message to the remittance virtual asset business server 140, including at least a part of the API connection key, the identification value of the verification request message, the value indicating the type of the verification target, the value indicating the type of the virtual asset, information on the receiving virtual asset business, the receiving virtual asset address, the hash value of the recipient's name, the hash value of the recipient's date of birth, the hash salt value, or the transaction identification value corresponding to the transfer of the virtual asset. In this case, the API server 108 may also transmit the auxiliary virtual asset address to the remittance virtual asset business server 140 according to the type of the virtual asset. Specific contents of the values ​​included in the verification request message will be described in detail with reference to FIG. 5A to FIG. 5B.

[0118] In step S375, the remittance virtual asset business server 140 may verify whether the recipient and the remitter are the same according to an embodiment. For example, the remittance virtual asset business server 140 may identify the remitter's name data and the remitter's date of birth data corresponding to the receiving virtual asset address or the transaction identification value, and generate a hash value of the remitter's name and a hash value of the remitter's date of birth by hashing the remitter's name data and the remitter's date of birth data, respectively. Thereafter, the remittance virtual asset business server 140 may check whether the hash value of the recipient's name received from the electronic device 100 matches the hash value of the remitter's name and whether the hash value of the recipient's date of birth received from the electronic device 100 matches the hash value of the remitter's date of birth. A more detailed operation of the remittance virtual asset business server 140 verifying whether the recipient and the remitter are the same will be omitted since it overlaps with the contents described in step S270 of FIG. 2.

[0119] Meanwhile, in one embodiment, the remittance virtual asset business server 140 can identify the remitter's name data and the remitter's date of birth data using the remittance virtual asset address, rather than the transaction identification value or the receiving virtual asset address. For example, in step S350, the receiving virtual asset business server 120 can identify the remittance virtual asset address after identifying the transferred virtual asset. In step S355, the receiving virtual asset business server 120 can transmit information regarding the transfer of virtual assets, including the remittance virtual asset address, to the enclave server 106, and in step S365, the enclave server 106 can transmit related information, including the remittance virtual asset address, to the API server 108. The remittance virtual asset business server 140 can receive a verification request message including the remittance virtual asset address from the API server 108, and identify the remitter's name data and the remitter's date of birth data corresponding to the received remittance virtual asset address.

[0120] In step S380, the API server 108 may receive a response message including verification result information performed based on the verification request message according to an embodiment from the remittance virtual asset business server 140. For example, the API server 108 may receive a response message including at least some of the following information from the remittance virtual asset business server 140: information indicating that a value matching the transaction identification value is not confirmed, information indicating that an address matching the receiving virtual asset address or the auxiliary virtual asset address is not confirmed, information regarding a mismatch between the hash value of the recipient's name and the hash value of the remitter's name, information regarding a mismatch between the hash value of the recipient's date of birth and the hash value of the remitter's date of birth, or information indicating that the remitter is verified to match the recipient. This will be described in detail with reference to FIG. 6.

[0121] In step S385, the API server 108 may send a response message to the enclave server 106 according to an embodiment. For example, the API server 108 may send the response message received from the remittance virtual asset business server 140 to the enclave server 106.

[0122] In step S390, the enclave server 106 may send a response message to the recipient virtual asset business server 120 according to an embodiment. For example, the enclave server 106 may send the response message received from the API server 108 to the recipient virtual asset business server 120.

[0123] In step S395, the receiving virtual asset business server 120 may reflect the virtual assets transferred to the payee's virtual asset address in the balance of the receiving virtual asset address based on the verification result information included in the response message according to an embodiment. For example, if the response message received from the enclave server 106 includes information indicating that the sender is verified to match the payee, the receiving virtual asset business server 120 may reflect the transferred virtual assets in the balance of the receiving virtual asset address at set time intervals or each time a response message is received. Alternatively, if the response message received from the enclave server 106 includes information other than information indicating that the sender is verified to match the payee, the receiving virtual asset business server 120 may not reflect the transferred virtual assets in the balance of the receiving virtual asset address.

[0124] 4a-4b are diagrams illustrating a process in which the electronic device 100 verifies a payee or remitter according to an embodiment. In the description of FIG. 4a-4b, the contents that overlap with the description of FIG. 2a-2b will be briefly described or omitted.

[0125] According to one embodiment, a user can transfer virtual assets in his / her own wallet managed by a remittance virtual asset business operator to another person's wallet managed by a receiving virtual asset business operator using the user terminal 160. In other words, the remitter who transfers the virtual assets and the recipient who receives the virtual assets may be different.

[0126] 4a illustrates a process in which the electronic device 100 verifies a recipient according to an embodiment. In this case, the electronic device 100 may represent a server present within a remittance virtual asset business.

[0127] In step S400, the remittance virtual asset business server 140 may identify information regarding the transfer of virtual assets according to an embodiment. For example, the remittance virtual asset business server 140 may receive at least a part of a value indicating the type of virtual assets the user wishes to transfer, information regarding the recipient virtual asset business, the address of the recipient virtual asset, the recipient's name data, or the recipient's date of birth data from the user terminal 160.

[0128] In step S405, according to an embodiment, the electronic device 100 may receive information regarding the transfer of virtual assets from the remittance virtual asset business server 140. For example, the remittance virtual asset business server 140 may transmit at least a part of a value indicating the type of virtual assets, information regarding the receiving virtual asset business, the receiving virtual asset address, the recipient's name data, or the recipient's date of birth data to the electronic device 100. In this case, the remittance virtual asset business server 140 may also transmit a secondary virtual asset address to the electronic device 100 according to the type of virtual assets.

[0129] In step S410, the electronic device 100 may identify a hash value of the recipient's name and a hash value of the recipient's birth date according to an embodiment. For example, the electronic device 100 may hash the recipient's name data and the recipient's birth date data received from the remittance virtual asset business server 140 to generate a hash value of the recipient's name and a hash value of the recipient's birth date.

[0130] In step S415, the electronic device 100 may transmit a verification request message to the receiving virtual asset business server 120 according to an embodiment. For example, the electronic device 100 may transmit a verification request message to the receiving virtual asset business server 120, including at least a part of an identification value of the verification request message, a value indicating the type of the verification target, a value indicating the type of the virtual asset, information on the remittance virtual asset business operator, a receiving virtual asset address, a hash value of the recipient's name, a hash value of the recipient's date of birth, or a hash salt value. In this case, the electronic device 100 may also transmit an auxiliary virtual asset address to the receiving virtual asset business server 120 according to the type of virtual asset. Specific contents of the values ​​included in the verification request message will be described in detail with reference to FIG. 5A to FIG. 5B.

[0131] In step S420, the receiving virtual asset business server 120 may verify whether the recipients match according to an embodiment. More specifically, the receiving virtual asset business server 120 may verify whether the hash value for the recipient (or the first recipient) received from the electronic device 100 matches the hash value for the recipient (or the second recipient) corresponding to the receiving virtual asset address.

[0132] For example, the receiving virtual asset business server 120 can check the second recipient's name data and the second recipient's date of birth data corresponding to the receiving virtual asset address, and generate a hash value of the second recipient's name and a hash value of the second recipient's date of birth by hashing the second recipient's name data and the second recipient's date of birth data, respectively. Thereafter, the receiving virtual asset business server 120 can check whether the hash value of the first recipient's name received from the electronic device 100 matches the hash value of the second recipient's name and whether the hash value of the first recipient's date of birth received from the electronic device 100 matches the hash value of the second recipient's date of birth.

[0133] According to an embodiment, the receiving virtual asset business server 120 may check whether there is an address that matches the receiving virtual asset address or the auxiliary virtual asset address. For example, the receiving virtual asset business server 120 may check whether there is an address in the database that matches the receiving virtual asset address received from the electronic device 100. Alternatively, if the receiving virtual asset business server 120 also receives the auxiliary virtual asset address from the electronic device 100, the receiving virtual asset business server 120 may check whether there are addresses in the database that match the receiving virtual asset address and the auxiliary virtual asset address.

[0134] According to one embodiment, the receiving virtual asset business server 120 can identify the second recipient's name data and the second recipient's date of birth data. For example, if it is confirmed that an address matching the receiving virtual asset address received from the electronic device 100 exists in the database, the receiving virtual asset business server 120 can identify the second recipient's name data and the second recipient's date of birth data corresponding to the receiving virtual asset address.

[0135] According to an embodiment, the receiving virtual asset business server 120 may check whether the hash value of one or more names of the first recipient matches the hash value of one or more names of the second recipient. For example, the receiving virtual asset business server 120 may receive a hash value of one first recipient name from the electronic device 100 and check whether the hash value of one first recipient name matches the hash value of one second recipient name. Alternatively, the receiving virtual asset business server 120 may receive a hash value set of first recipient names including hash values ​​of multiple first recipient names from the electronic device 100 and check whether the hash value of one second recipient name matches any one of the hash values ​​of the multiple first recipient names. The receiving virtual asset business server 120 may receive a hash value of one first recipient name from the electronic device 100 and check whether the hash value of one first recipient name matches any one of the hash values ​​of the multiple second recipient names. This will be described in detail with reference to FIG. 7e to FIG. 7h.

[0136] In step S425, the electronic device 100 may receive a response message including information on the result of the verification performed based on the verification request message from the receiving virtual asset business server 120 according to an embodiment. For example, the electronic device 100 may receive a response message including at least some of information indicating that an address matching the receiving virtual asset address or the auxiliary virtual asset address is not confirmed, information on a mismatch in the hash value of the recipient's name, information on a mismatch in the hash value of the recipient's date of birth, or information indicating that the recipient is verified to be the same, from the receiving virtual asset business server 120. This will be described in detail with reference to FIG. 6.

[0137] In step S430, according to an embodiment, the electronic device 100 may send a response message to the remittance virtual asset business server 140. For example, the electronic device 100 may send the response message received from the receiving virtual asset business server 120 to the remittance virtual asset business server 140.

[0138] In step S435, the remittance virtual asset business server 140 may transfer the virtual assets to the receiving virtual asset address based on the verification result information included in the received response message. For example, if the response message received from the electronic device 100 includes information indicating that the recipient is verified to be the same, the remittance virtual asset business server 140 may transfer the virtual assets to the receiving virtual asset address based on the information received from the user terminal 160. Alternatively, if the response message received from the electronic device 100 includes information other than the information indicating that the recipient is verified to be the same, the remittance virtual asset business server 140 may not transfer the virtual assets to the receiving virtual asset address.

[0139] 4b illustrates a process in which the electronic device 100 verifies a recipient according to an embodiment. In this case, the electronic device 100 may represent a server present within the recipient virtual asset business.

[0140] In step S450, the receiving virtual asset business server 120 may identify the virtual assets transferred to the receiving virtual asset address according to an embodiment. For example, the receiving virtual asset business server 120 may identify the virtual assets or deposits transferred to the receiving virtual asset address by the remittance virtual asset business server 140.

[0141] In step S455, according to an embodiment, the electronic device 100 may receive information regarding the transfer of virtual assets from the receiving virtual asset business server 120. For example, the electronic device 100 may receive at least a part of a value indicating the type of virtual assets, information regarding the receiving virtual asset business, a receiving virtual asset address, a recipient's name data, or a recipient's date of birth data from the electronic receiving virtual asset business server 120. In this case, the receiving virtual asset business server 120 may also transmit a secondary virtual asset address to the electronic device 100 according to the type of virtual assets.

[0142] In step S460, the electronic device 100 may identify a hash value of the recipient's name and a hash value of the recipient's birth date according to an embodiment. For example, the electronic device 100 may hash the recipient's name data and the recipient's birth date data received from the receiving virtual asset business server 120 to generate a hash value of the recipient's name and a hash value of the recipient's birth date.

[0143] In step S465, the electronic device 100 may transmit a verification request message to the remittance virtual asset business server 140 according to an embodiment. For example, the electronic device 100 may transmit a verification request message to the remittance virtual asset business server 140, including at least a part of the identification value of the verification request message, a value indicating the type of the verification target, a value indicating the type of the virtual asset, information on the receiving virtual asset business, the receiving virtual asset address, a hash value of the recipient's name, a hash value of the recipient's date of birth, a hash salt value, or a transaction identification value corresponding to the transfer of the virtual asset. In this case, the electronic device 100 may also transmit the auxiliary virtual asset address to the receiving virtual asset business server 120 according to the type of the virtual asset. Specific contents of the values ​​included in the verification request message will be described in detail with reference to FIG. 5A to FIG. 5B.

[0144] In step S470, the remittance virtual asset business server 140 may verify whether the recipients match according to an embodiment. More specifically, the remittance virtual asset business server 140 may verify whether the hash value for the recipient (or the first recipient) received from the electronic device 100 matches the hash value for the recipient (or the second recipient) corresponding to the received virtual asset address or transaction identification value.

[0145] For example, the remittance virtual asset business server 140 may identify the second recipient's name data and the second recipient's date of birth data corresponding to the receiving virtual asset address or the transaction identification value, and generate a hash value of the second recipient's name and a hash value of the second recipient's date of birth by hashing the second recipient's name data and the second recipient's date of birth data, respectively. Thereafter, the remittance virtual asset business server 140 may check whether the hash value of the first recipient's name received from the electronic device 100 matches the hash value of the second recipient's name and whether the hash value of the first recipient's date of birth received from the electronic device 100 matches the hash value of the second recipient's date of birth.

[0146] At this time, the remittance virtual asset business server 140 may receive the second recipient's name data and the second recipient's date of birth data from the user terminal 160 before transferring the virtual assets, and store them in a database. More specifically, the user terminal 160 may acquire a user input for inputting the recipient's name data and date of birth data corresponding to the receiving virtual asset address to which the remitter intends to transfer the virtual assets, and may transmit the acquired recipient's name data and date of birth data to the remittance virtual asset business server 140. Thereafter, the remittance virtual asset business server 140 may store the received second recipient's name data and second recipient's date of birth data in a database, and generate a hash value of the second recipient's name and a hash value of the second recipient's date of birth by hashing the data.

[0147] According to an embodiment, the remittance virtual asset business server 140 may check whether there is a value that matches the transaction identification value. For example, the remittance virtual asset business server 140 may check whether there is a value in the database that matches the transaction identification value received from the electronic device 100.

[0148] According to one embodiment, the remittance virtual asset business server 140 may check whether there is an address that matches the receiving virtual asset address or the auxiliary virtual asset address. For example, the remittance virtual asset business server 140 may check whether there is an address in the database that matches the receiving virtual asset address received from the electronic device 100. Alternatively, if the remittance virtual asset business server 140 also receives the auxiliary virtual asset address from the electronic device 100, the remittance virtual asset business server 140 may check whether there are addresses in the database that match the receiving virtual asset address and the auxiliary virtual asset address.

[0149] According to one embodiment, the remittance virtual asset business operator server 140 can identify the second recipient's name data and the second recipient's date of birth data. For example, if it is confirmed that a value matching the transaction identification value and an address matching the receiving virtual asset address received from the electronic device 100 exist in the database, the remittance virtual asset business operator server 140 can identify the second recipient's name data and the second recipient's date of birth data corresponding to the transaction identification value or the receiving virtual asset address.

[0150] According to an embodiment, the remittance virtual asset business server 140 may check whether the hash value of one or more names of the first recipient matches the hash value of one or more names of the second recipient. For example, the remittance virtual asset business server 140 may receive a hash value of one first recipient name from the electronic device 100 and check whether the hash value of one first recipient name matches the hash value of one second recipient name. Alternatively, the remittance virtual asset business server 140 may receive a hash value set of the first recipient name including hash values ​​of multiple first recipient names from the electronic device 100 and check whether the hash value of one second recipient name matches any one of the hash values ​​of the first recipient names. The remittance virtual asset business server 140 may receive a hash value of one first recipient name from the electronic device 100 and check whether the hash value of one first recipient name matches any one of the hash values ​​of the second recipient names. This will be described in detail with reference to FIG. 7e to FIG. 7h.

[0151] In step S475, the electronic device 100 may receive a response message including verification result information performed based on the verification request message according to an embodiment from the remittance virtual asset business server 140. For example, the electronic device 100 may receive a response message including at least some of information indicating that a value matching the transaction identification value is not confirmed, information indicating that an address matching the receiving virtual asset address or the auxiliary virtual asset address is not confirmed, information regarding a mismatch in the hash value of the recipient's name, information regarding a mismatch in the hash value of the recipient's date of birth, or information indicating that the recipient is verified to be the same. This will be described in detail with reference to FIG. 6.

[0152] In step S480, the electronic device 100 may transmit a response message to the receiving virtual asset business server 120 according to an embodiment. For example, the electronic device 100 may transmit the response message received from the remittance virtual asset business server 140 to the receiving virtual asset business server 120.

[0153] In step S485, the receiving virtual asset business server 120 may reflect the virtual assets transferred to the recipient's virtual asset address in the balance of the receiving virtual asset address based on the verification result information included in the response message according to an embodiment. For example, if the response message received from the electronic device 100 includes information indicating that the recipient is verified to be the same, the receiving virtual asset business server 120 may reflect the transferred virtual assets in the balance of the receiving virtual asset address at set time intervals or each time a response message is received. Alternatively, if the response message received from the electronic device 100 includes information other than information indicating that the recipient is verified to be the same, the receiving virtual asset business server 120 may not reflect the transferred virtual assets in the balance of the receiving virtual asset address.

[0154] 5a-5b illustrate example validation request messages 500, 550 according to one embodiment.

[0155] According to an embodiment, the verification request message 500, 550 may include a query parameter 510, 560, a header 520, 570, or a body 530, 580. In this case, data included in the query parameter 510, 560, the header 520, 570, and the body 530, 580 may be represented as a string type based on the JSON (JavaScript Object Notation) format, but is not limited to the above.

[0156] In one embodiment, the query parameters 510 , 560 may include an identification value of the validation request message 500 , 550 .

[0157] According to an embodiment, the identification value (reqID) of the verification request message 500, 550 may indicate a unique identification value assigned to each request message for reconciliation. For example, the identification value of the verification request message 500, 550 may be assigned to each verification request message 500, 550 sent by the electronic device 100 and may be used to distinguish the verification request messages 500, 550.

[0158] In one embodiment, the headers 520, 570 may include at least a portion of a value indicating the type of content, an API connection key, or information about the receiving virtual asset business or the sending virtual asset business.

[0159] According to one embodiment, a value indicating a content type (Content-Type) may indicate a format of data included in the verification request message 500, 550. For example, the value indicating the content type may be set to "application / json".

[0160] According to an embodiment, the API connection key (VASP-API-Key) may indicate a token sent by the electronic device 100 for approval when calling an API. For example, the electronic device 100 may request an API connection key at the same time as requesting the virtual asset business server to whitelist the IP address of the endpoint of the electronic device 100. Thus, the electronic device 100 may receive the API connection key from the virtual asset business server and generate a code for the virtual asset business.

[0161] According to an embodiment, the information on the receiving virtual asset business operator or the sending virtual asset business operator may indicate a counter party code (VASP-Counterparty-Code). For example, the virtual asset business operator code is a unique identification value for distinguishing virtual asset businesses, and may be registered in the system of the electronic device 100 in the process of receiving the API connection key.

[0162] According to one embodiment, the text 530, 580 may include at least a part of a value indicating the type of the verification target, a value indicating the type of the virtual asset, a receiving virtual asset address, a hash value of the sender's name, a hash value of the sender's date of birth, or a hash salt value. Alternatively, the text 530, 580 may include a transaction identification value corresponding to the transfer of the virtual asset according to the type of the verification target, and may include an auxiliary virtual asset address according to the type of the virtual asset.

[0163] According to an embodiment, the value indicating the type of the verification target (verificationType) may indicate whether the verification target is a remitter or a recipient. For example, if the verification target is a transfer, the value indicating the type of the verification target may include VerifyOriginator, and if the verification target is a receipt, the value indicating the type of the verification target may include VerifyBeneficiary. Thus, in FIG. 2a, the electronic device 100 may send a verification request message 500, 550 including VerifyBeneficiary to the receiving virtual asset business server 120, and in FIG. 2b, the electronic device 100 may send a verification request message 500, 550 including VerifyOriginator to the remittance virtual asset business server 140.

[0164] According to one embodiment, a transaction identification value (txID) corresponding to a virtual asset transfer may indicate a unique identification number given to each virtual asset transfer. For example, the transaction identification value may be used to identify a sender, a recipient, or a receiving virtual asset address corresponding to a virtual asset transfer.

[0165] Meanwhile, the inclusion or non-inclusion of the transaction identification value in the verification request message 500, 550 may be determined depending on the type of the verification target. More specifically, when the verification is performed after the virtual asset is transferred, the transaction identification value may be included in the verification request message 500, 550.

[0166] For example, the transaction identification value may be included in the verification request message 500, 550 when the type of the verification target is the remitter when the remitter who transfers the virtual asset and the recipient who receives the virtual asset are the same. Alternatively, the transaction identification value may be included in the verification request message 500, 550 when the remitter who transfers the virtual asset and the recipient who receives the virtual asset are different and the remittance virtual asset business server 140 verifies the recipient.

[0167] As another example, when the remitter who transfers the virtual asset and the recipient who receives the virtual asset are the same, the transaction identification value may not be included in the verification request message 500, 550 if the type of the verification target is the recipient. Alternatively, when the remitter who transfers the virtual asset and the recipient who receives the virtual asset are different, the transaction identification value may not be included in the verification request message 500, 550 if the receiving virtual asset business server 120 verifies the recipient. According to one embodiment, the value indicating the type of the virtual asset may indicate an abbreviation or symbol given to identify the unique name of the virtual asset, and may be mixed with a token ticker. For example, the value indicating the type of the virtual asset may include BTC, ETH, or XRP depending on the type of the virtual asset.

[0168] According to one embodiment, the receiving virtual asset address may indicate a wallet address to which the virtual assets managed by the receiving virtual asset business operator are deposited. In this case, regardless of whether the type of the verification target is a recipient or a remitter, the verification request message 500, 550 may include the receiving virtual asset address.

[0169] According to one embodiment, the auxiliary virtual asset address (tag) may indicate a secondary virtual asset address managed by the receiving virtual asset business operator to which the virtual asset is transferred. In this case, regardless of whether the type of the verification target is a recipient or a remitter, the verification request message 500, 550 may include the receiving auxiliary virtual asset address.

[0170] Meanwhile, the inclusion or exclusion of the auxiliary virtual asset address in the verification request message 500, 550 may be determined depending on the type of the virtual asset. For example, if the type of the virtual asset is Ripple (XRP), the auxiliary virtual asset address may be included in the verification request message 500, 550 as the name of the destination tag. Or, if the type of the virtual asset is EOS, Stellar Lumens (XLM), or MediBloc (MED), the auxiliary virtual asset address may be included in the verification request message 500, 550 as the name of the memo. If the type of the virtual asset is NEM (XEM) or Stellar Lumens (XLM), the auxiliary virtual asset address may be included in the verification request message 500, 550 as the name of the message.

[0171] According to an embodiment, the hash salt value may indicate an arbitrary character string used in the additional input when hashing the name data or the birth date data. In this case, the hash salt value should be a universally unique identifier (UUID) value that is arbitrarily generated for each request. For example, when hashing the name data or the birth date data, the electronic device 100 may generate a hash value of the name or the birth date by applying a hash salt value to each of the name data or the birth date data and then hashing the data.

[0172] According to an embodiment, the hash value of the date of birth (dobHash) may indicate a value generated by hashing the date of birth data of the recipient or remitter. For example, the electronic device 100 may hash the date of birth data in the format of "${YYYY}-${MM}-${DD},${hashSalt}" to generate a hash value of the date of birth in a string type encoded in hexadecimal with a length of 64 characters. In this case, in the case of a corporate account, the date of birth may be set in the form of "0000-00-00".

[0173] According to an embodiment, the name hash value (nameHashes) may indicate a value generated by hashing the name data of the payee or remitter. For example, if the name data is expressed in English, the electronic device 100 may hash the name data in a format of "${lowercase(FirstName)}${lowercase(LastName)},${hashSalt}" to generate a hash value of the date of birth as a string type encoded in hexadecimal with a length of 64 characters. Alternatively, if the name data is expressed in a local language, the electronic device 100 may hash the name data in a format of "${FirstName}${LastName},${hashSalt}" to generate a hash value of the date of birth as a string type encoded in hexadecimal with a length of 64 characters. In this case, the electronic device 100 may remove spaces included in the name data and convert at least one character included in the name data to lowercase before hashing the name data.

[0174] Meanwhile, the electronic device 100 may hash the full name data after converting it into various forms, so that the full name hash value may indicate a full name hash value set including one or more hash values. For example, the electronic device 100 may hash the full name information configured as a single entry in the order of first name and last name to generate a hash value, or may hash the full name information configured as a single entry in the order of last name and first name to generate a hash value. Alternatively, the electronic device 100 may hash the full name in Korean to generate a hash value, or may hash the full name in English to generate a hash value. This will be described in detail with reference to FIGS. 7a to 7h.

[0175] FIG. 5a illustrates a validation request message 500 according to one embodiment.

[0176] According to one embodiment, the verification request message 500 may include UPBT001KR as the code of the relative virtual asset business operator.

[0177] According to one embodiment, the verification request message 500 may include VerifyOriginator as a value indicating the type of verification target, and may thus include a transaction identification value corresponding to the transfer of virtual assets.

[0178] According to one embodiment, the validation request message 500 may include EHT as a value indicating the type of virtual asset, and may therefore not include a secondary virtual asset address.

[0179] According to one embodiment, the verification request message 500 may include four hash values ​​as the hash value of the name.

[0180] FIG. 5b illustrates a validation request message 550 according to one embodiment.

[0181] According to one embodiment, the verification request message 550 may include UPBT001KR as the code of the counterpart virtual asset business operator.

[0182] According to one embodiment, the verification request message 550 may include VerifyOriginator as a value indicating the type of verification target, and may thus include a transaction identification value corresponding to the transfer of virtual assets.

[0183] According to one embodiment, the validation request message 550 may include XRP as a value indicating the type of virtual asset, and may therefore include 76188721 as a secondary virtual asset address.

[0184] In one embodiment, the verification request message 550 may include four hash values ​​of the name.

[0185] FIG. 6 illustrates an example of a response message 600 according to one embodiment.

[0186] According to one embodiment, the response message may include a header 620 or a body 640. In this case, the data included in the header 620 and the body 640 may be represented as a string type based on the JSON format, but is not limited to the above.

[0187] In one embodiment, the header 620 may include a value indicating the type of content.

[0188] According to an embodiment, a value indicating a content type (Content-Type) may indicate a format of data included in the verification request message. For example, the value indicating the content type may be set to “application / json”.

[0189] In one embodiment, the body 640 may include validation result information.

[0190] According to an embodiment, the verification result information (verificationResult) may indicate a verification decision value of the sender or the recipient made based on the verification request message. For example, the verification result information may include a value (TXID-NOT-FOUND) indicating that a value matching the transaction identification value is not confirmed, a value (MISMATCH-ADDRESS) indicating that an address matching the receiving virtual asset address or the auxiliary virtual asset address is not confirmed, a value (MISMATCH-NAME) indicating that the hash value of the name does not match, a value (MISMATCH-DOB) indicating that the hash value of the date of birth does not match, or a value (VERIFIED) indicating that the sender or the recipient has been verified.

[0191] In this case, if one or more mismatches are found, the verification result information may include a value indicating one or more mismatches. For example, the verification result information may include MISMATCH-NAME and MISMATCH-DOB.

[0192] Referring to FIG. 6, a response message 600 may include VERIFIED as verification result information according to one embodiment.

[0193] 7a to 7h are diagrams illustrating a process in which the virtual asset business server 120, 140 checks whether the hash values ​​of names match, according to an embodiment.

[0194] Referring to FIG. 7a, the virtual asset business server 120, 140 may check whether a hash value of one remitter's name matches a hash value of one receiver's name according to an embodiment. For example, the electronic device 100 or the virtual asset business server 120, 140 may generate a hash value of one remitter's name by converting the remitter's name data in a set manner and then hashing the data. Also, the virtual asset business server 120, 140 or the electronic device 100 may generate a hash value of one receiver's name by converting the receiver's name data in a set manner and then hashing the data. Thereafter, if the hash value of one remitter's name matches a hash value of one receiver's name, the virtual asset business server 120, 140 may check that the receiver's and remitter's names match.

[0195] According to an embodiment, the electronic device 100 or the virtual asset business server 120, 140 may convert the name data in a common manner and then hash the name data. For example, the electronic device 100 or the virtual asset business server 120, 140 may remove spaces included in the name data and convert at least one character included in the name data to lowercase before hashing the name data. Alternatively, the electronic device 100 or the virtual asset business server 120, 140 may convert the name data into English before hashing it. If the name data includes a middle name, the electronic device 100 or the virtual asset business server 120, 140 may remove the middle name and convert the name data in the order of first name and last name before hashing it. However, the manner in which the electronic device 100 or the virtual asset business server 120, 140 converts the name data for hashing is not limited to the above.

[0196] Meanwhile, the operation of hashing the name data may correspond to the operation of the electronic device 100 hashing the name data of the remitter at step S205 of FIG. 2a, the operation of the receiving virtual asset business server 120 hashing the name data of the recipient at step S215 of FIG. 2a, the operation of the electronic device 100 hashing the name data of the recipient at step S260 of FIG. 2b, or the operation of the remittance virtual asset business server 140 hashing the name data of the remitter at step S270 of FIG. 2b. In addition, the operation of hashing the name data may correspond to the operation of the enclave server 102 hashing the sender's name data at step S305 of FIG. 3a, the operation of the receiving virtual asset business server 120 hashing the recipient's name data at step S320 of FIG. 3a, the operation of the enclave server 106 hashing the recipient's name data at step S360 of FIG. 3b, or the operation of the remittance virtual asset business server 140 hashing the sender's name data at step S375 of FIG. 3b.

[0197] Referring to FIG. 7b, the virtual asset business server 120, 140 may check whether a hash value of one payee's name matches one of the hash values ​​of the remitter's names according to an embodiment. For example, the electronic device 100 or the virtual asset business server 120, 140 may convert the remitter's name data in various ways and then hash the data to generate a hash value set of the remitter's name including the hash values ​​of the remitter's names. In addition, the virtual asset business server 120, 140 or the electronic device 100 may convert the payee's name data in a set way and then hash the data to generate a hash value of one payee's name. Thereafter, if a hash value of one payee's name matches one of the hash values ​​of the remitter's names, the virtual asset business server 120, 140 may check that the payee and remitter's names match.

[0198] According to an embodiment, the electronic device 100 or the virtual asset business server 120, 140 may convert the remitter's name data in various ways before hashing. For example, the electronic device 100 or the virtual asset business server 120, 140 may convert the remitter's name data into a single entry in the order of first name and last name, and may remove set characters including at least some of spaces or hyphens (-) included in the name data, and may perform hashing. Alternatively, the electronic device 100 or the virtual asset business server 120, 140 may convert the remitter's name data into multiple entries including a last name, a first name, and at least one middle name, and may convert the letter case of at least one character included in the name data into a set case (lowercase or uppercase), and may perform hashing. However, the manner in which the electronic device 100 or the virtual asset business server 120, 140 converts the remitter's name data for hashing is not limited to the above.

[0199] Meanwhile, the operation of hashing the remitter's name data may correspond to the operation of the electronic device 100 hashing the remitter's name data at step S205 of FIG. 2a, the operation of the remittance virtual asset business server 140 hashing the remitter's name data at step S270 of FIG. 2b, the operation of the enclave server 102 hashing the remitter's name data at step S305 of FIG. 3a, or the operation of the remittance virtual asset business server 140 hashing the remitter's name data at step S375 of FIG. 3b.

[0200] Referring to FIG. 7c, the virtual asset business server 120, 140 may check whether a hash value of one remitter's name matches one of the hash values ​​of the recipient's names according to an embodiment. For example, the electronic device 100 or the virtual asset business server 120, 140 may convert the recipient's name data in various ways and then hash the data to generate a hash value set of the recipient's name including the hash values ​​of the recipient's names. Also, the virtual asset business server 120, 140 or the electronic device 100 may convert the remitter's name data in a set way and then hash the data to generate a hash value of one remitter's name. Thereafter, if a hash value of one remitter's name matches one of the hash values ​​of the recipient's names, the virtual asset business server 120, 140 may check that the recipient and remitter's names match.

[0201] According to an embodiment, the electronic device 100 or the virtual asset business server 120, 140 may convert the recipient's name data in various ways before hashing. For example, the electronic device 100 or the virtual asset business server 120, 140 may convert the recipient's name data into a single entry in the order of last name and first name, remove spaces included in the name data, and convert at least one character included in the name data to lower case before hashing. Alternatively, the electronic device 100 or the virtual asset business server 120, 140 may combine the last name, first name, and at least one middle name included in the recipient's name data in various orders to convert them into multiple single entries, and convert at least one character included in the name data to lower case before hashing. However, the manner in which the electronic device 100 or the virtual asset business server 120, 140 converts the recipient's name data for hashing is not limited to the above.

[0202] Meanwhile, the operation of hashing the recipient's name data may correspond to the operation of the receiving virtual asset business server 120 hashing the recipient's name data at step S215 of FIG. 2a, the operation of the electronic device 100 hashing the recipient's name data at step S260 of FIG. 2b, the operation of the receiving virtual asset business server 120 hashing the recipient's name data at step S320 of FIG. 3a, or the operation of the enclave server 106 hashing the recipient's name data at step S360 of FIG. 3b.

[0203] Referring to FIG. 7d, the virtual asset business server 120, 140 may check whether one of the hash values ​​of the remitter's name matches one of the hash values ​​of the recipient's name according to an embodiment. For example, the electronic device 100 or the virtual asset business server 120, 140 may convert the remitter's name data in various ways and then hash the data to generate a hash value set of the remitter's name including the hash values ​​of the remitter's name. In addition, the virtual asset business server 120, 140 or the electronic device 100 may convert the recipient's name data in various ways and then hash the data to generate a hash value set of the recipient's name including the hash values ​​of the recipient's name. Thereafter, if the matching hash value among the hash values ​​of the remitter's name and the hash values ​​of the recipient's name is equal to or greater than a set value, the virtual asset business server 120, 140 may check that the recipient and remitter's names match.

[0204] According to an embodiment, the electronic device 100 or the virtual asset business server 120, 140 may hash the remitter's name data or the recipient's name data after converting them in various ways. A detailed operation of the electronic device 100 or the virtual asset business server 120, 140 hashing the name data is omitted since it overlaps with the contents described with reference to Figures 7a to 7c.

[0205] Meanwhile, the operation of hashing the remitter's name data may correspond to the operation of the electronic device 100 hashing the remitter's name data at step S205 of FIG. 2a, the operation of the remittance virtual asset business server 140 hashing the remitter's name data at step S270 of FIG. 2b, the operation of the enclave server 102 hashing the remitter's name data at step S305 of FIG. 3a, or the operation of the remittance virtual asset business server 140 hashing the remitter's name data at step S375 of FIG. 3b. In addition, the operation of hashing the recipient's name data may correspond to the operation of the receiving virtual asset business server 120 hashing the recipient's name data at step S215 of FIG. 2a, the operation of the electronic device 100 hashing the recipient's name data at step S260 of FIG. 2b, the operation of the receiving virtual asset business server 120 hashing the recipient's name data at step S320 of FIG. 3a, or the operation of the enclave server 106 hashing the recipient's name data at step S360 of FIG. 3b.

[0206] Referring to FIG. 7e, the virtual asset business server 120, 140 may check whether a hash value of one first recipient's name and a hash value of one second recipient's name match, according to an embodiment. For example, the electronic device 100 may generate a hash value of one first recipient's name by converting the first recipient's name data in a set manner and then hashing the data. Also, the virtual asset business server 120, 140 may generate a hash value of one second recipient's name by converting the second recipient's name data in a set manner and then hashing the data. Thereafter, if the hash value of one first recipient's name and the hash value of one second recipient's name match, the virtual asset business server 120, 140 may check that the recipient's names match.

[0207] According to an embodiment, the electronic device 100 or the virtual asset business server 120, 140 may convert the name data in a common manner and then hash the name data. A detailed operation of the electronic device 100 or the virtual asset business server 120, 140 to hash the name data is omitted since it overlaps with the contents described with reference to Figures 7a to 7c.

[0208] Meanwhile, the operation of hashing the name data may correspond to the operation of the electronic device 100 hashing the recipient's name data at step S410 of FIG. 4a, the operation of the receiving virtual asset business server 120 hashing the recipient's name data at step S420 of FIG. 4a, the operation of the electronic device 100 hashing the recipient's name data at step S460 of FIG. 4b, or the operation of the remittance virtual asset business server 140 hashing the recipient's name data at step S470 of FIG. 4b.

[0209] Referring to FIG. 7f, the virtual asset business server 120, 140 may check whether a hash value of one second recipient's name matches one of the hash values ​​of the first recipient's names according to an embodiment. For example, the electronic device 100 may convert the first recipient's name data in various ways and then hash the data to generate a hash value set of the first recipient's name including the hash values ​​of the first recipient's names. Also, the virtual asset business server 120, 140 may convert the second recipient's name data in a set way and then hash the data to generate a hash value of one second recipient's name. Then, if a hash value of one second recipient's name matches one of the hash values ​​of the first recipient's names, the virtual asset business server 120, 140 may check that the recipient's names match.

[0210] According to an embodiment, the electronic device 100 may convert the name data of the first recipient in various ways and then hash the converted name data. A detailed operation of the electronic device 100 hashing the name data is omitted since it overlaps with the description of Figures 7a to 7c.

[0211] Meanwhile, the operation of hashing the first recipient's name data may correspond to the operation of the electronic device 100 hashing the recipient's name data at step S410 of FIG. 4a, or the operation of the electronic device 100 hashing the recipient's name data at step S460 of FIG. 4b.

[0212] Referring to FIG. 7g, the virtual asset business server 120, 140 may check whether a hash value of one first recipient's name matches one of the hash values ​​of the second recipient's names according to an embodiment. For example, the virtual asset business server 120, 140 may convert the second recipient's name data in various ways and then hash it to generate a hash value set of the second recipient's name including the hash values ​​of the second recipient's names. Also, the electronic device 100 may convert the first recipient's name data in a set manner and then hash it to generate a hash value of one first recipient's name. Thereafter, if a hash value of one first recipient's name matches one of the hash values ​​of the second recipient's names, the virtual asset business server 120, 140 may check that the recipient's names match.

[0213] According to an embodiment, the virtual asset business server 120, 140 may convert the name data of the second recipient in various ways and then hash the data. A detailed operation of the virtual asset business server 120, 140 hashing the name data is omitted since it overlaps with the contents described with reference to Figures 7a to 7c.

[0214] Meanwhile, the operation of hashing the second recipient's name data may correspond to the operation of the receiving virtual asset business server 120 hashing the recipient's name data at step S420 of FIG. 4a, or the operation of the remittance virtual asset business server 140 hashing the recipient's name data at step S470 of FIG. 4b.

[0215] Referring to FIG. 7h, the virtual asset business server 120, 140 may check whether one of the hash values ​​of the first recipient's name matches one of the hash values ​​of the second recipient's name according to an embodiment. For example, the electronic device 100 may convert the first recipient's name data in various ways and then hash the data to generate a hash value set of the first recipient's name including the hash values ​​of the first recipient's name. Also, the virtual asset business server 120, 140 may convert the second recipient's name data in various ways and then hash the data to generate a hash value set of the second recipient's name including the hash values ​​of the second recipient's name. Thereafter, if the matching hash value among the hash values ​​of the first recipient's name and the hash values ​​of the second recipient's name is equal to or greater than a set value, the virtual asset business server 120, 140 may check that the recipient's names match.

[0216] According to an embodiment, the electronic device 100 or the virtual asset business server 120, 140 may hash the first payee's name data or the second payee's name data after converting the data in various ways. A detailed operation of the virtual asset business server 120, 140 hashing the name data is omitted since it overlaps with the contents described with reference to Figures 7a to 7c.

[0217] Meanwhile, the operation of hashing the first recipient's name data may correspond to the operation of the electronic device 100 hashing the recipient's name data in step S410 of Fig. 4a, or the operation of the electronic device 100 hashing the recipient's name data in step S460 of Fig. 4b. Also, the operation of hashing the second recipient's name data may correspond to the operation of the receiving virtual asset business server 120 hashing the recipient's name data in step S420 of Fig. 4a, or the operation of the remittance virtual asset business server 140 hashing the recipient's name data in step S470 of Fig. 4b.

[0218] 8 is a diagram illustrating a process in which the electronic device 100 verifies a recipient according to an embodiment. In this case, the electronic device 100 may represent a server existing within a remittance virtual asset business.

[0219] According to one embodiment, a user can transfer virtual assets in his / her wallet managed by a remittance virtual asset business operator to his / her wallet managed by a receiving virtual asset business operator using the user terminal 160. That is, the remitter who transfers the virtual assets and the recipient who receives the virtual assets can be the same person.

[0220] In step S800, the user terminal 160 may acquire information about a receiving virtual asset business and a receiving virtual asset address according to an embodiment. For example, the user terminal 160 may acquire user input regarding a receiving virtual asset address to which virtual assets are transferred and information about a receiving virtual asset business that manages the address.

[0221] In step S805, according to an embodiment, the electronic device 100 may receive information about the receiving virtual asset business and the receiving virtual asset address from the user terminal 160. For example, the user terminal 160 may transmit to the electronic device 100 the receiving virtual asset address entered by the user and information about the receiving virtual asset business that manages the address.

[0222] In step S810, according to an embodiment, the electronic device 100 may transmit a request for a hash value of the recipient's name and a receiving virtual asset address to the receiving virtual asset business server 120. For example, the electronic device 100 may transmit a receiving virtual asset address to the receiving virtual asset business server 120 and request the receiving virtual asset business server 120 to transmit a hash value of the recipient's name corresponding to the receiving virtual asset address.

[0223] In step S815, the electronic device 100 may receive from the virtual asset business server 120 whether or not it has a receiving virtual asset address and a hash value of the recipient's name, according to an embodiment. For example, the receiving virtual asset business server 120 may check whether there is an address that matches the receiving virtual asset address. Thereafter, the receiving virtual asset business server 120 may identify the recipient's name data corresponding to the receiving virtual asset address, and may hash the recipient's name data to generate a hash value of the recipient's name. The receiving virtual asset business server 120 may transmit to the electronic device 100 whether or not there is an address that matches the receiving virtual asset address and a hash value of the recipient's name.

[0224] According to an embodiment, the receiving virtual asset business server 120 may check whether there is an address that matches the receiving virtual asset address or the auxiliary virtual asset address. For example, the receiving virtual asset business server 120 may check whether there is an address in the database that matches the receiving virtual asset address received from the electronic device 100. Alternatively, if the receiving virtual asset business server 120 also receives the auxiliary virtual asset address from the electronic device 100, the receiving virtual asset business server 120 may check whether there are addresses in the database that match the receiving virtual asset address and the auxiliary virtual asset address.

[0225] According to one embodiment, the receiving virtual asset business server 120 can identify the name data of the recipient. For example, if it is confirmed that an address matching the receiving virtual asset address exists in the database, the receiving virtual asset business server 120 can identify the name data of the recipient corresponding to the receiving virtual asset address.

[0226] According to one embodiment, the receiving virtual asset business server 120 may generate a hash value of one or more names of the recipient. A detailed operation of the receiving virtual asset business server 120 generating a hash value of one or more names of the recipient is omitted since it overlaps with the contents described with reference to Figures 7a to 7h.

[0227] In step S820, the electronic device 100 may verify whether the remitter and the recipient are the same according to an embodiment. For example, the electronic device 100 may identify the remitter's name data and generate a hash value of the remitter's name by hashing the remitter's name data. Thereafter, the electronic device 100 may check whether the hash value of the recipient's name received from the receiving virtual asset business server 120 is the same as the hash value of the remitter's name. A detailed operation of the electronic device 100 verifying whether the remitter and the recipient are the same will be omitted since it overlaps with the contents described with reference to Figs. 7a to 7h.

[0228] In step S825, if the remitter and the recipient match, the electronic device 100 may transmit a request to issue an OTP (one time password) to the receiving virtual asset business server 120 according to an embodiment. Alternatively, if the remitter and the recipient do not match, the electronic device 100 may transmit a request to re-enter the address of the receiving virtual asset to the user terminal 160 according to an embodiment. However, it is obvious to those skilled in the art that the OTP is only one embodiment and various types of passwords may be used.

[0229] In step S830, the electronic device 100 may obtain an OTP according to an embodiment. For example, if the sender and the recipient match, the receiving virtual asset business server 120 may issue an OTP and provide it to the receiving virtual asset business account of the user. Thereafter, the user may input the issued OTP into the user terminal 160.

[0230] In step S835, the electronic device 100 may receive an OTP from the user terminal 160 according to an embodiment. For example, the user terminal 160 may transmit an OTP input by a user to the electronic device 100.

[0231] In step S840, the electronic device 100 may transmit the OTP to the receiving virtual asset business server 120 according to an embodiment. For example, the electronic device 100 may transmit the OTP received from the user terminal 160 to the receiving virtual asset business server 120.

[0232] In step S845, the receiving virtual asset business server 120 may verify the OTP. For example, the receiving virtual asset business server 120 may check whether the OTP issued by itself matches the OTP entered by the user.

[0233] In step S850, the electronic device 100 may receive an OTP verification result from the receiving virtual asset business server 120. For example, the electronic device 100 may receive from the receiving virtual asset business server 120 a value (true) indicating that the OTP issued by the receiving virtual asset business server 120 matches the OTP entered by the user, or a value (false) indicating that the OTP issued by the receiving virtual asset business server 120 does not match the OTP entered by the user.

[0234] In step S855, if the OTP issued by the receiving virtual asset business server 120 matches the OTP entered by the user, the electronic device 100 may transfer the virtual asset according to an embodiment. Alternatively, if the OTP issued by the receiving virtual asset business server 120 does not match the OTP entered by the user, the electronic device 100 may transmit a request to re-enter the OTP to the user terminal 160 according to an embodiment.

[0235] In step S860, when the electronic device 100 transfers the virtual asset, the electronic device 100 may transmit a transaction identification value to the receiving virtual asset business server 120 according to an embodiment. For example, the electronic device 100 may transmit a transaction identification value corresponding to the transfer of the virtual asset to the receiving virtual asset business server 120. However, step S860 may be omitted.

[0236] In step S865, the receiving virtual asset business server 120 may reflect the transferred virtual assets in the balance of the receiving virtual asset address according to an embodiment. For example, the receiving virtual asset business server 120 may reflect the transferred virtual assets in the balance of the receiving virtual asset address at set time intervals or each time a response message is received based on a transaction identification value, etc.

[0237] 9 is a diagram illustrating a process in which the electronic device 100 verifies a remitter according to an embodiment. In this case, the electronic device 100 may represent a server existing within a receiving virtual asset business.

[0238] According to one embodiment, a user can transfer virtual assets in his / her wallet managed by a remittance virtual asset business operator to his / her wallet managed by a receiving virtual asset business operator using the user terminal 160. That is, the remitter who transfers the virtual assets and the recipient who receives the virtual assets can be the same person.

[0239] In step S900, the user terminal 160 may acquire information about a receiving virtual asset business and a receiving virtual asset address according to an embodiment. For example, the user terminal 160 may acquire user input regarding a receiving virtual asset address to which virtual assets are transferred and information about a receiving virtual asset business that manages the address.

[0240] In step S905, according to an embodiment, the remittance virtual asset business server 140 may receive information about the receiving virtual asset business and the receiving virtual asset address from the user terminal 160. For example, the user terminal 160 may transmit the receiving virtual asset address entered by the user and information about the receiving virtual asset business that manages the address to the remittance virtual asset business server 140.

[0241] In step S910, according to an embodiment, the electronic device 100 may receive a hash value of the address of the receiving virtual asset and the name of the remitter from the remittance virtual asset business server 140. For example, the remittance virtual asset business server 140 may hash the remitter's name data to generate a hash value of the remitter's name. Thereafter, the remittance virtual asset business server 140 may transmit the hash value of the address of the receiving virtual asset and the name of the remitter to the electronic device 100.

[0242] According to one embodiment, the remittance virtual asset business server 140 may generate a hash value of one or more names of the remitter. A detailed operation of the remittance virtual asset business server 140 generating a hash value of one or more names of the remitter is omitted since it overlaps with the contents described with reference to Figures 7a to 7h.

[0243] In step S915, the electronic device 100 may verify whether the sender and the recipient match according to an embodiment. For example, the electronic device 100 may check whether there is an address that matches the address of the receiving virtual assets. Thereafter, the electronic device 100 may identify the recipient's name data corresponding to the address of the receiving virtual assets, and may hash the recipient's name data to generate a hash value of the recipient's name. The electronic device 100 may check whether the hash value of the recipient's name matches the hash value of the sender's name.

[0244] According to one embodiment, the electronic device 100 can check whether there is an address that matches the receiving virtual asset address or the auxiliary virtual asset address. For example, the electronic device 100 can check whether there is an address in the database that matches the receiving virtual asset address received from the remittance virtual asset business server 140. Alternatively, if the electronic device 100 also receives the auxiliary virtual asset address from the remittance virtual asset business server 140, the electronic device 100 can check whether there are addresses in the database that match the receiving virtual asset address and the auxiliary virtual asset address.

[0245] According to one embodiment, the electronic device 100 can verify the name data of the recipient. For example, if it is determined that an address matching the receiving virtual asset address exists in the database, the electronic device 100 can verify the name data of the recipient corresponding to the receiving virtual asset address.

[0246] According to one embodiment, the electronic device 100 may generate a hash value of one or more names of the recipient. A more detailed operation of the electronic device 100 generating a hash value of one or more names of the recipient is omitted since it overlaps with the contents described with reference to Figures 7a to 7h.

[0247] According to an embodiment, the electronic device 100 may verify whether a hash value of one or more names of the payee matches a hash value of one or more names of the remitter. A detailed operation of the electronic device 100 verifying whether the remitter and the payee match is omitted since it overlaps with the contents described with reference to Figures 7a to 7h.

[0248] In step S920, the electronic device 100 may transmit the verification result to the remittance virtual asset business server 140. For example, the electronic device 100 may transmit a value indicating that there is no address that matches the receiving virtual asset address or the auxiliary virtual asset address to the remittance virtual asset business server 140. Alternatively, the electronic device 100 may transmit a value indicating that the hash value of the remitter's name and the hash value of the recipient's name match (true) or a value indicating that the hash value of the remitter's name and the hash value of the recipient's name do not match (false) to the remittance virtual asset business server 140.

[0249] In step S925, if the remitter and the recipient match, the electronic device 100 may receive an OTP issuance request from the remittance virtual asset business server 140 according to an embodiment. Alternatively, if the remitter and the recipient do not match, the remittance virtual asset business server 140 may send a request to re-enter the address of the receiving virtual asset to the user terminal 160 according to an embodiment. However, it is obvious to those skilled in the art that the OTP is only one embodiment and various types of passwords may be used.

[0250] In step S930, the electronic device 100 may obtain an OTP according to an embodiment. For example, if the sender and the recipient match, the electronic device 100 may issue an OTP and provide it to the user's account of the receiving virtual asset business. Thereafter, the user may input the issued OTP into the user terminal 160.

[0251] In step S935, according to an embodiment, the remittance virtual asset business server 140 may receive an OTP from the user terminal 160. For example, the user terminal 160 may transmit an OTP input by the user to the remittance virtual asset business server 140.

[0252] In step S940, according to an embodiment, the electronic device 100 may receive an OTP from the remittance virtual asset business server 140. For example, the remittance virtual asset business server 140 may transmit the OTP received from the user terminal 160 to the electronic device 100.

[0253] In step S945, the electronic device 100 may verify the OTP. For example, the electronic device 100 may check whether the OTP issued by the electronic device 100 matches the OTP entered by the user.

[0254] In step S950, the electronic device 100 may transmit the OTP verification result to the remittance virtual asset business server 140. For example, the electronic device 100 may transmit to the remittance virtual asset business server 140 a value (true) indicating that the OTP issued by the electronic device 100 matches the OTP entered by the user, or a value (false) indicating that the OTP issued by the electronic device 100 does not match the OTP entered by the user.

[0255] In step S955, if the OTP issued by the electronic device 100 matches the OTP entered by the user, the remittance virtual asset business server 140 may transfer the virtual assets according to an embodiment. Alternatively, if the OTP issued by the electronic device 100 does not match the OTP entered by the user, the remittance virtual asset business server 140 may send a request to re-enter the OTP to the user terminal 160 according to an embodiment.

[0256] In step S960, when the remittance virtual asset business server 140 transfers virtual assets, the electronic device 100 may receive a transaction identification value from the remittance virtual asset business server 140 according to an embodiment. For example, the electronic device 100 may receive a transaction identification value corresponding to the transfer of virtual assets from the remittance virtual asset business server 140. However, step S960 may be omitted.

[0257] In step S965, the electronic device 100 can reflect the transferred virtual assets in the balance of the receiving virtual asset address according to one embodiment. For example, the electronic device 100 can reflect the transferred virtual assets in the balance of the receiving virtual asset address at set time intervals or each time a response message is received based on a transaction identification value or the like.

[0258] 10 is a diagram illustrating a process in which the electronic device 100 verifies a recipient according to an embodiment. In this case, the electronic device 100 may represent a server existing within a remittance virtual asset business.

[0259] According to one embodiment, a user can transfer virtual assets in his / her wallet managed by a remittance virtual asset business operator to his / her wallet managed by a receiving virtual asset business operator using the user terminal 160. That is, the remitter who transfers the virtual assets and the recipient who receives the virtual assets can be the same person.

[0260] In step S1000, the user terminal 160 may obtain a public key and a receiving virtual asset address according to an embodiment. For example, the user terminal 160 may obtain a user input regarding a public key of a generated public key and private key pair. The user terminal 160 may also obtain a user input regarding a receiving virtual asset address to which virtual assets are transferred and information regarding a receiving virtual asset business entity that manages the address.

[0261] In step S1005, according to an embodiment, the electronic device 100 may receive a public key, a receiving virtual asset address, and a request to transfer virtual assets to the receiving virtual asset address from the user terminal 160. For example, the user terminal 160 may request to transfer virtual assets to the receiving virtual asset address while transmitting the public key and the receiving virtual asset address to the electronic device 100.

[0262] In step S1010, the electronic device 100 may transfer virtual assets and identify a transaction identification value according to an embodiment. For example, the electronic device 100 may transfer virtual assets to a receiving virtual asset address and identify a transaction identification value corresponding to the transfer of the virtual assets.

[0263] In step S1015, the electronic device 100 may encrypt the transaction identification value according to an embodiment. For example, the electronic device 100 may encrypt the transaction identification value using a public key received from the user terminal 160 to obtain an encryption result or a cypher text.

[0264] In step S1020, the electronic device 100 may upload the pair of the transaction identification value and the encryption result to an open server according to an embodiment. For example, the electronic device 100 may upload the pair of the transaction identification value and the encryption result to a web server that is accessible to all virtual asset business servers.

[0265] In step S1025, the receiving virtual asset business server 120 may identify the virtual assets transferred to the receiving virtual asset address according to an embodiment. For example, the receiving virtual asset business server 120 may identify the virtual assets or deposits transferred by the electronic device 100 to the receiving virtual asset address.

[0266] In step S1030, according to an embodiment, the receiving virtual asset business server 120 may transmit a request for a private key to the user terminal 160. For example, the receiving virtual asset business server 120 may request the user terminal 160 to obtain and transmit a private key.

[0267] In step S1035, the user terminal 160 may obtain a private key according to an embodiment. For example, the user terminal 160 may display a pop-up window for inputting the private key on the display of the user terminal 160 and obtain a user input for inputting the private key.

[0268] In step S1040, according to an embodiment, the receiving virtual asset business server 120 may receive a private key from the user terminal 160. For example, the user terminal 160 may transmit a private key input by a user to the receiving virtual asset business server 120.

[0269] Meanwhile, although it has been described that steps S1015 to S1020 are performed after steps S1025 to S1040, this is merely an embodiment. For example, steps S1015 to S1020 and steps S1025 to S1040 may be performed in parallel, or steps S1025 to S1040 may be performed before steps S1015 to S1020.

[0270] In step S1045, the receiving virtual asset business server 120 may acquire a transaction identification value according to an embodiment. For example, the receiving virtual asset business server 120 may load the transaction identification value based on the receiving virtual asset address.

[0271] In step S1050, the receiving virtual asset business server 120 may obtain a pair of a transaction identification value and an encryption result from an open server according to an embodiment. For example, the receiving virtual asset business server 120 may search for the obtained transaction identification value in a web server and load the pair of the transaction identification value and the encryption result from the web server.

[0272] Meanwhile, although it has been described that steps S1030 to S1040 are performed followed by steps S1045 to S1050, this is merely an embodiment, and for example, steps S1030 to S1040 and steps S1045 to S1050 may be performed in parallel, or steps S1045 to S1050 may be performed followed by steps S1030 to S1040.

[0273] In operation S1055, the receiving virtual asset business server 120 may decrypt the encryption result according to an embodiment. For example, the receiving virtual asset business server 120 may decrypt the encryption result using the acquired private key.

[0274] In step S1060, the receiving virtual asset business server 120 may check whether the decryption result matches the transaction identification value according to an embodiment.

[0275] Meanwhile, Fig. 10 illustrates that the electronic device 100 or the receiving virtual asset business server 120 encrypts or decrypts the transaction identification value to check whether it matches, but this is only one embodiment and is not limited to the above. For example, Fig. 10 illustrates that the electronic device 100 or the receiving virtual asset business server 120 can encrypt or decrypt name data or date of birth data to check whether it matches.

[0276] In step S1065, the receiving virtual asset business server 120 may reflect the transferred virtual assets in the balance of the receiving virtual asset address according to an embodiment. For example, the receiving virtual asset business server 120 may reflect the transferred virtual assets in the balance of the receiving virtual asset address at set time intervals or each time a response message is received based on a transaction identification value, etc.

[0277] 11 is a diagram illustrating a process in which the electronic device 100 verifies a remitter according to an embodiment. In this case, the electronic device 100 may represent a server existing within a receiving virtual asset business.

[0278] According to one embodiment, a user can transfer virtual assets in his / her wallet managed by a remittance virtual asset business operator to his / her wallet managed by a receiving virtual asset business operator using the user terminal 160. That is, the remitter who transfers the virtual assets and the recipient who receives the virtual assets can be the same person.

[0279] In step S1100, the user terminal 160 may obtain a public key and a receiving virtual asset address according to an embodiment. For example, the user terminal 160 may obtain a user input regarding a public key of a generated public key and private key pair. The user terminal 160 may also obtain a user input regarding a receiving virtual asset address to which virtual assets are transferred and information regarding a receiving virtual asset business entity that manages the address.

[0280] In step S1105, according to an embodiment, the remittance virtual asset business server 140 may receive a public key, a receiving virtual asset address, and a request to transfer virtual assets to the receiving virtual asset address from the user terminal 160. For example, the user terminal 160 may request to transfer virtual assets to the receiving virtual asset address while transmitting the public key and the receiving virtual asset address to the remittance virtual asset business server 140.

[0281] In step S1110, the remittance virtual asset business server 140 may transfer virtual assets and identify a transaction identification value according to an embodiment. For example, the remittance virtual asset business server 140 may transfer virtual assets to a receiving virtual asset address and identify a transaction identification value corresponding to the transfer of the virtual assets.

[0282] In step S1115, the remittance virtual asset business server 140 may encrypt the transaction identification value according to an embodiment. For example, the remittance virtual asset business server 140 may encrypt the transaction identification value using the public key received from the user terminal 160 and obtain an encryption result or a cypher text.

[0283] In step S1120, the remittance virtual asset business server 140 may upload the pair of the transaction identification value and the encryption result to an open server according to an embodiment. For example, the remittance virtual asset business server 140 may upload the pair of the transaction identification value and the encryption result to a web server that is accessible to all virtual asset business servers.

[0284] In step S1125, the electronic device 100 may identify the virtual assets transferred to the receiving virtual asset address according to an embodiment. For example, the electronic device 100 may identify the virtual assets or deposit transferred by the remittance virtual asset business server 140 to the receiving virtual asset address.

[0285] In operation S1130, according to an embodiment, the electronic device 100 may transmit a request for a private key to the user terminal 160. For example, the electronic device 100 may request the user terminal 160 to obtain and transmit a private key.

[0286] In step S1135, the user terminal 160 may obtain a private key according to an embodiment. For example, the user terminal 160 may display a pop-up window for inputting the private key on the display of the user terminal 160 and obtain a user input for inputting the private key.

[0287] In operation S1140, the electronic device 100 may receive a private key from the user terminal 160 according to an embodiment. For example, the user terminal 160 may transmit a private key input by a user to the electronic device 100.

[0288] Meanwhile, although it has been described that steps S1115 to S1120 are performed after steps S1125 to S1140, this is merely one embodiment. For example, steps S1115 to S1120 and steps S1125 to S1140 may be performed in parallel, or steps S1125 to S1140 may be performed before steps S1115 to S1120.

[0289] In step S1145, the electronic device 100 may obtain a transaction identification value according to an embodiment. For example, the electronic device 100 may load the transaction identification value based on the receiving virtual asset address.

[0290] In step S1150, the electronic device 100 may obtain a pair of the transaction identification value and the encryption result from an open server according to an embodiment. For example, the electronic device 100 may search for the obtained transaction identification value in a web server and load the pair of the transaction identification value and the encryption result from the web server.

[0291] Meanwhile, although it has been described that steps S1130 to S1140 are performed followed by steps S1145 to S1150, this is merely one embodiment. For example, steps S1130 to S1140 and steps S1145 to S1150 may be performed in parallel, or steps S1130 to S1140 may be performed after steps S1145 to S1150.

[0292] In operation S1155, the electronic device 100 may decrypt the encryption result according to an embodiment of the present invention. For example, the electronic device 100 may decrypt the encryption result using the obtained private key.

[0293] In step S1160, the electronic device 100 may check whether the decryption result matches the transaction identification value according to an embodiment.

[0294] Meanwhile, Fig. 11 illustrates that the electronic device 100 or the remittance virtual asset business server 140 checks whether the transaction identification value is consistent by encrypting or decrypting it, but this is only one embodiment and is not limited to the above. For example, Fig. 11 illustrates that the electronic device 100 or the remittance virtual asset business server 140 can check whether the name data or the date of birth data is consistent by encrypting or decrypting it.

[0295] In step S1165, the electronic device 100 may reflect the transferred virtual assets in the balance of the receiving virtual asset address according to an embodiment. For example, the electronic device 100 may reflect the transferred virtual assets in the balance of the receiving virtual asset address at set time intervals or each time a response message is received based on a transaction identification value, etc.

[0296] Meanwhile, in order to more strictly verify the transmission and reception, the electronic device 100, the receiving virtual asset business server 120, the remittance virtual asset business server 140, and the user terminal 160 may perform at least one of the operations described above with reference to Figures 2a to 4b and 8 to 11. For example, the electronic device 100, the receiving virtual asset business server 120, the remittance virtual asset business server 140, and the user terminal 160 may check whether the hash value of the name and the hash value of the date of birth match as described with reference to Figure 2a, and then check whether the OTP matches as described with reference to Figure 8. Alternatively, the electronic device 100, the receiving virtual asset business server 120, the remittance virtual asset business server 140, and the user terminal 160 may check whether the transaction identification value matches as described with reference to Figure 11, and then check whether the hash value of the name and the hash value of the date of birth match as described with reference to Figure 2b. In addition, the electronic device 100, the receiving virtual asset business server 120, the sending virtual asset business server 140, and the user terminal 160 can verify the recipient or sender by various combinations of the operations described above with respect to Figures 2a to 4b and Figures 8 to 11.

[0297] 12 shows a flow chart of a method for beneficiary verification in an electronic device according to one embodiment. In the case of overlapping content, the previous statements may apply.

[0298] In step S1200, the electronic device can identify information regarding the transfer of virtual assets, including the originator's full name data, the originator's date of birth data, and the recipient virtual assets address.

[0299] In step S1220, the electronic device may identify a set of hash values ​​of the remitter's name generated based on the remitter's name data and a set of hash values ​​of the remitter's date of birth generated based on the remitter's date of birth data.

[0300] According to one embodiment, when the electronic device identifies the set of hash values ​​of the sender's name and the set of hash values ​​of the sender's date of birth, the electronic device can remove set characters, including spaces, from the sender's name data.

[0301] According to one embodiment, when the electronic device identifies the hash value set of the remitter's name and the hash value set of the remitter's date of birth, the electronic device can convert the letter case of the characters contained in the remitter's name data to a set case.

[0302] According to one embodiment, the set of hash values ​​of the remitter's name may include at least one of: a first hash value generated based on the remitter's name information consisting of a single entry in the order of first name and last name; a second hash value generated based on the remitter's name information consisting of a single entry in the order of last name and first name; or a third hash value generated based on the remitter's name information consisting of multiple entries including a last name, a first name, and at least one middle name.

[0303] According to one embodiment, the set of hash values ​​of the recipient's name generated based on the recipient's name data corresponding to the receiving virtual asset address may include at least one of: a fourth hash value generated based on the recipient's name information consisting of a single entry in first name and last name order; a fifth hash value generated based on the recipient's name information consisting of a single entry in last name and first name order; or a sixth hash value generated based on the recipient's name information consisting of multiple entries including a last name, a first name, and at least one middle name.

[0304] In step S1240, the electronic device may send a verification request message to a beneficiary server, the message including a hash value set of the sender's name, a hash value set of the sender's date of birth, and the recipient virtual asset address.

[0305] According to one embodiment, the verification request message may further include at least one of a value indicating the type of the object to be verified, a value indicating the type of virtual asset, an auxiliary virtual asset address related to the type of virtual asset, or a hash salt value associated with at least one of a hash value set of the remitter's name or a hash value set of the remitter's date of birth.

[0306] In step S1260, the electronic device may receive a response message from the receiving server, the response message including verification result information regarding whether the sender and the recipient match based on the verification request message.

[0307] According to an embodiment, it may be determined whether or not to transfer virtual assets from the remittance virtual asset address of the remittance sender to the receiving virtual asset address based on the verification result information. For example, if the response message includes information indicating that the recipient is verified to match the remittance sender, it may be determined that the transfer of virtual assets is to be performed. Or, if the response message includes any one of information indicating that an address matching the receiving virtual asset address or the auxiliary virtual asset address is not confirmed among the virtual asset addresses related to the receiving server, information regarding a mismatch between the hash value set of the remittance sender's name and the hash value set of the recipient's name generated based on the recipient's name data corresponding to the receiving virtual asset address, or information regarding a mismatch between the hash value set of the remittance sender's date of birth and the hash value set of the recipient's date of birth generated based on the recipient's date of birth data, it may be determined that the transfer of virtual assets is blocked.

[0308] According to one embodiment, the verification result information may include at least one of the following: information indicating that no address matching the receiving virtual asset address or the auxiliary virtual asset address is identified among the virtual asset addresses on the receiving server; information regarding a mismatch between a hash value set of the sender's name and a hash value set of the recipient's name generated based on the recipient's name data corresponding to the receiving virtual asset address, or information regarding a mismatch between a hash value set of the sender's date of birth and a hash value set of the recipient's date of birth generated based on the recipient's date of birth data; or information indicating that the recipient is verified to match the sender.

[0309] According to one embodiment, the verification result information may include information regarding a mismatch between the remitter's name hash value set and the recipient's name hash value set when any one of the hash values ​​included in the recipient's name hash value set generated based on the recipient's name data corresponding to the receiving virtual asset address does not match any one of the first hash value, the second hash value, or the third hash value.

[0310] According to one embodiment, the verification result information may include information regarding a mismatch between the hash value set of the remitter's name and the hash value set of the recipient's name if any one of the hash values ​​included in the hash value set of the remitter's name does not match any one of the fourth hash value, the fifth hash value, or the sixth hash value.

[0311] According to one embodiment, the receiving virtual asset address may be checked to see if there is an address in the receiving server's database that matches the receiving virtual asset address, regardless of whether at least one character included in the receiving virtual asset address is in lowercase or uppercase. Also, the receiving virtual asset address may be checked to see if there is an address in the receiving server's database that matches the receiving virtual asset address after removing a configured prefix included in the receiving virtual asset address.

[0312] 13 illustrates a flow chart of a method for verifying an originator of an electronic device according to an embodiment. In the case of overlapping content, the above description may apply.

[0313] In step S1300, the electronic device can identify the transferred virtual assets and the receiving virtual asset address.

[0314] In step S1320, the electronic device can identify the recipient's name data and the recipient's date of birth data corresponding to the receiving virtual asset address.

[0315] In step S1340, the electronic device can identify a set of hash values ​​of the recipient's name generated based on the recipient's name data and a set of hash values ​​of the recipient's date of birth generated based on the recipient's date of birth data.

[0316] According to one embodiment, when the electronic device identifies the set of hash values ​​of the recipient's name and the set of hash values ​​of the recipient's birth date, the electronic device can remove set characters, including spaces, from the recipient's name data.

[0317] According to one embodiment, when the electronic device identifies a hash value set of the recipient's name and a hash value set of the recipient's birth date, the electronic device can convert the letter case of the characters contained in the recipient's name data to a set case.

[0318] According to one embodiment, the hash value set of the recipient's name may include at least one of a first hash value generated based on the recipient's name information consisting of a single entry in first name and last name order, a second hash value generated based on the recipient's name information consisting of a single entry in last name and first name order, or a third hash value generated based on the recipient's name information consisting of multiple entries including a last name, a first name, and at least one middle name.

[0319] According to one embodiment, the hash value set of the sender's name corresponding to the receiving virtual asset address or the transaction identification value may include at least one of a fourth hash value generated based on the sender's name information consisting of a single entry in the order of first name and last name, a fifth hash value generated based on the sender's name information consisting of a single entry in the order of last name and first name, or a sixth hash value generated based on the sender's name information consisting of multiple entries including a last name, a first name, and at least one middle name.

[0320] In step S1360, the electronic device may send a verification request message to the ordering server, the message including a hash value set of the recipient's name, a hash value set of the recipient's date of birth, and the receiving virtual asset address.

[0321] According to one embodiment, the verification request message may further include at least one of a transaction identification value corresponding to the transfer of virtual assets, a value indicating the type of the object to be verified, a value indicating the type of virtual asset to be transferred, an auxiliary virtual asset address related to the type of virtual asset, or a hash salt value associated with at least one of a hash value set of the recipient's name or a hash value set of the recipient's date of birth.

[0322] In step S1380, the electronic device may receive a response message from the remittance server, the response message including verification result information regarding whether the recipient and the remitter match based on the verification request message.

[0323] According to one embodiment, the verification result information may include at least one of the following: information indicating that a value matching the transaction identification value is not identified among the transaction identification values ​​related to the remittance server; information indicating that an address matching the receiving virtual asset address or the auxiliary virtual asset address is not identified among the virtual asset addresses related to the remittance server; information regarding a mismatch between a hash value set of the recipient's name and a hash value set of the sender's name generated based on the receiving virtual asset address or the sender's name data corresponding to the transaction identification value, or information regarding a mismatch between a hash value set of the recipient's date of birth and a hash value set of the sender's date of birth generated based on the sender's date of birth data; or information indicating that the sender is verified to match the recipient.

[0324] According to one embodiment, the verification result information may include information regarding a mismatch between the hash value set of the recipient's name and the hash value set of the sender's name, if any one of the hash values ​​of the hash value set of the sender's name corresponding to the recipient virtual asset address or the transaction identification value does not match any one of the first hash value, the second hash value, or the third hash value.

[0325] According to one embodiment, the verification result information may include information regarding a mismatch between the hash value set of the recipient's name and the hash value set of the remitter's name if any one of the hash values ​​of the recipient's name does not match any one of the fourth hash value, the fifth hash value, or the sixth hash value.

[0326] According to one embodiment, if the verification result information includes information indicating that the sender is verified to match the recipient, the virtual assets may be reflected in the balance of the receiving virtual asset address at set intervals based on the transaction identification value.

[0327] According to one embodiment, the receiving virtual asset address may be checked to see if there is an address in the remittance server's database that matches the receiving virtual asset address, regardless of whether at least one character included in the receiving virtual asset address is in lowercase or uppercase. Also, the receiving virtual asset address may be checked to see if there is an address in the remittance server's database that matches the receiving virtual asset address after removing a set prefix included in the receiving virtual asset address.

[0328] According to one embodiment, the transaction identification value may be checked to see if there is a value matching the transaction identification value in the remittance server's database, regardless of whether at least one character included in the transaction identification value is lowercase or uppercase. Also, if the type of the transaction identification value includes an identifier type and a hash value type, the transaction identification value may be checked to see if there is a value matching the transaction identification value in the remittance server's database using a transaction identification value of a hash value type. The transaction identification value may be checked to see if there is a value matching the transaction identification value in the remittance server's database using a transaction identification value including a leading zero value.

[0329] FIG. 14 illustrates a block diagram of an electronic device 100 according to an embodiment.

[0330] According to an embodiment, the electronic device 100 may include a memory 1400 and one or more processors 1450. The electronic device 100 illustrated in Fig. 14 illustrates only components related to this embodiment. Therefore, it can be understood by a person having ordinary skill in the art of this embodiment that other general components may be included in addition to the components illustrated in Fig. 14.

[0331] For example, the electronic device may include a communication device (not shown) according to an embodiment. The communication device is a device for performing wired / wireless communication and may communicate with an external electronic device. The external electronic device may be a terminal or a server. In addition, communication technologies used by the communication device include global system for mobile communication (GSM), code division multi access (CDMA), long term evolution (LTE), 5G, wireless LAN (WLAN), wireless fidelity (Wi-Fi), Bluetooth (Bluetooth 2.0), and the like. TM ), RFID (radio frequency identification), infrared data association (IrDA), ZigBee, NFC (near field communication), etc.

[0332] The one or more processors 1450 can control the overall operation of the electronic device 100 and process data and signals. The one or more processors 1450 can be implemented as at least one hardware unit. The one or more processors 1450 can also be operated by one or more software modules generated by executing one or more instructions stored in the memory 1400.

[0333] The one or more processors 1450 may be configured to identify information regarding the transfer of virtual assets including a full name data of an originator, a date of birth data of the originator, and a recipient virtual asset address, identify a hash value set of the originator's name generated based on the originator's name data and a hash value set of the originator's date of birth generated based on the originator's date of birth data, send a verification request message to a beneficiary server including the hash value set of the originator's name, the hash value set of the originator's date of birth, and the recipient virtual asset address, and receive a response message from the beneficiary server including verification result information performed based on the verification request message.

[0334] The one or more processors 1450 may be configured to identify the transferred virtual assets and the receiving virtual asset address, identify a recipient's name data and the recipient's date of birth data corresponding to the receiving virtual asset address, identify a set of hash values ​​of the recipient's name generated based on the recipient's name data and a set of hash values ​​of the recipient's date of birth generated based on the recipient's date of birth data, send a verification request message including the set of hash values ​​of the recipient's name, the set of hash values ​​of the recipient's date of birth, and the receiving virtual asset address to a remittance (ordering) server, and receive a response message including verification result information performed based on the verification request message from the remittance server.

[0335] The electronic device according to the above-mentioned embodiment may include a processor, a memory for storing and executing program data, a permanent storage such as a disk drive, a communication port for communicating with an external device, and a user interface device such as a touch panel, keys, buttons, etc. The method implemented by the software module or algorithm may be stored on a computer readable recording medium as computer readable code or program instructions executable on the processor. Here, examples of the computer readable recording medium include magnetic storage media (e.g., read-only memory (ROM), random-access memory (RAM), floppy disk, hard disk, etc.) and optically readable media (e.g., CD-ROM, digital versatile disc (DVD)). The computer readable recording medium may be distributed among computer systems connected via a network, and the computer readable code may be stored and executed in a distributed manner. The medium may be readable by a computer, stored in a memory, and executed by a processor.

[0336] The present embodiment may be illustrated in terms of functional block configurations and various processing steps. Such functional blocks may be embodied in various numbers of hardware and / or software configurations that perform specific functions. For example, the embodiment may employ direct circuit configurations such as memory, processing, logic, look-up tables, etc. that can perform various functions under the control of one or more microprocessors or other control devices. Just as components may be implemented in software programming or software elements, the present embodiment may include various algorithms embodied in combinations of data structures, processes, routines, or other programming configurations, and may be embodied in programming or script languages ​​such as C, C++, Java, assembler, etc. Functional aspects may be embodied in algorithms executed by one or more processors. The present embodiment may also employ conventional techniques for electronic configuration, signal processing, and / or data processing, etc. Terms such as "mechanism," "element," "means," and "configuration" may be used broadly and are not limited to mechanical and physical configurations. The terms may include the meaning of a series of software routines in cooperation with a processor, etc.

[0337] The above-described embodiments are by way of example only and other embodiments may be practiced within the scope of the following claims.

Claims

1. 1. A method for beneficiary verification of an electronic device, comprising: identifying information relating to the transfer of virtual assets, including a personal identification number of an originator and a receiving virtual asset address; identifying a set of hash values ​​of the remitter's personal identification information generated based on the remitter's personal identification information; sending a verification request message to a beneficiary server, the verification request message including a hash value set of the sender's personal identification information and the address of the receiving virtual asset; receiving a response message from the receiving server, the response message including verification result information regarding whether the remitter and the recipient match based on the verification request message; A recipient verification method, in which it is determined whether or not to transfer the virtual assets from the remittance virtual asset address of the remitter to the receiving virtual asset address based on the verification result information.

2. The personal identification information of the remitter is: The full name data of the remitter; The sender's date of birth data; and the sender's mobile phone number data.

3. The verification request message includes: A value indicating the type to validate; A value indicating a type of the virtual asset; an auxiliary virtual asset address for said type of virtual asset; 2. The method of claim 1, further comprising at least one of: a hashed set of the sender's personally identifiable information and an associated hash salt value.

4. The verification result information is information indicating that no address matching the receiving virtual asset address or the auxiliary virtual asset address is identified among the virtual asset addresses associated with the receiving server; Information regarding a discrepancy between a hash value set of the sender's personal identification information and a hash value set of the recipient's personal identification information generated based on the recipient's personal identification information corresponding to the receiving virtual asset address; and and information indicating that the payee has been verified to match the sender.

5. If the response message includes information indicating that the recipient is verified to match the sender, it is determined that the transfer of the virtual assets will occur; 5. The method of claim 4, wherein if the response message includes one of information indicating that an address matching the receiving virtual asset address or the auxiliary virtual asset address is not identified among the virtual asset addresses on the receiving server, or information regarding a mismatch between a hash value set of the sender's personal identification information and a hash value set of the recipient's personal identification information, it is determined that the transfer of the virtual asset is blocked.

6. The personal identification information of the remitter includes the name data of the remitter, The step of identifying a set of hash values ​​of the sender's personal identification information comprises: removing spaces from the remitter name data; and generating a set of hash values ​​of the sender's name based on the whitespace removed sender's name data.

7. The personal identification information of the remitter includes the name data of the remitter, The step of identifying a set of hash values ​​of the sender's personal identification information comprises: converting the letter case of the remitter's name data into a set case; and generating a set of hash values ​​of the sender's name based on the sender's name data including the converted characters into the set case.

8. The personal identification information of the remitter includes the name data of the remitter, identifying a set of hash values ​​of the remitter's personal identification information includes identifying a set of hash values ​​of the remitter's name generated based on the remitter's name data; The set of hash values ​​of the sender's name is A first hash value generated based on the sender's name information, which is a single entry in the order of first name and last name; A second hash value generated based on the sender's name information composed of a single entry of the last name and the first name; and a third hash value generated based on the sender's name information, the third hash value being composed of a plurality of entries including the last name, the first name, and at least one middle name.

9. The verification result information is 9. The method of claim 8, further comprising information regarding a mismatch between the remitter's name hash value set and the recipient's name hash value set, if any one of the hash values ​​included in the recipient's name hash value set generated based on the recipient's name data corresponding to the receiving virtual asset address does not match any one of the first hash value, the second hash value, or the third hash value.

10. 1. A method for verifying a remitter by an electronic device, comprising: identifying a transferred virtual asset and a receiving virtual asset address; identifying a recipient's personal identification information corresponding to the receiving virtual asset address; identifying a set of hash values ​​of the recipient's personally identifying information generated based on the recipient's personally identifying information; Sending a verification request message to a remittance (ordering) server, the verification request message including a hash value set of the recipient's personal identification information and the address of the receiving virtual asset; receiving from the remittance server a response message including verification result information regarding whether or not the recipient and the remitter match based on the verification request message.

11. The recipient's personal identification information is Name data of the recipient; said recipient's date of birth data; and the payee's mobile phone number data.

12. The verification request message includes: A transaction identification value corresponding to the transfer of the virtual assets; A value indicating the type to validate; A value indicating a type of the virtual asset; an auxiliary virtual asset address for said type of virtual asset; 11. The method of claim 10, further comprising at least one of: a set of hashed values ​​of the recipient's personally identifiable information and an associated hash salt value.

13. A non-transitory computer-readable recording medium having a program recorded thereon for causing a computer to execute the method according to any one of claims 1 to 12.

14. 1. An electronic device comprising: one or more processors; a memory storing one or more instructions to be executed by the one or more processors; The one or more processors execute the one or more instructions to: Identifying information regarding the transfer of virtual assets, including the originator's personal identification information and the recipient's virtual asset address; identifying a set of hash values ​​of the remitter's personal identifying information generated based on the remitter's personal identifying information; Send a verification request message to a beneficiary server, the message including a hash value set of the sender's personal identification information and the address of the receiving virtual asset; a response message including information on a result of the verification performed based on the verification request message is received from the receiving server; An electronic device that determines whether to transfer the virtual assets from the remittance virtual asset address of the remitter to the receiving virtual asset address based on the verification result information.

15. 1. An electronic device comprising: one or more processors; a memory storing one or more instructions to be executed by the one or more processors; The one or more processors execute the one or more instructions to: Identifying the transferred virtual assets and the address of the receiving virtual assets; Identifying a recipient's personal identification information corresponding to the receiving virtual asset address; identifying a set of hash values ​​of the recipient's personally identifiable information generated based on the recipient's personally identifiable information; Sending a verification request message to an ordering server, the message including a hash value set of the recipient's personal identification information and the address of the receiving virtual asset; An electronic device configured to receive a response message from the remittance server, the response message including information on a result of the verification performed based on the verification request message.

Images