Order processing method and device, equipment, medium and program product

By providing order processing methods in the banking system, the problem of difficult users' point transactions in different scenarios is solved, and the detailed viewing of points transaction orders between multiple scenarios is realized, ensuring the security of interactive communication and user experience.

CN119624539AActive Publication Date: 2025-03-14CHINA CONSTRUCTION BANK +1
View PDF 9 Cites 0 Cited by

Patent Information

Application Number
CN202411672694.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-21
Publication Date
2025-03-14
Estimated Expiration
2044-11-21

AI Technical Summary

Technical Problem

In the banking system scenario, it is difficult for users to track the source of the transaction when they conduct points transactions on different scenarios, resulting in user complaints.

Method used

An order processing method is provided, by receiving a point order traceability request from the first scene party, authenticating and processing the order link, so that the user can jump from the point transaction flow view of the first scene party to the order details interface of the second scene party.

Benefits of technology

It realizes the viewing of the details of points transaction orders between parties in multiple scenarios, supports users to trace transactions, ensures the security of interactive communication, and improves user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119624539A_ABST
    Figure CN119624539A_ABST
Patent Text Reader

Abstract

The invention provides an order processing method and device, equipment, a medium and a program product, which can be applied to the technical field of data interaction. The method comprises the following steps: in response to an integral order traceability request received from a first scene party, authenticating the first scene party according to a scene party identifier and a key corresponding to the first scene party in the integral order traceability request to obtain a first authentication result, the point order traceability request represents and checks order details of point transaction performed by the user in the second scene party; and processing an order link corresponding to the second scene party in the integral order tracing request under the condition that the first authentication result represents that the authentication is passed and the first scene party has the order permission of querying the second scene party, so that an integral transaction flow view of the first scene party jumps to an order detail interface of the second scene party. And checking order details of point transaction of the user in the second scene party.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of data interaction technology, and in particular to an order processing method, device, equipment, medium and program product. Background Art

[0002] In the banking system scenario, the user's consumption behavior, deposit behavior, marketing activity rewards and other behaviors in the scenario can all accumulate points for the user's point account. Similarly, the bank's multiple systems also provide different ways to use points, such as point redemption, point cash, point exchange, etc. However, since each scenario party conducts point activities separately, it is difficult for users to track the source of transactions when they query the point flow, which is easy to cause user complaints. Summary of the invention

[0003] In view of the above problems, the present disclosure provides an order processing method, apparatus, device, medium and program product.

[0004] According to a first aspect of the present disclosure, there is provided an order processing method, comprising:

[0005] In response to receiving a points order tracing request from a first scenario party, authenticating the first scenario party according to a scenario party identifier and a key corresponding to the first scenario party in the points order tracing request, and obtaining a first authentication result, wherein the points order tracing request represents viewing order details of a points transaction conducted by a user on a second scenario party, and the first scenario party and the second scenario party are different scenario parties in a scenario party terminal; and

[0006] When the first authentication result indicates that the authentication is passed and the first scenario party has the order authority to query the second scenario party, the order link corresponding to the second scenario party in the points order tracing request is processed, so that the points transaction flow view of the first scenario party is jumped to the order details interface of the second scenario party to view the order details of the user's points transaction on the second scenario party.

[0007] According to a second aspect of the present disclosure, there is provided an order processing method, comprising:

[0008] In response to the user's point order tracing operation on the first scenario party, a point order tracing request is sent to the point system terminal, wherein the point order tracing request represents viewing the order details of the point transaction conducted by the user on the second scenario party, and the first scenario party and the second scenario party are different scenario parties in the scenario party terminal; and

[0009] After the points system terminal processes the order link corresponding to the second scenario party, it jumps from the points transaction flow view of the first scenario party to the order details interface of the second scenario party to view the order details of the points transaction conducted by the user in the second scenario;

[0010] Among them, when the first authentication result indicates that the authentication is passed and the above-mentioned first scenario party has the order authority to query the above-mentioned second scenario party, the above-mentioned points system terminal processes the order link corresponding to the above-mentioned second scenario party in the above-mentioned points order tracing request; the above-mentioned first authentication result is obtained by the above-mentioned points system terminal through authentication of the above-mentioned first scenario party based on the scene party identifier and key corresponding to the above-mentioned first scenario party in the above-mentioned points order tracing request.

[0011] A third aspect of the present disclosure provides an order processing device, including: a first authentication module and a first processing module.

[0012] Among them, the first authentication module is used to respond to receiving a points order tracing request from the first scenario party, authenticate the first scenario party according to the scenario party identifier and key corresponding to the first scenario party in the points order tracing request, and obtain a first authentication result, wherein the points order tracing request represents viewing the order details of the user's points transaction on the second scenario party, and the first scenario party and the second scenario party are different scenario parties in the scenario party terminal; and

[0013] The first processing module is used to process the order link corresponding to the second scenario party in the above-mentioned point order tracing request when the above-mentioned first authentication result indicates that the authentication is passed and the above-mentioned first scenario party has the order authority to query the above-mentioned second scenario party, so as to jump from the point transaction flow view of the above-mentioned first scenario party to the order details interface of the above-mentioned second scenario party to view the order details of the above-mentioned user's point transaction on the above-mentioned second scenario party.

[0014] A fourth aspect of the present disclosure provides an order processing device, including: a first sending module and a jump module.

[0015] The first sending module is used to send a points order tracing request to the points system terminal in response to the user's points order tracing operation on the first scenario party, wherein the points order tracing request represents viewing the order details of the points transaction conducted by the user on the second scenario party, and the first scenario party and the second scenario party are different scenario parties in the scenario party terminal; and

[0016] A jump module, for jumping from the point transaction flow view of the first scenario party to the order details interface of the second scenario party after processing the order link corresponding to the second scenario party at the point system terminal, so as to view the order details of the point transaction conducted by the user in the second scenario;

[0017] Among them, when the first authentication result indicates that the authentication is passed and the above-mentioned first scenario party has the order authority to query the above-mentioned second scenario party, the above-mentioned points system terminal processes the order link corresponding to the above-mentioned second scenario party in the above-mentioned points order tracing request; the above-mentioned first authentication result is obtained by the above-mentioned points system terminal through authentication of the above-mentioned first scenario party based on the scene party identifier and key corresponding to the above-mentioned first scenario party in the above-mentioned points order tracing request.

[0018] A fifth aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the above method.

[0019] The sixth aspect of the present disclosure further provides a computer-readable storage medium having a computer program or instructions stored thereon, which implements the steps of the above method when the above computer program or instructions are executed by a processor.

[0020] The seventh aspect of the present disclosure further provides a computer program product, including a computer program or instructions, which implement the steps of the above method when the above computer program or instructions are executed by a processor.

[0021] According to the order processing method, device, equipment, medium and program product provided by the present invention, since the points system terminal provides a unified cross-platform order query and authentication interface, there is no need for docking and interaction between the various scene parties, and it can support the viewing of points transaction order details between multiple scene parties, and support users to trace transactions, so that the order details of the user's points transaction on the second scene party can be viewed on the first scene party. In addition, when the points system terminal receives a points order tracing request, the points system terminal first authenticates the first scene party and determines whether the first scene party has the order authority to query the second scene party, so as to ensure the security of interactive communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The above contents and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0023] Figure 1 The application scenario diagram of the order processing method according to the embodiment of the present disclosure is schematically shown;

[0024] Figure 2A flowchart of an order processing method according to an embodiment of the present disclosure is schematically shown;

[0025] Figure 3 A schematic diagram of the jump relationship of the points order traceability according to an embodiment of the present disclosure is schematically shown;

[0026] Figure 4 A flowchart schematically shows a process of processing a point request when the point request is a point accumulation request according to an embodiment of the present disclosure;

[0027] Figure 5 A flowchart schematically shows a process of processing a point request when the point request is a point consumption request according to an embodiment of the present disclosure;

