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

Abstract

This disclosure provides an order processing method, apparatus, device, medium, and program product, which can be applied to the field of data interaction technology. The method includes: responding to receiving a points order tracing request from a first scenario party; 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, obtaining a first authentication result, wherein the points order tracing request indicates viewing the order details of a user's points transaction in a second scenario party; if the first authentication result indicates successful authentication and the first scenario party has the permission to query orders in the second scenario party, processing the order link corresponding to the second scenario party in the points order tracing request, causing a 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 in the second scenario party.

Description

Technical Field

[0001] This disclosure relates to the field of data interaction technology, and in particular to an order processing method, apparatus, device, medium, and program product. Background Technology

[0002] In banking systems, users accumulate points in their loyalty programs through various activities such as spending, depositing, and participating in marketing campaigns. Similarly, different banking systems offer different ways to use points, such as redeeming points, using points for cash, and point redemption. However, because each platform operates its own points program, it's difficult for users to trace the source of transactions when checking their points history, which can easily lead to user complaints. Summary of the Invention

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

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

[0005] In response to receiving a points order tracing request from a first scenario provider, the system authenticates the first scenario provider based on the scenario provider identifier and key corresponding to the first scenario provider in the points order tracing request, obtaining a first authentication result. The points order tracing request represents viewing the order details of a user's points transaction with a second scenario provider. The first and second scenario providers are different scenario providers within the scenario provider terminal.

[0006] If the first authentication result indicates that the authentication is successful and the first scenario party has the permission to query the orders of the second scenario party, the order link corresponding to the second scenario party in the above 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 in the second scenario party.

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

[0008] In response to a user's points order tracing operation in the first scenario, a points order tracing request is sent to the points system terminal. This request indicates a desire to view the order details of the user's points transaction in the second scenario. The first and second scenarios are different scenarios within the scenario terminal.

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

[0010] Wherein, if the first authentication result indicates that the authentication is successful and the first scenario party has the permission to query the order of 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.

[0011] A third aspect of this disclosure provides an order processing apparatus, comprising: a first authentication module and a first processing module.

[0012] The first authentication module is used to respond to a points order tracing request received from a first scenario party, and to authenticate the first scenario party based on the scenario party identifier and key corresponding to the first scenario party in the points order tracing request, thereby obtaining a first authentication result. The points order tracing request represents viewing the order details of a user's points transaction in a second scenario party. The first scenario party and the second scenario party are different scenario parties within the scenario party terminal.

[0013] The first processing module is used to process the order link corresponding to the second scenario party in the above-mentioned points 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 permission to query the orders of the above-mentioned second scenario party, so that the points transaction flow view of the above-mentioned first scenario party jumps to the order details interface of the above-mentioned second scenario party to view the order details of the above-mentioned user's points transaction in the above-mentioned second scenario party.

[0014] A fourth aspect of this disclosure provides an order processing apparatus, comprising: a first sending module and a redirection module.

[0015] The first sending module is configured to respond to a user's points order tracing operation in the first scenario by sending a points order tracing request to the points system terminal. This request indicates the intention to view the order details of the user's points transaction in the second scenario. The first and second scenarios are different scenarios within the scenario terminal.

[0016] The jump module is used to jump from the points transaction flow view of the first scenario to the order details interface of the second scenario after the order link corresponding to the second scenario is processed in the points system terminal, so as to view the order details of the user's points transaction in the second scenario;

[0017] Wherein, if the first authentication result indicates that the authentication is successful and the first scenario party has the permission to query the order of 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.

[0018] A fifth aspect of this 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 method described above.

[0019] A sixth aspect of this disclosure also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a processor, implement the steps of the above-described method.

[0020] The seventh aspect of this disclosure also provides a computer program product, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method.

[0021] According to the order processing method, apparatus, equipment, medium, and program products provided in this disclosure, since the points system terminal provides a unified cross-platform order query and authentication interface, there is no need for interaction between different scenario parties. It can support viewing the details of points transaction orders between multiple scenario parties and support users to trace the source of transactions. The first scenario party can view the order details of the user's points transaction in the second scenario party. Furthermore, when the points system terminal receives a points order traceability request, the points system terminal first authenticates the first scenario party and determines whether the first scenario party has the permission to query the orders of the second scenario party to ensure the security of interactive communication. Attached Figure Description

[0022] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0023] Figure 1 This diagram illustrates an application scenario of the order processing method according to an embodiment of the present disclosure.

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

[0025] Figure 3 This diagram illustrates the jump relationship of points order tracing according to an embodiment of the present disclosure;

[0026] Figure 4 This schematically illustrates a flowchart of processing a points request when the points request is a points accumulation request, according to an embodiment of the present disclosure.

[0027] Figure 5 This illustration shows a flowchart of processing a points request when the points request is a points consumption request, according to an embodiment of the present disclosure.

[0028] Figure 6 This illustration shows a flowchart of processing a points request when the points request is a points redemption refund request, according to an embodiment of the present disclosure.

[0029] Figure 7 An illustrative view of a user's points transaction history according to an embodiment of this disclosure is shown.

[0030] Figure 8 This schematically illustrates a points transaction flow view of a first scenario party according to an embodiment of the present disclosure;

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

[0032] Figure 10 This schematically illustrates a structural block diagram of an order processing apparatus applied to an points system terminal according to an embodiment of the present disclosure;

[0033] Figure 11 This schematically illustrates a structural block diagram of an order processing device applied to a scenario-side terminal according to an embodiment of the present disclosure; and

[0034] Figure 12 A block diagram schematically illustrates an electronic device suitable for implementing an order processing method according to an embodiment of the present disclosure. Detailed Implementation

[0035] The embodiments of the present disclosure will now 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 disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0036] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

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

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

[0039] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0040] In the technical solution disclosed herein, the user information (including but not limited to user personal information, user image information, user device information, such as location information) and data (including but not limited to data used for analysis, stored data, and displayed data) involved are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of related data all comply with relevant laws, regulations, and standards, necessary confidentiality measures have been taken, and they do not violate public order and good morals. Corresponding operation entry points are provided for users to choose to authorize or refuse.

