Financial product reservation processing method and device, computer equipment and storage medium

Abstract

The invention relates to a financial product reservation processing method and device, computer equipment, a storage medium and a computer program product. The method comprises the following steps: receiving a reservation request of a financial product, and obtaining reservation request information and a request terminal identifier; determining whether historical reservation information corresponding to the request terminal identifier exists according to the request terminal identifier; if the historical reservation information exists, performing reservation risk detection on the request terminal and the reservation request information based on the historical reservation information and the reservation request information; and when neither the request terminal nor the reservation request information has the reservation risk, calling a task processing thread to process the reservation task according to the reservation request. By adopting the method, the cheating behavior of financial product reservation can be effectively prevented, and the fairness of the financial product issuing process is improved.

Description

Technical Field

[0001] The present application relates to the technical field of financial data processing, and in particular to a method, apparatus, computer equipment, storage medium and computer program product for processing a reservation of a financial product. Background Art

[0002] In order to take into account the collection and use needs of users, banks and other financial institutions will regularly issue some financial products for users to collect or exchange, such as commemorative coins and banknotes. Before the official issuance, financial institutions usually open a reservation channel for users to make reservations for financial products, and then issue corresponding financial products to users based on the reservation results.

[0003] With the popularity of online reservation channels and the increasing number of financial products issued each year, users' enthusiasm for booking financial products has also increased year by year. Often, some popular financial products will be sold out in the first few minutes of issuance. However, due to the operability of online reservations, some users will use technical cheating methods such as batch scripts to make reservations in order to obtain more financial products. This is an unfair phenomenon and may also have a negative impact on the reputation of financial product issuers. Summary of the invention

[0004] Based on this, it is necessary to provide a financial product reservation processing method, device, computer equipment, computer-readable storage medium and computer program product that can effectively prevent cheating in financial product reservations and improve the fairness of the financial product issuance process in response to the above-mentioned technical problems.

[0005] In a first aspect, the present application provides a method for processing a financial product reservation, the method comprising:

[0006] Receive a reservation request for a financial product, and obtain reservation request information and a request terminal identifier;

[0007] determining, according to the requesting terminal identifier, whether there is historical reservation information corresponding to the requesting terminal identifier;

[0008] If the historical reservation information exists, performing reservation risk detection on the requesting terminal and the reservation request information based on the historical reservation information and the reservation request information;

[0009] When there is no reservation risk between the request terminal and the reservation request information, a task processing thread is called to process the reservation task according to the reservation request.

[0010] In one embodiment, the performing reservation risk detection on the request terminal and the reservation request information based on the historical reservation information and the reservation request information includes:

[0011] Based on the reservation request information and the historical reservation information, acquiring the request generation time of the reservation request information and the historical reservation time of the historical reservation information;

[0012] Performing reservation risk detection on the requesting terminal according to the request generation time and the historical reservation time;

[0013] Acquire a reservation withdrawal point for the financial product based on the reservation request information;

[0014] The reservation risk detection is performed on the reservation request information according to the reservation extraction point.

[0015] In one embodiment, performing reservation risk detection on the requesting terminal according to the request generation time and the historical reservation time includes:

[0016] Compare the request generation time with the historical reservation time to obtain a reservation time difference;

[0017] When the reservation time difference is less than a preset time difference threshold, it is determined that the requesting terminal has a reservation risk.

[0018] In one embodiment, performing appointment risk detection on the appointment request information according to the appointment extraction point includes:

[0019] Determining, according to the reservation request information, a user identifier of a target user generating the reservation request;

[0020] Acquire the target business handling point preset by the target user based on the user identifier;

[0021] Matching the appointment pick-up point with the target business handling point;

[0022] If the matching is unsuccessful, it is determined that the reservation request information has a reservation risk.

[0023] In one embodiment, the method further comprises:

[0024] When there is a reservation risk at the requesting terminal, determining that the reservation request is not approved;

[0025] Call the task processing thread to generate and push request failure prompt information.

[0026] In one embodiment, the method further comprises:

[0027] When there is no reservation risk at the requesting terminal and there is a reservation risk at the reservation request information, calling the identity verification thread to obtain a preset verification method of the target user corresponding to the reservation request;

[0028] Performing identity authentication on the reservation user based on the preset verification method;

[0029] When the identity authentication is successful, the task processing thread is called to process the reservation task according to the reservation request.

[0030] In a second aspect, the present application further provides a financial product reservation processing device, the device comprising:

[0031] A request response module, used to respond to a reservation request for a financial product and obtain reservation request information and a request terminal identifier;

[0032] A historical reservation information determination module, used to determine whether there is historical reservation information corresponding to the requesting terminal identifier according to the requesting terminal identifier;

[0033] a risk detection module, configured to perform a reservation risk detection on the request terminal and the reservation request information based on the historical reservation information and the reservation request information if the historical reservation information exists;

[0034] The reservation request processing module is used to call the task processing thread to process the reservation task according to the reservation request when there is no reservation risk between the request terminal and the reservation request information.

[0035] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.

[0036] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the steps of the above method when executed by a processor.