[0028] Figure 6 A flowchart for processing a points request when the points request is a points consumption refund request according to an embodiment of the present disclosure is schematically shown;

[0029] Figure 7 A schematic diagram of a user's points transaction flow view according to an embodiment of the present disclosure is shown;

[0030] Figure 8 The schematic diagram shows a point transaction flow view of a party in the first scenario according to an embodiment of the present disclosure;

[0031] Fig. 9 A flowchart of an order processing method according to another embodiment of the present disclosure is schematically shown;

[0032] Fig.10 The structure block diagram of the order processing device applied to the points system terminal according to the embodiment of the present disclosure is schematically shown;

[0033] Fig.11 A structural block diagram schematically shows an order processing device applied to a scenario party terminal according to an embodiment of the present disclosure; and

[0034] Fig.12 A block diagram of an electronic device suitable for implementing an order processing method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0035] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0036] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0037] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0038] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0039] 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.

[0040] In the technical solution of the present disclosure, the user information (including but not limited to user personal information, user image information, user device information, such as location information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0041] In the scenario of using personal information for automated decision-making, the methods, devices, and systems provided by the embodiments of the present disclosure provide users with corresponding operation portals for users to choose to agree or reject the automated decision-making results; if the user chooses to reject, the expert decision-making process will be entered. The expression "automated decision-making" here refers to the activity of automatically analyzing and evaluating a person's behavioral habits, interests and hobbies, or economic, health, credit status, etc. through computer programs, and making decisions. The expression "expert decision-making" here refers to the activity of making decisions by people who specialize in a certain field, have specialized experience, knowledge and skills, and have reached a certain level of professionalism.

[0042] Figure 1 The application scenario diagram of the order processing method according to the embodiment of the present disclosure is schematically shown.

[0043] like Figure 1 As shown, the application scenario 100 according to this embodiment may include a scenario party terminal 110 and a points system terminal 120. The scenario party terminal 110 includes multiple scenario parties, including but not limited to scenario party A, scenario party B, and scenario party C. The network may be used to provide a medium for a communication link between the scenario party terminal 110 and the points system terminal 120. The network may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0044] The user can use the scene party in the scene party terminal 110 to interact with the points system terminal 120 through the network to receive or send messages, etc. Various communication client applications can be installed on each scene party in the scene party terminal 110, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only for example).

[0045] Each scene party in the scene party terminal 110 can be a variety of electronic devices with a display screen and supporting web browsing, including but not limited to a smart phone, a tablet computer, a laptop computer, a desktop computer, and the like.

[0046] The points system terminal 120 may be a server that provides various services. The points system terminal 120 may analyze and process the received user request and other data, and feed back the processing results (such as web pages, information, or data obtained or generated according to the user request) to the scene party in the scene party terminal 110.

[0047] For example, in response to receiving a points order tracing request from a first scenario party, the points system terminal 120 can authenticate the first scenario party according to the scenario party identifier and key corresponding to the first scenario party in the points order tracing request to obtain a first authentication result. When the first authentication result indicates that the authentication is successful and the first scenario party has the authority to query the order of the second scenario party, the order link corresponding to the second scenario party in the points order tracing request is processed, so as to jump from the points transaction flow view of the first scenario party to the order details interface of the second scenario party to view the order details of the user's points transaction on the second scenario party.

[0048] It should be noted that the order processing method provided in the embodiment of the present disclosure can generally be executed by the points system terminal 120. Accordingly, the order processing device provided in the embodiment of the present disclosure can generally be set in the points system terminal 120. The order processing method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the points system terminal 120 and can communicate with each scene party in the scene party terminal 120 and / or the points system terminal 120. Accordingly, the order processing device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the points system terminal 120 and can communicate with each scene party in the scene party terminal 120.

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

[0050] The following will be based on Figure 1 The scene described by Figure 2~Figure 9 The order processing method of the embodiment of the present disclosure is described in detail.

[0051] Figure 2 The flowchart of the order processing method according to the embodiment of the present disclosure is schematically shown.

[0052] like Figure 2 As shown, the method 200 includes operations S210 to S220.

[0053] In operation S210, in response to receiving a points order tracing request from a first scenario party, the first scenario party is authenticated according to a scenario party identifier and a key corresponding to the first scenario party in the points order tracing request to obtain a first authentication result.

[0054] Among them, the points order tracing request represents viewing the order details of the user's points transaction with the second scene party. The first scene party and the second scene party are different scene parties in the scene party terminal. The scene party terminal includes multiple scene parties, that is, the first scene party and the second scene party can be any two different scene parties in the scene party terminal.

[0055] According to an embodiment of the present disclosure, when a user views the points details in a first scenario party, the first scenario party can display a points transaction flow view, which can display the user's current points balance, points transactions conducted by the user in different scenario parties, and other points details.

[0056] For example, when the first scene party is scene party A, the point transaction flow view of scene party A can also display the point transactions conducted by users in scene party B.

[0057] According to an embodiment of the present disclosure, in order to view the order details of the user's point transaction on the second scenario party in the interface of the first scenario party, the user can perform a point order tracing operation on the point transaction on the second scenario party in the point transaction flow view of the first scenario party. For example, the user can click on the point details portion corresponding to the second scenario party in the point transaction flow view, so that the first scenario party can send a point order tracing request to the point system terminal.

[0058] Among them, the points order tracing request may include the scene party identifier and key corresponding to the first scene party.

[0059] According to the embodiments of the present disclosure, each scene party in the scene party terminal can be used to create a points transaction activity, such as the scene party can establish points exchange for goods, points cash payment, consumption accumulation points and other points transaction activities, so that users can conduct points transactions in the scene party, that is, the scene party can handle user interaction, that is, the user's operation behavior is carried out in the scene party, such as point order tracing, etc. The scene party can also provide users with a clear and visible point transaction flow view.

[0060] According to an embodiment of the present disclosure, in response to a received points order tracing request, the points system terminal authenticates the first scene party according to a scene party identifier and a key corresponding to the first scene party to obtain a first authentication result.

[0061] For example, the points system terminal will store keys corresponding to multiple scene parties. When the points system terminal receives a points order tracing request, the key corresponding to the scene party identifier corresponding to the first scene party in the points order tracing request is queried to obtain the key stored in the points system terminal, and the key stored in the points system terminal is compared with the key in the points order tracing request. If they are consistent, the first authentication result can indicate that the authentication is successful; if they are inconsistent, the first authentication result indicates that the authentication is unsuccessful.

[0062] According to an embodiment of the present disclosure, the first scene party is authenticated based on the scene party identifier and key in the points order tracing request in order to perform security verification to ensure the security of interactive communication.

[0063] In operation S220, when the first authentication result indicates that the authentication is passed and the first scenario party has the order authority to query the second scenario party, the order link corresponding to the second scenario party in the points order tracing request is processed, so that the points transaction flow view of the first scenario party jumps to the order details interface of the second scenario party to view the order details of the user's points transaction on the second scenario party.

[0064] According to an embodiment of the present disclosure, when the first authentication result indicates that the authentication is passed, it is also necessary to determine whether the first scenario party has the order authority to query the second scenario party. If the first scenario party does not have the order authority to query the second scenario party, the points system terminal will not process the order link corresponding to the second scenario party; if the first scenario party has the order authority to query the second scenario party, the points system terminal will process the order link corresponding to the second scenario party.

[0065] Among them, the points system terminal can configure the query permissions between each scene party in advance, that is, whether there is order permission to query order details between each scene. For example, scene party A has the order permission to query scene party B, that is, scene party A can view the order of scene party C.

[0066] According to an embodiment of the present disclosure, the points system terminal processes the order link corresponding to the second scenario party, so that the interface of the first scenario party jumps from the points transaction flow view to the order details interface of the second scenario party. The user can view the order details of the user's points transaction on the second scenario party on the interface of the first scenario party.

[0067] Figure 3 The jump relationship diagram of the point order traceability according to the embodiment of the present disclosure is schematically shown.

