Payment tokenization method, apparatus and system based on digital currency sub-wallet

Abstract

The application discloses a payment tokenization method, device and system based on a digital currency sub-wallet. A specific embodiment of the method comprises: parsing a target digital wallet, a target merchant and a wallet payment password corresponding to the target digital wallet from a payment tokenization acquisition request of a user; sending the wallet payment password to a wallet institution system of the target digital wallet, so that the wallet institution system of the target digital wallet verifies the wallet payment password; in the case of verification, sending a sub-wallet opening request to the wallet institution system of the target digital wallet; and in the case of successful opening of the wallet, sending a payment token generation request to a token service provider, so that the token service provider generates a payment token corresponding to the digital currency sub-wallet. The embodiment can enable the user to complete the establishment of payment tokenization in advance at the digital wallet end, facilitate the user to centrally manage the payment tokenization relationship, and thus improve the convenience and security of the user in using tokenized payment.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to a payment tokenization method, device and system based on a digital currency sub-wallet. BACKGROUND

[0002] In electronic payment consumption, payment tokenization uses a unique payment token (associated with a payment account) for transaction verification, and the payment token is limited to use in a specific merchant or channel. In the existing payment scenario, users initiate the process of applying for a payment token at the merchant end when they have a consumption intention or demand. Users cannot actively establish, adjust or cancel the payment token relationship from the perspective of asset management. SUMMARY

[0003] Therefore, the embodiments of the present application provide a payment tokenization method, device and system based on a digital currency sub-wallet, which can enable users to pre-establish payment tokenization at the digital wallet end, facilitate users to centrally manage payment tokenization relationships, and thus improve the convenience and security of tokenization payment for users.

[0004] To achieve the above-mentioned purpose, according to an aspect of the embodiments of the present application, a payment tokenization method based on a digital currency sub-wallet is provided, comprising:

[0005] parsing a target digital wallet, a target merchant and a wallet payment password corresponding to the target digital wallet from a user payment token acquisition request;

[0006] sending the wallet payment password to a wallet institution system of the target digital wallet, so that the wallet institution system of the target digital wallet verifies the wallet payment password, and receiving a verification result returned by the wallet institution system of the target digital wallet;

[0007] in the case of passing the verification, sending a sub-wallet opening request to the wallet institution system of the target digital wallet, so that the wallet institution system of the target digital wallet generates a digital currency sub-wallet corresponding to the target digital wallet and the target merchant, and receiving a sub-wallet opening result returned by the wallet institution system of the target digital currency wallet;

[0008] in the case of successful wallet opening, sending a payment token generation request to a token service provider, so that the token service provider generates a payment token corresponding to the digital currency sub-wallet, and receiving a payment token generation result returned by the token service provider.

[0009] Optionally, the payment tokenization method of the embodiments of the present application further comprises:

[0010] obtaining a merchant list of the user from the mark service provider and sending to the terminal for display before receiving the payment mark obtaining request of the user, so that the user screens one or more merchants from the merchant list as the target merchant; or

[0011] obtaining a digital wallet list of the user and sending to the terminal for display before receiving the payment mark obtaining request of the user, so that the user screens the target digital wallet from the digital wallet list.

[0012] Optionally, the payment marking method of the embodiment of the present application further comprises:

[0013] obtaining a merchant list corresponding to the target digital wallet and sending to the terminal for display in response to the operation of the user screening the target digital wallet from the digital wallet list, so that the user screens one or more merchants from the merchant list corresponding to the target digital wallet as the target merchant.

[0014] Optionally, the payment marking method of the embodiment of the present application further comprises: obtaining account information of the target merchant, verifying the account information of the target merchant and confirming that the verification is passed after the user screens one or more merchants from the merchant list as the target merchant.

[0015] Optionally, obtaining the account information of the target merchant comprises:

[0016] determining whether the account information of the target merchant exists in the local storage device; if yes, obtaining the account information of the target merchant from the local storage device; otherwise, obtaining the account information of the target merchant from the merchant institution system of the target merchant, and storing the obtained account information of the target merchant into the local storage device.

[0017] Optionally, verifying the account information of the target merchant comprises: verifying whether the real name information and the communication information of the target merchant are consistent; if yes, the verification is passed; otherwise, the verification is not passed.

[0018] Optionally, after the mark service provider generates the payment mark corresponding to the digital currency sub-wallet, the payment mark is pushed to the wallet institution system of the target digital wallet; the wallet institution system of the target digital wallet pushes the payment mark to the merchant institution system of the target merchant; the merchant institution system of the target merchant pushes the payment mark to the merchant service end system of the target merchant.

[0019] The merchant server system of the target merchant receives the payment mark, and returns a response message to the merchant institution system of the target merchant.

[0020] The merchant server system of the target merchant pushes the payment mark to the merchant terminal of the target merchant, so that the merchant terminal of the target merchant displays the message pushed by the merchant server system of the target merchant.

[0021] Optionally, the payment marking method further comprises: before sending the sub-wallet opening request to the wallet institution system of the target digital wallet, confirming that there is no digital currency sub-wallet corresponding to the target digital wallet and the target merchant.

[0022] Optionally, the payment mark acquisition request comprises: a plurality of consumption accounts of the user in the target merchant.

[0023] The payment mark generation request is sent to the mark service provider, comprising: a payment mark generation request corresponding to each of the consumption accounts is sent to the mark service provider respectively, so that the mark service provider generates one payment mark corresponding to each of the consumption accounts respectively.

[0024] Optionally, the payment marking method further comprises:

[0025] After generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, in response to the limit query request of the user for the to-be-queried sub-wallet, the sub-wallet limit of the to-be-queried sub-wallet is acquired and sent to the terminal for display; or,

[0026] After generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, receiving the limit modification request of the user, analyzing the to-be-adjusted sub-wallet and the target limit of the to-be-adjusted limit from the limit modification request, sending the to-be-adjusted sub-wallet and the target limit to the wallet institution system corresponding to the to-be-adjusted sub-wallet, so that the wallet institution system corresponding to the to-be-adjusted sub-wallet adjusts the sub-wallet limit of the to-be-adjusted sub-wallet to the target limit.

[0027] Optionally, the payment tokenization method further comprises: before receiving the quota modification request of the user, obtaining a current quota of the to-be-adjusted sub-wallet, generating a sub-wallet quota management page according to the current quota of the to-be-adjusted sub-wallet, and sending the sub-wallet quota management page to a terminal for display, so that the user sets a target quota of the to-be-adjusted sub-wallet through an operation on the sub-wallet management page.

[0028] Optionally, the payment tokenization method further comprises: after generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, in response to a payment request of the user based on the target sub-wallet, verifying the payment request to determine that the to-be-paid amount is less than or equal to the sub-wallet quota of the target sub-wallet.

[0029] Optionally, after receiving the payment token generation result returned by the token service provider, the method further comprises: obtaining a risk control level of the target digital wallet and consumption history data of a consumption account of the user in the target merchant; and determining a payment quota of the payment token corresponding to the consumption account according to the consumption history data of the consumption account and the risk control level.

[0030] According to a second aspect of the present application, a payment method based on a digital currency sub-wallet is provided, comprising:

[0031] receiving a collection request sent by a target merchant background system in response to a consumption request of a user, the collection request including a payment token of a digital currency sub-wallet of the user corresponding to the target merchant and a collection amount;

[0032] determining a target operating agency background system corresponding to the digital currency sub-wallet according to the payment token, and sending a collection request message to the target operating agency background system;

[0033] receiving digital currency transferred in by the target operating agency background system in response to the collection request message, and in a case where the transferred digital currency is consistent with the collection amount, pushing payment result information to the target merchant background system, so that the target merchant background system pushes payment success information to the user;

[0034] The payment token is generated according to the payment tokenization method provided in the first aspect of the present application.

[0035] According to a third aspect of the present application, a payment tokenization device based on a digital currency sub-wallet is provided, comprising:

[0036] The request analysis module analyzes a target digital wallet, a target merchant, and a wallet payment password corresponding to the target digital wallet from a payment token acquisition request of a user.

[0037] The password verification module sends the wallet payment password to a wallet agency system of the target digital wallet, so that the wallet agency system of the target digital wallet verifies the wallet payment password, and receives a verification result returned by the wallet agency system of the target digital wallet;

[0038] The sub-wallet opening module sends a sub-wallet opening request to the wallet agency system of the target digital wallet, so that the wallet agency system of the target digital wallet generates a digital currency sub-wallet corresponding to the target digital wallet and the target merchant, receives a sub-wallet opening result returned by the wallet agency of the target digital currency wallet, in the case of verification passing;

[0039] The label generation module sends a payment label generation request to a label service provider, so that the label service provider generates a payment label corresponding to the digital currency sub-wallet, receives a payment label generation result returned by the label service provider, in the case of wallet opening success.

