Payment saving method, electronic equipment and computer readable storage medium

Abstract

The invention provides a payment saving method, electronic equipment and a computer readable storage medium, which can improve the saving success rate. The method is applied to a client and comprises the following steps: detecting a payment behavior of a user; when it is detected that the user has the payment behavior, a query request is sent to a payment management server, and the query request is used for querying retention information; receiving the retention information sent by the payment management server, wherein the retention information comprises first retention information and / or second retention information; splicing the retention information to obtain a retention pop-up window; and when it is detected that the user cancels payment, displaying the retention pop-up window to the user.

Description

TECHNICAL FIELD

[0001] The present application relates to the payment field, and in particular to a payment retention method, an electronic device and a computer readable storage medium. BACKGROUND

[0002] When a user purchases goods or services online, the user may abandon the purchase and cancel the payment due to various reasons when entering a settlement page to prepare for payment. Cancellation of payment means loss of users with purchase intentions, which directly affects the revenue of manufacturers.

[0003] In order to improve the user payment success rate and increase revenue, it is necessary to retain the user when the user cancels the payment. However, the current retention scheme has the problem of low recovery success rate. SUMMARY

[0004] The present application provides a payment retention method, an electronic device and a computer readable storage medium, which can improve the recovery success rate.

[0005] In a first aspect, a payment retention method is provided, which is applied to a client and includes: detecting a payment behavior of a user; in a case where it is detected that the user has a payment behavior, sending a query request to a payment management server, the query request being used to query retention information; receiving the retention information sent by the payment management server, the retention information including first retention information and / or second retention information; splicing the retention information to obtain a retention pop-up window; and in a case where it is detected that the user cancels the payment, displaying the retention pop-up window to the user.

[0006] In the present application, the retention information is obtained from the payment management server and the retention pop-up window is generated in a case where it is detected that the user has a payment behavior, so that the retention information is loaded and the retention pop-up window is spliced before the user cancels the payment. In this way, the retention pop-up window can be displayed to the user in time when the user cancels the payment, the success rate of displaying the retention pop-up window to the user is improved, and the success rate of the user payment is further improved.

[0007] In some implementations, the retention information includes first retention information and second retention information, the splicing of the retention information to obtain a retention pop-up window includes: splicing the first retention information to obtain a first retention pop-up window; and splicing the second retention information to obtain a second retention pop-up window; and the displaying of the retention pop-up window to the user in a case where it is detected that the user cancels the payment includes: displaying the first retention pop-up window to the user in a case where it is detected that the user cancels the payment, to perform first retention; and in a case where the first retention fails, displaying the second retention pop-up window to the user, to perform second retention.

[0008] The payment management server can return two retention messages to the client at once, allowing the client to make two retention attempts with the user, thereby enhancing the user's willingness to purchase and increasing the success rate of retention.

[0009] In some implementations, the method further includes: upon detecting that the user has made a payment, sending payment order information to a big data management platform, wherein the payment order information is used by the big data management platform to generate coupon information based on an artificial intelligence (AI) model; receiving the retention information sent by the payment management server includes: receiving the retention information assembled by the payment management server based on the coupon information; wherein the payment order information includes one or more of the following: consumption amount, order time, product type, and delivery address.

[0010] Generating coupon information through a big data management platform can reduce the processing burden on the coupon management server. Furthermore, the platform can generate coupon information that best satisfies users, thereby improving user satisfaction and the success rate of customer retention.

[0011] In some implementations, the query request includes one or more of the following information: order number, product identifier ID, application ID, and user ID, and the information in the query request is used by the payment management server to match the retention information.

[0012] In some implementations, detecting the user's payment behavior includes: detecting the client's operation of launching the cashier; the method further includes: if the client launches the cashier, then determining that the user has made a payment.

[0013] By detecting whether the checkout counter is activated, user payment behavior can be detected immediately, improving the timeliness of payment detection.

[0014] Secondly, a payment retention method is provided, which is applied to a payment management server and includes: receiving a query request sent by a client, the query request being used to query retention information, the query request being sent when a user has made a payment; responding to the query request, sending the retention information to the client, the retention information including initial retention information and / or secondary retention information, the initial retention information being used to perform an initial retention attempt on the user, and the secondary retention information being used to perform a secondary retention attempt on the user if the initial retention attempt fails.

[0015] In some implementations, the query request includes payment order information. Before sending the retention information to the client, the method further includes: responding to the query request, matching a retention scenario for the payment order based on a retention strategy; if the matched retention scenario requires a new coupon, sending a coupon request to a coupon management server; receiving information about the new coupon sent by the coupon management server; and generating the retention information based on the information about the new coupon.

[0016] In some implementations, the method further includes: if the matched retention scenario is retention through coupons or gift coupons, then determining that the matched retention scenario requires new coupons.

[0017] In some implementations, the method further includes: receiving the retention strategy configured by the operations personnel, wherein the retention strategy includes card rules configured by the operations personnel, the card rules include rules for a first card and / or rules for a second card, and the card rules include one or more of the following information: card priority, card scope of application, card validity period, and text information on the card, wherein the first card is the card with the highest priority, and the second card is the card with a priority between the priority of the first card and the priority of the fallback card.

[0018] In some implementations, the retention strategy includes a matching order of multiple retention scenarios and multiple switches for the multiple retention scenarios. The multiple switches are used to control whether to execute the matching process of the multiple retention scenarios. The multiple retention scenarios include one or more of the following: first card retention, marketing activity retention, expansion coupon retention, expired coupon retention, gift coupon retention, second card retention, and fallback card retention.

[0019] In some implementations, matching retention scenarios for the payment order based on retention strategies includes: for a first retention scenario among the multiple retention scenarios, if the switch corresponding to the first retention scenario is in a closed state and / or the first retention scenario does not match the payment order, then based on the matching order, a matching process with the next retention scenario of the first retention scenario is executed; if the switch corresponding to the first retention scenario is in a closed state and the first retention scenario matches the payment order, then the matched retention scenario is determined to be the first retention scenario.

[0020] In some implementations, the method further includes: determining that the payment order matches the first retention scenario if a first condition is met, wherein the first condition includes one or more of the following: the scope of application of the first retention scenario matches the information of the payment order; the payment order hits an A / B test; the first retention scenario is a coupon retention scenario, and the first retention scenario configures a coupon for the payment order, wherein the coupon is an expansion coupon or a gift coupon.

[0021] In some implementations, the payment order information includes one or more of the following: order number, product ID, application ID, and user ID.

[0022] Thirdly, a payment retention method is provided, which is applied to a coupon management server and includes: receiving a coupon request sent by the payment management server, wherein the coupon request is used to request an expansion coupon or a gift coupon;

[0023] In response to the coupon request, coupon information is sent to the payment management server. The coupon information includes information on expansion coupons or gift coupons. The coupon information is used to generate retention information to retain users.

[0024] In some implementations, the coupon request includes information about a payment order, and the method further includes: matching the payment order based on coupon matching rules to obtain coupons that match the payment order.

[0025] In some implementations, the coupon matching rules are configured by the operators in the coupon management server.

[0026] In some implementations, the coupon information is generated by a big data management platform based on payment order information. The payment order information includes one or more of the following: consumption amount, order time, product type, and delivery address. The payment order information is sent from the client to the big data management platform.

[0027] In some implementations, the method further includes: in the event of retention failure, reclaiming coupons issued to the user, including expansion coupons or gift coupons. The reclamation of coupons issued to the user includes: deleting the coupon from the user's account after the coupon's effective period has expired.

[0028] In some implementations, the method further includes: after sending coupon information to the payment management server once, incrementing the value of a first counter by 1; and after the value of the first counter reaches a preset threshold, ceasing to respond to coupon requests from the payment management server.

[0029] Fourthly, an apparatus is provided, the apparatus comprising a unit consisting of software and / or hardware, the unit being configured to perform any one of the methods described in any one of the first to third aspects.

[0030] Fifthly, a chip is provided, including a processor; the processor is configured to read and execute a computer program stored in a memory to perform any of the methods described in the first aspect.

[0031] In a sixth aspect, a chip is provided, including a processor; the processor is configured to read and execute a computer program stored in a memory to perform any one of the methods described in the second or third aspect.

[0032] Optionally, the chip further includes a memory, which is connected to the processor via a circuit or wire.

[0033] Alternatively, the chip may further include a communication interface.

[0034] In a seventh aspect, an electronic device is provided, wherein a client is installed on the electronic device, the electronic device comprising: a processor, a memory, and an interface; the processor, the memory, and the interface cooperate with each other to enable the electronic device to execute any one of the methods described in the first aspect; or to include any one of the chips described in the fifth aspect.

[0035] Eighthly, a server is provided, the server comprising: a processor, a memory, and an interface; the processor, the memory, and the interface cooperate with each other to enable an electronic device to perform any one of the technical solutions described in the second or third aspect; or to include any one of the chips described in the sixth aspect.

[0036] Ninth aspect, a computer-readable storage medium is provided, wherein a computer program is stored therein, and when the computer program is executed by a processor, the processor performs any one of the methods of the technical solutions described in any one of the first to third aspects.

[0037] In a tenth aspect, a computer program product is provided, the computer program product comprising: computer program code, which, when executed on an electronic device, causes the electronic device to perform any one of the technical solutions described in any one of the first to third aspects. Attached Figure Description

[0038] Figure 1 This is a schematic diagram of the structure of an electronic device 100 provided in an embodiment of this application;

[0039] Figure 2 This is a schematic diagram of the payment retention system provided in the embodiments of this application;

[0040] Figure 3 This is a schematic diagram of the P0 card retention scenario provided in the embodiments of this application;

[0041] Figure 4 This is a schematic diagram of a marketing campaign retention scenario provided in an embodiment of this application;

[0042] Figure 5 This is a schematic diagram of a scenario for retaining customers using expansion coupons, as provided in an embodiment of this application.

[0043] Figure 6 This is a schematic diagram of an expired coupon retention scenario provided in an embodiment of this application;

