Transaction method and device based on red envelope and electronic equipment

Abstract

The invention discloses a transaction method and device based on a red envelope and electronic equipment, and relates to the technical field of digital currency. A specific embodiment of the method comprises the following steps: receiving a transaction request sent by a point-of-sale terminal, wherein the transaction request carries a transaction amount, a wallet number of a payee and a wallet number of a payer; querying and acquiring a red envelope account associated with a hard wallet of the payer according to the wallet number of the payer, wherein the red envelope account is used for receiving a red envelope; and in response to the fact that the transaction request is matched with the use rule of the red envelope, paying digital currency corresponding to the transaction amount to the wallet corresponding to the wallet number of the payee based on the wallet corresponding to the wallet number of the payer and the red envelope account. According to the embodiment, the technical problem that existing red envelope processing logic cannot meet market requirements can be solved.

Description

Technical Field

[0001] The present invention relates to the field of digital currency technology, and in particular to a red envelope-based transaction method, device, electronic device and computer-readable medium. Background Art

[0002] With the promotion of digital currency hard wallets, the existing red envelope processing logic can no longer meet market demand. Specifically, the hard wallet has the following technical problems in the process of receiving, viewing and using red envelopes:

[0003] (1) There is a lack of red envelope solutions based on hard wallets on the market, including the issuance of red envelopes to hard wallets, the inheritance of red envelopes from parent wallets by hard wallets, and the use and recycling of corresponding red envelopes.

[0004] (2) The hardware wallets on the market lack flexibility and convenience in issuing, using and viewing red envelopes. For example, red envelopes need to be written into hardware to enable red envelope issuance and use. When making payments, the hardware wallet cannot obtain red envelopes on the red envelope management platform in real time, and users cannot view the red envelopes in the hardware wallet in real time, resulting in a lack of convenience. Summary of the invention

[0005] In view of this, an embodiment of the present invention provides a red envelope-based transaction method, device, electronic device and computer-readable medium to solve the technical problem that the existing red envelope processing logic can no longer meet market demand.

[0006] To achieve the above object, according to one aspect of an embodiment of the present invention, a transaction method based on red envelopes is provided, wherein the red envelopes are digital currencies with usage rules attached, and the method comprises:

[0007] Receive a transaction request sent by a sales terminal, the transaction request carrying a transaction amount, a wallet number of a payee, and a wallet number of a payee;

[0008] Querying and acquiring a red envelope account associated with the payer's hard wallet according to the payer's wallet number, wherein the red envelope account is used to receive red envelopes;

[0009] In response to the transaction request matching the usage rules of the red envelope, based on the wallet corresponding to the wallet number of the payee and the red envelope account, the digital currency corresponding to the transaction amount is paid to the wallet corresponding to the wallet number of the payee.

[0010] Optionally, before receiving the transaction request sent by the sales terminal, the method further includes:

[0011] Determine whether to send a red envelope to the red envelope account associated with the payer's hard wallet via the mobile phone number;

[0012] If yes, the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payer's hard wallet;

[0013] If not, the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payee's hard wallet through the hard wallet number.

[0014] Optionally, the red envelope is distributed from the red envelope account of the investor to the red envelope account associated with the hard wallet of the payer, including:

[0015] Determine whether the payer has opened a soft wallet;

[0016] If yes, the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payer's hard wallet;

[0017] If not, the payee is guided to open a soft wallet in the digital currency application and bind the soft wallet to the payee's hard wallet, and the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payee's hard wallet.

[0018] Optionally, in response to the transaction request matching the usage rule of the red envelope, paying the digital currency corresponding to the transaction amount to the wallet corresponding to the wallet number of the payee based on the wallet corresponding to the wallet number of the payee and the red envelope account, comprises:

[0019] Determining whether there is a red envelope in the red envelope account whose usage rules match the transaction request;

[0020] If so, the red envelope is transferred from the red envelope account to the wallet corresponding to the wallet number of the payee, and / or the wallet balance is transferred from the payer's hard wallet or the soft wallet bound to the hard wallet to the wallet corresponding to the payee's wallet number to pay the digital currency corresponding to the transaction amount;

[0021] If not, the wallet balance is transferred from the payer's hard wallet or the soft wallet bound to the hard wallet to the wallet corresponding to the payee's wallet number to pay the digital currency corresponding to the transaction amount.

[0022] Optionally, the transaction request is generated based on a hardware wallet trigger of the payer or is generated based on a soft wallet trigger of the payer.

[0023] Optionally, querying and obtaining a red envelope account associated with the payer's hard wallet according to the payer's wallet number includes:

[0024] Determine whether the wallet number of the payer is a hard wallet number;

[0025] If yes, query and obtain the red envelope account associated with the payer's hard wallet according to the payer's hard wallet number;

[0026] If not, query and obtain the hard wallet bound to the soft wallet according to the soft wallet number of the payer, and then query and obtain the red envelope account associated with the hard wallet according to the hard wallet number.

[0027] Optionally, the method further comprises:

[0028] Receiving a refund request sent by the sales terminal, the refund request carrying a refund amount, a wallet number of the refunding party, and a wallet number of the payer;

[0029] Determine whether the payment method of the transaction corresponding to the refund request is a combination of red envelope and wallet balance;

[0030] If yes, the red envelope is returned from the refunder's wallet to the payer's red envelope account, and / or the wallet balance is returned from the refunder's wallet to the payer's hard wallet or a soft wallet bound to the hard wallet;

[0031] If not, the red envelope will be returned to the payer's red envelope account.

[0032] Optionally, returning the red envelope from the wallet of the refunding party to the red envelope account of the paying party includes:

[0033] Determine whether the red envelope returned from the wallet of the refunder to the red envelope account of the payer has expired;

[0034] If not, the red envelope is returned to the red envelope account of the payer;

[0035] If so, the red envelope will be returned to the red envelope account of the investor, or the red envelope will be returned to the red envelope account of the payer and the validity period of the red envelope will be extended.

[0036] Optionally, returning the red envelope to the red envelope account of the payer includes:

[0037] Determine whether the red envelope is a red envelope dedicated to a hard wallet;