[0040] Optionally, the request analysis module is further configured to: before receiving the payment label acquisition request of the user, acquire a merchant list of the user from the label service provider and send the merchant list to the terminal for display, so that the user selects one or more merchants from the merchant list as the target merchant; or, before receiving the payment label acquisition request of the user, acquire a digital wallet list of the user and send the digital wallet list to the terminal for display, so that the user selects the target digital wallet from the digital wallet list.

[0041] Optionally, the request analysis module is further configured to: after acquiring the digital wallet list of the user and sending the digital wallet list to the terminal for display, in response to an operation of the user selecting a target digital wallet from the digital wallet list, acquire a merchant list corresponding to the target digital wallet and send the merchant list to the terminal for display, so that the user selects one or more merchants from the merchant list corresponding to the target digital wallet as the target merchant.

[0042] Optionally, the password verification module is further configured to: after the user selects one or more merchants from the merchant list as the target merchant, acquire account information of the target merchant, verifies the account information of the target merchant and confirms that the verification is passed.

[0043] Optionally, the password verification module acquires the account information of the target merchant, including:

[0044] determining whether the account information of the target merchant exists in the local storage device; if yes, obtaining the account information of the target merchant from the local storage device; otherwise, obtaining the account information of the target merchant from a merchant system of the target merchant, and storing the obtained account information of the target merchant into the local storage device.

[0045] Optionally, the password verification module verifies the account information of the target merchant, including: verifying whether the real-name information and the communication information of the target merchant are consistent; if yes, the verification is passed; otherwise, the verification is failed.

[0046] Optionally, after the mark service provider generates the payment mark corresponding to the digital currency sub-wallet, the mark service provider pushes the payment mark to a wallet system of the target digital wallet; the wallet system of the target digital wallet pushes the payment mark to a merchant system of the target merchant; the merchant system of the target merchant pushes the payment mark to a merchant server system of the target merchant.

[0047] After the merchant server system of the target merchant receives the payment mark, the merchant server system of the target merchant returns a response message to the merchant system of the target merchant; after the merchant system of the target merchant receives the response message returned by the merchant system of the target merchant, the merchant system of the target merchant returns a response message to the wallet system of the target digital wallet; after the wallet system of the target digital wallet receives the response message returned by the merchant system of the target merchant, the wallet system of the target digital wallet returns a response message to the mark service provider; after the mark service provider receives the response message returned by the wallet system of the target digital wallet, the mark service provider generates the payment mark generation result.

[0048] Optionally, the merchant server system of the target merchant pushes the payment mark to a merchant terminal of the target merchant, so that the merchant terminal of the target merchant displays the message pushed by the merchant server system of the target merchant.

[0049] Optionally, the sub-wallet opening module is further configured to: before sending a sub-wallet opening request to the wallet system of the target digital wallet, confirm that there is no digital currency sub-wallet corresponding to the target digital wallet and the target merchant.

[0050] Optionally, the payment mark acquisition request includes: a plurality of consumption accounts of the user in the target merchant.

[0051] The label generation module sends a payment label generation request to the label service provider, including: sending a payment label generation request corresponding to each of the consumption accounts to the label service provider respectively, so that the label service provider generates one payment label corresponding to each of the consumption accounts respectively.

[0052] Optionally, the device further comprises a quota management module, configured to:

[0053] After generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, in response to a quota query request of the user for a to-be-queried sub-wallet, the sub-wallet quota of the to-be-queried sub-wallet is acquired and sent to a terminal for display; or,

[0054] After generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, a quota modification request of the user is received, a to-be-adjusted sub-wallet and a target quota of a to-be-adjusted sub-wallet are parsed from the quota modification request, and the to-be-adjusted sub-wallet and the target quota of the to-be-adjusted sub-wallet are sent to a wallet institution system corresponding to the to-be-adjusted sub-wallet, so that the wallet institution system corresponding to the to-be-adjusted sub-wallet adjusts the sub-wallet quota of the to-be-adjusted sub-wallet to the target quota.

[0055] Optionally, the quota management module is further configured to: before receiving the quota modification request of the user, a current quota of the to-be-adjusted sub-wallet is acquired, a sub-wallet quota management page is generated according to the current quota of the to-be-adjusted sub-wallet and is sent to a terminal for display, so that the user sets a target quota of the to-be-adjusted sub-wallet through an operation on the sub-wallet management page.

[0056] Optionally, the device further comprises a payment management module, configured to: after generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, in response to a payment request of the user based on a target sub-wallet, the payment request is verified to determine that a to-be-paid amount is less than or equal to a sub-wallet quota of the target sub-wallet.

[0057] Optionally, the device further comprises a quota management module, configured to: after receiving the payment label generation result returned by the label service provider, a risk control level of the target digital wallet and consumption history data of a consumption account of the user in the target merchant are acquired; according to the consumption history data of the consumption account and the risk control level, a payment quota of a payment label corresponding to the consumption account is determined.

[0058] According to the fourth aspect of the present application, a payment labeling system based on a digital currency sub-wallet is provided, comprising: a digital wallet system, a label service provider, and a wallet institution system; wherein,

[0059] The digital wallet system parses a target digital wallet, a target merchant, and a wallet payment password corresponding to the target digital wallet from a payment mark obtaining request of a user; sends the wallet payment password to a wallet institution system of the target digital wallet, so that the wallet institution system of the target digital wallet verifies the wallet payment password;

[0060] If the verification is passed, the digital wallet system sends a sub-wallet opening request to the wallet institution system of the target digital wallet, the wallet institution system of the target digital wallet generates a digital currency sub-wallet corresponding to the target digital wallet and the target merchant, and returns a sub-wallet opening result to the digital wallet system;

[0061] If the wallet opening is determined to be successful according to the wallet opening result, the digital wallet system sends a payment mark generation request to a mark service provider;

[0062] The mark service provider generates a payment mark corresponding to the digital currency sub-wallet, and then returns a payment mark generation result to the digital wallet system.

[0063] Optionally, the digital wallet system is further configured to:

[0064] Before receiving the payment mark obtaining request of the user, the digital wallet system obtains a merchant list of the user from the mark service provider and sends the merchant list to a terminal for display, so that the user selects one or more merchants from the merchant list as the target merchant; or

[0065] Before receiving the payment mark obtaining request of the user, the digital wallet system obtains a digital wallet list of the user and sends the digital wallet list to a terminal for display, so that the user selects the target digital wallet from the digital wallet list.

[0066] Optionally, the digital wallet system is further configured to:

[0067] After obtaining the digital wallet list of the user and sending the digital wallet list to a terminal for display, in response to an operation of the user selecting a target digital wallet from the digital wallet list, the digital wallet system obtains a merchant list corresponding to the target digital wallet and sends the merchant list to a terminal for display, so that the user selects one or more merchants from the merchant list corresponding to the target digital wallet as the target merchant.

[0068] Optionally, the digital wallet system is further configured to: after the user selects one or more merchants from the merchant list as the target merchant, the digital wallet system obtains account information of the target merchant, verifies the account information of the target merchant, and confirms that the verification is passed.

[0069] Optionally, the digital wallet system obtains the account information of the target merchant, comprising:

[0070] determining whether the account information of the target merchant exists in the local storage device; if yes, obtaining the account information of the target merchant from the local storage device; otherwise, obtaining the account information of the target merchant from the merchant institution system of the target merchant, and storing the obtained account information of the target merchant into the local storage device.

[0071] Optionally, the digital wallet system verifies the account information of the target merchant, comprising: verifying whether the real name information and the communication information of the target merchant are consistent; if yes, the verification is passed; otherwise, the verification is failed.

[0072] Optionally, after the mark service provider generates the payment mark corresponding to the digital currency sub-wallet, the mark service provider pushes the payment mark to the wallet institution system of the target digital wallet; the wallet institution system of the target digital wallet pushes the payment mark to the merchant institution system of the target merchant; the merchant institution system of the target merchant pushes the payment mark to the merchant server system of the target merchant;

[0073] After the merchant server system of the target merchant receives the payment mark, the merchant server system of the target merchant returns an answer message to the merchant institution system of the target merchant; after the merchant institution system of the target merchant receives the answer message returned by the merchant institution system of the target merchant, the merchant institution system of the target merchant returns an answer message to the wallet institution system of the target digital wallet; after the wallet institution system of the target digital wallet receives the answer message returned by the merchant institution system of the target merchant, the wallet institution system of the target digital wallet returns an answer message to the mark service provider; after the mark service provider receives the answer message returned by the wallet institution system of the target digital wallet, the mark service provider generates the payment mark generation result;