[0044] Figure 7 This is a schematic diagram of a coupon retention scenario provided in an embodiment of this application;

[0045] Figure 8 This is a schematic diagram of a fallback card retention scenario provided in an embodiment of this application;

[0046] Figure 9 This is a schematic diagram of the user interface for operators provided in the embodiments of this application;

[0047] Figure 10 This is a schematic diagram of the interface for operators to configure card rules, provided in an embodiment of this application.

[0048] Figure 11 This is a flowchart illustrating the payment retention method provided in the embodiments of this application;

[0049] Figure 12 This is a schematic diagram illustrating the interaction process between the big data management platform, the client, and the coupon management server provided in this application embodiment;

[0050] Figure 13 This is a schematic diagram of the coupon processing flow provided in the embodiments of this application;

[0051] Figure 14 This is a schematic diagram of the scenario matching process based on retention strategies provided in the embodiments of this application;

[0052] Figure 15 This is a schematic diagram of a PC payment scenario provided in an embodiment of this application;

[0053] Figure 16 This is a schematic diagram of a user subscription retention scheme provided in an embodiment of this application;

[0054] Figure 17 This is a schematic block diagram of the electronic device provided in the embodiments of this application;

[0055] Figure 18This is a schematic block diagram of the payment management server provided in an embodiment of this application;

[0056] Figure 19 This is a schematic block diagram of the coupon management server provided in the embodiments of this application;

[0057] Figure 20 This is a schematic diagram of the payment retention device provided in the embodiments of this application. Detailed Implementation

[0058] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; "and / or" in this text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0059] Hereinafter, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first," "second," or "third" may explicitly or implicitly include one or more of that feature.

[0060] The solution in this application embodiment is applied to a scenario of retaining users through payment. The system for retaining users through payment may include electronic devices. The electronic devices involved in this application embodiment are described below.

[0061] The electronic devices in this application embodiment can be handheld terminal devices or wearable devices, etc. Handheld terminal devices may include, for example, mobile phones, tablets, augmented reality (AR) / virtual reality (VR) devices, etc. Wearable devices may include, for example, watches, bracelets, headphones, etc.

[0062] For example, Figure 1This is a schematic diagram of the structure of an electronic device 100 provided in an embodiment of this application. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, etc.

[0063] The mobile communication module 150 may include one or more of second-generation (2G), 3G, 4G, and 5G communication modules. The mobile communication module 150 may include one or more of a filter, a switch, a power amplifier, and a low-noise amplifier (LNA).

[0064] The wireless communication module 160 may include one or more of the following: Bluetooth (BT) module, Wireless Local Area Network (WLAN) module, Global Navigation Satellite System (GNSS) module, Near Field Communication (NFC) module, Infrared (IR) module, and Frequency Modulation (FM) module. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering on the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification on them, and then convert them into electromagnetic waves for radiation via antenna 2.

[0065] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0066] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0067] When users purchase goods or services online, they may abandon their purchase or cancel payment for various reasons when they reach the checkout page and are ready to pay. Cancellation means the loss of a potential customer, directly impacting the manufacturer's revenue.

[0068] To improve user payment success rates and increase revenue, it is necessary to retain users when they cancel their payments. This can be achieved by providing pop-up coupons or benefit cards to users when they cancel their payments, thereby enhancing their willingness to purchase.

[0069] Current retention strategies suffer from low success rates. The reasons for this problem are analyzed below. As an example, current retention efforts only begin when the user cancels payment. This includes retrieving retention information, assembling and combining this information, and generating a retention pop-up. However, these operations take time. When the user cancels payment, the client may not have had time to generate or display the retention pop-up before the user has completely exited the payment page, resulting in retention failure.

[0070] As another example, current retention strategies only attempt to retain users once. If this fails, the user exits the checkout and the payment fails. However, in some scenarios, the initial retention attempt may not present the user with detailed offers. The user might cancel the payment before fully understanding the offers. Without a second retention attempt, some users may be lost, reducing the success rate of retention.

[0071] Furthermore, current retention strategies suffer from security vulnerabilities. For example, current coupons are managed by a payment management server. This server needs to assemble retention information and interact with clients, making it susceptible to cyberattacks. Delegating coupon management authority to the payment management server would compromise financial security. Additionally, current payment management servers perform numerous operations, increasing their workload.

[0072] Based on this, this application proposes a payment retention method. After detecting a user's payment behavior, it performs operations such as acquiring and assembling retention information and splicing retention pop-ups. When the user clicks to cancel payment, a retention pop-up can be displayed to the user in a timely manner to improve the retention success rate.

[0073] In some implementations, embodiments of this application can also perform a second retention attempt on the user. If the first retention attempt fails, a second retention attempt pop-up window can be displayed to the user. The second retention attempt pop-up window can display more detailed information on promotional activities, enhance the user's purchase intention, and increase the success rate of retention.

[0074] In some implementations, embodiments of this application separate the retention information processing function from the coupon management function, with two servers performing the retention information processing and coupon management respectively. For example, the payment management server performs the retention information processing, and the coupon management server performs the coupon management. In other words, the financial-related control behavior is completely handed over to the coupon management server, which can reduce the load on the payment management server while ensuring financial security.

[0075] In some implementations, for scenarios requiring the use of new coupons (such as expansion coupons and gift coupons), the payment management server can send a coupon usage request to the coupon management server. Upon receiving the request, the coupon management server can generate coupon information matching the current payment order and send this coupon information to the payment management server. The payment management server can then generate retention information based on the coupon information. For example, the payment management server can assemble the coupon information to obtain retention information.

[0076] In some implementations, if the payment management server determines that coupon information is not needed, it can generate retention information based on local information. For example, the payment management server can assemble card information and / or existing coupon information in the user account to obtain retention information.

[0077] The following is combined Figure 2This application describes a payment retention system based on embodiments thereof. The payment retention system in these embodiments may include a client, a payment management server, and a coupon management server.

[0078] The client can be an app, a mini-program, or a webpage accessed by scanning a QR code. The client can also be called the application client. In some implementations, the client can be an IAP client. The client can detect user actions; for example, it can detect user payment behavior, such as detecting payment actions, cancellations, and completions.

[0079] The client can be installed on electronic devices. These devices may include, for example, mobile phones, computers, tablets, smartwatches, and smart bracelets.

[0080] A client application can provide users with goods and services, allowing them to purchase these items. For example, a client application could be a game app, enabling users to purchase in-game items. Another example is a cloud storage app, allowing users to top up their memberships and enjoy corresponding benefits. Yet another example is a shopping app, allowing users to purchase their desired goods. A third example is a client application that leads to a webpage by scanning a QR code provided by the manufacturer, through which users can purchase goods and services. This QR code could be provided by manufacturers of shared massage chairs, shared power banks, or shared bicycles.

[0081] The client-side can concatenate retention messages to create a retention pop-up, which can be displayed to the user when they cancel payment. Displaying the retention pop-up to the user can refer to showing it on the screen of an electronic device. Retention pop-ups can be coupon pop-ups, card pop-ups, or marketing campaign pop-ups, etc.

[0082] The payment management server resides in the cloud, meaning it can be a cloud server. Taking an IAP system as an example, the payment management server can be an IAP server. The payment management server can assemble retention information and determine the information content to be presented to the user.

[0083] The payment management server can interact with clients. For example, a client can send a query request to the payment management server to retrieve retention information. In response to this query request, the payment management server can send retention information to the client.

[0084] The payment management server can decide which type of retention pop-up to offer to the user. The payment management server can determine the type of retention pop-up based on the retention strategy. The retention strategy can be determined jointly based on parameters configured by operations personnel and / or matching results from the big data management platform.

[0085] This application provides seven types of retention pop-up windows, which will be described in detail below.

[0086] The coupon management server resides in the cloud and can also be called a coupon cloud server. The coupon management server has financial-related control permissions. For example, it can decide whether to provide coupons to users, the face value of the coupons provided, and the validity period of the coupons.

[0087] The coupon management server can interact with the payment management server. For example, the payment management server can send a coupon request to the coupon management server to request coupon information. In response to the coupon request, the coupon management server can send the coupon-related information to the payment management server.

[0088] In some implementations, the payment retention system in this application embodiment may further include an operations configuration platform. Operators can configure retention strategies and coupon matching rules through the operations configuration platform. The operations configuration platform can send retention strategies to the payment management server and coupon matching rules to the coupon management server.

[0089] The coupon matching rules can be configured by operations personnel or AI models, taking into account the user group type, age distribution, consumption habits and other potential group consumption behaviors reflected in the payment process.

[0090] The operations configuration platform can be a webpage where operations personnel can configure various rules. After the rules are configured, the webpage can send them to the corresponding server. The operations configuration platform will be described in detail below.

[0091] In some implementations, the payment retention system in this application embodiment may also include a big data management platform. The big data management platform includes an artificial intelligence (AI) model, which can be trained using a large amount of training data. The big data management platform has various functions. For example, it can match users with the best coupon information. It can also obtain the best retention strategies. Furthermore, it can obtain the best coupon matching rules.

[0092] The retention scenarios in this application embodiment may include retention using a first card, marketing campaigns, coupons, expired coupons, gift coupons, a second card, and a fallback card. The first card is the highest priority card, and the second card is a card whose priority is between that of the first card and the fallback card. For ease of description, the first card will be referred to as the P0 card, and the second card as the non-P0 card. A non-P0 card may include one or more cards.

[0093] P0 card retention and non-P0 card retention can show users information about the benefits they can get after paying for the order, in order to enhance their willingness to buy and increase the success rate of their payment.

[0094] Retention efforts through marketing campaigns can involve showing users rebates for participating in the campaign. These rebates can include small gifts or opportunities to win free orders after a certain number of payments, participation in lucky draws, and bonus points, all designed to encourage user participation and increase payment success rates.

[0095] Coupon inflation can refer to inflating a user's existing coupons to increase the discount offered to the user, enhance the user's willingness to buy, and improve the user's payment success rate.

