JP2023023438A - Utility token management system - Google Patents

Abstract

To provide a token management system that manages a token associated with provision of service or a product using a block chain without intervention of any paper medium.SOLUTION: A token management system 1000 comprises: a token authentication server 200 that in order to manage a token associated with provision of service or a product using a block chain network (BCN) 100, authenticates a transaction of the token; a token ledger management server 300 for managing a token ledger; a wallet management server 400 for managing a wallet for utilizing the token using a token right holder terminal device 800; and a POS coordination infrastructure management server 500 for coordinating with a POS system that manages the service or the product.SELECTED DRAWING: Figure 1

Description

The present invention relates to a utility token management system that uses blockchain to manage utility tokens related to the provision of services or products.

At the time of B2C (transactions between companies and general consumers), as part of marketing, shareholder benefits, facility use tickets, membership rights, etc. attached to existing listed stocks are provided in paper form.

In B2C marketing using paper media, the following issues (1) and (2) arise from the standpoints of both the implementer (company) and the general consumer (individual) who is the recipient.
(1) Challenges for companies: Acquisition and maintenance of recognition and interest requires a large amount of money.
(2) Issues on the individual side: Advertisements may lead to momentary interest and consumption, but advertisements with a frequency exceeding a threshold may lead to disgust.
In relation to B2C marketing, there are shareholder benefit measures such as "supportive investment" (fan marketing), but the following problems (i) to (ii) have arisen in the existing shareholder benefit measures.

(i) Issues for companies: Shareholder lists are insufficient for marketing in terms of content and freshness. Even if they are attached, it is practically difficult to control after the shareholder's complimentary coupon is issued (such as cash coupon shops), and it is also difficult to grasp the secondary right holder after the shareholder's complimentary coupon is transferred.

(ii) Issues on the individual side: It is complicated, such as the need to manage the expiration date for each shareholder complimentary coupon, and the need to bring it with you when using it, and when you cannot use it, such as when you are not using it and when you exchange it A middleman margin occurs.

The above problems (i) and (ii) are not limited to shareholder complimentary coupons, but can be used for any service or There are also cases where products are provided.

In existing tokenization mechanisms (including security token platforms such as Progmat), tokens are fungible tokens that are substitutable and divisible, and are not independent for each underlying right. None.

On the other hand, an existing non-fungible/non-divisible tokenization mechanism called non-fungible token (NFT) has also been proposed. However, even if it is an NFT, for example, if the right to view digital art is linked to a certain token, the specification may be such that the URL information for displaying the image of the digital art is posted as metadata of the token. It's becoming

Therefore, even if each token ID itself is unique, if a third party consciously or accidentally learns the URL, only the token holder may view the digital art. We do not guarantee that rights such as rights are unique, nor that rights holders can exercise their rights exclusively.

Accordingly, an object of the present invention is to provide a token management system that manages tokens related to the provision of services or products using block chains without using paper media.

Aspects of the token management system of the present invention are as follows.
[Aspect 1]
A token management system that manages tokens related to the provision of services or products,
a blockchain network (BCN);
a token authentication server that configures the nodes of the BCN and authenticates the token transactions;
one or more wallet management servers that configure the nodes of the BCN and manage wallet applications that operate on each of one or more token right holder terminal devices;
A token management system comprising a cooperation management server that constitutes a node of the BCN and cooperates with a service or product management system that manages the service or product.

[Aspect 2]
In the token management system according to aspect 1,
A token management system, wherein the token authentication server, the token ledger management server, the wallet management server, and the cooperation management server each have a first private key for signing the transaction at each node.
[Aspect 3]
In the token management system according to aspect 2,
The token management system, wherein the wallet management server has a second private key for signing a transaction associated with the right holder of the token.
[Aspect 4]
In the token management system according to aspect 3,
The wallet management server is a token management system in which account information of the wallet application is registered in association with a right holder of the token.

[Aspect 5]
In the token management system according to any one of aspects 1 to 4,
The token management system, wherein the wallet management server is set so as not to participate in transfer processing of tokens other than tokens managed by itself.
[Aspect 6]
In the token management system according to aspect 5,
The token management system, wherein the wallet management server has a different private key for each account of the wallet application.
[Aspect 7]
In the token management system according to any one of aspects 1 to 6,
A token management system comprising a matching server that matches exchanges of tokens linked to different services or products among the plurality of right holder terminal devices.