[0068] like Figure 3 As shown, the first scene party is scene party A, and the second scene party is scene party C.

[0069] According to an embodiment of the present disclosure, when a user wants to query the points details, the first scene party can display the points details of the user, that is, the points transaction flow view 310. The points transaction flow view 310 of the first scene party displays the current points balance of the user as 150 points, and also displays the points details of the user's points transactions in scene parties A, B, and C.

[0070] For example, for the points details of a points transaction conducted on scene party C, scene party C is the scene party identifier, points consumption is the points transaction type, -50 points is the points consumption value, xx / xx / xx is the time of points consumption, and the order details URL (Uniform Resource Locator, web address or URL) is the scene party order details link.

[0071] According to an embodiment of the present disclosure, the user performs a point order tracing operation on the point transaction of the second scene party, that is, the user can click on the point details corresponding to the scene party C in the point transaction flow view, that is, click on Figure 3 The point details of scenario party C are shown in , and scenario party A can send a point order tracing request to the point system terminal 120.

[0072] According to an embodiment of the present disclosure, the points system terminal 120 provides an authentication interface, that is, the points system terminal 120 authenticates the scene party A and determines whether the scene party A has the order authority to view the scene party C. If the authentication is passed, the points system terminal 120 can process the order link corresponding to the scene party C, so that the interface of the scene party A jumps from the points transaction flow view 310 to the order details interface of the scene party C.

[0073] According to the embodiments of the present disclosure, since the points system terminal provides a unified cross-platform order query and authentication interface, the various scene parties do not need to connect and interact with each other, and can support the viewing of points transaction order details between multiple scene parties, and support users to trace transactions, so that the order details of the user's points transaction on the second scene party can be viewed on the first scene party. In addition, when the points system terminal receives a points order tracing request, the points system terminal first authenticates the first scene party and determines whether the first scene party has the order authority to query the second scene party, so as to ensure the security of interactive communication.

[0074] According to an embodiment of the present disclosure, the above-mentioned order processing method also includes: allocating respective scene party identifiers, points rule identifiers and keys to at least one scene party connected to the points system terminal, wherein the scene party terminal includes multiple scene parties.

[0075] According to an embodiment of the present disclosure, the points system terminal can allocate respective scene party identifiers and keys to the scene parties connected to the points system terminal, and open a network access relationship between the scene parties and the points system terminal.

[0076] For example, the points system terminal can assign respective keys to the connected scene parties based on asymmetric encryption algorithms, etc.; the points system terminal can assign respective scene party IDs, that is, scene party identifications, to the connected scene parties based on the UUID (Universally Unique Identifier) ​​ID generation method.

[0077] According to the embodiment of the present disclosure, the points system terminal can configure the points rule for the corresponding scene party according to the scene party identifier, and generate a unique rule ID for each points rule, that is, the points rule identifier.

[0078] Among them, for a certain scenario party, at least one rule regarding point accumulation and at least one rule regarding point consumption can be configured for the scenario party, and corresponding point rule identifiers can be generated for each rule respectively.

[0079] For example, the points rule for point accumulation may be that the total amount of points consumed cannot exceed 1,000, a single point consumption cannot exceed 100, and so on.

[0080] According to the embodiment of the present disclosure, for scene party A and scene party B, the points system terminal can generate a points rule identifier, rule A1, for the rules related to points accumulation in scene party A, and generate rule A2 for the rules related to points consumption; and can generate rule B1 for the rules related to points accumulation in scene party B, and generate rule B2 for the rules related to points consumption.

[0081] For example, the rule corresponding to rule A1 may be that the accumulated points for a single transaction cannot exceed 50, and the rule corresponding to rule B1 may be that the accumulated points for a single transaction cannot be less than 50, that is, the points rules of each scenario party may be mutually exclusive; the rule corresponding to rule A1 may be that the total accumulated points cannot exceed 1000, and the rule corresponding to rule B1 may be that the total accumulated points cannot exceed 1000, that is, the points rules of each scenario party may also take effect at the same time.

[0082] According to an embodiment of the present disclosure, the points system terminal will also store the keys corresponding to each scene party identifier and the points rules corresponding to the points rule identifier, so that the subsequent points system terminal can query the corresponding keys based on the scene party identifier in the request and query the corresponding points rules based on the points rule identifier in the request.

[0083] According to an embodiment of the present disclosure, the points system terminal allocates the corresponding scene party identifiers, points rule identifiers and keys to the connected scene parties in advance, which serve as the basis for subsequent scene party authentication and interactive communication security, and as the basis for the points system terminal to authenticate and query the scene party, thereby ensuring the interactive communication security between the scene party and the points system terminal.

[0084] According to an embodiment of the present disclosure, the above-mentioned order processing method also includes: in response to receiving a points request from the scene party, authenticating the scene party according to the scene party identifier and key in the points request to obtain a second authentication result; when the second authentication result indicates that the authentication is passed, processing the points request to send the user's current points balance to the scene party.

[0085] According to an embodiment of the present disclosure, a user can perform a point transaction in any of the scene party terminals. When a user performs a point transaction in a scene party, the scene party will send a corresponding point request to the point system terminal. The types of point transactions may include point accumulation, point consumption, and point consumption refund.

[0086] According to an embodiment of the present disclosure, when the points system terminal receives the points request, it will first authenticate the scene party according to the scene party identifier and key in the points request, and obtain a second authentication result to ensure the security of the interactive communication.

[0087] According to an embodiment of the present disclosure, when the second authentication result indicates that the authentication fails, the points system terminal will not process the points request; when the second authentication result indicates that the authentication passes, the points system terminal processes the points request, that is, accumulates, consumes or refunds the current points balance of the user recorded in the points system terminal to obtain the new current points balance of the user.

[0088] According to an embodiment of the present disclosure, the points system terminal may also send the user's current points balance to the scene party, so that the user's current points balance may be displayed on the scene party to indicate that the points request is successful.

[0089] According to an embodiment of the present disclosure, before the points system terminal processes the points request, it can also determine whether the user is a new user based on the user ID in the points request. If the points account corresponding to the user ID can be queried in the points system terminal, it can be proved that the user is not a new user; if the points account corresponding to the user ID cannot be queried in the points system terminal, it can be proved that the user is a new user and a new points account needs to be opened for the user. Among them, the user's points account can record the flow of each point transaction of the user.

[0090] Among them, the principle for each scene party to access the points system terminal is that the user ID is unique, that is, the user information exists in different scene parties, but in the points system terminal, each user has only one user ID, and the user ID of each user will be stored in the points system terminal, such as user A, user B, etc.

[0091] According to an embodiment of the present disclosure, when a user conducts a points transaction in the scene party, the scene party will send a points request to the points system terminal, and the points system terminal will first authenticate the scene party to ensure the security of interactive communication, and process the points request when the authentication is passed, that is, accumulate, consume or refund the user's current points balance, etc., to achieve an update of the points transaction flow in the points account, and at the same time send the user's current points balance to the scene party, so as to intuitively display the user's current points balance on the scene party, and prompt the scene party that the points request is successful.

[0092] Figure 4 The flowchart of processing a point request when the point request is a point accumulation request according to an embodiment of the present disclosure is schematically shown.

[0093] like Figure 4 As shown, the method 400 includes operations S410 to S430.

[0094] In operation S410, the point accumulation request is verified according to the scenario party identifier and the point rule identifier in the point accumulation request to obtain a first verification result.

[0095] According to an embodiment of the present disclosure, when the points request is a points accumulation request, the points system terminal verifies the points accumulation request according to the scenario party identifier and the points rule identifier in the points accumulation request to obtain a first verification result.

[0096] According to an embodiment of the present disclosure, the points system terminal can query other points rules related to the scene party based on the scene party identifier in the points request. For example, when the points request is a points accumulation request, other points accumulation rules related to the scene party can be queried, and based on the points rule identifier in the points request, the points rule corresponding to the points rule identifier can be queried, and the points request can be verified based on these points rules.