[0037] In a fifth aspect, the present application also provides a computer program product, including a computer program, which implements the steps of the above method when executed by a processor.

[0038] The above-mentioned financial product reservation processing method, device, computer equipment, storage medium and computer program product, when a user has a financial product reservation demand, receives a financial product reservation request, obtains reservation request information and a request terminal identifier, and determines whether there is historical reservation information corresponding to the request terminal identifier based on the request terminal identifier. If so, it means that the request terminal has previously made a reservation for the financial product and there is a possibility of repeated reservations. It is necessary to perform reservation risk detection on the request terminal and the reservation request information based on the historical reservation information and the current reservation request information. Only when there is no reservation risk on the request terminal and the reservation request information can the task processing thread be called to process the reservation task according to the reservation request. By performing reservation risk detection on the two dimensions of the request terminal and the reservation request information, it is possible to effectively prevent cheating in financial product reservations and improve the fairness of the financial product issuance process. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 An application environment diagram of a method for processing a reservation for a financial product in one embodiment;

[0040] Figure 2 It is a flowchart of a method for processing a reservation of a financial product in one embodiment;

[0041] Figure 3 A flowchart of a step of performing reservation risk detection on a requesting terminal and reservation request information based on historical reservation information and reservation request information in an embodiment;

[0042] Figure 4 It is a flowchart of a step of performing reservation risk detection on reservation request information according to a reservation extraction point in one embodiment;

[0043] Figure 5 A flowchart of a method for processing a financial product reservation in another embodiment;

[0044] Figure 6 A flowchart of a method for processing a financial product reservation in another embodiment;

[0045] Figure 7 It is a structural block diagram of a financial product reservation processing device in one embodiment;

[0046] Figure 8 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0047] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0048] The financial product reservation processing method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the reservation processing system 102 communicates with the request terminal 104 through the network. The data storage system can store the data that the reservation processing system 102 needs to process. The data storage system can be integrated on the reservation processing system 102, or it can be placed on the cloud or other network servers. The request terminal 104 generates a reservation request for the financial product based on the triggered financial product reservation event, and sends the reservation request for the financial product to the reservation processing system 102. The reservation processing system 102 responds to the reservation request for the financial product, obtains the reservation request information and the request terminal identifier, and determines whether there is historical reservation information corresponding to the request terminal identifier according to the request terminal identifier. If there is historical reservation information, the request terminal 104 and the reservation request information are detected for reservation risk based on the historical reservation information and the reservation request information. When there is no reservation risk for both the request terminal 104 and the reservation request information, the task processing thread is called to process the reservation task according to the reservation request. Among them, the request terminal 104 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers and portable wearable devices, and the portable wearable devices can be smart watches, smart bracelets, etc. The reservation processing system 102 may be integrated on a server, and the server may be implemented as an independent server or a server cluster consisting of multiple servers.

[0049] In one embodiment, Figure 2 As shown, a financial product reservation processing method is provided, and the method is applied to Figure 1 Taking the reservation processing system 102 in FIG. 1 as an example, the following steps are included:

[0050] S202, receiving a reservation request for a financial product, and obtaining reservation request information and a request terminal identifier.

[0051] Among them, financial products refer to products issued by banks to meet the collection and use needs of users, such as commemorative coins and banknotes issued by banks. The reservation request for financial products is a request for a designated user to make an appointment to receive a financial product based on the bank's business service system. Before the bank officially issues a financial product, it will open a reservation channel for designated users who meet the conditions for receiving the financial product. The designated user triggers a financial product reservation event based on the request terminal, which can generate a reservation request for the financial product, and send the reservation request to the reservation processing system through the request terminal for processing.

[0052] In one of the embodiments, a designated user inputs corresponding reservation information through a reservation channel and clicks "confirm" to trigger a financial product reservation event and generate a reservation request for the financial product.

[0053] The reservation request information is request information used to reflect the user's reservation needs, and the reservation request information may include the reservation information input by the designated user through the reservation channel, such as user information and reserved financial product information, etc. It may also include environmental information when the reservation request is generated, such as the time when the reservation request is generated.

[0054] The request terminal identifier is a unique identifier for marking the request terminal. Each request terminal has its own terminal identifier, and the request terminal that generates the reservation request information can be determined by the request terminal identifier. It can be understood that the request terminal identifier can be the terminal IP of the request terminal.

[0055] Specifically, the requesting terminal generates a reservation request for the financial product based on the triggered financial product reservation event, and sends the reservation request to the bank's reservation processing system, where the reservation request carries reservation request information and a requesting terminal identifier. The reservation processing system receives the reservation request for the financial product and obtains the reservation request information and the requesting terminal identifier carried in the reservation request.

[0056] S204: Determine, according to the requesting terminal identifier, whether there is historical reservation information corresponding to the requesting terminal identifier.

[0057] Among them, historical reservation information refers to the reservation information generated after the reservation of a financial product is made through the request terminal and the reservation is successfully made. The historical reservation information may include user information, reserved financial product information, and environmental information when the reservation is successful, such as the historical reservation time when the reservation is successful.

[0058] Specifically, the reservation processing system searches for reservation information in a reservation information repository according to the requesting terminal identifier to determine whether there is historical reservation information corresponding to the requesting terminal identifier.

