Data processing method and device in cooperative payment, equipment, storage medium and program product

Abstract

The invention provides a data processing method and device in cooperative payment, equipment, a storage medium and a program product, and relates to the technical field of mobile internet. The method comprises the following steps: acquiring payment activity page information of a target user and determining role information of the target user; in response to determining that the role of the target user is an invited party, querying a payment activity state in the target task table; in response to determining that the payment activity state is uncompleted, sending a payment window to the client device; in response to determining that the target user successfully pays through the payment window, updating the target task table; in response to the condition that the current total payment amount corresponding to the target user group in the target task table is greater than the preset payment amount, obtaining all up-to-standard user information in the target user group in the target task table; and according to the up-to-standard user information, payment up-to-standard information is sent to client equipment of each up-to-standard According to the method, the payment experience of the user during cooperative payment can be improved, and the storage burden is effectively reduced.

Description

Technical Field

[0001] The present application relates to the field of mobile Internet technology, and in particular to a data processing method, device, equipment, storage medium and program product in cooperative payment. Background Art

[0002] At present, the living expense payment platform has greatly facilitated the daily life of users. Users can pay water, electricity, gas or heating fees, etc. through the existing living expense payment platform. An existing living expense payment platform allows multiple users to cooperate in payment, thereby increasing the user's enthusiasm for payment.

[0003] However, when the existing living expense payment platform processes data in cooperative payment, it requires the invited user to confirm whether to participate in the cooperative payment, which affects the customer's payment experience, and needs to record the confirmation status of the inviting user and the invited user, thereby increasing the storage burden of the living expense payment platform. Summary of the invention

[0004] The present application provides a data processing method, device, equipment, storage medium and program product in cooperative payment to solve the problems in the prior art.

[0005] In a first aspect, the present application provides a data processing method in cooperative payment, comprising:

[0006] Obtaining payment activity page information of a target user, where the target user is a user who triggers the payment activity page on a client device;

[0007] Determine the role information of the target user based on the payment activity page information, the role information being the inviter or the invitee;

[0008] In response to determining that the role of the target user is an invited party, querying the payment activity status in the target task table based on the payment activity page information, the payment activity status being completed or incomplete;

[0009] In response to determining that the payment activity status is incomplete, sending a payment window to the client device to display the payment window on the client device;

[0010] In response to determining that the target user has successfully paid through the payment window, updating the target task table based on the payment information of the target user;

[0011] In response to the current total payment amount corresponding to the target user group in the target task table being greater than the preset payment amount, obtaining all qualified user information in the target user group in the target task table, wherein the target user group is used to store user information that belongs to the same cooperative payment group as the target user and has successfully paid;

[0012] The payment compliance information is sent to the client device of each qualified user according to the qualified user information, so that the payment compliance information is displayed on the payment activity page.

[0013] In a possible design, determining the role information of the target user based on the payment activity page information includes:

[0014] Determine whether the page link of the payment activity page has a payment activity group identifier and a forwarding identifier;

[0015] If it is determined that the page link of the payment activity page has a payment activity group identifier and a forwarding identifier, then the role of the target user is determined to be an invitee;

[0016] If it is determined that there is no payment activity group identifier and forwarding identifier in the page link of the payment activity page, then the role of the target user is determined to be the inviter.

[0017] In one possible design, it also includes:

[0018] In response to determining that the role of the target user is an invitee, querying the target task table to see whether there is a payment activity group identifier in the page link;

[0019] If the payment activity group identifier does not exist in the target task table, the payment activity group identifier and the forwarding identifier in the page link are added to the target task table, where the forwarding identifier is the user identifier of the inviting party.

[0020] In a possible design, after determining that the role of the target user is the inviting party, the method further includes:

[0021] Add the payment activity group identifier and the forwarding identifier to the corresponding page link of the payment activity page.

[0022] In one possible design, it also includes:

[0023] In response to determining that the target user has completed payment, the payment activity group identifier in the page link and the user identifier of the target user are added to the target task table.

[0024] In a possible design, the payment information includes a payment activity group identifier, a user identifier, and a payment amount, and the target task table includes a payment activity group identifier, a target user group, and a current total payment amount;

[0025] In response to the target user successfully paying through the payment window, updating the target task table based on the payment information of the target user includes:

[0026] Determine the target user group and the current total payment amount corresponding to the payment activity group identifier in the target task table based on the payment activity group identifier in the payment information;

[0027] Adding the user identification in the payment information to the target user group;

[0028] The current total payment amount is updated based on the payment amount in the payment information to obtain an updated current total payment amount.

[0029] In a possible design, the payment compliance information is sent to the client device of each qualified user according to the qualified user information, so as to display the payment compliance information on the payment activity page, including:

[0030] The payment achievement information and the corresponding achievement object information are sent to the client device of each meeting user according to the achievement user information, so that the payment achievement information and the achievement object information are displayed on the payment activity page.

[0031] In a possible design, before sending the payment compliance information and the corresponding compliance object information to the client device of each compliance user according to the compliance user information, the method further includes:

[0032] Obtain the payment activity group identifier corresponding to the target user group that completes the payment task in the target task table;

[0033] The name of the target-reaching income object corresponding to the payment activity group identifier in the target-reaching income object table is determined based on the payment activity group identifier.

[0034] In one possible design, it also includes:

[0035] In response to the payment activity status being determined to be completed, the current payment activity completion information and the payment activity selection window are sent to the client device to display the current payment activity completion information and the payment activity selection window on the client device. The payment activity selection window is used for the target user to start a new group of payment activities or leave the payment activity page.

[0036] In a second aspect, the present application provides a data processing device in cooperative payment, comprising:

[0037] An acquisition module, used to acquire payment activity page information of a target user, where the target user is a user who triggers the payment activity page on a client device;

[0038] A role determination module, used to determine the role information of the target user based on the payment activity page information, wherein the role information is the inviter or the invitee;

[0039] A payment activity confirmation module, configured to query the payment activity status in the target task table based on the payment activity page information in response to determining that the role of the target user is an invited party, wherein the payment activity status is completed or incomplete;

[0040] a payment module, configured to send a payment window to the client device in response to the payment activity status being determined to be incomplete, so as to display the payment window on the client device;

[0041] An updating module, configured to update the target task table based on the payment information of the target user in response to determining that the target user has successfully paid through the payment window;

[0042] A target-reaching confirmation module, configured to obtain information of all users who have reached the target in the target task table in response to the current total payment amount corresponding to the target user group in the target task table being greater than a preset payment amount, wherein the target user group is used to store information of users who belong to the same cooperative payment group as the target user and have successfully paid;

[0043] The sending module is used to send payment compliance information to the client device of each qualified user according to the qualified user information, so as to display the payment compliance information on the payment activity page.

[0044] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0045] The memory stores computer-executable instructions;

[0046] The processor executes the computer-executable instructions stored in the memory to implement the method described in the first aspect.

[0047] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in the first aspect.

[0048] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which implements the method described in the first aspect when executed by a processor.

[0049] The data processing method, apparatus, device, storage medium and program product in cooperative payment provided by the present application obtain payment activity page information of a target user, where the target user is a user who triggers a payment activity page on a client device; determine the role information of the target user based on the payment activity page information, where the role information is an inviter or an invitee; in response to determining that the role of the target user is an invitee, query the payment activity status in a target task table based on the payment activity page information, where the payment activity status is completed or incomplete; in response to determining that the payment activity status is incomplete, send a payment window to the client device to display the payment window on the client device; in response to determining that the target user has successfully paid through the payment window, update the target task table based on the payment information of the target user; in response to the current total payment amount corresponding to the target user group in the target task table being greater than a preset payment amount, obtain all qualified user information in the target user group in the target task table, where the target user group is used to store user information that belongs to the same cooperative payment group as the target user and has successfully paid; send payment qualified information to the client device of each qualified user according to the qualified user information, so that the payment qualified information is displayed on the payment activity page. The data processing method in the cooperative payment will update the target task table based on the payment information of the invitee only after the invitee has successfully paid, so as to automatically identify the invitee as participating in the payment activity, so that the invitee does not need to confirm the activity participation. In this way, the payment experience of users in cooperative payment can be improved, and there is no need to record the confirmation status of the inviter and the invitee, which can effectively reduce the storage burden. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0051] Figure 1 An application scenario diagram of a data processing method in cooperative payment provided in an embodiment of the present application;

[0052] Figure 2 A flowchart of a data processing method in cooperative payment provided in an embodiment of the present application;

[0053] Figure 3 A flowchart of a data processing method in cooperative payment provided in another embodiment of the present application;

[0054] Figure 4 A schematic diagram of the structure of a data processing device in a cooperative payment provided in an embodiment of the present application;

[0055] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0056] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0057] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0058] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of information such as financial data or user data involved shall comply with the provisions of relevant laws and regulations and shall not violate public order and good morals.

[0059] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0060] In order to clearly understand the technical solution of the present application, the solution of the prior art is first introduced in detail. At present, with the rapid development of digital life, the living expenses payment platform has become an indispensable service tool in daily life. Residents can complete the payment of living expenses such as water bills, electricity bills, gas bills or heating bills without leaving home through the living expenses payment platform, which greatly improves the convenience and efficiency of residents' payment. Some existing living expenses payment platforms allow multiple users to make cooperative payments, thereby enhancing the enthusiasm of residents to pay. However, when multiple users cooperate to pay, the existing living expenses payment platform requires the invited users to manually confirm whether to participate in the cooperative payment. Although this step can help to protect the rights and interests of users, it invisibly prolongs the payment procedure, increases the complexity of user operations, and affects the user's payment experience; at the same time, the living expenses payment platform also needs to record the confirmation status of both the inviting user and the invited user, thereby increasing the storage burden of the living expenses payment platform.

[0061] In response to the above technical problems, the present application proposes a data processing method in cooperative payment, in order to improve the payment experience of users in cooperative payment and reduce the storage burden. First, the role of the target user is determined based on the payment activity page information of the target user. When the role of the target user is an invited party and the payment activity status is incomplete, the target user is allowed to pay through the payment window. After the payment is completed, the target task table is updated according to the payment information. When the current total payment amount corresponding to the target user group in the target task table is greater than the preset payment amount, the cooperative payment activity is completed. Therefore, the invited party does not need to confirm participation in the activity, and can automatically participate in the cooperative payment activity as long as the payment is completed, which can increase the payment experience of users in cooperative payment, and there is no need to record the confirmation status of the inviting party and the invited party, thereby reducing the storage burden.