[0074] Wherein, the merchant server system of the target merchant pushes the payment mark to the merchant terminal of the target merchant, so that the merchant terminal of the target merchant displays the message pushed by the merchant server system of the target merchant.

[0075] Optionally, the digital wallet system is further configured to: before sending the sub-wallet opening request to the wallet institution system of the target digital wallet, confirming that there is no digital currency sub-wallet corresponding to the target digital wallet and the target merchant.

[0076] Optionally, the payment mark acquisition request comprises: a plurality of consumption accounts of the user in the target merchant;

[0077] The digital wallet system sends a payment token generation request to the token service provider, including: sending a payment token generation request corresponding to each of the consumption accounts to the token service provider respectively, so that the token service provider generates one payment token corresponding to each of the consumption accounts respectively.

[0078] Optionally, the digital wallet system is further configured to:

[0079] After generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, in response to a limit query request of the user for a to-be-queried sub-wallet, the sub-wallet limit of the to-be-queried sub-wallet is acquired and sent to a terminal for display; or,

[0080] After generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, a limit modification request of the user is received, a to-be-adjusted sub-wallet and a target limit of a to-be-adjusted limit of the to-be-adjusted sub-wallet are parsed from the limit modification request, and the to-be-adjusted sub-wallet and the target limit of the to-be-adjusted limit are sent to a wallet institution system corresponding to the to-be-adjusted sub-wallet, so that the wallet institution system corresponding to the to-be-adjusted sub-wallet adjusts the sub-wallet limit of the to-be-adjusted sub-wallet to the target limit.

[0081] Optionally, the digital wallet system is further configured to: before receiving the limit modification request of the user, acquire a current limit of the to-be-adjusted sub-wallet, generate a sub-wallet limit management page according to the current limit of the to-be-adjusted sub-wallet and send the sub-wallet limit management page to a terminal for display, so that the user sets a target limit of the to-be-adjusted sub-wallet through an operation on the sub-wallet management page.

[0082] Optionally, the digital wallet system is further configured to: after generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, in response to a payment request of the user based on a target sub-wallet, verifying the payment request to determine whether a to-be-paid amount is less than or equal to a sub-wallet limit of the target sub-wallet.

[0083] Optionally, the digital wallet system is further configured to: after receiving the payment token generation result returned by the token service provider, acquiring a risk control level of the target digital wallet and consumption history data of a consumption account of the user in the target merchant; and determining a payment limit of a payment token corresponding to the consumption account according to the consumption history data of the consumption account and the risk control level.

[0084] According to a fifth aspect of an embodiment of the present application, a payment tokenization electronic device based on a digital currency sub-wallet is provided, including:

[0085] one or more processors;

[0086] a storage device storing one or more programs,

[0087] When the one or more programs are executed by the one or more processors, the one or more processors implement the method provided by the first aspect of the embodiments of the present application.

[0088] According to a sixth aspect of the embodiments of the present application, a computer readable medium is provided, having stored thereon a computer program which, when executed by a processor, implements the method provided by the first aspect of the embodiments of the present application.

[0089] An embodiment of the above-mentioned application has the following advantages or beneficial effects: the method for establishing payment tokenization with a consumption merchant initiated by a digital wallet party provided by the embodiments of the present application enables a user to pre-establish payment tokenization on the digital wallet side, which facilitates the user to centrally manage the payment tokenization relationship, thereby improving the convenience and security of the user using tokenization payment.

[0090] Further effects of the above-mentioned non-conventional optional mode will be described in the following combined with the specific embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0091] The accompanying drawings are used to better understand the present application and do not constitute an improper limitation on the present application. Among them:

[0092] Figure 1 is a schematic diagram of the main process of the payment tokenization method based on the digital currency sub-wallet of the embodiments of the present application;

[0093] Figure 2 is a schematic diagram of the main process of the payment tokenization method based on the digital currency sub-wallet of the optional embodiments of the present application;

[0094] Figure 3 is a schematic diagram of the main process of the modification of the sub-wallet limit of the optional embodiments of the present application;

[0095] Figure 4 is a schematic diagram of the main modules of the payment tokenization device based on the digital currency sub-wallet of the embodiments of the present application;

[0096] Figure 5 is a schematic diagram of the main components of the payment tokenization system based on the digital currency sub-wallet of the embodiments of the present application;

[0097] Figure 6 is an exemplary system architecture diagram to which the embodiments of the present application can be applied;

[0098] Figure 7 is a structural schematic diagram of a computer system of a terminal device or a server suitable for implementing the embodiments of the present application. DETAILED DESCRIPTION

[0099] Exemplary embodiments of the present application are described herein with reference to the accompanying drawings, which are meant to be exemplary in nature, and include various specific details to facilitate understanding, and are to be considered in the context of the description. One skilled in the art will realize that the embodiments described herein are not the only ones that can be utilized, and that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Also, for the sake of brevity and clarity, descriptions of well-known functions and constructions are omitted herein where such functions and constructions are well known from the related art.

[0100] According to an aspect of the embodiments of the present application, there is provided a payment tokenization method based on a digital currency sub-wallet.

[0101] Figure 1 is a schematic diagram of the main process of the payment tokenization method based on a digital currency sub-wallet according to the embodiments of the present application, as shown, the payment tokenization method based on a digital currency sub-wallet comprises: Figure 1

[0102] Step S101, parsing a target digital wallet, a target merchant, and a wallet payment password corresponding to the target digital wallet from a payment token acquisition request of a user;

[0103] Step S102, sending the wallet payment password to a wallet institution system of the target digital wallet, so that the wallet institution system of the target digital wallet verifies the wallet payment password, and receiving a verification result returned by the wallet institution system of the target digital wallet;

[0104] Step S103, in the case of passing the verification, sending a sub-wallet opening request to the wallet institution system of the target digital wallet, so that the wallet institution system of the target digital wallet generates a digital currency sub-wallet corresponding to the target digital wallet and the target merchant, and receiving a sub-wallet opening result returned by the wallet institution of the target digital currency wallet;

[0105] Step S104, in the case of successful wallet opening, sending a payment token generation request to a token service provider, so that the token service provider generates a payment token corresponding to the digital currency sub-wallet, and receiving a payment token generation result returned by the token service provider.

[0106] ​The digital wallet refers to a digital currency wallet, and the wallet institution system refers to a computer system providing related services for the digital currency wallet, such as a computer system of a digital currency operation institution authorized by a digital currency issuing institution. The token service provider refers to an institution providing tokenization services, such as a TSP (Token Service Provider). The merchant refers to a party providing a commodity selling service through an electronic transaction, and the merchant account refers to account information of the merchant, such as a mobile phone number, a bank card number, a digital currency wallet account, and the like. The merchant institution system refers to a computer system of an institution providing digital currency related services for the merchant, such as a computer system of a digital currency operation institution authorized by a digital currency issuing institution. The merchant system refers to a computer system providing background service support for the merchant. Exemplarily, the seller a sells electronic products on the e-commerce platform A, and the digital currency account of the seller a is a digital currency account opened at the bank B. In this application scenario, the e-commerce platform A is a merchant, the background service support provided for the e-commerce platform A is a merchant system, and the bank B is a computer system providing related services for the digital currency wallet, which is a merchant institution system.

[0107] The embodiment of the application is based on a digital currency, and a payment token is used to replace an account number of a user digital currency wallet for transaction authentication. The payment token is usually a Token (token), and other tokens can also be used as payment tokens in actual application processes, as long as the token has uniqueness and can meet the transaction security requirements. The embodiment of the application does not specifically limit the embodiment form of the payment token.

[0108] The embodiment of the application uses a low-sensitivity payment token to replace sensitive real account information, which can reduce the opportunity of each participant in the payment link to contact the real account information, reduce the transaction risk caused by leakage of the real account information, and enhance the security of the transaction without affecting the transaction processing. At the same time, a real account information can correspond to generate multiple payment tokens and be distributed to different scenarios, and further, each payment token can be set with a different validity period, thereby facilitating the user to perform payment token life cycle management. In addition, the payment tokenization technology has a domain control function, and can set personalized domain control attributes when each payment token is generated or through a later management interface, including but not limited to transaction channel restriction, transaction limit setting, whether to allow cross-border transaction, and the like. The wallet institution system to which the digital currency wallet belongs can set domain control attributes for the payment token in a specific scenario according to the characteristics of the transaction scenario, so as to further reduce the payment risk.

[0109] The method of the embodiment of the application is generally applied to a digital currency wallet server. A user can initiate a payment tokenization request at a digital currency wallet terminal, actively select different merchants to establish a tokenization payment relationship (i.e., an association relationship between a digital currency sub-wallet corresponding to the digital currency wallet and a corresponding merchant) from the perspective of payment wallet asset management, and centrally manage the tokenization payment relationship. The method of the embodiment of the application realizes pre-establishment of a tokenization relationship before consumption, realizes batch relationships of signed merchants, for example, one-key opening of a payment tokenization service for all merchants under the same group, and greatly increases the convenience of tokenization payment for users.