[0041] In scenarios involving automated decision-making using personal information, the methods, devices, and systems provided in this disclosure all offer users corresponding entry points for choosing to agree to or reject the automated decision-making results. If the user chooses to reject, the process proceeds to the expert decision-making stage. Here, "automated decision-making" refers to the activity of automatically analyzing and evaluating an individual's behavioral habits, interests, or economic, health, and credit status through computer programs, and then making a decision. Here, "expert decision-making" refers to the activity of making decisions by personnel who specialize in a particular field, possess specialized experience, knowledge, and skills, and have reached a certain level of professional expertise.

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

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

[0044] Users can use the scenario-based terminal 110 to interact with the points system terminal 120 via the network to receive or send messages, etc. Each scenario-based terminal 110 can have various communication client applications installed, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0045] Each scenario party in the scenario terminal 110 can be a variety of electronic devices with a display screen and support for web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

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

[0047] For example, in response to a points order tracing request received from the first scenario party, the points system terminal 120 can authenticate the first scenario party based on the scenario party identifier and key corresponding to the first scenario party in the points order tracing request, obtain a first authentication result, and if the first authentication result indicates that the authentication is successful and the first scenario party has the permission to query the orders of the second scenario party, process the order link corresponding to the second scenario party in the points order tracing request, 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 in the second scenario party.

[0048] It should be noted that the order processing method provided in this embodiment can generally be executed by the points system terminal 120. Correspondingly, the order processing device provided in this embodiment can generally be installed in the points system terminal 120. The order processing method provided in this embodiment can also be executed by a server or server cluster that is different from the points system terminal 120 and capable of communicating with each scene party and / or the points system terminal 120. Correspondingly, the order processing device provided in this embodiment can also be installed in a server or server cluster that is different from the points system terminal 120 and capable of communicating 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 shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0050] The following will be based on Figure 1 The described scene, through Figures 2-9 The order processing method according to the embodiments of this disclosure will be described in detail.

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

