Coin anti-counterfeiting verification method and computer

Abstract

The application provides a coin anti-counterfeiting verification method and a computer. The coin is locally verified locally, and coin information is sent to a cloud server to perform cloud verification on the coin, so that the coin can be prevented from being cracked, counterfeited or forged, and the coin can also be prevented from circulating between different merchants to affect economic benefits. Meanwhile, the cloud server returns verification results and coin value information corresponding to the coin, so that one coin can correspond to different countermeasures, and the use range of the coin is improved.

Description

Technical Field

[0001] This invention relates to the field of coin anti-counterfeiting verification technology, and more specifically, to a coin anti-counterfeiting verification method and a computer. Background Technology

[0002] In the existing technology, taking claw machines as an example, claw machines have become a very popular entertainment activity. Users purchase coins for claw machines at a certain price, and then insert the coins into the claw machine to participate in the claw machine activity.

[0003] Since claw machines are usually unattended, preventing counterfeit coins from being inserted is an urgent problem. A Chinese invention patent (application number: CN200610117445.3) proposes a duplex stainless steel with special magnetic properties and its manufacturing method. This invention controls the ferrite content through compositional adjustments, thereby developing a duplex stainless steel with unique magnetic properties, excellent corrosion resistance, and good formability. This distinguishes its magnetic properties from common stainless steel and carbon steel on the market, thus providing anti-counterfeiting features.

[0004] However, simply using the game coins minted in the aforementioned patents still cannot solve the problem of game coins being counterfeited, altered, or reused. Summary of the Invention

[0005] In view of the shortcomings of the existing technology, the purpose of this invention is to provide a coin anti-counterfeiting verification method and computer, so as to overcome the problem that the existing technology cannot solve the problem of game coins being counterfeited, altered or reused simply by using special processes to mint coins.

[0006] The above-mentioned technical objective of this invention is achieved through the following technical solution: a coin anti-counterfeiting verification method, applied to a coin acceptor, comprising:

[0007] Retrieve the first verification information stored within the coin;

[0008] The coin is locally verified based on the first verification information stored within it, and the local verification result is obtained.

[0009] If the local verification result is true, retrieve the second verification information stored in the coin and send the second verification information to the cloud server to perform cloud verification on the coin;

[0010] Receive the cloud verification result returned by the cloud server; if the cloud verification result is true, complete the coin insertion according to the coin's value.

[0011] Optionally, obtaining the first verification information stored within the coin includes: obtaining the token value stored within the coin.

[0012] Optionally, the step of performing local verification on the coin based on the first verification information stored within the coin to obtain a local verification result includes:

[0013] Obtain the username and password logged in to the coin acceptor, verify the username, password and token value, and determine whether the token value is valid. If valid, return the local verification result that the coin is real; if invalid, return the local verification result that the coin is fake.

[0014] Optionally, the step of verifying the username, password, and token value, and determining whether the token value is valid, includes:

[0015] Check if the token has expired; if it has expired, then the token value is deemed invalid.

[0016] Determine if the token has been tampered with; if it has been tampered with, then the token value is deemed invalid.

[0017] Determine if the token is associated with a user. If it is not associated with a user, then the token value is considered invalid.

[0018] Optionally, determining whether the token value is valid further includes:

[0019] Decompose the token into a header ciphertext, a payload ciphertext, and a signature ciphertext;

[0020] Decrypt the ciphertext of the title using a preset decryption algorithm to obtain the token type and signature algorithm;

[0021] The concatenated ciphertext is obtained by concatenating the ciphertext of the title and the ciphertext of the payload.

[0022] The concatenated ciphertext is verified sequentially using the valid public key and the aforementioned signature algorithm, following the order of local public key priority from highest to lowest.

[0023] If any valid public key is successfully verified, the token is considered valid; if all valid public keys are invalid, the token is considered invalid.

[0024] A coin anti-counterfeiting verification method, applied to a cloud server, includes:

[0025] Receive the second verification information sent by the coin acceptor, compare the second verification information with the historical data of cloud verification, and obtain the cloud verification result;

[0026] Send the cloud verification result to the coin acceptor.

[0027] Optionally, the second verification information received from the coin acceptor includes: user information associated with the coin acceptor and ID information corresponding to each coin.

[0028] Optionally, comparing the second verification information with historical data from cloud verification to obtain the cloud verification result includes:

[0029] Determine whether the ID information is pre-stored in the cloud database; if not, return a cloud verification result indicating that the coin is fake.

[0030] Determine whether the ID information is disabled; if so, return a cloud verification result indicating that the coin is fake.

[0031] Determine whether the ID information is associated with the user information. If not, return a cloud verification result indicating that the coin is fake.

[0032] Based on the ID information, determine whether the coin has been reused within a predetermined time threshold. If so, return a cloud verification result indicating that the coin is fake.

[0033] Optionally, it also includes: obtaining the coin's value information and returning the coin's value information to the coin acceptor.

[0034] A computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps of the method described above.

[0035] In summary, the present invention has the following beneficial effects: This application proposes a coin anti-counterfeiting verification method, which verifies the coin locally and sends the coin information to a cloud server for cloud verification. This can prevent the coin from being cracked, counterfeited, or faked, and can also prevent the coin from circulating between different merchants and affecting economic benefits. At the same time, the cloud server returns the coin's corresponding value information along with the verification result, enabling a coin to correspond to different values ​​and increasing the coin's scope of use. Attached Figure Description

[0036] Figure 1 This is a flowchart of the coin anti-counterfeiting verification method applied to coin acceptors according to the present invention;

[0037] Figure 2 This is a flowchart of the coin anti-counterfeiting verification method applied to a cloud server according to the present invention;

[0038] Figure 3 This is an internal structural diagram of a computer device in an embodiment of the present invention. Detailed Implementation

[0039] To make the objectives, features, and advantages of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Several embodiments of the present invention are shown in the drawings. However, the present invention can be implemented in many different forms and is not limited to the embodiments described herein.

[0040] In this invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," "linking," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances. The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined with "first" or "second" may explicitly or implicitly include one or more of that feature.

[0041] In this invention, unless otherwise expressly specified and limited, "above" or "below" a second feature can include direct contact between the first and second features, or contact between the first and second features through another feature between them. Furthermore, "above," "over," and "on top" of a second feature includes the first feature being directly above or diagonally above the second feature, or simply indicates that the first feature is at a higher horizontal level than the second feature. "Below," "below," and "under" of a second feature includes the first feature being directly below or diagonally below the second feature, or simply indicates that the first feature is at a lower horizontal level than the second feature. The terms "vertical," "horizontal," "left," "right," "above," "below," and similar expressions are for illustrative purposes only and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed or operated in a specific orientation, and therefore should not be construed as limiting the invention.

[0042] The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0043] This invention provides a method for verifying the authenticity of coins, such as... Figure 1 As shown, it is applied to a coin acceptor and includes:

[0044] S1. Obtain the first verification information stored in the coin;

[0045] S2. Perform local verification on the coin based on the first verification information stored in the coin to obtain the local verification result;

[0046] S3. If the local verification result is true, obtain the second verification information stored in the coin and send the second verification information to the cloud server to perform cloud verification on the coin.

[0047] S4. Receive the cloud verification result returned by the cloud server; if the cloud verification result is true, complete the coin insertion according to the coin's value.

[0048] In practical applications, the algorithm used for coin anti-counterfeiting consists of two parts. When the device receives a coin, it first verifies the coin locally. If the local verification result is genuine, the coin is then sent to the cloud server for verification. The cloud verification result is then returned to the coin acceptor. If the cloud verification result is genuine, the coin acceptor accepts the coin; if the cloud verification result is false, the coin is rejected. If the cloud verification is genuine, the cloud server also sends a coin value along with the verification result, based on a pre-set coin value. After receiving this coin value data, the coin acceptor can control the corresponding device to perform actions based on the coin value data while completing the coin acceptance verification.

