Card processing method and device based on block chain and electronic equipment

Abstract

The invention discloses a card processing method and device based on a block chain and electronic equipment. Relates to the technical field of information, and comprises the following steps: receiving a use record for a target card, the target card being an unnamed card which is not pre-bound with corresponding card holding account information; based on a corresponding relationship between the card identifier and the account identifier, determining a target account identifier corresponding to the target card, the target account identifier being an identity identifier pre-registered by the card holding account on the block chain; and based on the target account identifier, sending use prompt information for the use record to the card holding account. According to the invention, the technical problems of loss of the anonymous card and difficulty in use and tracing in the prior art are solved.

Description

Technical Field

[0001] The present invention relates to the field of information technology, and in particular to a card processing method, device and electronic device based on blockchain. Background Art

[0002] People often use anonymous cards (such as stored-value cards) in their daily lives, for shopping, taking public transportation, getting a haircut, etc. Anonymous cards are flexible to use, can be given to others, are easy to carry, and can be used to purchase goods at designated merchants; anonymous cards have different denominations, making it convenient for companies to give employees benefits of different amounts; however, because anonymous cards have no password settings and do not contain the cardholder's information, they are difficult to retrieve once lost.

[0003] With respect to the problems of loss and difficulty in tracing the use of anonymous cards in the above-mentioned related technologies, no effective solution has been proposed so far. Summary of the invention

[0004] The embodiments of the present invention provide a card processing method, device and electronic device based on blockchain, so as to at least solve the technical problems of loss of bearer cards and difficulty in tracing their use existing in the related art.

[0005] According to one aspect of an embodiment of the present invention, a card processing method based on blockchain is provided, comprising: receiving a usage record for a target card, wherein the target card is an anonymous card that is not pre-bound with corresponding cardholder account information; determining a target account identifier corresponding to the target card based on a correspondence between a card identifier and an account identifier, wherein the target account identifier is an identity identifier pre-registered by the cardholder account on the blockchain; and sending usage prompt information for the usage record to the cardholder account based on the target account identifier.

[0006] According to another aspect of an embodiment of the present invention, a card processing device based on blockchain is also provided, including: a record acquisition module, used to receive a usage record for a target card, wherein the target card is an anonymous card that is not pre-bound with corresponding cardholder account information; an identification determination module, used to determine a target account identification corresponding to the target card based on a correspondence between a card identification and an account identification, wherein the target account identification is an identity identification pre-registered by the cardholder account on the blockchain; and a prompt generation module, used to send usage prompt information for the usage record to the cardholder account based on the target account identification.

[0007] According to another aspect of an embodiment of the present invention, a non-volatile storage medium is further provided, wherein the non-volatile storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing any one of the blockchain-based card processing methods.

[0008] According to another aspect of an embodiment of the present invention, there is also provided an electronic device, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any one of the blockchain-based card processing methods.

[0009] In an embodiment of the present invention, by receiving a usage record for a target card, wherein the target card is a bearer card that is not pre-bound with corresponding cardholder account information; based on the correspondence between the card identifier and the account identifier, determining the target account identifier corresponding to the target card, wherein the target account identifier is the identity identifier pre-registered by the cardholder account on the blockchain; based on the target account identifier, sending usage prompt information for the usage record to the cardholder account, thereby achieving the purpose of tracing the card usage record through the account identifier by pre-binding the correspondence between the card identifier and the account identifier registered on the blockchain, thereby achieving the technical effect of tracing the loss and use of bearer cards even without binding user information, thereby solving the technical problem of the loss and use of bearer cards in the related art. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0011] Figure 1 is a flowchart of a card processing method based on blockchain according to an embodiment of the present invention;

[0012] Figure 2 is an optional blockchain-based card processing interaction diagram according to an embodiment of the present invention;

[0013] Figure 3 is a schematic diagram of a blockchain-based card processing device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0014] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0015] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0016] According to an embodiment of the present invention, a method embodiment of blockchain-based card processing is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in an order different from that shown here.

[0017] Figure 1 is a flowchart of a card processing method based on blockchain according to an embodiment of the present invention, such as Figure 1 As shown, the method comprises the following steps:

[0018] Step S102, receiving a usage record for a target card, wherein the target card is an anonymous card that is not pre-bound with corresponding card account information;