[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 traceability request from the first scenario party, the first scenario party is authenticated based on the scenario party identifier and key corresponding to the first scenario party in the points order traceability request, and the first authentication result is obtained.

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

[0055] According to embodiments of this disclosure, when a user views points details in a first scenario, the first scenario can display a points transaction log view, which can show the user's current points balance, points transactions made by the user in different scenarios, and other points details.

[0056] For example, if the first scenario is scenario A, the points transaction log view of scenario A can also display the points transactions made by the user in scenario B.

[0057] According to embodiments of this disclosure, in order to allow users to view order details of points transactions made by users in the second scenario on the interface of the first scenario, users can perform points order traceability operations on points transactions in the second scenario in the points transaction flow view of the first scenario. For example, users can click on the points details section corresponding to the second scenario in the points transaction flow view so that the first scenario can send a points order traceability request to the points system terminal.

[0058] The points order traceability request may include the scenario party identifier and key corresponding to the first scenario party.

[0059] According to embodiments of this disclosure, each scenario provider in the scenario provider terminal can be used to create points-based transaction activities. For example, scenario providers can establish points-based transaction activities such as redeeming goods with points, using points for cash payments, and accumulating points for consumption, so that users can conduct points-based transactions within the scenario provider. In other words, the scenario provider can handle user interactions, meaning that user actions are carried out within the scenario provider, such as tracing the origin of points-based orders. The scenario provider can also provide users with a clearly visible view of the points-based transaction flow.

[0060] According to an embodiment of this disclosure, in response to a received points order traceability request, the points system terminal authenticates the first scenario party based on the scenario party identifier and key corresponding to the first scenario party, and obtains a first authentication result.

[0061] For example, the points system terminal stores keys corresponding to multiple scenario parties. When the points system terminal receives a points order traceability request, it queries the key stored in the points system terminal corresponding to the scenario party identifier corresponding to the first scenario party in the points order traceability request. The key stored in the points system terminal is then compared with the key in the points order traceability request. If they match, the first authentication result indicates that the authentication is successful; if they do not match, the first authentication result indicates that the authentication is unsuccessful.

[0062] According to embodiments of this disclosure, the authentication of the first scenario party based on the scenario party identifier and key in the points order traceability request is for security verification to ensure the security of interactive communication.

[0063] In operation S220, if the first authentication result indicates that the authentication is successful and the first scenario party has the permission 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 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 in the second scenario party.

[0064] According to the embodiments of this disclosure, if the first authentication result indicates that the authentication is successful, it is also necessary to determine whether the first scenario party has the permission to query the order of the second scenario party. If the first scenario party does not have the permission to query the order of 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 permission to query the order of 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 pre-configure the query permissions between different scenarios, that is, whether each scenario has the order permission to query order details. For example, scenario A has the permission to query the orders of scenario B, that is, scenario A can view the orders of scenario C.

[0066] According to an embodiment of this disclosure, the points system terminal processes the order link corresponding to the second scenario party, causing the interface of the first scenario party to jump 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 points transaction made by the user in the second scenario party on the interface of the first scenario party.

[0067] Figure 3 The diagram illustrates the jump relationship of points order tracing according to an embodiment of the present disclosure.

[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 embodiments of this disclosure, when a user wants to query their points details, the first scenario provider can display the user's points details, namely, the points transaction log view 310. The points transaction log view 310 of the first scenario provider shows that the user's current points balance is 150 points, and also shows the points details of the user's points transactions with scenario providers A, B, and C.

[0070] For example, in the points details section for points transactions conducted at Scenario C, Scenario C is the Scenario C identifier, points consumption is the points transaction type, -50 points is the points consumption value, xx year xx month xx day is the points consumption time, and the order details URL (Uniform Resource Locator, web address or URL) is the Scenario C order details link.

[0071] According to embodiments of this disclosure, a user performs a points order traceability operation for points transactions in the second scenario. Specifically, the user can click on the points details section corresponding to scenario C in the points transaction flow view, i.e., click on... Figure 3 In the points details section of scenario C shown in the diagram, scenario A can send a points order traceability request to the points system terminal 120.

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

[0073] According to the embodiments of this disclosure, since the points system terminal provides a unified cross-platform order query authentication interface, there is no need for interaction between different scenario parties to support the viewing of points transaction order details between multiple scenario parties. It also supports users to trace transactions, so that the first scenario party can view the order details of the user's points transaction in the second scenario party. Furthermore, when the points system terminal receives a points order tracing request, the points system terminal first authenticates the first scenario party and determines whether the first scenario party has the permission to query the orders of the second scenario party to ensure the security of interactive communication.

[0074] According to embodiments of this disclosure, the order processing method further includes: assigning a scene party identifier, a points rule identifier, and a key to at least one scene party connected to the points system terminal, wherein the scene party terminal includes multiple scene parties.

[0075] According to embodiments of this disclosure, the points system terminal can assign scene party identifiers and keys to scene parties connected to the points system terminal, and enable network access between scene parties and the points system terminal.

[0076] For example, the points system terminal can assign keys to the connected scene parties based on asymmetric encryption algorithms; the points system terminal can also assign scene party IDs, or scene party identifiers, to the connected scene parties based on UUID (Universally Unique Identifier) ​​generation methods.

[0077] According to embodiments of this disclosure, the points system terminal can configure points rules for the corresponding scene party based on the scene party identifier, and generate a unique rule ID, i.e., points rule identifier, for each points rule.

[0078] Specifically, for a particular scenario, at least one rule related to points accumulation and at least one rule related to points consumption can be configured for that scenario, and a corresponding points rule identifier can be generated for each rule.

[0079] For example, the rules for accumulating points could be that the total amount of points spent cannot exceed 1,000, and a single point purchase cannot exceed 100, etc.

[0080] According to embodiments of this disclosure, for scenario A and scenario B, the points system terminal can generate a points rule identifier, rule A1, for the points accumulation rules in scenario A, and rule A2 for the points consumption rules; it can generate rule B1 for the points accumulation rules in scenario B, and rule B2 for the points consumption rules.

[0081] For example, rule A1 can be that the total points accumulated in a single transaction cannot exceed 50, while rule B1 can be that the total points accumulated in a single transaction cannot be less than 50. This means that the point rules of different scenarios can be mutually exclusive. Alternatively, rule A1 can be that the total accumulated points cannot exceed 1000, while rule B1 can be that the total accumulated points cannot exceed 1000. This means that the point rules of different scenarios can also be effective simultaneously.

[0082] According to embodiments of this disclosure, the points system terminal will also store the key corresponding to each scenario party identifier and the points rule corresponding to the points rule identifier, so that the points system terminal can query the corresponding key based on the scenario party identifier in the request and query the corresponding points rule based on the points rule identifier in the request.

[0083] According to embodiments of this disclosure, the points system terminal pre-assigns corresponding scene identifiers, points rule identifiers, and keys to the connected scene parties as the basis for subsequent scene party authentication and secure interactive communication, and as the basis for the points system terminal to authenticate and query the scene parties, thus ensuring secure interactive communication between the scene parties and the points system terminal.

[0084] According to embodiments of this disclosure, the order processing method further includes: in response to receiving a points request from a scenario provider, authenticating the scenario provider based on the scenario provider identifier and key in the points request to obtain a second authentication result; and if the second authentication result indicates that the authentication is successful, processing the points request to send the user's current points balance to the scenario provider.

[0085] According to embodiments of this disclosure, a user can conduct points transactions at any of the participating venues within a given venue. When a user conducts a points transaction at a venue, that venue will send a corresponding points request to the points system terminal. The types of points transactions can include points accumulation, points consumption, and points consumption refunds.

[0086] According to an embodiment of this disclosure, when the points system terminal receives the points request, it first authenticates the scene party based on the scene party identifier and key in the points request, and obtains a second authentication result to determine the security of interactive communication.

[0087] According to embodiments of this disclosure, if the second authentication result indicates that authentication has failed, the points system terminal will not process the points request; if the second authentication result indicates that authentication has passed, the points system terminal will process the points request, that is, accumulate, consume, or refund the user's current points balance recorded in the points system terminal to obtain the user's new current points balance.

[0088] According to embodiments of this disclosure, the points system terminal can also send the user's current points balance to the scene provider, so that the scene provider can display the user's current points balance to indicate that the points request was successful.

[0089] According to embodiments of this 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 identifier in the points request. If a points account corresponding to the user identifier can be found in the points system terminal, it proves that the user is not a new user; if a points account corresponding to the user identifier cannot be found in the points system terminal, it proves that the user is a new user, and a new points account needs to be opened for the user. The user's points account can record the transaction history of each points transaction.

[0090] The principle for each scenario party to access the points system terminal is that the user identifier is unique. That is, the user information exists in different scenario parties, but in the points system terminal, each user has only one user identifier. In addition, the points system terminal will store the user identifier of each user, such as user A, user B, etc.

[0091] According to embodiments of this disclosure, when a user conducts a points transaction at a location, the location sends a points request to the points system terminal. The points system terminal first authenticates the location to ensure secure communication. If authentication is successful, it processes the points request, such as accumulating, consuming, or refunding the user's current points balance, updating the points transaction history in the points account, and sending the user's current points balance to the location so that the location can visually display the current points balance to the user and indicate that the points request was successful.

[0092] Figure 4 The flowchart illustrating the processing of an integration request when the integration request is an integration accumulation request, according to an embodiment of the present disclosure, is 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 based on the scenario identifier and point rule identifier in the point accumulation request, and the first verification result is obtained.

[0095] According to an embodiment of this disclosure, when the points request is a points accumulation request, the points system terminal verifies the points accumulation request based on the scene identifier and points rule identifier in the points accumulation request, and obtains a first verification result.

[0096] According to embodiments of this disclosure, the points system terminal can query other points rules related to the scenario party based on the scenario party identifier in the points request. For example, if the points request is a points accumulation request, it can query other points accumulation rules related to the scenario party, and query the points rule corresponding to the points rule identifier in the points request. The points request is then verified based on these points rules.

[0097] According to embodiments of this disclosure, when verifying a points request, the points system terminal can be configured to require the corresponding points transaction to simultaneously meet the corresponding points rules, or it can be configured that the corresponding points transaction only needs to meet one of the corresponding points rules. In other words, the points system terminal can configure the points rules that the points transaction needs to meet as needed.

[0098] For example, the points system terminal retrieves other points accumulation rules A related to the scenario based on the scenario identifier in the points accumulation request, and retrieves points rule B based on the points rule identifier in the points accumulation request. If a points accumulation transaction requires both points accumulation rules A and points rule B to pass verification, such as points accumulation rule A being that a single points accumulation cannot exceed 100 points, and points rule B being that the total amount of points accumulated by the user cannot exceed 1000 points, then if the user's points transaction requires accumulating 50 points and the user's total points accumulation is 980 points, the verification of the user's points request will fail.

[0099] In operation S420, if the first verification result indicates that the verification is successful, the points accumulation operation corresponding to the points accumulation request is executed according to the points to be accumulated value in the points accumulation request to obtain the user's current points balance.

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

[0101] According to embodiments of this disclosure, if the first verification result indicates that the verification is successful, the points system terminal can perform a points accumulation operation corresponding to the points accumulation request based on the points to be accumulated value in the points accumulation request, so as to obtain the user's new current points balance. Here, the points to be accumulated value represents the points required for the user to accumulate for points-earning activities such as deposits.

[0102] For example, if the 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 will perform the points accumulation operation corresponding to the points accumulation request, that is, add the points to be accumulated to the user's current points balance, so that the user's new current points balance is 120 points.

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

[0104] The points accumulation record includes the user's current points balance.

[0105] According to embodiments of this disclosure, the points system terminal can also record points accumulation records corresponding to points accumulation requests under the points account corresponding to the user identifier. The points accumulation records may also include the reason for points accumulation, points expiration time, and links to information about points acquisition scenarios.

[0106] According to embodiments of this disclosure, the points system terminal can also send the user's new current points balance to the scene provider to indicate that the points accumulation request was successful and display the current points balance to the user in the scene provider.

[0107] According to embodiments of this disclosure, during the processing of a points accumulation request by the points system terminal, the point accumulation request is first verified based on the scenario provider identifier and the points rule identifier to restrict points accumulation transactions between the scenario provider and the user, thereby preventing malicious points acquisition. If the verification is successful, the points accumulation operation is executed to accumulate the user's points, and the points accumulation transaction record corresponding to the points accumulation request is recorded in the corresponding points account so that the user's points details can be retrieved from the points account later.

[0108] Figure 5 The flowchart illustrating the processing of a points request in the case of a points consumption request according to an embodiment of the present disclosure is shown.

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

[0110] When operating S510, the points consumption request is verified based on the scenario identifier and points rule identifier in the points consumption request, and a second verification result is obtained.

[0111] According to an embodiment of this disclosure, when the points request is a points consumption request, the points system terminal first verifies the points consumption request based on the scenario identifier and points rule identifier in the points consumption request, and obtains a second verification result.

[0112] For example, the points system terminal retrieves other points consumption rules A related to the scenario based on the scenario identifier in the points consumption request, and retrieves points rule B based on the points rule identifier in the points consumption request. If a points consumption transaction requires both points consumption rule A and points rule B to pass verification, such as points consumption rule A being that a single points consumption cannot exceed 50 points, and points rule B being that the total amount of points consumed by the user cannot exceed 500 points, then if the user's points transaction requires 50 points and the user's total points consumption is 480 points, the verification of the user's points request will fail.

[0113] In operation S520, if the second verification result indicates that the verification is successful, the value of points to be consumed in the points consumption request is compared with the user's valid points value to obtain the comparison result.

[0114] Among them, the user's valid points value represents the current points balance of the user under the points account corresponding to the user identifier in the points consumption request.

[0115] According to an embodiment of this disclosure, if the second verification result indicates that the verification fails, the points system terminal will prompt the scenario party that the points consumption has failed.

[0116] According to embodiments of this disclosure, if the second verification result indicates that the verification is successful, the points system terminal compares the points to be consumed value in the points consumption request with the user's valid points value to obtain a comparison result, thereby determining whether the user's current points balance is sufficient for consumption. The points to be consumed value can represent the points required for the user to consume for points redemption and other points-related activities.

[0117] In operation S530, if the comparison result indicates that the user's valid points value is greater than or equal to the points value to be consumed, the points consumption operation corresponding to the points consumption request is executed according to the points value to be consumed, and the user's current points balance is obtained.

[0118] According to embodiments of this disclosure, if the comparison result indicates that the user's valid 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 scenario party that the points consumption request has failed.

[0119] According to embodiments of this disclosure, if the comparison result indicates that the user's valid points value is greater than or equal to the points value to be consumed, that is, the user's current points balance is sufficient for the points consumption. The points system terminal can execute the points consumption operation corresponding to the points consumption request based on the points value to be consumed, to obtain the user's new current points balance.

[0120] For example, if the points to be consumed in a points consumption request is 100 points and the user's current points balance is 200 points, the points system terminal will execute the points consumption operation corresponding to the points consumption request, that is, subtract the user's valid points value from the points to be consumed, so that the user's new current points balance is 100 points.

[0121] When operating the S540, under the points account corresponding to the user identifier, record the points consumption transaction record corresponding to the points consumption request, and send the user's current points balance to the scenario party.

[0122] The points consumption record includes the user's current points balance.

[0123] According to embodiments of this disclosure, the points system terminal can also record points consumption records corresponding to points consumption requests under the points account corresponding to the user identifier. The points consumption records may also include a scenario-based order identifier, a scenario-based order details link, etc.

[0124] According to embodiments of this disclosure, the points system terminal can also send the user's new current points balance to the scene provider to indicate that the points consumption request was successful and display the current points balance to the user in the scene provider.

[0125] According to the embodiments of this disclosure, during the process of processing a points consumption request, the points system terminal first verifies the points consumption request based on the scenario provider identifier and the points rule identifier to restrict points consumption transactions between the scenario provider and the user, thereby preventing malicious points consumption. If the verification is successful, the points consumption operation is executed to realize the user's points consumption, and the points consumption transaction record corresponding to the points consumption request is recorded in the corresponding points account so that the user's points details can be retrieved from the points account later.

[0126] Figure 6 The flowchart illustrating the processing of a points request in the case of a points redemption refund request according to an embodiment of the present disclosure is shown.

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

[0128] When operating S610, under the points account corresponding to the user identifier in the points consumption refund request, query the points consumption transaction records corresponding to the scenario party identifier and scenario party order identifier in the points consumption refund request, and obtain the query results.

[0129] According to embodiments of this disclosure, when the points request is a points consumption refund request, the points system terminal needs to query the points consumption transaction records corresponding to the scenario party identifier and the scenario party order identifier under the points account corresponding to the user identifier, and obtain the query results to determine whether the user has made a points consumption transaction corresponding to the order related to the points consumption refund request.

[0130] For example, if a user applies for a refund of points for product A at a service provider, the points system terminal needs to first check whether the user has made a points transaction for product A.

[0131] For example, Figure 3 The order IDC shown is the scene party's order identifier.

[0132] When operating S620, if the query results indicate that there are points consumption records corresponding to the scenario identifier and the scenario order identifier under the points account, the points refund operation corresponding to the points refund request is executed according to the points to be refunded value in the points consumption refund request, and the user's current points balance is obtained.

[0133] According to the embodiments of this disclosure, if the query results indicate that there is no points consumption transaction record corresponding to the scenario provider identifier and the scenario provider order identifier under the points account, it means that the user has not made the corresponding points consumption transaction, and the points system terminal prompts the scenario provider that the points consumption refund has failed.

[0134] According to embodiments of this disclosure, if the query results indicate that there are points consumption records corresponding to the scenario identifier and the scenario order identifier under the points account, it indicates that the user has made the corresponding points consumption transaction. The points system terminal can execute the points refund operation corresponding to the points refund request based on the points to be refunded value in the points consumption refund request to obtain the user's new current points balance. The points to be refunded value can represent the points value required for the user to receive a refund.

[0135] According to embodiments of this disclosure, when a points-based refund request is determined to be a full refund, a points refund operation corresponding to the points-based refund request is executed. That is, it is determined whether the points to be refunded are consistent with the points actually refunded. If the points to be refunded are inconsistent with the points actually refunded, the points system terminal prompts the scenario party that the points-based refund request has failed. If the points to be refunded are consistent with the points actually refunded, the points system terminal subtracts the points to be refunded from the user's current points balance to process the points-based refund.

[0136] According to embodiments of this disclosure, when a points-based refund request is determined to be a partial refund, the points system terminal executes a points refund operation corresponding to the points-based refund request. That is, it determines whether the points to be refunded do not exceed the remaining refundable points. If the points to be refunded exceed the remaining refundable points, the points system terminal prompts the scenario party that the points-based refund request has failed. If the points to be refunded do not exceed the remaining refundable points, the points system terminal subtracts the user's current points balance from the points to be refunded to process a partial points-based refund.

[0137] For example, in a user's points spending transaction, the user redeemed 5 items using points, spending 100 points in total. Item A cost 10 points, Item B cost 20 points, Item C cost 15 points, Item D cost 30 points, and Item E cost 25 points. If the user wants to request a refund for Items A and D, the refundable points amount to 40, and the remaining refundable points amount to 100. If the user then requests a refund for Item E, the refundable points amount to 25, and the remaining refundable points amount to 60.

[0138] When operating S630, under the points account corresponding to the user identifier, record the points consumption refund transaction corresponding to the points consumption refund request, and send the user's current points balance to the scenario party.

[0139] The refund record for points-based spending includes the user's current points balance.

[0140] According to embodiments of this disclosure, the points system terminal can also record points consumption refund transaction details corresponding to points consumption refund requests under the points account corresponding to the user identifier. The points consumption refund transaction details may also include the scenario-based order identifier, remaining refundable points value, etc.

[0141] According to embodiments of this disclosure, when a points-based refund request is determined to be a full refund, the points system terminal can also send the scenario provider's order identifier, the refund points value, and the user's current points balance to the scenario provider to indicate that the points-based refund request was successful; when a points-based refund request is determined to be a partial refund, the points system terminal can also send the scenario provider's order identifier, the refund points value, the remaining refundable points value, and the user's current points balance to the scenario provider to indicate that the points-based refund request was successful.

[0142] According to embodiments of this disclosure, during the processing of a points consumption refund request by the points system terminal, the system first queries the points consumption transaction records corresponding to the scenario provider identifier and the scenario provider order identifier under the points account corresponding to the user identifier to determine whether the user has made the corresponding points consumption transaction, thus avoiding errors in points consumption refunds. If the user has made the corresponding points consumption transaction, the system executes the points consumption refund operation to refund the user's points consumption and record the points consumption refund transaction records corresponding to the points consumption request under the corresponding points account, so that the user's points details can be queried from the points account later.

[0143] According to embodiments of this disclosure, the order processing method further includes: in response to receiving a points details query request from a first scenario party, authenticating the first scenario party based on the scenario party identifier and key corresponding to the first scenario party in the points details query request, and obtaining a third authentication result; if the third authentication result indicates that the authentication is successful, querying the user's points transaction history in the points account corresponding to the user identifier based on the user identifier in the points details query request; and sending the user's points transaction history to the first scenario party to display the user's points transaction history view in the first scenario party.

[0144] According to embodiments of this disclosure, users can perform points details query operations on the first scenario platform. For example, if a user clicks "points details query" on the interface of the first scenario platform, the first scenario platform can send a points details query request to the points system terminal.

[0145] According to embodiments of this disclosure, the points system terminal first authenticates the first scenario party based on the scenario party identifier and key in the points details query request, and obtains a third authentication result to ensure the security of interactive communication.

[0146] According to embodiments of this disclosure, if the third authentication result indicates that authentication has failed, the points system terminal will not process the points details query request; if the third authentication result indicates that authentication has passed, the points system terminal will process the points details query request.

[0147] According to an embodiment of this disclosure, when the third authentication result indicates that the authentication is successful and the points details query request indicates that the user has made all points transactions, the points system terminal can query the points account corresponding to the user identifier based on the user identifier, and send the user's points transaction records in the points account to the first scenario party so that the first scenario party can display the user's points transaction record view.

[0148] Figure 7 An illustrative view of a user's points transaction history is shown according to an embodiment of this disclosure.

[0149] According to embodiments of this disclosure, when the first scenario party is scenario party A, the user's points transaction log view is as follows: Figure 7 As shown, this points transaction log view displays the details of points transactions made by users in different scenarios.

[0150] According to embodiments of this disclosure, since the points system terminal records the points transaction history of each user, in response to a points details query request, the points transaction history of the user under the corresponding points account can be queried based on the user identifier, and the user's points transaction history 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 this disclosure, the order processing method further includes: if the third authentication result indicates that the authentication is successful, querying the points transaction history of the first scenario party corresponding to the scenario party identifier under the points account corresponding to the user identifier based on the user identifier and scenario party identifier in the points details query request; and sending the points transaction history of the first scenario party to the first scenario party to display the points transaction history view of the first scenario party in the first scenario party.

[0152] The points transaction log view of the first scenario includes the points transaction log of users conducting points transactions in the first scenario.

[0153] According to the embodiments of this disclosure, when the third authentication result indicates that the authentication is passed and the points details query request indicates that the user's points transactions in the first scenario are being queried, the points system terminal can query the points transaction details of the first scenario corresponding to the scenario identifier under the points account corresponding to the user identifier, that is, the points transaction details of the user's points transactions in the first scenario.

[0154] According to embodiments of this disclosure, the points system terminal can also send the points transaction log of the first scenario party to the first scenario party so that the points transaction log view of the first scenario party can be displayed in the first scenario party.

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

[0156] According to embodiments of this disclosure, when the first scenario party is scenario party A, the transaction flow of the first scenario party's points is as follows: Figure 8 As shown, this points transaction flow view displays the details of points transactions made by a user in the first scenario.

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

[0158] Based on the above, the scenario-based terminal needs to handle user interaction and the creation of points activities, while the points system terminal is responsible for managing user points accounts and does not need to establish user interaction. Simultaneously, the scenario-based terminal provides users with a clear and visible view of points details. Therefore, the clear system boundary between the scenario-based terminal and the points system terminal facilitates unified points management and subsequent points settlement. Furthermore, the points data is consistent across all scenario-based terminals, meaning users can view their points status across multiple scenarios. This demonstrates that the points system terminal provides a unified query service across multiple channels, improving the user experience.

[0159] Figure 9 A flowchart illustrating an order processing method according to another embodiment of the present disclosure is shown.

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

[0161] When operating the S910, in response to the user's points order tracing operation in the first scenario, a points order tracing request is sent to the points system terminal.

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

[0163] According to embodiments of this disclosure, the points system terminal can be configured with a unified data interaction format, meaning that the scenario party needs to send requests to the points system terminal according to the data interaction format configured by the points system terminal.

[0164] When operating the S920, after processing the order link corresponding to the second scenario in the points system terminal, the user is redirected from the points transaction flow view of the first scenario to the order details interface of the second scenario to view the order details of the user's points transaction in the second scenario.

[0165] Specifically, if the first authentication result indicates that the authentication is successful and the first scenario party has the authority to query the orders of 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 this disclosure, since the points system terminal provides a unified cross-platform order query authentication interface, there is no need for interaction between different scenario parties to support the viewing of points transaction order details between multiple scenario parties. It also supports users to trace transactions, so that the first scenario party can view the order details of the user's points transaction in the second scenario party. Furthermore, when the points system terminal receives a points order tracing request, the points system terminal first authenticates the first scenario party and determines whether the first scenario party has the permission to query the orders of the second scenario party to ensure the security of interactive communication.

[0167] According to embodiments of this disclosure, the order method further includes: in response to a user's points transaction operation at the scene, sending a points request corresponding to the type of points transaction operation to the points system terminal, so that the points system terminal processes the points request and sends the user's current points balance to the scene; and in response to the received current points balance of the user, displaying the user's current points balance in the scene.

[0168] Specifically, if the second authentication result indicates that the authentication is successful, the points system terminal processes the points request; the second authentication result is obtained by the points system terminal authenticating the scene party based on the scene party identifier and key in the points request.

[0169] According to embodiments of this disclosure, points transaction operations may include users redeeming points, making purchases, depositing funds, etc. Points transaction operations may include three types of points transactions: points consumption, points accumulation, and points consumption refunds. In other words, points requests may include points consumption requests, points accumulation requests, and points consumption refund requests.

[0170] The points request may include user identifier, scenario identifier, points rule identifier, points transaction type, and number of points generated.

[0171] According to embodiments of this disclosure, when a user performs a points accumulation transaction in a scenario, the points accumulation request may also include the reason for points generation, points expiration time, and a link to a points acquisition activity.

[0172] The number of points generated is the total points to be accumulated; the reasons for generating points can include user spending, depositing money, etc.

[0173] According to embodiments of this disclosure, when a user performs a points transaction at a venue, the points transaction request may also include the reason for the points transaction, the venue's order identifier, and a link to the venue's order details.

[0174] The number of points generated is the value of points to be consumed; reasons for consuming points can include redeeming points, using points to offset cash, etc.

[0175] According to embodiments of this disclosure, when a user performs a points transaction refund at a particular venue, the points refund request may also include the original consumption order identifier of the venue, the refund type, and a link to the venue's order details.

[0176] The number of points generated is the points value for refunds pending consumption, and the refund type can include full refund and partial refund.

[0177] According to embodiments of this disclosure, the scenario provider can also send a points details query request to the points system terminal. The points system terminal can then return the queried points transaction records, i.e., points details, to the scenario provider through the points details query interface. These points details can record the scenario provider identifier, scenario provider order identifier, and points acquisition activity link for each points transaction.

[0178] According to embodiments of this disclosure, the scenario provider can also freely choose whether to display details of the points breakdown, such as links to points acquisition activities.

[0179] According to embodiments of this disclosure, when a user conducts a points transaction at a location, the location sends a points request to the points system terminal. The points system terminal first authenticates the location to ensure secure communication. If authentication is successful, it processes the points request, such as accumulating, consuming, or refunding the user's current points balance, updating the points transaction history in the points account, and sending the user's current points balance to the location so that the location can visually display the current points balance to the user and indicate that the points request was successful.

[0180] Based on the above order processing method, this disclosure also provides an order processing apparatus. The following will be combined with... Figure 10 The device is described in detail.

[0181] Figure 10 The diagram illustrates a structural block diagram of an order processing apparatus applied to an points system terminal according to an embodiment of the present disclosure.

[0182] like Figure 10As shown, the order processing device 1000 applied to the points system terminal in 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 a points order tracing request received from a first scenario party, and to authenticate the first scenario party based on the scenario party identifier and key corresponding to the first scenario party in the points order tracing request, thereby obtaining a first authentication result. The points order tracing request represents viewing the order details of a user's points transaction in a second scenario party, and the first and second scenario parties 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 authentication has passed and the first scenario party has the permission to query the orders of the second scenario party. This allows the user 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 in the second scenario party. In one embodiment, the first processing module 1020 can be used to execute the operation S220 described above, which will not be repeated here.

[0185] According to embodiments of this disclosure, the order processing apparatus 1000 further includes an allocation module.

[0186] The allocation module is used to allocate a scene party identifier, an points rule identifier, and a key to at least one scene party connected to the points system terminal, wherein the scene party terminal includes multiple scene parties.

[0187] According to embodiments of this disclosure, the order processing device 1000 further includes a second authentication module and a second processing module.

[0188] The second authentication module is used to respond to a points request received from the scene party, and to authenticate the scene party based on 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 points request when the second authentication result indicates that the authentication is successful, so as to send the user's current points balance to the scenario party.

[0190] According to embodiments of this 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 points accumulation request based on the scenario identifier and points rule identifier in the points accumulation request, and obtain the first verification result.

[0192] The first execution unit is used to, upon verification that the first verification result indicates that the verification is successful, perform the points accumulation operation corresponding to the points accumulation request based on the points to be accumulated value in the points accumulation request, and obtain the user's current points balance.

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

[0194] According to embodiments of this 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 points consumption request based on the scenario identifier and points rule identifier in the points consumption request, and obtain the second verification result.

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

[0197] The second execution unit is used to execute the points consumption operation corresponding to the points consumption request based on the points to be consumed, when the comparison result indicates that the user's valid points value is greater than or equal to the points to be consumed, so as to obtain the user's current points balance.

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

[0199] According to embodiments of this 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 points consumption transaction records corresponding to the scenario party identifier and scenario party order identifier in the points consumption refund request under the points account corresponding to the user identifier in the points consumption refund request, and obtain the query results.

[0201] The third execution unit is used to execute the points refund operation corresponding to the points consumption refund request based on the points consumption refund value in the points consumption refund request, when the query result indicates that there are points consumption transactions corresponding to the scenario identifier and scenario order identifier under the points account, so as to obtain the user's current points balance.

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

[0203] According to embodiments of this 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 the received points details query request from the first scenario party, and to authenticate the first scenario party based on the scenario party identifier and key corresponding to the first scenario party in the points details query request, and obtain the third authentication result.

[0205] The first query module is used to retrieve the points transaction history of the user in the points account corresponding to the user identifier based on the user identifier in the points details query request, provided that the third authentication result indicates that the authentication has passed.

[0206] The second sending module is used to send the user's points transaction history to the first scenario party so that the user's points transaction history view can be displayed in the first scenario party.

[0207] According to embodiments of this disclosure, the order processing apparatus 1000 further includes a second query module and a third sending module.

[0208] The second query module is used to retrieve the points transaction history of the first scenario party corresponding to the scenario party under the points account corresponding to the user identifier and scenario party identifier in the points details query request, based on the user identifier and scenario party identifier in the points details query request.

[0209] The third sending module is used to send the points transaction records of the first scenario party to the first scenario party so as to display the points transaction record view of the first scenario party in the first scenario party. The points transaction record view of the first scenario party includes the points transaction records of users making points transactions in the first scenario party.

[0210] According to embodiments of this disclosure, any plurality of modules in the first authentication module 1010 and the first processing module 1020 can be combined into one module, or any one of the modules can be split into multiple modules. Alternatively, at least a portion of the functionality of one or more of these modules can be combined with at least a portion of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the first authentication module 1010 and the first processing module 1020 can be at least partially implemented as hardware circuitry, 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-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or implemented in any one of software, hardware, and firmware methods, or in a suitable combination of any of these. 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, which can perform corresponding functions when the computer program module is run.

[0211] Based on the above order processing method, this disclosure also provides an order processing apparatus. The following will be combined with... Figure 11 The device is described in detail.

[0212] Figure 11 The diagram illustrates a structural block diagram of an order processing device applied to a scenario terminal according to an embodiment of the present disclosure.

[0213] like Figure 11 As shown, the order processing device 1100 applied to the scene terminal in this embodiment includes a first sending module 1110 and a jump module 1120.

[0214] The first sending module 1110 is used to respond to a user's points order tracing operation in the first scenario by sending a points order tracing request to the points system terminal. The points order tracing request indicates that the user is viewing the order details of a points transaction conducted in the second scenario. The first and second scenarios are different scenarios within the scenario terminal. In one embodiment, the first sending module 1110 can be used to execute the operation S910 described above, which will not be repeated here.

[0215] The jump module 1120 is used 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 user's points transaction in the second scenario; wherein, if the first authentication result indicates that the authentication is successful and the first scenario party has the permission to query the orders of 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 according to the scenario party identifier and key corresponding to the first scenario party in the points order tracing request. In one embodiment, the jump module 1120 can be used to execute the operation S920 described above, which will not be repeated here.

[0216] According to embodiments of this disclosure, the order processing apparatus further includes a fourth sending module and a display module.

[0217] The fourth sending module is used to respond to the user's points transaction operation at the scene provider by sending a points request corresponding to the type of points transaction operation to the points system terminal, so that the points system terminal can process the points request and send the user's current points balance to the scene provider. Specifically, if the second authentication result indicates that the authentication is successful, the points system terminal processes the points request. The second authentication result is obtained by the points system terminal authenticating the scene provider based on the scene provider identifier and key in the points request.

[0218] The display module is used to respond to the received current points balance of the user and display the user's current points balance in the scene.

[0219] According to embodiments of this disclosure, any plurality of modules in the first transmitting module 1110 and the jump module 1120 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least a portion of the functionality of one or more of these modules can be combined with at least a portion of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the first transmitting module 1110 and the jump module 1120 can be at least partially implemented as hardware circuitry, 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-package, an application-specific integrated circuit (ASIC), or any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, at least one of the first transmitting module 1110 and the jump module 1120 can be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

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

[0221] like Figure 12 As shown, an 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 portion 1208 into 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 an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1201 may also include 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] RAM 1203 stores various programs and data required for the operation of electronic device 1200. Processor 1201, ROM 1202, and RAM 1203 are interconnected via bus 1204. Processor 1201 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 1202 and / or RAM 1203. It should be noted that the programs may also be stored in one or more memories other than ROM 1202 and RAM 1203. Processor 1201 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0223] According to embodiments of this disclosure, the electronic device 1200 may further include an input / output (I / O) interface 1205, which is also connected to a bus 1204. The electronic device 1200 may also include one or more of the following components connected to the input / output (I / O) interface 1205: an input section 1206 including a keyboard, mouse, etc.; an output section 1207 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1208 including a hard disk, etc.; and a communication section 1209 including a network interface card such as a LAN card, modem, etc. The communication section 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 disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 1210 as needed so that computer programs read from it can be installed into the storage section 1208 as needed.