[0038] If yes, determine whether the payer's hard wallet is cancelled; if no, return the red envelope to the payer's red envelope account; if yes, return the red envelope to the investor's red envelope account;

[0039] If not, determine whether the payer's soft wallet is cancelled; if not, return the red envelope to the payer's red envelope account; if so, return the red envelope to the investor's red envelope account.

[0040] In addition, according to another aspect of an embodiment of the present invention, a transaction device based on a red envelope is provided, wherein the red envelope is a digital currency with usage rules attached, and the device comprises:

[0041] A receiving module, used to receive a transaction request sent by a sales terminal, wherein the transaction request carries a transaction amount, a wallet number of a payee, and a wallet number of a payee;

[0042] A query module, used to query and obtain a red envelope account associated with the payer's hard wallet according to the payer's wallet number, wherein the red envelope account is used to receive red envelopes;

[0043] A processing module is used to pay the digital currency corresponding to the transaction amount to the wallet corresponding to the wallet number of the payee based on the wallet corresponding to the wallet number of the payee and the red envelope account in response to the transaction request matching the usage rules of the red envelope.

[0044] Optionally, the device further comprises a distribution module, configured to:

[0045] Determine whether to send a red envelope to the red envelope account associated with the payer's hard wallet via the mobile phone number;

[0046] If yes, the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payer's hard wallet;

[0047] If not, the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payee's hard wallet through the hard wallet number.

[0048] Optionally, the issuing module is further used for:

[0049] Determine whether the payer has opened a soft wallet;

[0050] If yes, the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payer's hard wallet;

[0051] If not, the payee is guided to open a soft wallet in the digital currency application and bind the soft wallet to the payee's hard wallet, and the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payee's hard wallet.

[0052] Optionally, the processing module is further used for:

[0053] Determining whether there is a red envelope in the red envelope account whose usage rules match the transaction request;

[0054] If so, the red envelope is transferred from the red envelope account to the wallet corresponding to the wallet number of the payee, and / or the wallet balance is transferred from the payer's hard wallet or the soft wallet bound to the hard wallet to the wallet corresponding to the payee's wallet number to pay the digital currency corresponding to the transaction amount;

[0055] If not, the wallet balance is transferred from the payer's hard wallet or the soft wallet bound to the hard wallet to the wallet corresponding to the payee's wallet number to pay the digital currency corresponding to the transaction amount.

[0056] Optionally, the transaction request is generated based on a hardware wallet trigger of the payer or is generated based on a soft wallet trigger of the payer.

[0057] Optionally, the query module is further used to:

[0058] Determine whether the wallet number of the payer is a hard wallet number;

[0059] If yes, query and obtain the red envelope account associated with the payer's hard wallet according to the payer's hard wallet number;

[0060] If not, query and obtain the hard wallet bound to the soft wallet according to the soft wallet number of the payer, and then query and obtain the red envelope account associated with the hard wallet according to the hard wallet number.

[0061] Optionally, the processing module is further used for:

[0062] Receiving a refund request sent by the sales terminal, the refund request carrying a refund amount, a wallet number of the refunding party, and a wallet number of the payer;

[0063] Determine whether the payment method of the transaction corresponding to the refund request is a combination of red envelope and wallet balance;

[0064] If yes, the red envelope is returned from the refunder's wallet to the payer's red envelope account, and / or the wallet balance is returned from the refunder's wallet to the payer's hard wallet or a soft wallet bound to the hard wallet;

[0065] If not, the red envelope will be returned to the payer's red envelope account.

[0066] Optionally, the processing module is further used for:

[0067] Determine whether the red envelope returned from the wallet of the refunder to the red envelope account of the payer has expired;

[0068] If not, the red envelope is returned to the red envelope account of the payer;

[0069] If so, the red envelope will be returned to the red envelope account of the investor, or the red envelope will be returned to the red envelope account of the payer and the validity period of the red envelope will be extended.

[0070] Optionally, the processing module is further used for:

[0071] Determine whether the red envelope is a red envelope dedicated to a hard wallet;

[0072] If yes, determine whether the payer's hard wallet is cancelled; if no, return the red envelope to the payer's red envelope account; if yes, return the red envelope to the investor's red envelope account;

[0073] If not, determine whether the payer's soft wallet is cancelled; if not, return the red envelope to the payer's red envelope account; if so, return the red envelope to the investor's red envelope account.

[0074] According to another aspect of an embodiment of the present invention, there is further provided an electronic device, including:

[0075] one or more processors;

[0076] a storage device for storing one or more programs,

[0077] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any one of the above embodiments.

[0078] According to another aspect of an embodiment of the present invention, a computer-readable medium is provided, on which a computer program is stored. When the program is executed by a processor, the method described in any one of the above embodiments is implemented.

[0079] According to another aspect of an embodiment of the present invention, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the method described in any one of the above embodiments is implemented.

[0080] One embodiment of the above invention has the following advantages or beneficial effects: because the red envelope account associated with the payee's hard wallet is queried and obtained according to the payee's wallet number, in response to the transaction request matching the red envelope usage rules, the digital currency corresponding to the transaction amount is paid to the wallet corresponding to the payee's wallet number based on the wallet and red envelope account corresponding to the payee's wallet number, thus overcoming the technical problem that the existing red envelope processing logic in the prior art can no longer meet market demand. The embodiment of the present invention enables the digital currency hard wallet to have the ability to use red envelopes, and the digital wallet operator can query the red envelope usage in real time when the hard wallet is paid, so as to realize the use of red envelopes by the hard wallet, and basically reach the same level as the marketing capability of the soft wallet, so that the use experience of the hard wallet and the soft wallet are aligned.

[0081] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with specific implementation examples. BRIEF DESCRIPTION OF THE DRAWINGS

[0082] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art descriptions. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. Among them:

[0083] Figure 1 is a flow chart of a red envelope-based transaction method according to a first embodiment of the present invention;

[0084] Figure 2 is a flow chart of a red envelope-based transaction method according to a second embodiment of the present invention;

[0085] Figure 3 is a flow chart of a red envelope-based transaction method according to a third embodiment of the present invention;