[0019] Optionally, the execution subject of this embodiment can be a system, which can be a service end (i.e., a merchant end) or a platform end. The target card is an anonymous card. When the anonymous card is used, the system (such as a service end or a platform end) receives the card usage record, including transaction amount, time, location, and other information. This information is crucial for subsequent card management operations. The system can receive the card usage information in real time or quickly, which provides a basis for real-time monitoring of card usage and subsequent account security operations. In the above manner, users can receive timely notifications of card usage records, including consumption amount and transaction time and location. This helps users manage their card usage in real time and discover any possible fraud in a timely manner. And because the card itself is not bound to specific account information, it is more flexible and convenient when transferred or circulated, which is very beneficial to the popularization and use of anonymous cards.

[0020] Step S104, based on the correspondence between the card identifier and the account identifier, determining the target account identifier corresponding to the target card, wherein the target account identifier is an identity identifier pre-registered on the blockchain by the cardholder account;

[0021] Optionally, after each use record for the target card is received, the blockchain account identifier (target account identifier) ​​corresponding to the card identifier is searched to confirm whether the transaction is associated with a compliant cardholder account. This step plays a key role in preventing unauthorized use and abnormal behavior. Bearer cards do not contain the cardholder's personal account information, but on the blockchain, each card is bound to a pre-registered blockchain account identifier. This binding allows the card to be used anonymously while still being recognized and associated with a specific account by the system. The account identifier on the blockchain is retrieved through the card identifier, and the transaction record is further processed, such as updating the account balance, recording the transaction history, etc. This is the basis for card transaction data processing and account management. In the above manner, even if the card is lost, due to the binding between the card identifier and the blockchain account identifier, the card issuer or platform can quickly locate the real holder of the card, so that when an abnormal transaction is detected, immediate measures can be taken, such as freezing the card, to prevent further losses. In addition, the above method can ensure that all card usage records are accurately associated with the blockchain account, which can provide cardholders with a clear transaction history and enhance the transparency of the processing process. Although the card is bound to the account, all user information is stored in the encrypted environment of the blockchain and is not disclosed to the public, which can protect the privacy of users. By matching each transaction with the blockchain account ID, the system can provide personalized services such as bill query and consumption analysis, providing users with more comprehensive card management services.

[0022] In summary, determining the target account ID based on the correspondence between the card ID and the account ID is the key bridge connecting the bearer card and the blockchain account. It can effectively achieve a balance between the anonymity of card use and the security of account management, and can provide users with a flexible and secure card use environment.

[0023] In an optional embodiment, before determining the target account identifier corresponding to the target card based on the correspondence between the card identifier and the account identifier, the method also includes: receiving a card issuance application for the target card from the target account; based on the card issuance application, detecting whether the target account has the card holding authority; if it is detected that the target account has the card holding authority, using the target account as a card holding account, and binding the card holding account to the target account identifier.

[0024] Optionally, the card issuer reviews the user's card issuance application and needs to review whether the user has the card holding authority. If the review is passed, the application is approved, otherwise the application is rejected. By detecting whether the target account has the card holding authority, it is ensured that only verified users can obtain the card, thereby enhancing the control of card issuance and preventing unauthorized card issuance. The target account is used as a card holding account and bound to the target account identifier, which can provide a clear account attribution for the subsequent use of the card and ensure that each transaction of the card can be traced back to the specific cardholder. Through the above permission detection and account binding process, the safe issuance of the card can be ensured and the risk of malicious or unauthorized use of the card can be reduced. Once the card is bound to the account identifier, the subsequent card usage records can be automatically associated with the account, which can simplify the additional verification process required when the user uses the card. The user can also query and manage the usage of all cards bound to it through his own account identifier, including balance, transaction records, etc., making card management more convenient. The above methods can not only improve security, but also simplify the process of card use and management, optimize the user experience as a whole, and increase the user's trust in the card system and willingness to use.

[0025] In an optional embodiment, the blockchain also pre-stores the card issuing end information of the target card, the service end information of the target card, and the card information of the target card.

[0026] Optionally, by storing the card issuer, server, and card information, it is possible to ensure that important data throughout the card life cycle is recorded on the blockchain, providing comprehensive data support for subsequent card management, transaction verification, and traceability. The card issuer information and server information help the system to verify permissions, ensuring that only compliant card issuers and servers can upload and process card data, thereby enhancing the security of the card usage process. The storage of card information (including card number, balance, expiration date, etc.) on the blockchain provides a basis for the verification of each transaction and ensures the accuracy of the transaction. By pre-storing this information, the system can establish an association between the card, the card issuer, and the server, making data query and processing more efficient.