[0224] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

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

[0226] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the order processing method provided in the embodiments of this disclosure.

[0227] When the computer program is executed by the processor 1201, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

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

[0229] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 1209, and / or installed from the removable medium 1211. When the computer program is executed by the processor 1201, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0230] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on a user's computing device, partially on a user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0231] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0232] Those skilled in the art will understand that the features described in the various embodiments of this disclosure can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments of this disclosure can be combined and / or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0233] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. An order processing method applied to a points system terminal, characterized in that, The method includes: In response to receiving a points order tracing request from a first scenario provider, the system authenticates the first scenario provider based on the scenario provider identifier and key corresponding to the first scenario provider in the points order tracing request, obtaining a first authentication result. The points order tracing request represents viewing the order details of a user's points transaction in a second scenario provider, and the first and second scenario providers are different scenario providers within the scenario provider terminal. If the first authentication result indicates that the authentication is successful and the first scenario party has the permission to query the orders of 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 in the second scenario party; At least one scenario party connected to the points system terminal is assigned a scenario party identifier, points rule identifier, and key, wherein the scenario party terminal includes multiple scenario parties.

2. The method according to claim 1, further comprising: In response to receiving a points request from the scene party, the scene party is authenticated based on the scene party identifier and key in the points request, and a second authentication result is obtained; If the second authentication result indicates that the authentication is successful, the points request is processed to send the user's current points balance to the scenario party.