[0086] Figure 4 is a flow chart of a red envelope-based transaction method according to a fourth embodiment of the present invention;

[0087] Figure 5 is a flow chart of a red envelope-based transaction method according to a fifth embodiment of the present invention;

[0088] Figure 6 is a schematic diagram of a red envelope-based transaction device according to an embodiment of the present invention;

[0089] Figure 7 is an exemplary system architecture diagram to which embodiments of the present invention may be applied;

[0090] Figure 8It is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0091] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0092] It should be noted that the collection, collection, updating, analysis, processing, use, transmission, storage and other aspects of user personal information involved in the technical solution of this disclosure are in compliance with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken for user personal information to prevent illegal access to user personal information data and maintain the security of user personal information, network security and national security.

[0093] Figure 1 is a flow chart of a red envelope-based transaction method according to a first embodiment of the present invention. As an embodiment of the present invention, Figure 1 As shown, the red envelope-based transaction method is applied to a digital wallet operating institution and may include:

[0094] Step 101, receiving a transaction request sent by a sales terminal, wherein the transaction request carries a transaction amount, a wallet number of a payee, and a wallet number of a payee.

[0095] Optionally, the transaction request is triggered based on the payer's hard wallet or based on the payer's soft wallet. Specifically, the payer uses the corresponding hard wallet to pay according to the usage rules and conditions displayed on the red envelope details page. For example, the payer uses a hard wallet (such as a mobile phone, SIM card, bank card, or smart device such as a wearable device) to conduct a transaction with a sales terminal (such as a POS machine) by touching it, and the sales terminal sends a transaction request to the digital wallet operator, and the transaction request carries the transaction amount, the payee's wallet number, and the payer's hard wallet number. Alternatively, the payer conducts a transaction with the sales terminal through a soft wallet, and the sales terminal sends a transaction request to the digital wallet operator, and the transaction request carries the transaction amount, the payee's wallet number, and the payer's soft wallet number.

[0096] After receiving the transaction request sent by the sales terminal, the digital wallet operator parses it to obtain the transaction amount, the wallet number of the payee and the wallet number of the payee carried in the transaction request.

[0097] Step 102, querying and acquiring a red envelope account associated with the payee's hard wallet according to the payee's wallet number, wherein the red envelope account is used to receive red envelopes;

[0098] After the digital wallet operator parses the transaction amount, the wallet number of the payee and the wallet number of the payee carried in the transaction request, it searches and obtains the red envelope account associated with the payer's hard wallet according to the payer's wallet number. Optionally, step 102 may include: determining whether the payer's wallet number is a hard wallet number; if so, searching and obtaining the red envelope account associated with the payer's hard wallet according to the payer's hard wallet number; if not, searching and obtaining the hard wallet bound to the soft wallet according to the payer's soft wallet number, and then searching and obtaining the red envelope account associated with the hard wallet according to the hard wallet number. In an embodiment of the present invention, the red envelope account associated with the payer's hard wallet can be queried and obtained through the hard wallet number. Therefore, it is first determined whether the wallet number of the payer carried in the transaction request is a hard wallet number or a soft wallet number. If it is a hard wallet number, the red envelope account associated with the payer's hard wallet is directly queried and obtained according to the hard wallet number. If it is a soft wallet number, the hard wallet bound to the soft wallet is first queried and obtained according to the soft wallet number, and then the red envelope account associated with the hard wallet is queried and obtained according to the hard wallet number.

[0099] It should be noted that if a soft wallet is bound to a hard wallet, the soft wallet is the parent wallet of the hard wallet. In other words, the hard wallet can be bound to the soft wallet, that is, the soft wallet is the parent wallet and the hard wallet is the child wallet, and the two are in a parent-child relationship.

[0100] Step 103, in response to the transaction request matching the usage rules of the red envelope, based on the wallet corresponding to the wallet number of the payee and the red envelope account, pay the digital currency corresponding to the transaction amount to the wallet corresponding to the wallet number of the payee.

[0101] In this step, the digital wallet operator responds to the transaction request matching the usage rules of the red envelope, and pays the digital currency corresponding to the transaction amount to the wallet corresponding to the wallet number of the payee based on the wallet corresponding to the wallet number of the payee and the red envelope account.

[0102] In an embodiment of the present invention, the payer does not need to manually select which red envelope to use and the amount to use (the specific restrictions are set by the digital wallet operator or the investor). The digital wallet operator deducts the money according to the red envelopes available in the payer's red envelope account and deducts it in the set order. When the payer makes a payment, the red envelopes that are close to the expiration date and available are silently deducted first. If the total amount of the deducted red envelopes is less than the transaction amount, the wallet balance is deducted. Therefore, when the total amount of red envelopes that can be used is greater than or equal to the transaction amount, the red envelope payment method is adopted. When the total amount of red envelopes that can be used is less than the transaction amount, the red envelope and wallet balance combination payment method is adopted.

[0103] Optionally, step 103 may include: determining whether there is a red envelope in the red envelope account whose usage rules match the transaction request; if so, transferring the red envelope from the red envelope account to the wallet corresponding to the wallet number of the payee, and / or transferring the wallet balance from the payee's hard wallet or the soft wallet bound to the hard wallet to the wallet corresponding to the payee's wallet number to pay the digital currency corresponding to the transaction amount; if not, transferring the wallet balance from the payee's hard wallet or the soft wallet bound to the hard wallet to the wallet corresponding to the payee's wallet number to pay the digital currency corresponding to the transaction amount. In this step, it is first determined whether there is a red envelope in the payer's red envelope account whose usage rules match the transaction request. If so, the matching red envelope is transferred from the payer's red envelope account to the payee's wallet (which can be the payee's red envelope account). If the total amount of the deducted red envelopes is less than the transaction amount, the wallet balance of the hard wallet or soft wallet is deducted; if not, the wallet balance is transferred from the payer's hard wallet or soft wallet to the payee's wallet (which can be a soft wallet or a hard wallet).

[0104] It should be noted that if it is a hard wallet in account mode, the wallet balance will be transferred from the payer's soft wallet to the payee's wallet. If it is a hard wallet in quasi-account mode, the wallet balance will be transferred from the payer's hard wallet to the payee's wallet.