[0110] Optionally, before receiving the payment token acquisition request of the user, a merchant list of the user is acquired from a token service provider and sent to the terminal for display, so that the user selects one or more merchants from the merchant list as the target merchant. The merchant list refers to a list formed by one or more merchants. The merchant list can include all merchants supported by the wallet agency system, or can only include merchants in which the user has a consumption account. For example, the user has a consumption account on e-commerce platforms A, B, and C, and the merchant list containing the e-commerce platforms A, B, and C can be displayed to the user, and the user selects one or more as the target merchant. In actual application, before the merchant list is displayed to the user, the merchants in the merchant list in which the user does not have a consumption account or the merchants in which the user has opened a payment tokenization service can be removed to facilitate user screening and viewing. Further, the merchant list can be returned in a certain rule sorting and classification, for example, the merchants are divided into transportation and travel type, shopping type, education and learning type, social type, and financial and investment type according to the purpose of the merchants.

[0111] Optionally, before receiving the payment token acquisition request of the user, a digital wallet list of the user can be acquired and sent to the terminal for display, so that the user selects a target digital wallet from the digital wallet list. The digital wallet list refers to a list formed by part or all of the digital currency wallets of the user. By displaying the digital currency wallet list to the user, the user can independently select the digital currency wallet account for which the payment token needs to be established.

[0112] Further, after acquiring the digital wallet list of the user and sending it to the terminal for display, the merchant list corresponding to the target digital wallet can be acquired and sent to the terminal for display in response to the operation of the user selecting the target digital wallet from the digital wallet list, so that the user selects one or more merchants from the merchant list corresponding to the target digital wallet as the target merchant. The embodiment can display each merchant supported by the target digital wallet to the user according to the target digital wallet selected by the user, and filter out the merchants not supported by the target digital wallet.