[Aspect 8]
In the token management system according to any one of aspects 1 to 7,
The token management system, wherein the cooperation management server is set so that it cannot sign or approve any token transaction, but only refers to it.
[Aspect 9]
In the token management system according to any one of aspects 1 to 8,
A token management system comprising one or a plurality of token ledger management servers that configure the nodes of the BCN and manage the ledger of the tokens.
[Aspect 10]
In the token management system according to aspect 9,
The token management system has a first public key for each node of the token authentication server, the one or more wallet management servers, the cooperation management server, and the token ledger management server, and for each right holder of the token. A token management system having a second public key at .
[Aspect 11]
In the token management system according to aspect 9 or 10,
A token management system in which the token ledger management server is set so as not to be involved in the ledger rewriting process of tokens other than tokens issued by itself.

[Aspect 12]
In the token management system according to any one of aspects 9 to 11,
The cooperation management server is a token management system that generates a different first serial number for each service or product for which the right of the token is to be exercised.
[Aspect 13]
In the token management system according to aspect 12,
After adding predetermined information to the first serial number, the token ledger management server generates first hashed data using a first secret key linked to the token ledger management server, and performs the first hashing. A token management system that issues tokens containing data.
[Aspect 14]
In the token management system according to aspect 13,
A token management system, wherein the predetermined information includes an ID of the token master management server and a date and time of token issuance.

[Aspect 15]
In the token management system according to aspect 13 or 14,
When the wallet application management server receives token exercise information for exercising the token and receiving the provision of the service or product from the token right holder terminal device, the wallet application management server sends the first hashed data to the token ledger management server. generating the first serial number by decrypting using the associated first public key, generating a read code based on the first serial number, and transmitting the read code to the UT right holder terminal device; Token management system.
[Aspect 16]
In the token management system according to aspect 15,
When generating a read code based on the first serial number, the wallet application management server generates second hashed data obtained by hashing the first serial number using a second secret key associated with the token right holder. and generating the read code from the second hashed data.
[Aspect 17]
In the token management system according to aspect 15 or 16,
The token management system, wherein the read code is a one-dimensional code or a two-dimensional code readable by a terminal device of the service or commodity management system.

[Aspect 18]
In the token management system according to any one of aspects 15-17,
The token management system, wherein the token right holder terminal device displays the read code on a display, and the store terminal device of the service or commodity management system reads the read code.
[Aspect 19]
In the token management system according to any one of aspects 15-18,
The cooperation management server generates a second serial number by decrypting the read code transmitted from the service or product management system using the second public key associated with the token right holder, A token management system that transmits information for providing the service or product related to the first serial number to the service or product management system when the first serial number and the second serial number match.

INDUSTRIAL APPLICABILITY The token management system of the present invention makes it possible to receive provision of any service or product using block chain without intervening paper media. Furthermore, the token management system according to claims 12 to 19 of the present invention enables token rights holders to exercise their rights exclusively.

1 is a configuration diagram including a UT management system according to an embodiment of the present invention; FIG. FIG. 2 is a configuration diagram showing processing when a UT is used in the UT management system of FIG. 1;

An embodiment in which the token management system of the present invention is a utility token (UT) management system will be described with reference to the drawings. In addition, the same code|symbol is attached|subjected to the part which is common in each figure, and description is abbreviate|omitted suitably. The meaning of each term in this embodiment is as follows. A utility token (UT) is a token (electronic voucher) that indicates the right to receive any service or product. A security token (ST) is a token (electronic voucher) that indicates ownership of securities, real estate, movable property, or the like. A transaction (Tx) is transaction data collectively recorded in units of blocks managed by a blockchain network. POS stands for Point Of Sales, and a POS system is a system that records and aggregates information on the provision of services or products for each service or product.

[UT management system]
A configuration diagram of a network including a UT management system 1000 according to an embodiment of the present invention is shown in FIG. The UT management system 1000 includes a distributed ledger or blockchain network (BCN) 100 having multiple nodes with different authorities, a UT authentication server 200, and a UT ledger management server 300 (a first UT ledger management server 300A and a second UT ledger management server 300A). It consists of a management server 300B), a wallet administrator server 400 (a first wallet administrator server 400A and a second wallet management server 400B), and a POS linkage base management server 500. UT management system 1000 may also include merchant POS system 600 , UT issuer server 700 , and/or UT rights holder terminal 800 .

