Accepting terminal and method for processing digital currency hard wallet transaction

Abstract

A kind of processing digital currency hard wallet transaction receiving terminal, method, electronic equipment and readable medium, the receiving terminal includes: communication ware, is configured to communicate with digital currency hard wallet;Memory is configured to at least store the transaction data of last time and the transaction of digital currency hard wallet with interruption and set type information change record;And at least one processor is configured to: control communication ware receives the transaction request initiated by digital currency hard wallet via wireless communication connection;Based on transaction request, the transaction data of last time interruption and set type information change record to identify the identity of digital currency hard wallet;In response to the identity identification result of digital currency hard wallet, select to execute the change operation of set type information of digital currency hard wallet and / or execute transaction operation.The terminal can solve the transaction interruption problem of digital currency hard wallet transaction.

Description

Technical Field

[0001] Embodiments of this disclosure relate to acceptance terminals, methods, electronic devices, and readable media for processing digital currency hard wallet transactions. Background Technology

[0002] Currently, when using digital currency hard wallets for contactless payments on industry terminals such as rail transit systems, the phenomenon of "flash cards" occasionally occurs. The current acceptance terminals cannot handle this situation well and complete the transaction between the two parties. Summary of the Invention

[0003] At least one embodiment of this disclosure provides a terminal for processing transactions in a digital currency hard wallet. The terminal includes: a communicator configured to communicate with a digital currency hard wallet; a memory configured to store at least the transaction data of the most recent transaction interrupted by the digital currency hard wallet and a record of changes to setting type information; and at least one processor configured to: control the communicator to receive a transaction request initiated by the digital currency hard wallet via a wireless communication connection; identify the identity of the digital currency hard wallet initiating the transaction request based on the transaction request, the transaction data of the most recent transaction interruption, and the record of changes to setting type information; and, in response to the identification result of the digital currency hard wallet initiating the transaction request, select to perform an operation to change the setting type information of the digital currency hard wallet and / or perform a transaction operation.

[0004] For example, in a receiving terminal according to at least one embodiment of the present disclosure, at least one processor is configured to generate first authentication information according to a shared key corresponding to set type information, control a communicator to send the first authentication information to a digital currency hard wallet to enable it to perform authentication, and control the communicator to receive second authentication information generated according to a shared key corresponding to set type information sent by the digital currency hard wallet, and perform authentication based on the received second authentication information and the generated first authentication information.

[0005] For example, in a receiving terminal according to at least one embodiment of the present disclosure, at least one processor is configured to compare the account identifier of a transaction request with the account identifier of the transaction data of the most recent transaction interruption to determine whether it is a digital currency hard wallet of the most recent transaction interruption; and to determine whether the digital currency hard wallet is a specific account based on the set type information change record.

[0006] For example, in a receiving terminal according to at least one embodiment of the present disclosure, at least one processor is configured to compare the account identifier of the transaction request with the account identifier of the transaction data of the most recent transaction interruption to determine whether it is a specific account.

[0007] For example, in a receiving terminal according to at least one embodiment of the present disclosure, at least one processor is configured to: upon identifying a specific user, not rewrite the setting type information of the digital currency hard wallet that initiated the transaction request, re-obtain payment information from the digital currency hard wallet and execute the transaction operation; upon identifying a non-specific user, perform a change operation on the setting type information of the digital currency hard wallet that initiated the transaction request and execute the transaction operation.

[0008] For example, in a receiving terminal according to at least one embodiment of the present disclosure, the setting type information includes industry scenario information, which represents scenario data corresponding to the industry field associated with the receiving terminal.

[0009] For example, according to at least one embodiment of the present disclosure, the acceptance terminal is a passage gate of a rail transit system, and the industry scenario information includes data related to the entry and exit scenarios.

[0010] At least one embodiment of this disclosure provides a method for processing transactions in a digital currency hard wallet. The method includes: receiving a transaction request initiated by the digital currency hard wallet; identifying the identity of the digital currency hard wallet that initiated the transaction request based on the transaction request, transaction data from the most recent transaction interruption, and a record of changes to setting type information; and, in response to the identification result of the digital currency hard wallet that initiated the transaction request, selecting to perform a change operation on the setting type information of the digital currency hard wallet and / or perform a transaction operation.

[0011] For example, according to at least one embodiment of the method of this disclosure, the method further includes: generating first authentication information according to a shared key corresponding to set type information; sending the first authentication information to the digital currency hard wallet to enable it to perform authentication; and receiving second authentication information generated according to the shared key corresponding to set type information sent by the digital currency hard wallet, and performing authentication based on the received second authentication information and the generated first authentication information.

[0012] For example, according to at least one embodiment of the method of this disclosure, the step of identifying the identity of a digital currency hard wallet includes: comparing the account identifier of a transaction request with the account identifier of the transaction data of the most recent transaction interruption to determine whether it is a digital currency hard wallet of the most recent transaction interruption; and determining whether the digital currency hard wallet is a specific account based on the set type information change record.

[0013] For example, according to at least one embodiment of the method of this disclosure, after being identified as a specific user, the setting type information of the digital currency hard wallet that initiated the transaction request is not rewritten, and the payment information is re-obtained from the digital currency hard wallet and the transaction operation is executed; after being identified as a non-specific user, the setting type information of the digital currency hard wallet that initiated the payment transaction request is changed and the transaction operation is executed.

[0014] For example, according to at least one embodiment of the method of this disclosure, the set type information includes industry scenario information, which represents scenario data corresponding to the industry field associated with the acceptance terminal.

[0015] For example, according to at least one embodiment of the method of this disclosure, the receiving terminal is a passage gate of a rail transit system, and the industry scenario information includes data related to the entry and exit scenarios.

[0016] At least one embodiment of this disclosure provides an electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement the method of processing a digital currency hard wallet as described in the above embodiments.