[0105] If the red envelope is not used when it expires, it will be returned from the payer's red envelope account to the investor's red envelope account when it expires.

[0106] According to the various embodiments described above, it can be seen that the embodiments of the present invention solve the technical problem that the existing red envelope processing logic in the prior art cannot meet market demand by querying and obtaining the red envelope account associated with the payee's hard wallet according to the payee's wallet number, responding to the transaction request and matching the red envelope usage rules, and paying the digital currency corresponding to the transaction amount to the wallet corresponding to the payee's wallet number based on the wallet and red envelope account corresponding to the payee's wallet number. The embodiments of the present invention enable the digital currency hard wallet to have the ability to use red envelopes, and the digital wallet operator can query the red envelope usage in real time when the hard wallet is paid, so as to realize the use of red envelopes by the hard wallet, and basically reach the same level as the marketing ability of the soft wallet, so that the use experience of the hard wallet and the soft wallet are aligned.

[0107] Figure 2 is a flow chart of a red envelope-based transaction method according to a second embodiment of the present invention. As another embodiment of the present invention, Figure 2 As shown, the red envelope-based transaction method may include:

[0108] Step 201, distribute the red envelope to the payer's red envelope account.

[0109] First, the digital wallet operator issues the red envelope to the payee's red envelope account. For example, the digital wallet operator issues the red envelope to the payee's red envelope account through the mobile phone number or the hard wallet number, and the red envelope is received as soon as it is issued, so the payee does not need to manually receive it again. Among them, the digital wallet operator can be the investor or not, and the embodiment of the present invention does not limit this.

[0110] Optionally, step 201 may include: determining whether to issue a red envelope to a red envelope account associated with the payee's hard wallet through a mobile phone number; if so, issuing the red envelope from the investor's red envelope account to the red envelope account associated with the payee's hard wallet; if not, issuing the red envelope from the investor's red envelope account to the red envelope account associated with the payee's hard wallet through the hard wallet number. The digital wallet operator may pre-configure the red envelope issuance method, such as issuing through a mobile phone number or issuing through a hard wallet number. When issuing a red envelope, the digital wallet operator reads the red envelope issuance method, determines whether to issue a red envelope to a red envelope account associated with the payee's hard wallet through a mobile phone number, and if so, issues the red envelope from the investor's red envelope account to the red envelope account associated with the payee's hard wallet. If not, the red envelope is issued from the investor's red envelope account to the red envelope account associated with the payee's hard wallet through the hard wallet number, and the issuance is the same as the receipt.

[0111] Since the soft wallet is bound to the hard wallet, if a red envelope is sent via a mobile phone number to a red envelope account associated with the payer's hard wallet, the soft wallet associated with the mobile phone number is first queried and obtained based on the mobile phone number, and then the hard wallet bound to the soft wallet is queried and obtained through the soft wallet, and finally the red envelope account associated with the hard wallet is queried and obtained based on the hard wallet.

[0112] The red envelope is issued from the red envelope account of the investor to the red envelope account associated with the hard wallet of the payee, including: judging whether the payee has opened a soft wallet; if so, issuing the red envelope from the red envelope account of the investor to the red envelope account associated with the hard wallet of the payee; if not, guiding the payee to open a soft wallet in the digital currency application and bind the soft wallet with the hard wallet of the payee, and issuing the red envelope from the red envelope account of the investor to the red envelope account associated with the hard wallet of the payee. If the payee has not opened a soft wallet of the digital wallet operator, it is necessary to first guide the payee to open a soft wallet in the digital currency APP, and automatically receive the issued red envelope after the soft wallet is bound to the hard wallet. The opening of the soft wallet requires the payee to provide a mobile phone number, and the mobile phone number is bound to the soft wallet. If the payee has opened a soft wallet in the digital currency APP, when issuing a red envelope through the mobile phone number, the red envelope is issued from the red envelope account of the investor to the red envelope account associated with the hard wallet of the payee.

[0113] The digital wallet operator can also configure the usage rules of the red envelopes, including but not limited to: available merchants, usage period, transaction amount, wallet mode (such as account mode hard wallet, quasi-account mode hard wallet, etc.), media type (such as SIM card, mobile phone PAY, etc.), designated hard wallet (such as designated wallet number), designated mobile phone number, whether the hard wallet is dedicated, etc. The digital wallet operator can configure one or more usage rules for the red envelopes. The red envelopes under the hard wallet have the ability to combine multiple usage rules. The digital wallet operator can restrict the usage rules of the red envelopes from different dimensions, such as combining restrictions on the use media and available merchants of the red envelopes, and the red envelopes that are not used after the expiration date can be automatically returned to the investor. It should be noted that the embodiments of the present invention are applicable to account mode hard wallets or quasi-account mode hard wallets.

[0114] Optionally, the method further includes: receiving a red envelope query request sent by a terminal, the red envelope query request carrying a mobile phone number or a soft wallet number; returning each red envelope in the red envelope account to the terminal; wherein the red envelope is issued via a mobile phone number; or, receiving a red envelope query request sent by a terminal, the red envelope query request carrying a soft wallet number or a hard wallet number; returning each red envelope in the red envelope account to the terminal; wherein the soft wallet is the parent wallet of the hard wallet, and the red envelope is issued via the hard wallet number. The hard wallet can be bound to the soft wallet, that is, the soft wallet is the parent wallet and the hard wallet is the child wallet, and the two are in a parent-child relationship.

[0115] In some embodiments of the present invention, for red envelopes issued to a red envelope account via a mobile phone number, the payee can use the mobile phone number or the soft wallet number to query each red envelope in the red envelope account. In other embodiments of the present invention, for red envelopes issued to a red envelope account via a hard wallet number, the payee can query each red envelope under the red envelope account via the hard wallet number or the soft wallet number of the hard wallet (the two are parent-child relationships), but cannot query each red envelope under the red envelope account via the mobile phone number. Red envelopes issued via hard wallet numbers have the ability to be issued and received, and it is possible to view the received hard wallet red envelopes in the soft wallet to which they belong, which makes the issuance, receipt and viewing of hard wallet red envelopes flexible and convenient. It should be noted that a hard wallet that is not bound to a soft wallet can only query the red envelopes in the red envelope account via the hard wallet number.