[0049] To illustrate the above process, let's take claw machines as an example. Since the economic development of different regions varies, the price for claw machines needs to be determined based on the actual economic situation of the region to avoid affecting the business's profitability due to excessively high or low prices. After purchasing coins, customers need to select the corresponding claw machine and insert the purchased coins (i.e., game tokens) into the coin acceptor. To prevent coins from being counterfeited, altered, or reused through other means, or from purchasing coins from merchant A and inserting them into merchant B's machine, this application first requires local verification of the coins. The local verification steps include: firstly, a preliminary inspection of the coin to see if it contains pre-stored information. If the coin does not contain pre-stored information, it indicates that the coin is invalid or has a problem, and therefore the insertion is refused; then, based on the information stored in the coin, it is determined whether the coin and the coin acceptor belong to the same merchant; if so, the encrypted information stored in the coin is verified to obtain a verification result. If the verification result is true, the information in the coin is sent to the cloud server for verification via the communication module. Because claw machines typically operate unattended, and to prevent operators from using fraudulent means to infringe on the rights of other operators, it's necessary to record coin insertions and prevent duplicate insertions. This avoids harming others' interests, especially when encrypted anti-counterfeiting verification is possible. Therefore, this application also requires recording coin insertions. This involves sending coin information to a cloud server via a communication module, recording the coin insertion details, analyzing historical records, and obtaining a cloud verification result. If the cloud verification result is valid, it is returned to the coin acceptor along with the coin value. As mentioned at the beginning of this paragraph, the coin value needs to be determined based on different regions. Generally, the coin value can be modified through a cloud database. For example, when purchasing coins, the information within the coin can be read, and the corresponding coin value can be modified in the cloud. This allows even the same coin to correspond to different coin values. When purchasing 10 chances to play the claw machine at once, you can provide the buyer with 10 coins. For ease of carrying, you can also choose to provide 5 coins. Each coin corresponds to two chances to play the claw machine. Similarly, you can use one coin to correspond to other numbers of chances.

[0050] Furthermore, obtaining the first verification information stored within the coin includes: obtaining the token value stored within the coin.

[0051] In practical applications, to maintain network connectivity and distinguish different coin acceptors, a user account needs to be set up in the coin acceptor to ensure it remains connected to the cloud server. A token is a string generated by the server that serves as a token for client requests. Upon the first login, the server generates a token and returns it to the client. Subsequent requests only require this new token, eliminating the need for a username and password. This method effectively reduces the computational load on the server for encryption verification, thus lowering the server's workload. Token validity is time-limited. After a user purchases coins, the cloud server refreshes the token and checks within a predetermined time to see if the corresponding coins have been used. Coins exceeding this time limit require manual processing by staff.

[0052] Furthermore, the step of performing local verification on the coin based on the first verification information stored within the coin to obtain a local verification result includes:

[0053] Obtain the username and password logged in to the coin acceptor, verify the username, password and token value, and determine whether the token value is valid. If valid, return the local verification result that the coin is real; if invalid, return the local verification result that the coin is fake.

[0054] Furthermore, the verification of the username, password, and token value, and the determination of whether the token value is valid, includes:

[0055] Check if the token has expired; if it has expired, then the token value is deemed invalid.

[0056] Determine if the token has been tampered with; if it has been tampered with, then the token value is deemed invalid.

[0057] Determine if the token is associated with a user. If it is not associated with a user, then the token value is considered invalid.

[0058] Furthermore, the determination of whether the token value is valid also includes:

[0059] Decompose the token into a header ciphertext, a payload ciphertext, and a signature ciphertext;

[0060] Decrypt the ciphertext of the title using a preset decryption algorithm to obtain the token type and signature algorithm;

[0061] The concatenated ciphertext is obtained by concatenating the ciphertext of the title and the ciphertext of the payload.

