Service processing method and device of scene wallet, service interaction method and device and equipment

By introducing scenario wallets in Internet services, flexibly configure merchant collections and activities according to different business scenarios, the problem of single existing wallet functions is solved, and more efficient user activity and retention rate is achieved.

CN119005961APending Publication Date: 2024-11-22RAJAX NETWORK &TECHNOLOGY (SHANGHAI) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310581864.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-22
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The existing wallet functions are too single in the Internet business scenario and cannot fully meet diversified business needs, resulting in limited frequency-elevating customer locking effect.

Method used

A business processing method for scenario wallets is proposed. By creating multiple scenario wallets, flexibly configure merchant collections according to different business scenarios, users can consume, recharge and withdraw cash within specific merchant collections, and use timed tasks and activity configurations to improve user activity .

Benefits of technology

It realizes the flexibly creating and configuring scenario wallets based on different business scenarios, meets users' diversified consumption needs, improves user activity and retention rates, and further improves the frequency-elevating customer locking effect.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119005961A_ABST
    Figure CN119005961A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses a business processing method, a business interaction method, a business processing device and business interaction equipment for a scene wallet. The business processing method comprises the following steps: creating at least one scene wallet; for any scene wallet, establishing a corresponding relationship between the scene wallet and a merchant set according to the merchant set configuration information of the scene wallet; receiving a user consumption request of a target user for a specified scene wallet or a specified merchant; and payment processing is completed by using the specified scene wallet or the scene wallet corresponding to the target merchant set to which the specified merchant belongs. According to the embodiment of the invention, the consumption demands of users in different business scenes can be fully met, and compared with a platform wallet, the frequency-increasing and customer-locking effects are further improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of Internet business, and specifically to a business processing method, business interaction method, device and computing equipment, and computer storage medium of a scenario wallet. Background Art

[0002] At present, general shopping applications have built-in wallet functions. Users can pre-charge their wallets. Whenever users make purchases, they can pay directly with their wallets without calling up third-party payment applications, thus simplifying the user's payment path. At the same time, users' pre-charge behavior will encourage users to make multiple purchases, improve user activity and retention rate, and to a certain extent achieve the effect of increasing frequency and locking in customers.

[0003] However, the existing wallets have relatively simple functions and cannot fully meet the needs of rich and diverse business scenarios on the Internet, which limits their effectiveness in increasing frequency and locking in customers. Summary of the invention

[0004] In view of the above problems, embodiments of the present invention are proposed to provide a business processing method, business interaction method, device, computing device, and computer storage medium of a scenario wallet that overcomes the above problems or at least partially solves the above problems.

[0005] According to one aspect of an embodiment of the present invention, a business processing method of a scenario wallet is provided, including:

[0006] Create at least one scenario wallet;

[0007] For any scenario wallet, establish a corresponding relationship between the scenario wallet and the merchant set according to the merchant set configuration information of the scenario wallet;

[0008] Receive consumption requests from target users for designated scenario wallets or designated merchants;

[0009] The payment process is completed using the designated scenario wallet or the scenario wallet corresponding to the target merchant set to which the designated merchant belongs.

[0010] In an optional manner, after receiving a user consumption request from a target user for a designated merchant, the method further includes:

[0011] It is queried whether the designated merchant belongs to the merchant set corresponding to the available scenario wallet of the target user. If so, the merchant set corresponding to the available scenario wallet of the target user including the designated merchant is determined as the target merchant set.

[0012] In an optional manner, if it is determined that there are multiple target merchant sets, completing the payment process using the scenario wallet corresponding to the target merchant set to which the designated merchant belongs further includes:

[0013] Based on the selection of multiple scenario wallets corresponding to multiple target merchant sets by the system or the target user, the selected scenario wallet is determined from the multiple scenario wallets to complete the payment processing.

[0014] In an optional manner, after receiving a user consumption request from a target user for a specified scenario wallet, the method further includes:

[0015] Query the target merchant set corresponding to the specified scenario wallet;

[0016] According to the target merchant set, obtaining a target merchant list for display;

[0017] The specific method of completing the payment process by using the designated scenario wallet is as follows: for the user consumption behavior of the target user at any merchant in the target merchant list, the payment process is completed by using the designated scenario wallet.

[0018] In an optional manner, after establishing a correspondence between the scenario wallet and the merchant set according to the merchant set configuration information of the scenario wallet for any scenario wallet, the method further includes:

[0019] According to the merchant set configuration update information for any scenario wallet, the correspondence between the scenario wallet and the merchant set is updated.

[0020] In an optional manner, the creating at least one scenario wallet further includes:

[0021] According to the activity configuration information for any scenario wallet, configure the corresponding activity for the scenario wallet.

[0022] In an optional manner, the creating at least one scenario wallet further includes:

[0023] According to the business element configuration information for any scenario wallet, the corresponding business element is configured for the scenario wallet.

[0024] In an optional manner, before receiving a user consumption request from a target user for a designated scenario wallet or a designated merchant, the method further includes:

[0025] Receive a user recharge request from a target user for a specified scenario wallet;

[0026] The designated scenario wallet is recharged according to the user recharge request, and the user recharge amount and the corresponding validity period are recorded in the designated scenario wallet.

[0027] In an optional manner, after receiving the user recharge request of the target user for the specified scenario wallet, the method further includes:

[0028] Determine whether the specified scenario wallet is configured with corresponding activities;

[0029] If yes, extract the user gift amount from the activity configuration information, recharge the designated scenario wallet based on the user recharge amount and the user gift amount, and record the user recharge amount and the corresponding first validity period, the user gift amount and the corresponding second validity period in the designated scenario wallet;

[0030] If not, recharge processing is performed based on the user's recharge amount, and the user's recharge amount and the corresponding first validity period are recorded.

[0031] In an optional manner, the method further includes:

[0032] Receive a withdrawal request from a target user for a specified scenario wallet;

[0033] The designated scenario wallet is processed for withdrawal according to the user withdrawal request, and the user recharge amount recorded in the designated scenario wallet is updated according to the user withdrawal amount.

[0034] In an optional manner, the method further includes:

[0035] Starting a first scheduled task according to the validity period corresponding to the user recharge amount;

[0036] According to the triggering of the first scheduled task, the designated scenario wallet is processed for withdrawal, and the user recharge amount recorded in the designated scenario wallet is updated.

[0037] In an optional manner, the method further includes:

[0038] Starting a second scheduled task according to the validity period corresponding to the user recharge amount;

[0039] Based on the triggering of the second scheduled task, a message is pushed to the target user to remind the user that the recharge amount is about to expire.

[0040] According to another aspect of an embodiment of the present invention, a business interaction method of a scenario wallet is provided, the method being implemented based on at least one pre-created scenario wallet, wherein a corresponding relationship between the scenario wallet and the merchant set is established according to merchant set configuration information of the scenario wallet; the method comprising:

[0041] Monitor user spending requests for wallets in specified scenarios;

[0042] The user consumption request is sent to the server, so that the server can use the specified scenario wallet to complete the payment processing of the target user's user consumption behavior for the specified merchant.

[0043] In an optional manner, before monitoring a user consumption request for a wallet in a specified scenario, the method further includes:

[0044] After the target user specifies a designated merchant for consumption, displaying at least one available scenario wallet of the target user corresponding to the target merchant set to which the designated merchant belongs;

[0045] The monitoring system or the target user selects any available scenario wallet to determine the designated scenario wallet.

[0046] In an optional manner, after sending the user consumption request to the server, the method further includes:

[0047] Displaying a target merchant list; wherein the target merchant list is a subset of the target merchant set corresponding to the specified scenario wallet;

[0048] Monitor the target user's user consumption behavior at any designated merchant in the target merchant list, and initiate a request for payment processing of the target user's user consumption behavior at the designated merchant using the designated scenario wallet.