[0113] It should be noted that the user can select one target digital wallet and one or more target merchants to establish a tokenized payment relationship, or can select multiple target digital wallets and one or more target merchants to establish a tokenized payment relationship. For the target digital wallet and the target merchant establishing the payment tokenization relationship, the target digital wallet can establish a payment tokenization relationship with one consumption account of the user in the target merchant, or can establish a payment tokenization relationship with multiple consumption accounts of the user in the target merchant. The consumption account of the user in the target merchant can refer only to a consumption account opened by the user himself / herself in the target merchant, or can refer to a consumption account opened by another person (such as the user's spouse, parent, child, friend, etc.) having a specific relationship with the user in the target merchant, or a consumption account designated by the user in the target merchant (such as a consumption account input by the user when selecting the target merchant).

[0114] The embodiment of the present application can realize that the payment capability of one digital wallet can be shared to multiple consumption accounts of merchants, can be applied to a scene such as "one digital wallet for the whole family", and the one-to-many combination relationship has the implementation basis of "smart contract" in the consumption field, and has strong expansibility.

[0115] The wallet payment password of the user is verified in step S102, which is used to verify the identity of the user. The wallet payment password can be transmitted in plaintext or in ciphertext form to ensure transaction security. Optionally, the payment tokenization method of the embodiment of the present application further comprises: before receiving the wallet payment password of the user, obtaining account information of the target merchant, verifying the account information of the target merchant and confirming that the verification is passed. The account information of the target merchant, for example, can be the account name of the target merchant, the bound mobile phone number, the real name information, etc. The content of verifying the account information of the target merchant can be selectively set according to the actual situation, for example, verifying whether each item of account information of the target merchant is consistent (such as whether the real name information and the communication information such as the mobile phone number of the target merchant are consistent), whether the account number of the target merchant is abnormal (such as whether it is sealed and frozen). By verifying the account information of the target merchant, the effectiveness of the target merchant can be ensured before opening the digital currency sub-wallet, which can avoid the situation that the tokenized payment relationship cannot be established due to problems such as abnormal account number of the target merchant or mismatch between the account number of the target merchant and the target merchant, and can avoid the consumption of system resources due to the continuous request to establish a digital currency sub-wallet in the above-mentioned situation.

[0116] In actual application, the target merchant institution system can be used for verification, the digital wallet system can directly obtain the verification result from the target merchant institution system, or the digital wallet system can obtain the account information of the target merchant from the target merchant institution system and then perform verification according to the obtained information. The digital wallet system can directly obtain the account information of the target merchant from the target merchant institution system, or obtain the account information of the target merchant from a local storage device. For example, the step of obtaining the account information of the target merchant includes: determining whether the account information of the target merchant exists in the local storage device; if yes, obtaining the account information of the target merchant from the local storage device; otherwise, obtaining the account information of the target merchant from the target merchant institution system and storing the obtained account information of the target merchant in the local storage device. By obtaining the account information from the local storage device first, the access frequency to the target merchant institution system can be reduced, and thus the network resource consumption can be reduced.

[0117] In the embodiment of the application, after the payment mark corresponding to the digital currency sub-wallet is generated, the mark service provider can push the payment mark to the digital wallet system, the wallet institution system of the target digital wallet, the merchant institution system of the target merchant, and the target merchant, respectively.

[0118] Optionally, after the mark service provider generates the payment mark corresponding to the digital currency sub-wallet, the mark service provider pushes the payment mark to the wallet institution system of the target digital wallet; the wallet institution system of the target digital wallet pushes the payment mark to the merchant institution system of the target merchant; the merchant institution system of the target merchant pushes the payment mark to the merchant server system of the target merchant; after the merchant server system of the target merchant receives the payment mark, the merchant server system of the target merchant returns a response message to the merchant institution system of the target merchant; after the merchant institution system of the target merchant receives the response message returned by the merchant institution system of the target merchant, the merchant institution system of the target merchant returns a response message to the wallet institution system of the target digital wallet; after the wallet institution system of the target digital wallet receives the response message returned by the merchant institution system of the target merchant, the wallet institution system of the target digital wallet returns a response message to the mark service provider; after the mark service provider receives the response message returned by the wallet institution system of the target digital wallet, the mark service provider generates a payment mark generation result.

[0119] The target merchant and the merchant institution system to which the target merchant belongs and the digital wallet system usually belong to different computer systems. The target merchant institution system pushes the payment mark to the target merchant, which can reduce the difficulty of cross-system communication and facilitate implementation. The target merchant institution system can push the payment mark to the target merchant in various ways according to actual conditions. For example, the target merchant server system pushes the payment mark to the target merchant terminal, so that the target merchant terminal displays the message pushed by the target merchant server system. The target merchant server system can push the payment mark to the target merchant terminal by using push information, which is also called service information or push information. Push information is a special format of short message. Push message is a message push method that can directly reach users, with low cost and various styles.

[0120] For a pair of target digital wallet and target merchant establishing a payment marking relationship, the target digital wallet can establish a payment marking relationship with multiple consumption accounts of the user in the target merchant.

[0121] In some optional embodiments, for a pair of target digital wallet and target merchant establishing a payment marking relationship, a digital currency sub-wallet corresponding to all consumption accounts in the corresponding target merchant can be established in the target digital wallet, that is, all consumption accounts in the target merchant share one digital currency sub-wallet. Illustratively, before sending a sub-wallet opening request to the wallet institution of the target digital wallet, it is confirmed that there is no digital currency sub-wallet corresponding to the target digital wallet and the target merchant. In this way, it can be ensured that there is only one digital currency sub-wallet for a target digital wallet in a target merchant, which is convenient for the user to manage.

[0122] In other optional embodiments, for a pair of target digital wallet and target merchant establishing a payment marking relationship, a digital currency sub-wallet corresponding to each consumption account in the corresponding target merchant is established in the target digital wallet, that is, one consumption account corresponds to one digital currency sub-wallet. Specifically, the payment mark acquisition request includes multiple consumption accounts of the user in the target merchant, and sending a payment mark generation request to the mark service provider includes: sending a payment mark generation request corresponding to each consumption account to the mark service provider respectively, so that the mark service provider generates one payment mark corresponding to each consumption account respectively. In this way, it can be ensured that one consumption account in the target merchant corresponds to one digital currency sub-wallet, which is convenient for the user to manage different consumption accounts diversely.

[0123] Figure 2FIG. 1 is a schematic diagram of the main flow of the payment tokenization method based on the digital currency sub-wallet in the optional embodiment of the present application. In this embodiment, the execution subject of the payment tokenization method of the present embodiment is the digital wallet system. As shown in FIG. 1, the main flow of the payment tokenization method based on the digital currency sub-wallet includes the following steps: Figure 2

[0124] 1. The digital wallet terminal (hereinafter referred to as App) requests the digital wallet system through the interface to query the pushable merchant list.

[0125] 2. The digital wallet system queries the pushable merchant list from the TSP.

[0126] 3. The TSP returns the pushable merchant list sorted and classified according to certain rules to the digital wallet system.

[0127] 4. The digital wallet system returns the pushable merchant list sorted and classified according to certain rules to the App.

[0128] 5. The user selects the pushable merchant and the wallet on the App. Here, the user can select multiple merchants for batch pushing, or select multiple consumption accounts of the same merchant for pushing.

[0129] 6. The App queries the merchant account information from the digital wallet system.

[0130] 7. The digital wallet system queries the basic configuration information of the merchant from the local storage device or the merchant institution system.

[0131] 8. The digital wallet system returns the queried basic configuration information of the merchant to the App.

[0132] 9. The user requests the digital wallet system through the App to query the consistency of the merchant account and the merchant account information.

[0133] 10. The digital wallet system queries the basic configuration information of the merchant from the local storage device or the merchant institution system.

[0134] 11. The digital wallet system queries the merchant account information from the merchant institution system.

[0135] 12. The merchant institution system queries the merchant account information from the merchant system.

[0136] 13. The merchant system returns the merchant account information to the merchant institution system.

[0137] 14. The merchant institution system returns the merchant account information to the digital wallet system.

[0138] 15. The digital wallet system requests the wallet institution system to judge the consistency of the real-name information of the merchant and the mobile phone number. ​

[0139] 16. The wallet institution system returns the result to the digital wallet system.

[0140] 17. The digital wallet system returns the result to the App.

[0141] 18. The user inputs the payment password through the App.

[0142] 19. The App sends the ciphertext of the input wallet payment password to the digital wallet system, and issues a sub-wallet push request.

[0143] 20. The digital wallet system checks the association code (such as dynamic check code, etc.) when the App issues the sub-wallet push request.

[0144] 21. After the check passes, the digital wallet system requests the wallet institution system to check the user input payment password.

[0145] 22. The wallet institution system returns the check result to the digital wallet system.

[0146] 23. In the case where the check result is a check pass, the digital wallet system issues a sub-wallet opening request to the wallet institution system.

[0147] 24. After the wallet institution system opens the digital currency sub-wallet, it returns the sub-wallet information to the digital wallet system.

[0148] 25. The digital wallet system sends a push request to the TSP to request the TSP to generate a payment token Token corresponding to the sub-wallet information.

[0149] 26-31. After the TSP generates the Token, it pushes the Token to the merchant, and the Token is synchronously sent to the wallet institution system, the merchant institution system, the merchant system, the merchant terminal, and the merchant terminal. The merchant system pushes the Token to the merchant terminal, and the merchant terminal displays the push information to the merchant.

[0150] 32-35. After the merchant institution system pushes the Token to the merchant system, it receives the push result information returned by the merchant system. The merchant institution system returns the push result information to the wallet institution system, and the wallet institution system returns the push result information to the TSP. The TSP returns the push result information to the digital wallet system. The digital wallet system returns the push result information to the App, prompting the user to complete the sub-wallet binding push.

[0151] After generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, in response to a payment request of the user based on the target sub-wallet, the payment request can be verified to determine that the to-be-paid amount is less than or equal to the sub-wallet limit of the target sub-wallet, so as to facilitate diversified management of the consumption limit of each digital currency sub-wallet.

[0152] In actual application, after generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, in response to a limit query request of the user for the to-be-queried sub-wallet, the sub-wallet limit of the to-be-queried sub-wallet can be obtained and sent to the terminal for display; or, after generating the sub-wallet corresponding to the target digital wallet and the target merchant, a limit modification request of the user is received, the to-be-adjusted sub-wallet and the target limit of the to-be-adjusted sub-wallet are parsed from the limit modification request, and the to-be-adjusted sub-wallet and the target limit of the to-be-adjusted sub-wallet are sent to the wallet agency system corresponding to the to-be-adjusted sub-wallet, so that the wallet agency system corresponding to the to-be-adjusted sub-wallet adjusts the sub-wallet limit of the to-be-adjusted sub-wallet to the target limit. Exemplarily, before receiving the limit modification request of the user, the current limit of the to-be-adjusted sub-wallet is obtained, a sub-wallet limit management page is generated according to the current limit of the to-be-adjusted sub-wallet and is sent to the terminal for display, so that the user sets the target limit of the to-be-adjusted sub-wallet through the operation on the sub-wallet management page.

[0153] Figure 3 is a schematic diagram of the main process of modifying the sub-wallet limit in the optional embodiment of the application.

[0154] As Figure 3 shown, the sub-wallet limit management process includes:

[0155] 1. The user queries the sub-wallet details through the digital wallet terminal to the digital wallet system.

[0156] 2. The digital wallet system queries the sub-wallet details to the wallet agency system.

[0157] 3. The wallet agency system returns the sub-wallet details to the digital wallet system.

[0158] 4. The digital wallet system returns the sub-wallet details to the digital wallet terminal. The user enters a certain sub-wallet management page through the digital wallet terminal.

[0159] 5. The user adjusts the limit of the sub-wallet by dragging the page. The limit includes the daily limit and the single limit. The user can also perform differentiated limit management on multiple Tokens under the same digital currency sub-wallet. The user sends a sub-wallet limit modification request to the digital wallet system through the digital wallet terminal.

[0160] 6. The digital wallet system sends the sub-wallet limit modification request to the wallet agency system.

[0161] 7. The wallet institution system modifies the limit of the corresponding digital currency sub-wallet according to the sub-wallet limit modification request, and then returns the result information to the digital wallet system. The wallet operation institution system can adjust the limit of the digital currency sub-wallet for this merchant to the latest value set by the user after verifying the payment password input by the user.

[0162] 8. The digital wallet server returns the result information to the digital wallet terminal.

[0163] After receiving the payment mark generation result returned by the mark service provider, the method can further include: obtaining a risk control level of the target digital wallet and consumption history data of a consumption account of the user in the target merchant; and determining a payment limit of a payment mark corresponding to the consumption account according to the consumption history data (such as purchase records, shopping cart records, browsing records, attention records, and the like) of the consumption account and the risk control level. For example, the user can open any one of five types of wallet accounts according to the needs of the user, the user information required for opening each type of wallet account is different, the corresponding authority is different, that is, the risk control level is different.

[0164] Based on the "one-to-many" marked payment relationship, the method of the embodiment of the application can realize more refined limit management, different payment limits can be set for different consumption history data of consumption accounts and in combination with the risk control level of the corresponding digital wallet, and the security of the marked payment is improved.

[0165] According to a second aspect of the embodiment of the application, a payment method based on a digital currency sub-wallet is provided, including:

[0166] receiving a collection request sent by a target merchant background system in response to a consumption request of a user, the collection request including a payment mark of a digital currency sub-wallet of the user corresponding to the target merchant and a collection amount;

[0167] determining a target operation institution background system corresponding to the digital currency sub-wallet according to the payment mark, and sending a collection request message to the target operation institution background system;

[0168] receiving digital currency transferred in by the target operation institution background system in response to the collection request message, and pushing payment result information to the target merchant background system in the case that the transferred digital currency is consistent with the collection amount, so as to make the target merchant background system push payment success information to the user;

[0169] The payment mark is generated according to the payment marking method provided in the first aspect of the embodiment of the application.

[0170] Digital currency sub-wallet consumption process:

[0171] 1. When the user consumes in the target merchant, the user can choose to use the Token of the bound digital wallet for payment.

[0172] 2. The merchant system finds the Token corresponding to the user, and then sends the Token to the merchant institution for collection.

[0173] 3. The merchant institution system finds the wallet institution system corresponding to the Token according to the record, and sends a collection request message.

[0174] 4. After receiving the collection request message, the wallet institution system pays into the merchant wallet provided in the collection request message. The merchant institution system returns the payment result to the merchant server.

[0175] 5. The merchant system prompts the user or the target merchant that the payment is successful.

[0176] According to a third aspect of an embodiment of the present application, a device for implementing the above method is provided.

[0177] Figure 4 is a schematic diagram of the main modules of the payment tokenization device based on the digital currency sub-wallet according to an embodiment of the present application. As shown in Figure 4 , the payment tokenization device based on the digital currency sub-wallet 400 includes:

[0178] The request analysis module 401 analyzes the target digital wallet, the target merchant, and the wallet payment password corresponding to the target digital wallet from the payment token acquisition request of the user;

[0179] The password verification module 402 sends the wallet payment password to the wallet institution system of the target digital wallet, so that the wallet institution system of the target digital wallet verifies the wallet payment password, and receives the verification result returned by the wallet institution system of the target digital wallet;

[0180] The sub-wallet opening module 403 sends a sub-wallet opening request to the wallet institution system of the target digital wallet in the case of verification passing, so that the wallet institution system of the target digital wallet generates a digital currency sub-wallet corresponding to the target digital wallet and the target merchant, and receives the sub-wallet opening result returned by the wallet institution of the target digital currency wallet;

[0181] The token generation module 404 sends a payment token generation request to the token service provider in the case of successful wallet opening, so that the token service provider generates a payment token corresponding to the digital currency sub-wallet, and receives the payment token generation result returned by the token service provider.

[0182] Optionally, the request parsing module is further configured to: before receiving the payment mark obtaining request of the user, obtain a merchant list of the user from the mark service provider and send the merchant list to the terminal for display, so that the user selects one or more merchants from the merchant list as the target merchant; or, before receiving the payment mark obtaining request of the user, obtain a digital wallet list of the user and send the digital wallet list to the terminal for display, so that the user selects the target digital wallet from the digital wallet list.

[0183] Optionally, the request parsing module is further configured to: after obtaining the digital wallet list of the user and sending the digital wallet list to the terminal for display, in response to an operation of the user selecting a target digital wallet from the digital wallet list, obtain a merchant list corresponding to the target digital wallet and send the merchant list to the terminal for display, so that the user selects one or more merchants from the merchant list corresponding to the target digital wallet as the target merchant.

[0184] Optionally, the password verification module is further configured to: after the user selects one or more merchants from the merchant list as the target merchant, obtain account information of the target merchant, and verify the account information of the target merchant and confirm that the verification is passed.

[0185] Optionally, the password verification module obtains the account information of the target merchant, including:

[0186] determining whether the account information of the target merchant exists in a local storage device; if yes, obtaining the account information of the target merchant from the local storage device; otherwise, obtaining the account information of the target merchant from a merchant institution system of the target merchant, and storing the obtained account information of the target merchant into the local storage device.

[0187] Optionally, the password verification module verifies the account information of the target merchant, including: verifying whether real-name information and communication information of the target merchant are consistent; if yes, the verification is passed; otherwise, the verification is failed.

[0188] Optionally, after the mark service provider generates the payment mark corresponding to the digital currency sub-wallet, the mark service provider pushes the payment mark to a wallet institution system of the target digital wallet; the wallet institution system of the target digital wallet pushes the payment mark to a merchant institution system of the target merchant; and the merchant institution system of the target merchant pushes the payment mark to a merchant service end system of the target merchant.

[0189] The merchant server system of the target merchant receives the payment mark, and returns a response message to the merchant institution system of the target merchant; the merchant institution system of the target merchant receives the response message returned by the merchant institution system of the target merchant, and returns a response message to the wallet institution system of the target digital wallet; the wallet institution system of the target digital wallet receives the response message returned by the merchant institution system of the target merchant, and returns a response message to the mark service provider; the mark service provider receives the response message returned by the wallet institution system of the target digital wallet, and generates the payment mark generation result;

[0190] The merchant server system of the target merchant pushes the payment mark to the merchant terminal of the target merchant by using push information, so that the merchant terminal of the target merchant displays the message pushed by the merchant server system of the target merchant.

[0191] Optionally, the sub-wallet opening module is further configured to: before sending the sub-wallet opening request to the wallet institution system of the target digital wallet, confirm that there is no digital currency sub-wallet corresponding to the target digital wallet and the target merchant.

[0192] Optionally, the payment mark acquisition request comprises: a plurality of consumption accounts of the user in the target merchant.

[0193] The mark generation module sends a payment mark generation request to the mark service provider, comprising: sending a payment mark generation request corresponding to each consumption account to the mark service provider respectively, so that the mark service provider generates one payment mark corresponding to each consumption account respectively.

[0194] Optionally, the device of the embodiment of the application further comprises a quota management module, configured to:

[0195] After generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, in response to the quota query request of the user for the to-be-queried sub-wallet, the sub-wallet quota of the to-be-queried sub-wallet is acquired and sent to the terminal for display; or,

[0196] After generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, the user's quota modification request is received, the to-be-adjusted sub-wallet and the target quota of the to-be-adjusted quota are parsed from the quota modification request, and the to-be-adjusted sub-wallet and the target quota are sent to the wallet institution system corresponding to the to-be-adjusted sub-wallet, so that the wallet institution system corresponding to the to-be-adjusted sub-wallet adjusts the sub-wallet quota of the to-be-adjusted sub-wallet to the target quota.

[0197] Optionally, the quota management module is further configured to: before receiving the quota modification request of the user, acquire a current quota of the to-be-adjusted sub-wallet, generate a sub-wallet quota management page according to the current quota of the to-be-adjusted sub-wallet, and send the sub-wallet quota management page to the terminal for display, so that the user sets a target quota of the to-be-adjusted digital currency sub-wallet through an operation on the sub-wallet management page.

[0198] Optionally, the apparatus further comprises a payment management module configured to: after generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, in response to a payment request of the user based on the target sub-wallet, verifying the payment request to determine that a to-be-paid amount is less than or equal to the sub-wallet quota of the target sub-wallet.

[0199] Optionally, the apparatus further comprises a quota management module configured to: after receiving the payment mark generation result returned by the marking service provider, acquiring a risk control level of the target digital wallet and consumption history data of a consumption account of the user in the target merchant; and determining a payment quota of the payment mark corresponding to the consumption account according to the consumption history data of the consumption account and the risk control level.

[0200] According to a fourth aspect of the embodiments of the present application, a system for implementing the above method is provided.

[0201] Figure 5 is a schematic diagram of the main components of the digital currency sub-wallet-based payment marking system according to the embodiments of the present application. As shown in Figure 5 the digital currency sub-wallet-based payment marking system 500 comprises a digital wallet system 501, a marking service provider 502, and a wallet institution system 503; wherein,

[0202] The digital wallet system 501 parses a target digital wallet, a target merchant, and a wallet payment password corresponding to the target digital wallet from a payment mark acquisition request of a user; sends the wallet payment password to the wallet institution system 503 of the target digital wallet, so that the wallet institution system 503 of the target digital wallet verifies the wallet payment password;

[0203] In the case of verification, the digital wallet system 501 sends a sub-wallet opening request to the wallet institution system 503 of the target digital wallet, and the wallet institution system 503 of the target digital wallet generates a digital currency sub-wallet corresponding to the target digital wallet and the target merchant, and returns a sub-wallet opening result to the digital wallet system 501;

[0204] The digital wallet system 501 sends a payment mark generation request to the mark service provider 502 in a case where it is determined that the wallet opening is successful according to the wallet opening result;

[0205] The mark service provider 502 generates a payment mark corresponding to the digital currency sub-wallet, and then returns a payment mark generation result to the digital wallet system 501.

[0206] Optionally, the digital wallet system is further configured to:

[0207] Before receiving the payment mark acquisition request of the user, the merchant list of the user is acquired from the mark service provider and sent to the terminal for display, so that the user selects one or more merchants from the merchant list as the target merchant; or

[0208] Before receiving the payment mark acquisition request of the user, the digital wallet list of the user is acquired and sent to the terminal for display, so that the user selects the target digital wallet from the digital wallet list.

[0209] Optionally, the digital wallet system is further configured to:

[0210] After the digital wallet list of the user is acquired and sent to the terminal for display, in response to the operation of the user selecting the target digital wallet from the digital wallet list, the merchant list corresponding to the target digital wallet is acquired and sent to the terminal for display, so that the user selects one or more merchants from the merchant list corresponding to the target digital wallet as the target merchant.

[0211] Optionally, the digital wallet system is further configured to: after the user selects one or more merchants from the merchant list as the target merchant, the account information of the target merchant is acquired, and the account information of the target merchant is verified and confirmed to be verified.

[0212] Optionally, the digital wallet system acquires the account information of the target merchant, comprising:

[0213] It is judged whether the account information of the target merchant exists in the local storage device; if yes, the account information of the target merchant is acquired from the local storage device; otherwise, the account information of the target merchant is acquired from the merchant institution system of the target merchant, and the acquired account information of the target merchant is stored in the local storage device.

[0214] Optionally, the digital wallet system verifies the account information of the target merchant, comprising: verifying whether the real name information and the communication information of the target merchant are consistent; if yes, the verification is passed; otherwise, the verification is failed.

[0215] Optionally, after the label service provider generates the payment label corresponding to the digital currency sub-wallet, the label service provider pushes the payment label to a wallet agency system of the target digital wallet; the wallet agency system of the target digital wallet pushes the payment label to a merchant agency system of the target merchant; the merchant agency system of the target merchant pushes the payment label to a merchant server system of the target merchant;

[0216] After the merchant server system of the target merchant receives the payment label, the merchant server system of the target merchant returns a response message to the merchant agency system of the target merchant; after the merchant agency system of the target merchant receives the response message returned by the merchant agency system of the target merchant, the merchant agency system of the target merchant returns a response message to the wallet agency system of the target digital wallet; after the wallet agency system of the target digital wallet receives the response message returned by the merchant agency system of the target merchant, the wallet agency system of the target digital wallet returns a response message to the label service provider; after the label service provider receives the response message returned by the wallet agency system of the target digital wallet, the label service provider generates the payment label generation result;

[0217] Optionally, the merchant server system of the target merchant pushes the payment label to a merchant terminal of the target merchant, so that the merchant terminal of the target merchant displays the message pushed by the merchant server system of the target merchant.

[0218] Optionally, the digital wallet system is further configured to: before sending the sub-wallet opening request to the wallet agency system of the target digital wallet, confirm that there is no digital currency sub-wallet corresponding to the target digital wallet and the target merchant.

[0219] Optionally, the payment label acquisition request includes: a plurality of consumption accounts of the user in the target merchant;

[0220] The digital wallet system sends a payment label generation request to a label service provider, including: sending a payment label generation request corresponding to each of the consumption accounts to the label service provider, respectively, so that the label service provider generates one payment label corresponding to each of the consumption accounts, respectively.

[0221] Optionally, the digital wallet system is further configured to:

[0222] After generating the digital currency sub-wallet corresponding to the target digital wallet and the target merchant, in response to the user's limit query request for a to-be-queried sub-wallet, the sub-wallet limit of the to-be-queried sub-wallet is acquired and sent to a terminal for display; or,

[0223] After the digital currency sub-wallet corresponding to the target digital wallet and the target merchant is generated, a quota modification request of the user is received, a to-be-adjusted sub-wallet and a target quota of the to-be-adjusted sub-wallet are parsed from the quota modification request, and the to-be-adjusted sub-wallet and the target quota of the to-be-adjusted sub-wallet are sent to a wallet agency system corresponding to the to-be-adjusted sub-wallet, so that the wallet agency system corresponding to the to-be-adjusted sub-wallet adjusts a sub-wallet quota of the to-be-adjusted sub-wallet to the target quota.

[0224] Optionally, the digital wallet system is further configured to: before receiving the quota modification request of the user, obtain a current quota of the to-be-adjusted sub-wallet, generate a sub-wallet quota management page according to the current quota of the to-be-adjusted sub-wallet, and send the sub-wallet quota management page to a terminal for display, so that the user sets a target quota of the to-be-adjusted sub-wallet through an operation on the sub-wallet management page.

[0225] Optionally, the digital wallet system is further configured to: after the digital currency sub-wallet corresponding to the target digital wallet and the target merchant is generated, in response to a payment request of the user based on the target sub-wallet, verifying the payment request to determine that a to-be-paid amount is less than or equal to a sub-wallet quota of the target sub-wallet.

[0226] Optionally, the digital wallet system is further configured to: after receiving the payment mark generation result returned by the marking service provider, obtaining a risk control level of the target digital wallet and consumption history data of a consumption account of the user in the target merchant; and determining a payment quota of a payment mark corresponding to the consumption account according to the consumption history data of the consumption account and the risk control level.

[0227] According to a fifth aspect of the embodiment of the present application, a payment marking electronic device based on a digital currency sub-wallet is provided, comprising:

[0228] one or more processors;

[0229] a storage device configured to store one or more programs,

[0230] When the one or more programs are executed by the one or more processors, the one or more processors implement the method provided by the first aspect of the embodiment of the present application.

[0231] According to a sixth aspect of the embodiment of the present application, a computer readable medium is provided, which stores a computer program, and the program is executed by a processor to implement the method provided by the first aspect of the embodiment of the present application.

[0232] Figure 6An exemplary system architecture 600 of the digital currency sub-wallet based payment tokenization method or the digital currency sub-wallet based payment tokenization apparatus to which embodiments of the present application can be applied is shown.

[0233] As shown in Figure 6 The system architecture 600 can include terminal devices 601, 602, 603, a network 604 and a server 605. The network 604 is a medium for providing communication links between the terminal devices 601, 602, 603 and the server 605. The network 604 can include various connection types, such as wired, wireless communication links or fiber optic cables, etc.

[0234] The users can use the terminal devices 601, 602, 603 to interact with the server 605 through the network 604 to receive or send messages, etc. Various communication client applications can be installed on the terminal devices 601, 602, 603, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0235] The terminal devices 601, 602, 603 can be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers and desktop computers, etc.