[0062] The concatenated ciphertext is verified sequentially using the valid public key and the aforementioned signature algorithm, following the order of local public key priority from highest to lowest.

[0063] If any valid public key is successfully verified, the token is considered valid; if all valid public keys are invalid, the token is considered invalid.

[0064] In practical applications, the plaintext header includes the token type and signature algorithm. This embodiment uses JWT as an example. The signature algorithm can be based on RSASHA, ECDSASHA, or RSAPSSSHA series, taking into account system security, load, and response time limits. The signature encryption algorithm for issuing tokens can even be dynamically adjusted to improve system security. The plaintext payload extracts token metadata, which can include the token issuance time, validity period, and issuer. The plaintext header and payload are encoded using base64 or base64url to obtain the ciphertext header and payload. The token management module uses its private key to generate a signature ciphertext from the concatenated ciphertext header and payload using the signature algorithm in the header. This signature ciphertext is then appended to the ciphertext header and payload to obtain the token returned to the requester. The public key sequence refers to prioritizing public keys according to their generation time, with the newest public key having the highest priority. At least two priority public keys must be maintained during operation. Initially, the system automatically generates a highest-priority public key, forming the public key sequence. Whenever a new public key is added, it is set to the highest priority, and the priority of the existing public keys is gradually reduced until they are reduced to invalid public keys. Invalid public keys need to be cleaned up.

[0065] A coin anti-counterfeiting verification method, applied to a cloud server, includes:

[0066] Receive the second verification information sent by the coin acceptor, compare the second verification information with the historical data of cloud verification, and obtain the cloud verification result;

[0067] Send the cloud verification result to the coin acceptor.

[0068] In practical applications, after a coin has been verified in a local coin acceptor and the verification result is obtained, the information in the coin also needs to be sent to the cloud for verification. The cloud verification mainly involves analyzing and statistically processing the coin's information to determine whether there are any abnormalities in the coin's usage process.

[0069] Furthermore, the second verification information received from the coin acceptor includes: user information associated with the coin acceptor and ID information corresponding to each coin.

[0070] Furthermore, comparing the second verification information with historical data from cloud verification to obtain the cloud verification result includes:

[0071] Determine whether the ID information is pre-stored in the cloud database; if not, return a cloud verification result indicating that the coin is fake.

[0072] Determine whether the ID information is disabled; if so, return a cloud verification result indicating that the coin is fake.

[0073] Determine whether the ID information is associated with the user information. If not, return a cloud verification result indicating that the coin is fake.

[0074] Based on the ID information, determine whether the coin has been reused within a predetermined time threshold. If so, return a cloud verification result indicating that the coin is fake.

[0075] In practical applications, determining whether a coin is abnormal can be done from the following dimensions. First, check if the coin's ID is pre-stored on a cloud server. If not, it indicates the coin does not belong to the company or is counterfeited or altered, thus failing verification. Second, check if the coin is disabled. For example, if a coin is sold after a predetermined time or marked as lost, it needs to be marked as disabled on the cloud server. The coin can only be reactivated after authorized personnel modify and refresh its status. If both of these conditions are met, further verification is needed to determine if the coin is linked to a merchant. This prevents losses to merchants by using coins purchased at merchant A at merchant B and also avoids disrupting market order by allowing coins to circulate between different regions. Finally, it is necessary to determine whether the coin has been reused in a short period of time. Specifically, in the usage scenario of coin acceptors, there is usually no situation where a coin can be reused in a short period of time. That is, once a coin is put into the coin acceptor, it is difficult to reuse it within a certain period of time. Therefore, if a coin is reused in a short period of time, it indicates that the usage status of the coin is abnormal. As a result, the cloud server will refuse to recognize the coin to avoid losses to the interests of the operation and management personnel.

[0076] In summary, this application provides a coin anti-counterfeiting verification method that, through verification at both local and cloud levels, can effectively prevent coins from being counterfeited or from circulating between different devices in violation of the agreement, thus avoiding situations that could affect the interests of merchants.