[0017] At least one embodiment of this disclosure provides a computer-readable medium having a computer program stored thereon, characterized in that, when the program is executed by a processor, it implements the method for processing a digital currency hard wallet as described in the above embodiments.

[0018] The solution for processing digital currency hard wallet transactions in this disclosure can effectively solve the problem of transaction failure caused by transaction interruption during hard wallet transactions, and improve the transaction success rate. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings of the embodiments of this disclosure will be briefly described below. Clearly, the drawings described below only relate to some embodiments of this disclosure and are not intended to limit the scope of this disclosure.

[0020] Figure 1 It is a view used to describe the "flash card" situation that occurs in a digital currency hardware wallet during a transaction;

[0021] Figure 2 A block diagram of an acceptance terminal for processing digital currency hard wallet transactions according to at least one embodiment of the present disclosure is shown;

[0022] Figure 3 A flowchart is shown illustrating a method for processing digital currency hard wallet transactions according to at least one embodiment of the present disclosure;

[0023] Figure 4 An exemplary operation flowchart is shown for handling the flash card situation of a digital currency hard wallet in a rail transit station entry scenario according to at least one embodiment of the present disclosure;

[0024] Figure 5 An exemplary operation flowchart is shown in the case of a digital currency hard wallet experiencing a flash card situation in a rail transit exit scenario according to at least one embodiment of the present disclosure;

[0025] Figure 6 A schematic diagram of an electronic device according to at least one embodiment of the present disclosure is shown;

[0026] Figure 7 A schematic diagram of a non-transiently readable storage medium according to at least one embodiment of the present disclosure is shown. Detailed Implementation

[0027] Reference will now be made in detail to specific embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. Although the present disclosure will be described in conjunction with specific embodiments, it will be understood that it is not intended to limit the present disclosure to the described embodiments. Rather, it is intended to cover variations, modifications, and equivalents included within the spirit and scope of the present disclosure as defined by the appended claims. It should be noted that the method operations described herein can be implemented by any functional block or functional arrangement, and any functional block or functional arrangement can be implemented as a physical entity or a logical entity, or a combination of both.

[0028] To enable those skilled in the art to better understand this disclosure, the disclosure will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0029] Note that the examples described below are merely specific examples and are not intended to limit the embodiments of this disclosure to the specific shapes, hardware, connections, operations, values, conditions, data, sequences, etc., shown and described. Those skilled in the art can utilize the concepts of this disclosure to construct further embodiments not mentioned herein by reading this specification.

[0030] The terminology used in this disclosure is that which is currently widely used in the art in consideration of the functionality of this disclosure; however, these terms may vary depending on the intent, precedent, or new technology of those skilled in the art. Furthermore, specific terms may be chosen by the applicant, and in such cases, their detailed meanings will be described in the detailed description of this disclosure. Therefore, the terminology used in this specification should not be construed as simple names, but rather based on the meaning of the terms and the overall description of this disclosure.

[0031] This disclosure uses flowcharts to illustrate the operations performed by a system according to embodiments of this disclosure. It should be understood that the preceding or following operations are not necessarily performed in exact order. Instead, various steps can be processed in reverse order or simultaneously, as needed. Furthermore, other operations can be added to these processes, or one or more steps can be removed from them.

[0032] To better understand the embodiments of this disclosure, the relevant terms involved in this disclosure will first be defined and explained.

[0033] Digital currency: Digital currency can be purchased using conventional forms of currency (e.g., fiat currency) and generated at a specific value. Typically, digital currency may not have a physical form of currency, but can be accessed through a user's computing device (e.g., a mobile device) using software applications such as digital wallets or mobile apps.

[0034] Secure Element (SE): Usually provided in the form of a chip, also known as a security chip, it is equivalent to a microcomputer and can realize functions such as secure data storage and encryption / decryption operations.

[0035] Digital wallets are the carriers of digital currency and the medium through which it reaches users. They are categorized into software wallets and hardware wallets based on their carrier. Hardware wallets utilize technologies such as security chips to implement digital currency-related functions and provide services to users through IC cards, mobile terminals, wearable devices, and IoT devices.

[0036] Contactless payment: also known as "non-contact payment," is a technology that allows payments to be completed without physical contact (such as card transactions) with the terminal device. This technology utilizes wireless communication technologies, such as radio frequency identification (RFID) or near field communication (NFC), to enable data transmission and interaction between the payment terminal and the accepting terminal.

[0037] Flash card: This refers to a transaction failure when a user attempts to make a payment using a digital currency hardware wallet. After the user taps the card (a contactless payment method), the receiving terminal fails to receive the final instruction from the digital currency hardware wallet for some reason, resulting in the transaction failing. In related technologies, alternative payment methods are required in this situation.

[0038] Industry scenario information: This can represent the scenario information corresponding to the industry sector associated with the payment terminal during the transaction process. Examples include wholesale and retail, catering and tourism, education and healthcare, and public services. Taking public services as an example, this could include data on entering and exiting stations in the public transportation sector, such as rail transit systems. It can also include scenarios such as supermarket shopping, hospital payments, campus card payments, and utility bill payments.