[0236] The server 605 can be a server providing various services, such as a background management server supporting shopping websites browsed by users using the terminal devices 601, 602, 603 (only as an example). The background management server can analyze and process received product information query requests and other data, and feed back the processing results (such as target push information, product information - only as examples) to the terminal devices.

[0237] It should be noted that the digital currency sub-wallet based payment tokenization method provided by the embodiments of the present application is generally executed by the server 605, and accordingly, the digital currency sub-wallet based payment tokenization apparatus is generally provided in the server 605.

[0238] It should be understood that Figure 6 the number of terminal devices, networks and servers in

[0239] Reference is made to Figure 7 which shows a structural schematic diagram of a computer system 700 of a terminal device suitable for implementing the embodiments of the present application. Figure 7 The terminal device shown is only an example and should not bring any limitation to the functions and use range of the embodiments of the present application.

[0240] AsFigure 7 As shown, the computer system 700 includes a central processing unit (CPU) 701 which can perform various appropriate actions and processes in accordance with programs stored in a read only memory (ROM) 702 or loaded from the storage section 708 into a random access memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0241] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including a display such as a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as necessary. A removable recording medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is attached to the drive 710 as necessary, so that a computer program read therefrom is installed into the storage section 708 as necessary.

[0242] In particular, the processes described above with reference to the flowcharts can be implemented as a computer software program in accordance with the embodiments disclosed herein. For example, the embodiments disclosed herein include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing program code for executing the methods illustrated by the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via the communication section 709, and / or installed from the removable recording medium 711. When the computer program is executed by the central processing unit (CPU) 701, the above-described functions defined in the system of the present application are performed.