[0049] In an optional manner, the displaying of at least one available scenario wallet of the target user corresponding to the target merchant set to which the designated merchant belongs specifically comprises: displaying, on the payment page, a business element corresponding to at least one available scenario wallet of the target user corresponding to the target merchant set to which the designated merchant belongs;

[0050] The business elements corresponding to the at least one available scenario wallet include: usage control elements and available amount display elements.

[0051] In an optional manner, before monitoring the user consumption request for the specified scenario wallet, the method further includes: displaying a business element corresponding to at least one available scenario wallet in at least one primary wallet page;

[0052] The business elements corresponding to the at least one available scenario wallet include: usage control elements and available amount display elements.

[0053] In an optional manner, if there are multiple available scenario wallets, displaying the business element corresponding to at least one available scenario wallet further includes: displaying the business elements corresponding to the multiple available scenario wallets according to the display priorities of the multiple available scenario wallets.

[0054] In an optional manner, the display priority of the multiple available scenario wallets is determined according to the available amount of the available scenario wallet, the validity period of the available amount, or the merchant set corresponding to the available scenario wallet.

[0055] In an optional manner, the method further includes: displaying a service element corresponding to at least one unavailable scenario wallet in at least one primary wallet page;

[0056] The business element corresponding to the at least one unavailable scenario wallet includes: a merchant resource location display element and / or an activity information display element.

[0057] In an optional manner, displaying the business element corresponding to at least one available scenario wallet further includes: displaying the business element corresponding to each available scenario wallet in a card form according to a preset card template.

[0058] In an optional manner, the method further includes: displaying a recharge control element of at least one scenario wallet in at least one primary wallet page;

[0059] Monitor the target user's recharge operation for the specified scenario wallet and send the user recharge request to the server.

[0060] In an optional manner, the method further includes: displaying a withdrawal control element of at least one scenario wallet in at least one primary wallet page;

[0061] Monitor the target user's withdrawal operations for the specified scenario wallet and send the user withdrawal request to the server.

[0062] In an optional manner, the method further includes: receiving a contact message pushed by the server to remind the user that the recharge amount is about to expire.

[0063] According to another aspect of an embodiment of the present invention, a business processing device of a scenario wallet is provided, the device comprising:

[0064] A creation module, used to create at least one scenario wallet;

[0065] A configuration module, used for establishing a correspondence between a scenario wallet and a merchant set according to the merchant set configuration information of the scenario wallet for any scenario wallet;

[0066] A receiving module, used to receive a target user's consumption request for a specified scenario wallet or a specified merchant;

[0067] The processing module is used to complete the payment processing by using the designated scenario wallet or the scenario wallet corresponding to the target merchant set to which the designated merchant belongs.

[0068] In an optional manner, the device further includes:

[0069] The query module is used to query whether the designated merchant belongs to the merchant set corresponding to the available scenario wallet of the target user, and if so, determine the merchant set corresponding to the available scenario wallet of the target user including the designated merchant as the target merchant set.

[0070] In an optional manner, the processing module is further used for: if it is determined that there are multiple target merchant sets, based on the system or the target user's selection of multiple scenario wallets corresponding to the multiple target merchant sets, determining the selected scenario wallet from the multiple scenario wallets to complete the payment processing.

[0071] In an optional manner, the device further includes:

[0072] A query module, used to query the target merchant set corresponding to the specified scenario wallet; and obtain a target merchant list for display according to the target merchant set;

[0073] The processing module is further used to: use the specified scenario wallet to complete payment processing for the user consumption behavior of the target user at any merchant in the target merchant list.

[0074] In an optional manner, the configuration module is further used to: update the correspondence between the scenario wallet and the merchant set according to the merchant set configuration update information for any scenario wallet.

[0075] In an optional manner, the creation module is further used to: configure corresponding activities for any scenario wallet according to the activity configuration information for the scenario wallet.

[0076] In an optional manner, the creation module is further used to: configure corresponding business elements for any scenario wallet according to the business element configuration information for the scenario wallet.

[0077] In an optional manner, the device also includes: a recharge module, used to receive a user recharge request from a target user for a specified scenario wallet; recharge the specified scenario wallet according to the user recharge request, and record the user recharge amount and the corresponding validity period in the specified scenario wallet.

[0078] In an optional manner, the recharge module is further used for:

[0079] Determine whether the specified scenario wallet is configured with corresponding activities;

[0080] If yes, extract the user gift amount from the activity configuration information, recharge the designated scenario wallet based on the user recharge amount and the user gift amount, and record the user recharge amount and the corresponding first validity period, the user gift amount and the corresponding second validity period in the designated scenario wallet;

[0081] If not, recharge processing is performed based on the user's recharge amount, and the user's recharge amount and the corresponding first validity period are recorded.

[0082] In an optional manner, the device also includes: a withdrawal module, used to receive a user withdrawal request from a target user for a specified scenario wallet; perform withdrawal processing on the specified scenario wallet according to the user withdrawal request, and update the user recharge amount recorded in the specified scenario wallet according to the user withdrawal amount.

[0083] In an optional manner, the device also includes: a withdrawal module, which is used to start a first scheduled task according to the validity period corresponding to the user recharge amount; based on the triggering of the first scheduled task, the designated scenario wallet is withdrawn and the user recharge amount recorded in the designated scenario wallet is updated.

[0084] In an optional manner, the device also includes: a message triggering module, which is used to start a second scheduled task according to the validity period corresponding to the user's recharge amount; and based on the triggering of the second scheduled task, push a contact message to the target user to remind the user that the recharge amount is about to expire.

[0085] According to another aspect of an embodiment of the present invention, a service interaction device of a scenario wallet is provided, the device being implemented based on at least one pre-created scenario wallet, wherein a corresponding relationship between the scenario wallet and the merchant set is established according to merchant set configuration information of the scenario wallet; the device comprising:

[0086] Monitoring module, used to monitor user consumption requests for wallets in specified scenarios;

[0087] The request module is used to send the user consumption request to the server, so that the server can use the specified scenario wallet to complete the payment processing of the target user's user consumption behavior for the specified merchant.

[0088] In an optional manner, the device further includes: a display module, configured to display at least one available scenario wallet of the target user corresponding to the target merchant set to which the designated merchant belongs after the target user designates a designated merchant for consumption;

[0089] The monitoring module is further used to: monitor the selection of any available scenario wallet by the system or the target user to determine the designated scenario wallet.

[0090] In an optional manner, the device further includes: a display module, configured to display a target merchant list; wherein the target merchant list is a subset of the target merchant set corresponding to the specified scenario wallet;

[0091] The monitoring module is further used to monitor the target user's consumption behavior at any designated merchant in the target merchant list; the request module is further used to initiate a request for payment processing of the target user's consumption behavior at the designated merchant using the designated scenario wallet.

[0092] In an optional manner, the display module is further used to: display on the payment page a business element corresponding to at least one available scenario wallet of the target user corresponding to the target merchant set to which the designated merchant belongs;

[0093] The business elements corresponding to the at least one available scenario wallet include: usage control elements and available amount display elements.

[0094] In an optional manner, the display module is further used to: display a business element corresponding to at least one available scenario wallet in at least one primary wallet page;

[0095] The business elements corresponding to the at least one available scenario wallet include: usage control elements and available amount display elements.

[0096] In an optional manner, if there are multiple available scenario wallets, the display module is further used to: display business elements corresponding to the multiple available scenario wallets according to the display priorities of the multiple available scenario wallets.

[0097] In an optional manner, the display priority of the multiple available scenario wallets is determined according to the available amount of the available scenario wallet, the validity period of the available amount, or the merchant set corresponding to the available scenario wallet.

[0098] In an optional manner, the display module is further used to: display a business element corresponding to at least one unavailable scenario wallet in at least one primary wallet page;