[0096] Expired coupon retention can display coupons that are about to expire in the user's account to encourage them to use them in time, thereby increasing their willingness to buy and improving the success rate of payment.

[0097] Retention coupons can be used to issue a new coupon to a user for their current payment order, thereby increasing the user's willingness to purchase and improving the success rate of payment.

[0098] A fallback card retention measure can refer to simply confirming with the user whether they wish to forgo payment, without typically offering any discounts or promotions; it is merely a simple payment confirmation.

[0099] Figures 3-8 The illustration shows several retention scenarios provided in the embodiments of this application.

[0100] Figure 3 The diagram shown illustrates a scenario where a P0 card is used to retain customers. Figure 3 Figure (a) shows the scenario where a user enters the payment page, where they can complete the payment by clicking the "Confirm Payment" button. However, for various reasons, the user may choose to cancel the payment. When a user cancels the payment, the client will display a P0 card pop-up window, such as... Figure 3 As shown in Figure (b) of the document. Figure 3The P0 card pop-up window shown in Figure (b) includes a prompt to "Confirm to cancel purchase" and a prompt for "Exclusive benefits available after upgrading to VIP". If the user clicks the "Continue Payment" button, the pop-up window closes, and the user remains at the checkout counter. The interface displayed to the user by the electronic device is as follows: Figure 3 As shown in Figure (c), users can complete the payment by clicking the "Confirm Payment" button. If the user clicks the "Cancel Payment" button, the pop-up window closes, the user exits the checkout, and the electronic device displays the following interface to the user: Figure 3 As shown in Figure (d) in the table. Figure 3 The interface shown in Figure (d) can display more detailed rights and benefits information to users, thereby enhancing their willingness to purchase and improving the payment success rate to some extent.

[0101] Figure 4 The illustration shows a scenario for retaining customers during a marketing campaign. Figure 4 Figure (a) shows the scenario where a user enters the payment page, where they can complete the payment by clicking the "Confirm Payment" button. However, for various reasons, the user may choose to cancel the payment. When a user cancels the payment, the client will display a marketing campaign pop-up, such as... Figure 4 As shown in Figure (b) of the document. Figure 4 The marketing pop-up shown in Figure (b) includes a prompt stating "Pay X yuan to get an XX yuan coupon," a message indicating "Remaining time until the end of the promotion," and coupon information. If the user clicks the "Continue Payment" button, the pop-up closes, and the user remains at the checkout counter. The interface displayed to the user by the electronic device is as follows: Figure 4 As shown in Figure (c), users can complete the payment by clicking the "Confirm Payment" button. If the user clicks the "Cancel Payment" button, the pop-up window closes, the user exits the checkout, and the electronic device displays the following interface to the user: Figure 4 As shown in Figure (d) in the table. Figure 4 The interface shown in Figure (d) can display more detailed rights and benefits information to users, thereby enhancing their willingness to purchase and improving the payment success rate to some extent.

[0102] Figure 5 This illustration depicts a scenario where coupons are used to retain users. Coupon retention can also be called coupon expansion retention. Coupons can be expanded based on a user's existing coupons to increase the discount offered to the user. Figure 5 Figure (a) shows the scenario where a user enters the payment page, where they can complete the payment by clicking the "Confirm Payment" button. However, for various reasons, the user may choose to cancel the payment. When a user cancels the payment, the client will display a pop-up window for the expansion coupon, such as... Figure 5 As shown in Figure (b) of the document. Figure 5The pop-up window for the expansion coupon shown in Figure (b) can display relevant information about the expansion coupon to the user, such as the face value of the expansion coupon (e.g., 1 yuan), the applicable threshold of the coupon (e.g., applicable when spending 5 yuan or more), the remaining time before the coupon activity ends, and the restrictions on the coupon (e.g., applicable only to this order).

[0103] If the user clicks Figure 5 The "Continue Payment" button shown in Figure (b) closes the pop-up window, returns the user to the checkout, and refreshes the payment amount based on the coupon. The interface displayed to the user by the electronic device is as follows: Figure 5 As shown in Figure (c), Figure 5 The payment amount shown in Figure (c) is the amount after using the coupon (e.g., the amount before using the coupon is 11.90 yuan, and the amount after using the coupon is 10.90 yuan). Additionally, Figure 5 Image (c) can also display payment discount information; users can access this information by clicking on area ②. Figure 5 The display interface is shown in Figure (d). Figure 5 The (d) image in the image displays details of the coupons used by the user. This interface shows the user information of the selected coupons, as well as the coupon's new label (such as "Valid only for this order" or "Exclusive Coupon"). If the user clicks... Figure 5 The "Abandon Payment" button shown in Figure (b) displays a secondary retention pop-up window to encourage user engagement. Figure 5 As shown in Figure (e). Figure 5 The secondary retention pop-up shown in Figure (e) can include a message such as "This order can be discounted by 1 yuan using a coupon. This discount will be forfeited if you cancel payment. Confirm cancellation." This message aims to increase the likelihood of the user continuing to pay. If the user clicks the "I'll think about it" button, they will be redirected to... Figure 5 As shown in Figure (c), the user can complete the payment by clicking the "Confirm Payment" button. If the user clicks the "Cancel Payment" button, the pop-up window closes, and the user exits the checkout. The electronic device then displays the following interface to the user: Figure 6 As shown in Figure (f).

[0104] After the countdown for the coupon promotion ends, the coupons will expire and revert to their original value as coupons.

[0105] Figure 6 This illustration depicts a scenario for retaining expired coupons. Retaining expired coupons can also be called coupon retention. Expired coupons can be coupons in a user's account that are about to expire. Figure 6Figure (a) shows the scenario where a user enters the payment page, where they can complete the payment by clicking the "Confirm Payment" button. However, for various reasons, the user may choose to cancel the payment. When a user cancels the payment, the client will display an expired coupon pop-up window, such as... Figure 6 Figure (b) in the middle and Figure 6 As shown in Figure (c). Figure 6 Figure (b) in the middle and Figure 6 The expired coupon pop-up shown in Figure (c) can display relevant information about the expired coupon to the user, such as the face value of the coupon (e.g., 5 yuan), the applicable threshold for the coupon (e.g., a no-threshold payment red envelope), and the remaining time of the expired coupon until the end of the activity.

[0106] Figure 6 Figure (b) in the middle and Figure 6 Figure (c) shows two different ways an expired coupon pop-up window will appear. Figure 6 Figure (b) shows users payment method selection buttons, such as "First Payment Method" and "Second Payment Method." Users can access the payment page by clicking the "First Payment Method" or "Second Payment Method" button. The interface displayed to the user by the electronic device is as follows: Figure 6 As shown in Figure (d), users can complete the payment by clicking the "Confirm Payment" button. If the user clicks the "×" button, the pop-up window closes, the client exits the cashier, the user cancels the payment, and the electronic device can display [the payment details]. Figure 6 The interface shown in Figure (e) is shown in the diagram.

[0107] Figure 6 Image (c) can display "Give Up" and "Continue Payment" buttons. By clicking the "Continue Payment" button, the user is taken to the payment page, and the interface displayed by the electronic device is as follows: Figure 6 As shown in Figure (d), users can complete the payment by clicking the "Confirm Payment" button. If the user clicks the "Cancel Payment" button, the pop-up window closes, the client exits the cashier, the user cancels the payment, and the electronic device can display the following information to the user: Figure 7 The interface shown in Figure (e) is shown in the diagram.

[0108] Figure 7 This illustration depicts a scenario where users are retained by offering free coupons. Retention through free coupons can also be called coupon gifting retention. Free coupons refer to new discount coupons offered to users; they can also be referred to as unexpected coupons. Figure 7 Figure (a) shows the scenario where a user enters the payment page, where they can complete the payment by clicking the "Confirm Payment" button. However, for various reasons, the user may choose to cancel the payment. When a user cancels the payment, the client will display a pop-up window for a gift coupon, such as... Figure 7 As shown in Figure (b) of the document. Figure 7The coupon pop-up shown in Figure (b) can display relevant information about the coupon to the user, such as the face value of the coupon (e.g., 1 yuan), the applicable threshold for the coupon (e.g., it can be used when the amount is 5 yuan or more), and the remaining time of the coupon until the end of the promotion.

[0109] If the user clicks the "Continue Payment" button, the pop-up window closes, and the user remains at the checkout counter, where they can continue to complete the payment. If the user clicks the "Cancel Payment" button, the pop-up window closes, and the user exits the checkout counter. The interface displayed to the user by the electronic device is as follows: Figure 7 As shown in Figure (c).

[0110] After the countdown for the free coupon ends and the coupon expires, the message refreshes, the coupon information turns gray, and the "Continue Payment" button becomes unclickable. Users can close the pop-up window and exit the checkout by clicking the "Cancel Payment" button. Figure 8 As shown in Figure (b) of the document.

[0111] Figure 9 This illustration depicts a fallback card used to retain users. The fallback card doesn't display any promotional information; instead, it simply presents a prompt asking the user whether they wish to cancel the payment. The user can complete the payment by clicking the "Continue" button or abandon the payment by clicking the "Cancel" button.

[0112] Generally, when displaying the remaining time for coupons before the end of the promotion, if the remaining time is less than 48 hours, a countdown can be shown to the user; if the remaining time is greater than 48 hours, the countdown can be hidden.

[0113] Figure 9 This shows the user interface for operations personnel. Operations personnel can configure card rules through this interface. Cards here can include P0 cards, non-P0 cards, and catch-all cards mentioned above. Configured card rules can be displayed on this interface, such as... Figure 10 The configured card rules for "cloud-based contract termination and retention" are displayed.

[0114] If operators need to add new card rules, they can click the "Add Configuration" button in the upper right corner to enter... Figure 10 The configuration page shown can include options such as basic configuration, payment retention configuration, and selected configuration. Operations personnel can configure accordingly based on the actual situation.