3. The method according to claim 2, characterized in that, When the points request is a points accumulation request, processing the points request to send the user's current points balance to the scenario provider includes: Based on the scenario identifier and the points accumulation rule identifier in the points accumulation request, the points accumulation request is verified to obtain a first verification result; If the first verification result indicates that the verification is successful, the user's current points balance is obtained by performing the points accumulation operation corresponding to the points accumulation request based on the points to be accumulated value in the points accumulation request. Under the points account corresponding to the user identifier in the points accumulation request, record the points accumulation flow corresponding to the points accumulation request, and send the user's current points balance to the scenario party, wherein the points accumulation flow includes the user's current points balance.

4. The method according to claim 2, characterized in that, When the points request is a points consumption request, processing the points request to send the user's current points balance to the scenario provider includes: Based on the scenario identifier and points rule identifier in the points consumption request, the points consumption request is verified to obtain a second verification result; If the second verification result indicates that the verification is successful, the value of points to be consumed in the points consumption request is compared with the user's valid points value to obtain a comparison result. The user's valid points value represents the current points balance of the user under the points account corresponding to the user identifier in the points consumption request. If the comparison result indicates that the user's valid points value is greater than or equal to the points value to be consumed, then the points consumption operation corresponding to the points consumption request is executed according to the points value to be consumed, and the user's current points balance is obtained. Under the points account corresponding to the user identifier, the points consumption transaction record corresponding to the points consumption request is recorded, and the user's current points balance is sent to the scenario party, wherein the points consumption transaction record includes the user's current points balance.