[0059] S206: If there is historical reservation information, a reservation risk detection is performed on the requesting terminal and the reservation request information based on the historical reservation information and the reservation request information.

[0060] Specifically, if the reservation processing system finds historical reservation information corresponding to the requesting terminal identifier in the reservation information repository, it means that the requesting terminal has previously successfully made a reservation for a financial product for a designated user, and there is a duplicate reservation behavior. The reservation processing system will perform a reservation risk detection on the requesting terminal and the reservation request information based on the historical reservation information and the current reservation request information to determine whether the requesting terminal and the reservation request information have reservation risks.

[0061] In one of the embodiments, the reservation processing system may be pre-configured with a reservation risk assessment model. After determining that the requesting terminal has repeated reservation behavior, the reservation processing system may input the acquired historical reservation information and the current reservation request information into the reservation risk assessment model to perform a reservation risk detection and obtain the risk detection results of the requesting terminal and the reservation request information.

[0062] S208: When there is no reservation risk for the requesting terminal and the reservation request information, a task processing thread is called to process the reservation task according to the reservation request.

[0063] The task processing thread is a processing thread for processing the corresponding reservation task according to the reservation request. The task processing thread can lock the corresponding financial product for the target user corresponding to the reservation request according to the reservation request and complete the reservation of the financial product.

[0064] Specifically, if the reservation processing system determines that there is no reservation risk for both the requesting terminal and the reservation request information, it means that although the requesting terminal has repeated reservation behavior, this behavior is reasonable, for example, different users use the same terminal to make reservations for financial products, and there is no reservation cheating behavior, so the reservation can be made. The reservation processing system writes the reservation request into the task pool of the task processing thread, and calls the task processing thread to process the reservation task according to the reservation request.

[0065] In the above-mentioned financial product reservation processing method, when a user has a need for a financial product reservation, a reservation request for the financial product is received, the reservation request information and the request terminal identifier are obtained, and it is determined whether there is historical reservation information corresponding to the request terminal identifier based on the request terminal identifier. If so, it means that the request terminal has previously made reservations for financial products and there is a possibility of repeated reservations. It is necessary to perform reservation risk detection on the request terminal and the reservation request information based on the historical reservation information and the current reservation request information. Only when there is no reservation risk on the request terminal and the reservation request information can the task processing thread be called to process the reservation task according to the reservation request. By performing reservation risk detection on the two dimensions of the request terminal and the reservation request information, cheating in financial product reservations can be effectively prevented and the fairness of the financial product issuance process can be improved.

[0066] In one embodiment, Figure 3 As shown, based on the historical reservation information and the reservation request information, performing reservation risk detection on the requesting terminal and the reservation request information includes:

[0067] S302: Based on the reservation request information and the historical reservation information, obtain the request generation time of the reservation request information and the historical reservation time of the historical reservation information.

[0068] Specifically, the reservation processing system obtains the request generation time of the reservation request information from the reservation request information, and obtains the historical reservation time of the historical reservation information from the historical reservation information summary, that is, the reservation time when the historical reservation is successful.

[0069] S304: Perform reservation risk detection on the requesting terminal according to the request generation time and the historical reservation time.

[0070] Specifically, when making a reservation for a financial product, if the same request terminal is used to make reservations for different users, the normal reservation process for a financial product will inevitably involve the process of re-entering user information, which takes a certain amount of time. If it is an abnormal reservation process for a financial product, that is, a reservation process made through technical cheating means such as batch scripts, the time used will definitely be different from the normal reservation process. Therefore, the reservation processing system can perform reservation risk detection on the request terminal based on the request generation time and the historical reservation time, so as to avoid cheating users making reservations for financial products through technical cheating means such as batch scripts, thereby reducing the fairness of the financial product issuance process.

[0071] In one embodiment, performing reservation risk detection on the requesting terminal according to the request generation time and the historical reservation time includes: comparing the request generation time with the historical reservation time to obtain a reservation time difference. When the reservation time difference is less than a preset time difference threshold, it is determined that the requesting terminal has a reservation risk.

[0072] Specifically, after obtaining the request generation time of the reservation request information and the historical reservation time of the historical reservation information, the reservation processing system compares the request generation time with the historical reservation time, and calculates the reservation time difference between the request generation time and the historical reservation time. Subsequently, the pre-configured preset time difference threshold is called, and the reservation time difference is compared with the preset time difference threshold. When the reservation time difference is less than the preset time difference threshold, it can be considered that there is a financial product reservation cheating behavior on the requesting terminal at this time, and it is determined that the requesting terminal has a reservation risk.

[0073] It can be understood that the preset time difference threshold is a time difference parameter used to determine whether the current financial product reservation is a normal reservation. The preset time difference threshold can be determined by the designer in advance according to the minimum time required to switch users to make reservations during the normal financial product reservation process. For example, if a financial product reservation is made on the same request terminal, the minimum time from the last user completing the reservation to switching to the next user to regenerate the financial product reservation request is 30 seconds, then 30 seconds can be determined as the preset time difference threshold. If the reservation time difference between the request generation time and the historical reservation time calculated by the reservation processing system is less than the preset time difference threshold, it means that the request terminal may be using technical cheating methods such as batch scripts to make reservations at this time, and there is cheating in financial product reservations.