[0062] Figure 1 An application scenario diagram corresponding to the data processing method in cooperative payment provided in an embodiment of the present application, such as Figure 1 As shown, in the application scenario provided by this embodiment, the target user triggers the payment activity page through the client device 11, and the client device 11 sends the payment activity page information to the payment terminal device 12. The payment terminal device 12 obtains the payment activity page information of the target user and determines the role information of the target user based on the payment activity page information. When the role of the target user is determined to be an invited party, the payment terminal device 11 sends a query request to the target database 13 based on the payment activity page information. The target database 13 queries the payment activity status in the target task table and sends the query result back to the payment terminal device 11. When it is determined that the payment activity status is incomplete, the payment terminal device 11 sends a payment window to the client device 12, and the client device 12 displays the payment window. The target user pays through the payment window. The target user pays through the payment window. When the target user successfully pays through the payment window, the client device 12 sends the payment information of the target user to the payment terminal device 11. The payment terminal device 11 receives and sends the payment information to the target database 13. The target database 13 updates the target task table based on the payment information. When the current total payment amount corresponding to the target user group in the target task table is greater than the preset payment amount, the target database 13 sends the information of all qualified users in the target user group in the target task table to the payment terminal device 11. The payment terminal device 11 sends the payment compliance information to the client device 12 of each qualified user according to the qualified user information. The payment activity page of the client device 12 displays the payment compliance information, so that the target user can know that the payment activity is completed according to the payment compliance information.

[0063] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0064] Figure 2 A flowchart of a data processing method in cooperative payment provided in an embodiment of the present application, such as Figure 2 As shown, the execution subject of this embodiment is the data processing device in the cooperative payment, which can be implemented by a computer program or by a medium storing relevant computer programs, such as a USB flash drive and / or a CD, etc.; or, it can also be implemented by a physical device integrated or installed with relevant computer programs, such as a chip, an electronic device, etc. The electronic device can be a computer or a server, etc. The data processing method in the cooperative payment provided in this embodiment includes the following steps:

[0065] S201. Obtain payment activity page information of a target user, where the target user is a user who triggers the payment activity page on a client device.

[0066] Specifically, when the target user opens or triggers the payment activity page on the client device, the payment terminal device obtains relevant information of the payment activity page, and the payment activity page information can be used for subsequent information extraction and processing.

[0067] Optionally, the payment activity page information includes but is not limited to user ID, payment activity ID, page access timestamp, activity page link, etc.

[0068] Optionally, the client device can be a computer, tablet or mobile phone.

[0069] S202: Determine the role information of the target user based on the payment activity page information, where the role information is the inviter or the invitee.

[0070] Specifically, after the payment activity page information is obtained, the role information of the current target user is determined to be the inviter or the invitee through the payment activity page information, so that different operation processes can be performed according to different role information of the target user.

[0071] Among them, the inviting party is the user who initiates the payment activity or invites others to participate in the payment activity, and the invited party is the user who is invited to participate in the payment activity.

[0072] Optionally, the payment activity page information includes but is not limited to user ID, payment activity ID, page access timestamp, and activity page link, etc. Therefore, the payment activity page information used to determine the role information of the target user is not specifically limited in this embodiment, as long as the role information of the target user can be determined.

[0073] Optionally, in other embodiments, the role information of the target user may also be determined based on the historical behavior or invitation code of the target user.

[0074] S203: In response to determining that the role of the target user is an invitee, query the payment activity status in the target task table based on the payment activity page information, and the payment activity status is completed or incomplete.

[0075] Specifically, when the role of the target user is determined to be the invited party, the payment activity status in the target task table is first queried through the payment activity page information to determine whether the payment activity status is completed or incomplete. Thus, it is convenient to execute different operation processes according to different payment activity statuses.

[0076] The target task table is used to store relevant information of the payment activity, including but not limited to the payment activity status, the list of participating users, and the target amount, etc., which are not specifically limited in this embodiment.

[0077] Optionally, the payment activity page information includes but is not limited to user ID, payment activity ID, page access timestamp, and activity page link, etc. Therefore, the payment activity status in the target task table can be determined in a variety of ways. In this embodiment, the method for determining the payment activity status is not limited.

[0078] S204: In response to the payment activity status being determined to be incomplete, a payment window is sent to the client device, so as to display the payment window on the client device.

[0079] Specifically, when it is determined that the payment activity status is incomplete, it indicates that the invited user can continue to participate in the payment activity, so a payment window is sent to the client device of the invited user to display the payment window on the client device, and the invited user can pay through the payment window.

[0080] Among them, the payment window is used to allow the user to enter payment information and complete payment.

[0081] Optionally, the payment window can allow the user to enter information such as user name and payment amount.

[0082] Optionally, the payment window is set to a highlight mode, or a payment countdown is set in the payment window, so as to remind the user to complete the payment as soon as possible.

[0083] S205: In response to determining that the target user has successfully paid through the payment window, update the target task table based on the payment information of the target user.

[0084] Specifically, when it is determined that the target user has completed payment through the payment window, the payment information of the target user is obtained and the target task table is updated based on the payment information. Thus, the progress of the payment activity can be updated in real time, ensuring that it is possible to accurately know whether the payment activity is completed.

[0085] Optionally, the payment information includes but is not limited to the payment amount, payment time, payment method, payment order number, payment user ID, etc.

[0086] Optionally, the content that needs to be updated in the target task table includes but is not limited to the user's payment record, payment amount, payment activity status, payment user ID, payment time, etc.

[0087] Optionally, there may be multiple ways to update the target task table, such as replacing existing data or directly adding data, etc., which is not limited in this embodiment.

[0088] Optionally, after the target task table is updated, the last modified timestamp is recorded so as to reflect the latest payment status changes.

[0089] Optionally, when the target user successfully pays through the payment window, a payment success information pop-up window is sent to the target user's payment activity page, so that the user can know whether he has successfully completed the payment through the information pop-up window.

[0090] S206. In response to the current total payment amount corresponding to the target user group in the target task table being greater than the preset payment amount, obtain information of all qualified users in the target user group in the target task table. The target user group is used to store information of users who belong to the same cooperative payment group as the target user and have successfully paid.