[0116] Step 202, receiving a transaction request sent by a sales terminal, wherein the transaction request carries a transaction amount, a wallet number of a payee, and a wallet number of a payee.

[0117] Optionally, the transaction request is triggered based on the payer's hard wallet or based on the payer's soft wallet. Specifically, the payer uses the corresponding hard wallet to pay according to the usage rules and conditions displayed on the red envelope details page. For example, the payer uses a hard wallet (such as a mobile phone, SIM card, bank card, or smart device such as a wearable device) to conduct a transaction with a sales terminal (such as a POS machine) by touching it, and the sales terminal sends a transaction request to the digital wallet operator, and the transaction request carries the transaction amount, the payee's wallet number, and the payer's hard wallet number. Alternatively, the payer conducts a transaction with the sales terminal through a soft wallet, and the sales terminal sends a transaction request to the digital wallet operator, and the transaction request carries the transaction amount, the payee's wallet number, and the payer's soft wallet number.

[0118] After receiving the transaction request sent by the sales terminal, the digital wallet operator parses it to obtain the transaction amount, the wallet number of the payee and the wallet number of the payee carried in the transaction request.

[0119] Step 203, determining whether the wallet number of the payer is a hard wallet number; if so, executing step 204; if not, executing step 205.

[0120] Step 204: query and obtain the red envelope account associated with the payer's hard wallet according to the payer's hard wallet number.

[0121] If the wallet number of the payer carried in the transaction request is a hard wallet number, the red envelope account associated with the payer's hard wallet is directly queried and obtained based on the payer's hard wallet number.

[0122] Step 205, query and obtain the hard wallet bound to the soft wallet according to the soft wallet number of the payer, and then query and obtain the red envelope account associated with the hard wallet according to the hard wallet number.

[0123] If the wallet number of the payer carried in the transaction request is a soft wallet number, the hard wallet bound to the soft wallet is first queried and obtained according to the soft wallet number of the payer, indicating that the soft wallet is the parent wallet of the hard wallet, and then the red envelope account associated with the hard wallet is queried and obtained according to the hard wallet number.

[0124] Step 206, in response to the transaction request matching the usage rules of the red envelope, based on the wallet corresponding to the payee's wallet number and the red envelope account, pay the digital currency corresponding to the transaction amount to the wallet corresponding to the payee's wallet number.

[0125] In this step, the digital wallet operator responds to the transaction request matching the usage rules of the red envelope, and pays the digital currency corresponding to the transaction amount to the wallet corresponding to the wallet number of the payee based on the wallet corresponding to the wallet number of the payee and the red envelope account.

[0126] In an embodiment of the present invention, the payer does not need to manually select which red envelope to use and the amount to use (the specific restrictions are set by the digital wallet operator or the investor). The digital wallet operator deducts the money according to the red envelopes available in the payer's red envelope account and deducts it in the set order. When the payer makes a payment, the red envelopes that are close to the expiration date and available are silently deducted first. If the total amount of the deducted red envelopes is less than the transaction amount, the wallet balance is deducted. Therefore, when the total amount of red envelopes that can be used is greater than or equal to the transaction amount, the red envelope payment method is adopted. When the total amount of red envelopes that can be used is less than the transaction amount, the red envelope and wallet balance combination payment method is adopted.

[0127] The red envelopes issued through the hard wallet number are both specific and extensible. The hard wallet and the soft wallet are in a parent-child relationship, so the red envelopes are both specific and extensible. That is, although the red envelopes are issued through the hard wallet number, they are not limited to use in the hard wallet after receiving them. The parent wallet can also use them, and hard wallets of other media types under the parent wallet are also applicable.

[0128] The embodiments of the present invention enable digital currency hard wallets to have the ability to use red envelopes. Digital wallet operators can query the use of red envelopes in real time when paying with the hard wallet, thereby enabling the hard wallet to use red envelopes and basically achieving the same level of marketing capabilities as soft wallets, thereby aligning the usage experience of hard wallets and soft wallets.

[0129] Figure 3 is a flow chart of a red envelope-based transaction method according to a third embodiment of the present invention. As another embodiment of the present invention, Figure 3 As shown, the red envelope-based transaction method may include:

[0130] Step 301, receiving a transaction request sent by a sales terminal, wherein the transaction request carries a transaction amount, a wallet number of a payee, and a wallet number of a payee.

[0131] Step 302: query and obtain a red envelope account associated with the payee's hard wallet according to the payee's wallet number, wherein the red envelope account is used to receive red envelopes.

[0132] Step 303, in response to the transaction request matching the usage rules of the red envelope, based on the wallet corresponding to the wallet number of the payee and the red envelope account, pay the digital currency corresponding to the transaction amount to the wallet corresponding to the wallet number of the payee.

[0133] Steps 301 to 302 in the third embodiment are similar to steps 101 to 103 in the first embodiment, and are not described in detail.

[0134] Step 304: Receive a refund request sent by the sales terminal, where the refund request carries the refund amount, the wallet number of the refunder, and the wallet number of the payer.

[0135] Step 305 , determining whether the payment method of the transaction corresponding to the refund request is a combination of red envelope and wallet balance; if so, executing step 306 ; if not, executing step 307 .

[0136] Step 306: Return the red envelope from the refunder's wallet to the payer's red envelope account, and / or return the wallet balance from the refunder's wallet to the payer's hard wallet or a soft wallet bound to the hard wallet.

[0137] Step 307: Return the red envelope to the payer's red envelope account.

[0138] In an embodiment of the present invention, the red envelope supports full refund and partial refund. The refund is based on the original refund principle, and the amount of the red envelope used is returned in the same amount. Optionally, the red envelope can be returned from the wallet of the refunder to the red envelope account of the payer.

[0139] If the payment method of the transaction corresponding to the refund request is a combination of red envelope and wallet balance, not only the red envelope needs to be returned, but also the wallet balance needs to be returned from the refunder's wallet to the payer's hard wallet or the soft wallet bound to the hard wallet. If the payment method of the transaction corresponding to the refund request is red envelope payment, then only the red envelope needs to be returned from the refunder's wallet to the payer's red envelope account.