[0074] S306: Obtain a reservation withdrawal point for the financial product based on the reservation request information.

[0075] The appointment pick-up point is the offline product pick-up point where users who have successfully made an appointment can obtain financial products. For example, if a user completes an appointment for a financial product that is about to be issued by a bank through an appointment channel, when the financial product is issued, the user can obtain the financial product that has been successfully reserved offline at the appointment pick-up point determined during the appointment.

[0076] Specifically, the reservation processing system may obtain, from the reservation request information, the reservation pick-up point of the financial product input or selected by the user when making a reservation for the financial product.

[0077] S308: Perform reservation risk detection on the reservation request information according to the reservation extraction point.

[0078] Specifically, since the target of financial product issuance is generally designated users of the bank, such as users whose user level in the bank reaches a preset level, if a cheating user performs a cheating operation of financial product reservation based on the request terminal, it is necessary to obtain the user information of multiple designated users to make reservations for financial products. In order to facilitate the acquisition of the reserved financial products, the cheating user usually chooses the same reservation withdrawal point, which is convenient for the cheating user to withdraw offline at the same time. Therefore, the reservation processing system can perform reservation risk detection on the reservation request information according to the reservation withdrawal point to avoid the situation where the cheating user makes repeated reservations by stealing the designated user information, thereby reducing the fairness of the financial product issuance process.

[0079] In one embodiment, if Figure 4 As shown, performing appointment risk detection on the appointment request information according to the appointment extraction point includes:

[0080] S402: Determine the user ID of the target user who generates the reservation request according to the reservation request information.

[0081] The target user refers to the designated user corresponding to the user information used when generating the reservation request. It is understandable that when making a normal reservation for a financial product, the target user is the reservation user who performs the reservation operation. When making an abnormal reservation for a financial product, the target user is not necessarily the reservation user who performs the reservation operation, and the reservation user may be a cheating user who performs reservation cheating.

[0082] Specifically, the reservation processing system obtains the user identification of the target user who generates the reservation request from the user information included in the reservation request information according to the reservation request information. It can be understood that the user identification can be a user account, a user name, etc.

[0083] S404, obtaining the target business handling point pre-set by the target user based on the user identifier.

[0084] The target business handling point is a target business handling point that the target user sets in advance based on his / her usage habits. When opening a user account, the target user can set one or more target business handling points based on his / her usage habits. For example, the target user can select the nearest offline bank branch as the target business handling point based on the residential area and work area.

[0085] Specifically, the reservation processing system obtains personalized information of the target user according to the user identifier, and obtains the target business handling point pre-set by the target user from the personalized information.

[0086] S406, matching the scheduled pickup point with the target business handling point.

[0087] Specifically, the appointment processing system matches the appointment pickup point with the target business handling point.

[0088] S408: If the match is unsuccessful, it is determined that the reservation request information has a reservation risk.

[0089] Specifically, if the target user has only one target service point pre-set, this target service point is matched with the reservation extraction point. When the target service point is consistent with the reservation extraction point, it means that the reservation request information at this time does not have a reservation risk, and the reservation request is a reservation request generated by the target user himself performing a normal reservation operation for a financial product. When the target service point is inconsistent with the reservation extraction point, it is determined that the match is unsuccessful, indicating that the reservation request information at this time has a reservation risk, and the reservation request may be a reservation request generated by a cheating user performing an abnormal reservation operation for a financial product.

[0090] If the target user has pre-set multiple target business handling points, the multiple target business handling points will be matched with the appointment pickup point. When there is a business handling point that is consistent with the appointment pickup point among the multiple target business handling points, it means that the appointment request information at this time does not have an appointment risk, and the appointment request is an appointment request generated by the target user himself performing a normal appointment operation for a financial product. When there is no business handling point that is consistent with the appointment pickup point among the multiple target business handling points, it is determined that the match is unsuccessful, indicating that there is an appointment risk in the appointment request information at this time, and the appointment request may be an appointment request generated by a cheating user performing an abnormal appointment operation for a financial product.

[0091] In the above embodiment, by performing appointment risk detection on two dimensions, namely, the request terminal and the appointment request information, it is possible to timely determine whether there is any cheating in the appointment of financial products based on the acquired appointment information, thereby providing a data basis for effectively preventing cheating in the appointment of financial products and improving the fairness of the financial product issuance process.

[0092] In one embodiment, the financial product reservation processing method further includes: when there is a reservation risk in the requesting terminal, determining that the reservation request is not approved, calling the task processing thread to generate and push request failure prompt information.

[0093] Specifically, when the reservation processing system determines that the requesting terminal has a reservation risk, it means that the financial product reservation request at this time is a reservation request generated by a cheating user through technical cheating means such as batch scripts. In order to ensure the fairness of the financial product issuance process, the reservation processing system directly determines that the reservation request is not passed, writes the reservation request into the failed task processing task pool of the task processing thread, calls the task processing thread to generate a request failure prompt message according to the reservation request, and sends the request failure prompt message to the requesting terminal for display to the user. Among them, the request failure prompt message is used to remind the user that there is a risk in the current reservation process and the request is not passed.