[0027] In the above method, by storing all card-related data, the security of the transaction can be ensured. Even if the card is lost or the data is tampered with, the information on the issuing end and the service end can help the system verify the authenticity and compliance of the transaction. The open and transparent nature of the blockchain makes the card issuance, use, service and other information visible to all network participants, improving the overall transparency of the card usage process. Pre-stored card information helps to simplify the card management process, such as card rebinding, freezing, unfreezing and other operations, which can directly access and update this information without additional query or verification.

[0028] Optionally, before the bearer card is issued to the corresponding cardholder, in addition to the blockchain identity registration, the card issuer and the merchant (i.e., the service end) are required to register and submit their identity information on the blockchain; the card issuer determines the unique identifier (i.e., card ID) of each card, such as the card number or serial number, and other related information. The card information is packaged into a data packet, which should contain the card's unique identifier (such as the card number or serial number) and other related information, and the card information is uploaded to the blockchain. The card issuer uses the interface provided by the platform end to send the card information to the blockchain node. After the upload is successful, the card information will be written into the blockchain ledger and become an unalterable public record.

[0029] Step S106: Based on the target account identifier, a usage reminder message for the usage record is sent to the cardholder account.

[0030] Optionally, by sending usage reminder information, the cardholder can be notified immediately about the card usage, including key information such as transaction amount, transaction time, and transaction location. This allows the cardholder to monitor card activities in real time. If the cardholder finds that the transaction record in the reminder information is inconsistent with his or her consumption behavior, he or she can take quick action, such as contacting the card issuer or freezing the card to prevent further unauthorized transactions. By providing instant feedback on card usage, users' participation in card management can be increased, allowing users to manage their cards and accounts more proactively, and enhancing user interaction with the system.

[0031] In an optional embodiment, the method further includes: storing the usage record and the target account identifier in a corresponding manner in the blockchain.

[0032] Optionally, the usage records and target account identifiers are stored on the blockchain, which means that these data will be permanently stored and cannot be tampered with or deleted, and can provide an unalterable evidence for transaction records. By storing the usage records in correspondence with the target account identifier, it can be ensured that each transaction can be accurately corresponded to the cardholder's account, and even if the card itself does not contain account information, the source of the transaction can be traced. It should be noted that due to the decentralization and immutability of the blockchain, the data stored on the blockchain is safer, which can effectively prevent the data from being maliciously tampered with and reduce the security risks in the use of cards. The corresponding storage of usage records and account identifiers allows any transaction to be traced, which can improve the transparency of the system, help resolve transaction disputes, and protect consumer rights. The transaction information stored on the blockchain can facilitate the card issuer or system to update and manage the card status in real time, such as updating the card balance and transaction records, and improve the efficiency of card management. Through the technical characteristics of the blockchain, the integrity and accuracy of all transaction data are ensured, providing cardholders with a reliable card usage record. In summary, by storing usage records and the associated target account identifiers on the blockchain, not only can the security and transparency of transactions be enhanced, but the card management process can also be optimized, and the overall credibility and user satisfaction of the card during use can be improved.

[0033] Optionally, when a user uses a card (such as swiping a card for consumption), the merchant needs to generate a consumption record for each card. Before the merchant uploads the card consumption information to the blockchain for the first time, it needs to authenticate and authorize. The merchant packages the consumption records and uploads the data to the blockchain node through the interface provided by the platform. When the merchant uploads the consumption data (i.e., the usage record), it triggers the client consumption reminder to remind the user to check the consumption details. If the user finds that the current consumption is not generated by himself and his card cannot be found, then he can take corresponding measures in time, such as immediately reporting the card lost (which can be achieved by monitoring the blockchain data).

[0034] Optionally, during the interaction between the card issuer, the merchant (i.e., the service end), and the user (i.e., the card account) and the blockchain, identity authentication is required. Specifically, the card issuer needs to perform identity authentication and authorization when uploading data to the blockchain. If the identity authentication is successful, the data can be uploaded. Otherwise, the data upload request is rejected. The merchant needs to perform identity authentication and authorization when uploading data to the blockchain. If the identity authentication is successful, the data can be uploaded. Otherwise, the data upload request is rejected. When the user queries the card information, identity authentication and authorization are required. If the identity authentication is successful, the information of the card bound to the user on the blockchain can be viewed. Otherwise, the viewing request is rejected.

[0035] Optionally, the uploaded data needs to be further verified for validity. Specifically, determine whether the card information uploaded by the card issuer meets the specifications, such as the basic information of the card, and whether the blockchain data identity association between the card and the user is correct). If the data on the card issuer meets the requirements, upload the data to the blockchain. If it does not meet the requirements, the upload request is rejected. Determine whether the consumption data uploaded by the merchant meets the specifications, such as whether some required items are missing. If the data verification passes, upload it to the blockchain, otherwise the upload request is rejected. Check whether the user registration information is correct. If the registration information is correct, allow the user to register. If not, prompt the user to enter the correct registration information.