[0039] Account identifier: This can refer to one or more types of identifiers associated with an account (e.g., a primary account associated with a user's account, a card number associated with the account, a payment card number associated with the account, a token associated with the account, etc.). The account identifier uniquely identifies one or more accounts associated with a user and can be any combination of numbers, characters, and / or symbols. In this disclosure, the focus is primarily on account identifiers for hardware wallets or hardware wallet-related applications.

[0040] Cryptocurrency applications are typically housed within the security authentication module of a hardware wallet, which can be, for example, a security chip. These applications provide services such as opening and managing personal cryptocurrency wallets, and exchanging and circulating cryptocurrencies (e.g., controlling transaction processes, secure storage, and managing issuers).

[0041] Feature negotiation: In the field of digital currency, feature negotiation refers to classifying the key capabilities involved in various business models, technical implementation solutions, and hardware media forms (card wallets, smartwatches, mobile terminals, wristbands, POS machines, IC cards, ATMs, etc.) of hardware wallets. Each institution achieves interoperability based on capability interaction and feature negotiation requirements. During implementation, some functions can be implemented according to business needs.

[0042] It should be noted that the technical solutions in this disclosure, including the collection, updating, analysis, processing, use, transmission, and storage of user personal information, all comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken to prevent unauthorized access to user personal information data and to safeguard user personal information security, network security, and national security.

[0043] In related technologies, when using a digital currency hard wallet (hereinafter referred to as "hard wallet") to make contactless payments on industry terminals such as rail transit, it is necessary to rewrite the industry scenario information on the hard wallet and obtain transaction information (or payment information). However, when the data on the hard wallet is rewritten, a "flash card" phenomenon may occur, resulting in the inability to receive response information from the digital currency hard wallet, causing the transaction to fail.

[0044] To address the aforementioned issues, at least one embodiment of this disclosure provides a transaction method and a related terminal, offering a reliable solution to the "flash card" phenomenon that occurs during transactions involving hardware wallets, thereby improving transaction success rate and efficiency.

[0045] In the following, embodiments according to this disclosure will be described in detail with reference to the accompanying drawings. In the drawings, like elements are designated using the same reference numerals. Furthermore, throughout the detailed description, like terms are used to refer to the same elements.

[0046] Figure 1 It is a view used to describe the "flash card" situation that occurs in digital currency hardware wallets during transactions.

[0047] refer to Figure 1The transaction system includes a hardware wallet 120 and acceptance terminals used in different scenarios (illustrated as 130A, 130B, and 130C). The hardware wallet 120 can be an electronic device including an NFC card chip. For example, the hardware wallet 120 can be a mobile terminal capable of supporting one or more NFC functions (NFC payment functions). Generally, the hardware wallet 120 can use NFC to perform payments or communications. When using NFC to perform payments or communications, it can drive and utilize digital currency applications.

[0048] For example, acceptance terminals 130A, 130B, and 130C can communicate with the hard wallet 120 in a contactless manner via NFC. Using NFC, acceptance terminals 130A, 130B, and 130C can perform the following functions with the hard wallet 120: contactless mobile payment, security authentication, and data exchange. Depending on the industry scenario, the acceptance terminals may include, for example, public facility acceptance terminals (the access gate of the rail transit system shown in Figure 130A), point-of-sale (POS) terminals 130B, mobile terminals 130C, etc. In addition, other acceptance terminals capable of transacting with digital currency hard wallets are also included, without limitation here. Hereinafter, the rail transit system access gate 130A will be used as an example of an acceptance terminal to describe the embodiments of this disclosure; however, the embodiments of this disclosure are not limited thereto.

[0049] During the transaction, user 110 uses a hardware wallet 120 to conduct a contactless transaction at the terminal. In different industry scenarios, such as subway exit scenarios in the public transportation sector, the terminal using the hardware wallet as the transaction object, such as the access gate 130A, needs to rewrite the industry scenario information on the hardware wallet (an example of setting type information) and simultaneously obtain payment transaction information. However, after the data on the hardware wallet is modified, due to communication interruption, the access gate 130A does not receive a response, resulting in transaction failure.

[0050] To address transaction interruptions caused by hardware wallet flash card issues, several embodiments of this disclosure provide a payment transaction solution. This solution identifies the hardware wallet that initiated the transaction request and performs corresponding processing operations. For example, it rewrites data for hardware wallets that did not have a specific account identity and re-executes subsequent transaction processes (e.g., gate opening for entry; gate opening after completing payment transactions for exit). For non-specific account identities, it selects to modify set type information and executes transaction operations (e.g., when exiting, if the user is determined to be a non-flash card user, the exit data rewriting and gate opening process is performed). This solution can handle unexpected situations at a lower cost and alleviate the inefficiency of payment transactions caused by unexpected situations.

[0051] Figure 2A block diagram of an acceptance terminal 200 for processing digital currency hard wallet transactions according to at least one embodiment of the present disclosure is shown.

[0052] refer to Figure 2 The receiving terminal 200 may include a communicator 210, a memory 220, and a processor 230.

[0053] For example, communicator 210 can communicate with another electronic device at least via a wireless communication network. According to embodiments of this disclosure, communicator 210 is configured to wirelessly communicate with a digital currency hard wallet 400. Specifically, the communication connection method can include a short-range wireless communication connection for forming a device-to-device (D2D) communication channel. Here, the short-range wireless communication connection can include a communication connection via a short-range wireless communication network according to short-range wireless communication standards such as Bluetooth, Wi-Fi, BLE, Near Field Communication (NFC) / Radio Frequency Identification (RFID), Wi-Fi Direct, Ultra Wideband (UWB), Zigbee, etc. For example, communicator 210 in embodiments of this disclosure includes an NFC card chip to transmit information via NFC wireless communication.

[0054] Memory 220 may store data, one or more programs, one or more instructions, or at least one of one or more applications. Memory 220 may include at least one type of storage medium selected from flash memory, hard disk storage, multimedia card micro storage, card-type memory (e.g., SD or XD memory), RAM, static RAM (SRAM), ROM, electrically erasable programmable ROM (EEPROM), programmable ROM (PROM), magnetic storage, magnetic disk, and optical disk.

[0055] For example, in at least one embodiment of this disclosure, the memory 220 is configured to store at least the transaction data and industry scenario information change records of the most recent interrupted transaction with the digital currency hard wallet 400. The transaction data of the most recent interrupted transaction (associated with the transaction) includes at least the account identifier or user identifier saved at the time of the most recent hard wallet transaction interruption. In addition, it may also include data such as terminal transaction attributes, transaction amount, data associated with the services involved in the transaction, acceptance terminal identifier, and random numbers.

[0056] For example, in embodiments of this disclosure, the setting type information can be information that the accepting terminal needs to modify to enable payment transactions with the paying terminal. For example, in embodiments of this disclosure, the setting type information includes industry scenario information, which represents the scenario information corresponding to the industry sector associated with the accepting terminal. In the scenario where the accepting terminal is a passage gate in a rail transit system, the industry scenario information includes data related to the entry and exit scenarios, such as the station number, time, terminal number, city number, and entry / exit status identifier. In public transportation scenarios, each time the terminal enters or exits a station, it needs to update the industry scenario information in its hardware wallet. Besides ensuring the status is normal, it also needs to perform segmented billing based on station information, such as calculating the payment amount based on the entry station number and the current (exit) point number in the hardware wallet.

[0057] Of course, in addition to the above, industry scenario information can also include setting an industry scenario identifier corresponding to the payment scenario. For example, when the payment scenario is a bus POS or a rail transit gate, its industry scenario identifier corresponds to this payment scenario; for example, the industry scenario identifier for a bus POS is A001, and the industry scenario identifier for a rail transit gate is A002. When the payment scenario is a shopping mall or supermarket POS, the industry scenario identifier will change; for example, the industry scenario identifier for a shopping mall POS is B001, and the industry scenario identifier for a supermarket POS is B002. Setting this industry scenario identifier also facilitates the payment terminal and the acceptance terminal to determine the shared key based on the identifier, thereby completing security authentication and other operations. Of course, for some general POS consumption scenarios, it is not necessary to set an industry scenario identifier; this is not a limitation.

[0058] For example, the industry scenario information change record includes the industry scenario information pre-stored in the acceptance terminal, and may also include the time, location (site), acceptance terminal number, and other information of the last data rewrite. This information can be used to prepare for the identification of the hardware wallet later.

[0059] In embodiments of this disclosure, processor 230 can execute at least one instruction to control a desired operation to be performed. The operations performed by processor 410 will be described in detail below. The term "processor" should be understood to include both the singular and plural forms. For example, processor 230 may preferably be a security element.

[0060] For example, in this embodiment of the disclosure, the processor 230 may be configured with instructions to perform the following operations: control the communicator 210 to receive a transaction request initiated by the digital currency hard wallet 400 via a wireless communication connection; identify the identity of the digital currency hard wallet 400 that initiated the transaction request based on the transaction request, the transaction data of the most recent transaction interruption, and the setting type information change record; and, in response to the identity recognition result of the digital currency hard wallet 400 that initiated the transaction request, select to perform a setting type information change operation on the digital currency hard wallet 400 and / or perform a transaction operation.

[0061] For the receiving terminal 200, it is unaware whether the hardware wallet 400 currently engaged in a transaction is making its first card swipe or a second card swipe; it needs to identify the identity of the hardware wallet 400. Therefore, the receiving terminal 200 in this embodiment of the disclosure can, by setting an identification strategy, identify whether the current hardware wallet 400 is making its first card swipe or a second card swipe (for a contactless card user) based on the request information sent by the current hardware wallet 400 and the record of the previous transaction interruption; or, it can also identify whether the current hardware wallet 400 is making its first card swipe or a second card swipe (for a contactless card user) based on the request information sent by the current hardware wallet 400, the record of the previous transaction interruption, and the data of the set type information, and provide a corresponding and reasonable transaction process operation after identifying the identity.

[0062] For example, in this embodiment of the disclosure, the processor 230 can be configured to compare the account identifier of the transaction request with the account identifier of the most recent interrupted transaction data to determine whether it belongs to a specific account (e.g., a flash card user). This method is relatively simple because, considering that in general, when a transaction is interrupted, the card is often swiped again to complete the transaction, the receiving terminal only needs to compare the account identifier to quickly determine the user's identity and whether it is the user whose transaction was interrupted last time. Since when a flash card is detected, the hardware wallet has often already completed the modification of the set type information, but has not yet returned response information to the receiving terminal that initiated the instruction, comparing only the account identifier information can cover a large range of flash card phenomena.

[0063] Of course, the following situation may also occur: Taking entry as an example, after the acceptance terminal and the hardware wallet establish a communication connection, the communication connection may be interrupted just as the acceptance terminal sends a data rewrite instruction. In this case, the hardware wallet has not yet received the data rewrite instruction and therefore has not completed the data rewrite operation. If only the account identifier is identified, it is possible that the access gate will be opened based on the account identifier to determine if the user is a flash card user. Although the access gate is opened, when the user exits, because the industry scenario information was not rewritten when entering the station, the payment amount cannot be accurately calculated, affecting the smooth progress of the payment transaction process.

[0064] In response to the above situation, for example, in the embodiments of this disclosure, the processor 230 may be configured to: compare the account identifier of the transaction request with the account identifier of the transaction data of the most recent transaction interruption to determine whether it is a digital currency hard wallet of the most recent transaction interruption; and determine whether the digital currency hard wallet is a specific account based on the set type information change record.

[0065] For example, the transaction data from the most recent interrupted transaction stored in the terminal contains an account identifier record. By comparing the account identifier, it can be determined whether it belongs to the hardware wallet of the terminal that made the most recent transaction. Then, the hardware wallet's configuration type information is read and compared with its own stored configuration type information records. For example, it checks whether the entry / exit time is within the data rewrite time window and whether the industry scenario information read, such as the site number and terminal number, matches the pre-stored industry scenario information. In this way, in addition to more accurately identifying flash card users, it can also confirm that the hardware wallet's configuration type information has been rewritten, ensuring the smooth progress of subsequent transaction processes.

[0066] For example, in this embodiment of the disclosure, the processor 230 can be configured to: upon identifying a specific user, not rewrite the setting type information of the digital currency hard wallet that initiated the transaction request, re-obtain payment information from the digital currency hard wallet, and execute the transaction operation; upon identifying a non-specific user, perform a change operation on the setting type information of the digital currency hard wallet that initiated the transaction request and execute the transaction operation. In this embodiment of the disclosure, the "specific user" can be the user who most recently experienced a transaction interruption and completed the rewriting of the setting type information (e.g., a flash card user whose transaction was interrupted due to a flash card situation).

[0067] For example, in this embodiment of the disclosure, after completing the payment operation, the hardware wallet needs to store payment information locally. The payment information may include the account identifiers of the payer and payee, digital currency information, MAC address, and other information. In addition, the acceptance terminal can determine whether to obtain the payment information stored in the hardware wallet based on the industry scenario information read from the hardware wallet. For example, if the read industry scenario information indicates that the entry / exit identifier has been updated, the payment information stored in the hardware wallet at the time of the most recent transaction interruption can be directly obtained, and subsequent operations will be performed, such as opening the gate. If the user is identified as a non-specific user, the operation of re-obtaining payment information is not supported, and the case is determined to be the case of opening the gate for entry.

[0068] For example, when determining that the current card-swiping hardware wallet belongs to a contactless card user, it's easy to understand that its internal configuration information has already been rewritten. Therefore, there's no need for redundant rewriting operations, and the transaction operation is re-executed, such as opening the gate. If the current card-swiping hardware wallet does not belong to a contactless card user, it proves that this is the first time swiping, so its configuration information needs to be rewritten. After receiving a response after the rewriting, the transaction operation continues. For example, in an outbound scenario where a contactless card occurs, the terminal also needs to retrieve the payment information from the digital currency hardware wallet again and execute the transaction operation, then send the payment information to the backend server for processing.

[0069] For example, in this embodiment of the disclosure, the processor 230 can also be configured to generate first authentication information according to a shared key corresponding to the set type information, control the communicator 220 to send the first authentication information to the digital currency hard wallet 400 to perform authentication, and receive second authentication information generated according to the shared key corresponding to the set type information sent by the hard wallet 400, and perform authentication based on the received second authentication information and the generated first authentication information. Specifically, the first authentication information may be generated by the receiving terminal, and the second authentication information may be generated by the hard wallet. The receiving terminal sends the first authentication information to the hard wallet, and the hard wallet compares the first authentication information and the second authentication information; the hard wallet sends the second authentication information to the receiving terminal, and the receiving terminal verifies the consistency of the first authentication information and the second authentication information, thereby achieving two-way authentication.

[0070] According to embodiments of this disclosure, authentication can determine whether the hardware wallet issuing the transaction request is a device with legitimate permissions. For example, if the type information is set to industry scenario information, each terminal can use the shared key corresponding to the industry scenario identifier in the industry scenario information. Then, the authentication information can be generated by processing a random number using a preset shared key to generate a transaction process key, and then using the transaction process key to generate a Message Authentication Code (MAC) to confirm information integrity and perform authentication. The generation method of the first authentication information and the generation method of the second authentication information are the same. By interactively sending the first authentication information and the second authentication information to the hardware wallet and the receiving terminal, two-way authentication between the receiving terminal and the hardware wallet can be completed.

[0071] Figure 3 A flowchart of a method 300 for processing digital currency hard wallet transactions according to at least one embodiment of the present disclosure is shown. Figure 3 It is based on reference Figure 2 The flowchart describes the operation performed by the receiving terminal 200 to process digital currency hard wallet transactions. Therefore, when describing method 300, further details will not be repeated. Figure 2 The same aspects of the operation performed by the acceptance terminal 200.

[0072] refer to Figure 3 According to method 300, in operation S310, the receiving terminal 200 receives a transaction request initiated by the hard wallet 400; in operation S320, the identity of the hard wallet 400 that initiated the transaction request is identified based on the transaction request, the transaction data of the most recent transaction interruption, and the setting type information change record; in operation S330, in response to the identity recognition result of the hard wallet 400 that initiated the transaction request, the terminal 200 selects to perform a change to the setting type information of the hard wallet 400 and / or perform a transaction operation.

[0073] Before operating S320, the receiving terminal 200 generates first authentication information based on the shared key corresponding to the set type information; sends the first authentication information to the hardware wallet 400 to enable it to perform authentication, and receives the second authentication information generated by the hardware wallet 400 based on the shared key corresponding to the set type information, and performs authentication based on the received second authentication information and the generated first authentication information.

[0074] Specifically, in operation S320, the receiving terminal 200 compares the account identifier of the transaction request with the account identifier of the transaction data of the most recent transaction interruption to determine whether it is the hardware wallet of the most recent transaction interruption; and determines whether the hardware wallet is a specific account based on the setting type information change record.

[0075] Alternatively, in operation S320, the receiving terminal 200 compares the account identifier of the transaction request with the account identifier of the transaction data of the most recent transaction interruption to determine whether it is a specific account.

[0076] Specifically, in operation S330, if the receiving terminal 200 determines that the hard wallet 400 is a specific user, it will not rewrite the setting type information of the hard wallet 400, but will re-execute the transaction operation or re-obtain payment information from the hard wallet 400 and execute the transaction operation; if it is identified as a non-specific user, it will perform the operation to change the setting type information of the hard wallet 400 and execute the transaction operation.

[0077] To better understand the embodiments of this disclosure, the following describes the transaction process using a hardware wallet and turnstile as the interaction objects, taking the scenario of entering and exiting a rail transit system in the public transportation field as an example.

[0078] Figure 4 An exemplary operation flowchart is shown for handling the flash card situation of a digital currency hard wallet in a rail transit station entry scenario according to at least one embodiment of the present disclosure.

[0079] refer to Figure 4The hard wallet 400 and the rail transit system's access gate 405 conduct the first transaction 4000. During this process, the two parties need to exchange information and perform relevant feature negotiation operations (step S410), security performance authentication operations (step S401), and industry scenario information rewriting operations (step S402).

[0080] First, let me explain the operation of step S410.

[0081] In step S410, the hardware wallet 400 interacts with the gate 405 to perform the operations of selecting an application and negotiating features.

[0082] After the gate 405 and the hard wallet 400 establish a communication connection, the gate 405 sends a command to the hard wallet 400 to select the digital currency application of the hard wallet 400, so that the application of the hard wallet 400 can be opened to realize the digital currency transaction process (the operation of selecting the application).

[0083] Next, during the transaction between the hardware wallet 400 and the gate 405, the gate 405 sends a transaction instruction for feature negotiation to the hardware wallet 400. This instruction includes, for example, the type of gate 405 (a public infrastructure terminal), the usage scenario type (e.g., rail transit, passenger ferries, public buses, etc.), the requested transaction mode (e.g., online or offline, real-time or delayed transaction), human-computer interaction features (e.g., display screen, keyboard, voice player, camera, biometric module, etc.), supported security algorithms, and version number. Subsequently, after receiving the feature negotiation transaction instruction from the gate 405, the hardware wallet 400 matches its supported transaction models with the requested model from the gate 405, records the type and usage scenario of the gate 405, and returns the matching result.

[0084] Next, the gate 405 determines the subsequent transaction process based on the matching result returned by the hard wallet 400. If the matching fails, the transaction is terminated and the gate does not open; if the matching is successful, the transaction continues and the security performance authentication operation in step S401 is executed.

[0085] After step S410, the gate 405 can initially verify whether the hard wallet 400, as the transaction object, has transaction capabilities, thus preparing for further transaction operations.

[0086] Next, the operation of each sub-step of step S401 will be explained.

[0087] In step S420, the gate 405 sends an instruction to obtain the user identifier, random number, and industry scenario information returned by the hardware wallet 400.

[0088] Specifically, the gate 405 sends the corresponding transaction instruction to conduct the transaction based on the successfully matched model, and the gate 405 obtains information such as the digital currency application user identifier, random number, and industry scenario information returned by the hard wallet 400.

[0089] In step S430, the gate 405 generates the corresponding transaction process key based on the preset shared key.

[0090] For example, a public transportation industry scenario identifier and a shared key (usually a symmetric key) are pre-written into the turnstile 405, and the shared key is stored in a one-to-one correspondence with the industry scenario identifier. The turnstile 405 processes the obtained random number based on the shared key to generate the transaction process key.

[0091] In step S440, the hardware wallet 400 generates the corresponding transaction process key based on the preset shared key.

[0092] Similarly, the shared key is also stored in the hard wallet 400, and this key is pre-written into the hard wallet 400's memory and corresponds to the industry scenario identifier. In this step, the hard wallet 400 generates the transaction process key using the shared key. The specific generation method can refer to the method of the gate 405 to ensure consistency in the generation method.

[0093] In step S450, the hard wallet 400 and the gate 405 complete two-way authentication based on the transaction process key.

[0094] For example, gate 405 can generate a Message Authentication Code (MAC) to verify information integrity and perform authentication. A transaction process key is obtained by encrypting a random number using a shared key. This key is then used to encrypt all transmitted transaction information in CBC mode, ultimately yielding the MAC. Since attackers do not possess the transaction process key, they cannot calculate the corresponding MAC value even if they modify the transaction information, thus identifying any forgery or tampering. Hard wallet 400 can also generate MAC values ​​using the same method.

[0095] Both the gate 405 and the hard wallet 400 use the same key and the same algorithm to generate MAC values ​​(an example of the first and second authentication information). They then exchange MAC values ​​for comparison. If the two MAC values ​​are the same, the MAC verification is successful; otherwise, the verification fails.

[0096] The gate 405 and the hardware wallet 400 interact by sending their self-generated MAC values, which can determine the security of the transaction and achieve the purpose of two-way authentication.

[0097] Next, the operation of each sub-step in step S402 will be explained.

[0098] In step S460, the gate 405 modifies the industry scenario information of the hardware wallet 500 and obtains the response information.

[0099] Specifically, gate 405 rewrites industry scenario information of the digital currency application in the hard wallet by using the transaction process key. For example, it uses the transaction process key to perform MAC integrity protection on transaction information (including industry scenario information).

[0100] In step S480, after receiving the instruction, the hardware wallet 400 rewrites the industry scenario information.

[0101] In step S470, the gate 405 detects a flash card situation and prompts the hard wallet 400 to swipe the card again.

[0102] If communication is suddenly interrupted after the gate 405 sends the industry scenario information rewrite instruction, and the gate 405 does not receive a response from the hardware wallet 400, then a flash card situation is determined to have occurred, and the transaction fails.

[0103] When the gate 405 detects a flash card situation, it saves the user identifier of the digital currency application in the hard wallet 400 and prompts the user of the hard wallet 400 to swipe the card again. Subsequently, the hard wallet 400 and the rail transit system's access gate 405 conduct a second transaction 5000. During this process, the gate 405 and the hard wallet 400 perform feature negotiation and two-way authentication, which is similar to steps S410 and S401 in the first transaction 4000, so it will not be described again.

[0104] The following describes the operation of each sub-step in identifying a user's identity.

[0105] The purpose of identifying users is as follows: Taking a rail transit scenario as an example, after a user swipes their card (a form of hardware wallet) again at the access gate, the gate determines whether it is the same hardware wallet user whose transaction failed due to a lack of response. If the entry / exit time, station, and other information (examples of industry scenario information) match, the entry process can be re-executed to allow the user to pass. If the information shows that the user has already entered the station, but it is not the card swiped just now, and the entry time and station do not match, it indicates an incomplete transaction occurred previously, which may require manual processing.

[0106] In step S490, the gate 405 identifies whether the current card-swiping account is a flash card account (an example of a specific account).

[0107] For example, first, compare the user identifier to determine if it is the same user identifier saved from the most recent transaction interruption, and then determine if it is a flash card user based on information such as the rewrite time, location, and terminal number in the industry scenario information change record. Of course, the method of only checking the user identifier is also possible.

[0108] In step S500, if the user is a flash card user and the entry / exit identifier has not been changed, the gate 405 will not rewrite the industry scenario information of the hardware wallet 400 and will not support obtaining the payment information of the hardware wallet (at this time, no payment has been made and the information has not been generated), and the gate will be opened to allow passage.

[0109] Figure 5 An exemplary operation flowchart is shown for handling the flash card situation of a digital currency hard wallet in a rail transit exit scenario according to at least one embodiment of the present disclosure. Figure 5 Zhongyu Figure 4 The same or similar steps are indicated by using the same tags, therefore, in the description Figure 5 At that time, the description will not be repeated. Figure 4 Similarities.

[0110] In the exit scenario, the turnstile 405 performs the same action as... Figure 4 The different operations for entering the station are: sub-step S480' in step S402', and steps S510 and S500' after identifying the account identity as a flash card user.

[0111] In step S480', the hardware wallet 400 modifies the industry scenario information while also saving the payment information.

[0112] In step S510, if the gate 405 recognizes the hard wallet 400 as a flash card user and the entry / exit identifier is updated, it can then retrieve the payment information of the last transaction (most recent transaction) of digital currency from the hard wallet 400.

[0113] In step S500', since the payment transaction is completed, the gate 405 opens to allow passage.

[0114] If you are not a flash card user, you can normally perform operations to rewrite industry scenario information and obtain digital currency payment information. This payment information may include the account identifiers of both the payer and payee, digital currency information, MAC addresses, and other details.

[0115] In step S500', the gate 405 can also upload the payment transaction information to the backend server 404 in real time for amount settlement after receiving the payment transaction information sent back by the hard wallet 400, or upload the payment transaction information during shutdown periods or off-peak periods.

[0116] It should be noted that the above application scenarios are merely illustrative to illustrate one or more aspects of this invention in specific scenarios. However, these aspects are not essential, and various modifications can be made to the application scenario. It is readily understood that specific application scenarios, besides the aforementioned communication gates in rail transit systems, can also include parking lots or highways, etc., and this disclosure does not limit the scope of the applications.

[0117] At least some embodiments of this disclosure also provide an electronic device. Figure 6 A schematic diagram of an electronic device 600 according to at least one embodiment of the present disclosure is shown.

[0118] like Figure 6 As shown, the electronic device 600 includes one or more processors 610 and a memory 620. The memory 620 includes one or more computer program modules 621. The one or more computer program modules 621 are stored in the memory 620 and configured to be executed by the processor 610. These computer program modules 621 include instructions for executing a method 300 for processing digital currency hard wallet transactions according to at least one embodiment of the present disclosure and its additional aspects. When executed by the processor 610, they can perform one or more steps of the method 300 for processing digital currency hard wallet transactions according to at least one embodiment of the present disclosure and its additional aspects. The memory 620 and the processor 610 can be interconnected via a bus system and / or other forms of connection mechanisms (not shown). For example, the bus may be a Peripheral Component Interconnect Standard (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc.

[0119] For example, processor 610 may be a central processing unit (CPU), a digital signal processor (DSP), or other processing unit with data processing and / or program execution capabilities, such as a field-programmable gate array (FPGA). Processor 610 may be a general-purpose processor or a special-purpose processor, capable of controlling other components in electronic device 600 to perform desired functions.

[0120] Exemplarily, memory 620 may include any combination of one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, erasable programmable read-only memory (EPROM), portable compact disc read-only memory (CD-ROM), USB memory, flash memory, etc. One or more computer program modules 621 may be stored on the computer-readable storage medium, and processor 610 may run one or more computer program modules 621 to implement various functions of electronic device 600. The computer program modules include multiple computer-executable instructions. Various application programs and various data, as well as various data used and / or generated by the application programs, may also be stored in the computer-readable storage medium.

[0121] For example, electronic device 600 may also include input devices such as touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, and gyroscopes; output devices such as liquid crystal displays, speakers, and vibrators; storage devices such as magnetic tapes and hard disks (HDDs or SDDs); and communication devices such as network interface cards like LAN cards and modems. The communication devices allow electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data and perform communication processing via networks such as the Internet. A drive is connected to the I / O interface as needed. Removable storage media, such as disks, optical disks, magneto-optical disks, and semiconductor memories, are installed on the drive as needed so that computer programs read from them can be installed into the storage device as required.

[0122] For example, the electronic device 600 may further include a peripheral interface (not shown in the figure). This peripheral interface can be of various types, such as a USB interface, a Lightning interface, etc. The communication device can communicate wirelessly with networks and other devices, such as the Internet, intranets and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs). Wireless communication can use any of a variety of communication standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Wi-Fi (e.g., based on IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11n standards), Voice over Internet Protocol (VoIP), Wi-MAX, protocols for email, instant messaging, and / or Short Message Service (SMS), or any other suitable communication protocol.

[0123] The electronic device 600 may be, for example, a system-on-a-chip (SOC) or a device including the SOC. For instance, it can be any device such as a mobile phone, tablet, laptop, e-reader, game console, television, digital photo frame, navigator, home appliance, communication base station, industrial controller, server, etc., or any combination of data processing devices and hardware. The embodiments of this disclosure do not limit this. The specific functions and technical effects of the electronic device 600 can be found in the description above of the method 300 for processing digital currency hard wallet transactions according to at least one embodiment of this disclosure and its additional aspects, and will not be repeated here.

[0124] Figure 7A schematic diagram of a non-transiently readable storage medium 700 according to at least one embodiment of the present disclosure is shown.

[0125] like Figure 7 As shown, a non-transiently readable storage medium 700 stores computer instructions 710, which, when executed by a processor, perform one or more steps of the method 300 for processing digital currency hard wallet transactions as described above and its additional aspects.

[0126] For example, when the program code is read by a computer, the computer can execute the program code stored in the computer storage medium to perform one or more steps to implement, for example, the method 300 for processing digital currency hard wallet transactions according to at least one embodiment of the present disclosure and its additional aspects.

[0127] For example, the non-transitory readable storage medium may include a memory card of a smartphone, a storage component of a tablet computer, a hard disk of a personal computer, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), portable compact disc read-only memory (CD-ROM), flash memory, and other non-transitory readable storage media or any combination thereof.