[0099] The business element corresponding to the at least one unavailable scenario wallet includes: a merchant resource location display element and / or an activity information display element.

[0100] In an optional manner, the display module is further used to: display the business elements corresponding to each available scenario wallet in the form of a card according to a preset card template.

[0101] In an optional manner, the display module is further used to: display at least one recharge control element of a scenario wallet in at least one primary wallet page;

[0102] The monitoring module is also used to monitor the target user's recharge operation for the specified scenario wallet; the request module is also used to send a user recharge request to the server.

[0103] In an optional manner, the display module is further used to: display a withdrawal control element of at least one scenario wallet in at least one primary wallet page;

[0104] The monitoring module is also used to monitor the target user's withdrawal operation for the specified scenario wallet; the request module is also used to send the user withdrawal request to the server.

[0105] In an optional manner, the device also includes: a receiving module, which is used to receive a contact message pushed by the server to remind the user that the recharge amount is about to expire.

[0106] According to another aspect of an embodiment of the present invention, there is provided a computing device, comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus;

[0107] The memory is used to store at least one executable instruction, which enables the processor to perform operations corresponding to the business processing method of the above-mentioned scenario wallet, and / or the executable instruction enables the processor to perform operations corresponding to the business interaction method of the above-mentioned scenario wallet.

[0108] According to another aspect of an embodiment of the present invention, a computer storage medium is provided, wherein at least one executable instruction is stored in the storage medium, wherein the executable instruction enables a processor to perform operations corresponding to the business processing method of the above-mentioned scenario wallet, and / or the executable instruction enables a processor to perform operations corresponding to the business interaction method of the above-mentioned scenario wallet.

[0109] The business processing method, business interaction method, device, computing device, and computer storage medium of the scenario wallet provided in the embodiments of the present invention support flexible creation of scenario wallets according to the needs of different business scenarios, and support flexible configuration of the merchant set corresponding to the scenario wallet, thereby limiting the merchant usage scope of different scenario wallets to fully meet the consumption needs of users in different business scenarios. Compared with the platform wallet, it further improves the effect of increasing frequency and locking customers.

[0110] The above description is only an overview of the technical solution of the embodiment of the present invention. In order to more clearly understand the technical means of the embodiment of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiment of the present invention more obvious and easy to understand, the specific implementation method of the embodiment of the present invention is specifically listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0111] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the embodiments of the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0112] Figure 1 A flowchart of a business processing method of a scenario wallet according to an embodiment of the present invention is shown;

[0113] Figure 2 A flowchart of a business processing method of a scenario wallet according to another embodiment of the present invention is shown;

[0114] Figure 3a to Figure 3c A schematic diagram showing various usage links of a scenario wallet in an embodiment of the present invention is shown;

[0115] Figure 4 A flowchart of a business interaction method of a scenario wallet according to an embodiment of the present invention is shown;

[0116] Figure 5 A schematic diagram of the structure of a business processing device of a scenario wallet according to an embodiment of the present invention is shown;

[0117] Figure 6 A schematic diagram showing the structure of a business interaction device of a scenario wallet according to an embodiment of the present invention is shown;

[0118] Figure 7 A schematic diagram of the structure of a computing device according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0119] The exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present invention and to enable the scope of the present invention to be fully communicated to those skilled in the art.

[0120] In this article, the existing application built-in wallet is called a platform wallet. The platform wallet supports the consumption behavior of users in all merchants on the platform corresponding to the application, that is, users can use the platform wallet to make consumption payments at any merchant on the platform. The embodiment of the present invention is different from the prior art in that, in addition to the platform wallet, the embodiment of the present invention introduces a scenario wallet, which can be flexibly created by the platform according to the needs of different business scenarios to meet the needs of different business scenarios. In some optional implementations, the scenario wallet can serve the following scenarios: Example 1, the platform can select subsidized merchants, launch a scenario wallet for the subsidized merchant collection, and provide users with more recharge subsidies; Example 2, in order to further improve UE (such as customer unit price) and expand scenario-based consumption behavior, the platform can pre-select high-UE merchants and launch a scenario wallet for the high-UE merchant collection, so as to consume the recharge amount more efficiently. In short, by flexibly creating a scenario wallet and based on various usage links of the pre-built scenario wallet, the user's consumption needs for high-UE merchants are fully met, and the effect of frequency locking is further improved.

[0121] Figure 1 A flowchart of a business processing method of a scenario wallet according to an embodiment of the present invention is shown. Figure 1 As shown, the method comprises the following steps:

[0122] Step 101, create at least one scenario wallet.

[0123] Different from platform wallets, scenario wallets are wallets for specific business scenarios, and scenario wallets limit the scope of merchant use. Taking the scenario wallet for high UE merchant collection as an example, it limits the merchant use scope to high UE merchant collection.

[0124] Specifically, creating a scenario wallet may include: configuring corresponding business elements for the scenario wallet based on the pre-built usage link and configuring corresponding activities for the scenario wallet based on operational needs. The usage link of the scenario wallet includes but is not limited to: consumption link, recharge link, withdrawal link, opening link and closing link; the business elements of the scenario wallet include but are not limited to: information display element class, interactive control element class; the activities of the scenario wallet include but are not limited to: recharge and delivery activities, etc.

[0125] Step 102: For any scenario wallet, a corresponding relationship between the scenario wallet and the merchant set is established according to the merchant set configuration information of the scenario wallet.

[0126] In order to meet the needs of different business scenarios, the platform can create multiple scenario wallets at the same time and configure each scenario wallet with its own merchant set. The merchant sets corresponding to different scenario wallets can be the same or different (for example, the merchant sets corresponding to different scenario wallets have intersections or are completely different). That is, according to the needs of different business scenarios, the merchant usage scope of different scenario wallets can be flexibly configured.

[0127] Taking the scenario wallet for high-UE merchant sets as an example, the platform can pre-select high-UE merchants, use the selection results as merchant set configuration information, and establish a correspondence between the scenario wallet and the merchant set based on the selection results to limit the scope of use of the scenario wallet.

[0128] The embodiments of the present invention support the creation of wallets for various business scenarios. For example, separate scenario wallets are created for food scenarios, afternoon tea scenarios, beauty and hairdressing scenarios, etc., but the present invention does not limit this.

[0129] Step 103: receiving a consumption request from a target user for a designated scenario wallet or a designated merchant.

[0130] In an embodiment of the present invention, the consumption link of the scenario wallet may include: a consumption link for a specified scenario wallet and / or a consumption link for a specified merchant.

[0131] Optionally, the target user can send a user consumption request for a specified scenario wallet. Specifically, the target user first specifies a scenario wallet, performs a usage operation of the specified scenario wallet, follows the consumption link for the specified scenario wallet, and initiates a consumption request for a merchant in the merchant set corresponding to the specified scenario wallet.

[0132] Optionally, the target user can also send a user consumption request to a designated merchant. Specifically, the target user specifies a merchant on the merchant page, initiates a user consumption request, follows the consumption link for the designated merchant, and finally calls up the scene wallet corresponding to the target merchant set to which the designated merchant belongs to complete the payment.

[0133] Step 104, complete the payment processing using the designated scenario wallet or the scenario wallet corresponding to the target merchant set to which the designated merchant belongs.

[0134] The business processing method of the scenario wallet provided in the embodiment of the present invention supports flexible creation of scenario wallets according to the needs of different business scenarios, and supports flexible configuration of the merchant set corresponding to the scenario wallet, thereby limiting the merchant use scope of different scenario wallets to fully meet the consumption needs of users in different business scenarios. Compared with the platform wallet, it further improves the effect of increasing frequency and locking customers.

[0135] Figure 2A flowchart of a business processing method of a scenario wallet according to another embodiment of the present invention is shown. Figure 2 As shown, the method comprises the following steps:

[0136] Step 201, create at least one scenario wallet.

[0137] Before creating a scenario wallet, the platform must first build various usage links of the scenario wallet. The usage links of the scenario wallet include but are not limited to: consumption link, recharge link, withdrawal link, activation link and closing link.

[0138] Figure 3a to Figure 3c A schematic diagram showing various usage links of a scenario wallet in an embodiment of the present invention is shown.

[0139] Figure 3a Schematic diagram of the activation link of a scenario wallet in an example of an embodiment of the present invention, such as Figure 3a As shown, add the business elements of the scenario wallet to the main page of my wallet, and optionally display each business element in the form of a card. For example, the food wallet is configured with a recharge activity. After the user clicks the activity control, enter the subpage of opening and recharging the food wallet. In this subpage, some merchants in the merchant set corresponding to the food wallet can also be displayed, so that users can view the merchant usage scope.

[0140] Figure 3b Schematic diagram of a recharge link of a scene wallet in an example of an embodiment of the present invention. The link is a recharge link when the scene wallet has been opened, such as Figure 3b As shown, add the card of the activated scene wallet to the main page of My Wallet. If the user wants to open other scene wallets, he can click More to enter the list page of other scene wallets to be opened. The user clicks on the activated food wallet card to enter the sub-page of the food wallet, which displays the recharge control and some merchants in the merchant set corresponding to the food wallet.

[0141] exist Figure 3b In the food wallet card, there is also a usage control "Go to Use", and the user clicks on the control to enter the consumption link for the specified scene wallet (not shown in the figure). In this consumption link, the target merchant list is displayed. The target merchant list is a subset of the target merchant set corresponding to the specified scene wallet. The user can select the merchant for consumption in the target merchant list. In another embodiment of the present invention, a consumption link for a specified merchant can also be built. The user specifies a merchant on the merchant page, initiates a user consumption request, and finally calls up the scene wallet corresponding to the target merchant set to which the specified merchant belongs to complete the payment.

[0142] exist Figure 3bIn the example, the card on the sub-page of the food wallet has a withdrawal control "Go to withdraw cash", and the user clicks the withdrawal control to enter the withdrawal link (not shown in the figure). The withdrawal link is used to support the return of the user's recharged amount in the scene wallet to the original recharge account.

[0143] Figure 3c Schematic diagram of a closing link of a scenario wallet in an example of an embodiment of the present invention, such as Figure 3c As shown, the "More" option of the card on the sub-page of the Food Wallet has a close control "Close Account". The user clicks the close control, and the sub-page pops up to display the "Please Withdraw First" page. The user clicks the withdrawal control to enter the withdrawal link (not shown in the figure). After the withdrawal is completed, return to the sub-page, and a pop-up window displays the confirmation page for closing the account. The user clicks to confirm the close, and the scene wallet is closed.

[0144] Optionally, the platform wallet and the scene wallet can be closed together in the closing link of the platform wallet. When the user chooses to close the platform wallet, the available balance information of the platform wallet and the scene wallet is displayed together to remind the user to withdraw cash. After the withdrawal is completed, the confirmation page for canceling the wallet account is displayed. The user clicks to confirm the closure, and the platform wallet and the scene wallet will be closed together.

[0145] Based on the establishment of the above links, the platform can create scenario wallets according to business scenario requirements. For example, create a food wallet for food scenarios, an afternoon tea wallet for afternoon tea scenarios, a beauty wallet for beauty salon scenarios, etc. The embodiment of the present invention supports the creation of multiple scenario wallets. When multiple scenario wallets exist at the same time, Figure 3a and Figure 3b Multiple scene wallet cards are added to the main page of my wallet. The specific display method can be sliding display or list display, which is not limited by the present invention.

[0146] The creation of a scene wallet specifically includes: configuring the corresponding business elements for the scene wallet according to the business element configuration information for any scene wallet. The business elements of the scene wallet include but are not limited to: information display element class and interactive control element class. The configuration information of the business element includes: element content, display color, display style, etc. Among them, the information display element class includes: card logo display element, card background display element, wallet theme display element, available amount (balance) display element, validity period display element, merchant resource position display element, activity information display element, etc.; the interactive control element class includes: use control, recharge control, withdrawal control, activation control, closing control, etc.

[0147] The creation of a scenario wallet also includes: configuring corresponding activities for the scenario wallet according to the activity configuration information for any scenario wallet. For example, based on the current operation needs, a recharge and delivery activity is selected for a scenario wallet, and the recharge and delivery activity can be configured for the scenario wallet according to the activity configuration information.

[0148] Step 202: For any scenario wallet, a corresponding relationship between the scenario wallet and the merchant set is established according to the merchant set configuration information of the scenario wallet.

[0149] For any scenario wallet, the platform can circle merchants that support consumption using the scenario wallet to achieve flexible configuration of merchant collections. For example, a catering merchant collection is configured for a food wallet, a merchant collection of coffee merchants, dessert merchants, etc. is configured for an afternoon tea wallet, and a merchant collection of beauty merchants, hairdressing merchants, etc. is configured for a beauty wallet; for another example, a merchant collection with a customer unit price higher than a preset unit price threshold is configured for a high UE scenario wallet. Based on the above merchant collection configuration information, a corresponding relationship between the scenario wallet and the merchant collection is established.

[0150] In the embodiment of the present invention, in addition to the initial configuration of the merchant set when the scene wallet is created, the configuration update of the merchant set is also supported during the launch of the scene wallet. According to the merchant set configuration update information for any scene wallet, the corresponding relationship between the scene wallet and the merchant set is updated. Specifically, after the scene wallet is launched, the platform can add and delete the merchant set corresponding to the scene wallet, for example, add new merchants to the set or delete merchants in the set. By supporting the configuration update of the merchant set, the platform can adjust the merchant circle set in real time according to operational needs, thereby improving the applicability of the scene wallet.

[0151] In the embodiment of the present invention, during the launch of the scene wallet, the configuration update of the activity is also supported, for example, canceling the initially configured activity or adding a new activity to the scene wallet. By supporting the configuration update of the activity, the activities of each scene wallet can be flexibly adjusted to meet the operational needs of different business scenarios in real time.

[0152] After the above steps 201 and 202, the scene wallet is created, and the platform can recommend the scene wallet to the target user group. For example, it can be recommended to users on the homepage of the target user group's My Wallet. In order to attract users to open the scene wallet, the scene wallet card can be loaded with display activity information, and the user clicks the corresponding activity control to enter the pre-built activation link. After the user opens the scene wallet, the user can complete the wallet payment in the business scenario through the pre-built consumption link. In the subsequent steps 203 to 205, the user consumption of the target user for the designated merchant is described as an example.

[0153] Step 203: receiving a consumer request from a target user for a designated merchant.

[0154] Optionally, the target user can specify a merchant for consumption by browsing the merchant list page and searching for merchants, and complete the operations of selecting products, raising orders, and calling up the checkout counter on the merchant's store page, thereby initiating a user consumption request.

[0155] Step 204, query whether the designated merchant belongs to the merchant set corresponding to the available scenario wallet of the target user, and if so, determine the merchant set corresponding to the available scenario wallet of the target user including the designated merchant as the target merchant set.

[0156] Available scenario wallets refer to scenario wallets that have been opened by the target user and whose available amount is greater than 0. The available amount includes the user's recharge amount and the user's gift amount (gift obtained through recharge and gift activities or other operating activities). Optionally, the server can further filter the available scenario wallets according to the consumption amount corresponding to the user's consumption request, and select the scenario wallet with an available amount greater than or equal to the consumption amount.

[0157] After the target user initiates a user consumption request for the designated merchant, the server makes a decision on the available payment methods, specifically: querying whether the designated merchant belongs to the merchant set corresponding to the target user's available scenario wallet. If so, the merchant set corresponding to the target user's available scenario wallet containing the designated merchant is determined as the target merchant set, that is, it is decided that the scenario wallet corresponding to the target merchant set is one of the currently available payment methods.