[0097] According to the embodiments of the present disclosure, when verifying a points request, the points system terminal can configure the corresponding points transaction to satisfy the corresponding points rules at the same time, or can configure the corresponding points transaction to satisfy only one of the corresponding points rules. That is, the points system terminal can configure the points rules that the points transaction needs to satisfy as needed.

[0098] For example, the points system terminal queries and obtains other points accumulation rule A related to the scene party based on the scene party identifier in the points accumulation request, and queries and obtains points rule B based on the points rule identifier in the points accumulation request. When the points accumulation transaction needs to satisfy both points accumulation rule A and points rule B to be verified, such as points accumulation rule A that a single points accumulation shall not exceed 100 points, and points rule B that the total points accumulation of the user shall not exceed 1,000 points, and the user's points transaction needs to accumulate 50 points and the user's total points accumulation is 980 points, the verification of the user's points request fails.

[0099] In operation S420, when the first verification result indicates that the verification is passed, a point accumulation operation corresponding to the point accumulation request is performed according to the point value to be accumulated in the point accumulation request to obtain the current point balance of the user.

[0100] According to an embodiment of the present disclosure, when the first verification result indicates that the verification has failed, the points system terminal prompts the scenario party that the points accumulation has failed.

[0101] According to an embodiment of the present disclosure, when the first verification result indicates that the verification is passed, the points system terminal can perform a points accumulation operation corresponding to the points accumulation request according to the points value to be accumulated in the points accumulation request to obtain the user's new current points balance. The points value to be accumulated indicates the points value required to be accumulated by the user for points activities such as deposits.

[0102] For example, when the value of points to be accumulated in the points accumulation request is 20 points and the user's current points balance is 100 points, the points system terminal executes the points accumulation operation corresponding to the points accumulation request, that is, the value of points to be accumulated is added to the user's current points balance, that is, the user's new current points balance is 120 points.

[0103] In operation S430, the points accumulation flow corresponding to the points accumulation request is recorded under the points account corresponding to the user identifier in the points accumulation request, and the current points balance of the user is sent to the scenario party.

[0104] Among them, the points accumulation flow includes the user's current points balance.

[0105] According to an embodiment of the present disclosure, the points system terminal can also record the points accumulation flow corresponding to the points accumulation request under the points account corresponding to the user ID. The points accumulation flow can also include the reason for the points generation, the points expiration time, and the link to introduce the points acquisition scenario.

[0106] According to an embodiment of the present disclosure, the points system terminal may also send the user's new current points balance to the scene party to prompt the scene party that the points accumulation request is successful, and display the user's current points balance in the scene party.

[0107] According to an embodiment of the present disclosure, when the points system terminal processes the points accumulation request, it will first verify the points accumulation request according to the scene party identifier and the points rule identifier to restrict the points accumulation transaction between the scene party and the user to avoid malicious points acquisition, and if the verification is passed, execute the points accumulation operation to realize the points accumulation of the user, and record the points accumulation flow corresponding to the points accumulation request under the corresponding points account, so as to subsequently query and obtain the user's points details from the points account.

[0108] Figure 5 The flowchart of processing a point request when the point request is a point consumption request according to an embodiment of the present disclosure is schematically shown.

[0109] like Figure 5 As shown, the method 500 includes operations S510 to S540.

[0110] In operation S510, the point consumption request is verified according to the scenario party identifier and the point rule identifier in the point consumption request to obtain a second verification result.

[0111] According to an embodiment of the present disclosure, when the points request is a points consumption request, the points system terminal first verifies the points consumption request according to the scenario party identifier and the points rule identifier in the points consumption request to obtain a second verification result.

[0112] For example, the points system terminal queries and obtains other point consumption rules A related to the scene party based on the scene party identifier in the point consumption request, and queries and obtains point rule B based on the point rule identifier in the point consumption request. When the point consumption transaction needs to meet both point consumption rules A and point rule B to be verified, such as point consumption rule A that a single point consumption shall not exceed 50 points, and point rule B that the total amount of user points consumption shall not exceed 500 points, and when the user's point transaction requires 50 points and the user's total point consumption is 480 points, the verification of the user's point request will fail.

[0113] In operation S520, when the second verification result indicates that the verification is passed, the point value to be consumed in the point consumption request is compared with the valid point value of the user to obtain a comparison result.

[0114] The effective points value of the user represents the current points balance of the user in the points account corresponding to the user identifier in the points consumption request.

[0115] According to an embodiment of the present disclosure, when the second verification result indicates that the verification fails, the points system terminal prompts the scenario party that the points consumption has failed.

[0116] According to an embodiment of the present disclosure, when the second verification result indicates that the verification is passed, the points system terminal compares the points value to be consumed in the points consumption request with the valid points value of the user to obtain a comparison result to determine whether the current points balance of the user is sufficient for consumption. The points value to be consumed may represent the points value required for the user to consume for points activities such as points redemption.

[0117] In operation S530, when the comparison result indicates that the effective points value of the user is greater than or equal to the points value to be consumed, a points consumption operation corresponding to the points consumption request is performed according to the points value to be consumed to obtain the current points balance of the user.

[0118] According to an embodiment of the present disclosure, when the comparison result indicates that the user's effective points value is less than the points value to be consumed, that is, the user's current points balance is insufficient for the points consumption, the points system terminal prompts the scene party that the points consumption request has failed.

[0119] According to an embodiment of the present disclosure, when the comparison result indicates that the effective points value of the user is greater than or equal to the points value to be consumed, that is, the current points balance of the user is sufficient for the points consumption. The points system terminal can perform a points consumption operation corresponding to the points consumption request according to the points value to be consumed to obtain the new current points balance of the user.

[0120] For example, when the value of points to be consumed in the points consumption request is 100 points and the user's current points balance is 200 points, the points system terminal executes the points consumption operation corresponding to the points consumption request, that is, subtracting the user's effective points value from the value of points to be consumed, that is, the user's new current points balance is 100 points.

[0121] In operation S540, the points consumption flow corresponding to the points consumption request is recorded under the points account corresponding to the user identifier, and the current points balance of the user is sent to the scenario party.

[0122] Among them, the points consumption flow includes the user’s current points balance.

[0123] According to an embodiment of the present disclosure, the points system terminal can also record the points consumption flow corresponding to the points consumption request under the points account corresponding to the user ID. The points consumption flow can also include the scene party order ID, the scene party order details link, etc.

[0124] According to an embodiment of the present disclosure, the points system terminal may also send the user's new current points balance to the scene party to prompt the scene party that the points consumption request is successful, and display the user's current points balance in the scene party.

[0125] According to an embodiment of the present disclosure, when the points system terminal processes the points consumption request, it will first verify the points consumption request according to the scene party identifier and the points rule identifier to restrict the points consumption transaction between the scene party and the user and avoid malicious points consumption. If the verification is passed, the points consumption operation will be executed to realize the points consumption of the user, and the points consumption flow corresponding to the points consumption request will be recorded under the corresponding points account, so as to subsequently query and obtain the user's points details from the points account.

[0126] Figure 6 The flowchart for processing a points request when the points request is a points consumption refund request according to an embodiment of the present disclosure is schematically shown.

[0127] like Figure 6 As shown, the method 600 includes operations S610 to S630.

[0128] In operation S610, under the points account corresponding to the user ID in the points consumption refund request, the points consumption flow corresponding to the scene party ID and the scene party order ID in the points consumption refund request is queried to obtain a query result.

[0129] According to an embodiment of the present disclosure, in the case where the points request is a points consumption refund request, the points system terminal needs to query the points consumption flow corresponding to the scene party identifier and the scene party order identifier under the points account corresponding to the user identifier, and obtain the query result to determine whether the user has conducted a points consumption transaction corresponding to the order related to the points consumption refund request.

[0130] For example, when a user applies for a refund on the points spent on product A at the scene party, the points system terminal needs to first check whether the user has conducted a points consumption transaction corresponding to product A.