[0094] In this embodiment, when it is determined that the requesting terminal has a reservation risk, the reservation processing system can directly determine that the reservation request is not approved, effectively preventing cheating users from making reservations for financial products through technical cheating means such as batch scripts, thereby improving the fairness of the financial product issuance process.

[0095] In one embodiment, Figure 5 As shown, the financial product reservation processing method also includes:

[0096] S502: When there is no reservation risk in the requesting terminal and there is a reservation risk in the reservation request information, an identity verification thread is called to obtain a preset verification method of a target user corresponding to the reservation request.

[0097] The identity verification thread is a processing thread used to execute identity verification tasks and complete the identity verification process of the user to be verified.

[0098] The preset verification method is a verification method that the target user sets in advance according to the verification method that is convenient for him / her. When opening a user account, the target user can set one or more verification methods according to the verification method that is convenient for him / her, such as fingerprint verification, SMS verification, password verification, etc. It is understandable that when the target user sets multiple verification methods, the verification order can be set for multiple verification methods at the same time, and the reservation processing system can use the corresponding verification method according to the verification order to complete the identity verification of the target user later.

[0099] Specifically, when the reservation processing system determines that the requesting terminal does not have a reservation risk, but the reservation request information does have a reservation risk, it can be considered that the reservation request at this time is not obtained through technical cheating means such as batch scripts, but may be generated by a cheating user who steals the user information of a designated user to make a reservation. Therefore, the reservation processing system needs to verify the user identity of the current reservation user. The reservation processing system writes the identity verification task into the task pool of the identity verification thread, calls the identity verification thread to obtain the personalized setting information of the target user corresponding to the reservation request, and obtains the preset verification method of the target user from the personalized setting information.

[0100] S504: Authentication of the reservation user is performed based on a preset verification method.

[0101] Specifically, the identity authentication thread can authenticate the reservation user based on a preset verification method. For example, if the preset verification method is password verification, the identity authentication thread can generate a password entry page, display the password entry page on the request terminal, and in response to the password input operation of the request terminal, obtain the password entered by the current reservation user, match the entered password with the preset password of the target user, and authenticate the reservation user. It can be understood that the reservation user is the user who currently performs the reservation operation.

[0102] S506: When the identity authentication is successful, the task processing thread is called to process the reservation task according to the reservation request.

[0103] Specifically, when identity authentication is successful, it means that the reservation user who performs the reservation operation at this time is the target user, and the reservation process of generating a financial product reservation request is a normal reservation process. There is no situation where a cheating user makes a reservation by stealing the user information of a designated user. The reservation processing system writes the reservation request into the task pool of the task processing thread, and calls the task processing thread to process the reservation task according to the reservation request.

[0104] In one embodiment, when identity authentication fails, the reservation processing system determines that the reservation request is not approved, writes the reservation request into the failed task processing task pool of the task processing thread, calls the task processing thread to generate a request failure prompt message according to the reservation request, and sends the request failure prompt message to the request terminal to display it to the user. The request failure prompt message is used to prompt the user that there is a risk in the current reservation process and the request is not approved.

[0105] In the above embodiment, when it is determined that the appointment request is not obtained through technical cheating means such as batch scripts, but may be generated by a cheating user who steals the user information of a designated user to make an appointment, the appointment processing system can verify the identity of the appointment user through the verification method pre-set by the target user, and only call the task processing thread to process the appointment task when the identity verification is successful, which can effectively prevent cheating in financial product appointments and improve the fairness of the financial product issuance process.

[0106] In one embodiment, Figure 6 As shown, a method for processing a financial product reservation is provided, and the method is described by taking the application of the method in a bank commemorative coin reservation scenario as an example. The method specifically includes the following steps:

[0107] The reservation user logs in to the reservation channel opened by the bank through the request terminal, fills in the relevant reservation information, and generates a reservation request for the commemorative coins. The request terminal sends the reservation request for the commemorative coins to the reservation processing system.

[0108] The reservation processing system receives a reservation request for commemorative coins, obtains reservation request information and the requesting terminal IP from the reservation request, searches for reservation information in a reservation information repository based on the requesting terminal IP, and determines whether there is historical reservation information corresponding to the requesting terminal IP.

[0109] If there is historical reservation information corresponding to the IP of the requesting terminal, the historical reservation time of the historical reservation information is obtained, that is, the reservation time when the historical reservation is successful. At the same time, the request generation time of the reservation request information is obtained from the reservation request information, the reservation time difference between the request generation time and the historical reservation time is calculated, and the reservation time difference is compared with the preset time difference threshold. When the reservation time difference is less than the preset time difference threshold, it can be considered that the commemorative coin reservation request at this time is a reservation request generated by a cheating user through technical cheating means such as batch scripts, and it is determined that the requesting terminal has a reservation risk. The reservation processing system directly determines that the reservation request is not passed, writes the reservation request into the failed task processing task pool of the task processing thread, calls the task processing thread to generate a request failure prompt message according to the reservation request, and sends the request failure prompt message to the requesting terminal for display to the user. Among them, the request failure prompt message is used to remind the user that there is a risk in the current reservation process and the request is not passed.