The BCN 100 includes nodes AN, NN, and CN, which will be described later.
The UT authentication server 200 includes a notary node NN for verifying (monitoring) UT double consumption and approving Tx updates, a database (not shown) for performing predetermined data processing, and a notary node NN ( It has a secret key NK for signing Tx at its own node) and a control unit (not shown) that executes various processes using the notary node NN and the secret key NK.

The UT management system 1000 has a first public key for each of the nodes of the UT authentication server 200, the wallet management server 400, the POS linkage infrastructure management server 500, and the UT master book management server 300. FIG. The UT management system 1000 has a second public key for each right holder of the token. In this embodiment, when each server performs encryption (hashing), it uses a "private key owned by the server that executes encryption" (a private key known only to the server) to decrypt (decode). At times, the "encrypted public key of the server" (a public key corresponding to the private key that can be known by participating in the BCN 100) is used.

Hereinafter, the first UT ledger management server 300A and the second UT ledger management server 300B will be referred to as the UT ledger management server 300 when not distinguished from each other. Similarly, hereinafter, when the first UT and the second UT are not distinguished, they are called UTs. Each UT is composed of multiple UTs each associated with a different right holder or owner.

The first UT ledger management server 300A includes a first asset node AN for approving Tx updates for the first UT, a relational database RDB for executing predetermined and consistent data processing, and a first asset node AN (own node). and a control unit (not shown) that executes various processes using the first asset node AN and the secret key NK. The first asset node AN of the first UT ledger management server 300A is set so as not to participate in the ledger rewriting process of UTs other than the first UT (UT issued by itself) such as the second UT.

The second UT ledger management server 300B includes a second asset node AN for approving Tx updates for the second UT, a relational database RDB for executing predetermined and consistent data processing, and a second asset node AN (own node). and a control unit (not shown) that executes various processes using the second asset node AN and the secret key NK. The second asset node AN of the second UT ledger management server 300B is set so as not to participate in the ledger rewriting process of UTs other than the second UT (UT issued by itself) such as the first UT.

In this embodiment, two of the first UT ledger management server 300A and the second UT ledger management server 300B are shown. can. The first UT ledger management server 300A can be a ledger management server that manages the first UT (shareholder benefits, etc.) associated with ST, which is a digital security. The second UT ledger management server 300B can be a ledger management server that manages the second UTs associated with securities ledger such as listed stocks. The UT issuer server 700 instructs the first UT ledger management server 300A and/or the second UT ledger management server 300B to issue each UT.

Hereinafter, the first wallet management server 400A and the second wallet management server 400B will be referred to as the wallet management server 400 when not distinguished from each other. The first wallet management server 400A comprises a first custodian node CN for managing Tx, a relational database RDB for executing predetermined consistent data processing, and an arbitrary A private key NK for signing the Tx of the first UT, a private key AK for signing the Tx associated with the first UT for each rights holder (account) of the first UT at the first custodian node CN, and the first custodian It also has a control unit (not shown) that executes various processes using the unnode CN and secret keys NK and AK. The first custodian node CN is set so as not to participate in transfer processing of UTs other than the first UT (UT managed by itself) such as the second UT.

The second wallet management server 400B comprises a second custodian node CN for managing Tx, a relational database RDB for executing predetermined consistent data processing, and an arbitrary A private key NK for signing the Tx of the second UT, a private key AK for signing the Tx associated with the second UT for each rights holder (account) of the second UT at the second custodian node CN, and a second custodian It has a control unit (not shown) that executes various processes using the unnode CN and secret keys NK and AK. The second custodian node CN is set so as not to participate in the ledger processing of UTs other than the second UT (UT managed by itself) such as the first UT.

Although two wallet management servers 400A and 400B are shown in this embodiment, the UT management system 1000 can include any number of wallet management servers 400 without being limited to this. .

A POS linkage base management server (linkage management server) 500 is communicably connected to the UT ledger management server 300 and member store POS system (service or product information management system) 600 . The POS linkage infrastructure management server 500 cooperates with the POS system 600 to execute processing for providing services or products based on the first UT and the second UT. The POS system 600 is composed of a plurality of store terminals 610 and a POS server 620 that transmits and receives service or product information to and from the plurality of store terminals 610 .

The POS linkage infrastructure management server 500 has a reference node RN that can only refer to Tx, a relational database RDB that executes predetermined and consistent data processing, and a reference node RN (self node) for UT related to a predetermined store. It comprises a secret key NK for referring to the Tx of the UT related to the service or product provided by the POS server 620, and a control unit (not shown) that executes various processes using the reference node RN and the secret key NK. ing. The reference node RN is set up so that it cannot sign (approve) any Tx, it can only refer to it.