5. The method according to claim 2, characterized in that, In the case that the points request is a points consumption refund request, the step of processing the points request to send the user's current points balance to the scenario party includes: Under the points account corresponding to the user identifier in the points consumption refund request, query the points consumption transaction records corresponding to the scenario party identifier and scenario party order identifier in the points consumption refund request to obtain the query results; If the query result indicates that there is a points consumption transaction record corresponding to the scenario party identifier and the scenario party order identifier under the points account, then according to the points to be refunded value in the points consumption refund request, the points refund operation corresponding to the points consumption refund request is executed to obtain the user's current points balance; Under the points account corresponding to the user identifier, record the points consumption refund transaction corresponding to the points consumption refund request, and send the user's current points balance to the scenario party, wherein the points consumption refund transaction includes the user's current points balance.

6. The method according to claim 1, further comprising: In response to receiving a points details query request from the first scenario party, the first scenario party is authenticated based on the scenario party identifier and key corresponding to the first scenario party in the points details query request, and a third authentication result is obtained. If the third authentication result indicates that the authentication is successful, the points transaction history of the user in the points account corresponding to the user identifier can be retrieved according to the user identifier in the points details query request. Send the user's points transaction history to the first scenario provider so that the user's points transaction history view can be displayed in the first scenario provider.

7. The method according to claim 6, further comprising: If the third authentication result indicates successful authentication, based on the user identifier and scenario provider identifier in the points details query request, the points transaction history of the first scenario provider corresponding to the scenario provider identifier is retrieved under the points account corresponding to the user identifier; and Send the points transaction history of the first scenario to the first scenario party to display the points transaction history view of the first scenario party in the first scenario party, wherein the points transaction history view of the first scenario party includes the points transaction history of the user's points transactions in the first scenario party.

