Disclosure of Invention
In view of the above, there is a need to provide a hardware wallet data synchronization method, apparatus, computer device, computer readable storage medium and computer program product capable of facilitating a payment process for a user in response to the above technical problems.
In a first aspect, the present application provides a hardware wallet data synchronization method. The method comprises the following steps:
acquiring a payment request of a hardware wallet;
acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
when the remaining offline times are lower than a first preset threshold value, synchronizing data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing management of digital assets in the hardware wallet;
and writing the transaction information corresponding to the payment request into the hardware wallet.
In one embodiment, the synchronizing data in the hardware wallet with a remote server to reset the number of times the hardware wallet can be taken offline includes:
obtaining balance credentials and transaction flow data from the hardware wallet;
uploading a balance voucher and transaction running water data corresponding to the hardware wallet to a remote server;
acquiring currency string data fed back by the remote server according to the balance voucher and the transaction running data;
writing the coin string data to the hardware wallet to reset the number of times the hardware wallet can be taken offline to update the number of times the hardware wallet is taken offline.
In one embodiment, after synchronizing the data in the hardware wallet with a remote server to reset the number of times the hardware wallet can be offline, the method further includes:
and when the hardware wallet and the remote server are synchronized, pushing user prompt information corresponding to the synchronization operation.
In one embodiment, the writing transaction information corresponding to the payment request to the hardware wallet includes:
obtaining payment delay corresponding to the payment request;
when the operation time of the synchronous operation exceeds the payment delay, pushing refreshing prompt information after the synchronous operation is finished;
acquiring a payment refreshing request submitted by the hardware wallet according to the refreshing prompt information;
and writing the transaction information corresponding to the payment re-swiping request into the automatically updated hardware wallet.
In a second aspect, the present application provides another hardware wallet data synchronization method. The method comprises the following steps:
acquiring a payment request of a hardware wallet;
acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
when the number of the remaining offline times is not zero, writing transaction information corresponding to the payment request into the hardware wallet;
and when the remaining offline times are lower than a second preset threshold value, synchronizing data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing management of digital assets in the hardware wallet.
In a third aspect, the application also provides a hardware wallet data synchronization device. The device comprises:
the first request acquisition module is used for acquiring a payment request of the hardware wallet;
the first data acquisition module is used for acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
a first data synchronization module, configured to synchronize data in the hardware wallet with a remote server to reset the offline times of the hardware wallet when the remaining offline times are lower than a first preset threshold, where the remote server is configured to implement management of digital assets in the hardware wallet;
and the first information updating module is used for writing the transaction information corresponding to the payment request into the hardware wallet.
In a fourth aspect, the present application further provides another hardware wallet data synchronization apparatus. The device comprises:
the second request acquisition module is used for acquiring a payment request of the hardware wallet;
the second data acquisition module is used for acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
the second information updating module is used for writing the transaction information corresponding to the payment request into the hardware wallet when the remaining offline times are not zero;
and the second data synchronization module is used for synchronizing the data in the hardware wallet with a remote server to reset the offline times of the hardware wallet when the remaining offline times are lower than a second preset threshold, and the remote server is used for realizing the management of the digital assets in the hardware wallet.
In a fifth aspect, the present application further provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the following steps when executing the computer program:
acquiring a payment request of a hardware wallet;
acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
when the remaining offline times are lower than a first preset threshold value, synchronizing data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing management of digital assets in the hardware wallet;
and writing the transaction information corresponding to the payment request into the hardware wallet.
In a sixth aspect, the present application further provides another computer device. The computer device comprises a memory storing a computer program and a processor implementing the following steps when executing the computer program:
acquiring a payment request of a hardware wallet;
acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
when the number of the remaining offline times is not zero, writing transaction information corresponding to the payment request into the hardware wallet;
and when the remaining offline times are lower than a second preset threshold value, synchronizing data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing management of digital assets in the hardware wallet.
In a seventh aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:
acquiring a payment request of a hardware wallet;
acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
when the remaining offline times are lower than a first preset threshold value, synchronizing data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing management of digital assets in the hardware wallet;
and writing the transaction information corresponding to the payment request into the hardware wallet.
In an eighth aspect, the present application further provides another computer-readable storage medium. The computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:
acquiring a payment request of a hardware wallet;
acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
when the number of the remaining offline times is not zero, writing transaction information corresponding to the payment request into the hardware wallet;
and when the remaining offline times are lower than a second preset threshold value, synchronizing data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing management of digital assets in the hardware wallet.
In a ninth aspect, the present application further provides a computer program product. The computer program product comprising a computer program which when executed by a processor performs the steps of:
acquiring a payment request of a hardware wallet;
acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
when the remaining offline times are lower than a first preset threshold value, synchronizing data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing management of digital assets in the hardware wallet;
and writing the transaction information corresponding to the payment request into the hardware wallet.
In a tenth aspect, the present application further provides another computer program product. The computer program product comprising a computer program which when executed by a processor performs the steps of:
acquiring a payment request of a hardware wallet;
acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
when the number of the remaining offline times is not zero, writing transaction information corresponding to the payment request into the hardware wallet;
and when the remaining offline times are lower than a second preset threshold value, synchronizing data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing management of digital assets in the hardware wallet.
According to the hardware wallet data synchronization method, the device, the computer equipment, the storage medium and the computer program product, the remaining offline times corresponding to the hardware wallet are acquired according to the payment request of the user after payment is carried out through the hardware wallet or the payment is finished; and when the remaining offline times are lower than a preset threshold value, synchronizing the data in the hardware wallet with the remote server to reset the offline times of the hardware wallet. Therefore, the online updating of the hardware wallet is not needed to be manually performed by the user during payment, and the convenience of the user in the payment process by using the hardware wallet is ensured.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The hardware wallet data synchronization method provided by the embodiment of the application can be applied to the application environment shown in fig. 1. The hardware wallet 102 may communicate with the payment receiving terminal 104 in a Near Field Communication (NFC), and the payment receiving terminal 104 may communicate with the server 106 through a network. The data storage system may store data that the server 106 needs to process. The data storage system may be integrated on the server 106, or may be located on the cloud or other network server. The checkout terminal 104 may obtain a payment request for the hardware wallet 102; acquiring the remaining offline times corresponding to the hardware wallet 102 according to the payment request; when the remaining offline times are lower than a first preset threshold value, synchronizing the data in the hardware wallet 102 with the remote server to reset the offline times of the hardware wallet 102; the transaction information corresponding to the payment request is written to the hardware wallet 102. The server 106 may be implemented as a stand-alone server or a server cluster composed of a plurality of servers.
In one embodiment, as shown in fig. 2, a hardware wallet data synchronization method is provided, which is described by taking the method as an example applied to the cash receiving terminal 104 in fig. 1, and includes the following steps:
step 201, acquiring a payment request of a hardware wallet;
step 203, obtaining the remaining offline times corresponding to the hardware wallet according to the payment request.
The hardware wallet is used for independently storing the digital asset private key in a chip, isolating the chip from the Internet and realizing plug and play. Hardware wallets are used primarily for offline transactions of digital assets. In an embodiment of the application, the hardware wallet 102 may communicate in close proximity with the checkout terminal 104 to enable offline transactions. The remaining offline times corresponding to the hardware wallet means that, for the hardware wallet, the offline transaction times are limited, and assuming that the consecutive offline transaction times of the hardware wallet 102 are M times, when the consecutive offline transactions are passed, the hardware wallet 102 cannot continue the offline transactions when the remaining offline transaction times are reduced to 0. Therefore, after acquiring the payment request, the remaining offline times corresponding to the hardware wallet need to be acquired at the same time, so as to confirm whether the transaction is allowed.
Specifically, when an offline transaction needs to be performed, the user may bring the hardware wallet close to the payment receiving terminal, submit a payment request to the payment receiving terminal 104 in a manner similar to a card swiping, and the payment receiving terminal 104 obtains the payment request of the hardware wallet 102 and then obtains the remaining offline times corresponding to the hardware wallet based on the payment request. The manner of obtaining the offline times may include obtaining the offline times through a relevant return code or an APDU (Application Protocol Data Unit) instruction.
And step 205, when the remaining offline times are lower than a first preset threshold, synchronizing data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing management of digital assets in the hardware wallet.
Step 207, writing the transaction information corresponding to the payment request into the hardware wallet.
For the hardware wallet, when the number of the remaining offline transactions of the hardware wallet is 0, and when the payment is made on the money collecting equipment, the equipment prompts that the transactions cannot be continued, at the moment, a user needs to use a mobile phone APP or the money collecting equipment, the online synchronous operation is manually performed, and the payment is made after the synchronous updating is successful. This situation may present problems a) affecting the user experience itself. b) Blocking subsequent user payments. c) Some mobile phones do not support NFC card reading, and most hardware wallets only support NFC communication, so that synchronous operation cannot be performed by using the mobile phones. d) The mobile phone with the NFC card reading function is poor in physical examination from the practical application effect. When a user is in operation, the phenomenon that NFC communication fails often occurs. e) Although the user may actively use the handset APP for synchronization before paying before the remaining number is reduced to 0. But this increases the learning cost and burdens the user. Therefore, in order to improve the payment efficiency of the user in the process of using the hardware wallet, by the hardware wallet data synchronization method, when the hardware wallet pays, the remaining offline transaction times of the hardware wallet are synchronized through the money receiving device so as to update the offline times of the hardware wallet, and the offline times of the hardware wallet can be recovered to the initial value. The first preset threshold is a judgment threshold for judging whether the hardware wallet needs to execute the automatic synchronization operation. The first preset threshold may be set to a fixed value, for example, the preset threshold may be set to 4 times, and when the remaining offline times corresponding to the hardware wallet are less than 4 times, it is determined that the automatic synchronization condition is satisfied. The first preset threshold may also be scaled according to a maximum number of times the hardware wallet is offline. If the maximum offline frequency corresponding to the hardware wallet is 10, the first preset threshold may be set to 3, and when the remaining offline frequency corresponding to the hardware wallet is less than 4, it is determined that the automatic synchronization condition is satisfied. When the maximum offline time corresponding to the hardware wallet is 20, the first preset threshold may be set to 5, and when the remaining offline time corresponding to the hardware wallet is less than 5, it is determined that the automatic synchronization condition is satisfied. The synchronization operation specifically refers to that the information of the hardware wallet and the information on the server 106 are synchronized through the cash receiving terminal 104, so that the remaining number of times of the hardware wallet is updated.
Specifically, after the remaining offline times corresponding to the hardware wallet are obtained, it may be determined whether the hardware wallet needs to perform automatic synchronization, and when the remaining offline times corresponding to the hardware wallet are lower than a first preset threshold, it indicates that the hardware wallet is close to being unable to perform offline transactions or is unable to perform offline transactions, and at this time, in order to improve the payment efficiency of the user, an automatic synchronization operation may be performed on the hardware wallet to update the offline times of the hardware wallet. And when the off-line times of the hardware wallet are updated, the transaction information corresponding to the payment request can be smoothly written into the automatically updated hardware wallet, so that the integrity of the payment process is ensured.
According to the hardware wallet data synchronization method, the remaining offline times corresponding to the hardware wallet are acquired according to the payment request of the user after payment is carried out through the hardware wallet or the payment is finished; and when the remaining offline times are lower than a preset threshold value, synchronizing the data in the hardware wallet with the remote server to reset the offline times of the hardware wallet. Therefore, the online updating of the hardware wallet is not needed to be manually performed by the user during payment, and the convenience of the user in the payment process by using the hardware wallet is ensured.
In one embodiment, as shown in FIG. 3, step 205 comprises:
step 302, obtain balance credentials and transaction flow data from the hardware wallet.
And step 304, uploading the balance voucher corresponding to the hardware wallet and transaction flow data to a remote server.
And step 306, acquiring currency string data fed back by the remote server according to the balance voucher and the transaction running data.
In step 308, the coin string data is written into the hardware wallet to reset the number of times the hardware wallet can be taken off line.
The balance certificate refers to a balance certificate of digital assets in the hardware wallet, and the transaction flow refers to flow data generated by the hardware wallet in the transaction process. The coin string data is an expression corresponding to the digital assets of the hardware wallet, and the coin string has the characteristics of separability, transferability, traceability, non-forgeability, non-repudiation and the like: wherein, the separability means that the transfer of partial digital assets can be realized by constructing a transaction chain; the transferable coin string is transmitted in a communication mode such as NFC (near field communication) in a certificate mode; traceability means that the transaction chain contains transaction information and the transaction chain traceability is realized; the unforgeability means that the currency string and the certificate cannot be forged on the premise of ensuring the medium and SE safety of the hardware wallet; non-repudiation refers to non-repudiation that enables the transfer of a currency string through a user signature.
Specifically, when the offline number of times of the hardware wallet is updated, the cash receiving terminal 104 may specifically upload the balance certificate and the transaction flow data corresponding to the hardware wallet to the server 106 of the digital asset operator, and then the server 106 of the digital asset operator checks the balance certificate and the transaction flow to generate a new coin string. And the money receiving terminal 104 sends the new money string to the hardware wallet, and the hardware wallet writes the new money string and restores the remaining offline transaction times to be the maximum value, thereby realizing the offline times updating of the hardware wallet. In this embodiment, the synchronous update of the hardware wallet can be effectively performed through the balance voucher and the transaction flow data.
In one embodiment, after step 203, the method further includes: and when the hardware wallet and the remote server are synchronized, pushing user prompt information corresponding to the synchronization operation.
The user prompt information may specifically include an indicator light, voice, and screen display content. Specifically, when the hardware wallet is automatically updated, in order to ensure the right of awareness of the user, corresponding user prompt information may be pushed to the user at the same time when the synchronous update is completed, so as to inform the user that the hardware wallet is being updated differently. In the embodiment, the openness of the synchronous updating process can be effectively ensured by pushing the user prompt information.
In one embodiment, as shown in FIG. 4, step 207 comprises:
step 401, obtaining a payment delay corresponding to the payment request.
And step 403, when the operation time of the synchronous operation exceeds the payment delay, pushing the re-brushing prompt information after the synchronous operation is completed.
And step 405, acquiring a payment refreshment request submitted by the hardware wallet according to the refreshment prompt information.
Step 407, writing the transaction information corresponding to the payment refreshment request into the automatically updated hardware wallet.
The swiping-again prompt message is used for prompting that the user fails to pay the current request and needs to swipe the card again to submit a new payment request. The payment swipe request is a new payment request submitted to the payee terminal 104 after the user swipes the card again.
In particular, there is a certain delay in a general payment request, and the payment must be completed within the payment delay. In auto-synchronization, the payment operation of the hardware wallet may not be completed within the payment delay due to the need for network communication with the remote server 106 to synchronize information. Therefore, when the operation time of the automatic synchronization operation exceeds the payment delay, the re-swiping prompt information can be pushed to the user after the automatic synchronization operation is completed, the user is prompted to swipe the card again, and the payment is ensured to be carried out smoothly.
In one embodiment, as shown in fig. 5, the present application further provides another hardware wallet data synchronization method, where the method includes:
step 502, a payment request for a hardware wallet is obtained.
And step 504, acquiring the remaining offline times corresponding to the hardware wallet according to the payment request.
Step 506, when the remaining offline number is not zero, writing the transaction information corresponding to the payment request into the hardware wallet.
And step 508, when the remaining offline times are lower than a second preset threshold, synchronizing data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing management of digital assets in the hardware wallet.
Specifically, in addition to automatic synchronization of the hardware wallet at the initial stage of collection when the payment request begins, synchronization may also occur after the payment is completed. The method comprises the steps of firstly obtaining a payment request of the hardware wallet, obtaining the remaining offline times corresponding to the hardware wallet, and judging that transaction information corresponding to the payment request can be written into the automatically updated hardware wallet when the remaining offline times are larger than zero. And then writing the transaction information corresponding to the payment request into the automatically updated hardware wallet, and synchronizing the data in the hardware wallet with the remote server based on the remaining offline times after the payment is completed and a second preset threshold value so as to reset the offline times of the hardware wallet.
According to the hardware wallet data synchronization method, after payment is completed through a hardware wallet, the remaining offline times corresponding to the hardware wallet are obtained according to the payment request of a user; and when the remaining offline times are lower than a preset threshold value, synchronizing the data in the hardware wallet with the remote server to reset the offline times of the hardware wallet. Therefore, the online updating of the hardware wallet is not needed to be manually performed by the user during payment, and the convenience of the user in the payment process by using the hardware wallet is ensured.
It should be understood that, although the steps in the flowcharts related to the embodiments are shown in sequence as indicated by the arrows, the steps are not necessarily executed in sequence as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flowcharts related to the above embodiments may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the steps or stages is not necessarily sequential, but may be performed alternately or alternately with other steps or at least a part of the steps or stages in other steps.
Based on the same inventive concept, the embodiment of the present application further provides a hardware wallet data synchronization apparatus for implementing the above-mentioned hardware wallet data synchronization method. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the method, so specific limitations in one or more embodiments of the hardware wallet data synchronization device provided below can be referred to the limitations of the hardware wallet data synchronization method in the foregoing, and details are not described herein again.
In one embodiment, as shown in fig. 6, there is provided a hardware wallet data synchronizing apparatus including:
a first request acquisition module 601, configured to acquire a payment request of a hardware wallet;
a first data obtaining module 603, configured to obtain, according to the payment request, the remaining offline times corresponding to the hardware wallet;
a first data synchronization module 605, configured to synchronize data in the hardware wallet with a remote server to reset the offline times of the hardware wallet when the remaining offline times are lower than a first preset threshold, where the remote server is configured to implement management of digital assets in the hardware wallet;
the first information updating module 607 is configured to write the transaction information corresponding to the payment request into the hardware wallet.
In one embodiment, the first data synchronization module 605 is specifically configured to: obtaining balance voucher and transaction flow data from the hardware wallet; uploading a balance voucher and transaction flow data corresponding to the hardware wallet to a remote server; acquiring currency string data fed back by the remote server according to the balance voucher and the transaction running data; and writing the currency string data into the hardware wallet to reset the offline times of the hardware wallet.
In one embodiment, the system further comprises a prompt information pushing module, configured to: and when the hardware wallet and the remote server are synchronized, pushing user prompt information corresponding to the synchronization operation.
In one embodiment, the first information updating module 607 is specifically configured to: obtaining payment delay corresponding to the payment request; when the operation time of the synchronous operation exceeds the payment delay, pushing the re-brushing prompt information after the synchronous operation is finished; acquiring a payment refreshing request submitted by the hardware wallet according to the refreshing prompt information; and writing the transaction information corresponding to the payment re-swiping request into the hardware wallet.
In one embodiment, the present application further provides another hardware wallet data synchronization apparatus, including:
and the second request acquisition module is used for acquiring the payment request of the hardware wallet.
And the second data acquisition module is used for acquiring the remaining offline times corresponding to the hardware wallet according to the payment request.
And the second information updating module is used for writing the transaction information corresponding to the payment request into the hardware wallet when the remaining offline times are not zero.
And the second data synchronization module is used for synchronizing the data in the hardware wallet with a remote server to reset the offline times of the hardware wallet when the remaining offline times are lower than a second preset threshold, and the remote server is used for realizing management of the digital assets in the hardware wallet.
The various modules in the hardware wallet data synchronizing device may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 7. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program when executed by a processor implements a hardware wallet data synchronization method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 7 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
acquiring a payment request of a hardware wallet;
acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
when the remaining offline times are lower than a first preset threshold value, synchronizing data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing management of digital assets in the hardware wallet;
and writing the transaction information corresponding to the payment request into the hardware wallet.
In one embodiment, the processor, when executing the computer program, further performs the steps of: obtaining balance voucher and transaction flow data from the hardware wallet; uploading a balance voucher and transaction flow data corresponding to the hardware wallet to a remote server; acquiring currency string data fed back by the remote server according to the balance voucher and the transaction running data; and writing the currency string data into the hardware wallet to reset the offline times of the hardware wallet.
In one embodiment, the processor, when executing the computer program, further performs the steps of: and when the hardware wallet and the remote server are synchronized, pushing user prompt information corresponding to the synchronization operation.
In one embodiment, the processor, when executing the computer program, further performs the steps of: obtaining payment delay corresponding to the payment request; when the operation time of the synchronous operation exceeds the payment delay, pushing the re-brushing prompt information after the synchronous operation is finished; acquiring a payment refreshing request submitted by the hardware wallet according to the refreshing prompt information; and writing the transaction information corresponding to the payment re-swiping request into the hardware wallet.
In one embodiment, another computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
acquiring a payment request of a hardware wallet;
acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
when the remaining offline times are not zero, writing the transaction information corresponding to the payment request into the hardware wallet;
and when the remaining offline times are lower than a second preset threshold value, synchronizing the data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing the management of the digital assets in the hardware wallet.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
acquiring a payment request of a hardware wallet;
acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
when the remaining offline times are lower than a first preset threshold value, synchronizing data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing management of digital assets in the hardware wallet;
and writing the transaction information corresponding to the payment request into the hardware wallet.
In one embodiment, the computer program when executed by the processor further performs the steps of: obtaining balance voucher and transaction flow data from the hardware wallet; uploading a balance voucher and transaction flow data corresponding to the hardware wallet to a remote server; acquiring currency string data fed back by the remote server according to the balance voucher and the transaction running data; and writing the currency string data into the hardware wallet to reset the offline times of the hardware wallet.
In one embodiment, the computer program when executed by the processor further performs the steps of: and when the hardware wallet and the remote server are synchronized, pushing user prompt information corresponding to the synchronization operation.
In one embodiment, the computer program when executed by the processor further performs the steps of: obtaining payment delay corresponding to the payment request; when the operation time of the synchronous operation exceeds the payment delay, pushing the re-brushing prompt information after the synchronous operation is finished; acquiring a payment refreshing request submitted by the hardware wallet according to the refreshing prompt information; and writing the transaction information corresponding to the payment re-swiping request into the hardware wallet.
In one embodiment, another computer-readable storage medium is provided, having a computer program stored thereon, the computer program, when executed by a processor, implementing the steps of:
acquiring a payment request of a hardware wallet;
acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
when the remaining offline times are not zero, writing the transaction information corresponding to the payment request into the hardware wallet;
and when the remaining offline times are lower than a second preset threshold value, synchronizing the data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing the management of the digital assets in the hardware wallet.
In one embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, performs the steps of:
acquiring a payment request of a hardware wallet;
after transaction information corresponding to the payment request is written into the automatically updated hardware wallet, acquiring the remaining offline times corresponding to the hardware wallet;
and when the remaining offline times corresponding to the hardware wallet are lower than a second preset threshold value, performing automatic synchronization operation on the hardware wallet to update the offline times of the hardware wallet.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
acquiring a payment request of a hardware wallet;
acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
when the remaining offline times are lower than a first preset threshold value, synchronizing data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing management of digital assets in the hardware wallet;
and writing the transaction information corresponding to the payment request into the hardware wallet.
In one embodiment, the computer program when executed by the processor further performs the steps of: obtaining balance voucher and transaction flow data from the hardware wallet; uploading a balance voucher and transaction flow data corresponding to the hardware wallet to a remote server; acquiring currency string data fed back by the remote server according to the balance voucher and the transaction running data; and writing the currency string data into the hardware wallet to reset the offline times of the hardware wallet.
In one embodiment, the computer program when executed by the processor further performs the steps of: and when the hardware wallet and the remote server are synchronized, pushing user prompt information corresponding to the synchronization operation.
In one embodiment, the computer program when executed by the processor further performs the steps of: obtaining payment delay corresponding to the payment request; when the operation time of the synchronous operation exceeds the payment delay, pushing the re-brushing prompt information after the synchronous operation is finished; acquiring a payment refreshing request submitted by the hardware wallet according to the refreshing prompt information; and writing the transaction information corresponding to the payment re-swiping request into the hardware wallet.
In one embodiment, another computer program product is provided, comprising a computer program which, when executed by a processor, performs the steps of:
acquiring a payment request of a hardware wallet;
acquiring the remaining offline times corresponding to the hardware wallet according to the payment request;
when the remaining offline times are not zero, writing the transaction information corresponding to the payment request into the hardware wallet;
and when the remaining offline times are lower than a second preset threshold value, synchronizing the data in the hardware wallet with a remote server to reset the offline times of the hardware wallet, wherein the remote server is used for realizing the management of the digital assets in the hardware wallet.
It should be noted that, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware related to instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high-density embedded nonvolatile Memory, resistive Random Access Memory (ReRAM), Magnetic Random Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (PCM), graphene Memory, and the like. Volatile Memory can include Random Access Memory (RAM), external cache Memory, and the like. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others. The databases referred to in various embodiments provided herein may include at least one of relational and non-relational databases. The non-relational database may include, but is not limited to, a block chain based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing based data processing logic devices, etc., without limitation.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above examples only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.