[0036] In an optional embodiment, the method also includes: receiving a freezing request for a target card, wherein the freezing request carries a target account identifier corresponding to the cardholder account; based on the account identifier corresponding to the freezing request, detecting whether there is freezing authority for the target card; and freezing the target card if it is detected that there is freezing authority.

[0037] Optionally, by receiving a freeze request for a target card, an immediate response measure can be provided for the cardholder when the card is lost or suspicious activities are discovered. Before processing the freeze request, the cardholder will be checked based on the account identifier carried in the request to see if he has the freeze permission for the target card, thereby ensuring the rigor of permission management. Once it is confirmed that the cardholder has the freeze permission, the target card can be quickly frozen to prevent further use and protect the cardholder's account security. The introduction of the card freeze function can significantly enhance the security of bearer cards. Even if the card is lost or stolen, the cardholder can take timely action to avoid property loss. The cardholder can actively control the card's usage status, including freezing and unfreezing the card, through the client or other methods provided by the system, thereby enhancing the user's control over the card. This process allows the system to respond quickly after receiving a card freeze request, and the card freezing operation can be completed without manual intervention, thereby improving the response speed and efficiency. Users can quickly protect their accounts through simple operations (such as sending a freeze request). This convenience and efficiency help improve user experience.

[0038] Optionally, after the user submits a freezing application (i.e., a report loss application), the corresponding user blockchain identity information is found through the identity information provided by the user, and the card information bound to the user is found through the blockchain identity information. The report loss application can be further reviewed, and if the review is passed, the target card can be frozen by the card issuer or the platform.

[0039] In an optional embodiment, the method also includes: receiving a rebinding request for a target card, wherein the rebinding request carries a target account identifier corresponding to the cardholder account; based on the account identifier corresponding to the rebinding request, detecting whether the rebinding authority for the target card is available; if it is detected that the rebinding authority is available, releasing the binding relationship between the target account identifier and the target card, and establishing a binding relationship between the target account identifier and a new card.

[0040] Optionally, the cardholder is allowed to change the bound card without changing the account identifier on the blockchain, which can maintain the card's transfer attribute and flexibility. Before processing the rebinding request, verify whether the requester has the rebinding authority for the target card to ensure the compliance of the operation. After the authority verification is passed, the binding between the original card and the account can be released, and the binding relationship between the new card and the account can be established to update the card and account status. In the above method, the card rebinding function can increase the convenience of users using cards. Even if the card needs to be replaced, it does not affect the continuity of the user's account and the integrity of the historical transaction records. The security of the card rebinding operation can be ensured through authority verification, prevent unauthorized rebinding requests, and protect the cardholder's account security. The above method can more flexibly adapt to the user's card replacement needs while maintaining control over the card status and account permissions. After the rebinding, the new card can also inherit the historical records and account information of the original card to ensure the continuity and consistency of the transaction records, which is convenient for subsequent query and management. The user can independently control the binding status of the card. For example, when the card is damaged or needs to be re-gifted, the rebinding operation can be performed conveniently and quickly, which improves the user's satisfaction with the card system. In summary, the card rebinding request processing process can increase the flexibility and security of the card processing system, providing users with a more convenient and safer card usage environment. Through this process, users can replace or transfer cards while keeping their blockchain account ID unchanged, without affecting the normal use of the card function and the traceability of its transaction records.

[0041] Optionally, after the user initiates a rebinding request, the card can be frozen through the card issuing end or the platform end, the relationship between the user and the old card can be unbound, and the new card can be rebound for the user, and the relevant information on the blockchain can be updated (the balance, validity period, supported merchants and other information of the new card depend on the on-chain data of the old card, and the balance is equal to the total amount of the old card data minus the amount used, and the validity period and supported merchant information are the same as the old card). The rebinding request applied by the user can be reviewed by the card issuing end or the platform end. After the review is passed, the current account can be unbound and the new account can be rebound, and the relevant information on the blockchain can be updated.

[0042] In an optional embodiment, the method also includes: receiving a query request for card information of a target card; based on an account identifier corresponding to the query request, detecting whether there is query authority for the card information of the target card; and if it is detected that there is query authority, feeding back the query result to the client that sent the query request.