[0158] Step 205, completing the payment process using the scenario wallet corresponding to the target merchant set to which the designated merchant belongs.

[0159] As mentioned above, the platform can launch multiple scenario wallets at the same time according to business scenario requirements. If the target user also opens multiple scenario wallets at the same time, there is a possibility that the designated merchant initiated by the user belongs to the merchant set corresponding to multiple available scenario wallets, that is, the target merchant set is determined to be multiple through the available payment method decision. For example, the target user opens a food wallet and an afternoon tea wallet at the same time, and the designated merchant belongs to both the merchant set of the food wallet and the merchant set of the afternoon tea wallet. In step 204, the available payment methods determined are the food wallet and the afternoon tea wallet. In this case, based on the system or the target user's selection of multiple scenario wallets corresponding to multiple target merchant sets, the selected scenario wallet is determined from multiple scenario wallets to complete the payment process.

[0160] Optionally, after calling up the cashier counter, multiple available scenario wallets are simultaneously displayed to the target user for selection by the target user.

[0161] Alternatively, the system may make priority payment selections based on actual conditions. For example, the system may give priority to scene wallets with larger user gift amounts for payment, or the system may give priority to scene wallets with larger available amounts for payment, or the system may give priority to scene wallets with shorter validity periods of available amounts for payment. The present invention is not limited to this.

[0162] In another optional implementation, after the user opens a scenario wallet, the user can complete the wallet payment in the business scenario through the pre-built consumption link for the specified scenario wallet. Figure 3b , the user clicks the "Go to Use" control, the server queries the target merchant set corresponding to the specified scenario wallet, and obtains the target merchant list for display based on the target merchant set. The target merchant list is a subset of the target merchant set corresponding to the specified scenario wallet. The user can select a merchant for consumption in the target merchant list. For the user consumption behavior of the target user at any merchant in the target merchant list, the specified scenario wallet is used to complete the payment processing.

[0163] As an implementation method, after a user opens a scenario wallet, the user can complete the wallet recharge through a pre-built recharge link. Specifically, the server receives a user recharge request from a target user for a specified scenario wallet, performs recharge processing on the specified scenario wallet according to the user recharge request, and records the user recharge amount and the corresponding validity period in the specified scenario wallet.

[0164] For example, see Figure 3b The user clicks on the activated Food Wallet card to enter the sub-page of the Food Wallet, in which the recharge control is displayed. The user clicks on the recharge control to send a user recharge request for the Food Wallet to the server. The server processes the recharge according to the user's recharge amount and records the user's recharge amount and the corresponding validity period in the Food Wallet.

[0165] Optionally, after receiving a user recharge request from a target user for a designated scenario wallet, the method further includes: determining whether the designated scenario wallet is configured with a corresponding activity; if so, extracting the user gift amount from the activity configuration information, performing a recharge process on the designated scenario wallet based on the user recharge amount and the user gift amount, and recording the user recharge amount and the corresponding first validity period, the user gift amount and the corresponding second validity period in the designated scenario wallet; if not, performing a recharge process based on the user recharge amount, and recording the user recharge amount and the corresponding first validity period.

[0166] For example, the food wallet is configured with corresponding recharge and gift activities. When the user clicks the recharge control of the food wallet, the server determines whether the food wallet is configured with the corresponding activity. If so, the server determines the gift money for this recharge based on the activity configuration information, and recharges the user's recharge amount and the gift money into the food wallet. In order to further attract users to consume multiple times, the embodiment of the present invention can set different validity periods for the user's recharge amount and the user's gift amount, for example, the validity period of the user's recharge amount is 1 year, and the validity period of the user's gift amount is 1 month, so as to attract users to consume the gift money as soon as possible and improve the effect of consumption frequency.

[0167] As an implementation method, after a user opens a scenario wallet, the user can complete the wallet withdrawal through the pre-built withdrawal link, that is, the user actively withdraws money. Specifically, the server receives the user withdrawal request from the target user for the specified scenario wallet; performs withdrawal processing on the specified scenario wallet according to the user withdrawal request, and updates the user recharge amount recorded in the specified scenario wallet according to the user withdrawal amount.

[0168] For example, see Figure 3b The user clicks on the activated Food Wallet card to enter the sub-page of the Food Wallet, in which the withdrawal control is displayed. The user clicks on the withdrawal control to send a user withdrawal request for the Food Wallet to the server. The server processes the withdrawal according to the user's withdrawal amount and updates the available amount of the Food Wallet according to the user's withdrawal amount.

[0169] As another implementation, after the user opens a scene wallet, the system can trigger the automatic withdrawal of the wallet according to the validity period recorded in the scene wallet, that is, to achieve automatic withdrawal triggered by the system. Specifically, the server starts the first scheduled task according to the validity period corresponding to the user's recharge amount; according to the triggering of the first scheduled task, the specified scene wallet is withdrawn, and the user's recharge amount recorded in the specified scene wallet is updated.

[0170] Taking the validity period of the user's recharge amount as 1 year as an example, after each recharge by the user, the server records the validity period corresponding to the user's recharge amount for the user's current recharge behavior, and starts the first scheduled task. The timing of the first scheduled task is set based on the expiration date of the validity period; when the timing of the first scheduled task arrives, the system triggers automatic withdrawal, that is, automatic withdrawal when the 1-year period arrives, and automatically returns the user's recharge amount to the recharge account, and updates the available amount of the scene wallet.

[0171] Optionally, the embodiment of the present invention may also support a message reminder that the user's recharge amount is about to expire. Specifically, the server starts a second scheduled task according to the validity period corresponding to the user's recharge amount; according to the triggering of the second scheduled task, a message is pushed to the target user to remind the user that the recharge amount is about to expire. The timing time of the second scheduled task is set to n days before the expiration date of the validity period.

[0172] Taking the example of a user recharge amount being valid for 1 year and n being 7, after each recharge by the user, the server records the validity period corresponding to the user's recharge amount for the user's current recharge behavior, and simultaneously starts the first scheduled task and the second scheduled task. When the timing of the second scheduled task arrives, the system pushes a message to the target user to remind the user that the recharge amount is about to expire, so as to remind the target user to consume as soon as possible.

[0173] Optionally, the above-mentioned user-initiated withdrawal and system-automatic withdrawal can be limited to the user's recharge amount, and the user's gift amount does not support withdrawal. In addition to supporting the touch message reminder of the user's recharge amount, it can also support the touch message reminder of the user's gift amount. The server starts the corresponding third scheduled task according to the validity period corresponding to the user's gift amount, and according to the triggering of the third scheduled task, pushes the touch message to the target user to remind the user that the gift amount is about to expire. Among them, the timing time of the third scheduled task is set to m days before the expiration date of the validity period corresponding to the user's gift amount.

[0174] In the above embodiments of the present invention, it is supported to flexibly create a scenario wallet according to the needs of different business scenarios, and it is supported to flexibly configure the merchant set corresponding to the scenario wallet, so as to limit the merchant use scope of different scenario wallets, so as to fully meet the consumption needs of users in different business scenarios, and further improve the effect of frequency locking customers compared with the platform wallet. During or after the creation of the scenario wallet, the configuration and / or activity configuration of the merchant set can be adjusted in real time according to the needs to meet the operation needs in different business scenarios. For user consumption, the embodiment of the present invention supports consumption for designated merchants and consumption for designated scenario wallets, which effectively improves the payment efficiency of the scenario wallet. For user recharge, the embodiment of the present invention can set different validity periods for the user recharge amount and the user gift amount, respectively, which can attract users to consume as soon as possible, further improving the user's retention rate and activity. For withdrawal, the embodiment of the present invention supports users to actively withdraw and the system automatically triggers withdrawal. The system automatically triggers withdrawal to achieve automatic refund after expiration, thereby eliminating the user's recharge concerns and attracting users to use the scenario wallet more frequently. The embodiment of the present invention also supports a touch message reminder that the available amount is about to expire, so as to remind users to consume as soon as possible and improve the user experience.