[0110] When the reservation time difference is greater than or equal to the preset time difference threshold, it can be considered that the commemorative coin reservation operation performed by the requesting terminal at this time is a normal operation, and it is determined that there is no reservation risk for the requesting terminal. The reservation processing system obtains the reservation extraction point of the commemorative coin input or selected by the user when making a commemorative coin reservation from the reservation request information, and at the same time, according to the reservation request information, obtains the user ID of the target user who generates the reservation request from the user information contained in the reservation request information. According to the user ID, the personalized information of the target user is obtained, and the target business handling point pre-set by the target user is obtained from the personalized information.

[0111] The reservation extraction point is matched with the target business handling point. If there is a target business handling point that matches the reservation extraction point, it means that the reservation request information at this time does not have a reservation risk, and the reservation request is a reservation request generated by the target user performing a normal reservation operation for commemorative coins. The reservation processing system writes the reservation request into the task pool of the task processing thread and calls the task processing thread to process the reservation task according to the reservation request.

[0112] If there is no target business handling point that matches the reservation pick-up point, it is determined that the match is unsuccessful, indicating that there is a reservation risk in the reservation request information at this time, and the reservation request may be a reservation request generated by a cheating user performing an abnormal reservation operation for commemorative coins. The reservation processing system needs to verify the user identity of the current reservation user. The reservation processing system writes the identity verification task into the task pool of the identity verification thread, calls the identity verification thread to obtain the personalized setting information of the target user corresponding to the reservation request, and obtains the preset verification method of the target user from the personalized setting information.

[0113] The identity authentication thread can authenticate the reservation user based on the preset verification method. When the identity authentication is successful, it means that the reservation user who performs the reservation operation at this time is the target user, and the reservation process of generating the commemorative coin reservation request is a normal reservation process. There is no cheating user who makes a reservation by stealing the user information of the designated user. The reservation processing system writes the reservation request into the task pool of the task processing thread and calls the task processing thread to process the reservation task according to the reservation request.

[0114] When identity authentication fails, the reservation processing system determines that the reservation request is not approved, writes the reservation request into the failed task processing task pool of the task processing thread, calls the task processing thread to generate a request failure prompt message according to the reservation request, and sends the request failure prompt message to the request terminal to display it to the user. Among them, the request failure prompt message is used to remind the user that there is a risk in the current reservation process and the request is not approved.

[0115] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0116] Based on the same inventive concept, the embodiment of the present application also provides a financial product reservation processing device for implementing the above-mentioned financial product reservation processing method. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above-mentioned method, so the specific limitations in one or more financial product reservation processing device embodiments provided below can refer to the limitations of the financial product reservation processing method above, and will not be repeated here.

[0117] In one embodiment, Figure 7 As shown, a financial product reservation processing device 700 is provided, comprising: a request response module 701, a historical reservation information determination module 702, a risk detection module 703 and a reservation request processing module 704, wherein:

[0118] The request response module 701 is used to respond to a reservation request for a financial product and obtain reservation request information and a request terminal identifier.

[0119] The historical reservation information determining module 702 is used to determine whether there is historical reservation information corresponding to the requesting terminal identifier according to the requesting terminal identifier.

[0120] The risk detection module 703 is configured to perform a reservation risk detection on the request terminal and the reservation request information based on the historical reservation information and the reservation request information if the historical reservation information exists.

[0121] The reservation request processing module 704 is used to call a task processing thread to process a reservation task according to the reservation request when there is no reservation risk between the request terminal and the reservation request information.

[0122] The above-mentioned financial product reservation processing device receives a reservation request for a financial product when a user has a need to make a reservation for a financial product, obtains the reservation request information and the request terminal identifier, and determines whether there is historical reservation information corresponding to the request terminal identifier based on the request terminal identifier. If so, it means that the request terminal has made a reservation for a financial product before, and there is a possibility of repeated reservations. It is necessary to perform a reservation risk detection on the request terminal and the reservation request information based on the historical reservation information and the current reservation request information. Only when there is no reservation risk on the request terminal and the reservation request information can the task processing thread be called to process the reservation task according to the reservation request. By performing reservation risk detection on the two dimensions of the request terminal and the reservation request information, it is possible to effectively prevent cheating in financial product reservations and improve the fairness of the financial product issuance process.

[0123] In one embodiment, the risk detection module is also used to: obtain the request generation time of the appointment request information and the historical appointment information based on the appointment request information and the historical appointment information; perform an appointment risk detection on the request terminal according to the request generation time and the historical appointment time; obtain the appointment withdrawal point of the financial product based on the appointment request information; and perform an appointment risk detection on the appointment request information according to the appointment withdrawal point.

[0124] In one embodiment, the risk detection module is further used to: compare the request generation time with the historical reservation time to obtain a reservation time difference; when the reservation time difference is less than a preset time difference threshold, determine that the requesting terminal has a reservation risk.