[0131] For example, Figure 3 The order IDC shown in is the order ID of the scenario party.

[0132] In operation S620, when the query result indicates that there is a point consumption flow corresponding to the scene party identifier and the scene party order identifier under the point account, the point refund operation corresponding to the point consumption refund request is performed according to the point value to be refunded in the point consumption refund request to obtain the user's current point balance.

[0133] According to an embodiment of the present disclosure, when the query result indicates that there is no point consumption flow corresponding to the scene party identifier and the scene party order identifier under the point account, it indicates that the user has not conducted the corresponding point consumption transaction, and the point system terminal prompts that the refund of the scene party point consumption has failed.

[0134] According to the embodiment of the present disclosure, when the query result indicates that there is a point consumption flow corresponding to the scene party identifier and the scene party order identifier under the point account, it indicates that the user has performed the corresponding point consumption transaction, and the point system terminal can perform the point refund operation corresponding to the point consumption refund request according to the point value to be refunded in the point consumption refund request to obtain the user's new current point balance. Among them, the point value to be refunded can represent the point value that the user needs to refund for consumption.

[0135] According to an embodiment of the present disclosure, when a refund request based on point consumption is determined to be a full refund, a point refund operation corresponding to the point consumption refund request is performed, that is, it is determined whether the point value to be refunded is consistent with the actual point value for refund. If the point value to be refunded is inconsistent with the actual point value for refund, the point system terminal prompts the scenario party that the point consumption refund request has failed; if the point value to be refunded is consistent with the actual point value for refund, the point system terminal subtracts the user's current point balance from the point value to be refunded to make a point consumption refund.

[0136] According to an embodiment of the present disclosure, when a refund request based on point consumption is determined to be a partial refund, the point system terminal executes a point refund operation corresponding to the point consumption refund request, that is, determines whether the point value to be refunded does not exceed the remaining refundable point value. If the point value to be refunded exceeds the remaining refundable point value, the point system terminal prompts the scenario party that the point consumption refund request has failed; if the point value to be refunded does not exceed the remaining refundable point value, the point system terminal subtracts the user's current point balance from the point value to be refunded to make a partial point consumption refund.

[0137] For example, in a user's point consumption flow, the user redeemed 5 items with points and consumed 100 points, among which item A consumed 10 points, item B consumed 20 points, item C consumed 15 points, item D consumed 30 points, and item E consumed 25 points; if the user wants to refund the points consumption of items A and D, the value of the points to be refunded is 40, and the remaining refundable points is 100; if the user continues to refund the points consumption of item E, the value of the points to be refunded is 25, and the remaining refundable points is 60.

[0138] In operation S630, the points consumption refund flow corresponding to the points consumption refund request is recorded under the points account corresponding to the user identifier, and the current points balance of the user is sent to the scenario party.

[0139] Among them, the points consumption refund flow includes the user’s current points balance.

[0140] According to an embodiment of the present disclosure, the points system terminal can also record the points consumption refund flow corresponding to the points consumption refund request under the points account corresponding to the user ID. The points consumption refund flow can also include the scene party order ID, the remaining refundable points value, etc.

[0141] According to an embodiment of the present disclosure, in the case where a refund request based on point consumption is determined to be a full refund, the points system terminal may also send the scene party's order identification, refund points value and the user's current points balance to the scene party to prompt the scene party that the points consumption refund request is successful; in the case where a refund request based on point consumption is determined to be a partial refund, the points system terminal may also send the scene party's order identification, refund points value, remaining refundable points value and the user's current points balance to the scene party to prompt the scene party that the points consumption refund request is successful.

[0142] According to the embodiments of the present disclosure, in the process of processing the point consumption refund request by the points system terminal, it will first query the point consumption flow corresponding to the scene party identifier and the scene party order identifier under the point account corresponding to the user identifier to determine whether the user has conducted the corresponding point consumption transaction to avoid causing point consumption refund errors, and if the user has conducted the corresponding point consumption transaction, execute the point consumption refund operation to realize the refund of the user's point consumption and record the point consumption refund flow corresponding to the point consumption request under the corresponding point account, so as to subsequently query the user's point details from the point account.

[0143] According to an embodiment of the present disclosure, the above-mentioned order processing method also includes: in response to receiving a points details query request from the first scene party, authenticating the first scene party according to the scene party identifier and key corresponding to the first scene party in the points details query request, and obtaining a third authentication result; when the third authentication result indicates that the authentication is passed, querying and obtaining the points transaction flow of the user in the points account corresponding to the user identifier according to the user identifier in the points details query request; sending the user's points transaction flow to the first scene party to display the user's points transaction flow view in the first scene party.

[0144] According to an embodiment of the present disclosure, a user may perform a points detail query operation on the first scene party. For example, a user may click on a points detail query on the interface of the first scene party, and the first scene party may send a points detail query request to the points system terminal.

[0145] According to an embodiment of the present disclosure, the points system terminal will first authenticate the first scene party according to the scene party identifier and key in the points detail query request, and obtain a third authentication result to ensure the security of interactive communication.

[0146] According to an embodiment of the present disclosure, when the third authentication result indicates that the authentication fails, the points system terminal will not process the points detail query request; when the third authentication result indicates that the authentication passes, the points system terminal will process the points detail query request.

[0147] According to an embodiment of the present disclosure, when the third authentication result represents that the authentication is passed and the points detail query request represents all transaction flows of the user conducting points transactions, the points system terminal can query and obtain the points account corresponding to the user identifier based on the user identifier, and send the points transaction flow of the user in the points account to the first scenario party, so that the first scenario party can display the user's points transaction flow view.

[0148] Figure 7 The diagram schematically shows a user's points transaction flow diagram according to an embodiment of the present disclosure.

[0149] According to an embodiment of the present disclosure, when the first scene party is scene party A, the user's point transaction flow view is as follows: Figure 7 As shown, the points transaction flow view shows the points details of users' points transactions in different scenarios.

[0150] According to the embodiments of the present disclosure, since the points transaction flow of each user is recorded in the points system terminal, in response to a points detail query request, the points transaction flow of the user under the corresponding points account can be queried based on the user identifier, and the user's points transaction flow can be sent to the first scenario party, so that the user can intuitively understand the details of the points transactions conducted in each scenario party.

[0151] According to an embodiment of the present disclosure, the above-mentioned order processing method also includes: when the third authentication result indicates that the authentication is passed, according to the user identifier and the scene party identifier in the points details query request, under the points account corresponding to the user identifier, query and obtain the points transaction flow of the first scene party corresponding to the scene party identifier; send the points transaction flow of the first scene party to the first scene party to display the points transaction flow view of the first scene party in the first scene party.

[0152] Among them, the point transaction flow view of the first scenario party includes the point transaction flow of the user performing point transactions on the first scenario party.

[0153] According to an embodiment of the present disclosure, when the third authentication result represents that the authentication is passed and the points details query request represents the query of the transaction flow of the user's points transaction with the first scenario party, the points system terminal can query and obtain the points transaction flow of the first scenario party corresponding to the scene party identifier under the points account corresponding to the user identifier, that is, the points transaction flow of the user's points transaction with the first scenario party.

[0154] According to an embodiment of the present disclosure, the points system terminal may also send the points transaction flow of the first scenario party to the first scenario party so as to display the points transaction flow view of the first scenario party in the first scenario party.

[0155] Figure 8 The schematic diagram shows the points transaction flow diagram of the first scenario party according to an embodiment of the present disclosure.

[0156] According to an embodiment of the present disclosure, when the first scene party is scene party A, the points transaction flow of the first scene party is as follows: Figure 8 As shown, the points transaction flow view shows the points details of the points transaction conducted by the user in the first scenario.