[0115] The basic configuration interface can be like Figure 10As shown in Figure (a), in this interface, operators can configure information such as strategy name, effective time, and priority. The effective time can be unlimited or within a specified time range. The strategy priority can be any one of P0-P3, where P0 has the highest priority and P3 has the lowest priority. If the strategy priority is P0, it means that the card corresponding to the strategy is a P0 card; if the strategy priority is P3, it means that the card corresponding to the strategy is a P3 card.

[0116] The interface for configuring payment retention can be as follows: Figure 10 As shown in Figure (b), in this interface, operators can configure information such as the type of rights, main title, subtitle, retention icon, stop button text, and termination button text. The configured information can be displayed as follows: Figure 10 The right figure in Figure (b) is shown in the middle.

[0117] The interface for selecting configurations can be as follows: Figure 11 As shown in Figure (c), in this user interface, operators can specify the scope of payment retention. For example, operators can specify business type, game type, application type, product type, target audience, etc., thereby restricting the card's applicability.

[0118] In some implementations, operators can also select switches for various retention scenarios (including card retention, marketing campaign retention, and various coupon retention scenarios) in the payment management server. These switches control whether a matching process for that retention scenario needs to be executed. If the switch is off, it indicates that the current payment order is not suitable for that retention scenario.

[0119] For example, if the switch corresponding to the coupon retention scenario is in the off state, it means that the current payment order cannot be retained using coupons. This coupon retention scenario can be skipped, and the matching process with other retention scenarios can be performed.

[0120] In some implementations, operators can also optimize the big data management platform. For example, they can add additional auxiliary information to the models in the big data management platform, such as delivery addresses and game durations, to improve the model's auxiliary analysis capabilities and inference performance.

[0121] The following is combined Figure 11 This application provides a detailed description of the payment retention method provided in its embodiments.

[0122] Figure 11 The method shown involves the interaction process between the client and the payment management server. The client and payment management server are described above.

[0123] See Figure 10 In step S1110, the client detects the user's payment behavior.

[0124] In some implementations, the client can detect whether it has launched the checkout. If the checkout is launched, it can be determined that the user has made a payment. Detecting payment behavior by checking whether the checkout is launched allows for immediate detection of user payments, improving the timeliness of payment detection.

[0125] In step S1120, if a user's payment behavior is detected, a query request is sent to the payment management server. This query request is used to query retention information.

[0126] In some implementations, the query request can carry order-related information. This information can be used by the payment management server to match retention information.

[0127] In some implementations, the query request can be an HTTP request.

[0128] In some implementations, the query request may include one or more of the following information: order number, product identifier (identity, ID), application ID, and user ID.

[0129] In some implementations, to ensure security and prevent hacker attacks, the client can generate verification information based on at least some information in the query request, using an encryption algorithm. This verification information could be, for example, a purchaseToken verification message. Encryption algorithms include, but are not limited to, asymmetric encryption algorithms and hash algorithms.

[0130] In step S1130, in response to the query request, the payment management server can send retention information to the client.

[0131] In some implementations, the payment management server can determine whether a query request is trustworthy based on the verification information in the query request. If the verification passes, the payment management server responds to the query request; if the verification fails, the payment management server can ignore the query request and not respond to it.

[0132] In some implementations, the payment management server can match retention scenarios for users based on the information carried in the query request, and generate retention information corresponding to the retention scenario.

[0133] In some implementations, embodiments of this application can set the scope of application for each retention scenario. The payment management server can determine whether the current payment order falls within the scope of application based on the information carried in the query request. If the current payment order does not fall within the scope of application, it is determined that the current payment order does not match the retention scenario.

[0134] The retention scenario in this application embodiment can be any one or more of the seven retention scenarios mentioned above.

[0135] For example, taking the P0 card as an example, if the target audience for the P0 card is users aged 20-45, and the user ID in the query request determines that the user age of this payment order is 50 years old, then the payment management server can filter out the P0 card, meaning that the current payment order does not match the P0 card.

[0136] For example, if the applicable goods for the P0 card are consumable goods, and the goods are determined to be consumable goods based on the product ID in the query request, then the payment management server can determine that the current payment order matches the P0 card.

[0137] In some implementations, retention information may include the information that needs to be displayed in the retention pop-up window.

[0138] For example, for card pop-ups (including P0 card pop-ups, non-P0 card pop-ups, and fallback card pop-ups), retention information can include the text content, graphic information, retention button information, card name, etc. that need to be displayed on the card pop-up.

[0139] For example, for coupon pop-ups (including expansion coupon pop-ups, expired coupon pop-ups, and gift coupon pop-ups), retention information can include the text content, graphic information, retention button information, and coupon name that need to be displayed on the coupon pop-up. The text content can include the main title, subtitle, expiration timestamp, coupon face value, coupon name, coupon type, coupon usage threshold, and coupon description information.

[0140] For example, for marketing campaign pop-ups, retention information can include the text content, graphic information, retention button information, and marketing campaign name that need to be displayed on the pop-up. The text content can include a description of the marketing campaign and details about the rebates offered.

[0141] In step S1140, the client concatenates the retention information to obtain a retention pop-up window.

[0142] The client-side splicing of retention information can refer to the client-side formatting of the retention information, such as setting the order of the various parts of the retention information, font size, etc.

[0143] In step S1150, if the user cancels payment, a retention pop-up window is displayed to the user.

[0144] User cancellation of payment can refer to order cancellation, expired renewal, subscription cancellation, or automatic termination of subscription. Users can cancel payment by clicking the "Cancel Payment" button on the payment page or by exiting the payment page.

[0145] This application's embodiment optimizes the loading process by retrieving retention information from the payment management server and generating a retention pop-up window upon detecting a user's payment activity. This ensures the retention information and pop-up window are loaded and assembled before the user cancels the payment. Consequently, the retention pop-up window can be displayed to the user promptly upon payment cancellation, increasing the success rate of displaying the pop-up window and further improving the success rate of the user's payment.

[0146] This application embodiment does not specify a limit on the number of times a user can be retained. The client can attempt to retain a user once or twice.

[0147] In some implementations, the retention information sent by the payment management server to the client may include initial retention information and / or secondary retention information. If the retention information is initial retention information, the retention pop-up displayed to the user by the client is the initial retention pop-up; if the retention information is secondary retention information, the retention pop-up displayed to the user by the client is the secondary retention pop-up.

[0148] Taking retention information, which includes initial retention efforts and secondary retention efforts, as an example, the client can concatenate the initial retention information to obtain an initial retention pop-up window, and concatenate the secondary retention information to obtain a secondary retention pop-up window. If the client detects that the user has cancelled payment, the initial retention pop-up window is displayed to the user for initial retention efforts. If the initial retention effort fails, the secondary retention pop-up window is displayed to the user for secondary retention efforts.

[0149] Compared to the first retention pop-up, the second retention pop-up can display more detailed discount information to users, thereby increasing their willingness to pay and improving the success rate of retention.

[0150] In some implementations, upon detecting a user's payment activity, the client can also send payment order information to the big data management platform. Payment order information may include one or more of the following: transaction amount, order time, product type, and shipping address.

[0151] Big data management platforms can generate coupon information based on payment order information. For example, a big data management platform may have an AI model. The platform can use payment order information as input to the AI ​​model, allowing it to output the coupon information that best suits the user or the user's preferences. This coupon information may include bonus coupons and / or gift coupons.

[0152] The big data management platform can send coupon information to the coupon management server. During the retention scenario matching process, if the matched retention scenario requires new coupons, the payment management server can send a coupon request to the coupon management server, which can then send the coupon information matched by the big data management platform to the payment management server.

[0153] In some implementations, if the matched retention scenario is retention through coupons or gift coupons, then it is determined that the matched retention scenario requires new coupons.

[0154] The payment management server can match retention scenarios to payment orders based on retention strategies. These strategies can include a matching order for various retention scenarios and multiple switches for each scenario. These switches control whether or not the matching process for different retention scenarios is executed. By filtering scenarios through retention strategies, the frequency of coupon requests sent from the payment management server to the coupon management server can be reduced, thus lowering the load on the coupon management server.

[0155] For example, seven switches can be configured for the seven retention scenarios mentioned above. Switch 1 corresponds to the P0 card retention scenario, switch 2 to the marketing campaign retention scenario, switch 3 to the coupon retention scenario, switch 4 to the expired coupon retention scenario, switch 5 to the gift coupon retention scenario, switch 6 to the non-P0 card retention scenario, and switch 7 to the backup card retention scenario. If switch 2 is off, the payment management server does not need to perform the matching process between payment orders and marketing campaign retention scenarios. If switch 3 is on, the payment management server needs to perform the matching process between payment orders and coupon retention scenarios.

[0156] The above example illustrates how each retention scenario corresponds to a switch. In some implementations, switches can be set only for certain retention scenarios, while others are left unset. Retention scenarios without switches will by default require a matching process with the payment order. For example, switches can be set only for coupon and marketing campaign retention scenarios, while card retention scenarios may not require a switch.

[0157] The retention strategy in this application embodiment may include card rules configured by operations personnel. Card rules may include one or more of the following information: card priority, card scope of application, card validity period, and text information on the card. The cards here may include P0 cards, non-P0 cards, and fallback cards.

[0158] Card priority determines the order in which cards are matched. For example, if a P0 card has a high priority, the matching process between payment orders and P0 card retention scenarios will be executed first. If a non-P0 card has a low priority, the matching process between payment orders and non-P0 retention scenario cards will be executed later.

[0159] The card's applicability is used for scenario filtering. If a payment order doesn't fall within the card's applicability scope, the card can be filtered out, and the process of matching it with other retention scenarios can be initiated. Filtering out invalid users can improve retention efficiency and reduce data processing burden.

[0160] The card's validity period is used to determine whether the card is valid. If the validity period expires, the card becomes invalid and will no longer be matched with the user.

[0161] The card's text information can include the main title, subtitle, retention image, "stop" button text, and "cancel" button text, such as... Figure 2 As shown in Figure (b) of the document.

[0162] Operations personnel can collect data on business scope, target audience, specific applications or games, and combine this data with user consumption coefficients (including personal consumption points, consumption expectations, recent consumption frequency, etc.) to generate user group filtering conditions. These filtering conditions can be used to determine the applicable scope of retention scenarios.