[0091] Specifically, when the current total payment amount corresponding to the target user group in the target task table is greater than the preset payment amount, it indicates that the current target user group has completed the payment activity, thereby obtaining all qualified user information in the target user group in the target task table to know which users have completed the payment activity task. This can facilitate notification of the qualified users.

[0092] It should be noted that the target user group, the current total payment amount and the preset payment amount are all stored in the target task table. The target user group is composed of users who belong to the same cooperative payment group and have successfully paid. The user information in the target user group can be user name, user abbreviation or user serial number, etc. The current total payment amount is the total payment amount of the target user group; the preset payment amount is the target amount of the payment activity, and the preset payment amount is pre-set by the activity party.

[0093] S207: Send payment compliance information to the client device of each qualified user according to the qualified user information, so as to display the payment compliance information on the payment activity page.

[0094] Specifically, after obtaining the information of the qualified user, the payment qualification information is sent to the client device of each qualified user according to the qualified user information, so that the payment qualification information is displayed on the payment activity page, so that the qualified user can know that he has completed the payment activity, so that the user can use it as a redemption voucher to exchange the activity or other operations with the activity party. By sending the payment qualification information to the qualified user in real time, the user's sense of achievement and participation can be increased, thereby enhancing the user's activity experience and improving the user's satisfaction.

[0095] Optionally, the meeting-the-target user information may include the meeting-the-target user ID, the meeting-the-target time, the meeting-the-target amount, etc.

[0096] Optionally, the payment achievement information may include a payment activity achievement notification, a achievement certificate or a redemption code, etc.

[0097] The data processing method in cooperative payment provided in this embodiment obtains payment activity page information of a target user, where the target user is a user who triggers a payment activity page on a client device; determines role information of the target user based on the payment activity page information, where the role information is an inviter or an invitee; in response to determining that the role of the target user is an invitee, inquiring about the payment activity status in a target task table based on the payment activity page information, where the payment activity status is completed or incomplete; in response to determining that the payment activity status is incomplete, sending a payment window to the client device to display the payment window on the client device; in response to determining that the target user has successfully paid through the payment window, updating the target task table based on the payment information of the target user; in response to the current total payment amount corresponding to the target user group in the target task table being greater than a preset payment amount, obtaining all qualified user information in the target user group in the target task table, where the target user group is used to store user information that belongs to the same cooperative payment group as the target user and has successfully paid; and sending payment qualified information to the client device of each qualified user according to the qualified user information, so that the payment qualified information is displayed on the payment activity page. The data processing method in the cooperative payment will update the target task table based on the payment information of the invitee only after the invitee has successfully paid, so as to automatically identify the invitee as participating in the payment activity, so that the invitee does not need to confirm the activity participation. In this way, the payment experience of users in cooperative payment can be improved, and there is no need to record the confirmation status of the inviter and the invitee, which can effectively reduce the storage burden.

[0098] Figure 3 A flowchart of a data processing method in cooperative payment provided in another embodiment of the present application is shown in FIG. Figure 3 As shown in , the data processing method in the cooperative payment provided in this embodiment, when determining the role information of the target user based on the payment activity page information, specifically includes the following steps:

[0099] S2021. Determine whether the page link of the payment activity page has a payment activity group identifier and a forwarding identifier.

[0100] S2022: If it is determined that the page link of the payment activity page has a payment activity group identifier and a forwarding identifier, then the role of the target user is determined to be an invitee.

[0101] S2023: If it is determined that the page link of the payment activity page does not contain a payment activity group identifier and a forwarding identifier, then the role of the target user is determined to be an inviter.

[0102] Specifically, when determining the role information of the target user based on the payment activity page information, first, determine whether the page link of the payment activity page contains the payment activity group identifier and the forwarding identifier; when the page link of the payment activity page contains the payment activity group identifier and the forwarding identifier, at this time, it is determined that the payment activity page is forwarded by others, and at this time the role of the target user is the invited party; when the page link of the payment activity page does not contain the payment activity group identifier and the forwarding identifier, at this time, it is determined that the user has accessed the payment activity page from the main activity interface, and at this time the role of the target user is the inviting party.

[0103] Among them, the payment activity group identifier is a unique identifier used to distinguish different activities and different cooperative payment groups. The payment activity information and cooperative payment group information can be determined through the payment activity group identifier; the forwarding identifier is a unique identifier with the information of the inviter. The information of the inviter can be determined through the forwarding identifier.

[0104] Optionally, the payment activity group identification can be in multiple forms, such as a combination of the payment activity sequence code and the cooperative payment group code, a combination of the payment activity sequence code and the cooperative payment group name, a combination of the payment activity name and the cooperative payment group name, or a combination of the payment activity sequence code and a timestamp, etc., which are not specifically limited here as long as they can be distinguished.

[0105] Optionally, the forwarding identifier may be in various forms, such as the name, ID, invitation code of the inviter, or a combination of a timestamp and the above name, ID and invitation code, etc., which are not specifically limited here as long as they can be distinguished.

[0106] Optionally, when the invited party forwards the payment activity to others, the payment activity group identifier and forwarding identifier carried in the page link of the payment activity page remain unchanged.

[0107] It should be noted that the position and format of the payment activity group identifier and forwarding identifier in the page links of different payment activity pages are unified.