[0175] Figure 4A flowchart of a business interaction method of a scenario wallet according to an embodiment of the present invention is shown. The business interaction method of this embodiment is implemented based on at least one pre-created scenario wallet, wherein a corresponding relationship between the scenario wallet and the merchant set is established according to the merchant set configuration information of the scenario wallet. The creation process of the scenario wallet can refer to the relevant description of the above embodiment.

[0176] like Figure 4 As shown, the method comprises the following steps:

[0177] Step 401, monitoring user consumption requests for a specified scenario wallet;

[0178] Step 402, sending a user consumption request to the server, so that the server can use the specified scenario wallet to complete the payment processing of the target user's user consumption behavior for the specified merchant.

[0179] Optionally, before the above step 401, the method may further include: after the target user specifies a designated merchant for consumption, displaying at least one available scenario wallet of the target user corresponding to the target merchant set to which the designated merchant belongs; and monitoring the selection of any available scenario wallet by the system or the target user to determine the designated scenario wallet. Displaying at least one available scenario wallet of the target user corresponding to the target merchant set to which the designated merchant belongs specifically includes: displaying the business element corresponding to at least one available scenario wallet of the target user corresponding to the target merchant set to which the designated merchant belongs on the payment page.

[0180] Specifically, the target user can specify the designated merchant for consumption by browsing the merchant list page, searching for merchants, etc., and enter the payment page after completing the product selection, bill of lading, and cashier operation in the store page of the designated merchant. In this process, the server queries whether the designated merchant belongs to the merchant set corresponding to the target user's available scenario wallet. If so, at least one available scenario wallet that can be used for this payment is determined. The business element corresponding to the at least one available scenario wallet is displayed on the payment page. Then, the system or the target user selects any available scenario wallet to determine the designated scenario wallet. Then, execute the above step 401, monitor the user consumption request for the designated scenario wallet, execute the above step 402, and send the user consumption request to the server, so that the server can use the designated scenario wallet to complete the payment processing of the target user's user consumption behavior for the designated merchant. This implementation corresponds to the consumption link for the designated merchant described in the above embodiment, that is, the target user first specifies the merchant, enters the payment page, and then specifies the designated scenario wallet for payment.

[0181] The business elements corresponding to the at least one available scenario wallet include: usage control elements and available amount display elements.

[0182] Optionally, after sending the target user's user consumption request for the designated scenario wallet to the server, the method further includes: displaying a target merchant list; wherein the target merchant list is a subset of the target merchant set corresponding to the designated scenario wallet; monitoring the target user's user consumption behavior at any designated merchant in the target merchant list, and initiating a request for payment processing using the designated scenario wallet to complete the target user's user consumption behavior for the designated merchant. This implementation corresponds to the consumption link for the designated scenario wallet described in the above embodiment, that is, the target user first specifies the scenario wallet, for example, the target user first enters at least one level wallet page, specifies the designated scenario wallet for payment on the wallet page, and then displays the target merchant list, and the target user then specifies the designated merchant for consumption.

[0183] Optionally, before monitoring the user consumption request for the specified scenario wallet, the method further includes: displaying a business element corresponding to at least one available scenario wallet in at least one level wallet page; the business element corresponding to the at least one available scenario wallet includes: a usage control element and an available amount display element. Figure 3b At least one level wallet page includes: the main page of my wallet, which displays the business elements corresponding to the current user's available scenario wallets, such as usage control elements and available amount display elements, for the user to select a usage scenario wallet.

[0184] Optionally, if there are multiple available scenario wallets, displaying the business element corresponding to at least one available scenario wallet further includes: displaying the business elements corresponding to the multiple available scenario wallets in at least one level wallet page according to the display priority of the multiple available scenario wallets. Optionally, the display priority of the multiple available scenario wallets is determined according to the available amount of the available scenario wallet, the validity period of the available amount, or the merchant set corresponding to the available scenario wallet.

[0185] If the current user has multiple available scenario wallets, multiple scenario wallets are displayed in the main page of my wallet or the payment page, and the specific display method can be sliding display or list display. Among them, the available scenario wallets can be displayed in sequence according to the display priority. For example, available scenario wallets with more available amounts are displayed first, or available scenario wallets with a shorter validity period of available amounts are displayed first, or available scenario wallets with a larger merchant collection coverage of available scenario wallets are displayed first. By setting the display priority, users can be recommended to use available scenario wallets with higher priority to promote user consumption.

[0186] Optionally, the method further includes: displaying a service element corresponding to at least one unavailable scenario wallet in at least one primary wallet page; the service element corresponding to at least one unavailable scenario wallet includes: a merchant resource location display element and / or an activity information display element. The unavailable scenario wallet refers to a scenario wallet that the user has not yet opened. Figure 3a At least one level wallet page includes: the main page of my wallet, which displays the business elements corresponding to the unavailable scenario wallet of the current user, such as merchant resource position display elements and / or activity information display elements, wherein the merchant resource position display elements are used to display applicable merchants for unactivated scenario wallets, and the activity information display elements are used to display charging and sending activities for unactivated scenario wallets, so as to attract users to choose to activate scenario wallets.

[0187] Optionally, displaying the business element corresponding to at least one available scenario wallet further includes: displaying the business element corresponding to each available scenario wallet in a card form according to a preset card template.

[0188] Optionally, the method further includes: displaying a recharge control element of at least one scenario wallet in at least one first-level wallet page; monitoring the recharge operation of the target user for the specified scenario wallet, and sending a user recharge request to the server.

[0189] Optionally, the method further includes: displaying a withdrawal control element of at least one scenario wallet in at least one primary wallet page; monitoring a withdrawal operation of a target user for a specified scenario wallet, and sending a user withdrawal request to a server.

[0190] Optionally, the method further includes: receiving a message pushed by the server to remind the user that the recharge amount is about to expire.

[0191] The business interaction method of the scene wallet provided by the embodiment of the present invention displays the business elements of the pre-created scene wallet on at least one first-level wallet page or payment page, monitors the user consumption request for the specified scene wallet according to the user's interactive operation, and sends the user consumption request to the server, so that the server can use the specified scene wallet to complete the payment processing of the user consumption behavior of the target user for the specified merchant, thereby realizing the consumption business of the scene wallet; further, the user's recharge, withdrawal and other operations are monitored, and corresponding requests are initiated to realize the recharge, withdrawal and other services of the scene wallet, thereby improving the user experience of the scene wallet and further improving the effect of frequency increase and customer lock-in.

[0192] Figure 5 The schematic diagram of the structure of the business processing device of the scenario wallet according to one embodiment of the present invention is shown. Figure 5 As shown, the device comprises:

[0193] A creation module 510, used to create at least one scenario wallet;

[0194] Configuration module 520, for establishing a corresponding relationship between any scenario wallet and a merchant set according to the merchant set configuration information of the scenario wallet;

[0195] The receiving module 530 is used to receive a user consumption request from a target user for a specified scenario wallet or a specified merchant;

[0196] The processing module 540 is used to complete the payment processing by using the designated scenario wallet or the scenario wallet corresponding to the target merchant set to which the designated merchant belongs.

[0197] In an optional manner, the device further includes:

[0198] The query module is used to query whether the designated merchant belongs to the merchant set corresponding to the available scenario wallet of the target user, and if so, determine the merchant set corresponding to the available scenario wallet of the target user including the designated merchant as the target merchant set.