The POS server 620 is communicably connected to a plurality of store terminal devices 610 . The POS system consists of a POS server 620 and a plurality of store terminals 610 .

[UT rights holder terminal device]
Hereinafter, the first UT rights holder terminal device 800A and the second UT rights holder terminal device 800B will be referred to as the UT rights holder terminal device 800 when not distinguished from each other. A plurality of first UT rights holder terminal devices 800A are communicably connected to the first wallet management server 400A. A wallet application is installed in each first UT right holder terminal device 800A for executing the first UT processing (update information reflection, etc.) via the first wallet management server 400A. A plurality of second UT rights holder terminal devices 800B are communicably connected to the second wallet management server 400B. Each second UT right holder terminal device 800B is installed with a wallet application for executing second UT processing (update information reflection, etc.) via the second wallet management server 400B. The wallet management server 400 registers wallet application account information in association with UT rights holders.

The UT rights holder terminal device 800 is a smart phone, a tablet terminal, or a personal computer. The owner of the first UT rights holder terminal device 800A and/or the owner of the second UT rights holder terminal device 800B are, for example but not limited to, investors in securities such as digital securities and/or listed stocks. be able to.

[UT matching server]
The UT matching server 900 is communicably connected to the first UT rights holder terminal device 800A, the second UT rights holder terminal device 800B, the first wallet management server 400A, and the second wallet management server 400B. The UT matching server 900 includes a relational database RDB that executes predetermined consistent data processing, and a control unit (not shown) that executes matching processing. The UT matching server 900 performs a matching process that matches exchanges of UTs between the first UT and the second UT.

[Specific processing of POS linkage]
1. Link code/UT link processing (when issuing UT (encrypted))
In the UT management system 1000 of this embodiment, the linking code/UT linking process at the time of UT issuance will be described with reference to FIG.
UT issuer server 700 transmits a UT issuance instruction to UT master record management server 300 in step S101. After receiving the UT issuance instruction from the UT issuer server 700, the UT ledger management server 300 receives service or product information from the POS server 620 in step S102. Based on the received service or product information, the UT ledger management server 300 sends a request for issuance of a linkage code (first serial number (x)) to the POS linkage base management server 500 in step S103.

Upon receiving a link code issuance request from the UT ledger management server 300, the POS link base management server 500, in step S104, assigns a different first serial number (x) to each service or product for which UT rights are to be exercised. It issues (generates) and notifies the first serial number (x) to the UT master book management server 300 that issues the UT. As a result, the first serial number (x) can be linked (shared) between the UT ledger management server 300 and the POS linkage infrastructure management server 500 . Note that the POS linkage infrastructure management server 500 can transmit the first serial number (x) to the POS server 620 . The store terminal device 610 can receive and confirm (share) the first serial number (x) from the POS server 620 .