[0163] For the first retention scenario among multiple retention scenarios, if the switch corresponding to the first retention scenario is in the off state and / or the first retention scenario does not match the payment order, then based on the matching order in the retention strategy, the matching process with the next retention scenario of the first retention scenario is executed; if the switch corresponding to the first retention scenario is in the on state and the first retention scenario matches the payment order, then the matched retention scenario is determined to be the first retention scenario.

[0164] The first scenario for retaining someone can be any of the scenarios mentioned above.

[0165] Under the condition that the first condition is met, it can be determined that the payment order matches the first retention scenario. The first condition includes one or more of the following: the scope of application of the first retention scenario matches the information of the payment order; the payment order hits the A / B test; the first retention scenario is a coupon retention strategy, and the first retention scenario configures a coupon for the payment order, which is an expansion coupon or a gift coupon.

[0166] Taking the first retention scenario as an example, the first condition may include: the operations staff has configured the card, and the payment order falls within the scope of the card's applicability.

[0167] Taking the first retention scenario as an example of coupon retention scenario, the first condition may include: the payment order falls within the applicable scope of the coupon retention scenario, and the coupon management server has configured the corresponding coupon for the payment order.

[0168] The payment order information in this application may be included in the query request. The payment order information may include one or more of the following: order number, product identifier ID, application ID, and user ID.

[0169] This application embodiment allows for A / B testing of retention scenarios. A payment order is considered a match for the retention scenario only if it successfully completes the A / B test. If the payment order fails to complete the test, it is considered a mismatch. A / B testing can be used to segment user payment orders, allowing for the collection of retention experiment results during testing or commercialization phases to determine whether the campaign should continue.

[0170] For example, the results of an A / B test can be used to determine the status of the switch corresponding to a retention scenario. The results of the A / B test can include the payment success rate of users who adopted the retention strategy in the retention scenario and the payment success rate of users who did not adopt the retention strategy in the retention scenario. By comparing the two payment success rates, the retention effect of the retention strategy can be determined, thereby deciding whether to turn on the switch corresponding to the retention scenario.

[0171] The following is combined Figure 12 The payment retention process of the embodiments of this application will be described in detail.

[0172] The client detects user actions, specifically payment transactions. If a user is detected entering the checkout area, it's confirmed that a payment is in progress. Upon detecting a payment transaction, the client sends a query to the payment management server to retrieve retention information. This embodiment of the application can synchronize the checkout process with the retention information retrieval process. This allows for loading retention information and stitching together the retention pop-up before the user completes payment, ensuring the pop-up is displayed promptly when the user leaves the checkout area, thus improving the success rate of the payment retention system in displaying retention pop-ups.

[0173] In some implementations, the query request may include information related to the current payment order, such as the order number, product ID, application ID, user ID, etc.

[0174] In some implementations, to ensure security and prevent hacker attacks, the client can generate verification information based on at least some information in the query request, using an encryption algorithm. This verification information could be, for example, a purchaseToken verification message. Encryption algorithms include, but are not limited to, asymmetric encryption algorithms and hash algorithms.

[0175] In some implementations, the query request can be an HTTP request.

[0176] After receiving a query request from a client, the payment management server can perform scenario filtering. The server can filter and match scenarios based on retention strategies and information in the query request. Retention strategies can include card rules configured by operations personnel.

[0177] For example, if the target audience for a P0 card is users aged 20-45, but the user's age for this order is determined to be 50 years old based on the user ID in the query request, then the payment management server can filter out the P0 card, meaning the current payment order does not match the P0 card.

[0178] For example, if the applicable goods for the P0 card are consumable goods, and the goods are determined to be consumable goods based on the product ID in the query request, then the payment management server can determine that the current payment order matches the P0 card.

[0179] The payment retention system described in this application provides a weighted configuration strategy interface for potential user groups based on their consumption behavior, such as user group type, age distribution, and spending habits. This interface is used by system operators for configuration. Operators can match retention rules to the retention strategy. The retention rules are mainly determined by the user consumption system, which assigns weights to various parameters or matches coupon values ​​and types based on the current operational activity.

[0180] The following section will provide a detailed introduction to the specific operations of scenario matching for the payment management server.

[0181] For use cases where coupons are not needed, the payment management server can return the configured retention information to the client; for use cases where coupons are needed, the payment management server can send a coupon request to the coupon management server. "Coupons needed" here can refer to the need for expansion coupons and / or gift coupons.

[0182] After receiving a coupon request, the coupon management server can determine the coupon information according to the coupon matching rules and send the coupon information to the payment management server. Additionally, the coupon management server can also add the coupon to the user's account.

[0183] In some implementations, the coupon request can be an HTTP request. The coupon request can include information related to the payment order. The coupon request can include one or more of the following information: coupon type, user ID, order number, etc. The coupon type can include bonus coupons and / or gift coupons.

[0184] The assembly of retention messages can include one or more of the following: activity description text, activity benefit reminders, pop-up display background, and button text information.

[0185] In some implementations, after receiving coupon information, the payment management server can pre-assemble information such as the coupon amount and usage restrictions so that it can quickly pop up when the user client displays a retention pop-up.

[0186] In some implementations, coupon matching rules can be pre-configured by operations personnel. Operations personnel can determine the coupon matching rules based on users' historical consumption information. In other implementations, coupon matching rules can be generated by a big data management platform, which can generate coupon matching rules based on users' historical consumption information.

[0187] After receiving the coupon information sent by the coupon management server, the payment management server can assemble retention information based on the coupon information. For example, it can assemble the coupon-related information used for display to obtain retention information.

[0188] The payment management server can generate retention information for the first retention attempt and retention information for the second retention attempt, and send both the first retention information and the second retention information to the client.

[0189] The payment management server can send retention messages to the client, which can then combine these messages to create a retention pop-up. The client can combine the retention messages from the initial retention attempt to create an initial retention pop-up, and vice versa, creating a secondary retention pop-up.

[0190] When a user clicks "Cancel Payment," an initial retention attempt pop-up can be displayed to try and retain them. If the initial attempt fails, a second retention attempt pop-up can be displayed to try and retain them again. If the second attempt fails, the pop-up can be closed, and the user can exit the checkout.

[0191] In some implementations, when the client detects a user's payment activity, it can also send a reporting message to the big data management platform. This reporting message includes non-privacy information related to the payment order. For example, the reporting message may include one or more of the following: the amount of the transaction, the order time, the type of goods, and the delivery address.

[0192] In some implementations, the big data management platform can match coupon information for users based on this reported message. This coupon information represents the most suitable coupon information matched by the big data management platform for the user. Additionally, the big data management platform can send the matched coupon information to a coupon management server for subsequent use in providing coupons to users.

[0193] In some implementations, the big data management platform can use this reported message to match the most suitable coupon issuance rules for the user and send the coupon issuance rules to the coupon management server.

[0194] The client detects whether the user clicks to cancel payment. During the detection period, the client has completed the acquisition and splicing of retention information, such as pop-ups corresponding to different retention scenarios at the splicing point. When the user clicks to cancel payment, the client can directly show the user a retention pop-up or an initial retention pop-up to retain the user through payment.

[0195] If the retention scenario involves card-based retention, including P0 card retention and non-P0 card retention, the client can display retention cards configured by the operations staff to inform users of potential changes in their consumption behavior after canceling the payment.

[0196] If the retention scenario involves a marketing campaign, the client application can display rebates to users who participate in the campaign. These rebates can include small gifts after a certain number of payments, opportunities to win free orders, participation in lucky draws, and bonus points, all designed to encourage user participation.

[0197] If the retention scenario involves using a coupon inflating the coupon, the client can display to the user that an existing coupon has been inflated into a marketing coupon, and inform the user of the coupon's discount amount, usage threshold, and information about the original coupon to encourage the user to complete the payment. If the retention attempt fails, a second retention attempt can be made, which can display the usage restrictions of the coupon to the user. These restrictions may include usage limited to this promotion, a countdown timer, etc., to inform the user of the scope of use of this coupon. If the second retention attempt fails, after the coupon's countdown ends, the coupon management server will reclaim the coupon and restore the original coupon.

[0198] If the retention scenario involves retaining an expired coupon, the client can display a coupon that is about to expire to inform the user that the coupon is about to expire and the user may miss out on the current promotional offer.

[0199] If the retention strategy involves offering a coupon, the client can display a newly acquired coupon to the user and directly select it for the current payment, encouraging the user to participate in the purchase. If the retention strategy fails, the coupon will be reclaimed by the coupon management server after its countdown ends.

[0200] If the retention scenario involves a fallback card, the client can ask the user to confirm whether they want to cancel the payment.

[0201] It should be noted that for all retention scenarios, the client does not need to exit the checkout during the retention process. Only after the retention fails should the client exit the checkout and end the payment. This ensures that if the retention is successful, the user can complete the payment smoothly.

[0202] Field The interaction process between the big data management platform, the client, and the coupon management server is shown.

[0203] The client can send users' payment order information to the big data management platform. Payment order information can include core parameters and auxiliary parameters. For example, payment order information includes the purchase amount, similar product purchase history, delivery address, order time, product type, and similar product purchase history.

[0204] The big data management platform can calculate the expected value of successful order retention based on the user's recent spending, similar product consumption behavior, and auxiliary information collected by operations (such as delivery address, game time, etc.) through a big model, and match the best coupon value and usage threshold according to the expected value.

[0205] The big data management platform can send the coupon matching rules obtained through training to the coupon management server. Alternatively, the big data management platform can send the face value and usage threshold of the best matched coupon to the coupon management server.

[0206] If the coupon management server receives coupon matching rules, it can match the best coupon according to the rules and send the coupon information and order number to the payment management server. If the coupon management server receives information about the best coupon (including face value and usage threshold), it can directly send the coupon information and order number to the payment management server.

[0207] The coupon management server can synchronize coupon information to the user's account, that is, load the coupon information on the client so that the user can view the coupon information in the account.