8. An order processing method, characterized in that, The method includes: In response to a user's points order tracing operation in the first scenario, a points order tracing request is sent to the points system terminal. This request indicates the intention to view the order details of the user's points transaction in the second scenario, where the first and second scenarios are different scenarios within the scenario terminal. 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; Wherein, if the first authentication result indicates that the authentication is successful and the first scenario party has the permission to query the order of 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.

9. The method according to claim 8, further comprising: In response to the user's points transaction operation at the scene provider, a points request corresponding to the type of the points transaction operation is sent to the points system terminal, so that the points system terminal processes the points request and sends the user's current points balance to the scene provider. Specifically, if the second authentication result indicates successful authentication, the points system terminal processes the points request; the second authentication result is obtained by the points system terminal authenticating the scene provider based on the scene provider identifier and key in the points request. In response to the received current points balance of the user, the current points balance of the user is displayed in the scenario.

10. An order processing device, characterized in that, The device includes: The 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 based on the scenario party identifier and key corresponding to the first scenario party in the points order tracing request, and obtain a first authentication result. The points order tracing request represents viewing the order details of a user's points transaction in a second scenario party, and the first and second scenario parties are different scenario parties within the scenario party terminal. 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 permission to query the order of the second scenario party, 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 in the second scenario party; At least one scenario party connected to the order processing device is assigned a scenario party identifier, points rule identifier, and key, wherein the scenario party terminal includes multiple scenario parties, and the order processing device is set in the points system terminal.

11. An order processing device, characterized in that, The device includes: The first sending module is configured to, in response to a user's points order tracing operation in a first scenario, send a points order tracing request to the points system terminal, wherein the points order tracing request represents viewing the order details of the user's points transaction in a second scenario, and the first scenario and the second scenario are different scenario parties in the scenario party terminal; and The jump module is used 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 user's points transaction in the second scenario. Wherein, if the first authentication result indicates that the authentication is successful and the first scenario party has the permission to query the order of 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.

12. An electronic device, comprising: One or more processors; Memory, used to store one or more computer programs. The characteristic feature is 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 7 or 8 to 9.

13. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7 or 8 to 9.

14. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7 or 8 to 9.

Images