[0125] In one embodiment, the risk detection module is also used to: determine the user identifier of the target user who generates the appointment request based on the appointment request information; obtain the target business processing point pre-set by the target user based on the user identifier; match the appointment pickup point with the target business processing point; if the match is unsuccessful, determine that the appointment request information has an appointment risk.

[0126] In one embodiment, the financial product reservation processing device further includes:

[0127] The prompt module is used to determine that the reservation request is not passed when there is a reservation risk in the requesting terminal; call the task processing thread to generate and push the request failure prompt information.

[0128] In one embodiment, the financial product reservation processing device further includes:

[0129] The identity authentication module is used to call the identity verification thread to obtain the preset verification method of the target user corresponding to the reservation request when there is no reservation risk at the requesting terminal and the reservation request information has reservation risk; authenticate the reservation user based on the preset verification method; when the identity authentication is successful, call the task processing thread to process the reservation task according to the reservation request.

[0130] Each module in the above-mentioned financial product reservation processing device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0131] In one embodiment, a computer device is provided. The computer device may be a server integrated with a reservation processing system. The internal structure diagram thereof may be as follows: Figure 8 As shown. The computer device includes a processor, a memory and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data such as appointment request information, request terminal identification, historical appointment information, etc. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a financial product appointment processing method is implemented.

[0132] Those skilled in the art will understand that Figure 8 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0133] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0134] Receive a reservation request for a financial product, and obtain reservation request information and a request terminal identifier;

[0135] Determining whether there is historical reservation information corresponding to the requesting terminal identifier according to the requesting terminal identifier;

[0136] If there is historical reservation information, then based on the historical reservation information and the reservation request information, a reservation risk detection is performed on the requesting terminal and the reservation request information;

[0137] When there is no appointment risk for both the requesting terminal and the appointment request information, the task processing thread is called to process the appointment task according to the appointment request.

[0138] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0139] Based on the reservation request information and the historical reservation information, obtaining the request generation time of the reservation request information and the historical reservation time of the historical reservation information;

[0140] Perform reservation risk detection on the requesting terminal based on the request generation time and historical reservation time;

[0141] Obtaining a reservation pick-up point for the financial product based on the reservation request information;

[0142] Perform appointment risk detection on the appointment request information based on the appointment extraction point.

[0143] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0144] Compare the request generation time with the historical reservation time to obtain the reservation time difference;

[0145] When the reservation time difference is less than a preset time difference threshold, it is determined that the requesting terminal has a reservation risk.

[0146] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0147] Determine, based on the reservation request information, a user ID of a target user who generates the reservation request;

[0148] Obtaining the target business handling point pre-set by the target user based on the user ID;

[0149] Match the appointment pick-up point with the target business handling point;

[0150] If the match is unsuccessful, it is determined that the appointment request information has an appointment risk.

[0151] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0152] When there is a reservation risk at the requesting terminal, determining that the reservation request is not approved;

[0153] Call the task processing thread to generate and push request failure prompt information.

[0154] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0155] When there is no reservation risk in the requesting terminal and there is a reservation risk in the reservation request information, the identity verification thread is called to obtain the preset verification method of the target user corresponding to the reservation request;

[0156] Authentication of the reservation user is performed based on a preset verification method;

[0157] When the identity authentication is successful, the task processing thread is called to process the reservation task according to the reservation request.

[0158] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0159] Receive a reservation request for a financial product, and obtain reservation request information and a request terminal identifier;

[0160] Determining whether there is historical reservation information corresponding to the requesting terminal identifier according to the requesting terminal identifier;

[0161] If there is historical reservation information, then based on the historical reservation information and the reservation request information, a reservation risk detection is performed on the requesting terminal and the reservation request information;

[0162] When there is no appointment risk for both the requesting terminal and the appointment request information, the task processing thread is called to process the appointment task according to the appointment request.

[0163] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0164] Based on the reservation request information and the historical reservation information, obtaining the request generation time of the reservation request information and the historical reservation time of the historical reservation information;

[0165] Perform reservation risk detection on the requesting terminal based on the request generation time and historical reservation time;

[0166] Obtaining a reservation pick-up point for the financial product based on the reservation request information;

[0167] Perform appointment risk detection on the appointment request information based on the appointment extraction point.

[0168] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0169] Compare the request generation time with the historical reservation time to obtain the reservation time difference;

[0170] When the reservation time difference is less than a preset time difference threshold, it is determined that the requesting terminal has a reservation risk.

[0171] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0172] Determine, based on the reservation request information, a user ID of a target user who generates the reservation request;

[0173] Obtaining the target business handling point pre-set by the target user based on the user ID;

[0174] Match the appointment pick-up point with the target business handling point;

[0175] If the match is unsuccessful, it is determined that the appointment request information has an appointment risk.

[0176] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0177] When there is a reservation risk at the requesting terminal, determining that the reservation request is not approved;

[0178] Call the task processing thread to generate and push request failure prompt information.

[0179] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0180] When there is no reservation risk in the requesting terminal and there is a reservation risk in the reservation request information, the identity verification thread is called to obtain the preset verification method of the target user corresponding to the reservation request;