[0077] Furthermore, it also includes: obtaining the coin's value information and returning the coin's value information to the coin acceptor.

[0078] By returning the coin verification result along with the coin value information to the coin acceptor, a single coin can be associated with different values, thereby increasing the coin's usability.

[0079] As those skilled in the art will understand, in the specific embodiments of this application, the coin is only one specific implementation method. It can be a traditional round metal coin, or an item made of plastic or similar materials. Similarly, its application scenarios should not be limited to claw machines, but should also include entertainment devices such as racing game machines and dance machines, all of which can achieve the purpose of coin verification through the coin anti-counterfeiting method provided in this application.

[0080] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 3 As shown, the computer device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage medium. When the computer program is executed by the processor, it implements a coin anti-counterfeiting verification method.

[0081] Those skilled in the art will understand that Figure 3 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0082] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps: applied to a coin acceptor, including:

[0083] Retrieve the first verification information stored within the coin;

[0084] The coin is locally verified based on the first verification information stored within it, and the local verification result is obtained.

[0085] If the local verification result is true, retrieve the second verification information stored in the coin and send the second verification information to the cloud server to perform cloud verification on the coin;

[0086] Receive the cloud verification result returned by the cloud server; if the cloud verification result is true, complete the coin insertion according to the coin's value.

[0087] In one embodiment, obtaining the first verification information stored within the coin includes: obtaining the token value stored within the coin.

[0088] In one embodiment, the step of performing local verification on the coin based on the first verification information stored within the coin to obtain a local verification result includes:

[0089] Obtain the username and password logged in to the coin acceptor, verify the username, password and token value, and determine whether the token value is valid. If valid, return the local verification result that the coin is real; if invalid, return the local verification result that the coin is fake.

[0090] In one embodiment, verifying the username, password, and token value, and determining whether the token value is valid, includes:

[0091] Check if the token has expired; if it has expired, then the token value is deemed invalid.

[0092] Determine if the token has been tampered with; if it has been tampered with, then the token value is deemed invalid.

[0093] Determine if the token is associated with a user. If it is not associated with a user, then the token value is considered invalid.

[0094] In one embodiment, determining whether the token value is valid further includes:

[0095] Decompose the token into a header ciphertext, a payload ciphertext, and a signature ciphertext;

[0096] Decrypt the ciphertext of the title using a preset decryption algorithm to obtain the token type and signature algorithm;

[0097] The concatenated ciphertext is obtained by concatenating the ciphertext of the title and the ciphertext of the payload.

[0098] The concatenated ciphertext is verified sequentially using the valid public key and the aforementioned signature algorithm, following the order of local public key priority from highest to lowest.

[0099] If any valid public key is successfully verified, the token is considered valid; if all valid public keys are invalid, the token is considered invalid.

[0100] In one embodiment, a coin anti-counterfeiting verification method is applied to a cloud server, including:

[0101] Receive the second verification information sent by the coin acceptor, compare the second verification information with the historical data of cloud verification, and obtain the cloud verification result;

[0102] Send the cloud verification result to the coin acceptor.

[0103] In one embodiment, receiving the second verification information sent by the coin acceptor includes: receiving user information associated with the coin acceptor and ID information corresponding to each coin.

[0104] In one embodiment, comparing the second verification information with historical data from cloud verification to obtain the cloud verification result includes:

[0105] Determine whether the ID information is pre-stored in the cloud database; if not, return a cloud verification result indicating that the coin is fake.

[0106] Determine whether the ID information is disabled; if so, return a cloud verification result indicating that the coin is fake.

[0107] Determine whether the ID information is associated with the user information. If not, return a cloud verification result indicating that the coin is fake.

[0108] Based on the ID information, determine whether the coin has been reused within a predetermined time threshold. If so, return a cloud verification result indicating that the coin is fake.

[0109] In one embodiment, the method further includes: obtaining the coin's value information and returning the coin's value information to the coin acceptor.