[0043] Optionally, users are allowed to query detailed information of the card through the client, which enhances the user's understanding of the card status. When processing the query request, the query permission can be verified based on the account identifier in the request to ensure that only those users who have access to the card information can query. If the user has the query permission, the query result is fed back to the client that sent the request, making the information acquisition process more efficient and direct. In the above methods, the card information query function can provide users with a convenient way to understand the use of the card at any time and enhance the convenience of card management. Permission verification can ensure the security of card information, prevent unauthorized query requests, and protect the privacy and account security of cardholders. By querying card information through blockchain, due to the open and transparent nature of blockchain, cardholders can be sure of the accuracy and immutability of the query information. Users can query card information regularly, which helps to detect any abnormal transactions in time and take timely measures, such as card freezing, thereby reducing the risk of abnormal transactions.

[0044] In summary, through the above card information query request processing flow, the function of users querying card information is added, and the security and compliance of the query can be guaranteed through permission verification. At the same time, through timely data feedback, user convenience and system transparency can be improved, which can enhance the user experience and the security of the card system as a whole.

[0045] Through the above steps S102 to S108, the correspondence between the card identifier and the blockchain identifier can be pre-bound, and the purpose of tracing the card usage record can be achieved through the account identifier, thereby achieving the technical effect of tracing the loss and use of the bearer card even without binding the user information, thereby solving the technical problem of the loss and use of the bearer card existing in the related technology.

[0046] Based on the above embodiments and alternative embodiments, the present invention proposes an alternative implementation manner of a card processing method based on blockchain. Figure 2 It is an alternative interaction diagram of card processing based on blockchain according to an embodiment of the present invention, as Figure 2 shown, where:

[0047] The client corresponding to the user (i.e., the card - holding account terminal) has the following functions:

[0048] 1) User registration, where the user conducts blockchain identity registration;

[0049] 2) Card application, where the user applies for card issuance;

[0050] 3) Card freezing / unfreezing application. If the user's card is lost, the user can apply for card freezing and further apply for reporting loss and reissuing a card. If the card is found again, the user can apply for unfreezing;

[0051] 4) Card information query, where the user can view the consumption information and balance information of the card through the client;

[0052] 5) Card re - binding application, where the user can apply for re - binding the account through the client to maintain the transfer property of the original anonymous card.

[0053] The system platform terminal has the following functions:

[0054] 1) The card - issuing end and the merchant (i.e., the service end) register on the blockchain and submit their identity information;

[0055] 2) Card - issuing application review. The card - issuing end reviews the user's card - issuing application. It is necessary to review whether the user has the card - holding permission. If the review passes, the application is approved; otherwise, the application is rejected;

[0056] 3) Binding of the card to the blockchain identity. After the card - issuing application passes, before the card - issuing end issues the card, it binds the card to the user's blockchain identity. The identifier of the card is used as an index to be associated with a specific user identity, thereby ensuring the uniqueness and relevance of the card and the user identity.

[0057] 4) Card information upload, specifically including:

[0058] Card information collection. The card - issuing end determines the unique identifier of each card (i.e., the card identifier), such as the card number or serial number, and other relevant information. The card information is packaged into a data packet, and the data packet should contain the unique identifier of the card (such as the card number or serial number) and other relevant information.

[0059] Identity verification of the card - issuing end. Before uploading the card information to the blockchain, the card - issuing end needs to conduct identity verification and authorization.

[0060] The card information is uploaded, and the card issuer uses the interface provided by the platform to send the card information to the blockchain node. After the upload is successful, the card information will be written into the blockchain ledger and become an unalterable public record.

[0061] 5) Upload card spending records, including:

[0062] Generate consumption records. When a user uses a card (such as swiping a card for consumption), the merchant needs to generate a consumption record for each card.

[0063] Merchant identity verification, before merchants upload card consumption information to the blockchain for the first time, they need to perform identity verification and authorization.

[0064] Upload consumption records. Merchants package consumption records and upload data to the blockchain node through the interface provided by the platform.

[0065] 6) Consumption reminders, including:

[0066] When the merchant uploads the consumption data (i.e. usage records), it triggers the client consumption reminder, reminding the user to check the consumption details. If the user finds that the current consumption is not generated by himself and his card cannot be found, he can immediately report the card lost (which can be achieved by monitoring the blockchain data).

[0067] 7) Card loss and retrieval, including:

[0068] If the cardholder finds that the card is lost or forgotten, he / she can apply for a freeze through the client to the card issuer. If the card is confirmed to be lost, he / she can apply for a replacement card.

[0069] The card issuer reviews the report of loss application, finds the corresponding user blockchain identity information through the identity information provided by the user, and finds the card information bound to the user through the blockchain identity information.