[0199] In an optional manner, the processing module is further used for: if it is determined that there are multiple target merchant sets, based on the system or the target user's selection of multiple scenario wallets corresponding to the multiple target merchant sets, determining the selected scenario wallet from the multiple scenario wallets to complete the payment processing.

[0200] In an optional manner, the device further includes:

[0201] A query module, used to query the target merchant set corresponding to the specified scenario wallet; and obtain a target merchant list for display according to the target merchant set;

[0202] The processing module is further used to: use the specified scenario wallet to complete payment processing for the user consumption behavior of the target user at any merchant in the target merchant list.

[0203] In an optional manner, the configuration module is further used to: update the correspondence between the scenario wallet and the merchant set according to the merchant set configuration update information for any scenario wallet.

[0204] In an optional manner, the creation module is further used to: configure corresponding activities for any scenario wallet according to the activity configuration information for the scenario wallet.

[0205] In an optional manner, the creation module is further used to: configure corresponding business elements for any scenario wallet according to the business element configuration information for the scenario wallet.

[0206] In an optional manner, the device also includes: a recharge module, used to receive a user recharge request from a target user for a specified scenario wallet; recharge the specified scenario wallet according to the user recharge request, and record the user recharge amount and the corresponding validity period in the specified scenario wallet.

[0207] In an optional manner, the recharge module is further used for:

[0208] Determine whether the specified scenario wallet is configured with corresponding activities;

[0209] If yes, extract the user gift amount from the activity configuration information, recharge the designated scenario wallet based on the user recharge amount and the user gift amount, and record the user recharge amount and the corresponding first validity period, the user gift amount and the corresponding second validity period in the designated scenario wallet;

[0210] If not, recharge processing is performed based on the user's recharge amount, and the user's recharge amount and the corresponding first validity period are recorded.

[0211] In an optional manner, the device also includes: a withdrawal module, used to receive a user withdrawal request from a target user for a specified scenario wallet; perform withdrawal processing on the specified scenario wallet according to the user withdrawal request, and update the user recharge amount recorded in the specified scenario wallet according to the user withdrawal amount.

[0212] In an optional manner, the device also includes: a withdrawal module, which is used to start a first scheduled task according to the validity period corresponding to the user recharge amount; based on the triggering of the first scheduled task, the designated scenario wallet is withdrawn and the user recharge amount recorded in the designated scenario wallet is updated.

[0213] In an optional manner, the device also includes: a message triggering module, which is used to start a second scheduled task according to the validity period corresponding to the user's recharge amount; and based on the triggering of the second scheduled task, push a contact message to the target user to remind the user that the recharge amount is about to expire.

[0214] The description of each module above refers to the corresponding description in the method embodiment and will not be repeated here.

[0215] The business processing device of the scenario wallet provided by the embodiment of the present invention supports flexible creation of scenario wallets according to the needs of different business scenarios, and supports flexible configuration of merchant sets corresponding to scenario wallets, thereby limiting the merchant use scope of different scenario wallets to fully meet the consumption needs of users in different business scenarios. Compared with the platform wallet, it further improves the effect of frequency-increasing and locking customers. During or after the creation of the scenario wallet, the configuration and / or activity configuration of the merchant set can be adjusted in real time according to the needs to meet the operation needs in different business scenarios. For user consumption, the embodiment of the present invention supports consumption for designated merchants and consumption for designated scenario wallets, effectively improving the payment efficiency of the scenario wallet. For user recharge, the embodiment of the present invention can set different validity periods for the user recharge amount and the user gift amount, respectively, which can attract users to consume multiple times as soon as possible, further improving the user's retention rate and activity. For withdrawal, the embodiment of the present invention supports users to actively withdraw and the system automatically triggers withdrawal. The system automatically triggers withdrawal to achieve automatic refund upon expiration, thereby eliminating users' concerns about recharge and attracting users to use scenario wallets more frequently. The embodiment of the present invention also supports a touch message reminder that the available amount is about to expire, so as to remind users to consume as soon as possible and improve user experience.

[0216] Figure 6 The schematic diagram of the structure of the business interaction device of the scenario wallet according to an embodiment of the present invention is shown. The device is implemented based on at least one pre-created scenario wallet, wherein the scenario wallet and the merchant set have a corresponding relationship established according to the merchant set configuration information of the scenario wallet; Figure 6 As shown, the device comprises:

[0217] Monitoring module 610, used to monitor user consumption requests for wallets in specified scenarios;

[0218] The request module 620 is used to send the user consumption request to the server, so that the server can use the specified scenario wallet to complete the payment processing of the target user's user consumption behavior for the specified merchant.

[0219] In an optional manner, the device further includes: a display module 630, configured to display at least one available scenario wallet of the target user corresponding to the target merchant set to which the designated merchant belongs after the target user designates a designated merchant for consumption;

[0220] The monitoring module is further used to: monitor the selection of any available scenario wallet by the system or the target user to determine the designated scenario wallet.

[0221] In an optional manner, the device further includes: a display module 630, configured to display a target merchant list; wherein the target merchant list is a subset of the target merchant set corresponding to the specified scenario wallet;

[0222] The monitoring module is further used to monitor the target user's consumption behavior at any designated merchant in the target merchant list; the request module is further used to initiate a request for payment processing of the target user's consumption behavior at the designated merchant using the designated scenario wallet.

[0223] In an optional manner, the display module is further used to: display on the payment page a business element corresponding to at least one available scenario wallet of the target user corresponding to the target merchant set to which the designated merchant belongs;

[0224] The business elements corresponding to the at least one available scenario wallet include: usage control elements and available amount display elements.

[0225] In an optional manner, the display module is further used to: display a business element corresponding to at least one available scenario wallet in at least one primary wallet page;

[0226] The business elements corresponding to the at least one available scenario wallet include: usage control elements and available amount display elements.

[0227] In an optional manner, if there are multiple available scenario wallets, the display module is further used to: display business elements corresponding to the multiple available scenario wallets according to the display priorities of the multiple available scenario wallets.

[0228] In an optional manner, the display priority of the multiple available scenario wallets is determined according to the available amount of the available scenario wallet, the validity period of the available amount, or the merchant set corresponding to the available scenario wallet.

[0229] In an optional manner, the display module is further used to: display a business element corresponding to at least one unavailable scenario wallet in at least one primary wallet page;

[0230] The business element corresponding to the at least one unavailable scenario wallet includes: a merchant resource location display element and / or an activity information display element.

[0231] In an optional manner, the display module is further used to: display the business elements corresponding to each available scenario wallet in the form of a card according to a preset card template.

[0232] In an optional manner, the display module is further used to: display at least one recharge control element of a scenario wallet in at least one primary wallet page;

[0233] The monitoring module is also used to monitor the target user's recharge operation for the specified scenario wallet; the request module is also used to send a user recharge request to the server.

[0234] In an optional manner, the display module is further used to: display a withdrawal control element of at least one scenario wallet in at least one primary wallet page;

[0235] The monitoring module is also used to monitor the target user's withdrawal operation for the specified scenario wallet; the request module is also used to send the user withdrawal request to the server.

[0236] In an optional manner, the device further includes: a receiving module (not shown in the figure), which is used to receive a contact message pushed by the server to remind the user that the recharge amount is about to expire.

[0237] The description of each module above refers to the corresponding description in the method embodiment and will not be repeated here.

[0238] The business interaction device of the scene wallet provided in the embodiment of the present invention displays the business elements of the pre-created scene wallet on at least one primary wallet page or payment page, monitors the user's interactive operations, and realizes the consumption, recharge, withdrawal and other services of the scene wallet, thereby improving the user experience of the scene wallet and further improving the effect of increasing frequency and locking customers.

[0239] An embodiment of the present invention further provides a non-volatile computer storage medium, which stores at least one executable instruction, and the executable instruction can execute the business processing method of the scenario wallet and / or the business interaction method of the scenario wallet in any of the above method embodiments.