[0108] The data processing method in cooperative payment provided by this embodiment determines the role information of the target user based on the payment activity page information, including: judging whether the page link of the payment activity page has the payment activity group identifier and the forwarding identifier; if it is determined that the page link of the payment activity page has the payment activity group identifier and the forwarding identifier, then the role of the target user is determined to be the invited party; if it is determined that the page link of the payment activity page does not have the payment activity group identifier and the forwarding identifier, then the role of the target user is determined to be the inviting party. The data processing method in cooperative payment of this embodiment, by checking the specific identifier in the page link of the payment activity page, has a simple judgment logic and is easy to implement, and can quickly and accurately determine whether the role of the target user is the invited party or the inviting party, thereby improving the user's activity experience.

[0109] Figure 3 A flowchart of a data processing method in cooperative payment provided in another embodiment of the present application is shown in FIG. Figure 3 As shown in, the data processing method in the cooperative payment provided in this embodiment also includes:

[0110] S2024: In response to determining that the role of the target user is an invitee, query whether there is a payment activity group identifier in the page link in the target task table.

[0111] S2025. If the payment activity group identifier does not exist in the target task table, add the payment activity group identifier and the forwarding identifier in the page link to the target task table, where the forwarding identifier is the user identifier of the inviting party.

[0112] Specifically, after determining that the role of the target user is the invited party, check whether there is a payment activity group identifier in the page link in the target task table; when the payment activity group identifier does not exist in the target task table, add the payment activity group identifier and the forwarding identifier in the page link to the target task table, where the forwarding identifier is the user identifier of the inviting party, thereby avoiding the situation where the corresponding payment activity group identifier does not exist in the target task table, resulting in the inability to record subsequent user and payment amount information, causing the user to participate in the activity ineffectively.

[0113] It should be noted that the method provided in this embodiment can be regarded as a safeguard measure, which can avoid the problem of failing to successfully record the payment activity group identifier and the user identifier of the inviter into the target task table due to system or equipment problems, thereby ensuring that users can effectively participate in payment activities.

[0114] It should also be noted that when adding the forwarding identifier to the target task table, a new target user group is first created, and then the user identifier of the inviting party is added to the newly created target user group.

[0115] The data processing method in cooperative payment provided by this embodiment also includes: in response to determining that the role of the target user is the invited party, querying whether there is a payment activity group identifier in the page link in the target task table; if the payment activity group identifier does not exist in the target task table, adding the payment activity group identifier in the page link and the forwarding identifier to the target task table, and the forwarding identifier is the user identifier of the inviting party. Thus, the problem that the corresponding payment activity group identifier does not exist in the target task table, resulting in the inability to record subsequent information such as users and payment amounts, can be avoided, and users can be guaranteed to effectively participate in payment activities.

[0116] Figure 3 A flowchart of a data processing method in cooperative payment provided in another embodiment of the present application is shown in FIG. Figure 3As shown in , the data processing method in the cooperative payment provided in this embodiment, after determining that the role of the target user is the inviting party, further includes:

[0117] S2026. Add the payment activity group identifier and the forwarding identifier to the page link of the corresponding payment activity page.

[0118] S2027: In response to determining that the target user has completed payment, add the payment activity group identifier in the page link and the user identifier of the target user to the target task table.

[0119] Specifically, when it is determined that the role of the target user is the inviter, the payment activity group identifier and the forwarding identifier are added to the page link of the corresponding payment activity page. Thus, when the inviter forwards the payment activity, the page link of the payment activity page forwarded by the inviter carries the payment activity group identifier and the forwarding identifier. Further, when the target user whose role is the inviter completes the payment, the payment activity group identifier in the page link and the user identifier of the target user are added to the target task table. Thus, the subsequent invited users can query the corresponding activities according to the payment activity group identifier in the target task table, which is convenient for the management and data statistics of the users participating in the payment activities.

[0120] Optionally, in this embodiment, the payment activity group identifier is a combination of a payment activity number and a timestamp.

[0121] Optionally, the forwarding identifier may be the name, ID, invitation code of the inviter, or a combination of a timestamp and the above name, ID and invitation code, etc., which is not specifically limited here as long as it can be distinguished.

[0122] The data processing method in cooperative payment provided by this embodiment, after determining that the role of the target user is the inviting party, further includes: adding the payment activity group identifier and the forwarding identifier to the page link of the corresponding payment activity page, and in response to determining that the target user has completed the payment, adding the payment activity group identifier in the page link and the user identifier of the target user to the target task table. With this arrangement, the inviting party can directly forward the payment activity page without performing other operations, which simplifies the invitation process and facilitates the management and data statistics of the users participating in the payment activity.

[0123] As an optional implementation mode, based on any one of the above embodiments, the payment information includes a payment activity group identifier, a user identifier and a payment amount, and the target task table includes a payment activity group identifier, a target user group and a current total payment amount; in response to the target user successfully paying through the payment window, updating the target task table based on the payment information of the target user, including: determining the target user group and the current total payment amount corresponding to the payment activity group identifier in the target task table based on the payment activity group identifier in the payment information; adding the user identifier in the payment information to the target user group; and updating the current total payment amount based on the payment amount in the payment information to obtain an updated current total payment amount.

[0124] Specifically, after the target user successfully pays through the payment window, when the target task table is updated based on the target user's payment information, the target user group corresponding to the payment activity group identifier in the target task table and the current total payment amount are determined through the payment activity group identifier in the payment information, and then the user identifier in the payment information is added to the target user group, and the current total payment amount is updated based on the payment amount in the payment information, so as to obtain the updated current total payment amount.

[0125] Optionally, there are multiple ways to store multiple user IDs in the target user group, such as placing all user IDs in the target user group in the same cell and separating them with special symbols, such as spaces, hyphens, percent signs, or vertical bars, or placing different user IDs in different cells in the same row or column. Accordingly, the way to add user IDs to the target user group also changes adaptively with the storage method of the target user group.