[0070] Freeze the card and reissue it. After the report of loss application is approved, the card issuer will freeze the card, unbind the user from the old card, rebind the new card for the user, and update the relevant information on the blockchain (the balance, validity period, supported merchants and other information of the new card depend on the chain data of the old card. The balance is equal to the total amount of the old card data minus the amount used. The validity period and supported merchant information are the same as the old card).

[0071] 8) Rebinding: The card issuer reviews the user's request for rebinding. After the review is passed, the current account will be unbound and the new account will be rebound, and the relevant information on the blockchain will be updated at the same time.

[0072] This method is applied to Figure 2 In the interaction diagram shown, the method includes:

[0073] S1. User registration: When the card is first issued, the user registers the blockchain identity through the client. The user provides some basic information (such as mobile phone number, email, etc.) and completes identity verification to ensure the authenticity and uniqueness of the user.

[0074] S2, card issuer and merchant registration: The card issuer and merchant register on the blockchain and submit their identity information.

[0075] S3. Card application: The user applies for card issuance through the client.

[0076] S4. Card application review: The user submits a card issuance application to the card issuer, and the card issuer reviews the user's authority to confirm whether he or she has the card holding authority.

[0077] S5. Blockchain identity binding: The card issuer binds the card to the user's blockchain identity before issuing the card. This operation is achieved by recording the relationship between the user's identity information and the card identifier in the contract. The card identifier is associated with a specific user identity as an index, thereby ensuring the uniqueness and association between the card and the user identity.

[0078] S6. Card issuance: The card issuing end issues the card after review. Each card has a unique identifier, such as a card number or QR code.

[0079] S7. Blockchain storage: The card's related information is encrypted and recorded in the contract on the blockchain. When the user uses the card, the card's related operations (such as recharge, consumption, balance inquiry, etc.) will be recorded in the contract on the blockchain.

[0080] S8. User Query: Users can access relevant information of the card through their blockchain identity, which ensures the security and immutability of the card information while providing an open and transparent query method.

[0081] S9. Card loss and tracing, including:

[0082] S91. Lost card reissue process: When a user loses a card, they can go through the online reissue application process on the client. The user needs to provide some verification information to confirm that they are the legal holder of the card.

[0083] S9, Blockchain review and unbinding: The card issuer reviews the information provided by the user and verifies it against the blockchain identity. Once the verification is passed, the card is marked as lost and unbound from the user's identity.

[0084] S9. Issuance of new card: The card issuer can issue a new card to the user based on the lost card replacement process, and rebind it to the user's blockchain identity, while updating the data on the blockchain.

[0085] Optionally, during the execution of the method, the following process is also included:

[0086] S11, identity authentication and authorization, including:

[0087] When the card issuer uploads data to the blockchain, it needs to undergo identity authentication and authorization. If the identity authentication is passed, the data can be uploaded. Otherwise, the data upload request will be rejected.

[0088] When merchants upload data to the blockchain, they need to undergo identity authentication and authorization. If the identity authentication is passed, the data can be uploaded. Otherwise, the data upload request will be rejected.

[0089] When users query card information, they need to undergo identity authentication and authorization. If the identity authentication is passed, they can view the information of the card bound to them on the blockchain, otherwise the viewing request will be rejected.

[0090] S12, upload data verification, including:

[0091] Determine whether the card information uploaded by the issuing end meets the specifications, such as the basic information of the card and whether the blockchain data identity association between the card and the user is correct. If the data on the issuing end meets the requirements, upload the data to the blockchain. If it does not meet the requirements, reject the upload request.

[0092] Determine whether the consumption data uploaded by the merchant complies with the specifications, such as whether some required items are missing. If the data verification passes, upload it to the blockchain, otherwise reject the upload request.

[0093] Whether the user registration information is correct, if the registration information is correct, the user is allowed to register, if not, the user is prompted to enter the correct registration information.

[0094] This embodiment can achieve at least one of the following effects: 1) Real-time transaction tracking and restriction: The anonymous card anti-loss system based on blockchain technology can track transaction records in real time and promptly notify users of abnormal or suspicious transactions. When a card is stolen or lost, users can immediately discover and take corresponding measures, such as freezing accounts or changing private keys, to protect the security of assets. 2) Immutability of data stored in blockchain: Transaction records on the blockchain are immutable. Once a transaction is confirmed and written to the blockchain, it cannot be changed or deleted. This provides higher reliability and security for the anti-loss system. Even if the lost anonymous card is obtained by others, its balance and transaction records can still be tracked and monitored, reducing the risk of asset abuse. 3) Quick report loss and recovery: The anonymous card anti-loss system based on blockchain technology can realize quick report loss and recovery functions. Users can quickly report loss operations through private keys or specific identity authentication methods to ensure the safety of assets. At the same time, when users find that the card is not really lost, they can easily restore the right to use the card, reducing the inconvenience caused by the report loss operation.