In step S105, the UT master book management server 300 adds the UT master book management server ID (y) and the UT issue date and time (z) to the received first serial number (x) to generate a second linkage code X (X=x+y+z). Generate. The UT ledger management server 300 generates first hashed (encrypted) data by hashing the second cooperation code X using the secret key NK. This allows the UT ledger management server 300 to issue a UT containing a Tx having the first hashed data as the "token ID" (X').

A "UT original manager ID" (y) and a "UT issue date and time" (z) are registered in the issued UT. The UTs shall be visible to the nodes NN, AN, CN and RN of the relational servers 200 , 300 , 400 , 500 participating in the UT management system 1000 .

2. Link code/UT link processing (when using UT (decryption/conversion/display))
In the UT management system 1000 of this embodiment, the linking code/UT linking process when using a UT will be described with reference to FIG.
When the UT right holder (operator of the UT right holder terminal device 800) exercises the right of the UT and receives the service or goods, the UT right holder terminal device 800 detects the operation (tap) of the UT exercise button of the wallet application. Then, the UT right holder terminal device 800 transmits UT exercise information to the wallet application management server 400 in step S201.

Upon receiving the UT exercise information, the wallet application management server 400 decrypts the "token ID" (X') to be used using the first public key of the UT ledger management server 300 in step S202, and generates the second linkage code X (x+y+z) is obtained.

In step S203, the wallet application management server 400 obtains the first serial number (x) by removing the "UT original management ID" (y) and the "UT issue date" (z) from the second linkage code X. In step S204, the wallet application management server 400 generates second hashed data ( Obtain the "first serial number after hashing" (x')).

The wallet application management server 400 converts the “first serial number after hashing” (x′) into a read code and transmits it to the UT right holder terminal device 800 in step S205. UT rights holder terminal device 800 displays the read code on the display of UT rights holder terminal device 800 using the wallet application in step S206A. The read code can be a one-dimensional code (barcode) or a two-dimensional code (QR code (registered trademark)).

3. Link code/UT link method (when UT is consumed (reading/converting/writing))
In step S206B, the store terminal device 610, which is a provider of UT-based services or products, reads the read code displayed on the display of the UT right holder terminal device 800 via a reading device, and "hashed A later first serial number” (x′) is generated, and in step S207, the “first serial number after hashing” (x′) is sent to the POS server 620 .

The POS server 620 transmits the received "first serial number after hashing" (x') to the POS linkage infrastructure management server 500 in step S208. In step S209, the POS linkage infrastructure management server 500 decrypts the received "first serial number after bashing" (x') using the second public key of the UT right holder, and converts the received "second serial number" ( x).

In step S210, the POS linkage infrastructure management server 500 determines whether or not the decrypted "second serial number" (x) matches the "first serial number" (x) issued by itself. If a match with the "first serial number" (x) is determined in step S210, the POS linkage infrastructure management server 500, in step S211, is specified by the POS server 620 and displayed on the shop terminal device 610 via the POS server 620 .

In step S212, the store terminal device 601 provides the service or product based on the content of the service or product specified by the POS system, and notifies the POSPOS server 620 of the "first serial number" (x) as used. Request number reconciliation and exit.

The processing by the UT management system 1000 according to the present embodiment described above can be summarized as mechanisms (1) to (3) described below. Based on these mechanisms (1) to (3), the exercise of rights for services or products displayed on the UT can only be exercised by the "UT rights holder" who is registered as the owner of the rights on the UT management system 1000. technically guarantee that it is possible.

(1) The UT ledger management server 300 issues a UT as a token ID, which is a code obtained by hashing a POS linkage code (serial number that differs for each service) using its own secret key.
(2) The UT rights holder terminal device 800 decrypts the token ID using the first public key of the UT ledger management server 800, obtains the POS linkage code, and uses the private key of the UT rights server 600 to Then, the hashed code is converted into a read code and displayed on the display of the UT right holder terminal device 800 .
(3) The store terminal device 610 of the POS system 600 reads the read code, and the POS system 600 obtains the POS linkage code before hashing using the UT right holder's second public key through the POS linkage infrastructure management server 500. Then, the store terminal device 610 displays, on the store terminal device 610, the content of the service or product that is uniquely associated with the cooperation code.

[summary]
The UT management system 1000 according to the present embodiment handles rights such as preferential treatment attached to existing listed stocks and usage rights attached to ST as digital securities tokenized using the BCN 100 as securities or digital securities. "Issue", "transfer", "use", and "redemption" are possible as independent UTs that are differentiated. By using the right holder terminal device 800 equipped with the wallet application according to the embodiment of the present invention, it is possible to digitally complete the process from issuance/granting to clearing of each right etc. Capturing usage history and the like is also possible on the UT management system 1000 .

In addition, each incidental right can be exercised only by a person who is registered as a right holder on the UT management system 1000 (BCN 100), and it is impossible to falsify the right information. Transactions can be made in a form that guarantees quality, and can be executed directly between individuals without going through an intermediary.

When using the UT (when exercising the right), by performing the "exercise right" process on the mobile wallet application running on each right holder terminal device 800, A read code for linking with the POS system 600 (displaying discounted prices and reconciling provided services) can be displayed and services or products can be received.

The "reading code" is generated based on a different "first serial number" for each service or product. By using “token ID”, it can be issued as a non-fungible token (NFT).

When the UT is used and reflected on the POS system, the issuer of the "linkage code" decrypts it using the second public key of the UT right holder, obtains the "second serial number", and compares it with the "first serial number". It is possible to technically guarantee that only those who are registered as UT rights holders on the UT management system 1000 can exercise their rights by the mechanism that needs to be done and the above-described NFT mechanism.

Furthermore, according to the UT management system 1000, the following benefits are obtained for both the implementer (company) and the recipient (individual) of the support investment.
(Profits for companies) Compared to existing coupons, the human load and costs for printing, paper management, delivery, etc. are reduced. Appropriate marketing measures can be planned by maximizing recognition and usage opportunities through relocation, and by grasping rights holders and exercise status in real time. Due to the above effect, the effectiveness of "supportive investment" will be improved, and a support base of loyal customers with high engagement ("same ship" awareness) will be built.
(Individual Benefits) The complexity associated with the management and use of various granted rights is eliminated. It is possible to transfer to a third party or exchange with another UT without burdening the middleman's margin, which improves satisfaction.

1000 UT management system 100 Blockchain network (BCN)
200 UT Authentication Server 300 UT Ledger Management Server 400 Wallet Management Server 500 POS Linkage Base Management Server 600 POS System 610 Store Terminal Device 620 POS Server 700 UT Issuer Server 800 UT Rights Holder Terminal Device 900 Matching Server

Claims (19)

A token management system that manages tokens related to the provision of services or products,
a blockchain network (BCN);
a token authentication server that configures the nodes of the BCN and authenticates the token transactions;
one or more wallet management servers that configure the nodes of the BCN and manage wallet applications that operate on each of one or more token right holder terminal devices;
A token management system comprising a cooperation management server that constitutes a node of the BCN and cooperates with a service or product management system that manages the service or product. The token management system of claim 1, wherein
A token management system, wherein the token authentication server, the token ledger management server, the wallet management server, and the cooperation management server each have a first private key for signing the transaction at each node. In the token management system of claim 2,
The token management system, wherein the wallet management server has a second private key for signing a transaction associated with the right holder of the token. In the token management system of claim 3,
The wallet management server is a token management system in which account information of the wallet application is registered in association with a right holder of the token. In the token management system according to any one of claims 1 to 4,
The token management system, wherein the wallet management server is set so as not to participate in transfer processing of tokens other than tokens managed by itself. In the token management system of claim 5,
The token management system, wherein the wallet management server has a different private key for each account of the wallet application. A token management system according to any one of claims 1 to 6,
A token management system comprising a matching server that matches exchanges of tokens linked to different services or products among the plurality of right holder terminal devices. A token management system according to any one of claims 1 to 7,
The token management system, wherein the cooperation management server is set so that it cannot sign or approve any token transaction, but only refers to it. A token management system according to any one of claims 1 to 8,
A token management system comprising one or a plurality of token ledger management servers that configure the nodes of the BCN and manage the ledger of the tokens. A token management system according to claim 9,
The token management system has a first public key for each node of the token authentication server, the one or more wallet management servers, the cooperation management server, and the token ledger management server, and for each right holder of the token. A token management system having a second public key at . In the token management system according to claim 9 or 10,
A token management system in which the token ledger management server is set so as not to be involved in the ledger rewriting process of tokens other than tokens issued by itself. A token management system according to any one of claims 9 to 11,
The cooperation management server is a token management system that generates a different first serial number for each service or product for which the right of the token is to be exercised. 13. The token management system of claim 12, wherein
After adding predetermined information to the first serial number, the token ledger management server generates first hashed data using a first secret key linked to the token ledger management server, and performs the first hashing. A token management system that issues tokens containing data. 14. The token management system of claim 13, wherein
A token management system, wherein the predetermined information includes an ID of the token master management server and a date and time of token issuance. A token management system according to claim 13 or 14,
When the wallet application management server receives token exercise information for exercising the token and receiving the provision of the service or product from the token right holder terminal device, the wallet application management server sends the first hashed data to the token ledger management server. generating the first serial number by decrypting using the associated first public key, generating a reading code based on the first serial number, and transmitting the reading code to the UT right holder terminal device; Token management system. 16. The token management system of claim 15, wherein
When generating a read code based on the first serial number, the wallet application management server generates second hashed data obtained by hashing the first serial number, and generates the read code from the second hashed data. Generate token management system. 17. A token management system according to claim 15 or 16,
The token management system, wherein the read code is a one-dimensional code or a two-dimensional code readable by a terminal device of the service or commodity management system. 18. A token management system according to any one of claims 15-17,
The token right holder terminal device displays the read code on a display, and the store terminal device of the service or commodity management system reads the read code. 19. A token management system according to any one of claims 15-18,
The cooperation management server generates a second serial number by decrypting the read code transmitted from the service or product management system using the second public key associated with the token right holder, A token management system that transmits information for providing the service or product related to the first serial number to the service or product management system when the first serial number and the second serial number match.

Images