[0126] Optionally, when updating the current total payment amount, the payment amount in the payment information and the current total payment amount in the target task table are directly summed up and calculated.

[0127] The data processing method in the cooperative payment provided by this embodiment, the payment information includes the payment activity group identifier, the user identifier and the payment amount, the target task table includes the payment activity group identifier, the target user group and the current total payment amount; in response to the target user successfully paying through the payment window, the target task table is updated based on the payment information of the target user, including: determining the target user group and the current total payment amount corresponding to the payment activity group identifier in the target task table based on the payment activity group identifier in the payment information; adding the user identifier in the payment information to the target user group; updating the current total payment amount based on the payment amount in the payment information to obtain the updated current total payment amount. The method of this embodiment immediately updates the target task table when the payment is successful, which can ensure the real-time update of the target task table, ensure the user's payment activity experience, and add the user identifier in the payment information to the target user group, and update the current total payment amount based on the payment amount in the payment information, which can quickly and accurately update the target user group and the current total payment amount in the target task table, ensuring the management and update efficiency of the target task table.

[0128] As an optional implementation mode, based on any one of the above embodiments, payment compliance information is sent to the client device of each qualified user based on the qualified user information, so that the payment compliance information is displayed on the payment activity page, including: sending payment compliance information and corresponding qualified object information to the client device of each qualified user based on the qualified user information, so that the payment compliance information and qualified object information are displayed on the payment activity page.

[0129] Specifically, when the payment achievement information is sent to the client device of each user who has met the standard according to the information of the user who has met the standard, and the payment achievement information is displayed on the payment activity page, the payment achievement information and the corresponding achievement object information are sent to the client device of each user who has met the standard according to the information of the user who has met the standard, and the payment achievement information and the achievement object information are displayed on the payment activity page. Thus, it can remind the user that the payment has met the standard and inform the user of the achievement object information, and the user can use the payment achievement information and the achievement object information as vouchers to exchange with the activity party.

[0130] Optionally, the payment target achievement information may include the payment target achievement amount, the achievement time, and a thank you note for achieving the payment target, etc.

[0131] Optionally, the qualified user information may be an ID of the qualified user, or an ID of a client device of the qualified user.

[0132] Optionally, the object information obtained by meeting the requirements may be a requirement coupon, requirement points, requirement money, or items of equivalent value, etc., which are not specifically limited here.

[0133] The data processing method in cooperative payment provided in this embodiment sends payment achievement information to the client device of each meeting the standard according to the meeting user information, so as to display the payment achievement information on the payment activity page, including: sending payment achievement information and corresponding meeting object information to the client device of each meeting the standard according to the meeting user information, so as to display the payment achievement information and the meeting object information on the payment activity page; when the payment activity meets the standard, the payment achievement information and the meeting object information are displayed on the payment activity page of the meeting user, which can improve the user's sense of participation in the payment activity and the activity experience.

[0134] As an optional implementation manner, based on any of the above embodiments, before sending payment compliance information and corresponding compliance object information to the client device of each compliance user according to the compliance user information, the method further includes:

[0135] Obtain the payment activity group identifier corresponding to the target user group that completes the payment task in the target task table;

[0136] Based on the payment activity group identifier, the name of the target-reaching income object corresponding to the payment activity group identifier in the target-reaching income object table is determined.

[0137] Specifically, before sending payment achievement information and corresponding achievement object information to the client devices of each achievement user according to the achievement user information, first obtain the payment activity group identifier corresponding to the target user group that completes the payment task in the target task table, and determine the achievement object name corresponding to the payment activity group identifier in the achievement object table from the payment activity group identifier. Thus, the achievement object name corresponding to the payment activity group identifier can be accurately obtained.

[0138] The target-obtained object table is a table storing payment activity group identifiers and target-obtained object names, and each payment activity group identifier corresponds to a unique target-obtained object name.

[0139] The data processing method in cooperative payment provided by this embodiment, before sending payment compliance information and corresponding compliance object information to the client device of each compliance user according to the compliance user information, also includes: obtaining the payment activity group identifier corresponding to the target user group that completes the payment task in the target task table; determining the compliance object name corresponding to the payment activity group identifier in the compliance object table based on the payment activity group identifier. The method of this embodiment stores the compliance object name separately in the compliance object table, so that the compliance object name corresponding to the payment activity group identifier can be quickly queried through the payment activity group identifier, thereby improving the query efficiency and accuracy.

[0140] As an optional implementation manner, based on any of the above embodiments, it also includes:

[0141] In response to the payment activity status being determined to be completed, the current payment activity completion information and the payment activity selection window are sent to the client device to display the current payment activity completion information and the payment activity selection window on the client device. The payment activity selection window is used for the target user to start a new group of payment activities or leave the payment activity page.

[0142] Specifically, when the payment activity status is determined to be completed, the current payment activity completion information and the payment activity selection window are sent to the client device of the target user, so that the target user can know the payment activity status and conduct a new group of payment activities through the payment activity selection window, or leave the payment activity page. Therefore, it can play the role of instant reminder and provide the target user with multiple choices, which is convenient for the target user to start a new group of payment activities, maintain interest and participation in the payment activities, and improve the activity experience of the target user.

[0143] The data processing method in cooperative payment provided by this embodiment also includes: in response to the payment activity status being determined to be completed, sending the current payment activity completion information and the payment activity selection window to the client device, so as to display the current payment activity completion information and the payment activity selection window on the client device, and the payment activity selection window is used for the target user to start a new group of payment activities or leave the payment activity page. In the method of this embodiment, the user can obtain feedback on the payment activity status in real time, and choose whether to continue to participate in a new group of payment activities according to his own wishes, which improves the flexibility and autonomy of the user in participating in the payment activity, and can also improve the user's experience and satisfaction.