[0243] It should be noted that the computer-readable medium shown in the present application can 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, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, 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 application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or component. In the present application, the computer-readable signal medium can include a data signal carried in a baseband or as a part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to an electromagnetic signal, an optical signal or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, which can send, propagate or transmit a program for use by or in conjunction with an instruction execution system, device or component. The program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0244] The flow diagrams and block diagrams in the drawings are schematic illustrations of possible architectures, functions and operations of systems, methods and computer program products in accordance with various embodiments of the present application. In this regard, each block in the flow diagrams or block diagrams can represent a module, a segment, or a portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks may be executed in the reverse order, depending on the functionality involved. It will also be noted that each block of the block diagrams or flow diagrams, and combinations of blocks in the block diagrams or flow diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or operations, or combinations of special purpose hardware and computer instructions.

[0245] The modules described in the embodiments of the present application can be implemented in the form of software or hardware. The modules described can also be arranged in a processor, for example, a processor can be described as including a request parsing module, a password verification module, a sub-wallet opening module, and a token generation module. In some cases, the names of these modules do not constitute a limitation on the modules themselves, for example, the request parsing module can also be described as a "module for sending a payment token generation request to a token service provider".

[0246] As another aspect, the present application also provides a computer readable medium, which can be included in the device described in the above embodiments, or can exist independently without being assembled into the device. The computer readable medium described above carries one or more programs, which, when executed by the device, cause the device to include:

[0247] parsing a target digital wallet, a target merchant, and a wallet payment password corresponding to the target digital wallet from a payment token acquisition request of a user;

[0248] sending the wallet payment password to a wallet institution system of the target digital wallet, so that the wallet institution system of the target digital wallet verifies the wallet payment password, and receiving a verification result returned by the wallet institution system of the target digital wallet;

[0249] in the case of verification, sending a sub-wallet opening request to the wallet institution system of the target digital wallet, so that the wallet institution system of the target digital wallet generates a digital currency sub-wallet corresponding to the target digital wallet and the target merchant, and receiving a sub-wallet opening result returned by the wallet institution system of the target digital currency wallet;

[0250] in the case of successful wallet opening, sending a payment token generation request to a token service provider, so that the token service provider generates a payment token corresponding to the digital currency sub-wallet, and receiving a payment token generation result returned by the token service provider.

[0251] According to the technical solution of the embodiments of the present application, the user can pre-establish the tokenization of payment on the digital wallet side, which is convenient for the user to centrally manage the tokenization of payment, thereby improving the convenience and security of the user using tokenization payment.