[0240] Figure 7 A schematic diagram of the structure of a computing device according to an embodiment of the present invention is shown. The specific implementation of the embodiment of the present invention does not limit the specific implementation of the computing device.

[0241] like Figure 7 As shown, the computing device may include: a processor (processor) 702 , a communication interface (Communications Interface) 704 , a memory (memory) 706 , and a communication bus 708 .

[0242] in:

[0243] The processor 702 , the communication interface 704 , and the memory 706 communicate with each other via a communication bus 708 .

[0244] The communication interface 704 is used to communicate with other devices such as clients or other servers.

[0245] Processor 702 is used to execute program 710, and specifically can execute relevant steps in the above-mentioned business processing method of the scenario wallet and / or the business interaction method embodiment of the scenario wallet.

[0246] Specifically, the program 710 may include program codes, which include computer operation instructions.

[0247] The processor 702 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention. The one or more processors included in the computing device may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.

[0248] The memory 706 is used to store the program 710. The memory 706 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0249] Program 710 can be specifically used to enable processor 702 to execute the business processing method of the scene wallet and / or the business interaction method of the scene wallet in any of the above-mentioned method embodiments. The specific implementation of each step in program 710 can refer to the corresponding descriptions in the corresponding steps and units in the above-mentioned scene wallet business processing method and / or scene wallet business interaction method embodiments, which will not be repeated here. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the above-described devices and modules can refer to the corresponding process description in the above-mentioned method embodiments, which will not be repeated here.

[0250] The algorithm or display provided herein is not inherently related to any particular computer, virtual system or other device. Various general purpose systems can also be used together with the teachings based on this. According to the above description, it is obvious that the structure required for constructing such systems. In addition, the embodiment of the present invention is not directed to any specific programming language either. It should be understood that various programming languages ​​can be utilized to realize the content of the embodiment of the present invention described herein, and the description of the above specific language is to disclose the preferred implementation of the embodiment of the present invention.

[0251] In the description provided herein, a large number of specific details are described. However, it is understood that embodiments of the present invention can be practiced without these specific details. In some instances, well-known methods, structures and techniques are not shown in detail so as not to obscure the understanding of this description.

[0252] Similarly, it should be understood that in order to streamline the embodiments of the present invention and to aid in understanding one or more of the various inventive aspects, in the above description of the exemplary embodiments of the present invention, the various features of the embodiments of the present invention are sometimes grouped together into a single embodiment, figure, or description thereof. However, the disclosed method should not be interpreted as reflecting the following intention: that the claimed embodiments of the present invention require more features than the features explicitly recited in each claim. More specifically, as reflected in the claims below, the inventive aspects lie in less than all the features of the single embodiment disclosed above. Therefore, the claims that follow the specific embodiment are hereby expressly incorporated into the specific embodiment, wherein each claim itself serves as a separate embodiment of the present invention.

[0253] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and in addition they may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive, all features disclosed in this specification (including the accompanying claims, abstracts and drawings) and all processes or units of any method or device disclosed in this manner may be combined in any combination. Unless otherwise expressly stated, each feature disclosed in this specification (including the accompanying claims, abstracts and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.

[0254] In addition, those skilled in the art will appreciate that, although some embodiments herein include certain features included in other embodiments but not other features, the combination of features of different embodiments is meant to be within the scope of the present invention and form different embodiments. For example, in the claims below, any one of the claimed embodiments may be used in any combination.

[0255] The various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It should be understood by those skilled in the art that a microprocessor or digital signal processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components according to the embodiments of the present invention. The embodiments of the present invention may also be implemented as a device or apparatus program (e.g., a computer program and a computer program product) for executing part or all of the methods described herein. Such a program implementing an embodiment of the present invention may be stored on a computer-readable medium, or may have the form of one or more signals. Such a signal may be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.

[0256] It should be noted that the above embodiments illustrate rather than limit the present invention, and that those skilled in the art may devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbol between brackets shall not be construed as a limitation on the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "one" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present invention may be implemented by means of hardware comprising a number of different elements and by means of a suitably programmed computer. In a unit claim listing a number of devices, several of these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc. does not indicate any order. These words may be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be understood as limitations on the order of execution.

Claims

1. A business processing method for a scenario wallet, the method include: Create at least one scenario wallet; For any scenario wallet, establish a corresponding relationship between the scenario wallet and the merchant set according to the merchant set configuration information of the scenario wallet; Receive consumption requests from target users for designated scenario wallets or designated merchants; The payment process is completed using the designated scenario wallet or the scenario wallet corresponding to the target merchant set to which the designated merchant belongs.

2. The method according to claim 1, in, After receiving a user consumption request from a target user for a designated merchant, the method further includes: It is queried whether the designated merchant belongs to the merchant set corresponding to the available scenario wallet of the target user. If so, the merchant set corresponding to the available scenario wallet of the target user including the designated merchant is determined as the target merchant set.

3. The method according to claim 2, in, If it is determined that there are multiple target merchant sets, completing the payment process using the scenario wallet corresponding to the target merchant set to which the designated merchant belongs further includes: Based on the selection of multiple scenario wallets corresponding to multiple target merchant sets by the system or the target user, the selected scenario wallet is determined from the multiple scenario wallets to complete the payment processing.

4. The method according to claim 1, in, After receiving a user consumption request from a target user for a wallet in a specified scenario, the method further includes: Query the target merchant set corresponding to the specified scenario wallet; According to the target merchant set, obtaining a target merchant list for display; The specific method of completing the payment process by using the designated scenario wallet is as follows: for the user consumption behavior of the target user at any merchant in the target merchant list, the payment process is completed by using the designated scenario wallet.

5. The method according to any one of claims 1 to 4, in, After establishing a corresponding relationship between the scenario wallet and the merchant set according to the merchant set configuration information of the scenario wallet for any scenario wallet, the method further includes: According to the merchant set configuration update information for any scenario wallet, the correspondence between the scenario wallet and the merchant set is updated.

6. A business interaction method of a scenario wallet, the method being implemented based on at least one pre-created scenario wallet, in, There is a corresponding relationship between the scene wallet and the merchant set established according to the merchant set configuration information of the scene wallet; the method includes: Monitor user spending requests for wallets in specified scenarios; The user consumption request is sent to the server, so that the server can use the specified scenario wallet to complete the payment processing of the target user's user consumption behavior for the specified merchant.

7. A business processing device for a scene wallet, the device include: A creation module, used to create at least one scenario wallet; A configuration module, used for establishing a correspondence between a scenario wallet and a merchant set according to the merchant set configuration information of the scenario wallet for any scenario wallet; A receiving module, used to receive a target user's consumption request for a specified scenario wallet or a specified merchant; The processing module is used to complete the payment processing by using the designated scenario wallet or the scenario wallet corresponding to the target merchant set to which the designated merchant belongs.

8. A business interaction device for a scenario wallet, the device being implemented based on at least one pre-created scenario wallet, in, There is a corresponding relationship between the scene wallet and the merchant set established according to the merchant set configuration information of the scene wallet; the device includes: Monitoring module, used to monitor user consumption requests for wallets in specified scenarios; The request module is used to send the user consumption request to the server, so that the server can use the specified scenario wallet to complete the payment processing of the user consumption behavior of the target user for the specified merchant.

9. A computing device, include: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform operations corresponding to the business processing method of the scene wallet as described in any one of claims 1-5, and / or, the executable instruction enables the processor to perform operations corresponding to the business interaction method of the scene wallet as described in claim 6.

10. A computer storage medium, wherein at least one executable instruction is stored in the storage medium, wherein the executable instruction enables a processor to perform operations corresponding to the business processing method of the scenario wallet as described in any one of claims 1 to 5, and / or the executable instruction enables a processor to perform operations corresponding to the business interaction method of the scenario wallet as described in claim 6.