[0157] According to an embodiment of the present disclosure, since the points system terminal records the points transaction flow of each user performing points transactions on each scenario party, in response to a points detail query request, the points system terminal can query the points transaction flow of the user performing points transactions on the first scenario party under the points account corresponding to the user identifier based on the user identifier and the scenario party identifier, and send the points transaction flow of the first scenario party to the first scenario party, so that the user can intuitively understand the details of the points transactions on the first scenario party and realize a separate points detail display for the first scenario party.

[0158] Based on the above, the scenario party terminal needs to handle user interaction and the creation of points activities, while the points system terminal is responsible for the management of the user's points account, and does not need to establish interaction with the user. At the same time, the scenario party provides the user with a clear and visible points detail view. Therefore, the clear system boundary between the scenario party and the points system terminal facilitates the unified management of points and subsequent points settlement. In addition, the points data in the points details obtained by the user in any scenario party query is consistent, that is, the user can view the points situation in multiple scenario parties, that is, the points system terminal provides a multi-channel unified query service, which improves the user experience.

[0159] Fig. 9 The flowchart of an order processing method according to another embodiment of the present disclosure is schematically shown.

[0160] like Fig. 9 As shown, the method 900 includes operation S910 and operation S920.

[0161] In operation S910, in response to the point order tracing operation of the user in the first scenario, a point order tracing request is sent to the point system terminal.

[0162] Among them, the points order tracing request represents viewing the order details of the user's points transaction on the second scene party, and the first scene party and the second scene party are different scene parties in the scene party terminal.

[0163] According to the embodiments of the present disclosure, the points system terminal can set a unified data interaction format, that is, the scene party needs to send a request to the points system terminal according to the data interaction format set by the points system terminal.

[0164] In operation S920, after the points system terminal processes the order link corresponding to the second scenario party, it jumps from the points transaction flow view of the first scenario party to the order details interface of the second scenario party to view the order details of the user's points transaction in the second scenario.

[0165] Among them, when the first authentication result indicates that the authentication is passed and the first scenario party has the order authority to query the second scenario party, the points system terminal processes the order link corresponding to the second scenario party in the points order tracing request; the first authentication result is obtained by the points system terminal authenticating the first scenario party based on the scenario party identifier and key corresponding to the first scenario party in the points order tracing request.

[0166] According to the embodiments of the present disclosure, since the points system terminal provides a unified cross-platform order query and authentication interface, the various scene parties do not need to connect and interact with each other, and can support the viewing of points transaction order details between multiple scene parties, and support users to trace transactions, so that the order details of the user's points transaction on the second scene party can be viewed on the first scene party. In addition, when the points system terminal receives a points order tracing request, the points system terminal first authenticates the first scene party and determines whether the first scene party has the order authority to query the second scene party, so as to ensure the security of interactive communication.

[0167] According to an embodiment of the present disclosure, the above-mentioned order method also includes: in response to the user's point transaction operation on the scene party, sending a point request corresponding to the type of the point transaction operation to the point system terminal, so that the point system terminal processes the point request and sends the user's current point balance to the scene party; in response to receiving the user's current point balance, displaying the user's current point balance in the scene party.

[0168] Wherein, when the second authentication result indicates that the authentication is passed, the points system terminal processes the points request; the second authentication result is obtained by the points system terminal authenticating the scene party according to the scene party identifier and key in the points request.

[0169] According to the embodiments of the present disclosure, point transaction operations may include users redeeming points, making consumption decisions, making deposits, etc. Point transaction operations may include three types of point transactions: point consumption, point accumulation, and point consumption refund. That is, point requests may include point consumption requests, point accumulation requests, and point consumption refund requests.

[0170] Among them, the points request may include user identification, scenario party identification, points rule identification, points transaction type, number of points generated, etc.

[0171] According to an embodiment of the present disclosure, when a user performs a points transaction operation of accumulating points on the scene party, the points accumulation request may also include the reason for generating points, the points expiration time, and the points acquisition activity link, etc.

[0172] Among them, the number of points generated is the point value to be accumulated; the reasons for generating points may include the user's consumption behavior, deposit behavior, etc.

[0173] According to an embodiment of the present disclosure, when a user performs a points transaction operation of points consumption on the scene party, the points consumption request may also include the reason for the points consumption, the scene party order identifier, and the scene party order details link.

[0174] Among them, the number of points generated is the point value to be consumed; the reasons for point consumption may include users redeeming points, using points to offset cash, etc.

[0175] According to an embodiment of the present disclosure, when a user performs a points transaction operation such as a points consumption refund on the scene party, the points consumption refund request may also include the scene party's original consumption order identifier, refund type, and a link to the scene party's order details.

[0176] Among them, the number of points generated is the point value to be refunded, and the refund type can include full refund and partial refund.

[0177] According to the embodiment of the present disclosure, the scene party can also send a points detail query request to the points system terminal, and the points system terminal can query the points transaction flow, that is, the points details, to the scene party through the points detail query interface. The points details can record the scene party ID, scene party order ID, points acquisition activity link, etc. of each points transaction.

[0178] According to an embodiment of the present disclosure, the scene party can also freely choose whether to display the details of the points breakdown, such as a link to a points acquisition activity.

[0179] According to an embodiment of the present disclosure, when a user conducts a points transaction in the scene party, the scene party will send a points request to the points system terminal, and the points system terminal will first authenticate the scene party to ensure the security of interactive communication, and process the points request when the authentication is passed, that is, accumulate, consume or refund the user's current points balance, etc., to achieve an update of the points transaction flow in the points account, and at the same time send the user's current points balance to the scene party, so as to intuitively display the user's current points balance on the scene party, and prompt the scene party that the points request is successful.

[0180] Based on the above order processing method, the present disclosure also provides an order processing device. Fig.10 The device is described in detail.

[0181] Fig.10 The structure block diagram of the order processing device applied to the points system terminal according to the embodiment of the present disclosure is schematically shown.

[0182] like Fig.10As shown, the order processing device 1000 applied to the point system terminal of this embodiment includes a first authentication module 1010 and a first processing module 1020 .

[0183] The first authentication module 1010 is used to respond to receiving a point order tracing request from the first scenario party, authenticate the first scenario party according to the scenario party identifier and key corresponding to the first scenario party in the point order tracing request, and obtain a first authentication result, wherein the point order tracing request represents viewing the order details of the user's point transaction on the second scenario party, and the first scenario party and the second scenario party are different scenario parties in the scenario party terminal. In one embodiment, the first authentication module 1010 can be used to perform the operation S210 described above, which will not be repeated here.

[0184] The first processing module 1020 is used to process the order link corresponding to the second scenario party in the points order tracing request when the first authentication result indicates that the authentication is passed and the first scenario party has the order permission to query the second scenario party, so as to jump from the points transaction flow view of the first scenario party to the order details interface of the second scenario party to view the order details of the user's points transaction on the second scenario party. In one embodiment, the first processing module 1020 can be used to perform the operation S220 described above, which will not be repeated here.

[0185] According to an embodiment of the present disclosure, the order processing device 1000 further includes a distribution module.

[0186] The allocation module is used to allocate respective scene party identifiers, point rule identifiers and keys to at least one scene party connected to the point system terminal, wherein the scene party terminal includes multiple scene parties.

[0187] According to an embodiment of the present disclosure, the order processing apparatus 1000 further includes a second authentication module and a second processing module.

[0188] The second authentication module is used to respond to receiving a points request from the scene party, authenticate the scene party according to the scene party identifier and key in the points request, and obtain a second authentication result.

[0189] The second processing module is used to process the point request when the second authentication result indicates that the authentication is passed, so as to send the user's current point balance to the scenario party.

[0190] According to an embodiment of the present disclosure, the second processing module includes a first verification unit, a first execution unit and a first recording unit.

[0191] The first verification unit is used to verify the point accumulation request according to the scenario party identifier and the point rule identifier in the point accumulation request to obtain a first verification result.

[0192] The first execution unit is configured to, when the first verification result indicates that the verification is passed, execute a point accumulation operation corresponding to the point accumulation request according to the point value to be accumulated in the point accumulation request to obtain a current point balance of the user.