[0208] In some implementations, to reduce the frequency of coupon issuance and avoid ineffective retention efforts, the number of coupons issued to users can be limited. After each coupon is issued to a user, the coupon management server increments the issuance count by 1. When the issuance count exceeds a preset threshold (the system-set upper limit), the coupon management server can stop responding to coupon issuance. In other words, even if the payment management server's retention strategy determines that providing coupons to users is a retention plan, the coupon management server will not provide any coupon information to the payment management server because the maximum number of coupons issued to users has already been reached.

[0209] This application embodiment can count the number of times expansion coupons and gift coupons are issued together, or count them separately.

[0210] For example, if the number of times expansion coupons and gift coupons are issued are counted together, the number of issuances will be incremented by 1 each time an expansion coupon is issued to a user, and the number of issuances will also be incremented by 1 each time a gift coupon is issued to a user. When the number of issuances reaches the upper limit, the coupon management server will not respond to the coupon request, regardless of whether the payment management server requests an expansion coupon or a gift coupon from the coupon management server.

[0211] If the issuance frequency of expansion coupons and gift coupons is counted separately, the issuance frequency of expansion coupons can be counted using counter 1, and the issuance frequency of gift coupons can be counted using counter 2. Each time an expansion coupon is issued to a user, the value of counter 1 is incremented by 1; each time a gift coupon is issued to a user, the value of counter 2 is incremented by 1. When the value of counter 1 reaches its maximum value, the coupon management server stops responding to the issuance of expansion coupons; when the value of counter 2 reaches its maximum value, the coupon management server stops responding to the issuance of gift coupons. The maximum values ​​of counter 1 and counter 2 can be the same or different; this embodiment does not specifically limit this.

[0212] The payment management server can assemble retention information. For example, in scenarios where coupons are not needed, the payment management server can assemble basic retention information. In scenarios where coupons are needed, the payment management server can assemble retention information related to the coupons to be displayed, as well as basic retention information.

[0213] For example, assembling coupon information mainly includes assembling one or more of the following information: coupon batch number, coupon code, coupon name, coupon description, coupon type, coupon type name, actual discount amount, face value, balance, applicable conditions, validity period, whether it is available, whether it is about to expire, coupon validity period start timestamp, coupon validity period end timestamp, whether it is recommended to use, coupon package ID, whether it is selected, etc.

[0214] The assembly information returned by the payment management server to the client may include one or more of the following: core voucher information, auxiliary voucher information, and secondary retention instruction information. The secondary retention instruction information is used to indicate that the retention information is intended for secondary retention efforts.

[0215] Tables 1-4 show the retention information corresponding to several retention scenarios.

[0216] Table 1 shows the content of the retention information corresponding to the inflated coupon (couponInflationInfo). This retention information may include the main title (title), subtitle (subTitle), expiration timestamp (expirationTime), inflated face value (couponAmountPattern), original face value (oldCouponAmountPattern), inflated coupon name (couponName), original coupon name (oldCouponName), inflated coupon description (couponDesc), original coupon description (oldCouponDesc), maximum inflated amount (InflationQuotaText), inflated restriction information (InflationRestrictText), retention button information (retentionButtonList), and secondary retention information (secondRetention).

[0217] Table 1

[0218]

[0219]

[0220] Table 2 shows the content of the retention information (couponGiftInfo) corresponding to the gift coupon. This retention information may include the main title (title), subtitle (subtitle), expiration timestamp (expirationTime), expiration reminder time range (expirationReminderDuration), coupon value (couponAmountPattern), coupon name (couponName), coupon description information (couponDesc), retention button information (retentionButtonList), and secondary retention information (secondRetention).

[0221] Table 2

[0222]

[0223]

[0224] Table 3 shows the retention information (erer) for expired coupons. This retention information may include a title, a description of the offer (benefitDesc), and retention button information (retentionButtonList).

[0225] Table 3

[0226] Description Type Whether null title Hello {benefitDesc} Hello String benefitDesc N For example: 3 yuan discount String retentionButtonList N Retention button Figure 13 List <retentionbutton> < / retentionbutton> N

[0227] Table 4 shows the specific information for the Retention Button. The Retention Button information may include the button name (buttonText), button code (buttonCode), and button type (buttonType).

[0228] Table 4

[0229]

[0230] Figure 13 The process for handling coupons is shown below. Figure 14 The process for processing coupons will be explained in detail.

[0231] When a user initiates a payment, the client redirects to the payment page and sends a retention request to the payment retention system. This retention request corresponds to the query request mentioned above.

[0232] After receiving a retention request, the payment retention system can match coupons for the current payment order and send the coupon information to the client.

[0233] After receiving the coupon information, the client preloads the coupon details and displays the coupon to the user when the user cancels payment. If the user completes payment, the retention process is successful.

[0234] If the user leaves or closes the retention pop-up, the system will display the coupon details to attempt a second retention effort. If the user completes the payment, the retention effort is successful; if the user cancels the payment, the second retention effort fails, the payment retention system will reclaim the coupon, and remove it from the user's account.

[0235] The following is combined Figure 14 This application provides a detailed description of the retention strategies involved in the embodiments.

[0236] The retention strategies in this application involve a variety of retention scenarios, which may include retention using P0 cards, marketing activities, expansion coupons, expired coupons, gift coupons, non-P0 cards, and fallback cards.

[0237] The retention strategy includes the matching order of multiple retention scenarios and the matching rules for these scenarios. The matching order refers to the sequence of matching different retention scenarios, from first to last. For example, the matching order provided in this embodiment could be: P0 card retention → marketing campaign retention → coupon retention → expired coupon retention → gift coupon retention → non-P0 card retention → fallback card retention. In other words, after receiving a query request from the client, the payment management server can first perform the matching for the P0 card retention scenario to determine if the current payment order is suitable for P0 card retention. If it is not suitable, the matching for the marketing campaign retention scenario is then performed to determine if the current payment order is suitable for marketing campaign retention, and so on, until a match is found or a retention scenario is hit, at which point the matching process ends. The payment management server can then assemble retention information based on the matched retention scenarios.

[0238] The matching rule refers to the value that specifies which actions should be taken for a particular retention attempt scenario to determine whether the current payment order matches that scenario. Figure 14 Taking the P0 card retention scenario as an example, the payment management server can first query the information of the current payment order. After retrieving the order information, it can query for P0 card retention to determine whether P0 card retention exists. If P0 card retention exists, then the current payment order matches the P0 card retention scenario; if P0 card retention does not exist, then the current payment order does not match the P0 card retention scenario. Other retention scenarios are similar and will not be listed here. For details, please refer to the process description below.

[0239] In some implementations, embodiments of this application may also set a switch for each retention scenario, which controls whether to execute a matching process for that retention scenario. Figure 14 For example, if the marketing retention scenario is off and the coupon retention scenario is on, then after the current payment order fails to match the P0 card retention scenario, the matching process of the marketing retention scenario can be skipped directly, and the matching process of the coupon retention scenario can be executed.

[0240] In some implementations, the on / off state of the switch can be pre-configured by the operations staff. The operations staff can determine the on / off state based on the historical consumption records of one or more users. For example, if the success rate of a certain retention scenario is relatively low, the operations staff can turn off the switch for that scenario; if the success rate of a certain retention scenario is relatively high, the operations staff can turn on the switch for that scenario.

[0241] In some implementations, the on / off state of the switch can be dynamically adjusted based on the results of A / B testing. For each retention scenario, payment orders can be routed through A / B testing. If the A / B test is successful, the matching process for that retention scenario can continue; if not, the process can jump to the next retention scenario for matching. By comparing the payment success rates corresponding to successful and unsuccessful A / B tests, it is determined whether the switch for that retention scenario needs to be turned off. For example, if the payment success rate for successful A / B tests is lower than that for unsuccessful A / B tests, it indicates that the retention effect of that scenario is poor, and the switch for that scenario can be turned off to reduce power consumption.

[0242] In some implementations, the initial on / off state of the switch is manually configured by the operators. During the use of retention strategies, the on / off state of the switch can be dynamically adjusted based on the results of A / B experiments.

[0243] The following is combined Figure 15 The matching process for retention scenarios in the embodiments of this application will be described in detail.

[0244] Upon receiving a query request from the client, the payment management server can first perform matching for P0 card retention.

[0245] The payment management server queries order information and, based on this information, checks the P0 card retention rules to determine if P0 card retention exists. If P0 card retention exists, the dialog type and content can be set. For example, dialogType can be set to 5, and the content can be set to pictureRetentionCardInfo.

[0246] The existence of a P0 card can be determined based on the operator's configuration. If the operator has not configured a P0 card, then a P0 card does not exist. If the operator has configured a P0 card and set its applicable scope, then a P0 card exists if the current order falls within that scope; otherwise, a P0 card does not exist.

[0247] If a P0 card exists, it means that this order matches the P0 card retention scenario. The payment management server can then configure the retention information for the P0 card and end the retention scenario matching process. If a P0 card does not exist, it means that this order does not match the P0 card retention scenario. The payment management server can then proceed with the matching process for a marketing campaign retention scenario.

[0248] If the marketing campaign retention scenario switch is on, the matching process for the marketing campaign retention scenario continues; if the marketing campaign retention scenario switch is off, the marketing campaign retention scenario is skipped, and the matching process for the coupon retention scenario is executed instead.

[0249] If the marketing campaign retention scenario is enabled, the payment management server determines whether marketing banner data is included and whether the display strategy is matched. If marketing banner data is included, the pop-up type is set (e.g., dialogType=1). The payment management server can query the A / B test to determine if this payment order matches the A / B test. If it matches the A / B test, the test information (ab TestInfo) is set; otherwise, the process jumps to the coupon retention scenario matching process.

[0250] If the A / B test is successful, set the test information (ab TestInfo) to determine if the pop-up policy is applied. If the pop-up policy is applied, set the pop-up type (e.g., dialogType=1) and pop-up content (e.g., marketingCampaignInfo). If the pop-up policy is not applied, set the pop-up type (e.g., dialogType=0).

