Management device for electronic commerce site
The management device facilitates e-commerce transactions with cryptocurrencies by employing multiple authentication methods, ensuring transactions can proceed despite cryptographic key unavailability, password forgetfulness, or server inaccessibility, thereby improving user convenience.
Patent Information
- Application Number
- PCT/JP2024/001496
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-01-19
- Publication Date
- 2025-07-24
AI Technical Summary
Existing e-commerce transaction systems using cryptocurrencies on blockchain face challenges in user convenience during authentication, particularly when users cannot access cryptographic keys, forget passwords, or cannot use external authentication servers, hindering transactions.
A management device that performs authentication using a combination of Web1 (password), Web2 (external authentication server), and Web3 (cryptographic key) methods, allowing users to conduct transactions even in difficult authentication scenarios.
Enhances user convenience in e-commerce transactions by enabling settlement using cryptographic assets even when cryptographic keys are unavailable, passwords are forgotten, or external authentication servers are inaccessible.
Smart Images

Figure JP2024001496_24072025_PF_FP_ABST
Abstract
Description
E-commerce site management device
[0001] The present invention relates to a management device for an electronic commerce site.
[0002] Crypto assets are seeing an expansion in holders and uses due to their use as currency in emerging markets, demand for remittances, and as an alternative means of storing value to gold. Even if their use in Japan is limited, their value is expected to rise in the long term as their use expands in the global market. Regarding blockchain tokens such as crypto assets, Japan has been exempting self-issued tokens from tax on end-of-year valuation gains since 2023. This has begun to create an environment for token issuance in Japan. Therefore, it is believed that a phase of blockchain expansion is about to begin in Japan.
[0003] Smart contracts implemented on blockchains can enable the management and servicing of tokenized financial products at a fraction of the cost of traditional finance. Therefore, it is expected that large corporations, local governments, and NPOs will begin issuing tokens in earnest in Japan. Therefore, the cryptocurrency economy is expected to become widespread as a new means of fundraising and an alternative to points. In the global market, the tokenization of financial assets is expected to popularize self-custody, whereby token assets are stored in wallets to which the private key is held. This is expected to accelerate the migration of financial assets to blockchains.
[0004] Incidentally, electronic commerce transactions where payments are made using crypto assets on a blockchain require access to a wallet where the crypto assets are stored. To maintain high security, access to the wallet is usually restricted by authentication using a corresponding cryptographic key. Therefore, if a user does not have access to the cryptographic key, the user will not be able to access the wallet and conduct the above-mentioned electronic commerce transactions. For example, a situation in which the cryptographic key cannot be accessed includes a situation in which the cryptographic key is stored on a specific device and the device is not at hand. Due to these circumstances, there is a need for a means to improve user convenience for transactions using blockchains, such as authentication in electronic commerce transactions where payments are made using crypto assets.
[0005] Regarding means for improving user convenience for transactions using blockchain, Patent Document 1 discloses a proposal evaluation system that performs authentication using user identification information such as a user ID and password stored in a user information DB realized by a distributed ledger such as a blockchain or other means, SNS-linked authentication, etc. The technology described in Patent Document 1 can improve security at the time of login, etc.
[0006] Japanese Patent Application Laid-Open No. 2021-149898
[0007] The blockchain in the technology described in Patent Literature 1 is used to realize a user information DB, etc. in the proposal evaluation system, and is not used by users of the system to make payments using crypto assets. Therefore, the technology described in Patent Literature 1 only enables users to log in to the proposal evaluation system using authentication using a password, etc., SNS-linked authentication, etc. Therefore, the technology described in Patent Literature 1 has room for further improvement in terms of increasing user convenience for transactions using blockchain, such as authentication in e-commerce transactions where payments are made using crypto assets.
[0008] The present invention has been made in consideration of the above circumstances, and an object of the present invention is to improve convenience for transaction participants in electronic commerce where settlement is made using crypto assets.
[0009] As a result of intensive research into solving the above problems, the inventors discovered that the above object can be achieved by enabling a user who has been authenticated using either a password, an external authentication server, or a cryptographic key of a crypto-asset wallet to make payments using crypto-assets stored in the crypto-asset wallet. The inventors then completed the present invention. Specifically, the present invention provides the following:
[0010] The present invention provides an e-commerce site management device comprising: a Web1 authentication unit that performs Web1 authentication, which is authentication using a password set by the user; a Web2 authentication unit that performs Web2 authentication, which is authentication using social authentication information that is information indicating successful authentication of the user sent from an external authentication server; a Web3 authentication unit that performs Web3 authentication, which is authentication using a cryptographic key of a cryptocurrency wallet owned by the user; an authentication management unit that manages, for each user, the correspondence between two or more of the Web1 authentication, the Web2 authentication, and the Web3 authentication; and a payment unit that makes payments using cryptocurrency stored in the cryptocurrency wallet in response to instructions from an authenticated user who is a user authenticated by the Web1 authentication, the Web2 authentication, and / or the Web3 authentication.
[0011] Improving the convenience of authentication in e-commerce transactions where payments are made using crypto assets includes improving the convenience of authentication associated with payments. When e-commerce transactions where payments are made using crypto assets on a blockchain only use authentication using a crypto asset wallet's encryption key, the encryption key is stored on a specific device, and the user cannot make the payment if the device is not at hand. On the other hand, when authentication uses a password, the user cannot make the payment if the password is forgotten. Furthermore, when authentication uses an external authentication server such as Google Authentication System (registered trademark) or Facebook Integration (registered trademark), the user cannot make the payment if the authentication server is unavailable. Therefore, there is a demand for improved convenience by enabling authentication associated with payments even in these situations.
[0012] In the present invention, a Web1 authentication unit performs authentication using a password (Web1 authentication). Also, in the present invention, a Web2 authentication unit performs authentication using an external authentication server (Web2 authentication). Furthermore, in the present invention, a Web3 authentication unit performs authentication using a cryptographic key of a crypto-asset wallet (Web3 authentication). And, in the present invention, a payment unit enables a user (authenticated user) authenticated by either Web1 authentication, Web2 authentication, or Web3 authentication to make payments using crypto-assets stored in the crypto-asset wallet.
[0013] That is, the present invention enables a user to perform electronic commerce transactions using crypto assets even in difficult authentication situations where any two of the following situations occur simultaneously: the user has forgotten their password, the user is unable to use the authentication server, or the user is unable to use the device on which the wallet's encryption key is stored. As a result, the present invention can improve the convenience of users regarding authentication in electronic commerce transactions using crypto assets. That is, the present invention can improve the convenience of users who are transaction participants in electronic commerce transactions using crypto assets.
[0014] The present invention can improve convenience for transaction participants in electronic commerce where payments are made using crypto assets.
[0015] FIG. 1 is a block diagram showing the hardware configuration of a system S of this embodiment. FIG. 2 is an example of a user database 131. FIG. 3 is an example of a preferable flow of management processing executed by the management device 1 of this embodiment. FIG. 4 is a diagram continuing from FIG. 3. FIG. 5 is a diagram continuing from FIG. 4. FIG. 6 is a diagram continuing from FIG. 5. FIG. 7 is a diagram continuing from FIG. 6. FIG. 8 is a diagram continuing from FIG. 7. FIG. 9 is a diagram continuing from FIG. 8. FIG. 10 is a diagram continuing from FIG. 9.
[0016] Hereinafter, an example of an embodiment of the present invention will be described in detail with reference to the drawings.
[0017] <System S> Figure 1 is a block diagram showing the hardware configuration of system S of this embodiment. The e-commerce system (system S) of this embodiment is configured to include at least a management device 1 of an e-commerce site that communicates with a terminal T via a network N. In order to provide participants with the convenience of increasing the value of NFTs without having to expend effort on manufacturing devices for cryptocurrency mining, it is preferable that system S is further configured to include a cryptocurrency mining device 2 that communicates with the management device 1 via the network N.
[0018] [Management Device 1] The management device 1 includes a control unit 11, a storage unit 13, a communication unit 14, etc. The type of management device 1 is not particularly limited. The type of management device 1 may be, for example, various types of servers, cloud servers, etc. The management device 1 participates in a blockchain via a network N. The management device 1 can communicate with an external authentication server (not shown) via the network N.
[0019] [Control Unit 11] The control unit 11 includes a central processing unit (CPU), a random access memory (RAM), a read only memory (ROM), and the like.
[0020] The control unit 11 cooperates with the storage unit 13 and / or the communication unit 14 as necessary. The control unit 11 then realizes the software components of the program of this embodiment executed by the management device 1. The software components include an authentication management unit 111, a Web1 authentication unit 112, a Web2 authentication unit 113, a Web3 authentication unit 114, a game token granting unit 115, a settlement unit 116, a reward granting unit 117, a fee granting unit 118, an application acceptance unit 119, a shipping command unit 120, an NFT granting unit 121, a first value granting unit 122, a second value granting unit 123, and the like.
[0021] [Storage Unit 13] The storage unit 13 is a device for storing data and / or files, and includes a storage unit for non-temporarily storing data using a hard disk, a semiconductor memory, a recording medium, a memory card, or the like.
[0022] The storage unit 13 may have a mechanism that enables connection to a storage device or storage system such as a Network Attached Storage (NAS), a Storage Area Network (SAN), cloud storage, a file server, and / or a distributed file system via a network N.
[0023] The memory unit 13 stores a program executed by the CPU, a user database 131, reward award conditions, reward award rates, fee award conditions, fee award rates, and criteria for assigning value to participants' NFTs in projects using crowdfunding.
[0024] (User database 131) The user database 131 stores correspondence between two or more of Web1 authentication, Web2 authentication, and Web3 authentication. However, Web1 authentication, Web2 authentication, and Web3 authentication referred to here are as follows: Web1 authentication is authentication using a password set by the user. Web2 authentication is authentication using social authentication information, which is information indicating successful authentication of the user sent from an external authentication server. Web3 authentication is authentication using an encryption key of a cryptocurrency wallet owned by the user. Hereinafter, the cryptocurrency wallet will also be simply referred to as a "wallet."
[0025] The user database 131 also stores information identifying users and authentication information related to the stored correspondence. The information identifying users is, for example, a uniquely defined user ID, a unique user account name, etc. The authentication information related to Web1 authentication is, for example, information for verifying a user's account name and password. The information for verifying a password is, for example, a password hash value, etc. The authentication information related to Web2 authentication is, for example, a user ID in the authentication server, information identifying the authentication server (authentication server information), and information indicating successful authentication. The authentication information related to Web3 authentication is, for example, a wallet public key, a signature made with the wallet private key, a wallet address on the blockchain, etc. By storing this authentication information in the user database 131, the management device 1 can perform Web1 authentication, Web2 authentication, and Web3 authentication using this authentication information. It is preferable that the authentication information related to Web3 authentication includes information for the management device 1 to make a payment using the cryptocurrency assigned to the wallet. Such information may include, for example, the address of a specific smart contract designed to effect such a payment.
[0026] 2 is an example of the user database 131. The user database 131 in this example stores a correspondence between a user ID "U0001," authentication information related to Web1 authentication (account name "BitC," password hash value "c86e38817a142a511f08fbfbbc1eb8b59aa8f31d"), and authentication information related to Web3 authentication (wallet public key "public key 1," signature "signature using private key 1," wallet address "0x1ABC...," and payment smart contract address "0x2ABC..."). In addition, the user database 131 in this example stores a correspondence between the user ID "U0002", authentication information related to Web2 authentication (user ID "@Shirushi", authentication server information "SNS1 authentication", information indicating successful authentication), and authentication information related to Web3 authentication (wallet public key "public key 2", signature "signature using private key 2", wallet address "0x1DEF...", payment smart contract address "0x2DEF...").
[0027] By storing these correspondences in the user database 131, the management device 1 can manage the correspondences between two or more of the authentications, Web1 authentication, Web2 authentication, and Web3 authentication. The management device 1 can then make payments using crypto assets stored in the crypto asset wallet to users authenticated by various authentication methods, not limited to Web3 authentication.
[0028] [Communication Unit 14] The communication unit 14 is not particularly limited as long as it connects the management device 1 to the network N and enables communication with the terminal T, etc. Examples of the communication unit 14 include a wireless device compatible with a mobile phone network, a device connectable to a wireless LAN, and a network card compatible with the Ethernet standard.
[0029] [Cryptocurrency Mining Device 2] The cryptocurrency mining device 2 is a device that mines cryptocurrencies. The "mining" performed by the cryptocurrency mining device 2 is a process of verifying cryptocurrency transaction records based on blockchain technology and issuing new cryptocurrencies. The cryptocurrency mining device 2 verifies the legitimacy of transactions by performing complex calculations associated with the issuance of new cryptocurrencies, and adds new blocks to the blockchain. The blockchain then realizes a distributed ledger system for managing cryptocurrencies.
[0030] The cryptocurrency mining device 2 is preferably a so-called IoT device that automatically connects to the network N. This allows the owner of the cryptocurrency mining device 2 to use the cryptocurrency mining device 2 via the network N without having to personally perform the complicated procedures for connecting the cryptocurrency mining device 2 to the network N. This also allows the cryptocurrency mining device 2 to transmit information related to the mined cryptocurrency to the management device 1 via the network N. To further reduce the effort required for connecting to the network N, the cryptocurrency mining device 2 is preferably equipped with communication security functions and connects to a wireless LAN network.
[0031] The cryptocurrency mining device 2 is preferably manufactured by the issuer of the cryptocurrency. This ensures that the cryptocurrency mining device 2 is appropriately designed and manufactured by an issuer that is familiar with the characteristics of the cryptocurrency. To improve the cost-effectiveness of mining, the economic cost associated with the power consumption of the cryptocurrency mining device 2 is preferably 5 yen or less per month. The cryptocurrency mining device 2 may be attached to other electronic devices, such as lighting fixtures. This allows the cryptocurrency mining device 2 to continue to be used as the attached electronic device even when mining rewards are no longer available. In addition, the cryptocurrency mining device 2 may be installed in IoT devices equipped with various sensors. This enables the cryptocurrency mining device 2 to collect a wider range of information, enabling the formation of more effective information sets. This also contributes to the promotion of the formation of a token economy, enabling a synergistic effect between the provision of effective information sets and the formation of a token economy.
[0032] [Network N] The type of the network N is not particularly limited as long as it allows communication between the management device 1 and the terminals T, etc. The type of the network N is, for example, the Internet, a mobile phone network, a wireless LAN, etc.
[0033] [Terminal T] Terminal T is, for example, a personal computer, laptop computer, smartphone, tablet terminal, feature phone, personal digital assistant, PDA, portable game console, stationary game console, etc. Terminal T can execute processes such as requesting sign-up to the management device 1, requesting sign-in to the management device 1, instructing the management device 1 to link accounts, and instructing the management device 1 to make payments. Terminal T also stores a wallet app that executes various processes related to crypto assets.
[0034] Incidentally, there are games that enable play-to-earn (P2E) where users can earn crypto assets by playing. Such games are also called "P2E games." In order to use the crypto assets earned in the P2E games for payments related to the management device 1, it is preferable that the terminal T includes processing related to the P2E games.
[0035] [Main Flowchart of Management Processing] Fig. 3 shows an example of a preferred flow of management processing executed by the management device 1 of this embodiment. Fig. 4 is a diagram continuing from Fig. 3. Fig. 5 is a diagram continuing from Fig. 4. Fig. 6 is a diagram continuing from Fig. 5. Fig. 7 is a diagram continuing from Fig. 6. Fig. 8 is a diagram continuing from Fig. 7. Fig. 9 is a diagram continuing from Fig. 8. Fig. 10 is a diagram continuing from Fig. 9. Below, an example of a preferred flow of management processing executed by the management device 1 of this embodiment will be described using Figs. 3 to 10.
[0036] The management process preferably includes a series of processes related to user sign-up so that participants in electronic commerce transactions that use crypto assets for settlement can register their authentication information in the management device 1. Steps S1 to S6 are an example of such processes.
[0037] [Step S1: Determine whether sign-up using Web1 authentication has been requested] The control unit 11 executes the authentication management unit 111 in cooperation with the storage unit 13 and the communication unit 14. The control unit 11 then executes a process to determine whether sign-up using Web1 authentication, which is authentication using a password set by the user, has been requested by the authentication management unit 111 (step S1, Web1 authentication sign-up request determination step). If it is determined that a request has been made, the control unit 11 proceeds to step S2. If it is not determined that a request has been made, the control unit 11 proceeds to step S3.
[0038] The determination in the Web1 authentication sign-up request determination step includes, for example, a procedure for determining that sign-up has been requested when an instruction requesting sign-up by Web1 authentication is received from terminal T.
[0039] [Step S2: Signing up using Web1 authentication] The control unit 11 executes a process of signing up using Web1 authentication, which is determined to have been requested in the Web1 authentication sign-up request determination step, using the authentication management unit 111 (step S2, Web1 authentication sign-up execution step). The control unit 11 then proceeds to step S3.
[0040] The Web1 authentication sign-up execution step includes a procedure for receiving a set of an account name and password desired by the user. In order to prevent duplicate account names, sign-ups using insecure passwords, etc., this step preferably includes a procedure for determining whether the account name and password are usable. If this determination determines that the account name and / or password are not usable, the management device 1 preferably sends a notification requesting the user to correct the unusable account name and / or password. The Web1 authentication sign-up execution step includes a procedure for storing information related to Web1 authentication in the user database 131.
[0041] [Step S3: Determining Whether Sign-Up by Web2 Authentication Has Been Requested] The control unit 11 executes a process of determining whether sign-up by Web2 authentication, which is authentication using social authentication information that is information indicating successful authentication of the user transmitted from an external authentication server, has been requested by the authentication management unit 111 (step S3, Web2 authentication sign-up request determination step). If it is determined that a request has been made, the control unit 11 proceeds to step S4. If it is not determined that a request has been made, the control unit 11 proceeds to step S5.
[0042] The determination in the Web2 authentication sign-up request determination step includes, for example, a procedure of determining that sign-up has been requested when an instruction requesting sign-up by Web2 authentication is received from terminal T.
[0043] [Step S4: Signing up with Web2 authentication] The control unit 11 executes a process of signing up with Web2 authentication, which is determined to be requested in the Web2 authentication sign-up request determination step, using the authentication management unit 111 (step S4, Web2 authentication sign-up execution step). The control unit 11 then proceeds to step S5.
[0044] The Web2 authentication sign-up execution step preferably includes a procedure of receiving, from the terminal T or the like, information identifying the authentication server used by the user for Web2 authentication, information identifying the user in the authentication server, and the like, and using this information to request authentication of the user from the authentication server. This allows the management device 1 to obtain social authentication information, which is information indicating successful authentication of the user, from the authentication server. The Web2 authentication sign-up execution step includes a procedure of storing information related to Web2 authentication in the user database 131.
[0045] [Step S5: Determine whether sign-up using Web3 authentication has been requested] The control unit 11 executes a process to determine whether sign-up using Web3 authentication, which is authentication using the encryption key of the crypto-asset wallet owned by the user, has been requested by the authentication management unit 111 (step S5, Web3 authentication sign-up request determination step). If it is determined that a request has been made, the control unit 11 proceeds to step S6. If it is not determined that a request has been made, the control unit 11 proceeds to step S7.
[0046] The determination in the Web3 authentication sign-up request determination step includes, for example, a procedure for determining that sign-up has been requested when an instruction requesting sign-up by Web3 authentication is received from terminal T.
[0047] [Step S6: Signing up with Web3 authentication] The control unit 11 executes a process of signing up with Web3 authentication, which is determined to be requested in the Web3 authentication sign-up request determination step, using the authentication management unit 111 (step S6, Web3 authentication sign-up execution step). The control unit 11 then proceeds to step S7.
[0048] The Web3 authentication sign-up execution step preferably includes a procedure of receiving the wallet public key, a signature made with the wallet private key, the wallet address on the blockchain, etc. from the terminal T, etc. This allows the management device 1 to perform Web3 authentication of the user using the public key, private key, and address. The Web3 authentication sign-up execution step includes a procedure of storing information related to Web3 authentication in the user database 131.
[0049] Furthermore, the Web3 authentication sign-up execution step preferably includes a procedure for the management device 1 to make a settlement using the crypto asset assigned to the wallet related to the Web3 authentication sign-up execution step. Such a procedure may include, for example, a procedure for requesting that a smart contract configured to make such a settlement be associated with the wallet.
[0050] To enable the granting of a game token to a wallet, the Web3 authentication sign-up execution step preferably includes a procedure for the management device 1 to execute a process of granting a game token related to a P2E game to the wallet related to the Web3 authentication sign-up execution step and a process of making a payment using the crypto asset granted the game token for payment. Such a procedure may include, for example, a procedure of requesting that a smart contract configured to perform such granting and a smart contract configured to perform such payment be associated with the wallet.
[0051] The management process includes a series of processes related to user sign-in so that a user who has been authenticated using either a password, an external authentication server, or a cryptographic key of the crypto asset wallet can make payments using the crypto asset stored in the crypto asset wallet. Steps S7 to S10 are an example of this process.
[0052] [Step S7: Determine whether sign-in has been performed using Web1 authentication] The control unit 11 executes the Web1 authentication unit 112 in cooperation with the storage unit 13 and communication unit 14. The control unit 11 then executes a process to determine whether sign-in has been performed using Web1 authentication, which is authentication using a password set by the user, using the Web1 authentication unit 112 (step S7, Web1 authentication step). If it is determined that sign-in has been performed, the control unit 11 proceeds to step S10. If it is not determined that sign-in has been performed, the control unit 11 proceeds to step S8.
[0053] The Web1 authentication step includes a procedure for receiving sign-in information such as an account name and password from terminal T, etc., and determining that sign-in using Web1 authentication has been performed if verification of this information using authentication information related to Web1 authentication stored in user database 131 is successful.
[0054] [Step S8: Determine whether sign-in using Web2 authentication has been performed] The control unit 11 executes the Web2 authentication unit 113 in cooperation with the storage unit 13 and the communication unit 14. The control unit 11 then executes a process of determining whether sign-in using Web2 authentication, which is authentication using social authentication information that is information indicating successful authentication of the user transmitted from an external authentication server, has been performed by the Web2 authentication unit 113 (step S8, Web2 authentication step). If it is determined that sign-in has been performed, the control unit 11 proceeds to step S10. If it is not determined that sign-in has been performed, the control unit 11 proceeds to step S9.
[0055] The Web2 authentication step includes a procedure for receiving social authentication information from terminal T, etc., and determining that sign-in using Web2 authentication has been performed if verification of the social authentication information using authentication information related to Web2 authentication stored in user database 131 is successful.
[0056] [Step S9: Determine whether sign-in has been performed using Web3 authentication] The control unit 11 executes the Web3 authentication unit 114 in cooperation with the storage unit 13 and communication unit 14. The control unit 11 then executes a process to determine whether sign-in has been performed using Web3 authentication, which is authentication using the encryption key of the crypto-asset wallet owned by the user, using the Web3 authentication unit 114 (step S9, Web3 authentication step). If it is determined that sign-in has been performed, the control unit 11 proceeds to step S10. If it is not determined that sign-in has been performed, the control unit 11 proceeds to step S32.
[0057] The Web3 authentication step includes a procedure for receiving the wallet public key, a signature made with the wallet private key, the wallet address on the blockchain, etc. from terminal T, etc., and determining that sign-in using Web3 authentication has been performed if verification of this information using authentication information related to Web3 authentication stored in user database 131 is successful.
[0058] [Step S10: Obtain User Information] The control unit 11 executes the authentication management unit 111 in cooperation with the storage unit 13 and the communication unit 14. The control unit 11 then executes a process of obtaining, from the user database 131, user information related to the step executed immediately before this step, among the Web1 authentication step, Web2 authentication step, and Web3 authentication step, using the authentication management unit 111 (step S10, user information obtaining step). The control unit 11 then proceeds to step S11. By performing the processes from step S7 to step S10, the management device 1 can obtain user information related to the user from the user database 131, regardless of whether the user signed in using Web1 authentication, Web2 authentication, or Web3 authentication. In other words, the management device 1 can obtain user information about authenticated users who have been authenticated using Web1 authentication, Web2 authentication, and / or Web3 authentication, from the user database 131.
[0059] In order to automate the association between the multiple authentications, the management process preferably includes a series of processes for associating the multiple authentications, steps S11 to S16 being an example of such processes.
[0060] [Step S11: Determine whether association of Web1 authentication has been requested] The control unit 11 executes the authentication management unit 111 in cooperation with the storage unit 13 and the communication unit 14. Then, the control unit 11 executes a process of determining whether association of the authenticated user related to the user information acquisition step with Web1 authentication has been requested by the authentication management unit 111 (step S11, Web1 authentication association request determination step). If it is determined that a request has been made, the control unit 11 proceeds to step S12. If it is not determined that a request has been made, the control unit 11 proceeds to step S13.
[0061] The Web1 authentication association request determination step preferably includes a procedure for determining that Web1 authentication association has been requested when a command requesting authentication association and sign-in information such as an account name and password is received from terminal T, etc. Also, the Web1 authentication association request determination step preferably includes a procedure for updating information related to Web1 authentication stored in user database 131 when Web1 authentication has already been associated.
[0062] [Step S12: Associating Web1 Authentication] The control unit 11 executes a process of associating the authenticated user related to the user information acquisition step with the Web1 authentication related to the Web1 authentication association request determination step (step S12, Web1 authentication association execution step). The control unit 11 then proceeds to step S13. The Web1 authentication association execution step includes a procedure of updating the user database 131 so that the association is performed.
[0063] [Step S13: Determining Whether Association of Web2 Authentication Has Been Requested] The control unit 11 executes a process of determining whether association of the authenticated user related to the user information acquisition step with Web2 authentication has been requested by the authentication management unit 111 (step S13, Web2 authentication association request determination step). If it is determined that a request has been made, the control unit 11 proceeds to step S14. If it is not determined that a request has been made, the control unit 11 proceeds to step S15.
[0064] The Web2 authentication association request determination step preferably includes a step of determining that Web2 authentication association has been requested when a command requesting association of social authentication information with authentication is received. Also, the Web2 authentication association request determination step preferably includes a step of updating information related to Web2 authentication stored in the user database 131 when Web2 authentication has already been associated.
[0065] [Step S14: Associating Web2 Authentication] The control unit 11 executes a process of associating the authenticated user related to the user information acquisition step with the Web2 authentication related to the Web2 authentication association request determination step (step S14, Web2 authentication association execution step). The control unit 11 then proceeds to step S15. The Web2 authentication association execution step includes a procedure of updating the user database 131 so that the association is performed.
[0066] [Step S15: Determining Whether Association of Web3 Authentication Has Been Requested] The control unit 11 executes a process of determining whether association of the authenticated user related to the user information acquisition step with Web3 authentication has been requested by the authentication management unit 111 (step S15, Web3 authentication association request determination step). If it is determined that a request has been made, the control unit 11 proceeds to step S16. If it is not determined that a request has been made, the control unit 11 proceeds to step S17.
[0067] The Web3 authentication association request determination step preferably includes a procedure of determining that association of Web3 authentication has been requested when a command requesting association of authentication with data related to Web3 authentication, such as a wallet public key, a signature made with the wallet private key, and a wallet address on the blockchain, is received. Also, the Web3 authentication association request determination step preferably includes a procedure of updating information related to Web3 authentication stored in the user database 131 when Web3 authentication has already been associated.
[0068] [Step S16: Associating Web3 Authentication] The control unit 11 executes a process of associating the authenticated user related to the user information acquisition step with the Web3 authentication related to the Web3 authentication association request determination step (step S16, Web3 authentication association execution step). The control unit 11 proceeds to step S17. The Web3 authentication association execution step includes a procedure of updating the user database 131 so that the association is performed.
[0069] The management process preferably includes a series of processes for assigning game tokens (crypto assets) granted by P2E to a wallet so that the game tokens can be used to settle transactions related to games. Steps S17 to S18 are an example of such processes.
[0070] [Step S17: Determining Whether to Grant a Game Token] The control unit 11 executes the game token granting unit 115 in cooperation with the storage unit 13 and the communication unit 14. Then, the control unit 11 executes a process of determining whether to grant a game token, which is a token granted by the P2E game, to the authenticated user's wallet by the game token granting unit 115 (step S17, game token grant determination step). If it is determined that the game token should be granted, the control unit 11 proceeds to step S18. If it is not determined that the game token should be granted, the control unit 11 proceeds to step S19.
[0071] The "game token" involved in the game token grant determination step is a cryptocurrency obtained in a P2E game. The cryptocurrency is realized as a token that can be granted to the wallet described above and stored on a blockchain. The procedure for determining whether to grant a game token in the game token grant determination step is not particularly limited. The procedure includes, for example, a procedure for determining that a game token should be granted when the game token is obtained in a P2E game.
[0072] [Step S18: Granting Game Token] The control unit 11 executes a process of granting the game token related to the game token granting determination step to the crypto asset wallet related to the authenticated user by the game token granting unit 115 (step S18, game token granting step). The control unit 11 then proceeds to step S19.
[0073] After the user signs in through a series of processes related to sign-in, the management device 1 executes a series of processes for making a payment. Steps S19 to S28 are an example of this process.
[0074] [Step S19: Determining whether a payment command has been issued] The control unit 11 executes the payment unit 116 in cooperation with the storage unit 13 and the communication unit 14. Then, the control unit 11 executes a process of determining whether a payment command has been issued from the terminal T or the like by the payment unit 116 (step S19, payment determination step). If it is determined that a command has been issued, the control unit 11 proceeds to step S20. If it is not determined that a command has been issued, the control unit 11 proceeds to step S29.
[0075] In order to provide P2E game players with the convenience of being able to use game tokens for payments without having to go through the trouble of converting game tokens into other currencies and trading them, the management process preferably includes a series of processes related to payments using game tokens. Steps S20 to S21 are an example of such processes.
[0076] [Step S20: Determining Whether Game Token Can Be Used] The control unit 11 executes a process to determine whether the game token granted to the authenticated user's wallet can be used in the payment commanded by the payment unit 116 in the payment determination step (step S20, game token usability determination step). If it is determined that the game token can be used, the control unit 11 proceeds to step S21. If it is not determined that the game token can be used, the control unit 11 proceeds to step S22.
[0077] [Step S21: Payment using game token] The control unit 11 executes a process in which the payment unit 116 performs a process of making a payment related to the payment determination step using the step game token that has been determined to be usable in the game token usability determination step (step S21, game token payment step). The control unit 11 then proceeds to step S24.
[0078] [Step S22: Determining Whether Crypto Assets Can Be Used] The control unit 11 executes a process to determine whether the crypto asset granted to the authenticated user's wallet can be used in the payment commanded in the payment determination step by the payment unit 116 (step S22, crypto asset use possibility determination step). If it is determined that the crypto asset can be used, the control unit 11 proceeds to step S23. If it is not determined that the crypto asset can be used, the control unit 11 proceeds to step S28.
[0079] [Step S23: Settlement using crypto asset] The control unit 11 executes a process in which the settlement unit 116 makes a settlement related to the settlement determination step using the crypto asset determined to be usable in the crypto asset usability determination (step S23, crypto asset settlement step). The control unit 11 then proceeds to step S24.
[0080] In order to provide the user with the convenience of being able to receive a reward in cryptocurrency in accordance with the payment amount without having to go through the procedures for receiving the reward in fiat currency, the management process preferably includes a series of processes for granting the user a reward in accordance with the payment amount. Steps S24 to S25 are an example of such processes.
[0081] [Step S24: Determine whether to grant a reward] The control unit 11 executes the reward granting unit 117 in cooperation with the storage unit 13 and communication unit 14. The control unit 11 then executes a process in which the reward granting unit 117 determines whether to grant a reward in the form of cryptocurrency to the authenticated user's wallet, according to the payment amount of the payment related to the payment determination step (step S24, reward grant determination step). If it is determined that a reward should be granted, the control unit 11 proceeds to step S25. If it is not determined that a reward should be granted, the control unit 11 proceeds to step S26.
[0082] The procedure for determining whether to grant a reward in the reward grant determination step is not particularly limited. This procedure includes, for example, a procedure for determining whether to grant a reward by referring to the reward granting conditions stored in the storage unit 13. In the reward grant determination step, a reward is granted in various forms, such as a cryptocurrency or a so-called coupon.
[0083] [Step S25: Granting a reward in cryptocurrency] The control unit 11 executes a process in which the reward granting unit 117 grants a reward in cryptocurrency to the wallet of the authenticated user according to the payment amount of the payment related to the payment determination step (step S25, reward granting step). The control unit 11 then proceeds to step S26.
[0084] The procedure for awarding the reward in the reward awarding step is not particularly limited, and may include, for example, a procedure for awarding the reward by referring to the reward award rate stored in the storage unit 13.
[0085] [Step S26: Determine whether to award a fee] The control unit 11 executes the fee awarding unit 118 in cooperation with the storage unit 13 and the communication unit 14. The control unit 11 then executes a process in which the fee awarding unit 118 determines whether to award a fee in cryptocurrency to the retailer's wallet according to the payment amount of the payment related to the payment determination step (step S26, fee award determination step). If it is determined that a fee should be awarded, the control unit 11 proceeds to step S27. If it is not determined that a fee should be awarded, the control unit 11 proceeds to step S29.
[0086] The procedure for determining whether to award a fee in the fee award determination step is not particularly limited, and may include, for example, a procedure for determining whether the payment in the payment determination step is a payment related to a transaction via a retailer by referring to the fee award conditions stored in the storage unit 13.
[0087] [Step S27: Granting a fee in cryptocurrency] The control unit 11 executes a process in which the fee granting unit 118 grants a fee in cryptocurrency to the wallet of the retailer according to the payment amount of the payment related to the payment determination step (step S27, fee granting step). The control unit 11 then proceeds to step S29.
[0088] The procedure for granting the fee in the fee granting step is not particularly limited, and may include, for example, a procedure for granting the fee by referring to the fee grant rate stored in the storage unit 13.
[0089] There are cases where it is not possible to make a payment using the crypto assets stored in the crypto asset wallet due to various reasons, such as not possessing a crypto asset wallet or not having a sufficient amount of crypto assets stored in the crypto asset wallet. In order to provide the user with the convenience of automatically making a payment using fiat currency when it is not possible to make a payment using the crypto assets stored in the crypto asset wallet, it is preferable that the management process include a series of processes related to making a payment in fiat currency. Step S28 is an example of such a process.
[0090] [Step S28: Settlement using legal tender] The control unit 11 executes the settlement unit 116 in cooperation with the storage unit 13 and the communication unit 14. Then, the control unit 11 executes a process of settling the settlement related to the settlement determination step using legal tender with the settlement unit 116 (step S28, legal tender settlement step). The control unit 11 proceeds to step S29.
[0091] The legal tender settlement step, for example, calculates the legal tender required to arrange for the cryptocurrency required for the settlement related to the settlement determination step, requests the user for the legal tender, and when the user pays the legal tender, executes a series of processes to make the settlement related to the settlement determination step using the cryptocurrency arranged using the legal tender.
[0092] [Wallet Opening Step] If no wallet is associated with the user information in the User Information Acquisition Step, before the Fiat Currency Payment Step is executed, the management device 1 preferably executes a wallet opening step in which the user opens a cryptocurrency wallet that can be used for payments in the Payment Determination Step. The wallet opening step includes the same procedures as those described above for signing up using Web3 authentication. The wallet opening step also includes the same procedures as those described above for associating Web3 authentication. This allows the management device 1 to manage and support users who do not have a wallet for cryptocurrency payments so that they can open a wallet and make payments.
[0093] To provide participants with the convenience of increasing the value of NFTs without expending labor on the construction of cryptocurrency mining equipment, the management process preferably includes a series of processes for increasing the value of NFTs granted to crowdfunding participants through the progress of a crowdfunding project and mining performed by a mining system, such as a cryptocurrency mining device 2, associated with the project. Steps S29 to S35 are an example of such processes. Through this series of processes, the system S of this embodiment can contribute to the establishment of a "Web3 economic zone," a new decentralized value creation platform. Furthermore, through this series of processes, the system S of this embodiment can realize investments in mining systems, such as the cryptocurrency mining device 2, that are subject to expense accounting. The following describes a case in which the mining system is implemented by the cryptocurrency mining device 2, which is hardware. The same applies when the mining system is implemented by cryptocurrency mining software, which is software. In this case, the software is provided to participants via various recording media, distribution via the network N, or the like. Furthermore, the mining system may be realized by the cooperation of hardware such as the cryptocurrency mining device 2 and software such as cryptocurrency mining software.
[0094] [Step S29: Determine whether an application to participate in the project has been submitted] The control unit 11 executes the application acceptance unit 119 in cooperation with the storage unit 13 and the communication unit 14. The control unit 11 then executes a process of determining whether an application to participate in a project using crowdfunding has been submitted by the application acceptance unit 119 (step S29, application acceptance step). If it is determined that an application to participate has been submitted, the control unit 11 proceeds to step S30. If it is not determined that an application to participate has been submitted, the control unit 11 proceeds to step S32.
[0095] In the application acceptance step, the application acceptance unit 119 of the management device 1 accepts from users applications to participate in a project using crowdfunding. The "crowdfunding project" involved in the application acceptance step is a project that involves the provision of a cryptocurrency mining device 2 and the granting to participants of NFTs whose value increases due to the cryptocurrency mined by the cryptocurrency mining device 2.
[0096] [Step S30: Command to Ship Cryptocurrency Mining Device] The control unit 11 executes the shipping command unit 120 in cooperation with the storage unit 13 and communication unit 14. The control unit 11 then executes a process in which the shipping command unit 120 commands participants, who are users who applied to participate in the application acceptance step, to ship the cryptocurrency mining device 2 related to the project whose application was accepted in the application acceptance step (step S30, shipping command step). The control unit 11 then proceeds to step S31.
[0097] [Step S31: Granting NFT] The control unit 11 executes the NFT granting unit 121 in cooperation with the storage unit 13 and the communication unit 14. Then, the control unit 11 executes a process of granting a non-fungible token (NFT) having value redeemable for crypto assets to the crypto asset wallet of the authenticated user by the NFT granting unit 121 (step S31, NFT granting step). The control unit 11 proceeds to step S32.
[0098] With regard to the NFT granting step, the crypto asset wallet of the authenticated user is also the wallet of the participant, who is the user who applied to participate in the application acceptance step. If information related to Web3 authentication is not stored in the user information, the management device 1 performs a series of processes to create a wallet for the participant, who is the user who applied to participate in the application acceptance step, and associate it with the user information. Note that this series of processes may be similar to the processes related to the association of Web3 authentication described above.
[0099] [Step S32: Determine Whether to Assign Value According to Project Progress Status] The control unit 11 executes the first value assigning unit 122 in cooperation with the storage unit 13 and the communication unit 14. The control unit 11 then executes a process in which the first value assigning unit 122 determines whether to assign value according to the progress status (project progress status) of the project related to the application acceptance step to the NFT related to the NFT assigning step (step S32, first value assignment determination step). If it is determined that value should be assigned, the control unit 11 proceeds to step S33. If it is not determined that value should be assigned, the control unit 11 proceeds to step S34.
[0100] The procedure for determining whether to assign a value according to the project progress status in the first value assignment determination step is not particularly limited. This procedure includes, for example, a procedure for determining that a value according to the project progress status should be assigned when a command to assign a value according to the project progress status is received from the project staff. This procedure also includes, for example, a procedure for making this determination by referring to the project progress status input by the project staff and the value assignment criteria stored in the storage unit 13.
[0101] [Step S33: Assigning a value to the NFT according to the progress status] The control unit 11 executes a process in which the first value assigning unit 122 assigns a value according to the progress status (project progress status) of the project related to the application acceptance step to the NFT related to the NFT assigning step (step S33, first value assigning step). The control unit 11 proceeds to step S34.
[0102] [Step S34: Determining whether mining has been performed] The control unit 11 executes the second value assigning unit 123 in cooperation with the storage unit 13 and communication unit 14. The control unit 11 then executes a process in which the second value assigning unit 123 determines whether crypto assets have been mined by the crypto asset mining device 2 shipped for the project related to the application acceptance step (step S34, second value assignment determination step). If it is determined that value should be assigned, the control unit 11 proceeds to step S35. If it is not determined that value should be assigned, the control unit 11 returns the process to step S1 and repeats the processes from step S1 to step S35.
[0103] [Step S35: Assigning a value corresponding to the crypto asset to the NFT] The control unit 11 executes a process in which the second value assigning unit 123 assigns a value corresponding to the crypto asset mined by the crypto asset mining device 2 shipped for the project related to the application acceptance step to the NFT related to the NFT assigning step (step S35, second value assigning step). The control unit 11 returns the process to step S1 and repeats the processes from step S1 to step S35.
[0104] <Example of Use> The following is an example of use of the management device 1 according to this embodiment.
[0105] [Signing up before opening a crypto-asset wallet] The management device 1 according to this embodiment allows a user to sign up before opening a crypto-asset wallet.
[0106] [Sign-up] First, the user signs up for the management device 1 by Web1 authentication using a password or Web2 authentication using social authentication information or the like.
[0107] [Commercial Transactions Using Crypto Assets] After signing up, when a user conducts a commercial transaction using crypto assets, the management device 1 manages the commercial transaction system so that the user can conduct a commercial transaction using crypto assets. Specifically, the management device 1 manages the opening of a crypto asset wallet or the handling of transactions using legal tender.
[0108] (Opening a crypto asset wallet) When a user selects to open a crypto asset wallet, the management device 1 assists with a series of procedures related to opening the crypto asset wallet and associates the opened crypto asset wallet with the authentication used by the user to sign up. A smart contract is then arranged in which the management device 1 makes payments using the crypto asset assigned to the crypto asset wallet. This allows the management device 1 to enable the user to conduct commercial transactions using crypto assets without requiring the user to perform Web3 authentication each time.
[0109] (Transaction agency via legal tender) If the user selects transaction agency via legal tender, the management device 1 charges the user the legal tender corresponding to the settlement and carries out the commercial transaction using the crypto asset in that legal tender.
[0110] [Simplifying Sign-in After Opening a Crypto Asset Wallet] The management device 1 according to this embodiment simplifies the sign-in process for a user after opening a crypto asset wallet.
[0111] [Signing Up with Web3 Authentication] First, the user signs up to the management device 1 using Web3 authentication, which is authentication using the encryption key of the crypto-asset wallet owned by the user.
[0112] [Associating Web1 Authentication or Web2 Authentication] The user instructs the management device 1 to associate the Web3 authentication signed up in the above procedure with the Web1 authentication or Web2 authentication. The management device 1 associates the Web3 authentication with the Web1 authentication or Web2 authentication. At this time, the management device 1 arranges a smart contract in which the management device 1 makes a payment using the crypto asset assigned to the crypto asset wallet related to the Web3 authentication.
[0113] [Commercial Transactions Using Web1 Authentication or Web2 Authentication] The user signs in using Web1 authentication or Web2 authentication associated with Web3 authentication. The user then instructs the management device 1 to settle the transaction using the crypto asset. The management device 1 settles the transaction using the crypto asset using the above-mentioned association and smart contract.
[0114] [Management of a crowdfunding project] The management device 1 of this embodiment can manage a crowdfunding project. This project is a project that increases the value of NFTs granted to participants in the crowdfunding project through the progress of the project and mining performed by the crypto asset mining device 2 related to the project.
[0115] [Application for Participation] A participant applies to participate in the above-mentioned project. The management device 1 ships the crypto asset mining device 2 related to the project to the participant and grants the above-mentioned NFT to the participant's wallet.
[0116] [Project Progress] Depending on the progress of the project, the management device 1 manages the project by assigning a value to the NFT according to the progress. This allows participants to increase the value of the NFT related to the crypto asset without having to expend effort on, for example, building a device for mining the crypto asset.
[0117] [Cryptocurrency Mining] The management device 1 manages the cryptocurrency mining by the cryptocurrency mining device 2, assigning a value to the NFT according to the mining. This allows participants to increase the value of the NFT related to the cryptocurrency without having to expend effort on building a device to mine the cryptocurrency. Therefore, the system S of this embodiment can contribute to the establishment of the "Web3 economic zone," a new decentralized value creation platform. Furthermore, this allows the system S of this embodiment to realize investment in the cryptocurrency mining device 2, which can be recorded as an expense.
[0118] The management device 1 of this embodiment can be used as described above. As a result, the management device 1 of this embodiment can improve the convenience of transaction participants in electronic commerce transactions where payments are made using crypto assets. Specifically, the management device 1 of this embodiment can enable a user to perform electronic commerce transactions where payments are made using crypto assets even in difficult authentication situations where any two of the following situations occur simultaneously: the user has forgotten their password, the user is unable to use the authentication server, or the user is unable to use the device where the wallet's encryption key is stored.
[0119] It should be noted that within the scope of the concept of the present invention, those skilled in the art may conceive of various modifications and alterations. Therefore, it is understood that such modifications and alterations fall within the scope of the present invention. For example, even if a person skilled in the art appropriately adds, deletes, or modifies components of the above-described embodiment, or adds, omits, or modifies the conditions of a process, such modifications are also included within the scope of the present invention as long as they maintain the gist of the present invention.
[0120] S System 1 Management device 11 Control unit 111 Authentication management unit 112 Web1 authentication unit 113 Web2 authentication unit 114 Web3 authentication unit 115 Game token granting unit 116 Settlement unit 117 Reward granting unit 118 Fee granting unit 119 Application reception unit 120 Shipping command unit 121 NFT granting unit 122 First value granting unit 123 Second value granting unit 13 Storage unit 131 User database 14 Communication unit 2 Crypto asset mining device N Network T Terminal
Claims
1. A management device for an e-commerce site, comprising: a Web1 authentication unit that performs Web1 authentication, which is authentication using a password set by a user; a Web2 authentication unit that performs Web2 authentication, which is authentication using social authentication information that is information indicating successful authentication of the user transmitted from an external authentication server; a Web3 authentication unit that performs Web3 authentication, which is authentication using a cryptographic key of a cryptographic asset wallet owned by the user; an authentication management unit that manages, for each user, the association between two or more of the Web1 authentication, the Web2 authentication, and the Web3 authentication; and a settlement unit that performs settlement using the cryptographic assets stored in the cryptographic asset wallet in response to a command from an authenticated user who has been authenticated by the Web1 authentication, the Web2 authentication, and / or the Web3 authentication.
2. The management device according to claim 1, further comprising a reward granting unit that grants, to the cryptographic asset wallet, a reward corresponding to the settlement amount in the settlement unit in cryptographic assets.
3. The management device according to claim 1, further comprising: an application reception unit that receives, from the user, an application to participate in a project using crowdfunding; a shipping command unit that commands to ship a cryptographic asset mining device to a participant who is a user who has made the participation application; an NFT granting unit that grants a non-fungible token (NFT) having a value exchangeable for cryptographic assets to the cryptographic asset wallet; a first value granting unit that grants a value corresponding to the progress status of the project to the NFT; and a second value granting unit that grants a value corresponding to the cryptographic assets mined by the cryptographic asset mining device to the NFT.
4. The management device according to claim 1, further comprising a fee granting unit that grants, to the retailer, a fee corresponding to the settlement amount related to the settlement in cryptographic assets when the settlement is a settlement related to a transaction via a retailer.
5. The management device according to claim 1, further comprising a game token granting unit that grants a game token, which is a token granted by a game, to the cryptographic asset wallet, and the settlement unit performs settlement using the game token in a transaction related to the game.
6. The management device according to claim 1, wherein the settlement unit performs settlement using legal tender when it is not possible to perform settlement using the cryptographic assets stored in the cryptographic asset wallet.
Citation Information
Patent Citations
Account access during sales
JP2014529779A
Service providing system, service providing method, and program
JP7177303B1
User and device authentication for web applications
US20180101847A1
Computer System and Method for Programmatic Collateralization Services
US20220309479A1