[0193] The first recording unit is used to record the point accumulation flow corresponding to the point accumulation request under the point account corresponding to the user identifier in the point accumulation request, and send the user's current point balance to the scenario party, wherein the point accumulation flow includes the user's current point balance.

[0194] According to an embodiment of the present disclosure, the second processing module further includes a second verification unit, a comparison unit, a second execution unit and a second recording unit.

[0195] The second verification unit is used to verify the point consumption request according to the scenario party identifier and the point rule identifier in the point consumption request to obtain a second verification result.

[0196] The comparison unit is used to compare the to-be-consumed points value in the points consumption request with the effective points value of the user when the second verification result indicates that the verification is passed, to obtain a comparison result, wherein the effective points value of the user indicates the current points balance of the user in the points account corresponding to the user identifier in the points consumption request.

[0197] The second execution unit is used to execute a point consumption operation corresponding to the point consumption request according to the point value to be consumed when the comparison result indicates that the effective point value of the user is greater than or equal to the point value to be consumed, so as to obtain the current point balance of the user.

[0198] The second recording unit is used to record the point consumption flow corresponding to the point consumption request under the point account corresponding to the user identifier, and send the user's current point balance to the scenario party, wherein the point consumption flow includes the user's current point balance.

[0199] According to an embodiment of the present disclosure, the second processing module further includes a third verification unit, a third execution unit and a third recording unit.

[0200] The third verification unit is used to query the point consumption flow corresponding to the scene party identifier and the scene party order identifier in the point consumption refund request under the point account corresponding to the user identifier in the point consumption refund request to obtain the query result.

[0201] The third execution unit is used to execute the point refund operation corresponding to the point consumption refund request according to the point value to be refunded in the point consumption refund request when the query result indicates that there is a point consumption flow corresponding to the scene party identifier and the scene party order identifier under the point account, so as to obtain the user's current point balance.

[0202] The third recording unit is used to record the point consumption refund flow corresponding to the point consumption refund request under the point account corresponding to the user identifier, and send the user's current point balance to the scenario party, wherein the point consumption refund flow includes the user's current point balance.

[0203] According to an embodiment of the present disclosure, the order processing device 1000 further includes a third authentication module, a first query module and a second sending module.

[0204] The third authentication module is used to respond to receiving a points detail query request from the first scene party, authenticate the first scene party according to the scene party identifier and key corresponding to the first scene party in the points detail query request, and obtain a third authentication result.

[0205] The first query module is used to query and obtain the point transaction flow of the user in the point account corresponding to the user identifier according to the user identifier in the point detail query request when the third authentication result indicates that the authentication is passed.

[0206] The second sending module is used to send the user's point transaction flow to the first scenario party to display the user's point transaction flow view in the first scenario party.

[0207] According to an embodiment of the present disclosure, the order processing device 1000 further includes a second query module and a third sending module.

[0208] The second query module is used to query the points transaction flow of the first scene party corresponding to the scene party identifier under the points account corresponding to the user identifier based on the user identifier and the scene party identifier in the points detail query request when the third authentication result indicates that the authentication is passed.

[0209] The third sending module is used to send the point transaction flow of the first scenario party to the first scenario party, so as to display the point transaction flow view of the first scenario party in the first scenario party, wherein the point transaction flow view of the first scenario party includes the point transaction flow of the user performing point transactions in the first scenario party.

[0210] According to an embodiment of the present disclosure, any multiple modules in the first authentication module 1010 and the first processing module 1020 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first authentication module 1010 and the first processing module 1020 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in any appropriate combination of any of them. Alternatively, at least one of the first authentication module 1010 and the first processing module 1020 can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be executed.

[0211] Based on the above order processing method, the present disclosure also provides an order processing device. Fig.11 The device is described in detail.

[0212] Fig.11 The structural block diagram of the order processing device applied to the scenario party terminal according to an embodiment of the present disclosure is schematically shown.

[0213] like Fig.11 As shown, the order processing device 1100 applied to the scenario party terminal of this embodiment includes a first sending module 1110 and a jumping module 1120.

[0214] The first sending module 1110 is used to respond to the user's point order tracing operation on the first scene party and send a point order tracing request to the point system terminal, wherein the point order tracing request represents viewing the order details of the user's point transaction on the second scene party, and the first scene party and the second scene party are different scene parties in the scene party terminal. In one embodiment, the first sending module 1110 can be used to perform the operation S910 described above, which will not be repeated here.

[0215] The jump module 1120 is used to jump from the point transaction flow view of the first scene party to the order details interface of the second scene party after the point system terminal processes the order link corresponding to the second scene party, so as to view the order details of the user's point transaction in the second scene; wherein, when the first authentication result indicates that the authentication is passed and the first scene party has the order authority to query the second scene party, the point system terminal processes the order link corresponding to the second scene party in the point order tracing request; the first authentication result is obtained by the point system terminal authenticating the first scene party according to the scene party identifier and key corresponding to the first scene party in the point order tracing request. In one embodiment, the jump module 1120 can be used to perform the operation S920 described above, which will not be repeated here.

[0216] According to an embodiment of the present disclosure, the above-mentioned order processing device also includes a fourth sending module and a display module.

[0217] The fourth sending module is used to respond to the user's point transaction operation on the scene party, send a point request corresponding to the type of the point transaction operation to the point system terminal, so that the point system terminal processes the point request and sends the user's current point balance to the scene party, wherein when the second authentication result indicates that the authentication is passed, the point system terminal processes the point request; the second authentication result is obtained by the point system terminal authenticating the scene party according to the scene party identifier and key in the point request.

[0218] The display module is used to display the current point balance of the user in the scene party in response to receiving the current point balance of the user.

[0219] According to an embodiment of the present disclosure, any multiple modules in the first sending module 1110 and the jump module 1120 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first sending module 1110 and the jump module 1120 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in an appropriate combination of any of them. Alternatively, at least one of the first sending module 1110 and the jump module 1120 can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be executed.

[0220] Fig.12 A block diagram of an electronic device suitable for implementing an order processing method according to an embodiment of the present disclosure is schematically shown.

[0221] like Fig.12 As shown, the electronic device 1200 according to an embodiment of the present disclosure includes a processor 1201, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1202 or a program loaded from a storage part 1208 to a random access memory (RAM) 1203. The processor 1201 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a dedicated microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1201 may also include an onboard memory for caching purposes. The processor 1201 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0222] In RAM 1203, various programs and data required for the operation of electronic device 1200 are stored. Processor 1201, ROM 1202 and RAM 1203 are connected to each other via bus 1204. Processor 1201 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 1202 and / or RAM 1203. It should be noted that the program can also be stored in one or more memories other than ROM 1202 and RAM 1203. Processor 1201 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0223] According to an embodiment of the present disclosure, the electronic device 1200 may further include an input / output (I / O) interface 1205, which is also connected to the bus 1204. The electronic device 1200 may further include one or more of the following components connected to the input / output (I / O) interface 1205: an input portion 1206 including a keyboard, a mouse, etc.; an output portion 1207 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 1208 including a hard disk, etc.; and a communication portion 1209 including a network interface card such as a LAN card, a modem, etc. The communication portion 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the input / output (I / O) interface 1205 as needed. A removable medium 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1210 as needed, so that a computer program read therefrom is installed into the storage portion 1208 as needed.

[0224] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0225] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus, or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 1202 and / or RAM 1203 described above and / or one or more memories other than ROM 1202 and RAM 1203.

[0226] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the order processing method provided by the embodiment of the present disclosure.

[0227] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 1201. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0228] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 1209, and / or installed from the removable medium 1211. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0229] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1209, and / or installed from the removable medium 1211. When the computer program is executed by the processor 1201, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0230] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

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