[0144] As an optional implementation, based on any of the above embodiments, the target user ID who has completed the payment and the current progress of the payment amount are displayed in real time on the payment activity page, so that the target user can know the current progress of the payment activity in real time based on the information on the payment activity page, which can enhance the user's enthusiasm for participating in the payment activity and improve the user's activity experience.

[0145] Figure 4 A data processing device for cooperative payment provided in an embodiment of the present application, such as Figure 4 As shown in , the data processing device in the cooperative payment provided in this embodiment is located in the electronic device. The data processing device in the cooperative payment provided in this embodiment includes: an acquisition module 31, a role determination module 32, a payment activity confirmation module 33, a payment module 34, an update module 35, a compliance confirmation module 36 and a sending module 37.

[0146] Specifically, the acquisition module 31 is used to obtain the payment activity page information of the target user, and the target user is the user who triggers the payment activity page on the client device; the role determination module 32 is used to determine the role information of the target user based on the payment activity page information, and the role information is the inviter or the invitee; the payment activity confirmation module 33 is used to query the payment activity status in the target task table based on the payment activity page information in response to determining that the role of the target user is the invitee, and the payment activity status is completed or incomplete; the payment module 34 is used to send a payment window to the client device in response to determining that the payment activity status is incomplete, so as to A payment window is displayed; an updating module 35 is used to update the target task table based on the payment information of the target user in response to determining that the target user has successfully paid through the payment window; a compliance confirmation module 36 is used to obtain all the qualified user information in the target user group in the target task table in response to the current total payment amount corresponding to the target user group in the target task table being greater than the preset payment amount, the target user group is used to store the user information that belongs to the same cooperative payment group as the target user and has successfully paid; a sending module 37 is used to send payment compliance information to the client device of each qualified user according to the qualified user information, so as to display the payment compliance information on the payment activity page.

[0147] Optionally, the role determination module 32, when determining the role information of the target user based on the payment activity page information, is specifically used to: determine whether the page link of the payment activity page contains a payment activity group identifier and a forwarding identifier; if it is determined that the page link of the payment activity page contains a payment activity group identifier and a forwarding identifier, determine that the role of the target user is an invited party; if it is determined that the page link of the payment activity page does not contain a payment activity group identifier and a forwarding identifier, determine that the role of the target user is an inviting party.

[0148] Optionally, the data processing device in the cooperative payment provided in this embodiment further includes an identification adding module.

[0149] Optionally, an identification adding module is used to, in response to determining that the role of the target user is an invited party, query whether the payment activity group identification in the page link exists in the target task table; if the payment activity group identification does not exist in the target task table, add the payment activity group identification in the page link and the forwarding identification to the target task table, and the forwarding identification is the user identification of the inviting party.

[0150] Optionally, the identification adding module is further used to add the payment activity group identification and the forwarding identification to the page link of the corresponding payment activity page.

[0151] Optionally, the identification adding module is further used to add the payment activity group identification in the page link and the user identification of the target user to the target task table in response to determining that the target user has completed payment.

[0152] Optionally, the payment information includes a payment activity group identifier, a user identifier and a payment amount, and the target task table includes a payment activity group identifier, a target user group and a current total payment amount; the update module 35, in response to the target user successfully paying through the payment window, updates the target task table based on the payment information of the target user, and is specifically used to: determine the target user group and the current total payment amount corresponding to the payment activity group identifier in the target task table based on the payment activity group identifier in the payment information; add the user identifier in the payment information to the target user group; and update the current total payment amount based on the payment amount in the payment information to obtain an updated current total payment amount.

[0153] Optionally, the sending module 37, when sending payment compliance information to the client device of each qualified user according to the qualified user information, so as to display the payment compliance information on the payment activity page, is specifically used for: sending the payment compliance information and corresponding information on the object obtained by meeting the requirements to the client device of each qualified user according to the qualified user information, so as to display the payment compliance information and the information on the object obtained by meeting the requirements on the payment activity page.

[0154] Optionally, before sending payment compliance information and corresponding compliance object information to the client device of each qualified user based on the qualified user information, the acquisition module 31 is also used to: obtain the payment activity group identifier corresponding to the target user group that completes the payment task in the target task table; and determine the compliance object name corresponding to the payment activity group identifier in the compliance object table based on the payment activity group identifier.

[0155] Optionally, the payment activity confirmation module 33 is also used to send the current payment activity completion information and the payment activity selection window to the client device in response to the payment activity status being determined to be completed, so as to display the current payment activity completion information and the payment activity selection window on the client device. The payment activity selection window is used for the target user to start a new group of payment activities or leave the payment activity page.

[0156] Figure 5 A schematic diagram of the structure of an electronic device is provided in an embodiment of the present application, such as Figure 5 As shown, the electronic device 40 provided in this embodiment includes: a processor 41 and a memory 42 communicatively connected to the processor.

[0157] The memory 42 stores computer-executable instructions; the processor 41 executes the computer-executable instructions stored in the memory 42 to implement the data processing method in the cooperative payment provided in any one of the above embodiments.

[0158] The program may include program codes, and the program codes include computer-executable instructions. The memory 42 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0159] In this embodiment, the memory 42 and the processor 41 are connected via a bus 43. The bus 43 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. The bus 43 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 Although only one straight line is used in the figure, it does not mean that there is only one bus or one type of bus 43.

[0160] An embodiment of the present application also provides a computer-readable storage medium, including computer-readable storage medium storing computer execution instructions, which, when executed by a processor, are used to implement the data processing method in cooperative payment provided in any one of the above embodiments.