[0181] Authentication of the reservation user is performed based on a preset verification method;

[0182] When the identity authentication is successful, the task processing thread is called to process the reservation task according to the reservation request.

[0183] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0184] Receive a reservation request for a financial product, and obtain reservation request information and a request terminal identifier;

[0185] Determining whether there is historical reservation information corresponding to the requesting terminal identifier according to the requesting terminal identifier;

[0186] If there is historical reservation information, then based on the historical reservation information and the reservation request information, a reservation risk detection is performed on the requesting terminal and the reservation request information;

[0187] When there is no appointment risk for both the requesting terminal and the appointment request information, the task processing thread is called to process the appointment task according to the appointment request.

[0188] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0189] Based on the reservation request information and the historical reservation information, obtaining the request generation time of the reservation request information and the historical reservation time of the historical reservation information;

[0190] Perform reservation risk detection on the requesting terminal based on the request generation time and historical reservation time;

[0191] Obtaining a reservation pick-up point for the financial product based on the reservation request information;

[0192] Perform appointment risk detection on the appointment request information based on the appointment extraction point.

[0193] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0194] Compare the request generation time with the historical reservation time to obtain the reservation time difference;

[0195] When the reservation time difference is less than a preset time difference threshold, it is determined that the requesting terminal has a reservation risk.

[0196] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0197] Determine, based on the reservation request information, a user ID of a target user who generates the reservation request;

[0198] Obtaining the target business handling point pre-set by the target user based on the user ID;

[0199] Match the appointment pick-up point with the target business handling point;

[0200] If the match is unsuccessful, it is determined that the appointment request information has an appointment risk.

[0201] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0202] When there is a reservation risk at the requesting terminal, determining that the reservation request is not approved;

[0203] Call the task processing thread to generate and push request failure prompt information.

[0204] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0205] When there is no reservation risk in the requesting terminal and there is a reservation risk in the reservation request information, the identity verification thread is called to obtain the preset verification method of the target user corresponding to the reservation request;

[0206] Authentication of the reservation user is performed based on a preset verification method;

[0207] When the identity authentication is successful, the task processing thread is called to process the reservation task according to the reservation request.

[0208] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0209] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0210] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0211] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be construed as limiting the scope of the present application. It should be noted that, for a person of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for processing a financial product reservation, characterized in that: The method comprises: Receive a reservation request for a financial product, and obtain reservation request information and a request terminal identifier; determining, according to the requesting terminal identifier, whether there is historical reservation information corresponding to the requesting terminal identifier; If the historical reservation information exists, performing reservation risk detection on the requesting terminal and the reservation request information based on the historical reservation information and the reservation request information; When there is no reservation risk between the request terminal and the reservation request information, a task processing thread is called to process the reservation task according to the reservation request.

2. The method according to claim 1, characterized in that: The performing reservation risk detection on the request terminal and the reservation request information based on the historical reservation information and the reservation request information comprises: Based on the reservation request information and the historical reservation information, acquiring the request generation time of the reservation request information and the historical reservation time of the historical reservation information; Performing reservation risk detection on the requesting terminal according to the request generation time and the historical reservation time; Acquire a reservation withdrawal point for the financial product based on the reservation request information; The reservation risk detection is performed on the reservation request information according to the reservation extraction point.

3. The method according to claim 2, characterized in that The performing reservation risk detection on the requesting terminal according to the request generation time and the historical reservation time includes: Compare the request generation time with the historical reservation time to obtain a reservation time difference; When the reservation time difference is less than a preset time difference threshold, it is determined that the requesting terminal has a reservation risk.

4. The method according to claim 2 or 3, characterized in that: The performing appointment risk detection on the appointment request information according to the appointment extraction point comprises: Determining, according to the reservation request information, a user identifier of a target user who generates the reservation request; Acquire the target business handling point preset by the target user based on the user identifier; Matching the appointment pick-up point with the target business handling point; If the matching is unsuccessful, it is determined that the reservation request information has a reservation risk.

5. The method according to claim 1, characterized in that The method further comprises: When there is a reservation risk at the requesting terminal, determining that the reservation request is not approved; Call the task processing thread to generate and push request failure prompt information.

6. The method according to claim 1 or 5, characterized in that: The method further comprises: When there is no reservation risk at the requesting terminal and there is a reservation risk at the reservation request information, calling the identity verification thread to obtain a preset verification method of the target user corresponding to the reservation request; Performing identity authentication on the reservation user based on the preset verification method; When the identity authentication is successful, the task processing thread is called to process the reservation task according to the reservation request.

7. A financial product reservation processing device, characterized in that: The device comprises: A request response module, used to respond to a reservation request for a financial product and obtain reservation request information and a request terminal identifier; A historical reservation information determination module, used to determine whether there is historical reservation information corresponding to the requesting terminal identifier according to the requesting terminal identifier; a risk detection module, configured to perform a reservation risk detection on the request terminal and the reservation request information based on the historical reservation information and the reservation request information if the historical reservation information exists; The reservation request processing module is used to call the task processing thread to process the reservation task according to the reservation request when there is no reservation risk between the request terminal and the reservation request information.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

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

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

Images