[0251] Whether the pop-up policy is triggered could refer to whether a preset number of payments has been reached. If the preset number of payments has been reached, the pop-up policy is triggered; if the preset number of payments has not been reached, the pop-up policy is not triggered.

[0252] If the switch for retaining the coupon is on, the matching process for retaining the coupon continues; if the switch for retaining the coupon is off, the coupon retention process is skipped, and the matching process for retaining expired coupons is executed.

[0253] If the coupon retention scenario is enabled, the payment management server queries the user's account for all coupon information. This coupon information can be sent to the payment management server by the client or obtained by the payment management server through a coupon API call. The payment management server determines whether the user's account contains any coupons. If no coupons are found, the process proceeds to the expired coupon retention scenario matching process.

[0254] If a coupon exists, query the marketing-side expansion coupon. The payment management server sends a coupon usage request to the coupon management server, which is used to query the expansion coupon. If the expansion coupon exists, the coupon management server can send the expansion coupon information to the payment management server; if the expansion coupon does not exist, the coupon management server may not send a response message to the payment management server, or it may send a response message to the payment management server indicating that the expansion coupon does not exist.

[0255] If no expansion coupon exists, proceed to the matching process for expired coupon retention. If an expansion coupon exists, set the pop-up type (e.g., dialogType=8) and pop-up content (e.g., expansionCouponInfo).

[0256] If the expired coupon retention scenario is on, the matching process for the expired coupon retention scenario will continue; if the expired coupon retention scenario is off, the expired coupon retention scenario will be skipped, and the matching process for the gift coupon retention scenario will be executed.

[0257] If the expired coupon retention feature is enabled, the payment management server queries the user's account for coupon information. This coupon information can be sent from the client to the payment management server, or obtained by the payment management server through a coupon API call. This coupon information can refer to selected coupons or specific coupons; for example, coupons with an expiration date of less than 48 hours.

[0258] The payment management server determines whether the specific coupon exists. If it does not exist, it proceeds to the matching process for the coupon retention scenario. If the coupon exists, it queries the A / B test. The payment management server determines whether the current payment order matches the A / B test. If it does not match the A / B test, it proceeds to the matching process for the coupon retention scenario. If it matches the A / B test, it sets the pop-up type (e.g., dialogType=2), pop-up content (e.g., couponValidityInfo), and test information (e.g., ab TestInfo).

[0259] If the coupon retention scenario is enabled, the matching process for the coupon retention scenario continues; if the coupon retention scenario is disabled, the coupon retention scenario is skipped, and the matching process for the non-P0 card retention scenario is executed.

[0260] If the coupon retention mechanism is enabled, the payment management server queries the user's account for coupon information. This coupon information can be sent from the client to the payment management server, or obtained by the payment management server through a coupon API call.

[0261] The payment management server determines whether a coupon exists in the user's account. If a coupon exists, the process proceeds to the matching phase for non-P0 card retention scenarios; if no coupon exists, the server queries the marketing side for promotional coupons. The payment management server sends a coupon usage request to the coupon management server, which requests the query for promotional coupons. If a promotional coupon exists, the coupon management server can send the coupon information to the payment management server; if no promotional coupon exists, the coupon management server may choose not to send a response message to the payment management server, or it may send a response message indicating that no promotional coupon exists.

[0262] The payment management server determines whether a gift coupon exists. If no gift coupon exists, it redirects to the matching process for non-P0 card retention scenarios. If a gift coupon exists, it sets the pop-up type (e.g., dialogType=9) and pop-up content (e.g., rewardCouponInfo).

[0263] For non-P0 card retention scenarios, the payment management server can query the non-P0 card retention rules and determine whether a non-P0 card exists. If a non-P0 card retention scenario exists, the pop-up type (e.g., dialogType=5) and pop-up content (e.g., pictureRetentionCardInfo) can be set.

[0264] The existence of non-P0 cards can be determined based on the operations personnel's configuration. If the operations personnel have not configured non-P0 cards, then non-P0 cards do not exist. If the operations personnel have configured non-P0 cards and set an applicable scope for them, then a non-P0 card exists if the current order falls within that scope; otherwise, a non-P0 card does not exist.

[0265] If a non-P0 card exists, it means this order matches a non-P0 card retention scenario. The payment management server can then assemble the retention information for the non-P0 card and end the retention scenario matching process. If no non-P0 card exists, it means this order does not match a non-P0 card retention scenario. The payment management server can then proceed with the matching process for a fallback card retention scenario.

[0266] For scenarios involving retaining customers with backup cards, the payment management server can set the pop-up type (e.g., dialogType=0).

[0267] The solution proposed in this application can be applied to in-app payments as well as other payment scenarios. For other payment scenarios, the payment retention system proposed in this application can be migrated after improving access to personal computers (PCs) and websites (web), that is, the corresponding retention solution can be implemented by calling the payment retention system proposed in this application.

[0268] It should be noted that third-party shopping platforms (third-party clients) can use the system described in this application to retain users through payment.

[0269] Figure 16 This paper illustrates an application scenario for PC payment. Even when a user's triggered payment behavior (i.e., the user submits a payment order) is detected, the user can still choose to access the payment retention system of this application embodiment.

[0270] The payment cancellation behavior in this application embodiment can be integrated with user cancellation of subscription, automatic termination of subscription, and other behaviors, and incorporated into the payment retention system. Figure 16 This demonstrates a retention strategy after a user cancels automatic renewal for a scenario involving automatic subscriptions.

[0271] See Figure 16 ,exist Figure 16 In Figure (a), if a user clicks the "Close Service" button, it means that the user has cancelled the payment. In this case, a retention pop-up window can be displayed to the user. Figure 16 Figure (b) in the middle Figure 16 Figure (c) in the middle and Figure 16 Figure (d) in the middle shows three types of retention pop-ups.

[0272] See Figure 16 In Figure (b), the retention pop-up can display a "Confirm closure of this service" prompt to the user, along with promotional information such as "We're giving you 30 days of VIP membership. Upon successful renewal, you'll enjoy ample storage space and benefits." If the user clicks the "Accept" button, the pop-up closes, and the next automatic payment is postponed by 30 days. If the user clicks the "Close Service" button, the pop-up closes, and the cancellation process continues. If the membership is cancelled, this operational configuration is no longer effective.

[0273] See Figure 16 As shown in Figure (c), the retention pop-up can display a "Confirm to close this service" prompt to the user, as well as show the VIP benefits that can be enjoyed by continuing to retain the service. If the user clicks the "Continue" button, the pop-up closes and the renewal continues. If the user clicks the "Close Service" button, the pop-up closes and the termination process continues.

[0274] See Figures 17-20As shown in Figure (d), this retention pop-up can display a "Confirm closure of this service" prompt to the user, as well as information about the benefits that will be lost after canceling automatic renewal. If the user clicks the "Continue" button, the pop-up closes and the renewal process continues. If the user clicks the "Close Service" button, the pop-up closes and the termination process continues.

[0275] The foregoing has detailed examples of the methods provided in this application. It is understood that the corresponding apparatus, in order to achieve the above functions, includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0276] This application can divide the payment retention device into functional modules based on the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0277] The payment retention device in this application embodiment can be an electronic device or a server, or the payment retention device can be a chip or the like used to implement the above method.

[0278] The following is combined Figure 17 The following describes the device embodiments of this application. It should be noted that the device embodiments correspond to the method embodiments, and any content not described in detail can be found in the method embodiments.

[0279] Figure 18 This is a schematic block diagram of an electronic device provided in an embodiment of this application. The electronic device has a client installed on it. The electronic device 1700 includes a detection module 1710, a sending module 1720, a receiving module 1730, a splicing module 1740, and a display module 1750.

[0280] The detection module 1710 is used to detect the user's payment behavior.

[0281] The sending module 1720 is used to send a query request to the payment management server when the user's payment behavior is detected. The query request is used to query retention information.

[0282] The receiving module 1730 is used to receive the retention information sent by the payment management server, the retention information including initial retention information and / or secondary retention information.

[0283] The splicing module 1740 is used to splice the retention information to obtain a retention pop-up window.

[0284] The display module 1750 is used to display the retention pop-up window to the user when the user cancels payment.

[0285] In some implementations, the retention information includes initial retention information and secondary retention information. The splicing module 1740 is used to: splice the initial retention information to obtain an initial retention pop-up window; and splice the secondary retention information to obtain a secondary retention pop-up window. The display module 1750 is used to: display the initial retention pop-up window to the user when the user cancels payment, in order to perform an initial retention attempt; and display the secondary retention pop-up window to the user when the initial retention attempt fails, in order to perform a secondary retention attempt.

[0286] In some implementations, the sending module 1720 is further configured to: send payment order information to a big data management platform when the user's payment behavior is detected, wherein the payment order information is used by the big data management platform to generate coupon information based on an artificial intelligence (AI) model; receiving the retention information sent by the payment management server includes: receiving the retention information assembled by the payment management server based on the coupon information; wherein the payment order information includes one or more of the following: consumption amount, order time, product type, and delivery address.

[0287] In some implementations, the query request includes one or more of the following information: order number, product identifier ID, application ID, and user ID, and the information in the query request is used by the payment management server to match the retention information.

[0288] In some implementations, the detection module is used to detect the client's operation of pulling up the cashier; the electronic device further includes a determination module, used to determine that the user has made a payment if the client is detected pulling up the cashier.

[0289] Figure 19 This is a schematic block diagram of a payment management server provided in an embodiment of this application. The payment management server 1800 includes a receiving module 1810 and a sending module 1820.

[0290] The receiving module 1810 is used to receive a query request sent by the client. The query request is used to query retention information and is sent when the user has made a payment.

[0291] The sending module 1820 is used to send the retention information to the client in response to the query request. The retention information includes initial retention information and / or secondary retention information. The initial retention information is used to make an initial retention attempt on the user, and the secondary retention information is used to make a secondary retention attempt on the user if the initial retention attempt fails.