[0232] It will be appreciated by those skilled in the art that the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations or combinations are not explicitly described in the present disclosure. In particular, without departing from the spirit and teachings of the present disclosure, the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0233] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. An order processing method, characterized in that: The method comprises: In response to receiving a points order tracing request from a first scenario party, authenticating the first scenario party according to a scenario party identifier and a key corresponding to the first scenario party in the points order tracing request, and obtaining a first authentication result, wherein the points order tracing request represents viewing order details of a points transaction conducted by a user on a second scenario party, and the first scenario party and the second scenario party are different scenario parties in a scenario party terminal; and When the first authentication result indicates that the authentication is passed and the first scenario party has the order authority to query the second scenario party, the order link corresponding to the second scenario party in the points order tracing request is processed, so that the point transaction flow view of the first scenario party jumps to the order details interface of the second scenario party to view the order details of the user's points transaction on the second scenario party.

2. The method according to claim 1, further comprising: A respective scene party identifier, a points rule identifier and a key are allocated to at least one scene party connected to the points system terminal, wherein the scene party terminal includes a plurality of scene parties.

3. The method according to claim 2, further comprising: In response to receiving a points request from the scene party, authenticating the scene party according to the scene party identifier and key in the points request to obtain a second authentication result; In the case where the second authentication result indicates that the authentication is passed, the points request is processed to send the user's current points balance to the scenario party.

4. The method according to claim 3, characterized in that In the case where the point request is a point accumulation request, the processing of the point request to send the current point balance of the user to the scenario party includes: Verifying the point accumulation request according to the scenario party identifier and the point rule identifier in the point accumulation request to obtain a first verification result; If the first verification result indicates that the verification is passed, performing a point accumulation operation corresponding to the point accumulation request according to the point value to be accumulated in the point accumulation request to obtain the current point balance of the user; In the points account corresponding to the user identifier in the points accumulation request, the points accumulation flow corresponding to the points accumulation request is recorded, and the current points balance of the user is sent to the scenario party, wherein the current points balance of the user is included in the points accumulation flow.

5. The method according to claim 3, characterized in that: In the case where the point request is a point consumption request, the processing of the point request to send the current point balance of the user to the scenario party includes: Verifying the point consumption request according to the scenario party identifier and the point rule identifier in the point consumption request to obtain a second verification result; If the second verification result indicates that the verification is passed, the points value to be consumed in the points consumption request is compared with the effective points value of the user to obtain a comparison result, wherein the effective points value of the user indicates the current points balance of the user in the points account corresponding to the user identifier in the points consumption request; If the comparison result indicates that the effective points value of the user is greater than or equal to the points value to be consumed, performing a points consumption operation corresponding to the points consumption request according to the points value to be consumed to obtain the current points balance of the user; In the points account corresponding to the user identifier, the points consumption flow corresponding to the points consumption request is recorded, and the current points balance of the user is sent to the scenario party, wherein the points consumption flow includes the current points balance of the user.

6. The method according to claim 3, characterized in that In the case where the point request is a point consumption refund request, the processing of the point request to send the current point balance of the user to the scenario party includes: Under the points account corresponding to the user ID in the points consumption refund request, query the points consumption flow corresponding to the scene party ID and the scene party order ID in the points consumption refund request to obtain the query result; If the query result indicates that there is a point consumption flow corresponding to the scenario party identifier and the scenario party order identifier under the point account, a point refund operation corresponding to the point consumption refund request is performed according to the point value to be refunded in the point consumption refund request to obtain the current point balance of the user; In the points account corresponding to the user identifier, the points consumption refund flow corresponding to the points consumption refund request is recorded, and the current points balance of the user is sent to the scenario party, wherein the points consumption refund flow includes the current points balance of the user.

7. The method according to claim 1, further comprising: In response to receiving the points detail query request from the first scene party, authenticating the first scene party according to the scene party identifier and key corresponding to the first scene party in the points detail query request to obtain a third authentication result; If the third authentication result indicates that the authentication is passed, querying the points transaction flow of the user in the points account corresponding to the user ID according to the user ID in the points details query request; The points transaction flow of the user is sent to the first scenario party to display the points transaction flow view of the user in the first scenario party.

8. The method according to claim 7, further comprising: If the third authentication result indicates that the authentication is passed, according to the user ID and the scene party ID in the points detail query request, under the points account corresponding to the user ID, query and obtain the points transaction flow of the first scene party corresponding to the scene party ID; and The points transaction flow of the first scenario party is sent to the first scenario party to display the points transaction flow view of the first scenario party in the first scenario party, wherein the points transaction flow view of the first scenario party includes the points transaction flow of the user performing points transactions in the first scenario party.

9. An order processing method, characterized in that: The method comprises: In response to the user's point order tracing operation on the first scenario party, a point order tracing request is sent to the point system terminal, wherein the point order tracing request represents checking the order details of the point transaction performed by the user on the second scenario party, and the first scenario party and the second scenario party are different scenario parties in the scenario party terminal; and After the points system terminal processes the order link corresponding to the second scenario party, jump from the points transaction flow view of the first scenario party to the order details interface of the second scenario party to view the order details of the points transaction conducted by the user in the second scenario; Among them, when the first authentication result indicates that the authentication is passed and the first scenario party has the order authority to query the second scenario party, the points system terminal processes the order link corresponding to the second scenario party in the points order tracing request; the first authentication result is obtained by the points system terminal authenticating the first scenario party based on the scenario party identifier and key corresponding to the first scenario party in the points order tracing request.

10. The method according to claim 9, further comprising: In response to the point transaction operation of the user on the scene party, a point request corresponding to the type of the point transaction operation is sent to the point system terminal, so that the point system terminal processes the point request and sends the current point balance of the user to the scene party, wherein, if the second authentication result indicates that the authentication is passed, the point system terminal processes the point request; the second authentication result is obtained by the point system terminal authenticating the scene party according to the scene party identifier and key in the point request; and In response to receiving the current points balance of the user, the current points balance of the user is displayed in the scenario party.

11. An order processing device, characterized in that: The device comprises: A first authentication module is configured to, in response to receiving a points order tracing request from a first scenario party, authenticate the first scenario party according to a scenario party identifier and a key corresponding to the first scenario party in the points order tracing request, and obtain a first authentication result, wherein the points order tracing request represents viewing order details of a user performing a points transaction on a second scenario party, and the first scenario party and the second scenario party are different scenario parties in a scenario party terminal; and The first processing module is used to process the order link corresponding to the second scenario party in the points order tracing request when the first authentication result indicates that the authentication is passed and the first scenario party has the order authority to query the second scenario party, so as to jump from the points transaction flow view of the first scenario party to the order details interface of the second scenario party to view the order details of the user's points transaction on the second scenario party.

12. An order processing device, characterized in that: The device comprises: A first sending module is configured to send a points order tracing request to a points system terminal in response to a points order tracing operation of a user on a first scenario party, wherein the points order tracing request represents checking order details of a points transaction performed by the user on a second scenario party, and the first scenario party and the second scenario party are different scenario parties in the scenario party terminal; and A jump module, configured to jump from the points transaction flow view of the first scenario party to the order details interface of the second scenario party after the points system terminal processes the order link corresponding to the second scenario party, so as to view the order details of the points transaction conducted by the user in the second scenario; Among them, when the first authentication result indicates that the authentication is passed and the first scenario party has the order authority to query the second scenario party, the points system terminal processes the order link corresponding to the second scenario party in the points order tracing request; the first authentication result is obtained by the points system terminal authenticating the first scenario party based on the scenario party identifier and key corresponding to the first scenario party in the points order tracing request.

13. An electronic device, comprising: one or more processors; a memory for storing one or more computer programs, It is characterized in that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 8 or claims 9 to 10.

14. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 8 or claims 9 to 10 are implemented.

15. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 8 or claims 9 to 10 are implemented.

Citation Information

Patent Citations

  • Point reward exchanging system, device and method

    CN101751635A

  • Member point data processing method

    CN106651455A

  • Cross-system account integral transfer method and system

    CN107862533A

  • Scene-based authentication method and device, server and storage medium

    CN110290142A

  • Unified service management method and platform

    CN110852545A