[0110] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0111] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0112] The above description is merely a preferred embodiment of the present invention. The scope of protection of the present invention is not limited to the above embodiments. All technical solutions falling within the scope of the present invention's concept are within the scope of protection of the present invention. It should be noted that for those skilled in the art, any improvements and modifications made without departing from the principles of the present invention should also be considered within the scope of protection of the present invention.

Claims

1. A method for verifying the anti-counterfeiting features of coins, characterized in that, Applied to coin acceptors, including: Retrieve the first verification information stored within the coin; The coin is locally verified based on the first verification information stored within it, and the local verification result is obtained. If the local verification result is true, retrieve the second verification information stored in the coin and send the second verification information to the cloud server to perform cloud verification on the coin; Receive the cloud verification result returned by the cloud server; if the cloud verification result is true, complete the coin insertion according to the coin's value; The step of obtaining the first verification information stored in the coin includes: obtaining the token value stored in the coin; The step of performing local verification on the coin based on the first verification information stored within the coin to obtain a local verification result includes: Obtain the username and password logged in to the coin acceptor, verify the username, password and token value, and determine whether the token value is valid. If valid, return the local verification result that the coin is real; if invalid, return the local verification result that the coin is fake. Specifically, to maintain network connectivity and distinguish different coin acceptors, a user account needs to be set up within the coin acceptor to ensure it remains connected to the cloud server. A token is a string generated by the server that serves as a token for client requests. Upon first login, the server generates a token and returns it to the client. Subsequent requests only require this new token, eliminating the need for a username and password. This method effectively reduces the computational load on the server for encryption verification. Token validity is time-limited. After a user purchases coins, the cloud server refreshes the token and checks within a predetermined time to determine if the corresponding coins have been used. Coins exceeding this time limit require manual processing by staff.

2. The coin anti-counterfeiting verification method according to claim 1, characterized in that, The verification of the username, password, and token value, and the determination of whether the token value is valid, includes: Check if the token has expired; if it has expired, then the token value is deemed invalid. Determine if the token has been tampered with; if it has been tampered with, then the token value is deemed invalid. Determine if the token is associated with a user. If it is not associated with a user, then the token value is considered invalid.

3. The coin anti-counterfeiting verification method according to claim 2, characterized in that, The determination of whether the token value is valid also includes: Decompose the token into a header ciphertext, a payload ciphertext, and a signature ciphertext; Decrypt the ciphertext of the title using a preset decryption algorithm to obtain the token type and signature algorithm; The concatenated ciphertext is obtained by concatenating the ciphertext of the title and the ciphertext of the payload. The concatenated ciphertext is verified sequentially using the valid public key and the aforementioned signature algorithm, following the order of local public key priority from highest to lowest. If any valid public key is successfully verified, the token is considered valid; if all valid public keys are invalid, the token is considered invalid.

4. A method for verifying the anti-counterfeiting features of coins, characterized in that, Applications to cloud servers include: Receive the second verification information sent by the coin acceptor, compare the second verification information with the historical data of cloud verification, and obtain the cloud verification result; Send the cloud verification result to the coin acceptor; The second verification information received from the coin acceptor includes: user information associated with the coin acceptor and ID information corresponding to each coin. The step of comparing the second verification information with historical data from cloud verification to obtain the cloud verification result includes: Determine whether the ID information is pre-stored in the cloud database; if not, return a cloud verification result indicating that the coin is fake. Determine whether the ID information is disabled; if so, return a cloud verification result indicating that the coin is fake. Determine whether the ID information is associated with the user information. If not, return a cloud verification result indicating that the coin is fake. Based on the ID information, determine whether the coin has been reused within a predetermined time threshold. If so, return a cloud verification result indicating that the coin is fake.

5. The coin anti-counterfeiting verification method according to claim 4, characterized in that, Also includes: Obtain the coin's value information and return it to the coin acceptor.

6. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

Images