[0292] In some implementations, the query request includes payment order information. Before the sending module 1820 sends the retention information to the client, the payment management server further includes a matching module, configured to: respond to the query request and match a retention scenario for the payment order based on a retention strategy; the sending module 1820 is also configured to: if the matched retention scenario requires a new coupon, send a coupon request to the coupon management server; the receiving module 1810 is also configured to: receive the information of the new coupon sent by the coupon management server; the payment management server further includes a generation module, configured to: generate the retention information based on the information of the new coupon.

[0293] In some implementations, the payment management server further includes a determination module, used to: if the matched retention scenario is retention with an expansion coupon or a gift coupon, then determine that the matched retention scenario requires a new coupon.

[0294] In some implementations, the receiving module 1810 is further configured to: receive the retention strategy configured by the operations personnel, the retention strategy including card rules configured by the operations personnel, the card rules including rules for a first card and / or rules for a second card, the card rules including one or more of the following information: card priority, card scope of application, card validity period, and text information on the card, wherein the first card is the card with the highest priority, and the second card is the card with a priority between the priority of the first card and the priority of the fallback card.

[0295] In some implementations, the retention strategy includes a matching order of multiple retention scenarios and multiple switches for the multiple retention scenarios. The multiple switches are used to control whether to execute the matching process of the multiple retention scenarios. The multiple retention scenarios include one or more of the following: first card retention, marketing activity retention, expansion coupon retention, expired coupon retention, gift coupon retention, second card retention, and fallback card retention.

[0296] In some implementations, the matching module is used to: for a first retention scenario among the multiple retention scenarios, if the switch corresponding to the first retention scenario is in the off state and / or the first retention scenario does not match the payment order, then based on the matching order, perform a matching process with the next retention scenario of the first retention scenario; if the switch corresponding to the first retention scenario is in the on state and the first retention scenario matches the payment order, then determine the matched retention scenario as the first retention scenario.

[0297] In some implementations, the payment management server further includes a determination module, configured to: determine that the payment order matches the first retention scenario if a first condition is met, wherein the first condition includes one or more of the following: the scope of application of the first retention scenario matches the information of the payment order; the payment order hits an A / B test; the first retention scenario is a coupon retention strategy, and the first retention scenario configures a coupon for the payment order, wherein the coupon is an expansion coupon or a gift coupon.

[0298] In some implementations, the payment order information includes one or more of the following: order number, product ID, application ID, and user ID.

[0299] Figure 20 This is a schematic block diagram of a coupon management server provided in an embodiment of this application. The coupon management server 1900 includes a receiving module 1910 and a sending module 1920.

[0300] The receiving module 1910 is used to receive a coupon request sent by the payment management server, wherein the coupon request is used to request an expansion coupon or a gift coupon;

[0301] The sending module 1920 is used to send coupon information to the payment management server in response to the coupon request. The coupon information includes information on expansion coupons or gift coupons. The coupon information is used to generate retention information to retain users.

[0302] In some implementations, the coupon request includes payment order information, and the coupon management server further includes a matching module for: matching the payment order based on coupon matching rules to obtain coupons that match the payment order.

[0303] In some implementations, the coupon matching rules are configured by the operators in the coupon management server.

[0304] In some implementations, the coupon information is generated by a big data management platform based on payment order information. The payment order information includes one or more of the following: consumption amount, order time, product type, and delivery address. The payment order information is sent from the client to the big data management platform.

[0305] In some implementations, the coupon management server further includes a recycling module for recycling coupons issued to users, including expansion coupons or gift coupons, in the event of a failed retention attempt. Specifically, the recycling module is used to delete the coupon from the user's account after the coupon's validity period has expired.

[0306] In some implementations, the coupon management server further includes a processing module, configured to: increment the value of a first counter by 1 after sending coupon information to the payment management server once; and stop responding to coupon requests from the payment management server after the value of the first counter reaches a preset threshold.

[0307] Figure 20 This is a schematic structural diagram of the device according to an embodiment of this application. ​ The dashed lines indicate that the unit or module is optional. The device 2000 can be used to implement the methods described in the above method embodiments. The device 2000 can be a chip, an electronic device, a payment management server, or a coupon management server.

[0308] Apparatus 2000 may include one or more processors 2010. The processor 2010 may support apparatus 2000 in implementing the methods described in the preceding method embodiments. The processor 2010 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0309] The apparatus 2000 may also include one or more memories 2020. The memories 2020 store a program that can be executed by the processor 2010, causing the processor 2010 to perform the methods described in the preceding method embodiments. The memories 2020 may be independent of the processor 2010 or integrated into the processor 2010.

[0310] The device 2000 may also include a transceiver 2030. The processor 2010 can communicate with other devices or chips through the transceiver 2030. For example, the processor 2010 can send and receive data with other devices or chips through the transceiver 2030.

[0311] This application also provides a chip including a processor, which is used to read and execute a computer program stored in a memory to perform the payment retention method described in any of the above embodiments.

[0312] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to perform the payment retention method described in any of the above embodiments.

[0313] This application also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement the payment retention method described in the above embodiments.

[0314] In this embodiment, the electronic device, computer-readable storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0315] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection between devices or units. The replaced units may or may not be physically separate. The component shown as a unit may be one physical unit or multiple physical units, that is, it may be located in one place or distributed in multiple different places. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0316] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0317] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0318] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0319] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A payment retention method, characterized in that, The method is applied to the client and includes: Detect user payment behavior; Upon detecting that the user has made a payment, a query request is sent to the payment management server. The query request is used to query retention information. Receive the retention information sent by the payment management server, the retention information including initial retention information and / or secondary retention information; The retention information is concatenated to obtain a retention pop-up window; If the user cancels payment, the retention pop-up window will be displayed to the user.

2. The method according to claim 1, characterized in that, The retention information includes initial retention information and secondary retention information. The process of concatenating the retention information to obtain a retention pop-up window includes: The initial retention information is pieced together to obtain the initial retention pop-up window; The secondary retention information is spliced ​​together to obtain a secondary retention pop-up window; The step of displaying the retention pop-up to the user upon detecting that the user has cancelled payment includes: If the user cancels payment, the initial retention pop-up window is displayed to the user to attempt an initial retention effort. If the initial attempt to retain the user fails, a second attempt to retain them will be made.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Upon detecting that the user has made a payment, payment order information is sent to the big data management platform. This payment order information is used by the big data management platform to generate coupon information based on an artificial intelligence (AI) model. The receipt of the retention information sent by the payment management server includes: Receive the retention information assembled by the payment management server based on the coupon information; The payment order information includes one or more of the following: consumption amount, order time, product type, and delivery address.

4. The method according to any one of claims 1-3, characterized in that, The query request includes one or more of the following information: order number, product ID, application ID, and user ID. The information in the query request is used by the payment management server to match the retention information.

5. The method according to any one of claims 1-4, characterized in that, The detection of user payment behavior includes: The system detects the client's operation of launching the cashier. The method further includes: If the client initiates a payment transaction, it is determined that the user has made a payment.

6. A payment retention method, characterized in that, The method is applied to a payment management server and includes: Receive a query request sent by the client. The query request is used to query retention information and is sent when the user has made a payment. In response to the query request, the retention information is sent to the client. The retention information includes initial retention information and / or secondary retention information. The initial retention information is used to make an initial retention attempt on the user, and the secondary retention information is used to make a second retention attempt on the user if the initial retention attempt fails.

7. The method according to claim 6, characterized in that, The query request includes payment order information. Before sending the retention message to the client, the method further includes: In response to the query request, a retention scenario is matched for the payment order based on the retention strategy; If the matched retention scenario requires a new coupon, a coupon request is sent to the coupon management server; Receive information about the new coupon sent by the coupon management server; Based on the information of the new coupon, the retention information is generated.

8. The method according to claim 7, characterized in that, The method further includes: If the matched retention scenario is retention through coupons or gift coupons, then it is determined that the matched retention scenario requires new coupons.

9. The method according to claim 7 or 8, characterized in that, The method further includes: The system receives the retention strategy configured by the operations personnel. The retention strategy includes card rules configured by the operations personnel. These card rules include rules for a first card and / or rules for a second card. Each card rule includes one or more of the following information: card priority, card scope of application, card validity period, and text information on the card. Among them, the first card is the card with the highest priority, and the second card is the card with a priority between the priority of the first card and the priority of the fallback card.

10. The method according to claim 9, characterized in that, The retention strategy includes a matching order of multiple retention scenarios and multiple switches for the multiple retention scenarios. The multiple switches are used to control whether to execute the matching process of the multiple retention scenarios. The multiple retention scenarios include one or more of the following: first card retention, marketing activity retention, expansion coupon retention, expired coupon retention, gift coupon retention, second card retention, and fallback card retention.

11. The method according to claim 10, characterized in that, The method of matching retention scenarios for the payment order based on retention strategies includes: For the first retention scenario among the multiple retention scenarios, if the switch corresponding to the first retention scenario is in the off state and / or the first retention scenario does not match the payment order, then based on the matching order, the matching process with the next retention scenario of the first retention scenario is executed; If the switch corresponding to the first retention scenario is in the on state and the first retention scenario matches the payment order, then the matched retention scenario is determined to be the first retention scenario.

12. The method according to claim 11, characterized in that, The method further includes: If the first condition is met, the payment order is determined to match the first retention scenario, wherein the first condition includes one or more of the following: The scope of application of the first retention scenario matches the information of the payment order; The payment order hit the AB test; The first retention scenario is a coupon retention strategy, and the first retention scenario is configured with a coupon for the payment order, which is an expansion coupon or a gift coupon.

13. The method according to any one of claims 7-12, characterized in that, The payment order information includes one or more of the following: order number, product ID, application ID, and user ID.

14. An electronic device, characterized in that, The electronic device has a client installed on it, and the electronic device includes a memory and a processor. The memory stores a computer program that can run on the processor, and the processor executes the computer program to implement the method as described in any one of claims 1 to 5.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, causes the processor to perform the method as described in any one of claims 1 to 5.

Images