[0128] At least some of the embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other.

[0129] It should be noted that, in this document, relational terms such as "first," "second," etc., are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0130] The following points should be noted regarding this disclosure:

[0131] (1) The accompanying drawings of the embodiments of this disclosure only involve the structures involved in the embodiments of this disclosure. Other structures can be referred to the general design.

[0132] (2) Where there is no conflict, the embodiments of this disclosure and the features in the embodiments can be combined with each other to obtain new embodiments.

[0133] The above description is merely an exemplary embodiment of this disclosure and is not intended to limit the scope of protection of this disclosure, which is determined by the appended claims.

Claims

1. A terminal for processing digital currency hard wallet transactions, the terminal comprising: A communicator configured to communicate with the digital currency hard wallet; The memory is configured to store at least the transaction data and configuration type information change records of the most recent transaction that was interrupted in the digital currency hard wallet; as well as At least one processor, configured as follows: The communicator is controlled to receive transaction requests initiated by the digital currency hard wallet via a wireless communication connection; Identifying the identity of the cryptocurrency hard wallet that initiated the transaction request based on the transaction request, the transaction data of the most recent transaction interruption, and the setting type information change record specifically includes: comparing the account identifier of the transaction request with the account identifier of the transaction data of the most recent transaction interruption to determine whether it is the cryptocurrency hard wallet of the most recent transaction interruption; and determining whether the cryptocurrency hard wallet is a specific account based on the setting type information change record. In response to the identity verification result of the digital currency hard wallet that initiated the transaction request, the system may choose to perform a change operation on the setting type information of the digital currency hard wallet and / or perform a transaction operation.