[0095] It should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. For example, an interface is set up between this system and the relevant user or organization. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or organization.

[0096] In this embodiment, a card processing device based on blockchain is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the terms "module" and "device" can implement a combination of software and / or hardware for a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0097] According to an embodiment of the present invention, there is also provided an apparatus embodiment for implementing the above-mentioned blockchain-based card processing method. Figure 3 is a schematic diagram of the structure of a card processing device based on blockchain according to an embodiment of the present invention, such as Figure 3 As shown, the card processing device based on blockchain includes: a record acquisition module 200, an identification determination module 202, and a prompt generation module 204, wherein:

[0098] The record acquisition module 200 is used to receive the usage record for the target card, wherein the target card is an anonymous card that is not pre-bound with the corresponding card account information;

[0099] The identification determination module 202 is connected to the record acquisition module 200 and is used to determine the target account identification corresponding to the target card based on the correspondence between the card identification and the account identification, wherein the target account identification is the identity identification pre-registered on the blockchain by the card holder account;

[0100] The prompt generating module 204 is connected to the identification determining module 202, and is used to send usage prompt information for the usage record to the card-holding account based on the target account identification.

[0101] In an embodiment of the present invention, a record acquisition module 200 is provided to receive usage records for a target card, wherein the target card is an anonymous card that is not pre-bound with corresponding cardholder account information; an identification determination module 202 is connected to the record acquisition module 200, and is used to determine the target account identification corresponding to the target card based on the correspondence between the card identification and the account identification, wherein the target account identification is an identity identification pre-registered on the blockchain by the cardholder account; a prompt generation module 204 is connected to the identification determination module 202, and is used to send usage prompt information for the usage record to the cardholder account based on the target account identification, thereby achieving the purpose of pre-binding the correspondence between the card identification and the blockchain identification, and tracing the card usage record through the account identification, thereby achieving the technical effect of tracing the loss and use of anonymous cards even without binding user information, thereby solving the technical problem of the loss and use of anonymous cards in the related art.

[0102] It should be noted that the above modules can be implemented by software or hardware. For example, for the latter, it can be implemented in the following ways: the above modules can be located in the same processor; or the above modules can be located in different processors in any combination.

[0103] It should be noted that the above-mentioned record acquisition module 200, identification determination module 202, and prompt generation module 204 correspond to steps S102 to S106 in the embodiment, and the examples and application scenarios implemented by the above-mentioned modules and the corresponding steps are the same, but are not limited to the contents disclosed in the above-mentioned embodiment. It should be noted that the above-mentioned modules can be run in a computer terminal as part of the device.

[0104] It should be noted that the optional or preferred implementation of this embodiment can refer to the relevant description in the embodiment, which will not be repeated here.

[0105] The above-mentioned blockchain-based card processing device may also include a processor and a memory. The above-mentioned record acquisition module 200, identification determination module 202, prompt generation module 204, etc. are all stored in the memory as program modules, and the processor executes the above-mentioned program modules stored in the memory to realize corresponding functions.

[0106] The processor includes a kernel, which retrieves the corresponding program module from the memory. The kernel may be one or more. The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. The memory includes at least one memory chip.

[0107] According to an embodiment of the present application, an embodiment of a non-volatile storage medium is also provided. Optionally, in this embodiment, the non-volatile storage medium includes a stored program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute any of the above-mentioned blockchain-based card processing methods.

[0108] Optionally, in this embodiment, the non-volatile storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group, and the non-volatile storage medium includes a stored program.

[0109] Optionally, when the program is running, the device where the non-volatile storage medium is located is controlled to perform the following functions: receiving a usage record for a target card, wherein the target card is an anonymous card that is not pre-bound with corresponding cardholder account information; determining a target account identifier corresponding to the target card based on a correspondence between a card identifier and an account identifier, wherein the target account identifier is an identity identifier pre-registered by the cardholder account on the blockchain; and sending usage prompt information for the usage record to the cardholder account based on the target account identifier.

[0110] According to an embodiment of the present application, an embodiment of a processor is also provided. Optionally, in this embodiment, the processor is used to run a program, wherein when the program is run, any of the above-mentioned card processing methods based on blockchain is executed.