[0140] Optionally, if the payment method of the transaction corresponding to the refund request is a combination of red envelope and wallet balance, the red envelope will first be refunded from the refunder's wallet to the payer's red envelope account. If the refund amount is greater than the total amount of the red envelope, the wallet balance will be refunded from the refunder's wallet to the payer's hard wallet or the soft wallet bound to the hard wallet.

[0141] In addition, the specific implementation content of the red envelope-based transaction method in a reference embodiment of the present invention has been described in detail in the red envelope-based transaction method described above, so the repeated content will not be described here.

[0142] Figure 4 4 is a flowchart of a red envelope-based transaction method according to a fourth embodiment of the present invention. As another embodiment of the present invention, this embodiment is similar to the third embodiment. In the fourth embodiment, Figure 4 As shown, the "returning the red envelope to the red envelope account of the payer" in step 307 may specifically include the following steps:

[0143] Step 401, determine whether the red envelope returned from the wallet of the refunder to the red envelope account of the payer is expired; if not, execute step 402; if yes, execute step 403.

[0144] Step 402: Return the red envelope to the payer's red envelope account.

[0145] Step 403: Return the red envelope to the red envelope account of the investor, or return the red envelope to the red envelope account of the payer and extend the validity period of the red envelope.

[0146] In a fourth embodiment, in the process of returning the red envelope from the refunding party's wallet to the payee's red envelope account, based on the usage period and the current time, it is determined whether the red envelope returned from the refunding party's wallet to the payee's red envelope account has expired. If the red envelope has not expired, the red envelope is returned to the payee's red envelope account; if the red envelope has expired, the red envelope is returned to the investor's red envelope account, or the red envelope is returned to the payee's red envelope account and the validity period of the red envelope is extended.

[0147] It should be noted that the investor or digital wallet operator can agree in advance on how to deal with expired red envelopes. If the purpose is to extend the validity period of the red envelopes, the length of the validity period can also be agreed upon.

[0148] In addition, the specific implementation content of the red envelope-based transaction method in a reference embodiment of the present invention has been described in detail in the red envelope-based transaction method described above, so the repeated content will not be described here.

[0149] Figure 5 is a flow chart of a red envelope-based transaction method according to a fifth embodiment of the present invention. As another embodiment of the present invention, this embodiment is similar to the second embodiment. In the fifth embodiment, Figure 5 As shown, the "returning the red envelope to the red envelope account of the payer" in step 307 may specifically include the following steps:

[0150] Step 401, determine whether the red envelope returned from the wallet of the refunder to the red envelope account of the payer is expired; if not, execute step 402; if yes, execute step 407.

[0151] Step 402, determine whether the red envelope is a red envelope dedicated to the hard wallet; if so, execute step 403; if not, execute step 406.

[0152] Step 403: Determine whether the payer's hard wallet is cancelled; if not, execute step 404; if yes, execute step 405.

[0153] Step 404: Return the red envelope to the payer's red envelope account.

[0154] Step 405: Return the red envelope to the red envelope account of the investor.

[0155] Step 406, determine whether the payer's soft wallet is cancelled; if not, execute step 404; if yes, execute step 405.

[0156] Step 407: Return the red envelope to the red envelope account of the investor, or return the red envelope to the red envelope account of the payer and extend the validity period of the red envelope.

[0157] In the fifth embodiment, in the process of returning the red envelope from the wallet of the refunder to the red envelope account of the payer, based on the usage period and the current time, it is determined whether the red envelope returned from the wallet of the refunder to the red envelope account of the payer has expired. If the red envelope has not expired, it is further determined whether the red envelope is a hard wallet-only red envelope. If the red envelope is a hard wallet-only red envelope, it is further determined whether the hard wallet of the payer has been cancelled. If the hard wallet has been cancelled, the red envelope is recovered, that is, the red envelope is returned to the red envelope account of the contributor. If the hard wallet has not been cancelled, the red envelope is returned to the red envelope account of the payer. If the red envelope is not a hard wallet-only red envelope, it is determined whether the soft wallet of the payer has been cancelled. If the soft wallet has been cancelled, the red envelope is recovered, that is, the red envelope is returned to the red envelope account of the contributor. If the soft wallet has not been cancelled, the red envelope is returned to the red envelope account of the payer.

[0158] If the red envelope has expired, the red envelope will be returned to the red envelope account of the investor, or the red envelope will be returned to the red envelope account of the payee and the validity period of the red envelope will be extended.

[0159] If the soft wallet is cancelled, all red envelopes in the soft wallet will be automatically returned to the investor's red envelope account without waiting for the red envelope expiration date; if the hard wallet is cancelled, the hard wallet-specific red envelopes will be automatically returned to the investor's red envelope account. However, unbinding the hard wallet from the parent wallet will not result in the recovery of the red envelopes.

[0160] Therefore, an embodiment of the present invention provides a transaction method based on red envelopes, which covers the restriction conditions, issuance, collection, viewing, use, refund, recycling and other functions of red envelopes, so that the usage experience of hard wallets and soft wallets is aligned.

[0161] In addition, the specific implementation content of the red envelope-based transaction method in a reference embodiment of the present invention has been described in detail in the red envelope-based transaction method described above, so the repeated content will not be described here.

[0162] Figure 6 Schematic diagram of a red envelope-based transaction device according to an embodiment of the present invention. Figure 6As shown, the red envelope-based transaction device 600 includes a receiving module 601, a query module 602 and a processing module 603; wherein the receiving module 601 is used to receive a transaction request sent by a sales terminal, and the transaction request carries a transaction amount, a wallet number of a payee and a wallet number of a payee; the query module 602 is used to query and obtain a red envelope account associated with the payee's hard wallet according to the payee's wallet number, wherein the red envelope account is used to receive red envelopes, and the red envelopes are digital currencies with usage rules; the processing module 603 is used to pay the digital currency corresponding to the transaction amount to the wallet corresponding to the payee's wallet number based on the wallet corresponding to the payee's wallet number and the red envelope account in response to the transaction request matching the red envelope usage rules.