2. The acceptance terminal according to claim 1, wherein, The at least one processor is configured to: upon identifying a specific user, not change the setting type information of the digital currency hard wallet that initiated the transaction request, and re-obtain payment information from the digital currency hard wallet and execute the transaction operation; After identifying that the user is not a specific user, the system performs a change operation on the setting type information of the digital currency hard wallet that initiated the transaction request and executes the transaction operation.

3. The acceptance terminal according to claim 1, wherein, The at least one processor is configured to generate first authentication information based on a shared key corresponding to a set type information, control the communicator to send the first authentication information to the digital currency hard wallet to enable it to perform authentication, and control the communicator to receive second authentication information generated by the digital currency hard wallet based on a shared key corresponding to a set type information, and perform authentication based on the received second authentication information and the generated first authentication information.

4. The acceptance terminal according to any one of claims 1 to 3, wherein, The set type information includes industry scenario information, which represents the scenario data corresponding to the industry field associated with the acceptance terminal.

5. The acceptance terminal according to claim 4, wherein, The acceptance terminal is a passage gate of the rail transit system, and the industry scenario information includes data related to the entry and exit scenarios.

6. A method for processing digital currency hard wallet transactions, the method comprising: Receive transaction requests initiated by the digital currency hardware wallet; The identity of the digital currency hard wallet that initiated the transaction request is identified based on the transaction request, the transaction data of the most recent transaction interruption, and the setting type information change record; In response to the identity verification result of the digital currency hard wallet that initiated the transaction request, the user may choose to perform a change operation on the setting type information of the digital currency hard wallet and / or perform a transaction operation. The step of identifying the identity of the digital currency hard wallet includes: Compare the account identifier of the transaction request with the account identifier of the transaction data of the most recent transaction interruption to determine whether it is a digital currency hard wallet of the most recent transaction interruption; And determine whether the digital currency hard wallet belongs to a specific account based on the change record of the set type information.

7. The method according to claim 6, wherein, Once a specific user is identified, the type information of the digital currency hard wallet that initiated the transaction request will not be rewritten. Instead, the payment information will be retrieved from the digital currency hard wallet again and the transaction operation will be executed. After identifying a non-specific user, the system performs a change operation on the setting type information of the digital currency hard wallet that initiated the transaction request and executes the transaction operation.

8. The method according to claim 6, wherein, The method further includes: Generate the first authentication information based on the shared key corresponding to the set type information; Send the first authentication information to the digital currency hard wallet to enable it to perform authentication, and The system receives second authentication information from the digital currency hard wallet, generated by a shared key corresponding to a set type of information, and performs authentication based on the received second authentication information and the generated first authentication information.

9. The method according to any one of claims 6 to 8, wherein, The set type information includes industry scenario information, which represents the scenario data corresponding to the industry field associated with the acceptance terminal.

10. The method according to claim 9, wherein, The acceptance terminal is a passage gate of the rail transit system, and the industry scenario information includes data related to the entry and exit scenarios.

11. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 6 to 10.

12. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 6 to 10.

Images