[0111] According to an embodiment of the present application, an embodiment of a computer program product is also provided. Optionally, in this embodiment, the computer program product includes a computer program, and when the computer program is executed by a processor, the computer program implements any one of the steps of the blockchain-based card processing method.

[0112] Optionally, the above-mentioned computer program product, when executed on a data processing device, is suitable for executing a program that initializes the following method steps: receiving a usage record for a target card, wherein the target card is an anonymous card that is not pre-bound with corresponding cardholder account information; determining a target account identifier corresponding to the target card based on a correspondence between a card identifier and an account identifier, wherein the target account identifier is an identity identifier pre-registered by the cardholder account on the blockchain; and sending usage prompt information for the usage record to the cardholder account based on the target account identifier.

[0113] An embodiment of the present invention provides an electronic device, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, the following steps are implemented: receiving a usage record for a target card, wherein the target card is an unnamed card that is not pre-bound with corresponding cardholder account information; determining a target account identifier corresponding to the target card based on a correspondence between a card identifier and an account identifier, wherein the target account identifier is an identity identifier pre-registered by the cardholder account on a blockchain; and sending usage prompt information for the usage record to the cardholder account based on the target account identifier.

[0114] The above sequence of the embodiments of the present invention is for description only and does not represent the superiority or inferiority of the embodiments.

[0115] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0116] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the above modules can be a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, modules or indirect coupling or communication connection of modules, which can be electrical or other forms.

[0117] The modules described above as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment.

[0118] In addition, each functional module in each embodiment of the present invention may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module. The above integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0119] If the above-mentioned integrated module is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable non-volatile storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a non-volatile storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the various embodiments of the present invention. The aforementioned non-volatile storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0120] The above are only preferred embodiments of the present invention. It should be pointed out that, for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A card processing method based on blockchain, characterized in that: include: receiving a usage record for a target card, wherein the target card is an anonymous card that is not pre-bound with corresponding cardholder account information; Based on the correspondence between the card identifier and the account identifier, determine the target account identifier corresponding to the target card, wherein the target account identifier is the identity identifier of the cardholder account pre-registered on the blockchain; Based on the target account identifier, usage prompt information for the usage record is sent to the card holding account.

2. The method according to claim 1, characterized in that The method further comprises: The usage record and the target account identifier are stored in the blockchain accordingly.

3. The method according to claim 1, characterized in that Before determining the target account identifier corresponding to the target card based on the correspondence between the card identifier and the account identifier, the method further includes: Receiving a card issuance application for the target card from a target account; Based on the card issuance application, detecting whether the target account has card holding authority; When it is detected that the target account has the card holding authority, the target account is used as the card holding account, and the card holding account is bound to the target account identifier.

4. The method according to claim 1, characterized in that: The method further comprises: receiving a freezing request for the target card, wherein the freezing request carries the target account identifier corresponding to the cardholder account; Based on the account identifier corresponding to the freezing request, detecting whether the freezing authority for the target card is available; When it is detected that the user has the freezing authority, the target card is frozen.

5. The method according to claim 1, characterized in that The method further comprises: A request for rebinding of the target card is received, wherein the request for rebinding carries the target account identifier corresponding to the cardholder account; Based on the account identifier corresponding to the rebinding request, detecting whether the rebinding permission for the target card is available; When it is detected that the user has the authority to change the binding, the binding relationship between the target account identifier and the target card is released, and a binding relationship between the target account identifier and the new card is established.

6. The method according to claim 1, characterized in that The method further comprises: Receiving a query request for card information of the target card; Based on the account identifier corresponding to the query request, detecting whether the user has the authority to query the card information of the target card; When it is detected that the query permission is possessed, the query result is fed back to the client that sent the query request.

7. The method according to any one of claims 1 to 6, characterized in that: The blockchain also pre-stores the card issuing end information of the target card, the service end information of the target card and the card information of the target card.

8. A card processing device based on blockchain, characterized in that: include: A record acquisition module, used to receive a usage record for a target card, wherein the target card is an anonymous card that is not pre-bound with corresponding card account information; An identification determination module, used to determine the target account identification corresponding to the target card based on the correspondence between the card identification and the account identification, wherein the target account identification is the identity identification pre-registered by the cardholder account on the blockchain; A prompt generating module is used to send usage prompt information for the usage record to the card holding account based on the target account identifier.

9. A non-volatile storage medium, characterized in that: The non-volatile storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the blockchain-based card processing method described in any one of claims 1 to 7.

10. An electronic device, characterized in that: The invention comprises one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the blockchain-based card processing method according to any one of claims 1 to 7.

Images