[0163] Optionally, the device further comprises a distribution module, configured to:

[0164] Determine whether to send a red envelope to the red envelope account associated with the payer's hard wallet via the mobile phone number;

[0165] If yes, the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payer's hard wallet;

[0166] If not, the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payee's hard wallet through the hard wallet number.

[0167] Optionally, the issuing module is further used for:

[0168] Determine whether the payer has opened a soft wallet;

[0169] If yes, the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payer's hard wallet;

[0170] If not, the payee is guided to open a soft wallet in the digital currency application and bind the soft wallet to the payee's hard wallet, and the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payee's hard wallet.

[0171] Optionally, the processing module 603 is further used for:

[0172] Determining whether there is a red envelope in the red envelope account whose usage rules match the transaction request;

[0173] If so, the red envelope is transferred from the red envelope account to the wallet corresponding to the wallet number of the payee, and / or the wallet balance is transferred from the payer's hard wallet or the soft wallet bound to the hard wallet to the wallet corresponding to the payee's wallet number to pay the digital currency corresponding to the transaction amount;

[0174] If not, the wallet balance is transferred from the payer's hard wallet or the soft wallet bound to the hard wallet to the wallet corresponding to the payee's wallet number to pay the digital currency corresponding to the transaction amount.

[0175] Optionally, the transaction request is generated based on a hardware wallet trigger of the payer or is generated based on a soft wallet trigger of the payer.

[0176] Optionally, the query module 602 is further used to:

[0177] Determine whether the wallet number of the payer is a hard wallet number;

[0178] If yes, query and obtain the red envelope account associated with the payer's hard wallet according to the payer's hard wallet number;

[0179] If not, query and obtain the hard wallet bound to the soft wallet according to the soft wallet number of the payer, and then query and obtain the red envelope account associated with the hard wallet according to the hard wallet number.

[0180] Optionally, the processing module 603 is further used for:

[0181] Receiving a refund request sent by the sales terminal, the refund request carrying a refund amount, a wallet number of the refunding party, and a wallet number of the payer;

[0182] Determine whether the payment method of the transaction corresponding to the refund request is a combination of red envelope and wallet balance;

[0183] If yes, the red envelope is returned from the refunder's wallet to the payer's red envelope account, and / or the wallet balance is returned from the refunder's wallet to the payer's hard wallet or a soft wallet bound to the hard wallet;

[0184] If not, the red envelope will be returned to the payer's red envelope account.

[0185] Optionally, the processing module 603 is further used for:

[0186] Determine whether the red envelope returned from the wallet of the refunder to the red envelope account of the payer has expired;

[0187] If not, the red envelope is returned to the red envelope account of the payer;

[0188] If so, the red envelope will be returned to the red envelope account of the investor, or the red envelope will be returned to the red envelope account of the payer and the validity period of the red envelope will be extended.

[0189] Optionally, the processing module 603 is further used for:

[0190] Determine whether the red envelope is a red envelope dedicated to a hard wallet;

[0191] If yes, determine whether the payer's hard wallet is cancelled; if no, return the red envelope to the payer's red envelope account; if yes, return the red envelope to the investor's red envelope account;

[0192] If not, determine whether the payer's soft wallet is cancelled; if not, return the red envelope to the payer's red envelope account; if so, return the red envelope to the investor's red envelope account.

[0193] It should be noted that the specific implementation content of the red envelope-based transaction device described in the present invention has been described in detail in the red envelope-based transaction method described above, so the repeated content will not be described here.

[0194] Figure 7 An exemplary system architecture 700 is shown to which a red envelope-based transaction method or a red envelope-based transaction device according to an embodiment of the present invention can be applied.

[0195] like Figure 7 As shown, system architecture 700 may include terminal devices 701, 702, 703, network 704 and server 705. Network 704 is used to provide a medium for communication links between terminal devices 701, 702, 703 and server 705. Network 704 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0196] Users can use terminal devices 701, 702, and 703 to interact with server 705 through network 704 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 701, 702, and 703, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

[0197] The terminal devices 701 , 702 , and 703 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.

[0198] Server 705 may be a server that provides various services, such as a backend management server (only an example) that provides support for shopping websites browsed by users using terminal devices 701, 702, and 703. The backend management server may analyze and process received transaction requests, red envelope query requests, and other data, and feed back the processing results to the terminal device.

[0199] It should be noted that the red envelope-based transaction method provided in the embodiment of the present invention is generally executed by the server 705 , and accordingly, the red envelope-based transaction device is generally set in the server 705 .

[0200] It should be understood that Figure 7 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0201] Reference below Figure 8 , which shows a schematic diagram of the structure of a computer system 800 of a terminal device suitable for implementing an embodiment of the present invention. Figure 8 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0202] like Figure 8 As shown, the computer system 800 includes a central processing unit (CPU) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage part 808 into a random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the system 800 are also stored. The CPU 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0203] The following components are connected to the I / O interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, a modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed, so that a computer program read therefrom is installed into the storage section 808 as needed.

[0204] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 809, and / or installed from the removable medium 811. When the computer program is executed by the central processing unit (CPU) 801, the above-mentioned functions defined in the system of the present invention are executed.

[0205] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0206] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0207] The modules involved in the embodiments of the present invention may be implemented by software or hardware. The modules described may also be set in a processor, for example, it may be described as: a processor includes a receiving module, a query module and a processing module, wherein the names of these modules do not constitute a limitation on the modules themselves in some cases.

[0208] As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently and not be assembled into the device. The above computer-readable medium carries one or more programs. When the above one or more programs are executed by a device, the device implements the following method: receiving a transaction request sent by a sales terminal, the transaction request carries the transaction amount, the wallet number of the payee and the wallet number of the payee; querying and obtaining a red envelope account associated with the hard wallet of the payee according to the wallet number of the payee, wherein the red envelope account is used to receive red envelopes, and the red envelopes are digital currency with usage rules attached; in response to the transaction request matching the usage rules of the red envelope, based on the wallet corresponding to the wallet number of the payee and the red envelope account, the digital currency corresponding to the transaction amount is paid to the wallet corresponding to the wallet number of the payee.