[0161] An embodiment of the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the data processing method in cooperative payment provided in any one of the above embodiments.

[0162] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0163] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to implement the solution of this embodiment.

[0164] In addition, each functional module in each embodiment of the present application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The above-mentioned module-composed unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0165] The above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the methods of various embodiments of the present application.

[0166] It should be understood that the above processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the invention can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor.

[0167] The memory may include a high-speed RAM memory, and may also include a non-volatile storage NVM, such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, etc.

[0168] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of this application is not limited to only one bus or one type of bus.

[0169] The above storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0170] An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the storage medium can also exist as discrete components in an electronic control unit or a main control device.

[0171] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0172] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A data processing method in cooperative payment, characterized in that: include: Obtaining payment activity page information of a target user, where the target user is a user who triggers the payment activity page on a client device; Determine the role information of the target user based on the payment activity page information, the role information being the inviter or the invitee; In response to determining that the role of the target user is an invited party, querying the payment activity status in the target task table based on the payment activity page information, the payment activity status being completed or incomplete; In response to determining that the payment activity status is incomplete, sending a payment window to the client device to display the payment window on the client device; In response to determining that the target user has successfully paid through the payment window, updating the target task table based on the payment information of the target user; In response to the current total payment amount corresponding to the target user group in the target task table being greater than the preset payment amount, obtaining all qualified user information in the target user group in the target task table, wherein the target user group is used to store user information that belongs to the same cooperative payment group as the target user and has successfully paid; The payment compliance information is sent to the client device of each qualified user according to the qualified user information, so that the payment compliance information is displayed on the payment activity page.

2. The method according to claim 1, characterized in that The determining the role information of the target user based on the payment activity page information includes: Determine whether the page link of the payment activity page has a payment activity group identifier and a forwarding identifier; If it is determined that the page link of the payment activity page has a payment activity group identifier and a forwarding identifier, then the role of the target user is determined to be an invitee; If it is determined that there is no payment activity group identifier and forwarding identifier in the page link of the payment activity page, then the role of the target user is determined to be the inviter.

3. The method according to claim 2, characterized in that Also includes: In response to determining that the role of the target user is an invitee, querying the target task table to see whether there is a payment activity group identifier in the page link; If the payment activity group identifier does not exist in the target task table, the payment activity group identifier and the forwarding identifier in the page link are added to the target task table, where the forwarding identifier is the user identifier of the inviting party.

4. The method according to claim 2, characterized in that: After determining that the role of the target user is the inviting party, the method further includes: Add the payment activity group identifier and the forwarding identifier to the corresponding page link of the payment activity page.

5. The method according to claim 4, characterized in that Also includes: In response to determining that the target user has completed payment, the payment activity group identifier in the page link and the user identifier of the target user are added to the target task table.

6. The method according to claim 1, characterized in that The payment information includes a payment activity group identifier, a user identifier, and a payment amount, and the target task table includes a payment activity group identifier, a target user group, and a current total payment amount; In response to the target user successfully paying through the payment window, updating the target task table based on the payment information of the target user includes: Determine the target user group and the current total payment amount corresponding to the payment activity group identifier in the target task table based on the payment activity group identifier in the payment information; Adding the user identification in the payment information to the target user group; The current total payment amount is updated based on the payment amount in the payment information to obtain an updated current total payment amount.

7. The method according to claim 1, characterized in that Sending payment compliance information to the client device of each qualified user according to the qualified user information, so as to display the payment compliance information on the payment activity page, including: The payment achievement information and the corresponding achievement object information are sent to the client device of each meeting user according to the achievement user information, so that the payment achievement information and the achievement object information are displayed on the payment activity page.

8. The method according to claim 7, characterized in that Before sending the payment compliance information and the corresponding compliance object information to the client device of each compliance user according to the compliance user information, the method further includes: Obtain the payment activity group identifier corresponding to the target user group that completes the payment task in the target task table; The name of the target-reaching income object corresponding to the payment activity group identifier in the target-reaching income object table is determined based on the payment activity group identifier.

9. The method according to any one of claims 1 to 8, characterized in that: Also includes: In response to the payment activity status being determined to be completed, the current payment activity completion information and the payment activity selection window are sent to the client device to display the current payment activity completion information and the payment activity selection window on the client device. The payment activity selection window is used for the target user to start a new group of payment activities or leave the payment activity page.

10. A data processing device in cooperative payment, characterized in that: include: An acquisition module, used to acquire payment activity page information of a target user, where the target user is a user who triggers the payment activity page on a client device; A role determination module, used to determine the role information of the target user based on the payment activity page information, wherein the role information is the inviter or the invitee; A payment activity confirmation module, configured to query the payment activity status in the target task table based on the payment activity page information in response to determining that the role of the target user is an invited party, wherein the payment activity status is completed or incomplete; a payment module, configured to send a payment window to the client device in response to the payment activity status being determined to be incomplete, so as to display the payment window on the client device; An updating module, configured to update the target task table based on the payment information of the target user in response to determining that the target user has successfully paid through the payment window; A target-reaching confirmation module, configured to obtain information of all users who have reached the target in the target task table in response to the current total payment amount corresponding to the target user group in the target task table being greater than a preset payment amount, wherein the target user group is used to store information of users who belong to the same cooperative payment group as the target user and have successfully paid; The sending module is used to send payment compliance information to the client device of each qualified user according to the qualified user information, so as to display the payment compliance information on the payment activity page.

11. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 9 when executed by a processor.

13. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 9 when being executed by a processor.

Images