[0252] The above specific embodiments do not constitute a limitation on the protection scope of the present application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A payment tokenization method based on a digital currency sub-wallet, characterized in that, Applied to digital wallet systems, including: The target digital wallet, target merchant, and wallet payment password corresponding to the target digital wallet are parsed from the user's payment token retrieval request. The wallet payment password is sent to the wallet institution system of the target digital wallet so that the wallet institution system of the target digital wallet verifies the wallet payment password and receives the verification result returned by the wallet institution system of the target digital wallet. If the verification is successful, a sub-wallet opening request is sent to the wallet institution system of the target digital wallet, so that the wallet institution system of the target digital wallet generates a digital currency sub-wallet corresponding to the target digital wallet and the target merchant, and receives the sub-wallet opening result returned by the wallet institution of the target digital wallet; Upon successful wallet opening, a payment token generation request is sent to the token service provider to enable the token service provider to generate a payment token corresponding to the digital currency sub-wallet, and the payment token generation result returned by the token service provider is received.

2. The payment tokenization method as described in claim 1, characterized in that, Also includes: Before receiving a user's payment tag acquisition request, the system obtains the user's merchant list from the tag service provider and sends it to the terminal for display, so that the user can select one or more merchants from the merchant list as the target merchants; or, Before receiving a user's payment token acquisition request, the system obtains the user's digital wallet list and sends it to the terminal for display, so that the user can filter the target digital wallet from the digital wallet list.

3. The payment tokenization method as described in claim 2, characterized in that, Also includes: After obtaining the user's list of digital wallets and sending it to the terminal for display, in response to the user's operation of filtering target digital wallets from the list of digital wallets, a list of merchants corresponding to the target digital wallets is obtained and sent to the terminal for display, so that the user can filter one or more merchants from the list of merchants corresponding to the target digital wallets as the target merchants.

4. The payment tokenization method as described in claim 2, characterized in that, Also includes: After the user selects one or more merchants from the merchant list as the target merchants, the account information of the target merchants is obtained, the account information of the target merchants is verified, and the verification is confirmed to be successful.

5. The payment tokenization method as described in claim 4, characterized in that, Obtain the account information of the target merchant, including: Determine whether the target merchant's account information exists in the local storage device; if so, retrieve the target merchant's account information from the local storage device; otherwise, retrieve the target merchant's account information from the target merchant's merchant organization system and store the retrieved target merchant's account information into the local storage device.

6. The payment tokenization method as described in claim 4, characterized in that, The account information of the target merchant is verified, including: verifying whether the real-name information and communication information of the target merchant are consistent; if so, the verification passes; otherwise, the verification fails.

7. The payment tokenization method as described in claim 6, characterized in that, After generating a payment token corresponding to the digital currency sub-wallet, the token service provider pushes the payment token to the wallet institution system of the target digital wallet; the wallet institution system of the target digital wallet pushes the payment token to the merchant institution system of the target merchant; the merchant institution system of the target merchant pushes the payment token to the merchant server system of the target merchant. After receiving the payment token, the merchant server system of the target merchant returns a response message to the merchant organization system of the target merchant; after receiving the response message returned by the merchant server system of the target merchant, the merchant organization system of the target merchant returns a response message to the wallet organization system of the target digital wallet; after receiving the response message returned by the merchant organization system of the target digital wallet, the wallet organization system of the target digital wallet returns a response message to the token service provider; after receiving the response message returned by the wallet organization system of the target digital wallet, the token service provider generates the payment token generation result. Specifically, the merchant server system of the target merchant pushes the payment token to the merchant terminal of the target merchant, so that the merchant terminal of the target merchant displays the message pushed by the merchant server system of the target merchant.

8. The payment tokenization method as described in claim 1, characterized in that, Also includes: Before sending a sub-wallet opening request to the wallet institution system of the target digital wallet, it is confirmed that there is no digital currency sub-wallet corresponding to the target digital wallet and the target merchant.

9. The payment tokenization method as described in claim 8, characterized in that, The payment token acquisition request includes: multiple consumer accounts of the user in the target merchant; Sending a payment token generation request to the token service provider includes: sending a payment token generation request corresponding to each of the consumer accounts to the token service provider, so that the token service provider generates a payment token corresponding to each of the consumer accounts.

10. The payment tokenization method as described in any one of claims 1-9, characterized in that, Also includes: After generating a digital currency sub-wallet corresponding to the target digital wallet and the target merchant, in response to the user's request for a limit query on the sub-wallet to be queried, the sub-wallet limit of the sub-wallet to be queried is obtained and sent to the terminal for display; or, After generating a digital currency sub-wallet corresponding to the target digital wallet and the target merchant, the system receives the user's limit modification request, parses the sub-wallet whose limit needs to be adjusted and its target limit from the limit modification request, and sends the sub-wallet whose limit needs to be adjusted and its target limit to the wallet institution system corresponding to the sub-wallet whose limit needs to be adjusted, so that the wallet institution system corresponding to the sub-wallet whose limit needs to be adjusted adjusts the sub-wallet limit of the sub-wallet whose limit needs to be adjusted to the target limit.

11. The payment tokenization method as described in claim 10, characterized in that, Also includes: Before receiving the user's limit modification request, the current limit of the sub-wallet to be adjusted is obtained, a sub-wallet limit management page is generated based on the current limit of the sub-wallet to be adjusted, and sent to the terminal for display, so that the user can set the target limit of the sub-wallet to be adjusted through the operation on the sub-wallet limit management page.

12. The payment tokenization method as described in claim 10, characterized in that, Also includes: After generating a digital currency sub-wallet corresponding to the target digital wallet and the target merchant, in response to the user's payment request based on the target sub-wallet, the payment request is verified to determine that the amount to be paid is less than or equal to the sub-wallet limit of the target sub-wallet.

13. The payment tokenization method as described in any one of claims 1-9, characterized in that, Also includes: After receiving the payment token generation result returned by the token service provider, the risk control level of the target digital wallet and the consumption history data of the user's consumption account in the target merchant are obtained; based on the consumption history data of the consumption account and the risk control level, the payment limit of the payment token corresponding to the consumption account is determined.

14. A payment method based on a digital currency sub-wallet, characterized in that, include: Receive a payment request sent by the target merchant's backend system in response to the user's consumption request. The payment request includes the payment token and payment amount of the user's digital currency sub-wallet corresponding to the target merchant. Based on the payment token, determine the target operating institution's back-end system corresponding to the digital currency sub-wallet, and send a payment request message to the target operating institution's back-end system; The system receives digital currency transferred from the target operator's back-end system in response to the payment request message. If the transferred digital currency matches the payment amount, the system pushes payment result information to the target merchant's back-end system so that the target merchant's back-end system can push payment success information to the user. The payment token is generated using the payment tokenization method described in any one of claims 1-13.

15. A payment tokenization device based on a digital currency sub-wallet, characterized in that, Applied to digital wallet systems, including: The request parsing module parses the target digital wallet, target merchant, and wallet payment password corresponding to the target digital wallet from the user's payment token acquisition request; The password verification module sends the wallet payment password to the wallet institution system of the target digital wallet, so that the wallet institution system of the target digital wallet verifies the wallet payment password and receives the verification result returned by the wallet institution system of the target digital wallet; The sub-wallet opening module, upon successful verification, sends a sub-wallet opening request to the wallet institution system of the target digital wallet, so that the wallet institution system of the target digital wallet generates a digital currency sub-wallet corresponding to the target digital wallet and the target merchant, and receives the sub-wallet opening result returned by the wallet institution of the target digital wallet; The token generation module, upon successful wallet opening, sends a payment token generation request to the token service provider, so that the token service provider generates a payment token corresponding to the digital currency sub-wallet, and receives the payment token generation result returned by the token service provider.

16. A payment tokenization system based on a digital currency sub-wallet, characterized in that, include: Digital wallet systems, token service providers, and wallet institution systems; among them, The digital wallet system parses the target digital wallet, target merchant, and wallet payment password corresponding to the target digital wallet from the user's payment token acquisition request; and sends the wallet payment password to the wallet institution system of the target digital wallet so that the wallet institution system of the target digital wallet can verify the wallet payment password; If the verification is successful, the digital wallet system sends a sub-wallet opening request to the wallet institution system of the target digital wallet. The wallet institution system of the target digital wallet generates a digital currency sub-wallet corresponding to the target digital wallet and the target merchant, and returns the sub-wallet opening result to the digital wallet system. If the digital wallet system determines that the wallet has been successfully opened based on the wallet opening result, it sends a payment token generation request to the token service provider. The token service provider generates a payment token corresponding to the digital currency sub-wallet and then returns the payment token generation result to the digital wallet system.

17. A payment tokenization electronic device based on a digital currency sub-wallet, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-14.

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

Images