[0209] As another aspect, an embodiment of the present invention further provides a computer program product, including a computer program, and when the computer program is executed by a processor, the method described in any of the above embodiments is implemented.

[0210] According to the technical solution of the embodiment of the present invention, the red envelope account associated with the payee's hard wallet is queried and obtained according to the payee's wallet number, and in response to the transaction request matching the red envelope usage rules, the digital currency corresponding to the transaction amount is paid to the wallet corresponding to the payee's wallet number based on the wallet and red envelope account corresponding to the payee's wallet number. Therefore, the technical problem that the existing red envelope processing logic in the prior art can no longer meet market demand is overcome. The embodiment of the present invention enables the digital currency hard wallet to have the ability to use red envelopes, and the digital wallet operator can query the red envelope usage in real time when the hard wallet is paid, so as to realize the use of red envelopes by the hard wallet, and basically reach the same level as the marketing ability of the soft wallet, so that the use experience of the hard wallet and the soft wallet are aligned.

[0211] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A transaction method based on red envelopes, characterized in that: The red envelope is a digital currency with usage rules attached, and the method includes: Receive a transaction request sent by a sales terminal, the transaction request carrying a transaction amount, a wallet number of a payee, and a wallet number of a payee; Querying and acquiring a red envelope account associated with the payer's hard wallet according to the payer's wallet number, wherein the red envelope account is used to receive red envelopes; In response to the transaction request matching the usage rules of the red envelope, based on the wallet corresponding to the wallet number of the payee and the red envelope account, the digital currency corresponding to the transaction amount is paid to the wallet corresponding to the wallet number of the payee.

2. The method according to claim 1, characterized in that: Before receiving the transaction request sent by the sales terminal, the method further includes: Determine whether to send a red envelope to the red envelope account associated with the payer's hard wallet via the mobile phone number; If yes, the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payer's hard wallet; If not, the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payee's hard wallet through the hard wallet number.

3. The method according to claim 2, characterized in that The red envelope is distributed from the red envelope account of the investor to the red envelope account associated with the hard wallet of the payer, including: Determine whether the payer has opened a soft wallet; If yes, the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payer's hard wallet; If not, the payee is guided to open a soft wallet in the digital currency application and bind the soft wallet to the payee's hard wallet, and the red envelope is distributed from the investor's red envelope account to the red envelope account associated with the payee's hard wallet.

4. The method according to claim 1, characterized in that: In response to the transaction request matching the usage rules of the red envelope, based on the wallet corresponding to the wallet number of the payee and the red envelope account, paying the digital currency corresponding to the transaction amount to the wallet corresponding to the wallet number of the payee, including: Determining whether there is a red envelope in the red envelope account whose usage rules match the transaction request; If so, the red envelope is transferred from the red envelope account to the wallet corresponding to the wallet number of the payee, and / or the wallet balance is transferred from the payer's hard wallet or the soft wallet bound to the hard wallet to the wallet corresponding to the payee's wallet number to pay the digital currency corresponding to the transaction amount; If not, the wallet balance is transferred from the payer's hard wallet or the soft wallet bound to the hard wallet to the wallet corresponding to the payee's wallet number to pay the digital currency corresponding to the transaction amount.

5. The method according to claim 1, characterized in that The transaction request is generated based on a hardware wallet trigger of the payer or based on a soft wallet trigger of the payer.

6. The method according to claim 1, characterized in that Querying and obtaining the red envelope account associated with the payer's hard wallet according to the payer's wallet number, including: Determine whether the wallet number of the payer is a hard wallet number; If yes, query and obtain the red envelope account associated with the payer's hard wallet according to the payer's hard wallet number; If not, query and obtain the hard wallet bound to the soft wallet according to the soft wallet number of the payer, and then query and obtain the red envelope account associated with the hard wallet according to the hard wallet number.

7. The method according to claim 4, characterized in that The method further comprises: Receiving a refund request sent by the sales terminal, the refund request carrying a refund amount, a wallet number of the refunding party, and a wallet number of the payer; Determine whether the payment method of the transaction corresponding to the refund request is a combination of red envelope and wallet balance; If yes, the red envelope is returned from the refunder's wallet to the payer's red envelope account, and / or the wallet balance is returned from the refunder's wallet to the payer's hard wallet or a soft wallet bound to the hard wallet; If not, the red envelope will be returned to the payer's red envelope account.

8. The method according to claim 7, characterized in that Returning the red envelope from the wallet of the refunder to the red envelope account of the payer, including: Determine whether the red envelope returned from the wallet of the refunder to the red envelope account of the payer has expired; If not, the red envelope is returned to the red envelope account of the payer; If so, the red envelope will be returned to the red envelope account of the investor, or the red envelope will be returned to the red envelope account of the payer and the validity period of the red envelope will be extended.

9. The method according to claim 8, characterized in that Returning the red envelope to the red envelope account of the payer includes: Determine whether the red envelope is a red envelope dedicated to a hard wallet; If yes, determine whether the payer's hard wallet is cancelled; if no, return the red envelope to the payer's red envelope account; if yes, return the red envelope to the investor's red envelope account; If not, determine whether the payer's soft wallet is cancelled; if not, return the red envelope to the payer's red envelope account; if so, return the red envelope to the investor's red envelope account.

10. A transaction device based on red envelopes, characterized in that: The red envelope is a digital currency with usage rules attached, and the device includes: A receiving module, used to receive a transaction request sent by a sales terminal, wherein the transaction request carries a transaction amount, a wallet number of a payee, and a wallet number of a payee; A query module, used to query and obtain a red envelope account associated with the payer's hard wallet according to the payer's wallet number, wherein the red envelope account is used to receive red envelopes; A processing module is used to pay the digital currency corresponding to the transaction amount to the wallet corresponding to the wallet number of the payee based on the wallet corresponding to the wallet number of the payee and the red envelope account in response to the transaction request matching the usage rules of the red envelope.

11. An electronic device, characterized in that: include: one or more processors; a 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 according to any one of claims 1 to 9.

12. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

13. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images