Flight refund risk management and control method and system
By collecting and analyzing equipment information in flight refund requests, combining ticket purchase information and preset strategies, determining the risk level to determine the method of refund, the problem of lack of risk identification mechanism in the existing technology is solved, and the safety management of flight refunds is realized. Improve the security of online ticket purchases.
Patent Information
- Application Number
- CN202411210244.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-30
- Publication Date
- 2024-12-27
AI Technical Summary
The existing flight refund process lacks an effective risk identification and prevention mechanism, which leads to telecom fraudsters being able to impersonate users to perform ticket refund operations, infringing on the information security and property security of passengers and airlines.
By receiving flight refund requests, collecting current equipment information, and obtaining ticket purchase equipment information from the flight ticket sales information database based on ticket purchase information, determining the risk level in combination with preset risk strategies, and deciding the refund method, including direct refund or intercepting the refund, to prevent illegal operations .
It improves the risk management of flight ticket refunds, enhances the security of online ticket purchases, prevents fraud, and protects the legitimate rights and interests of users and airlines.
Smart Images
Figure CN119204653A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of flight ticket refund management, and in particular to a flight ticket refund risk management method and system. Background Art
[0002] Civil aviation passengers need to refund their tickets due to changes in itinerary or flight delays or cancellations. Passengers apply for refunds online through official websites, apps, etc. At present, the civil aviation industry faces severe challenges from telecommunications fraud. Fraudsters obtain user information through illegal means and then impersonate users to refund tickets, which seriously infringes on the legitimate rights and interests of passengers. The existing refund process lacks an effective risk identification and prevention mechanism, and it is impossible to verify in time whether the refund operation is performed by the user when refunding online, resulting in certain information security and property security issues for both users and airlines. Summary of the invention
[0003] In order to solve the technical problems existing in the background technology, the present invention proposes a flight refund risk management method and system.
[0004] The present invention provides a flight ticket refund risk management method, comprising the following steps:
[0005] S1. Receive a flight refund request and collect the current device information of the flight refund request, including the current device number, current IP address, current login method, and current mobile phone number;
[0006] S2. parse the flight refund request to obtain the corresponding ticket purchase information, which includes user identity information, ticket purchase serial number, ticket purchase flight number, and travel date;
[0007] S3. Obtain the corresponding ticket purchasing device information from the flight ticket information database according to the ticket purchasing information. The ticket purchasing device information includes the ticket purchasing device number, ticket purchasing IP address, and ticket purchasing login mobile phone number;
[0008] S4. Determine the risk level and the refund method corresponding to the risk level based on the ticket purchase device information, the current device information and the preset risk strategy. The risk level includes but is not limited to the first level, the second level, the third level, the fourth level and the fifth level.
[0009] S5. Complete the refund operation or intercept the refund according to the risk level and the refund method corresponding to the risk level.
[0010] Preferably, the flight ticket information database is configured with a one-to-one mapping relationship between the ticket purchase serial number, ticket purchase flight number, travel date, ticket purchase device number, ticket purchase IP address, and ticket purchase login mobile phone number; step S3 specifically includes:
[0011] Obtain the corresponding ticket purchase device number, ticket purchase IP address, and ticket purchase login mobile phone number from the flight ticket information database according to the ticket purchase serial number, ticket purchase flight number, and travel date;
[0012] The ticket purchasing device number, ticket purchasing IP address, and ticket purchasing login mobile phone number will be used as the ticket purchasing device information.
[0013] Preferably, the preset risk strategy specifically includes:
[0014] Compare the ticket purchase device information with the current device information one by one;
[0015] When the ticket purchase device number is the same as the current device number, the risk level is specifically the first level;
[0016] When the ticket purchase device number is inconsistent with the current device number, obtain the current login method and determine whether the risk level is the second level;
[0017] When the current login method is one-click login using a mobile phone number, the risk level is the second level;
[0018] When the current login method is not one-click login using a mobile phone number, obtain the current mobile phone number and determine whether the risk level is the third level;
[0019] When the mobile phone number used to purchase tickets is the same as the current mobile phone number, the risk level is specifically the third level;
[0020] When the mobile phone number used to purchase tickets is inconsistent with the current mobile phone number, obtain the current IP address to determine whether the risk level is level 4;
[0021] When the ticket purchase IP address is the same as the current IP address, the risk level is specifically the fourth level;
[0022] When the ticket purchasing IP address is inconsistent with the current IP address, the risk level is specifically level five.
[0023] Preferably, the refund methods corresponding to the risk levels specifically include:
[0024] The refund methods for the first level are as follows:
[0025] If the device number of the ticket purchase is the same as the current device number, the ticket will be refunded directly;
[0026] The refund methods for the second level are as follows:
[0027] If the current login method is one-click login using a mobile phone number, the ticket will be refunded directly;
[0028] The refund methods for the third level are as follows:
[0029] If the mobile phone number used to purchase the ticket is the same as the current mobile phone number, the ticket will be refunded directly;
[0030] The refund methods for the fourth level are as follows:
[0031] If the IP address used to purchase the ticket is the same as the current IP address, the ticket will be refunded directly;
[0032] The refund methods for the fifth level are as follows:
[0033] Compare the current IP address with the IP addresses in the risk IP database one by one. When there is an IP address in the risk IP database that is consistent with the current IP address, initiate a refund rejection instruction and send a prompt message and manual refund method to the mobile phone number where the ticket was purchased;
[0034] When there is no IP address consistent with the current IP address in the risky IP database, a manual ticket refund process is initiated.
[0035] Preferably, step S5 specifically includes:
[0036] Marking the flight refund request with a risk level to obtain a mapping relationship between the flight refund request and the risk level, and storing the mapping relationship between the flight refund request and the risk level in the flight sales change database;
[0037] Complete the refund operation or block the refund according to the risk level corresponding to the flight refund request and the refund method corresponding to the risk level.
[0038] Preferably, a plurality of risky IP addresses are pre-configured in the risky IP database, and the risky IP database is updated through terminal input.
[0039] The present invention provides a flight refund risk management system, a flight refund risk management system, comprising:
[0040] The data collection module is used to receive flight refund requests and collect the current device information of the flight refund request, including the current device number, current IP address, current login method, and current mobile phone number;
[0041] The data analysis module is used to analyze the flight refund request to obtain the corresponding ticket purchase information, which includes user identity information, ticket purchase serial number, ticket purchase flight number, and travel date;
[0042] The data acquisition module is used to obtain the corresponding ticket purchase device information from the flight ticket information database according to the ticket purchase information. The ticket purchase device information includes the ticket purchase device number, ticket purchase IP address, and ticket purchase login mobile phone number;
[0043] A data processing module, used to determine the risk level and the refund method corresponding to the risk level based on the ticket purchasing device information, the current device information and the preset risk strategy, the risk level includes but is not limited to the first level, the second level, the third level, the fourth level and the fifth level;
[0044] The output module is used to complete the refund operation or intercept the refund according to the risk level and the refund method corresponding to the risk level.
[0045] Preferably, in the data processing module, the preset risk strategy specifically includes:
[0046] Compare the ticket purchase device information with the current device information one by one;
[0047] When the ticket purchase device number is the same as the current device number, the risk level is specifically the first level;
[0048] When the ticket purchase device number is inconsistent with the current device number, obtain the current login method and determine whether the risk level is the second level;
[0049] When the current login method is one-click login using a mobile phone number, the risk level is the second level;
[0050] When the current login method is not one-click login using a mobile phone number, obtain the current mobile phone number and determine whether the risk level is the third level;
[0051] When the mobile phone number used to purchase tickets is the same as the current mobile phone number, the risk level is specifically the third level;
[0052] When the mobile phone number used to purchase tickets is inconsistent with the current mobile phone number, obtain the current IP address to determine whether the risk level is level 4;
[0053] When the ticket purchase IP address is the same as the current IP address, the risk level is specifically the fourth level;
[0054] When the ticket purchasing IP address is inconsistent with the current IP address, the risk level is specifically level five.
[0055] In the present invention, the proposed flight refund risk management method and system receive flight refund requests and collect the current device information of the flight refund request; perform data analysis on the flight refund request to obtain the corresponding ticket purchase information; obtain the corresponding ticket purchase device information from the flight ticket information database according to the ticket purchase information; determine the risk level and the refund method corresponding to the risk level based on the ticket purchase device information, the current device information and the preset risk strategy; complete the refund operation or intercept the refund according to the risk level and the refund method corresponding to the risk level. The risk management of flight refunds is realized and the security of online ticket purchases is improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0056] Figure 1 A schematic diagram of the workflow structure of a flight ticket refund risk management method proposed by the present invention;
[0057] Figure 2 This is a schematic diagram of the implementation process of a flight refund risk management method proposed by the present invention;
[0058] Figure 3 This is a schematic diagram of the system architecture of a flight refund risk management system proposed by the present invention. DETAILED DESCRIPTION
[0059] Reference Figure 1-3 The present invention proposes a flight refund risk management method, comprising the following steps:
[0060] S1. Receive a flight refund request and collect the current device information of the flight refund request, the current device information including the current device number, current IP address, current login method, and current mobile phone number.
[0061] In this embodiment, the current login method includes but is not limited to verification code login, password login, and one-click login with a mobile phone number.
[0062] S2. Parse the flight refund request to obtain corresponding ticket purchase information, which includes user identity information, ticket purchase serial number, ticket purchase flight number, and travel date.
[0063] In this embodiment, by performing data analysis on the flight refund request to obtain the ticket purchase serial number, flight number, and travel date, it is convenient to obtain the device information at the time of ticket purchase based on the ticket purchase information, facilitate device information comparison, and improve the efficiency of refund risk management.
[0064] S3. Obtain the corresponding ticket purchasing device information from the flight ticket information database according to the ticket purchasing information. The ticket purchasing device information includes the ticket purchasing device number, ticket purchasing IP address, and ticket purchasing login mobile phone number.
[0065] In this embodiment, the flight ticket information database is configured with a one-to-one mapping relationship between the ticket purchase serial number, the ticket purchase flight number, the travel date, the ticket purchase device number, the ticket purchase IP address, and the ticket purchase login mobile phone number; step S3 specifically includes:
[0066] According to the ticket purchase serial number, flight number and travel date, the corresponding ticket purchase device number, ticket purchase IP address and ticket purchase login mobile phone number are obtained from the flight ticket information database; and the ticket purchase device number, ticket purchase IP address and ticket purchase login mobile phone number are used as the ticket purchase device information.
[0067] S4. Determine the risk level and the refund method corresponding to the risk level based on the ticket purchasing device information, the current device information and the preset risk strategy. The risk levels include but are not limited to the first level, the second level, the third level, the fourth level and the fifth level.
[0068] In this embodiment, the preset risk strategy specifically includes:
[0069] The ticket purchasing device information is compared with the current device information one by one; when the ticket purchasing device number is consistent with the current device number, the risk level is specifically the first level; when the ticket purchasing device number is inconsistent with the current device number, the current login method is obtained to determine whether the risk level is the second level; when the current login method is specifically one-click login with a mobile phone number, the risk level is specifically the second level; when the current login method is not one-click login with a mobile phone number, the current mobile phone number is obtained to determine whether the risk level is the third level; when the ticket purchasing login mobile phone number is consistent with the current mobile phone number, the risk level is specifically the third level; when the ticket purchasing login mobile phone number is inconsistent with the current mobile phone number, the current IP address is obtained to determine whether the risk level is the fourth level; when the ticket purchasing IP address is consistent with the current IP address, the risk level is specifically the fourth level; when the ticket purchasing IP address is inconsistent with the current IP address, the risk level is specifically the fifth level.
[0070] In this embodiment, when submitting a refund application after logging into the user account, the device number will be checked first, that is, whether the device number is the device number when the user places an order. If the device number is consistent, it means that the current user is the user himself, and the refund can be made directly. If not, the next step of judgment is performed. Among them, the device number changes after changing the login mobile phone and uninstalling and reinstalling the app. When the device number verification is inconsistent, the most recent login method of the account is determined, whether it is a mobile phone number verification code login. If not, the refund can be submitted directly. If it is, there is a risk and it is necessary to continue to the next step of judgment. Through the Umeng SDK, try to obtain the token of the user's current SIM card mobile network and the mobile phone number bound to the account to determine whether the SIM card mobile phone number is consistent with the account mobile phone number. If it is consistent, it means that it is the user himself, and the refund can be submitted directly. If not, it may not be the user himself (dual card users, or users connecting to wifi will also cause inconsistent verification, and it cannot be 100% determined to be a fraudster), and it is necessary to judge further. According to the user's current IP address, it is determined whether it belongs to the risk IP database. If it meets the risk IP database, the refund is intercepted and the manual customer service phone number is displayed, so that the user can contact the manual customer service to verify the identity before submitting the refund.
[0071] In this embodiment, the refund methods corresponding to the risk levels specifically include:
[0072] The refund methods for the first level are as follows:
[0073] If the device number of the ticket purchase is the same as the current device number, the ticket will be refunded directly;
[0074] The refund methods for the second level are as follows:
[0075] If the current login method is one-click login using a mobile phone number, the ticket will be refunded directly;
[0076] The refund methods for the third level are as follows:
[0077] If the mobile phone number used to purchase the ticket is the same as the current mobile phone number, the ticket will be refunded directly;
[0078] The refund methods for the fourth level are as follows:
[0079] If the IP address used to purchase the ticket is the same as the current IP address, the ticket will be refunded directly;
[0080] The refund methods for the fifth level are as follows:
[0081] The current IP address is compared with the IP addresses in the risk IP database one by one. When there is an IP address in the risk IP database that is consistent with the current IP address, a refund rejection instruction is initiated, and a prompt message and manual refund method are sent to the mobile phone number where the ticket was purchased; when there is no IP address in the risk IP database that is consistent with the current IP address, a manual refund process is initiated.
[0082] In this embodiment, a plurality of risky IP addresses are pre-configured in the risky IP database, and the risky IP database is updated through terminal input.
[0083] S5. Complete the refund operation or intercept the refund according to the risk level and the refund method corresponding to the risk level.
[0084] In this embodiment, step S5 specifically includes:
[0085] The flight refund request is marked with a risk level to obtain a mapping relationship between the flight refund request and the risk level, and the mapping relationship between the flight refund request and the risk level is stored in the flight sales change database; the refund operation is completed or the refund is intercepted according to the risk level corresponding to the flight refund request and the refund method corresponding to the risk level.
[0086] Reference Figure 1-3 The present invention proposes a flight refund risk management system, comprising:
[0087] The data collection module is used to receive flight refund requests and collect the current device information that issued the flight refund request. The current device information includes the current device number, current IP address, current login method, and current mobile phone number.
[0088] The data analysis module is used to analyze the flight refund request to obtain the corresponding ticket purchase information, which includes user identity information, ticket purchase serial number, ticket purchase flight number, and travel date.
[0089] The data acquisition module is used to obtain the corresponding ticket purchasing device information from the flight ticket information database according to the ticket purchasing information. The ticket purchasing device information includes the ticket purchasing device number, ticket purchasing IP address, and ticket purchasing login mobile phone number.
[0090] The data processing module is used to determine the risk level and the refund method corresponding to the risk level based on the ticket purchasing device information, the current device information and the preset risk strategy. The risk levels include but are not limited to the first level, the second level, the third level, the fourth level and the fifth level.
[0091] In the data processing module, the preset risk strategies specifically include:
[0092] The ticket purchasing device information is compared with the current device information one by one; when the ticket purchasing device number is consistent with the current device number, the risk level is specifically the first level; when the ticket purchasing device number is inconsistent with the current device number, the current login method is obtained to determine whether the risk level is the second level; when the current login method is specifically one-click login using a mobile phone number, the risk level is specifically the second level; when the current login method is not one-click login using a mobile phone number, the current mobile phone number is obtained to determine whether the risk level is the third level; when the ticket purchasing login mobile phone number is consistent with the current mobile phone number, the risk level is specifically the third level; when the ticket purchasing login mobile phone number is inconsistent with the current mobile phone number, the current IP address is obtained to determine whether the risk level is the fourth level; when the ticket purchasing IP address is consistent with the current IP address, the risk level is specifically the fourth level; when the ticket purchasing IP address is inconsistent with the current IP address, the risk level is specifically the fifth level.
[0093] The output module is used to complete the refund operation or intercept the refund according to the risk level and the refund method corresponding to the risk level.
[0094] The above description is only a preferred specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can make equivalent replacements or changes according to the technical scheme and inventive concept of the present invention within the technical scope disclosed by the present invention, which should be covered by the protection scope of the present invention.
Claims
1. A flight ticket refund risk management method, characterized in that: The following steps are involved: S1. Receive a flight refund request and collect the current device information of the flight refund request, including the current device number, current IP address, current login method, and current mobile phone number; S2. parse the flight refund request to obtain the corresponding ticket purchase information, which includes user identity information, ticket purchase serial number, ticket purchase flight number, and travel date; S3. Obtain the corresponding ticket purchasing device information from the flight ticket information database according to the ticket purchasing information. The ticket purchasing device information includes the ticket purchasing device number, ticket purchasing IP address, and ticket purchasing login mobile phone number; S4. Determine the risk level and the refund method corresponding to the risk level based on the ticket purchase device information, the current device information and the preset risk strategy. The risk level includes but is not limited to the first level, the second level, the third level, the fourth level and the fifth level. S5. Complete the refund operation or intercept the refund according to the risk level and the refund method corresponding to the risk level.
2. The flight ticket refund risk management method according to claim 1, characterized in that: The flight ticket information database is configured with a one-to-one mapping relationship between the ticket purchase serial number, ticket purchase flight number, travel date, ticket purchase device number, ticket purchase IP address, and ticket purchase login mobile phone number; step S3 specifically includes: Obtain the corresponding ticket purchase device number, ticket purchase IP address, and ticket purchase login mobile phone number from the flight ticket information database according to the ticket purchase serial number, ticket purchase flight number, and travel date; The ticket purchasing device number, ticket purchasing IP address, and ticket purchasing login mobile phone number will be used as the ticket purchasing device information.
3. The flight refund risk management method according to claim 1, characterized in that: The preset risk strategy specifically includes: Compare the ticket purchase device information with the current device information one by one; When the ticket purchase device number is the same as the current device number, the risk level is specifically the first level; When the ticket purchase device number is inconsistent with the current device number, obtain the current login method and determine whether the risk level is the second level; When the current login method is one-click login using a mobile phone number, the risk level is the second level; When the current login method is not one-click login using a mobile phone number, obtain the current mobile phone number and determine whether the risk level is the third level; When the mobile phone number used to purchase tickets is the same as the current mobile phone number, the risk level is specifically the third level; When the mobile phone number used to purchase tickets is inconsistent with the current mobile phone number, obtain the current IP address to determine whether the risk level is level 4; When the ticket purchase IP address is the same as the current IP address, the risk level is specifically the fourth level; When the ticket purchasing IP address is inconsistent with the current IP address, the risk level is specifically level five.
4. The flight refund risk management method according to claim 1, characterized in that: The refund methods corresponding to the risk levels include: The refund methods for the first level are as follows: If the device number of the ticket purchase is the same as the current device number, the ticket will be refunded directly; The refund methods for the second level are as follows: If the current login method is one-click login using a mobile phone number, the ticket will be refunded directly; The refund methods for the third level are as follows: If the mobile phone number used to purchase the ticket is the same as the current mobile phone number, the ticket will be refunded directly; The refund methods for the fourth level are as follows: If the IP address used to purchase the ticket is the same as the current IP address, the ticket will be refunded directly; The refund methods for the fifth level are as follows: Compare the current IP address with the IP addresses in the risk IP database one by one. When there is an IP address in the risk IP database that is consistent with the current IP address, initiate a refund rejection instruction and send a prompt message and manual refund method to the mobile phone number where the ticket was purchased; When there is no IP address consistent with the current IP address in the risky IP database, a manual ticket refund process is initiated.
5. The flight refund risk management method according to claim 1, characterized in that: Step S5 specifically includes: Marking the flight refund request with a risk level to obtain a mapping relationship between the flight refund request and the risk level, and storing the mapping relationship between the flight refund request and the risk level in the flight sales change database; Complete the refund operation or block the refund according to the risk level corresponding to the flight refund request and the refund method corresponding to the risk level.
6. The flight ticket refund risk management method according to claim 4, characterized in that: The risky IP database is pre-configured with a plurality of risky IP addresses, and the risky IP database is updated through terminal input.
7. A flight refund risk management system, characterized in that: include: The data collection module is used to receive flight refund requests and collect the current device information of the flight refund request, including the current device number, current IP address, current login method, and current mobile phone number; The data analysis module is used to analyze the flight refund request to obtain the corresponding ticket purchase information, which includes user identity information, ticket purchase serial number, ticket purchase flight number, and travel date; The data acquisition module is used to obtain the corresponding ticket purchase device information from the flight ticket information database according to the ticket purchase information. The ticket purchase device information includes the ticket purchase device number, ticket purchase IP address, and ticket purchase login mobile phone number; A data processing module, used to determine the risk level and the refund method corresponding to the risk level based on the ticket purchasing device information, the current device information and the preset risk strategy, the risk level including but not limited to the first level, the second level, the third level, the fourth level and the fifth level; The output module is used to complete the refund operation or intercept the refund according to the risk level and the refund method corresponding to the risk level.
8. The flight refund risk management system according to claim 7, characterized in that: In the data processing module, the preset risk strategy specifically includes: Compare the ticket purchase device information with the current device information one by one; When the ticket purchase device number is the same as the current device number, the risk level is specifically the first level; When the ticket purchase device number is inconsistent with the current device number, obtain the current login method and determine whether the risk level is the second level; When the current login method is one-click login using a mobile phone number, the risk level is the second level; When the current login method is not one-click login using a mobile phone number, obtain the current mobile phone number and determine whether the risk level is the third level; When the mobile phone number used to purchase tickets is the same as the current mobile phone number, the risk level is specifically the third level; When the mobile phone number used to purchase tickets is inconsistent with the current mobile phone number, obtain the current IP address to determine whether the risk level is level 4; When the ticket purchase IP address is the same as the current IP address, the risk level is specifically the fourth level; When the ticket purchasing IP address is inconsistent with the current IP address, the risk level is specifically level five.